Allied Telesis X900-48FE-N, AT-9924T/4SP-A-20, AT-8948, AT-9924T-40 manual Ports and Recovery Times

Page 30

Ports and Recovery Times

Ports and Recovery Times

In practice, recovery time in an EPSR ring is generally between 50 and 100ms. However, it depends on the port type, because this determines how long it takes for the port to report that it is down and send a Link-Down message.

The following ports report that they are down immediately or within a few milliseconds, which leads to an EPSR recovery time of 50 to 100ms:

10/100M copper RJ-45 ports

tri-speed copper RJ-45 ports operating at 10 or 100M

fiber 1000M ports

10G ports

However, for tri-speed copper RJ-45 ports operating at 1000M, there is a short delay— either 350ms or 750ms—before the port reports that it is down. This is because the IEEE standard for 1000BASE-T specifies that a port must wait for a certain length of time after a link goes down before it decides that the link is actually down (see Section 40.4.5.2 of IEEE Std 802.3-2002). The length of the wait depends on whether the 1000BASE-T port is “master” or “slave” end of the link (“master” and “slave” are determined when the port autonegotiates and are not related to the master node of EPSR). If a 1000BASE-T port is the master the wait is 750ms; if it is the slave, the wait is 350ms.

This means that if a 1000M copper link goes down between two transit nodes, EPSR recovers after approximately 350ms. The EPSR nodes at both ends of the broken link send a Link-Down message when they detect that the link has gone down. As the diagram shows, the node at the slave end of the link sends a Link-Down message in 350ms. The node at the master end does not send a Link-Down message until 750ms have passed, but by then the EPSR master node has already handled the first Link- Down message. You can see the messages in the debugging output in "Link Down Between Two Transit Nodes" on page 47.

 

 

Master

1

Link-Down

 

 

Node

 

 

after 350ms

 

 

 

 

 

 

Transit

 

 

 

Transit

Node

 

 

 

 

 

 

 

Node

 

slave end

 

 

 

of link

2

Link-Down

Transit

 

 

Node

 

 

 

after 750ms

master end

 

 

 

 

 

 

 

 

of link

 

 

 

 

 

 

epsr-copper

For almost all networks, this slight delay in recovery has no practical effect. For networks with extremely stringent failover requirements, we recommend using fiber 1000M ports instead of copper.

Page 30 AlliedWare™ OS How To Note: EPSR

Image 30
Contents Introduction What information will you find in this document?Which products and software versions does it apply to? How Epsr Works Epsr ComponentsEstablishing a Ring Recovering from a Fault Fault in a link or a transit nodeFault in the master node Transit Nodes with One Port Down Restoring Normal OperationMaster Node Transit Nodes with Both Ports DownHow To Configure Epsr Configuring EpsrEnable Epsr Iii. Remove the ring ports from the default VlanIv. Configure the Epsr domain Configure other ports and protocols as requiredModifying the Control Vlan Configure the Master Node a Example 1 a Basic RingCreate the Epsr domain Configure the Transit Nodes B and CRemove the ring ports from the default Vlan Add the data Vlan to the domainCreate epsr=test mode=transit controlvlan=vlan1000 Configure the master node switch a for domain Example 2 a Double RingConfigure the master node switch C for domain Configure EpsrConfigure the data Vlan for domain Configure the master node switch a for the Epsr domain Example 3 Epsr and RstpRemove the STP VLAN’s ports from the default Vlan Configure switch E for Epsr and Rstp Example 4 Epsr with Nested VLANs Epsr DomainConfigure the Epsr control Vlan Configure client switch G connected to transit node C Configure client switch E connected to the master nodeConfigure client switch F connected to transit node B Configure client switch H connected to transit node DExample 5 Epsr with management stacking Configure stacking on the first transit node host2 Configure stacking on the second transit node host3Configure the other VLANs on the stacked switches Configure Epsr on the stacked switchesConfigure the AT-TN7100 iMAP as Master Node Example 6 Epsr with an iMAPChecking the Master Node Configuration Following diagram shows the expected outputConfigure the AT-TN7100 iMAP as a Transit Node Checking the Transit Node ConfigurationClassifiers and Hardware Filters LINKS-UPPorts and Recovery Times Igmp Snooping and Recovery Times Health Message PriorityEpsr State and Settings Epsr Information Name Domain1 Snmp Traps Counters Master Node Node a Debug Output DebuggingLink Down Between Master Node and Transit Node Master node sends Health messagesMaster node continues sending Health messages Primary port goes downMaster node transmits a Ring-Down-Flush-FDB message Hello timer expires Hello timer expires againPrimary port comes back up Master node returns the ring to a state of Complete Master node receives the Ring-Up-Flush-FDB message on portMaster node transmits and receives Health messages Transit Node Node B Debug Output Transit node receives Health messagesPort 1 on the transit node goes down Transit node receives a Ring-Down-Flush-FDB messagePort 1 comes back up Transit node receives a Health messageTransit node receives a Ring-Up-Flush-FDB message 252 Link Down Between Two Transit Nodes Link between the two transit nodes goes down Master node receives a second Link-Down message Master node receives a Health message 51 AlliedWare OS How To Note Epsr 375 53 AlliedWare OS How To Note Epsr Transit node sends a Link-Down message Link comes back up Transit node receives another Health messageTransit node receives a Ring-Up-Flush-FDB message

AT-9924SP-30, AT-9924T-40, AT-8948, AT-9924T/4SP-A-20, X900-48FE-N specifications

Allied Telesis is a leading provider of networking solutions, renowned for its innovative technologies and high-performance networking equipment. Among its extensive product lineup, the X900-48FE-N, AT-9924T-40, AT-8948, AT-9924T/4SP-A-20, and AT-9924SP-30 stand out for their remarkable features and capabilities.

The X900-48FE-N is a robust layer 2/3 managed switch that features 48 Fast Ethernet ports. This model is particularly known for its energy efficiency and reliability, making it a suitable choice for enterprises with demanding networking needs. It supports a wide range of Layer 2 Ethernet switching technologies, including VLANs, Spanning Tree Protocol (STP), and Link Aggregation Control Protocol (LACP), which enhances network reliability and efficiency.

The AT-9924T-40 is a versatile switch designed for high-performance environments. It offers a rich set of features, including 24 Gigabit Ethernet ports and 4 SFP ports for fiber connectivity. This device is equipped with Advanced Layer 2 and Layer 3 features, including IPv4/IPv6 support, Quality of Service (QoS) capabilities, and robust security options. This switch is ideal for core and distribution deployments within enterprise networks, ensuring fast and reliable connectivity.

The AT-8948 is another important model in Allied Telesis' offerings. It features 48 10/100 Mbps Ethernet ports and 4 Gigabit uplink ports, providing a high density of connectivity options. The AT-8948 is also equipped with advanced management capabilities, including SNMP, RMON, and web-based management, allowing for easy configuration and monitoring of the network.

The AT-9924T/4SP-A-20 offers a combination of 24 Gigabit Ethernet ports and 4 SFP slots to extend network capabilities through fiber connections. It is particularly well-suited for environments requiring high bandwidth and flexible connectivity. Its compact design makes it an excellent choice for data centers and enterprise networks.

Lastly, the AT-9924SP-30 is characterized by its 24 Gigabit SFP ports, offering flexibility in terms of fiber connectivity. This switch supports advanced routing capabilities and is designed for high-availability environments. Its ability to handle diverse network traffic while maintaining optimal performance makes it a valuable asset for any modern enterprise.

In summary, these Allied Telesis models showcase advanced features, network reliability, and versatile management options, making them critical components for efficient and scalable networking solutions.