Extreme Networks ExtremeWare XOS Command Reference Manual page 913

However, if you have a partner switch with the segment-timeout expiry action set to
and the controller switch does not have a segment timer configuration, you must configure the
partner switch's segment-timeout expiry action to
If you have a network containing non-Extreme Networks switches, set the segment-timeout expiry
●
action to
segment-down
The following events may cause a ring segment failure:
There is a hardware failure.
●
The controller or partner received a Link Down message from the partner or controller, respectively.
●
The segment timer expires and the expiry action was set to segment down. This means that either
●
the controller or partner did not receive health check messages during the defined segment timeout.
To view shared-port information, including shared-port segment status, use the
port {<port>} {detail}
Example
The following example makes the following assumptions:
The controller switch is an Extreme Networks switch running ExtremeWare XOS 11.1
●
The partner switch is an Extreme Networks switch running ExtremeWare 7.3
●
The following command configures the controller to keep the segment down if the segment-timeout
expires:
configure eaps shared-port 3:3 segment-timeout expiry-action segment-down
History
This command was first available in ExtremeWare XOS 11.1.
Platform Availability
This command is available on all platforms with a Core or an Advanced Core license.
ExtremeWare XOS 11.3 Command Reference
configure eaps shared-port segment-timeout expiry-action
.
command.
.
segment-down
,
send-alert
show eaps shared-
913