Shutting Interface VLAN 1 down should not create any problems since the VLAN 1 itself will still be active. The question is that the latest IOS version allows you to remove VLAN 1 from you trunk ports which is fine as long as the Data and the Management VLAN is not 1. I was reading Cisco LAN Switching Book, and found out that most of the control traffic such as VTP, DISL/DTP (used for trunk negotiation) , CDP, and PAGP always use VLAN 1. Won't it create a major problem if VLAN 1 is removed from the trunk links. When is it possible to remove VLAN 1 from all trunk links.
VTP pruning cannot be applied to VLANs that need to exist everywhere and to be allowed on all switches in the campus (to be able to carry VTP, CDP traffic, and other control traffic). There is a way, however, to limit the extent of VLAN 1. This is a feature called VLAN 1 disable on trunk, and it is available on Catalyst 4000, 5000, and 6000 family switches since Cisco IOS release 5.4(x). This allows you to prune VLAN 1 from a trunk as you would do for any other VLAN, but this pruning will not include all of the control protocol traffic that will still be allowed on the trunk (DTP, PagP, CDP, VTP, and so on). However, you will block all user traffic on that trunk. Using this feature, you can completely avoid the VLAN spanning the entire campus, and as such, STP loops will be limited in extent, even in VLAN 1. You can configure VLAN 1 to be disabled as you would configure other VLANs to be cleared from the trunk by issuing the following commands:
Thanks Steve, This really cleared up lot of the issues for me. According to your reply, it means that if i clear VLAN1 from my all trunk links as you are recommending that everybody should do then it only disable VLAN for user traffic, but still enable for the control traffic. My swich has an integrated IOS, so I will just remove vlan1 from my all trunk links.
Should it matter what LAN Design one has. For Example, in my design I have two 6509 backbone switches with about 10 VLANS. Each Floor has it own Switch and VLAN. I am restricting my trunk links to each switch only to take the VLANS assigned to each floor. I will go head and also remove VLAN1 from all trunk links as well since it will still carry controll traffic.
Yes, user data filtered but control traffic (DTP, PagP, CDP, VTP, and so on) allowed. Generally though, users/servers shouldn't be placed on vlan 1 anyway.
It shouldn't work with IOS switches though, only CatOS 5.4(x) or greater. You can set the trunk port to prune (switchport trunk pruning vlan ...) vlan 1, but not to remove/clear (switchport trunk allowed vlan...) vlan 1. You cannot remove any of the default VLANs (vlan 1 is default for ethernet) from a trunk on IOS trunks.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...