[cisco-voip] Proper VLANS and IPs
Lelio Fulgenzi
lelio at uoguelph.ca
Tue Sep 30 08:57:35 EDT 2008
There's nothing wrong with using different VLANs for voice, servers and data.
Using VLAN 1 for anything should likely be avoided though since that is the default VLAN if trunking goes awry.
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Bad grammar makes me [sic]" - Tshirt
----- Original Message -----
From: "Jay Prailun" <j23paul at gmail.com>
To: cisco-voip at puck.nether.net
Sent: Tuesday, September 30, 2008 8:47:32 AM GMT -05:00 US/Canada Eastern
Subject: [cisco-voip] Proper VLANS and IPs
I have inherited this project from a project manager who just left with no warning. I always noticed he and I did things a bit differently, but this one has me stumped.
4 buildings, linked by fiber. CCM 6.1 and Unity. 2801s for SRST and 911 in each building. 10-15 phones per building, so total of 60 (actual total shows 52).
He has CCM and Unity in VLAN 7 in the .7 subnet.
Phones are in VLAN 6 and in the .6 subnet.
Doesn't this mean that for each packet in the voice stream, we will have to traverse the router to get to the diff subnet? Is this common to do it this way, leaving CCM and Unity in their own subnet and VLAN? If the main router were to have an issue, all phone traffic would die, it seems.
Data is in VLAN 1 in the .1 subnet.
Depending on who I get in TAC, this is either fine,or troubling, since Cisco's mgt traffic uses VLAN1. But with only about 50 users, so figure 50 PCs, would this be an issue running the data on VLAN1?
Your thoughts?
_______________________________________________ cisco-voip mailing list cisco-voip at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080930/6a92f175/attachment.html>
More information about the cisco-voip
mailing list