Andrew,
I don't have a link right off hand but I can give you the main reasons why
its a bad idea. You don't want to mix user traffic with control and
management traffic.
Certain protocols always run over VLAN 1. These protocols include VTP, STP,
CDP, PAgP, and DISL/DTP. Other protocols use the VLAN associated with the
switch's management interface (sc0). These protocols include telnet, tftp,
syslog, ping, and SNMP. Making this VLAN1 keeps all your control and
management traffic to a single VLAN. Also, setting the native VLAN for
trunking ports to VLAN 1 allows access to the management interface of the
switches should trunking go down (as long as your router or MSFC/RSM has a
subinterface set up for VLAN 1). Anyway, if ytou set the priority for
traffic on VLAN 1 higher than regular user traffic, you'll always be able to
manage the network/switches even if the user traffic is swamping it.
Another option is to use one VLAN for control traffic (VLAN 1), another VLAN
for management traffic, and other VLANs for user traffic.
Hope this helps,
Karen
*********** REPLY SEPARATOR ***********
On 5/7/2001 at 1:15 PM Andrew Shappell wrote:
>I remember reading somewhere that using VLAN 1 in a large switching
>environment is a bad idea. I have been searching CCO for this
>information, but have been unsuccessful in locating it. Does anybody
>have a link to CCO explaining this in more detail??
>
>--
>Andrew E. Shappell
>CCNP & CCDP
>Data Engineering
>FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=3485&t=3475
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
