XRN Stack Reboot

[Cghostino]

Hi Guys,

we have an XRN stack of four 5500G. if we shutdown one switch, the network continues to be stable but when putting that switch ON, all the stack reboots.

Notes:

1-the same issue happened when rebooting all the switches

2-First auto-numbering was configured and later we tried manual unit IDs but still the same behavior.

any idea??

Thanks

[rogero]

We have the same problem on 5500G with last firmware (V3.03.02p05) but I saw yesterday on software features from release notes it support only 4 GE ports (or 8 FE ports) on 1 of 8 possible aggregation groups.

In our configuration, backbone of this 6 units stack is made with ang aggragation of 6 GE ports ?

Is it possible problem come from this number ports aggregation ?

Thanks

[Cghostino]

Hi Guys,

we have an XRN stack of four 5500G. if we shutdown one switch, the network continues to be stable but when putting that switch ON, all the stack reboots.

Notes:

1-the same issue happened when rebooting all the switches

2-First auto-numbering was configured and later we tried manual unit IDs but still the same behavior.

any idea??

Thanks

[Fred_Mancen_1]

Are you using the last software version on the switches? Check the file system of the units, with the command "dir /fabric"; all the files in the entire stack are the same? I always use the fixed unit ID, setting manually the IDs and names of the units, but if there's a problem with auto-numbering maybe this is the cause of the reboot.

[Cghostino]

hey rogero,

after long investigation, it seems the problem is related to link aggregation issues.

are u still facing the problem?

BR

[rogero]

Thanks Cghostino,

It seems error is only on release note (4 GE ports (or 8 FE ports) on 1 of 8 possible aggregation groups) ....We must read 4 x10GE ports  (or 8 GE ports) on 1 of 8 possible aggregation groups.

But I still facing the problem.!

Best regards

Rogero

[Fred_Mancen_1]

Rogero, in the last year I faced a problem like yours; the stack was rebooting itself several times without logging any issue. After a couple hours troubleshooting I figured out a little difference between the name of tha config file of a unit; after equalize ALL the file names of the .cfg files the problem stopped.

Actually I don't know if this case is exactly the same as you are facing, but if all the switches are running the latest versions and are with the unit IDs fixed, I cannot think in anything else.

Regards