krishna.puthraya wrote:
We had a issue recently in our network. The issue follows as below:
A application server was introduced in the core switch running a Cat IOS, but the vlan configuration of the port was missed, and the traffic had taken the native vlan 1. This server was generating a huge traffic, and all of a sudden the switch went in a hung state. now the question is How does the switch handles the traffic if not configured to any vlan and does the traffic flows in the native vlan..? Does this makes the switch to go into the hung state.?
Pls let me know whether traffic on the native vlan creates this kind of issue
By default the native vlan is vlan 1. However it doesn't have to be so don't necessarily confuse the native vlan and the default vlan a port goes into. If you do not configure the port with a vlan it will by default be in vlan 1. This may or may not be the native vlan depending on whether you have changed it or not.
As for how the switch handles vlan 1 traffic, pretty much the same as it handles all the other vlans traffic. There is nothing special in those terms for vlan 1 (although vlan 1 is special in other ways). So by itself that would not necessarily cause your switch to hang.
It's hard to say why your switch hung without further details.
Jon
