Submission + - question about Cisco redundancy?
data plumber writes: This is regarding a corporate LAN enviroment. Dual, redundant Cisco 6509s running dual, redundant fiber uplinks to 3750 stacks (the works). Redundancy all around in an effort to not have any downtime for a pysical problem. One stacking port goes bad and the 3750 stack starts sending data up both fiber uplinks to both 6509 cores jabbering about it's IP address while the stacking ports are arguing about whick one has a connection or not. The result is routing loops on the cores and a corporate LAN that packs up. This is the "industry leading giant" that can have a corporate LAN taken out by 1(one) bad port that all this redundancy is supposed to prevent from happening?
So you call vendor tech support...... You spend all this time and money engineering a solution, buying equipment from a vendor that is not exactly the "loss leader" of the industry and you get a poop response like the one below.
Cisco bug CSCsc54052 -
Description:
A Cisco 3750 Stack with a single faulty stacking port may cause unexpected conditions.
Symptoms
1) other non-related stacking ports may flap in addition to the faulty stacking port:
%STACKMGR-6-STACK_LINK_CHANGE: Stack Port 1 Switch 5 has changed to state DOWN
%STACKMGR-6-STACK_LINK_CHANGE: Stack Port 1 Switch 5 has changed to state UP
2) switches not associatated with the faulty stack port may hang
Workaround
Remove and replace the switch that has a faulty stacking port.
Please let me know if you have futher questions
Aynone else having this kind of fun and are there any fixes other than pitching the several mil$ network equipment and starting again? Please remeber, I did not design this, I just fix it.
So you call vendor tech support...... You spend all this time and money engineering a solution, buying equipment from a vendor that is not exactly the "loss leader" of the industry and you get a poop response like the one below.
Cisco bug CSCsc54052 -
Description:
A Cisco 3750 Stack with a single faulty stacking port may cause unexpected conditions.
Symptoms
1) other non-related stacking ports may flap in addition to the faulty stacking port:
%STACKMGR-6-STACK_LINK_CHANGE: Stack Port 1 Switch 5 has changed to state DOWN
%STACKMGR-6-STACK_LINK_CHANGE: Stack Port 1 Switch 5 has changed to state UP
2) switches not associatated with the faulty stack port may hang
Workaround
Remove and replace the switch that has a faulty stacking port.
Please let me know if you have futher questions
Aynone else having this kind of fun and are there any fixes other than pitching the several mil$ network equipment and starting again? Please remeber, I did not design this, I just fix it.
