cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1354
Views
5
Helpful
7
Replies

Vlan trunk causing reboot

I have a Layer 2 campus, a core that does our routing and a distribution switch that connects to all our access switching. All vlans are carried by Tengig interface trucks and bundles into a L2 ether channel with LACP. A few instances I’ve added a vlan to the interface trunk and the switch automatically reboots, has anyone had this issue and found the cause? Or is this a bug in the 17.9.1 IOS? Feedback is much appreciated.

1 Accepted Solution

Accepted Solutions

Leo Laohoo
Hall of Fame
Hall of Fame

Look at the firmware version the switch is running.  Pay close attention to the last digit, a "1".  

I would never recommend anyone use a firmware version that ends with a 1 or a 2.  

My recommendation is upgrade to 17.9.3.

View solution in original post

7 Replies 7

Hi

   This can be a Bug of course but I am wondering if you repeted the process in order to make sure that the act of adding the vlan to the trunk caused the device to reload. If you did it once and the switch reloaded but it was one time thing, it might have another explanation. But if you repeat the action and you got the same result then you probably hit a Bug as dont make any sense a device reload like this.

  If you can, report this to Cisco through a TAC case.

We had the same issue in another IDF with a stack running an older IOS but with the base ".1" firmware. We will be upgrading the firmware.

Leo Laohoo
Hall of Fame
Hall of Fame

Look at the firmware version the switch is running.  Pay close attention to the last digit, a "1".  

I would never recommend anyone use a firmware version that ends with a 1 or a 2.  

My recommendation is upgrade to 17.9.3.

Thanks for your input, we will be upgrading the firmware soon.

There loop in you network'

The broadcast storm make cpu/memory up to 90-100% this lead SW to reboot. 

Check the stp and if you can check cpu when add vlan.

My STP setup is to use the spanning-tree extend system-id, we have our distribution priority manually set to 24,576 with the system ID config, while the access layer uses the default priority.

You already select solution' If not work then we can go further in troubleshooting.

Thanks 

MHM