In the recent past, I had deleted a given vlan from our VTP server thus removing the vlan from all client switches in the network.
Last week I did an upgrade to the IOS on one of our access switches and lost connectivity with it upon the reload. A physical inspection of the access switch showed there to be no link light....but consoling in showed the new IOS came up fine and the configuration was not corrupted.
Looking at the core switched also showed no link light to that access switch. Telnetting into the core switch and looking at that port showed that the port had been associated with that previously mentioned vlan that had been deleted awhile back.
Upon resetting the port on the access switch to the proper vlan membership restored connectivity to the access switch.
My question is how, by reloading the access switch, did it try and negotiate a vlan membership of a vlan that was non-existant with the core and/or what could have caused the core to 'misconfigure' itself like this?
"Be the packet."
Last week I did an upgrade to the IOS on one of our access switches and lost connectivity with it upon the reload. A physical inspection of the access switch showed there to be no link light....but consoling in showed the new IOS came up fine and the configuration was not corrupted.
Looking at the core switched also showed no link light to that access switch. Telnetting into the core switch and looking at that port showed that the port had been associated with that previously mentioned vlan that had been deleted awhile back.
Upon resetting the port on the access switch to the proper vlan membership restored connectivity to the access switch.
My question is how, by reloading the access switch, did it try and negotiate a vlan membership of a vlan that was non-existant with the core and/or what could have caused the core to 'misconfigure' itself like this?
"Be the packet."