Salman, For FCX (and ICX6610 unless you need mixed family stacking) you should stick to the 7.3.0 code train. I recommend going to 7.3.0h. 7.3.0j is newer, however I had stack communication issues with it (just like you're seeing with 7.4f).
--Jon (works for Brocade) On Thu, Jun 5, 2014 at 5:26 AM, salman sadiq <[email protected]> wrote: > Dear Team, > We have around 300 FCX HPOE switches in a campus network. All of > them are stacks. After upgrading to 7.4f we have seen a lot of stack sync > issues. The standby unit in all the cases seems to be the source of the > problem. Rebooting the stack causes the standby unit to go unresponsive > unless the unit is hard rebooted. The show stack connection command shows > the following. > > sh stack connection > > Probing the topology. Please wait ... > > telnet@SW1-XXX# > > active standby > > +---+ +---+ > > -2/1| 1 |2/2--2/1| 2 |2/2- > > | +---+ +---+ | > > | | > > |------------------------| > > > > > > **** Error! there should be 2 links, but 0.* > > **** Error! no CPU to CPU: u1 -x- u2,* > > From another switch > > active standby > +---+ +---+ +---+ +---+ +---+ +---+ > -2/1| 1 |2/2--2/1| 2 |2/2--2/1| 3 |2/2--2/1| 4 |2/2--2/1| 5 |2/2--2/1| 6 > |2/2- > | +---+ +---+ +---+ +---+ +---+ > +---+ | > | > | > | > | > | > +---+ | > ------------------------------------------------------------------2/2| 7 > |2/1- > +---+ > > *** Error! should have 7 links, but 5: missing u2-u3, u3-u4, . > Link 1: u7 -- u1, num=1 > 1: 1/2/1 (P0) <---> 7/2/2 (P1) > Link 2: u2 -- u1, num=1 > 1: 1/2/2 (P1) <---> 2/2/1 (P0) > Link 3: u5 -- u4, num=1 > 1: 4/2/2 (P1) <---> 5/2/1 (P0) > Link 4: u6 -- u5, num=1 > 1: 5/2/2 (P1) <---> 6/2/1 (P0) > Link 5: u7 -- u6, num=1 > 1: 6/2/2 (P1) <---> 7/2/1 (P0) > *** Error! no CPU to CPU: u1 -x- u3, > *** Error! no CPU to CPU: u2 -x- u3, > *** Error! no CPU to CPU: u3 -x- u4, > *** Error! no CPU to CPU: u3 -x- u5, > *** Error! no CPU to CPU: u3 -x- u6, > *** Error! no CPU to CPU: u3 -x- u7, > > > Anyone has seen this before? I'm working with the TAC but they seem to be > clueless as of now. > > BR > Salman > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp >
_______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
