techmiss
asked on
Extreme EPS-500 Switch Error
Sounds like a stacking issue to me, check or replace the cables if you have spares. What version XOS do they run?
ASKER
Hi, thanks for your reply - don't have any spare cables but will investigate!
Version is 12.2.1.1 v1221b1
Version is 12.2.1.1 v1221b1
What do you get from the 'sh stacking' command?
ASKER
Slot-1 IPI_CORE_HQ.2 # sh stacking
Stack Topology is a Ring
Active Topology is a Ring
Node MAC Address Slot Stack State Role Flags
------------------ ---- ----------- ------- ---
*00:04:96:35:c1:84 1 Active Master CA-
00:04:96:35:c1:f8 2 Active Standby CA-
* - Indicates this node
Flags: (C) Candidate for this active topology, (A) Active Node
(O) node may be in Other active topology
Stack Topology is a Ring
Active Topology is a Ring
Node MAC Address Slot Stack State Role Flags
------------------ ---- ----------- ------- ---
*00:04:96:35:c1:84 1 Active Master CA-
00:04:96:35:c1:f8 2 Active Standby CA-
* - Indicates this node
Flags: (C) Candidate for this active topology, (A) Active Node
(O) node may be in Other active topology
That looks fine. If you 'sh port 2:1' does it display details as you would expect?
ASKER
Yep, nothing out of the ordinary at all.
Just to clarify, as it is a 2 switches stacked - for a continuity point of view if I spread a device, such a server, across both switches, if one goes down it should still be able to survive with the second?
I think the way they have it here is as a "100 port switch" and have not split any devices to take into account resilency.
Thanks
Just to clarify, as it is a 2 switches stacked - for a continuity point of view if I spread a device, such a server, across both switches, if one goes down it should still be able to survive with the second?
I think the way they have it here is as a "100 port switch" and have not split any devices to take into account resilency.
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Everything is back to normal now - after the swiches were rebooted via a console session. (in future a bit more troubleshooting needs to be done at the time).
I was thinking of bridging the NICs on the server and splitting them across the stack...
I have a nasty taste in my mouth when I can't find a route cause!
I was thinking of bridging the NICs on the server and splitting them across the stack...
I have a nasty taste in my mouth when I can't find a route cause!
ASKER
Thanks for the help, I'll close the question as all seems to be working fine now. I've logged a SA with Extreme just to be safe.
K
K