Fun (not!) with virtual CSM ports
One of the things that we found recently, which might relate to some of the ATM instabilities we've had lately, was that the configurations of several ports on a key switch were not quite right. So last night I fixed them and rebooted the switch.
Unfortunately, one of the incorrect ports was a virtual port on the FCSM, and it came up in a non-working state. So there was no way to fix that from home; I had to come into the data center to the console to even talk to the switch.
Somehow, it had originally let me change the state of the port, but now would not let me fix it because it was "in use". I tried several different ways to try and clear that, without success.
What finally worked was to shut down the switch, pull its DS3 and OC3 cards so nothing would be seen by the FCSM, reboot, fix the FCSM port config, shutdown, reinsert the cards, and reboot. It's now up and working, and traffic is once more flowing between the campuses.
Unfortunately, one of the incorrect ports was a virtual port on the FCSM, and it came up in a non-working state. So there was no way to fix that from home; I had to come into the data center to the console to even talk to the switch.
Somehow, it had originally let me change the state of the port, but now would not let me fix it because it was "in use". I tried several different ways to try and clear that, without success.
What finally worked was to shut down the switch, pull its DS3 and OC3 cards so nothing would be seen by the FCSM, reboot, fix the FCSM port config, shutdown, reinsert the cards, and reboot. It's now up and working, and traffic is once more flowing between the campuses.
