Page 1 H3C S5500-SI Series Ethernet Switches High Availability Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Document Version: 20100722-C-1.03 Product Version: Release 2202...
Page 2 SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V G, V G, PSPT, XGbus, N-Bus, TiGem, InnoVision and HUASAN are trademarks of Hangzhou H3C Technologies Co., Ltd. All other trademarks that may be mentioned in this manual are the property of their respective owners.
Page 3 The H3C S5500-SI documentation set includes 9 configuration guides, which describe the software features for the S5500-SI Series Ethernet Switches and guide you through the software configuration procedures. These configuration guides also provide configuration examples to help you apply software features to different network scenarios.
Page 4 Means reader be careful. Improper operation may cause data loss or damage to equipment. Means a complementary description. About the H3C S5500-SI Documentation Set The H3C S5500-SI documentation set also includes: Category Documents Purposes Marketing brochures Describe product specifications and benefits.
Page 5 Obtaining Documentation You can access the most up-to-date H3C product documentation on the World Wide Web at http://www.h3c.com. Click the links on the top navigation bar to obtain different categories of product documentation: [Technical Support &...
Page 6: Table Of Contents
Table of Contents 1 High Availability Overview ····················································································································1-1 Availability Requirements ····················································································································1-1 Availability Evaluation ··························································································································1-1 High Availability Technologies ·············································································································1-2 Fault Detection Technologies·······································································································1-2 Protection Switchover Technologies ····························································································1-3 2 Ethernet OAM Configuration·················································································································2-1 Ethernet OAM Overview ······················································································································2-1 Background ··································································································································2-1 Major Functions of Ethernet OAM ································································································2-1 Ethernet OAMPDUs ·····················································································································2-1 How Ethernet OAM Works ···········································································································2-3 Standards and Protocols ··············································································································2-6...
Page 7 Configuration Prerequisites ········································································································3-10 Finding the Path Between a Source MEP and a Target MEP····················································3-10 Enabling Automatic LT Messages Sending················································································3-10 Displaying and Maintaining CFD ·······································································································3-10 CFD Configuration Examples ············································································································3-11 Configuring Service Instance ·····································································································3-11 Configuring MEP and Enabling CC on it ····················································································3-12 Configuring the Rules for Generating MIPs················································································3-14 Configuring LB on MEPs ············································································································3-15 Configuring LT on MEPs ············································································································3-15...
Page 8 Configuring an RRPP Ring Group ·····································································································5-17 Displaying and Maintaining RRPP ·····································································································5-18 RRPP Configuration Examples··········································································································5-19 Single Ring Configuration Example····························································································5-19 Intersecting Ring Configuration Example ···················································································5-21 Intersecting-Ring Load Balancing Configuration Example ·························································5-26 Troubleshooting ·································································································································5-35 6 Smart Link Configuration ····················································································································6-36 Smart Link Overview··························································································································6-36 Background ································································································································6-36 Terminology································································································································6-37 How Smart Link Works ···············································································································6-38 Smart Link Collaboration Mechanisms·······················································································6-39...
Page 9 Displaying and Maintaining Track Object(s) ························································································8-4 Track Configuration Examples·············································································································8-4 Static Routing-Track-NQA Collaboration Configuration Example ················································8-4 9 Index ························································································································································9-1...
Page 10: High Availability Overview
High Availability Overview With the wide deployment of various types of value-added services such as IPTV and video conference, communication interruption may affect these services and result in serious lost. Therefore, as the carrier of services, the availability of basic network infrastructures is becoming a great concern.
Page 11: High Availability Technologies
MTTR MTTR is the average time required to repair a failed system. MTTR in a broad sense also involves spare parts management and customer services. MTTR = fault detection time + hardware replacement time + system initialization time + link recovery time + routing time + forwarding recovery time.
Page 12: Protection Switchover Technologies
Technology Introduction Reference Network Network Quality Analyzer (NQA) analyzes network performance, Management and services and service quality through sending test packets, and Monitoring provides you with network performance and service quality Configuration parameters such as jitter, TCP connection delay, FTP connection Guide/NQA delay and file transfer rate.
Page 13 Technology Introduction Reference Smart Link is a feature developed to address the slow High Availability convergence issue with STP. It provides link redundancy as well Configuration Smart Link as fast convergence in a dual uplink network, allowing the backup Guide/Smart Link link to take over quickly when the primary link fails.
Page 14: Ethernet Oam Configuration
Ethernet OAM Configuration When configuring the Ethernet OAM function, go to these sections for information you are interested Ethernet OAM Overview Ethernet OAM Configuration Task List Configuring Basic Ethernet OAM Functions Configuring Link Monitoring Enabling OAM Remote Loopback Displaying and Maintaining Ethernet OAM Configuration Ethernet OAM Configuration Example Ethernet OAM Overview Background...
Page 15 Figure 2-1 Formats of different types of Ethernet OAMPDUs The fields in an OAMPDU are described as follows: Table 2-1 Description of the fields in an OAMPDU Field Description Destination MAC address of the Ethernet OAMPDU. It is a slow protocol multicast address 0180c2000002. As slow protocol Dest addr packet cannot be forwarded by bridges, Ethernet OAMPDUs cannot be forwarded.
Page 16: How Ethernet Oam Works
Table 2-2 Functions of different types of OAMPDUs OAMPDU type Function Used for transmitting state information of an Ethernet OAM entity (including the Information information about the local device and remote devices, and customized information) to OAMPDU the remote Ethernet OAM entity and maintaining OAM connections Event Notification Used by link monitoring to notify the remote OAM entity when it detects problems on the OAMPDU...
Page 17 Passive Ethernet OAM Item Active Ethernet OAM mode mode Available (if both sides operate in Responding to Loopback Control OAMPDUs Available active OAM mode) OAM connections can be initiated only by OAM entities operating in active OAM mode, while those operating in passive mode wait and respond to the connection requests sent by their peers. No OAM connection can be established between OAM entities operating in passive OAM mode.
Page 18 Ethernet OAM link events Description When the number of error frame seconds detected on a port over a Errored frame seconds event detection interval reaches the error threshold, an errored frame seconds event occurs. The system transforms the period of detecting errored frame period events into the maximum number of 64-byte frames that a port can send in the specific period, that is, the system takes the maximum number of frames sent as the period.
Page 19: Standards And Protocols
The support of S5500-SI series Ethernet switches for information OAMPDUs carrying critical link events is as follows: S5500-SI series Ethernet switches are able to receive information OAMPDUs carrying the critical link events listed in Table 2-5. Only the Gigabit optical ports are able send information OAMPDUs carrying Link Fault events.
Page 20: Configuring Basic Ethernet Oam Functions
Configuring Basic Ethernet OAM Functions As for Ethernet OAM connection establishment, a device can operate in active mode or passive mode. After Ethernet OAM is enabled on an Ethernet port, according to its Ethernet OAM mode, the Ethernet port establishes an Ethernet OAM connection with its peer port. Follow these steps to configure basic Ethernet OAM functions: To do…...
Page 21: Configuring Errored Frame Event Detection
To do… Use the command… Remarks Optional Configure the errored symbol oam errored-symbol period event detection interval period-value 1 second by default Optional Configure the errored symbol oam errored-symbol threshold event triggering threshold threshold-value 1 by default Configuring Errored Frame Event Detection An errored frame event occurs when the number of detected error frames over a specific interval exceeds the predefined threshold.
Page 22: Enabling Oam Remote Loopback
Follow these steps to configure errored frame seconds event detection: To do… Use the command… Remarks Enter system view — system-view Configure the errored frame Optional oam errored-frame-seconds period seconds event detection period-value 60 second by default interval Configure the errored frame Optional oam errored-frame-seconds threshold seconds event triggering...
Page 23: Displaying And Maintaining Ethernet Oam Configuration
Ethernet OAM remote loopback is available only after the Ethernet OAM connection is established and can be performed only by the Ethernet OAM entities operating in active Ethernet OAM mode. Remote loopback is available only on full-duplex links that support remote loopback at both ends. Ethernet OAM Remote loopback needs the support of the peer hardware.
Page 24: Ethernet Oam Configuration Example
Ethernet OAM Configuration Example Network requirements Enable Ethernet OAM on Device A and Device B to auto-detect link errors between the two devices. Monitor the performance of the link between Device A and Device B by collecting statistics about the error frames received by Device A. Figure 2-2 Network diagram for Ethernet OAM configuration Configuration procedure Configure Device A...
Page 25 Errored-frame-seconds Event period(in seconds) Errored-frame-seconds Event threshold According to the above output information, the detection period of errored frame events is 20 seconds, the detection threshold is 10 seconds, and all the other parameters use the default values. You can use the display oam critical-event command to display the statistics of Ethernet OAM critical link events.
Page 26: Cfd Configuration
CFD Configuration When configuring CFD, go to these sections for information you are interested in: Overview CFD Configuration Task List Basic Configuration Tasks Configuring CC on MEPs Configuring LB on MEPs Configuring LT on MEPs Displaying and Maintaining CFD CFD Configuration Examples Overview Connectivity Fault Detection (CFD), which conforms to Connectivity Fault Management (CFM) defined by IEEE 802.1ag, is an end-to-end per-VLAN link layer Operations, Administration and Maintenance...
Page 27 Figure 3-1 Two nested MDs CFD exchanges messages and performs operations on a per-domain basis. By planning MDs properly in a network, you can use CFD to rapidly locate failure points. Maintenance association A maintenance association (MA) is a set of maintenance points (MPs) in an MD. An MA is identified by the “MD name + MA name”.
Page 28 As shown in Figure 3-2, an outward-facing MEP sends packets to its host port. Figure 3-3 Inward-facing MEP As shown in Figure 3-3, an inward-facing MEP does not send packets to its host port. Rather, it sends packets to other ports on the device. A MIP is internal to an MD.
Page 29: Basic Functions Of Cfd
Basic Functions of CFD CFD works effectively only in properly-configured networks. Its functions, which are implemented through the MPs, include: Continuity check (CC); Loopback (LB) Linktrace (LT) Continuity check Continuity check is responsible for checking the connectivity between MEPs. Connectivity faults are usually caused by device faults or configuration errors.
Page 30: Basic Configuration Tasks
Tasks Remarks Required Basic Configuration Tasks These configurations are the foundation for other configuration tasks. Required Configuring CC on MEPs Configuring the MEPs to send CCMs to manage link connectivity Optional Configuring LB on MEPs Checking link state by testing link connectivity Optional Configuring LT on MEPs Tracing link fault and finding the path between the source MEP and target...
Page 31: Configuring Mep
To do... Use the command... Remarks Enter system view system-view — Required Enable CFD cfd enable CFD is disabled by default. Required Create an MD cfd md md-name level level-value Not created by default Required cfd ma ma-name md md-name vlan Create an MA vlan-id Not created by default...
Page 32: Configuring Mip Generation Rules
Configuring MIP Generation Rules As functional entities in a service instance, MIPs respond to various CFD frames, such as LTM frames, LBM frames, 1DM frames, DMM frames, and TST frames. MIPs are generated on each port automatically according to related MIP generation rules. If a port has no MIP, the system will check the MAs in each MD (from low to high levels), and follow the procedure described in Figure 3-5...
Page 33: Configuring Cc On Meps
Any of the following actions or cases can cause MIPs to be created or deleted after you have configured the cfd mip-rule command: Enabling CFD (use the cfd enable command) Creating or deleting the MEPs on a port Changes occur to the VLAN attribute of a port The rule specified in the cfd mip-rule command changes Configuring CC on MEPs After the CC function is configured, MEPs can send CCMs mutually to check the connectivity between...
Page 34: Configuring Lb On Meps
Table 3-1 Relationship of the interval field value, the interval between CCM messages and the timeout time of the remote MEP The interval between CCM The timeout time of the remote The interval field value messages 1 second 3.5 seconds 10 second 35 seconds 60 seconds...
Page 35: Configuration Prerequisites
In the latter case, after LT messages automatic sending is enabled, if a MEP fails to receive the CCMs from the remote MEP within 3.5 sending intervals, the link between the two is regarded as faulty and LTMs will be sent out. Based on the LTRs that echo back, the fault source can be located.
Page 36: Cfd Configuration Examples
To do... Use the command... Remarks Display the attribute and running display cfd mep mep-id Available in any view information of the MEPs service-instance instance-id display cfd linktrace-reply Display LTR information received Available in any view [ service-instance instance-id by a MEP [ mep mep-id ] ] display cfd remote-mep Display the information of a remote...
Page 37: Configuring Mep And Enabling Cc On
Figure 3-6 Network diagram for MD configuration Configuration procedure Configuration on Device A (configuration on Device E is the same as that on Device A) <DeviceA> system-view [DeviceA] cfd enable [DeviceA] cfd md MD_A level 5 [DeviceA] cfd ma MA_MD_A md MD_A vlan 100 [DeviceA] cfd service-instance 1 md MD_A ma MA_MD_A Configuration on Device C <DeviceC>...
Page 38 Decide the remote MEP for each MEP, and enable these MEPs. According to the network diagram as shown in Figure 3-7, perform the following configurations: In MD_A, there are three edge ports: GigabitEthernet 1/0/1 on Device A, GigabitEthernet 1/0/3 on Device D and GigabitEthernet 1/0/4 on Device E.
Page 39: Configuring The Rules For Generating Mips
[DeviceD-GigabitEthernet1/0/3] cfd remote-mep 1001 service-instance 1 mep 4002 [DeviceD-GigabitEthernet1/0/3] cfd remote-mep 5001 service-instance 1 mep 4002 [DeviceD-GigabitEthernet1/0/3] cfd mep service-instance 1 mep 4002 enable [DeviceD-GigabitEthernet1/0/3] cfd cc service-instance 1 mep 4002 enable On Device E <DeviceE> system-view [DeviceE] interface gigabitethernet 1/0/4 [DeviceE-GigabitEthernet1/0/4] cfd mep 5001 service-instance 1 inbound [DeviceE-GigabitEthernet1/0/4] cfd remote-mep 1001 service-instance 1 mep 5001 [DeviceE-GigabitEthernet1/0/4] cfd remote-mep 4002 service-instance 1 mep 5001...
Page 40: Configuring Lb On Meps
Configuration procedure Configure Device B <DeviceB> system-view [DeviceB] cfd mip-rule explicit service-instance 1 Configure Device C <DeviceC> system-view [DeviceC] cfd mip-rule default service-instance 2 After the above operation, you can use the display cfd mp command to verify your configuration. Configuring LB on MEPs Network requirements Use the LB function to trace the fault source after CC detects a link fault.
Page 41: Dldp Configuration
DLDP Configuration This chapter includes these topics: Overview DLDP Configuration Task List Enabling DLDP Setting DLDP Mode Setting the Interval for Sending Advertisement Packets Setting the DelayDown Timer Setting the Port Shutdown Mode Configuring DLDP Authentication Resetting DLDP State Displaying and Maintaining DLDP DLDP Configuration Examples Troubleshooting DLDP Overview...
Page 42: How Dldp Works
Figure 4-1 Correct and incorrect fiber connections The Device link detection protocol (DLDP) is a technology for dealing with unidirectional links (fiber links or copper twisted-pair links) that may occur in a network. On detecting a unidirectional link, DLDP, as configured, can shut down the related port automatically or prompt users to take actions to avoid network problems.
Page 43 State Indicates… Active DLDP is enabled and the link is up, or the neighbor entries have been cleared. All neighbors are bi-directionally reachable or DLDP has been in active state for Advertisement more than five seconds. This is a relatively stable state where no unidirectional link has been detected.
Page 44 DLDP timer Description This timer is set to 10 seconds and is triggered when a device transits to the Probe state or an enhanced detect is launched. When the Echo timer expires and no Echo packet has been received from a neighbor device, the state of the link is Echo timer set to unidirectional and the device transits to the Disable state.
Page 45 neighbor. If no Echo packet is received from the neighbor when the Echo timer expires, the device transits to the Disable state. Table 4-3 DLDP mode and neighbor entry aging Detecting a neighbor Removing the neighbor Triggering the Enhanced DLDP mode after the corresponding entry immediately after the timer after an Entry timer...
Page 46 DLDP authentication mode You can prevent network attacks and illegal detect through DLDP authentication. Three DLDP authentication modes exist, as described below. Non-authentication. In this mode, the sending side sets the Authentication field and the Authentication type field of DLDP packets to 0. The receiving side checks the values of the two fields of received DLDP packets and drops the packets with the two fields conflicting with the corresponding local configuration.
Page 47 Table 4-5 Procedures for processing different types of DLDP packets received Packet type Processing procedure If the corresponding neighbor entry does not exist, creates the neighbor entry, triggers the Entry timer, and transits to Probe Advertisement Retrieves the state. packet with RSY tag neighbor information If the corresponding neighbor entry already exists, resets the Entry timer and transits to Probe state.
Page 48 Packet type Processing procedure packet local port is in Disable or If yes, returns RecoverEcho packets. Advertisement state If not, no process is performed. Checks whether the RecoverEcho If yes, the local port transits to Active state if the neighbor local port is in packet information the packet carries is consistent with the local port...
Page 49: Dldp Configuration Task List
DLDP neighbor state A DLDP neighbor can be in one of the three states described in Table 4-7. Table 4-7 Description on DLDP neighbor states DLDP neighbor state Description A neighbor is in this state when it is just detected and is being probed. A neighbor is Unknown in this state only when it is being probed.
Page 50: Enabling Dldp
Enabling DLDP To properly configure DLDP on the device, first enable DLDP globally, and then enable it on each port. Follow these steps to enable DLDP: To do… Use the command… Remarks Enter system view system-view — Required Enable DLDP globally dldp enable Globally disabled by default Enter Ethernet...
Page 51: Setting The Interval For Sending Advertisement Packets
Setting the Interval for Sending Advertisement Packets DLDP detects unidirectional links by sending Advertisement packets. To ensure that DLDP can detect unidirectional links in time without affecting network performance, set the advertisement interval appropriately depending on your network environment. Typically, the interval should be set shorter than one third of the STP convergence time.
Page 52: Setting The Port Shutdown Mode
Setting the Port Shutdown Mode On detecting a unidirectional link, the ports can be shut down in one of the following two modes. Manual mode. This mode applies to low performance networks, where normal links may be treated as unidirectional links. It protects data traffic transmission against false unidirectional links. In this mode, DLDP only detects unidirectional links and the DLDP state machine generates log and traps to prompt you to manually shut down unidirectional link ports with the shutdown command.
Page 53: Resetting Dldp State
To enable DLDP to operate properly, make sure the DLDP authentication modes and the passwords configured on the two ends of a link are the same. Resetting DLDP State After DLDP detects a unidirectional link on a port, the port enters Disable state. In this case, DLDP prompts you to shut down the port manually or shuts down the port automatically depending on the user-defined port shutdown mode.
Page 54: Displaying And Maintaining Dldp
To do… Use the command… Remarks Enter Ethernet port Either is required. interface interface-type Enter view interface-number Configurations made in Ethernet Ethernet port view apply to the current port port only; configurations performed in Enter port group port-group manual view/port port group view apply to all the ports view port-group-name...
Page 55 Figure 4-3 Network diagram for configuring automatic shutdown of unidirectional links Correct fiber connection Cross-connected fibers Device A Device A GE1/0/50 GE1/0/51 GE1/0/50 GE1/0/51 GE1/0/50 GE1/0/51 GE1/0/50 GE1/0/51 Device B Device B Ethernet Fiber link Tx end Rx end optical port Configuration procedure Configuration on Device A # Enable DLDP globally.
Page 56 # Enable DLDP globally, configure GigabitEthernet 1/0/50 and GigabitEthernet 1/0/50 to operate in full duplex mode, and then enable DLDP on the two ports. <DeviceB> system-view [DeviceB] dldp enable [DeviceB] interface gigabitethernet 1/0/50 [DeviceB-GigabitEthernet1/0/50] duplex full [DeviceB-GigabitEthernet1/0/50] speed 1000 [DeviceB-GigabitEthernet1/0/50] dldp enable [DeviceB-GigabitEthernet1/0/50] quit [DeviceB] interface gigabitethernet 1/0/51 [DeviceB-GigabitEthernet1/0/51] duplex full...
Page 57: Manually Shutting Down Unidirectional Links
The output indicates that both GigabitEthernet 1/0/50 and GigabitEthernet 1/0/51 are in Advertisement state, which means both links are bidirectional. # Enable system information monitoring on Device A, and enable the display of log and trap information. [DeviceA] quit <DeviceA> terminal monitor <DeviceA>...
Page 58 Make configuration so that DLDP, upon detecting a unidirectional link, reminds the network administrator to manually shut down the faulty port. Figure 4-4 Network diagram for configuring manual shutdown of unidirectional links Correct fiber connection Cross-connected fibers Device A Device A GE1/0/50 GE1/0/51 GE1/0/50...
Page 59 Configuration on Device B # Enable DLDP globally, configure GigabitEthernet 1/0/50 and GigabitEthernet 1/0/51 to operate in full duplex mode, and then enable DLDP on the two ports. <DeviceB> system-view [DeviceB] dldp enable [DeviceB] interface gigabitethernet 1/0/50 [DeviceB-GigabitEthernet1/0/50] duplex full [DeviceB-GigabitEthernet1/0/50] speed 1000 [DeviceB-GigabitEthernet1/0/50] dldp enable [DeviceB-GigabitEthernet1/0/50] quit...
Page 60 The output indicates that both GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50 are in Advertisement state, which means both links are bidirectional. # Enable system information monitoring on Device A, and enable the display of log and trap information. [DeviceA] quit <DeviceA> terminal monitor <DeviceA>...
Page 61: Troubleshooting Dldp
[DeviceA-GigabitEthernet1/0/50] %Jan 18 18:22:46:065 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/50 link status is UP. The output above indicates that the link status of both GigabitEthernet 1/0/50 and GigabitEthernet 1/0/51 is now up. Troubleshooting DLDP Symptom Two DLDP-enabled devices, Device A and Device B, are connected through two fiber pairs, in which two fibers are cross-connected.
Page 62: Rrpp Configuration
RRPP Configuration This chapter includes these sections: RRPP Overview RRPP Configuration Task List Creating an RRPP Domain Configuring Control VLANs Configuring Protected VLANs Configuring RRPP Rings Activating an RRPP Domain Configuring RRPP Timers Configuring an RRPP Ring Group Displaying and Maintaining RRPP RRPP Configuration Examples Troubleshooting RRPP Overview...
Page 63: Basic Concepts In Rrpp
Basic Concepts in RRPP Figure 5-1 RRPP networking diagram RRPP domain The interconnected devices with the same domain ID and control VLANs constitute an RRPP domain. An RRPP domain contains the following elements: primary ring, subring, control VLAN, master node, transit node, primary port, secondary port, common port, edge port, and so on. As shown in Figure 5-1, Domain 1 is an RRPP domain, including two RRPP rings: Ring 1 and...
Page 64 Data VLAN A data VLAN is a VLAN dedicated to transferring data packets. Both RRPP ports and non-RRPP ports can be assigned to a data VLAN. Node Each device on an RRPP ring is referred to as a node. The role of a node is configurable. There are the following node roles: Master node: Each ring has one and only one master node.
Page 65: Rrppdus
Common port and edge port The ports connecting the edge node and assistant-edge node to the primary ring are common ports. The ports connecting the edge node and assistant-edge node only to the subrings are edge ports. As shown in Figure 5-1, Device B and Device C lie on Ring 1 and Ring 2.
Page 66: Rrpp Timers
Type Description The assistant-edge node initiates Major-Fault packets to notify the edge Major-Fault node of SRPT failure when an SRPT between edge node and assistant-edge node is torn down. RRPPDUs of subrings are transmitted as data packets in the primary ring, while RRPPDUs of the primary ring can only be transmitted within the primary ring.
Page 67 If the ring is torn down, the secondary port of the master node will fail to receive Hello packets before the Fail timer expires. The master node will release the secondary port from blocking data VLANs while sending Common-Flush-FDB packets to instruct all transit nodes to update their own MAC entries and ARP/ND entries.
Page 68: Typical Rrpp Networking
RRPP ring group In an edge node RRPP ring group, only an activated subring with the lowest domain ID and ring ID can send Edge-Hello packets. In an assistant-edge node RRPP ring group, any activated subring that has received Edge-Hello packets will forward these packets to the other activated subrings.
Page 69 Figure 5-3 Schematic diagram for a tangent-ring network Intersecting rings As shown in Figure 5-4, there are two or more rings in the network topology and two common nodes between rings. In this case, you only need to define an RRPP domain, and configure one ring as the primary ring and the other rings as subrings.
Page 70 Figure 5-5 Schematic diagram for a dual-homed-ring network Single-ring load balancing In a single-ring network, you can achieve load balancing by configuring multiple domains. As shown in Figure 5-6, Ring 1 is configured as the primary ring of both Domain 1 and Domain 2.
Page 71: Protocols And Standards
Domain 2. With the configurations, you can enable traffic of different VLANs to travel over different paths in the subring and primary ring, thus achieving intersecting-ring load balancing. Figure 5-7 Schematic diagram for an intersecting-ring load balancing network Protocols and Standards RFC 3619 Extreme Networks' Ethernet Automatic Protection Switching (EAPS) Version 1 is related to RRPP.
Page 72: Creating An Rrpp Domain
Task Remarks Optional Configuring RRPP Timers Perform this task on the master node in the RRPP domain. Optional Configuring an RRPP Ring Group Perform this task on the edge node and assistant-edge node in the RRPP domain. RRPP does not have an auto election mechanism, so you must configure each node in the ring network properly for RRPP to monitor and protect the ring network.
Page 73: Configuring Protected Vlans
To do… Use the command… Remarks Specify the primary control control-vlan vlan-id Required VLAN for the RRPP domain To ensure proper forwarding of RRPPDUs, do not enable QinQ or VLAN mapping on the control VLANs. To ensure that RRPPDUs can be sent and received correctly, do not configure the default VLAN of a port accessing an RRPP ring as the primary control VLAN or the secondary control VLAN.
Page 74: Configuring Rrpp Rings
Configuring RRPP Rings When configuring an RRPP ring, you must make some configurations on the ports connecting each node to the RRPP ring before configuring the nodes. RRPP ports, that is, ports connecting devices to an RRPP ring, must be Layer-2 Ethernet ports, Layer-2 GE ports, Layer-2 XGE ports, or Layer-2 aggregate ports and cannot be member ports of any aggregation group, or smart link group.
Page 75: Configuring Rrpp Nodes
For more information about the port link-type trunk and port trunk permit vlan commands, see VLAN Configuration Commands in the Layer 2 - LAN Switching Command Reference. For more information about the undo stp enable command, see MSTP Configuration Commands in the Layer 2 - LAN Switching Command Reference. The 802.1p priority of trusted packets on the RRPP ports must be configured, so that RRPP packets take higher precedence than data packets when passing through the RRPP ports.
Page 76 To do… Use the command… Remarks ring ring-id node-mode master Specify the current device as [ primary-port interface-type the master node of the ring, and interface-number ] Required specify the primary port and the [ secondary-port interface-type secondary port interface-number ] level level-value Specifying a transit node Perform this configuration on a device to be configured as a transit node.
Page 77: Activating An Rrpp Domain
Specifying an assistant-edge node When configuring an assistant-edge node, you must first configure the primary ring before configuring the subrings. Perform this configuration on a device to be configured as an assistant-edge node. Follow these steps to specify an assistant-edge node: To do…...
Page 78: Configuring Rrpp Timers
To prevent Hello packets of subrings from being looped on the primary ring, enable the primary ring on its master node before enabling the subrings on their separate master nodes. On an edge node or assistant-edge node, enable/disable the primary ring and subrings separately as follows: Enable the primary ring of an RRPP domain before enabling the subrings of the RRPP domain.
Page 79: Displaying And Maintaining Rrpp
Perform this configuration on both the edge node and the assistant-edge node in an RRPP domain. Follow these steps to configure an RRPP ring group: To do… Use the command… Remarks Enter system view system-view — Create an RRPP ring group and rrpp ring-group ring-group-id Required enter RRPP ring group view...
Page 80: Rrpp Configuration Examples
To do… Use the command… Remarks reset rrpp statistics domain domain-id Available in user Clear RRPP statistics [ ring ring-id ] view RRPP Configuration Examples Single Ring Configuration Example Networking requirements Device A, Device B, Device C, and Device D constitute RRPP domain 1, specify the primary control VLAN of RRPP domain 1 as VLAN 4092, and RRPP domain 1 protects all VLANs;...
Page 81 [DeviceA-GigabitEthernet1/0/1] quit [DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] undo link-delay [DeviceA-GigabitEthernet1/0/2] undo stp enable [DeviceA-GigabitEthernet1/0/2] port link-type trunk [DeviceA-GigabitEthernet1/0/2] port trunk permit vlan all [DeviceA-GigabitEthernet1/0/2] qos trust dot1p [DeviceA-GigabitEthernet1/0/2] quit # Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure the VLANs mapped to MSTIs 0 through 16 as the protected VLANs of RRPP domain 1.
Page 82: Intersecting Ring Configuration Example
# Configure Device B as the transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port, and enable ring 1. [DeviceB-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0 [DeviceB-rrpp-domain1] ring 1 enable [DeviceB-rrpp-domain1] quit # Enable RRPP.
Page 83 Figure 5-9 Network diagram for intersecting rings configuration Configuration procedure Configuration on Device A # Disable physical state change suppression and STP on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2, configure the two ports as trunk ports, and assign them to all VLANs, and configure them to trust the 802.1p precedence of the received packets.
Page 84 [DeviceA] rrpp enable Configuration on Device B # Disable physical state change suppression and STP on GigabitEthernet 1/0/1, GigabitEthernet 1/0/2, and GigabitEthernet 1/0/3, configure the ports as trunk ports, and assign them to all VLANs, and configure them to trust the 802.1p precedence of the received packets. <DeviceB>...
Page 85 # Disable physical state change suppression and STP on GigabitEthernet 1/0/1, GigabitEthernet 1/0/2, and GigabitEthernet 1/0/3, configure the ports as trunk ports, and assign them to all VLANs, and configure them to trust the 802.1p precedence of the received packets. <DeviceC>...
Page 86 [DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] undo link-delay [DeviceD-GigabitEthernet1/0/1] undo stp enable [DeviceD-GigabitEthernet1/0/1] port link-type trunk [DeviceD-GigabitEthernet1/0/1] port trunk permit vlan all [DeviceD-GigabitEthernet1/0/1] qos trust dot1p [DeviceD-GigabitEthernet1/0/1] quit [DeviceD] interface gigabitethernet 1/0/2 [DeviceD-GigabitEthernet1/0/2] undo link-delay [DeviceD-GigabitEthernet1/0/2] undo stp enable [DeviceD-GigabitEthernet1/0/2] port link-type trunk [DeviceD-GigabitEthernet1/0/2] port trunk permit vlan all [DeviceD-GigabitEthernet1/0/2] qos trust dot1p [DeviceD-GigabitEthernet1/0/2] quit...
Page 87: Intersecting-Ring Load Balancing Configuration Example
# Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure VLANs mapped to MSTIs 0 through 16 as the protected VLANs of RRPP domain [DeviceE] rrpp domain 1 [DeviceE-rrpp-domain1] control-vlan 4092 [DeviceE-rrpp-domain1] protected-vlan reference-instance 0 to 16 # Configure Device E as the master node of subring 2, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port, and enable ring 2.
Page 88 Figure 5-10 Network diagram for intersecting-ring load balancing configuration Configuration procedure Configuration on Device A # Create VLANs 10 and 20, map VLAN 10 to MSTI 1 and VLAN 20 to MSTI 2, and activate MST region configuration. <DeviceA> system-view [DeviceA] vlan 10 [DeviceA-vlan10] quit [DeviceA] vlan 20...
Page 89 [DeviceA-GigabitEthernet1/0/2] qos trust dot1p [DeviceA-GigabitEthernet1/0/2] quit # Create RRPP domain 1, configure VLAN 100 as the primary control VLAN of RRPP domain 1, and configure the VLAN mapped to MSTI 1 as the protected VLAN of RRPP domain 1. [DeviceA] rrpp domain 1 [DeviceA-rrpp-domain1] control-vlan 100 [DeviceA-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device A as the master node of primary ring 1, with GigabitEthernet 1/0/1 as the...
Page 90 [DeviceB-GigabitEthernet1/0/1] quit [DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] undo link-delay [DeviceB-GigabitEthernet1/0/2] undo stp enable [DeviceB-GigabitEthernet1/0/2] port link-type trunk [DeviceB-GigabitEthernet1/0/2] port trunk permit vlan 10 20 [DeviceB-GigabitEthernet1/0/2] qos trust dot1p [DeviceB-GigabitEthernet1/0/2] quit # Disable physical state change suppression and STP on GigabitEthernet 1/0/3, configure the port as a trunk port, and assign it to VLAN 20, and configure it to trust the 802.1p precedence of the received packets.
Page 91 [DeviceB-rrpp-domain2] protected-vlan reference-instance 2 # Configure Device B as the transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port, and enable ring 1. [DeviceB-rrpp-domain2] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0 [DeviceB-rrpp-domain2] ring 1 enable # Configure Device B as the assistant-edge node of subring 2 in RRPP domain 2, with...
Page 92 [DeviceC-GigabitEthernet1/0/3] undo stp enable [DeviceC-GigabitEthernet1/0/3] port link-type trunk [DeviceC-GigabitEthernet1/0/3] port trunk permit vlan 20 [DeviceC-GigabitEthernet1/0/3] qos trust dot1p [DeviceC-GigabitEthernet1/0/3] quit # Disable physical state change suppression and STP on GigabitEthernet 1/0/4, configure the port as a trunk port, and assign it to VLAN 10, and configure it to trust the 802.1p precedence of the received packets.
Page 93 [DeviceC] rrpp enable Configuration on Device D # Create VLANs 10 and 20, map VLAN 10 to MSTI 1 and VLAN 20 to MSTI 2, and activate MST region configuration. <DeviceD> system-view [DeviceD] vlan 10 [DeviceD-vlan10] quit [DeviceD] vlan 20 [DeviceD-vlan20] quit [DeviceD] stp region-configuration [DeviceD-mst-region] instance 1 vlan 10...
Page 94 # Configure Device D as the transit node of primary ring 1 in RRPP domain 2, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port, and enable ring 1. [DeviceD-rrpp-domain2] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0 [DeviceD-rrpp-domain2] ring 1 enable [DeviceD-rrpp-domain2] quit...
Page 95 Configuration on Device F # Create VLAN 10, map VLAN 10 to MSTI 1, and activate MST region configuration. <DeviceF> system-view [DeviceF] vlan 10 [DeviceF-vlan10] quit [DeviceF] stp region-configuration [DeviceF-mst-region] instance 1 vlan 10 [DeviceF-mst-region] active region-configuration [DeviceF-mst-region] quit # Disable physical state change suppression and STP on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2, configure the two ports as trunk ports, and assign them to VLAN 10, and configure them to trust the 802.1p precedence of the received packets.
Page 96: Troubleshooting
[DeviceC-rrpp-ring-group1] domain 1 ring 3 Verification After the configuration, you can use the display command to view RRPP configuration and operational information on each device. Troubleshooting Symptom: When the link state is normal, the master node cannot receive Hello packets, and the master node unblocks the secondary port.
Page 97: Smart Link Configuration
Smart Link Configuration This chapter includes these sections: Smart Link Overview Configuring a Smart Link Device Configuring an Associated Device Displaying and Maintaining Smart Link Smart Link Configuration Examples Smart Link Overview Background To avoid single-point failures and guarantee network reliability, downstream devices are usually dual uplinked to upstream devices.
Page 98: Terminology
suitable for users who have high demand on convergence speed. RRPP can meet users’ demand on convergence speed, but it involves complicated networking and configurations and therefore is mainly used in ring-shaped networks. For more information about STP, see MSTP Configuration in the Layer 2 - LAN Switching Configuration Guide.
Page 99: How Smart Link Works
Transmit control VLAN The transmit control VLAN is used for transmitting flush messages. When link switchover occurs, the devices (such as Device C and Device D in Figure 6-1) broadcast flush messages within the transmit control VLAN. Receive control VLAN The receive control VLAN is used for receiving and processing flush messages.
Page 100: Smart Link Collaboration Mechanisms
Role preemption mechanism As shown in Figure 6-1, the link on Port1 of Device C is the master link, and the link on Port2 of Device C is the slave link. Once the master link fails, Port1 is automatically blocked and placed in the standby state, while Port2 takes over to forward traffic.
Page 101: Configuring A Smart Link Device
A smart link device is a device that supports Smart Link and is configured with a smart link group and a transmit control VLAN for flush message transmission. Device C and Device D in Figure are two examples of smart link devices. An associated device is a device that supports Smart Link, and receives flush messages sent from the specified control VLAN.
Page 102: Configuring Member Ports For A Smart Link Group
The protected-vlan command configures protected VLANs for a smart link group by referencing MSTIs. To view VLAN-to-MSTI mappings, use the display stp region-configuration command. For more information about VLAN-to-MSTI mapping configuration, see MSTP Configuration in the Layer 2 - LAN Switching Configuration Guide. Configuring Member Ports for a Smart Link Group You can configure member ports for a smart link group either in smart link group view or in port view.
Page 103: Enabling The Sending Of Flush Messages
To do… Use the command… Remarks Create a smart link group and enter smart-link group group-id — smart link group view Required Enable role preemption preemption mode role Disabled by default Optional Configure the preemption delay preemption delay delay-time 1 second by default The preemption delay configuration takes effect only after role preemption is enabled.
Page 104: Configuring An Associated Device
Configuring an Associated Device Enabling the Receiving of Flush Messages You do not need to enable all ports on the associated devices to receive flush messages sent from the transmit control VLAN, only those on the master and slave links between the smart link device and the destination device.
Page 105: Smart Link Configuration Examples
Smart Link Configuration Examples Single Smart Link Group Configuration Example Network requirements As shown in Figure 6-2: Device C and Device D are smart link devices, and Device A, Device B, and Device E are associated devices. Traffic of VLANs 1 through 30 on Device C and Device D are dually uplinked to Device A.
Page 106 [DeviceC-GigabitEthernet1/0/2] quit # Create smart link group 1, and configure all VLANs mapped to MSTI 1 as the protected VLANs. [DeviceC] smart-link group 1 [DeviceC-smlk-group1] protected-vlan reference-instance 1 # Configure GigabitEthernet 1/0/1 as the master port and GigabitEthernet 1/0/2 as the slave port for smart link group 1.
Page 107 # Configure GigabitEthernet 1/0/1, GigabitEthernet 1/0/2, and GigabitEthernet 1/0/3 as trunk ports that permit VLANs 1 through 30 and enable flush message receiving on them. [DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] port link-type trunk [DeviceB-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/1] smart-link flush enable [DeviceB-GigabitEthernet1/0/1] quit [DeviceB] interface gigabitethernet 1/0/2...
Page 108: Multiple Smart Link Groups Load Sharing Configuration Example
[DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] port link-type trunk [DeviceA-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/2] smart-link flush enable [DeviceA-GigabitEthernet1/0/2] quit Verifying the configurations You can use the display smart-link group command to display the smart link group configuration on each device.
Page 109 Figure 6-3 Network diagram for multiple smart link groups load sharing configuration Configuration procedure Configuration on Device C # Create VLAN 1 through VLAN 200, map VLANs 1 through 100 to MSTI 1, and VLANs 101 through 200 to MSTI 2, and activate MST region configuration. <DeviceC>...
Page 110 [DeviceC-smlk-group-1] flush enable control-vlan 10 [DeviceC-smlk-group-1] quit # Create smart link group 2, and configure all VLANs mapped to MSTI 2 as the protected VLANs for smart link group 2. [DeviceC] smart-link group 2 [DeviceC-smlk-group2] protected-vlan reference-instance 2 # Configure GigabitEthernet 1/0/1 as the slave port and GigabitEthernet 1/0/2 as the master port for smart link group 2.
Page 111 [DeviceD-GigabitEthernet1/0/2] quit Configuration on Device A # Create VLAN 1 through VLAN 200. <DeviceA> system-view [DeviceA] vlan 1 to 200 # Configure GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 as trunk ports and assign them to VLANs 1 through 200; enable flush message receiving on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 and configure VLAN 10 and VLAN 101 as the receive control VLANs.
Page 112 Received flush packets Receiving interface of the last flush packet : GigabitEthernet1/0/2 Receiving time of the last flush packet : 16:25:21 2009/02/21 Device ID of the last flush packet : 000f-e23d-5af0 Control VLAN of the last flush packet : 10 6-51...
Page 113: Monitor Link Configuration
Monitor Link Configuration This chapter includes these sections: Overview Configuring Monitor Link Displaying and Maintaining Monitor Link Monitor Link Configuration Example Overview Monitor Link is a port collaboration function. Monitor Link usually works together with Layer 2 topology protocols. The idea is to monitor the states of uplink ports and adapt the up/down state of downlink ports to the up/down state of uplink ports, triggering link switchover on the downstream device in time, as shown in Figure...
Page 114: How Monitor Link Works
Uplink/Downlink ports Uplink port and downlink port are two port roles in monitor link groups: Uplink ports refer to the monitored ports. The state of a monitor link group adapts to that of its member uplink ports. When a monitor link group contains no uplink port or all the uplink ports are down, the monitor link group becomes down;...
Page 115: Configuring Monitor Link Group Member Ports
Configuring Monitor Link Group Member Ports You can configure member ports for a monitor link group either in monitor link group view or port view. The configurations made in these two views lead to the same result. In monitor link group view Follow these steps to configure member ports for a monitor link group in monitor link group view: To do…...
Page 116: Monitor Link Configuration Example
Monitor Link Configuration Example Network requirements As shown in Figure 7-2: Device C is a smart link device, and Device A, Device B, and Device D are associated devices. Traffic of VLANs 1 through 30 on Device C is dual-uplinked to Device A through a smart link group.
Page 117 [DeviceC-GigabitEthernet1/0/1] quit [DeviceC] interface gigabitethernet 1/0/2 [DeviceC-GigabitEthernet1/0/2] undo stp enable [DeviceC-GigabitEthernet1/0/2] port link-type trunk [DeviceC-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/2] quit # Create smart link group 1, and configure all the VLANs mapped to MSTI 1 as the protected VLANs for smart link group 1.
Page 118 [DeviceB-GigabitEthernet1/0/2] quit # Create monitor link group 1, and then configure GigabitEthernet 1/0/1 as an uplink port and GigabitEthernet 1/0/2 as a downlink port for monitor link group 1. [DeviceB] monitor-link group 1 [DeviceB-mtlk-group1] port gigabitethernet 1/0/1 uplink [DeviceB-mtlk-group1] port gigabitethernet 1/0/2 downlink [DeviceB-mtlk-group1] quit Configuration on Device D # Create VLANs 1 through 30.
Page 119 Member Role Status ------------------------------------------ GigabitEthernet1/0/1 UPLINK DOWN GigabitEthernet1/0/2 DOWNLINK DOWN...
Page 120: Track Configuration
Track Configuration This chapter includes these sections: Track Overview Track Configuration Task List Configuring Collaboration Between the Track Module and the Detection Modules Configuring Collaboration Between the Track Module and the Application Modules Displaying and Maintaining Track Object(s) Track Configuration Examples Track Overview Figure 8-1 Collaboration through the Track module Application modules...
Page 121: Collaboration Between The Track Module And The Application Modules
If the probe fails, the status of the corresponding Track object is Negative. If the probe result is invalid (for example, the NQA test group collaborating with the track entry does not exist.), the status of the track entry is Invalid. At present, the detection modules that can collaborate with the Track module is the Network Quality Analyzer (NQA).
Page 122: Configuring Collaboration Between The Track Module And The Application Modules
To do… Use the command… Remarks Required Create a track entry, associate it track track-entry-number nqa with the specified NQA reaction entry admin-name operation-tag No track entry is created by entry reaction item-number default. You can configure a track entry before creating an NQA test group and its reaction entry. In this case, the status of the configured track entry is Invalid.
Page 123 To do… Use the command… Remarks ip route-static dest-address Configure the track-static routing { mask | mask-length } Required collaboration, so as to check the next-hop-address track reachability of the next hop of the track-entry-number [ preference Not configured by default. static route preference-value ] [ tag tag-value ] [ description description-text ]...
Page 124 The static route with Switch B as the next hop has a higher priority, and is the master route. If this route is available, Switch A forwards packets to 30.1.1.0/24 through Switch B. The static route with Switch C as the next hop acts as the backup route. Configure static routing-track-NQA collaboration to determine whether the master route is available in real time.
Page 125 [SwitchA] nqa entry admin test # Configure the test type as ICMP-echo. [SwitchA-nqa-admin-test] type icmp-echo # Configure the destination address of the test as 10.2.1.4 and the next hop address as 10.1.1.2 to check the connectivity of the path from Switch A to Switch B, and then to Switch D through NQA. [SwitchA-nqa-admin-test-icmp-echo] destination ip 10.2.1.4 [SwitchA-nqa-admin-test-icmp-echo] next-hop 10.1.1.2 # Configure the test frequency as 100 ms.
Page 126 # Configure the destination address of the test as 10.1.1.1 and the next hop address as 10.2.1.2 to check the connectivity of the path from Switch D to Switch B, and then to Switch A through NQA. [SwitchD-nqa-admin-test-icmp-echo] destination ip 10.1.1.1 [SwitchD-nqa-admin-test-icmp-echo] next-hop 10.2.1.2 # Configure the test frequency as 100 ms.
Page 127 Track ID: 1 Status: Negative Notification delay: Positive 0, Negative 0 (in seconds) Reference object: NQA entry: admin test Reaction: 1 # Display the routing table of Switch A. [SwitchA] display ip routing-table Routing Tables: Public Destinations : 10 Routes : 10 Destination/Mask Proto Pre Cost NextHop...
Page 128 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/1/2 ms...
Page 129 Index Configuring RRPP Nodes 5-14 Configuring RRPP Ports 5-13 Automatically Shutting Down Unidirectional Configuring the Rules for Generating MIPs Links 4-14 3-14 Configuring Track-NQA Collaboration Basic Concepts in CFD Configuring Track-Static Routing Basic Concepts in RRPP Collaboration Basic Functions of CFD Creating a Monitor Link Group Collaboration Between the Track Module and Enabling Automatic LT Messages Sending...
Page 130 Manually Shutting Down Unidirectional Links 4-17 Multiple Smart Link Groups Load Sharing Configuration Example 6-47 Protection Switchover Technologies RRPP Timers RRPPDUs Single Ring Configuration Example 5-19 Single Smart Link Group Configuration Example 6-44 Smart Link Collaboration Mechanisms 6-39 Standards and Protocols Typical RRPP Networking...

H3C S5500-SI Series Configuration Manual

1 High Availability Overview

2 Ethernet OAM Configuration

3 CFD Configuration

4 DLDP Configuration

5 RRPP Configuration

6 Smart Link Configuration

7 Monitor Link Configuration

8 Track Configuration

Quick Links

Troubleshooting

Related Manuals for H3C S5500-SI Series

Summary of Contents for H3C S5500-SI Series

Table of Contents