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.
The H3C S9500E documentation set includes 13 configuration guides, which describe the software features for the H3C S9500E Series Routing 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.
Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional.
Page 5
Network topology icons Convention Description Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.
Provides a complete guide to hardware installation Installation guide and hardware specifications. Card manuals Provide the hardware specifications of cards. Cabinet Installation and Guides you through installing and remodeling H3C Hardware specifications Remodel Introduction cabinets. and installation H3C Pluggable SFP...
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 & Documents > Technical Documents] –...
Table of Contents Preface ·········································································································································································· 3 Audience ············································································································································································ 3 Conventions ······································································································································································· 4 About the H3C S9500E Documentation Set ·················································································································· 6 High availability overview ········································································································································· 13 Availability requirements ··············································································································································· 13 Availability evaluation ··················································································································································· 13 High availability technologies ······································································································································ 14 Fault detection technologies ································································································································· 14 Protection switchover technologies ······················································································································...
Page 9
Setting the DelayDown timer ········································································································································ 40 Setting the port shutdown mode ··································································································································· 41 Configuring DLDP authentication ·································································································································· 41 Resetting DLDP state ······················································································································································· 42 Resetting DLDP state in system view ···················································································································· 42 Resetting DLDP state in port view/port group view ··························································································· 42 Displaying and maintaining DLDP ································································································································...
Page 10
Configuration prerequisites ·································································································································· 92 Configuring protected VLANs for a Smart Link group ······················································································· 92 Configuring member ports for a Smart Link group ···························································································· 93 Configuring role preemption for a Smart Link group ························································································ 93 Enabling the sending of flush messages ············································································································· 94 Smart Link switch configuration example ············································································································...
Page 11
Enabling the trap function of VRRP ···················································································································· 126 Displaying and maintaining VRRP for IPv4 ······································································································· 126 Configuring VRRP for IPv6 ··········································································································································· 127 Configuring the association between virtual IPv6 address and MAC address ············································ 127 Creating VRRP group and configuring virtual IPv6 address ··········································································· 128 Configuring router priority, preemptive mode and tracking function ····························································...
Page 12
Configuring collaboration between the track module and the interface management module ···························· 181 Configuring collaboration between the track module and the application modules ············································ 181 Configuring track-VRRP collaboration ··············································································································· 181 Configuring track-static routing collaboration ·································································································· 183 Configuring track-policy routing collaboration ································································································ 184 Displaying and maintaining track entries ··················································································································...
High availability overview Communication interruptions can seriously affect widely-deployed value-added services such as IPTV and video conference. Therefore, the basic network infrastructures must be able to provide high availability. There are three effective ways to improve availability: • Increasing fault tolerance •...
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.
Technology Introduction Reference Network NQA analyzes network performance, services and service quality by Management and sending test packets, and provides you with network performance and Monitoring service quality parameters such as jitter, TCP connection delay, FTP Configuration connection delay and file transfer rate. Guide/NQA Configuration Monitor link is a port collaboration function.
Page 16
Technology Introduction Reference Smart Link is a feature developed to address the slow convergence High Availability issue with STP. It provides link redundancy as well as fast Configuration Smart Link convergence in a dual uplink network, allowing the backup link to Guide/Smart Link take over quickly when the primary link fails.
Active and standby switchover configuration The switch operates in IRF or standalone (the default) mode. For more information about the IRF mode, • see IRF in the IRF Configuration Guide. When the device works in standalone mode, you can use the features and functions in this manual to •...
When the device operates normally, do not disconnect the AMB. Perform an active and standby • switchover first, and disconnect it when it is no longer acting as the AMB. You cannot execute any command on the SMB. Instead, you perform configurations at the command •...
Manually configuring active and standby switchover The original AMB is restarted when an AMB and SMB switchover is performed. Therefore, check the consistency of the software version of the AMB and SMB before performing AMB and SMB switchover. If their software versions are not consistent, configure to ignore version check of the SMB first. To upgrade the AMB, restart the AMB.
Ethernet OAM configuration Ethernet OAM overview Ethernet OAM is a tool that monitors Layer-2 link status by sending OAMDPUs between switches. Currently, Ethernet OAM is mainly used to address common link-related issues on the “last mile.” You can enable Ethernet OAM on two switches connected by a point-to-point connection, to monitor the status of the link.
Field Description Destination MAC address of the Ethernet OAMPDU. Dest addr It is a slow protocol multicast address 0180c2000002. Bridges cannot forward slow protocol packets, so Ethernet OAMPDUs cannot be forwarded. Source MAC address of the Ethernet OAMPDU. Source addr It is the bridge MAC address of the sending side and is a unicast MAC address.
Page 22
For Ethernet OAM connection establishment, switches can operate in active Ethernet OAM mode or passive Ethernet OAM mode, but a switch’s role will be somewhat different depending on mode. For example, only a switch in active mode can initiate OAM Discovery. Table 6 compares active and passive Ethernet OAM modes.
Page 23
The interval to send Information OAMPDUs is determined by a timer. Up to ten Information OAMPDUs can be sent in a second. Link monitoring Error detection in an Ethernet is difficult, especially when the physical connection in the network is not disconnected but network performance is degrading gradually.
Table 8 Critical link events OAMPDU transmission Ethernet OAM link events Description frequencies Link fault Peer link signal is lost. Once per second A power failure or other Dying gasp Non-stop unexpected error occurred. An undetermined critical event Critical event Non-stop occurred.
Configuring link monitoring After Ethernet OAM connections are established, the link monitoring periods and thresholds configured in this section take effect on all Ethernet ports automatically. Configuring errored symbol event detection An errored symbol event occurs when the number of detected symbol errors during a specified detection interval exceeds the predefined threshold.
Configuring errored frame period event detection An errored frame period event occurs if the number of frame errors received in a specified period (the period is specified as a number of received frames) exceeds the predefined threshold. To configure errored frame period event detection: To do…...
To do… Use the command… Remarks Enter system view system-view — interface interface-type interface- Enter Ethernet port view — number Required Enable Ethernet OAM remote oam loopback loopback Disabled by default. Ethernet OAM remote loopback is available only after the Ethernet OAM connection is established, and •...
To do… Use the command… Remarks display oam { local | remote } [ Display the information about an Ethernet interface interface-type interface- OAM connection number ] reset oam [ interface interface- Clear statistics on Ethernet OAM packets Available in user view and Ethernet OAM link error events type interface-number ] only...
Page 29
[SwitchA] oam errored-frame threshold 10 Configure Switch B Configure GigabitEthernet 4/0/1 to operate in active Ethernet OAM mode (the default) and enable Ethernet OAM for it. <SwitchB> system-view [SwitchB] interface gigabitethernet 4/0/1 [SwitchB-GigabitEthernet4/0/1] oam mode active [SwitchB-GigabitEthernet4/0/1] oam enable [SwitchB-GigabitEthernet4/0/1] quit Verify the configuration Display the global Ethernet OAM configuration information on Switch A.
Page 30
--------------------------------------------------------------------- Event Time Stamp : 5789 Errored FrameWindow : 10(100ms) Errored Frame Threshold Errored Frame Error Running Total : 35 Event Running Total : 17 The above information indicates that 35 errors occurred since Ethernet OAM is enabled on Switch A, 17 of which are caused by error frames. The link is instable.
DLDP configuration Overview Background Unidirectional links occur when one end of a link can receive packets from the other end, but the other end cannot receive packets sent by the first end. Unidirectional links result in problems such as loops in an STP-enabled network. Two kinds of unidirectional fiber links exist.
Figure 4 Unidirectional fiber link: fiber either not connected, or disconnected Device A GE2/0/1 GE2/0/2 GE2/0/1 GE2/0/2 Device B DLDP can detect the link status of twisted pair or fiber cable. On detecting a unidirectional link, DLDP can shut down the related port automatically or prompt users to take measures as configured to avoid network problems.
Page 33
State Indicates… DLDP enters this state if it receives a packet from an unknown neighbor. In this state, DLDP sends packets to check whether the link is unidirectional. As soon as DLDP Probe transits to this state, a probe timer starts and an echo timeout timer starts for each neighbor being probed.
Page 34
DLDP timer Description In the enhanced mode, this timer is triggered if no packet is received from a neighbor when the entry aging timer expires. Enhanced timer is set to 1 second. Enhanced timer After the Enhanced timer is triggered, the switch sends up to eight probe packets to the neighbor at a frequency of one packet per second.
Page 35
Figure 5 A situation for Enhanced DLDP mode In normal DLDP mode, only fiber cross-connected unidirectional links (as shown in Figure 3 ) can be • detected. In enhanced DLDP mode, two types of unidirectional links can be detected. One is fiber cross-connected •...
Page 36
DLDP state Type of DLDP packets sent Active Advertisement packet with RSY tag Advertisement Normal Advertisement packet Probe Probe packet Disable Disable packet and RecoverProbe packet When a switch transits from a DLDP state other than Inactive state or Disable state to Initial state, it sends Flush packets.
Page 37
Packet type Processing procedure If the corresponding neighbor entry does not exist, creates the neighbor entry, triggers the Entry timer, and transits to Probe state. If the neighbor information it carries conflicts with the corresponding locally maintained Retrieves the neighbor entry, drops the packet. Echo packet neighbor corresponding...
On a DLDP down port, DLDP monitors the unidirectional link. Once DLDP finds out that the state of the link has been restored to bidirectional, it brings up the port. The specific process is as follows: The DLDP down port sends out a RecoverProbe packet, which carries only information about the local port, every two seconds.
DLDP does not process any link aggregation control protocol (LACP) events. The links in an aggregation • group are treated individually in DLDP. When connecting two DLDP-enabled switches, make sure the DLDP software version ID fields of the DLDP • packets exchanged between the two switches are the same.
If the interval is too short, unnecessary Advertisement packets can be generated, which consumes bandwidth. Therefore, H3C recommends using the default value. To enable DLDP to operate properly, make sure the intervals for sending Advertisement packets on both •...
The DelayDown timer setting applies to all DLDP-enabled ports. 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 networks with low performance, where normal links may be treated as unidirectional links.
To do… Use the command… Remarks dldp authentication-mode { Required Configure DLDP md5 md5-password | none | authentication none by default simple simple-password } To enable DLDP to operate properly, make sure the DLDP authentication modes and the passwords of both sides of a link are the same.
To do… Use the command… Remarks Enter system view system-view — Either is required. interface interface-type Enter Ethernet Configurations made in Ethernet Enter Ethernet port view interface-number port view apply to the current port port view/port only; configurations performed in group view port-group manual port- Enter port...
Page 44
Figure 6 Network diagram for DLDP configuration Device A GE2/0/1 GE2/0/2 GE2/0/1 GE2/0/2 Device B Configuration procedure Configuration on Device A Enable DLDP on GigabitEthernet2/0/1 and GigabitEthernet 2/0/2 separately. <DeviceA> system-view [DeviceA] interface gigabitethernet 2/0/1 [DeviceA-GigabitEthernet2/0/1] dldp enable [DeviceA-GigabitEthernet2/0/1] quit [DeviceA] interface gigabitethernet 2/0/2 [DeviceA-GigabitEthernet2/0/2] dldp enable [DeviceA-GigabitEthernet2/0/2] quit...
Page 45
You can use the display dldp command to display the DLDP configuration information on ports. Display the DLDP configuration information on all the DLDP-enabled ports of Device A. [DeviceA] display dldp DLDP global status : enable DLDP interval : 6s DLDP work-mode : enhance DLDP authentication-mode : none DLDP unidirectional-shutdown : auto...
Neighbor state : two way Neighbor aged time : 11 Interface GigabitEthernet2/0/2 DLDP port state : advertisement DLDP link state : up The neighbor number of the port is 1. Neighbor mac address : 0000-0000-0102 Neighbor port index : 59 Neighbor state : two way Neighbor aged time : 11 The output information indicates that both GigabitEthernet2/0/1 and GigabitEthernet2/0/2 are...
RRPP configuration RRPP overview RRPP is a link layer protocol designed for Ethernet rings. RRPP can prevent broadcast storms caused by data loops when an Ethernet ring is healthy, and rapidly restore the communication paths between the nodes in the event that a link is disconnected on the ring. RRPP features fast topology convergence.
Page 48
RRPP domain Interconnected switches 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, and edge port. As shown in Figure 7, Domain 1 is an RRPP domain, including two RRPP rings: Ring 1 and Ring 2.
Page 49
• Transit node: Transit nodes include all nodes except the master node on the primary ring and all nodes on subrings except the master nodes and the nodes where the primary ring intersects with the subrings. A transit node monitors the state of its directly-connected RRPP links and notifies the master node of the link state changes, if any.
RRPP ring group To reduce Edge-Hello traffic, you can configure a group of subrings on the edge node or assistant-edge node. For information about Edge-Hello packets, see RRPPDUs. You must configure a switch as the edge node of these subrings, and another switch as the assistant-edge node of these subrings.
RRPP timers When RRPP checks the link state of an Ethernet ring, the master node sends Hello packets out the primary port according to the Hello timer and determines whether its secondary port receives the Hello packets based on the Fail timer. •...
Page 52
• 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 53
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.
Typical RRPP networking The following networking applications are typical. Single ring As shown in Figure 8, there is only a single ring in the network topology. In this case, you only need to define an RRPP domain. Figure 8 Schematic diagram for a single-ring network Domain 1 Device A Device B...
Page 55
Intersecting rings As shown in Figure 10, 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. Figure 10 Schematic diagram for an intersecting-ring network Domain 1...
Page 56
Single-ring load balancing In a single-ring network, you can achieve load balancing by configuring multiple domains. As shown in Figure 12, Ring 1 is configured as the primary ring of both Domain 1 and Domain 2. Domain 1 and Domain 2 are configured with different protected VLANs. In Domain 1, Device A is configured as the master node of Ring 1;...
Figure 13 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. RRPP configuration task list You can create RRPP domains based on service planning, specify control VLANs and data VLANs for each RRPP domain, and then determine the ring roles and node roles based on the traffic paths in each RRPP domain.
Task Remarks Optional Configuring RRPP timers Perform this task on the master node in the RRPP domain. Optional Enabling fast Perform this task on the master node, edge node, and detection Configuring RRPP fast assistant-edge node in the RRPP domain. detection Optional Configuring fast...
To do… Use the command… Remarks Enter system view system-view — Enter RRPP domain view rrpp domain domain-id — 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. •...
Do not enable OAM remote loopback function on an RRPP port. Otherwise, this may cause a temporary • broadcast storm. H3C recommends using the link-delay command to enable link status rapid report function on an • RRPP port by setting the link-delay of the port to 0, to accelerate topology convergence. For more information about the link-delay command, see Ethernet Interface in the Interface Command Reference.
Configuring RRPP nodes The maximum number of rings that can be configured on a switch in all RRPP domains is 16 total. • If a switch carries multiple RRPP rings in an RRPP domain, only one ring can be configured as the •...
To specify an edge node: To do… Use the command… Remarks Enter system view system-view — Enter RRPP domain view rrpp domain domain-id — Specify the current switch as a ring ring-id node-mode transit [ transit node of the primary primary-port interface-type interface- Required ring, and specify the primary...
To do… Use the command… Remarks Required Enable RRPP rrpp enable Disabled by default Enter RRPP domain view rrpp domain domain-id — Required Enable the specified RRPP ring ring ring-id enable Disabled by default When enabling or disabling the primary ring and subrings on an edge node or assistant-edge node, follow these guidelines: Enable the primary ring of an RRPP domain before enabling subrings of the RRPP domain.
To configure fast detection on the master node of a subring, make sure that the edge node and assistant- • edge node of the subring support fast detection. Otherwise, H3C does not recommend that you configure fast detection on the master node of the subring.
The value of the Fast-Fail timer must be equal to or greater than three times the Fast-Hello timer. • In a dual-homed-ring network, to avoid temporary loops when the primary ring fails, ensure that the Fast- • Fail timer value is equal to or greater than six times the timer resolution, and the difference between the Fast-Fail timer value on the master node of the subring and that on the master node of the primary ring is greater than twice the Fast-Hello timer value of the master node of the subring.
Displaying and maintaining RRPP To do… Use the command… Remarks Display brief information about display rrpp brief RRPP configuration Display RRPP group configuration display rrpp ring-group [ ring-group-id ] information Available in any view display rrpp verbose domain domain- Display detailed information about RRPP configuration id [ ring ring-id ] display rrpp statistics domain domain-...
Page 67
Figure 14 Network diagram for single ring configuration Domain 1 Device A GE3/0/1 Device B GE3/0/1 Transit node GE3/0/2 GE3/0/2 Master node Ring 1 Transit node Transit node GE3/0/1 GE3/0/2 GE3/0/1 Device C GE3/0/2 Device D Configuration procedure Configuration on Device A Configure the suppression time of physical-link-state changes on GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2 as zero, disable STP, configure the two ports as trunk ports, and assign them to all VLANs.
Page 68
Configure Device A as the master node of primary ring 1, with GigabitEthernet 3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port, and enable ring 1. [DeviceA-rrpp-domain1] ring 1 node-mode master primary-port gigabitethernet 3/0/1 secondary-port gigabitethernet 3/0/2 level 0 [DeviceA-rrpp-domain1] ring 1 enable [DeviceA-rrpp-domain1] quit Enable RRPP.
Configure Device C using the same procedure as for configuring Device B. Configuration on Device D Configure Device D using the same procedure as for configuring Device B. Verification After the above configuration, you can use the display command to view RRPP configuration on each device.
Page 70
Configuration procedure Configuration on Device A Configure the suppression time of physical-link-state changes on GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2 as zero, disable STP, configure the two ports as trunk ports, and assign them to all VLANs. <DeviceA> system-view [DeviceA] interface gigabitethernet 3/0/1 [DeviceA-GigabitEthernet3/0/1] link-delay 0 [DeviceA-GigabitEthernet3/0/1] undo stp enable [DeviceA-GigabitEthernet3/0/1] port link-type trunk...
Page 71
[DeviceB-GigabitEthernet3/0/1] port link-type trunk [DeviceB-GigabitEthernet3/0/1] port trunk permit vlan all [DeviceB-GigabitEthernet3/0/1] quit [DeviceB] interface gigabitethernet 3/0/2 [DeviceB-GigabitEthernet3/0/2] link-delay 0 [DeviceB-GigabitEthernet3/0/2] undo stp enable [DeviceB-GigabitEthernet3/0/2] port link-type trunk [DeviceB-GigabitEthernet3/0/2] port trunk permit vlan all [DeviceB-GigabitEthernet3/0/2] quit [DeviceB] interface gigabitethernet 3/0/3 [DeviceB-GigabitEthernet3/0/3] link-delay 0 [DeviceB-GigabitEthernet3/0/3] undo stp enable [DeviceB-GigabitEthernet3/0/3] port link-type trunk [DeviceB-GigabitEthernet3/0/3] port trunk permit vlan all...
Page 72
[DeviceC-GigabitEthernet3/0/1] undo stp enable [DeviceC-GigabitEthernet3/0/1] port link-type trunk [DeviceC-GigabitEthernet3/0/1] port trunk permit vlan all [DeviceC-GigabitEthernet3/0/1] quit [DeviceC] interface gigabitethernet 3/0/2 [DeviceC-GigabitEthernet3/0/2] link-delay 0 [DeviceC-GigabitEthernet3/0/2] undo stp enable [DeviceC-GigabitEthernet3/0/2] port link-type trunk [DeviceC-GigabitEthernet3/0/2] port trunk permit vlan all [DeviceC-GigabitEthernet3/0/2] quit [DeviceC] interface gigabitethernet 3/0/3 [DeviceC-GigabitEthernet3/0/3] link-delay 0 [DeviceC-GigabitEthernet3/0/3] undo stp enable [DeviceC-GigabitEthernet3/0/3] port link-type trunk...
Page 73
[DeviceD-GigabitEthernet3/0/1] undo stp enable [DeviceD-GigabitEthernet3/0/1] port link-type trunk [DeviceD-GigabitEthernet3/0/1] port trunk permit vlan all [DeviceD-GigabitEthernet3/0/1] quit [DeviceD] interface gigabitethernet 3/0/2 [DeviceD-GigabitEthernet3/0/2] link-delay 0 [DeviceD-GigabitEthernet3/0/2] undo stp enable [DeviceD-GigabitEthernet3/0/2] port link-type trunk [DeviceD-GigabitEthernet3/0/2] port trunk permit vlan all [DeviceD-GigabitEthernet3/0/2] quit Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure VLANs mapped to MSTIs 0 through 47 as the protected VLANs of RRPP domain 1.
Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure VLANs mapped to MSTIs 0 through 47 as the protected VLANs of RRPP domain 1. [DeviceE] rrpp domain 1 [DeviceE-rrpp-domain1] control-vlan 4092 [DeviceE-rrpp-domain1] protected-vlan reference-instance 0 to 47 Configure Device E as the master node of subring 2, with GigabitEthernet 3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port, and enable ring 2.
Page 75
Figure 16 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 [DeviceA-vlan20] quit...
Page 76
Configure the suppression time of physical-link-state changes on GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2. as zero, disable STP, configure the two ports as trunk ports, remove them from VLAN 1, and assign them to VLAN 10 and VLAN 20. [DeviceA] interface gigabitethernet 3/0/1 [DeviceA-GigabitEthernet3/0/1] link-delay 0 [DeviceA-GigabitEthernet3/0/1] undo stp enable [DeviceA-GigabitEthernet3/0/1] port link-type trunk...
Page 77
Configuration on Device B Create VLANs 10 and 20, map VLAN 10 to MSTI 1 and VLAN 20 to MSTI 2, and activate MST region configuration. <DeviceB> system-view [DeviceB] vlan 10 [DeviceB-vlan10] quit [DeviceB] vlan 20 [DeviceB-vlan20] quit [DeviceB] stp region-configuration [DeviceB-mst-region] instance 1 vlan 10 [DeviceB-mst-region] instance 2 vlan 20 [DeviceB-mst-region] active region-configuration...
Page 78
Configure the suppression time of physical-link-state changes on GigabitEthernet 3/0/4 as zero, disable STP, configure the port as a trunk port, remove it from VLAN 1, and assign it to VLAN [DeviceB] interface gigabitethernet 3/0/4 [DeviceB-GigabitEthernet3/0/4] link-delay 0 [DeviceB-GigabitEthernet3/0/4] undo stp enable [DeviceB-GigabitEthernet3/0/4] port link-type trunk [DeviceB-GigabitEthernet3/0/4] undo port trunk permit vlan 1 [DeviceB-GigabitEthernet3/0/4] port trunk permit vlan 10...
Page 79
Enable RRPP. [DeviceB] rrpp enable Configuration on Device C Create VLANs 10 and 20, map VLAN 10 to MSTI 1 and VLAN 20 to MSTI 2, and activate MST region configuration. <DeviceC> system-view [DeviceC] vlan 10 [DeviceC-vlan10] quit [DeviceC] vlan 20 [DeviceC-vlan20] quit [DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 10...
Page 80
[DeviceC-GigabitEthernet3/0/3] port trunk permit vlan 20 [DeviceC-GigabitEthernet3/0/3] quit Configure the suppression time of physical-link-state changes on GigabitEthernet 3/0/4 as zero, disable STP, configure the port as a trunk port, remove it from VLAN 1, and assign it to VLAN [DeviceC] interface gigabitethernet 3/0/4 [DeviceC-GigabitEthernet3/0/4] link-delay 0 [DeviceC-GigabitEthernet3/0/4] undo stp enable [DeviceC-GigabitEthernet3/0/4] port link-type trunk...
Page 81
[DeviceC-rrpp-domain2] quit Enable RRPP. [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...
Page 82
[DeviceD-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 3/0/1 secondary-port gigabitethernet 3/0/2 level 0 [DeviceD-rrpp-domain1] ring 1 enable [DeviceD-rrpp-domain1] quit Create RRPP domain 2, configure VLAN 105 as the primary control VLAN of RPPP domain 2, and configure the VLAN mapped to MSTI 2 as the protected VLAN of RRPP domain 2. [DeviceD] rrpp domain 2 [DeviceD-rrpp-domain2] control-vlan 105 [DeviceD-rrpp-domain2] protected-vlan reference-instance 2...
Page 83
[DeviceE-GigabitEthernet3/0/2] undo port trunk permit vlan 1 [DeviceE-GigabitEthernet3/0/2] port trunk permit vlan 20 [DeviceE-GigabitEthernet3/0/2] quit Create RRPP domain 2, configure VLAN 105 as the primary control VLAN, and configure the VLAN mapped to MSTI 2 as the protected VLAN. [DeviceE] rrpp domain 2 [DeviceE-rrpp-domain2] control-vlan 105 [DeviceE-rrpp-domain2] protected-vlan reference-instance 2 Configure Device E as the master mode of subring 2 in RRPP domain 2, with GigabitEthernet...
[DeviceF-GigabitEthernet3/0/2] port trunk permit vlan 10 [DeviceF-GigabitEthernet3/0/2] quit Create RRPP domain 1, configure VLAN 100 as the primary control VLAN, and configure the VLAN mapped to MSTI 1 as the protected VLAN. [DeviceF] rrpp domain 1 [DeviceF-rrpp-domain1] control-vlan 100 [DeviceF-rrpp-domain1] protected-vlan reference-instance 1 Configure Device F as the master node of subring 3 in RRPP domain 1, with GigabitEthernet 3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port, and enable subring 3.
Page 85
Figure 17 Network diagram for fast detection configuration Configuration procedure Configuration on Device A Configure the suppression time of physical-link-state changes on GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2 as zero, disable STP, configure the two ports as trunk ports, and assign them to all VLANs.
Page 86
[DeviceA-rrpp-domain1] ring 1 node-mode master primary-port gigabitethernet 3/0/1 secondary-port gigabitethernet 3/0/2 level 0 [DeviceA-rrpp-domain1] ring 1 enable Enable fast detection, and set the Fast-Fail timer and Fast-Hello timer to 60 milliseconds and 20 milliseconds respectively. [DeviceA-rrpp-domain1] fast-detection enable [DeviceA-rrpp-domain1] timer fast-fail-timer 60 [DeviceA-rrpp-domain1] timer fast-hello-timer 20 [DeviceA-rrpp-domain1] quit Enable the RRPP protocol.
[DeviceC-GigabitEthernet3/0/2] undo stp enable [DeviceC-GigabitEthernet3/0/2] port link-type trunk [DeviceC-GigabitEthernet3/0/2] port trunk permit vlan all Configuration on Device D Configure the suppression time of physical-link-state changes on GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2 as zero, disable STP, configure the two ports as trunk ports, and assign them to all VLANs.
Page 88
When the link state is normal, the master node cannot receive Hello packets, and the master node unblocks the secondary port. Analysis: The reasons may be: • RRPP is not enabled on some nodes in the RRPP ring. • The domain ID or primary control VLAN ID is not the same for the nodes in the RRPP ring. •...
Smart Link configuration Smart Link overview To avoid single-point failures and guarantee network reliability, downstream switches are usually dual uplinked to upstream switches. That is, a downstream switch connects to two different upstream switches, as shown in Figure 18. Figure 18 Diagram for a dual uplink network A dual uplink network demonstrates high reliability, but it may contain network loops.
Terminology Smart Link group A Smart Link group consists of only two member ports: the master and the subordinate. At a time, only one port is active for forwarding, and the other port is blocked, that is, in the standby state. When link failure occurs on the active port due to port shutdown or presence of unidirectional link for example, the standby port becomes active to take over while the original active port transits to the blocked state.
flush messages in the receive control VLAN and refresh their MAC address forwarding entries and ARP/ND entries. Protected VLAN A Smart Link group controls the forwarding state of some data VLANs, which are referred to as protected VLANs. Different Smart Link groups on a port control different protected VLANs. The state of the port in a protected VLAN is determined by the state of the port in the Smart Link group.
Load sharing mechanism A ring network may carry traffic of multiple VLANs. Smart Link can forward traffic of different VLANs in different Smart Link groups, for load sharing. To implement load sharing, you can assign a port to multiple Smart Link groups (each configured with different protected VLANs), making sure that the state of the port is different in these Smart Link groups.
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 interface view. The configurations made in these two views have the same effect. In Smart Link group view To configure member ports for a Smart Link group in Smart Link group view: To do…...
The preemption delay configuration takes effect only after role preemption is enabled. Enabling the sending of flush messages To enable the sending of flush messages: To do… Use the command… Remarks Enter system view system-view — Create a Smart Link group and smart-link group Required enter Smart Link group view...
Make sure that the receive control VLAN is the same as the transmit control VLAN configured on the • Smart Link switch. If they are not the same, the associated switch will forward the received flush messages directly without any processing. Do not remove the control VLANs.
Page 97
• Configure Smart Link on the switches for uplink backup, using VLAN 1 (the default) for flush update. Figure 19 Single Smart Link group configuration Configuration procedure Configuration on Switch C Disable STP on related ports. <SwitchC> system-view [SwitchC] interface gigabitethernet 4/0/1 [SwitchC-GigabitEthernet4/0/1] stp disable [SwitchC-GigabitEthernet4/0/1] interface gigabitethernet 4/0/2 [SwitchC-GigabitEthernet4/0/2] stp disable...
Page 98
[SwitchE-GigabitEthernet4/0/1] interface gigabitethernet 4/0/2 [SwitchE-GigabitEthernet4/0/2] stp disable [SwitchE-GigabitEthernet4/0/2] quit Create Smart Link group 1 and configure all VLANs mapped to MSTIs 0 through 15 as the protected VLANs. [SwitchE] smart-link group 1 [SwitchE-smlk-group1] protected-vlan reference-instance 0 to 15 Configure GigabitEthernet 4/0/2 as the master port and GigabitEthernet 4/0/1 as the subordinate port of Smart Link group 1.
[SwitchA-GigabitEthernet4/0/2] smart-link flush enable [SwitchA-GigabitEthernet4/0/2] quit Verify the configurations You can use the display smart-link group command to display the Smart Link group configuration on each switch. For example: Display the Smart Link group configuration on Switch C. [SwitchC] display smart-link group 1 Smart Link group 1 information: Device ID: 000f-e23d-5af0 Preemption mode: NONE...
Page 100
Figure 20 Multiple Smart Link groups load sharing configuration Switch A GE4/0/1 GE4/0/2 GE4/0/1 GE4/0/1 GE4/0/2 GE4/0/2 Switch B Switch D GE4/0/1 GE4/0/2 Switch C Configuration procedure Configuration on Switch C Create VLAN 1 through VLAN 200, map VLAN 1 through VLAN 100 to MSTI 0 and VLAN 101 through VLAN 200 to MSTI 2, and activate MST region configuration.
Page 101
Configure GigabitEthernet 4/0/1 as the master port and GigabitEthernet 4/0/2 as the subordinate port of Smart Link group 1. [SwitchC-smlk-group1] port gigabitethernet4/0/1 master [SwitchC-smlk-group1] port gigabitethernet4/0/2 slave Enable role preemption in Smart Link group 1, enable flush message sending, and configure VLAN 10 as the transmit control VLAN.
Page 102
<SwitchD> system-view [SwitchD] vlan 1 to 200 Disable STP on ports GigabitEthernet 4/0/1 and GigabitEthernet 4/0/2, configure them as trunk ports, and assign them to VLANs 1 through 200; enable flush message receiving on the ports, and configure VLAN 10 and VLAN 101 as the receive control VLANs. [SwitchD] interface gigabitethernet 4/0/1 [SwitchD-GigabitEthernet4/0/1] port link-type trunk [SwitchD-GigabitEthernet4/0/1] port trunk permit vlan 1 to 200...
Page 103
Member Role State Flush-count Last-flush-time ----------------------------------------------------------------------------- GigabitEthernet4/0/1 MASTER ACTVIE 16:37:20 2009/02/21 GigabitEthernet4/0/2 SLAVE STANDBY 17:45:20 2009/02/21 Smart Link group 2 information: Device ID: 000f-e23d-5af0 Preemption mode: ROLE Control VLAN: 101 Protected VLAN: Reference Instance 2 Member Role State Flush-count Last-flush-time ----------------------------------------------------------------------------- GigabitEthernet4/0/2 MASTER...
Monitor link configuration Overview Monitor link is a port collaboration function. Monitor link is usually used in conjunction with Layer 2 topology protocols. The idea is to adapt the up/down state of downlink ports to the up/down state of uplink ports, triggering link switchover on the downlink switch in time. Terminology Monitor link group A monitor link group is a set of uplink ports and downlink ports.
Configuring monitor link Configuration prerequisites Before assigning a port to a monitor link group, make sure the port is not a member port of any aggregation group. Configuration procedure Follow these steps to configure monitor link: To do… Use the command… Remarks Enter system view system-view...
Monitor link configuration example By default, Ethernet, VLAN, and aggregate interfaces are in DOWN state. Before configuring these interfaces, use the undo shutdown command to bring them up. Network requirements As shown in Figure 21: • Switch C is dually uplinked to Switch A through a smart link group. •...
Page 107
[SwitchC-GigabitEthernet4/0/2] quit Create smart link group 1 and configure the smart link group to protect all the VLANs mapped to MSTIs 0 through 15. [SwitchC] smart-link group 1 [SwitchC-smlk-group1] protected-vlan reference-instance 0 to 15 Configure GigabitEthernet 4/0/1 as the master port and GigabitEthernet 4/0/2 as the slave port of smart link group 1.
VRRP configuration The switch operates in IRF or standalone (the default) mode. For more information about the IRF mode, • see IRF in the IRF Configuration Guide. The term router in this document refers to both routers and Layer 3 switches. •...
election mechanism to elect a master to take the responsibility of a gateway, so hosts on a LAN only need to configure the virtual router as their default network gateway. VRRP is an error-tolerant protocol, which improves network reliability and simplifies host configuration.
Page 111
Figure 23 Network diagram for VRRP Virtual router Router A Host A Router B Network Host B Router C Host C As shown in Figure 23, Router A, Router B, and Router C form a virtual router, which has its own IP address.
• Preemptive mode When a backup finds its priority higher than that of the master, the backup sends VRRP advertisements to start a new master election in the VRRP group and becomes the master. Accordingly, the original master becomes a backup. Authentication mode To avoid being attacked by unauthorized users, VRRP authenticates the received packets by adding authentication keys into the packets.
Page 113
Figure 24 Format of a VRRPv2 packet Figure 25 Format of a VRRPv3 packet Version Type Virtual Rtr ID Priority Count IPv6 Addrs Auth Type Adver Int Checksum IPv6 address 1 IPv6 address n Authentication data 1 Authentication data 2 A VRRP packet consists of the following fields: •...
• Auth Type: Authentication type. 0 means no authentication, 1 means simple text authentication, and 2 means MD5 authentication. VRRPv3 does not support MD5 authentication. • Adver Int: Interval for sending advertisement packets. For VRRPv2, the interval is in seconds and defaults to 1;...
• Monitor an uplink and modify the priority of the router according to the state of the uplink. If there is a fault on the uplink, hosts in the LAN cannot access the external network through the router. In this case, the state of the monitored track entry changes to negative and the priority of the router decreases by a specified value.
Load sharing You can create more than one VRRP group on an interface of a router, and allow the router to be the master of one VRRP group and a backup of another at the same time. In load sharing mode, multiple routers provide services at the same time. This mode requires two or more VRRP groups, each of which includes a master and one or more backups.
load sharing among multiple routers, hosts on the LAN need to be configured with different gateways, making the configuration complicated. For load balancing, besides virtual gateway redundancy, VRRP can work in load balancing mode. In load balancing mode, you associate a virtual IP address with multiple virtual MAC addresses to make each router in a VRRP group correspond to a virtual MAC address.
Figure 28 Allocating virtual MAC addresses As shown in Figure 28, the virtual IP address of the VRRP group is 10.1.1.1/24; Router A is the master; Router B and Router C are the backups. Router A allocates different virtual MAC addresses to Routers A, B and C.
Page 119
a VF corresponding to this MAC address, and the router becomes the owner of the VF it has created. VF weight and priority The weight of a VF indicates the forwarding capability of a router: the higher the weight, the higher the forwarding capability.
VF tracking The AVF forwards packets destined to the MAC address of the AVF. If the uplink of the AVF fails and no LVF is notified to take over the AVF's work, hosts (on the LAN) that take the MAC address of the AVF as their gateway MAC address cannot access the external network.
Configuring VRRP for IPv4 Configuring the association between virtual IP address and MAC address After the virtual IP address of a VRRP group is associated with a MAC address, the master takes the configured MAC address as the source MAC address of the packets to be sent, so that the hosts in the internal network can learn the association between the IP address and the MAC address and forward the packets to be forwarded to the other network segments to the master.
If you specify another virtual IP address for the VRRP group later, the virtual IP address is added to the virtual IP address list of the VRRP group. H3C does not recommend creating VRRP groups on the VLAN interface of a super VLAN. Otherwise, network performance may be affected.
VRRP group resides or the IP address of an interface on a router in the VRRP group. In the latter case, the router is called the IP address owner. Removal of the VRRP group of the IP address owner will cause IP address collision. In such a case, H3C •...
To configure router priority, preemptive mode and the track entry tracking function: To do… Use the command… Remarks Enter system view system-view — interface interface-type interface- Enter interface view — number Optional Configure router priority in the vrrp vrid virtual-router-id VRRP group priority priority-value 100 by default.
decrease by a specified value; when the state of the track entry becomes positive or invalid, the weight values of all VFs on the routers restore their original values. To configure VF tracking: To do… Use the command… Remarks Enter system view system-view —...
To do… Use the command… Remarks Configure the time interval for Optional vrrp vrid virtual-router-id timer the Master in the VRRP group advertise adver-interval 1 second by default to send VRRP advertisement Optional Enabled by default Disable TTL check on VRRP vrrp un-check ttl You do not need to create a VRRP packets...
To do… Use the command… Remarks display vrrp statistics [ interface Display VRRP group statistics interface-type interface-number [ vrid virtual- Available in any view router-id ] ] reset vrrp statistics [ interface interface- Available in user view Clear VRRP group statistics type interface-number [ vrid virtual-router-id ] ] Configuring VRRP for IPv6 Configuring the association between virtual IPv6 address...
If you specify another virtual IPv6 address for the VRRP group later, the virtual IPv6 address is added to the virtual IPv6 address list of the VRRP group. H3C does not recommend creating VRRP groups on the VLAN interface of a super VLAN, because network performance may be affected.
• that VRRP group no longer take effect. Removal of the VRRP group of the IP address owner will cause IP address collision. In such a case, H3C • recommends that you change the IPv6 address of the interface of the IP address owner to resolve the collision.
The running priority of an IP address owner is always 255 and you do not need to configure it. An IP • address owner always works in the preemptive mode. Interface tracking is not configurable on an IP address owner. •...
only when the weight of the VF owner decreases by a properly specified value and becomes lower than the lower limit of failure, can another VF take over the VF owner's work and become the AVF. Configuring VRRP packet attributes Configuration prerequisites Before configuring the relevant attributes of VRRP packets, you should first create a VRRP group and configure a virtual IPv6 address.
To do… Use the command… Remarks reset vrrp ipv6 statistics [ interface Available in user Clear VRRP group statistics interface-type interface-number [ vrid virtual- view router-id ] ] IPv4-based VRRP configuration examples By default, Ethernet interfaces, VLAN interfaces, and aggregate interfaces are in the DOWN state. To configure such an interface, use the undo shutdown command to bring it up first.
Page 133
Configure VLAN 2. <SwitchA> system-view [SwitchA] vlan 2 [SwitchA-vlan2] port Gigabitethernet 3/0/5 [SwitchA-vlan2] quit [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] ip address 202.38.160.1 255.255.255.0 Create VRRP group 1 and set its virtual IP address to be 202.38.160.111. [SwitchA-Vlan-interface2] vrrp vrid 1 virtual-ip 202.38.160.111 Set the priority of Switch A in VRRP group 1 to 110.
Page 134
Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : 202.38.160.111 Virtual MAC : 0000-5e00-0101 Master IP : 202.38.160.1 Display detailed information of VRRP group 1 on Switch B. [SwitchB-Vlan-interface2] display vrrp verbose IPv4 Standby Information: Run Mode : Standard Run Method : Virtual MAC...
VRRP interface tracking configuration example Network requirements • Host A needs to access Host B on the Internet, using 202.38.160.111/24 as its default gateway. • Switch A and Switch B belong to VRRP group 1 with the virtual IP address of 202.38.160.111/24.
Page 136
Configure the authentication mode of the VRRP group as simple and authentication key as hello. [SwitchA-Vlan-interface2] vrrp vrid 1 authentication-mode simple hello Set the interval for Master to send VRRP advertisement to five seconds. [SwitchA-Vlan-interface2] vrrp vrid 1 timer advertise 5 Set the interface to be tracked.
Page 137
Virtual MAC : 0000-5e00-0101 Master IP : 202.38.160.1 VRRP Track Information: Track Interface: Vlan3 State : Up Pri Reduced : 30 Display detailed information of VRRP group 1 on Switch B. [SwitchB-Vlan-interface2] display vrrp verbose IPv4 Standby Information: Run Mode : Standard Run Method : Virtual MAC...
If VLAN-interface 3 on Switch A is not available, the detailed information of VRRP group 1 on Switch B is displayed. [SwitchB-Vlan-interface2] display vrrp verbose IPv4 Standby Information: Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer...
Page 139
Figure 32 Network diagram for multiple VRRP group configuration Virtual IP address 1: 202.38.160.100/25 Switch A Vlan-int2 VLAN 2 202.38.160.1/25 Vlan-int3 Gateway: 202.38.160.130/25 202.38.160.100/25 Internet VLAN 3 Vlan-int2 202.38.160.2/25 Gateway: Vlan-int3 202.38.160.200/25 202.38.160.131/25 Switch B Virtual IP address 2: 202.38.160.200/25 Configuration procedure Configure Switch A Configure VLAN 2.
Page 140
Configure VLAN 2. <SwitchB> system-view [SwitchB] vlan 2 [SwitchB-vlan2] port Gigabitethernet 3/0/5 [SwitchB-vlan2] quit [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] ip address 202.38.160.2 255.255.255.128 Create a VRRP group 1 and set its virtual IP address to 202.38.160.100. [SwitchB-Vlan-interface2] vrrp vrid 1 virtual-ip 202.38.160.100 [SwitchB-Vlan-interface2] quit Configure VLAN 3.
Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : 202.38.160.200 Master IP : 202.38.160.131 Display detailed information of the VRRP group on Switch B. [SwitchB-Vlan-interface3] display vrrp verbose IPv4 Standby Information: Run Mode...
Page 142
• Hosts on network segment 10.1.1.0/24 use 10.1.1.1/24 as their default gateway. Use the VRRP group to ensure that when a gateway (Switch A, Switch B, or Switch C) fails, the hosts on the LAN can access the external network through another gateway. •...
Page 143
[SwitchA-Vlan-interface2] vrrp vrid 1 priority 120 Set Switch A to work in preemptive mode. The preemption delay is five seconds. [SwitchA-Vlan-interface2] vrrp vrid 1 preempt-mode timer delay 5 Configure Switch B Configure VLAN 2. <SwitchB> system-view [SwitchB] vlan 2 [SwitchB-vlan2] port Gigabitethernet 3/0/5 [SwitchB-vlan2] quit Configure VRRP to work in load balancing mode.
Page 144
IPv4 Standby Information: Run Mode : Load Balance Run Method : Virtual MAC Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer Admin Status : Up State : Master Config Pri : 120 Running Pri : 120 Preempt Mode : Yes Delay Time...
Page 145
VRID Adver Timer Admin Status : Up State : Backup Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : 10.1.1.1 Master IP : 10.1.1.2 Forwarder Information: 3 Forwarders 1 Active Config Weight : 255 Running Weight : 255...
Page 146
Virtual IP : 10.1.1.1 Master IP : 10.1.1.2 Forwarder Information: 3 Forwarders 1 Active Config Weight : 255 Running Weight : 255 Forwarder 01 State : Listening Virtual MAC : 000f-e2ff-0011 (Learnt) Owner ID : 0000-5e01-1101 Priority : 127 Active : 10.1.1.2 Forwarder 02 State...
Master IP : 10.1.1.3 Forwarder Information: 3 Forwarders 2 Active Config Weight : 255 Running Weight : 255 Forwarder 01 State : Active Virtual MAC : 000f-e2ff-0011 (Take Over) Owner ID : 0000-5e01-1101 Priority : 85 Active : local Redirect Time : 577 secs Time-out Time : 1777 secs...
Page 148
• If Switch A operates normally, packets sent from Host A to Host B are forwarded by Switch A; if Switch A fails, packets sent from Host A to Host B are forwarded by Switch B. Figure 34 Network diagram for single VRRP group configuration Virtual IPv6 address: FE80::10 Vlan-int2...
Page 149
[SwitchB] ipv6 [SwitchB] vlan 2 [SwitchB-vlan2] port Gigabitethernet 3/0/5 [SwitchB-vlan2] quit [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] ipv6 address fe80::2 link-local [SwitchB-Vlan-interface2] ipv6 address 1::2 64 Create a VRRP group 1 and set its virtual IPv6 addresses to FE80::10. [SwitchB-Vlan-interface2] vrrp ipv6 vrid 1 virtual-ip fe80::10 link-local Configure Switch B to work in the preemptive mode, with the preemption delay set to 5 seconds.
VRID Adver Timer : 100 Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : FE80::10 1::10 Master IP : FE80::1 The above information shows that in VRRP group 1 Switch A is the master, Switch B is the backup and packets sent from Host A to Host B are forwarded by Switch A.
Page 151
Figure 35 Network diagram for VRRP interface tracking Configuration procedure Configure Switch A Configure VLAN 2. <SwitchA> system-view [SwitchA] ipv6 [SwitchA] vlan 2 [SwitchA-vlan2] port Gigabitethernet 3/0/5 [SwitchA-vlan2] quit [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] ipv6 address fe80::1 link-local [SwitchA-Vlan-interface2] ipv6 address 1::1 64 Create a VRRP group 1 and set its virtual IPv6 addresses to FE80::10 and 1::10.
Page 152
[SwitchA-Vlan-interface2] vrrp ipv6 vrid 1 track interface vlan-interface 3 reduced 30 Enable Switch A to send RA messages. [SwitchA-Vlan-interface2] undo ipv6 nd ra halt Configure Switch B Configure VLAN 2. <SwitchB> system-view [SwitchB] ipv6 [SwitchB] vlan 2 [SwitchB-vlan2] port Gigabitethernet 3/0/5 [SwitchB-vlan2] quit [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] ipv6 address fe80::2 link-local...
Page 153
Auth Type : Simple : hello Virtual IP : FE80::10 1::10 Virtual MAC : 0000-5e00-0201 Master IP : FE80::1 VRRP Track Information: Track Interface: Vlan3 State : Up Pri Reduced : 30 Display detailed information of VRRP group 1 on Switch B. [SwitchB-Vlan-interface2] display vrrp ipv6 verbose IPv6 Standby Information: Run Mode...
Virtual IP : FE80::10 1::10 Master IP : FE80::2 VRRP Track Information: Track Interface: Vlan3 State : Down Pri Reduced : 30 If interface VLAN-interface 3 on Switch A is not available, the detailed information of VRRP group 1 on Switch B is displayed. [SwitchB-Vlan-interface2] display vrrp ipv6 verbose IPv6 Standby Information: Run Mode...
Page 155
Figure 36 Network diagram for multiple VRRP group configuration Configuration procedure Configure Switch A Configure VLAN 2. <SwitchA> system-view [SwitchA] ipv6 [SwitchA] vlan 2 [SwitchA-vlan2] port Gigabitethernet 3/0/5 [SwitchA-vlan2] quit [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] ipv6 address fe80::1 link-local [SwitchA-Vlan-interface2] ipv6 address 1::1 64 Create VRRP group 1 and set its virtual IPv6 addresses to FE80::10 to 1::10.
Page 156
[SwitchA-vlan3] quit [SwitchA] interface vlan-interface 3 [SwitchA-Vlan-interface3] ipv6 address fe90::1 link-local [SwitchA-Vlan-interface3] ipv6 address 2::1 64 Create VRRP group 2 and set its virtual IPv6 addresses to FE90::10 and 2::10. [SwitchA-Vlan-interface3] vrrp ipv6 vrid 2 virtual-ip fe90::10 link-local [SwitchA-Vlan-interface3] vrrp ipv6 vrid 2 virtual-ip 2::10 Enable Switch A to send RA messages.
Page 157
Verify the configuration You can use the display vrrp ipv6 verbose command to verify the configuration. Display detailed information of the VRRP group on Switch A. [SwitchA-Vlan-interface3] display vrrp ipv6 verbose IPv6 Standby Information: Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 2 Interface Vlan-interface2...
Virtual IP : FE80::10 1::10 Master IP : FE80::1 Interface Vlan-interface3 VRID Adver Timer : 100 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : FE90::10 2::10...
Page 159
Figure 37 Network diagram for VRRP load balancing mode Configuration procedure Configure Switch A Configure VLAN 2. <SwitchA> system-view [SwitchA] vlan 2 [SwitchA-vlan2] port Gigabitethernet 3/0/5 [SwitchA-vlan2] quit Configure VRRP to work in load balancing mode. [SwitchA] vrrp mode load-balance Create VRRP group 1 and configure its virtual IPv6 address as FE80::10.
Page 160
Enable Switch A to send RA messages. [SwitchA-Vlan-interface2] undo ipv6 nd ra halt Configure Switch B Configure VLAN 2. <SwitchB> system-view [SwitchB] vlan 2 [SwitchB-vlan2] port Gigabitethernet 3/0/5 [SwitchB-vlan2] quit Configure VRRP to work in load balancing mode. [SwitchB] vrrp mode load-balance Create VRRP group 1 and configure its virtual IPv6 address as FE80::10.
Page 161
Verify the configuration After the configuration, Host A can ping the external network. You can use the display ipv6 vrrp verbose command to verify the configuration. Display detailed information of VRRP group 1 on Switch A. [SwitchA-Vlan-interface2] display vrrp ipv6 verbose IPv6 Standby Information: Run Mode : Load Balance...
Page 162
[SwitchB-Vlan-interface2] display vrrp ipv6 verbose IPv6 Standby Information: Run Mode : Load Balance Run Method : Virtual MAC Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer : 100 Admin Status : Up State : Backup Config Pri : 110 Running Pri : 110...
Page 163
Interface Vlan-interface2 VRID Adver Timer : 100 Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : FE80::10 Master IP : FE80::1 Forwarder Information: 3 Forwarders 1 Active Config Weight : 255...
VRID Adver Timer : 100 Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : FE80::10 Master IP : FE80::2 Forwarder Information: 3 Forwarders 2 Active Config Weight : 255 Running Weight : 255...
Page 165
This error is probably caused by the following: • Inconsistent configuration of the switches in the VRRP group. • A switch is attempting to send illegal VRRP packets. Solution: • In the first case, modify the configuration. • In the latter case, you have to resort to non-technical measures. Symptom 2: Multiple masters are present in the same VRRP group.
GR overview The term router in this document refers to both routers and Layer 3 switches. Introduction to GR GR ensures the continuity of packet forwarding when a protocol restarts or during an active/standby switchover process. The mechanism of GR works as follows: When the protocol on a switch restarts, the switch notifies its neighbors to temporarily preserve the routing information and adjacency relationship with the switch.
GR time GR time refers to the maximum time allowed to complete a GR communication procedure. The GR Helper preserves topology or routing information sent from the GR Restarter until GR time expires. When GR time expires, the GR communication procedure is ended. GR communication procedure In some cases, GR Restarter and GR Helper can replace each other.
Page 168
Restarting GR Restarter Figure 39 Protocol restarting process for the GR Restarter Router D GR helper GR restarter Router A Router C Router B GR helper GR helper GR session The administrator restarts GR Restarter or GR Restarter is operating abnormally As illustrated in Figure 39, the GR Helper detects that the GR Restarter has restarted its routing protocol and assumes that it will recover within the GR Time.
As illustrated in Figure 40, after the GR Restarter has recovered, it will signal to all its neighbors and reestablish GR Session. Obtaining topology and routing information Figure 41 The GR Restarter obtains topology and routing information from the GR Helper As illustrated in Figure 41, the GR Restarter obtains the necessary topology and routing information from all its neighbors through the GR sessions between them and calculates its own routing table based on this information.
BFD configuration The term router in this document refers to both routers and Layer 3 switches. Introduction to BFD Switches needs to detect communication failures quickly so that measures can be taken in time to ensure service continuity. Fault detection methods include the following: •...
Page 171
Operation of BFD Figure 42 BFD session establishment (on OSPF routers) Router A Router B OSPF neighbors BFD neighbors OSPF advertises the BFD neighbor relationship BFD session establishment (as shown in Figure 42): • A protocol sends hello messages to discover neighbors and establish neighborships. •...
Page 172
BFD detection methods • Single-hop detection: Detects the IP connectivity between two directly connected systems. • Multi-hop detection: Detects any of the paths between two systems. These paths have multiple hops and may be overlapped. • Bidirectional detection: Sends detection packets at two sides of a bidirectional link to detect the bidirectional link status and find link failures in milliseconds.
Dynamic BFD parameter changes After a BFD session is established, both ends can negotiate the related BFD parameters, such as the minimum transmit interval, minimum receive interval, initialization mode, and packet authentication mode. After that, both ends use the negotiated parameters, without affecting the current session state.
• State (Sta): Current BFD session state. Its value can be 0 for AdminDown, 1 for Down, 2 for Init, and 3 for Up. • Demand (D): If set, Demand mode is active in the transmitting system (the system is beginning to operate in Demand mode, knows that the session is up in both directions, and is directing the remote system to cease the periodic transmission of BFD Control packets).
• IS-IS: For more information, see IS-IS in the Layer 3 – IP Routing Configuration Guide and Layer 3 – IP Routing Command Reference. • RIP: For more information, see RIP in the Layer 3 – IP Routing Configuration Guide and Layer 3 –...
Configuration procedure To configure BFD basic functions: To do… Use the command… Remarks Enter system view system-view — Optional Specify the mode for bfd session init-mode { establishing a BFD session active | passive } active by default Optional The source IP address should not be on the same network segment as any local Configure the source IP bfd echo-source-ip ip-...
To do… Use the command… Remarks Configure the maximum number of consecutive BFD Optional packets that the remote switch bfd detect-multiplier value fails to receive from the local 5 by default switch before considering the BFD session down Displaying and maintaining BFD To do…...
Track configuration Track overview Figure 45 Collaboration through the track module The track module is used to implement collaboration between different modules. The collaboration involves three parts: the application modules, the track module, and the detection modules. These modules collaborate with one another through collaboration objects (Reaction entries).
• For more information about NQA Configuration, see NQA in the Network Management and Monitoring Configuration Guide. • For more information about BFD, see BFD in the High Availability Configuration Guide. • The interface management module is used to monitor the physical status or Layer 3 protocol status of an interface.
To do… Use the command… Remarks Create a track entry, associate it with track track-entry-number nqa Required the specified reaction entry of the entry admin-name operation- No track entry that is NQA test group, and specify the delay tag reaction item-num [ associated with the specified time for the track module to notify the delay { negative negative-...
When configuring collaboration between track and BFD, do not configure the local address or remote address of a BFD session as the virtual IP address of a VRRP group. Configuring collaboration between the track module and the interface management module Through the following configuration, you can establish collaboration between the track module and the interface management module, which informs the track module of the changes of the physical status and Layer 3 protocol status of an interface.
Page 182
master, hosts in the LAN cannot access the external network. This problem can be solved with the track-VRRP collaboration function. Use the detection modules to monitor the status of the uplink of the router and establish collaborations between the detection modules, track module and VRRP.
monitored using the vrrp vrid track command, and then create the track entry using the track command. For more information about VRRP configuration, see VRRP in the High Availability Configuration Guide. • Configuring track-static routing collaboration A static route is a manually configured route. With a static route configured, packets to the specified destination are forwarded through the path specified by the administrator.
directly; for a nonexistent static route, the system creates the static route and then associates it with the specified track entry. The track entry to be associated with the static route can be a nonexistent one. After you use the track •...
To do… Use the command… Remarks policy-based-route policy-name Create a policy or policy node { deny | permit } node node- Required and enter the policy view number Match an ACL if-match acl acl-number Optional Optional apply ip-address next-hop ip- Specify the next hop of packets address1 [ direct ] [ track track- You can configure two next hops,...
Page 186
• When Switch A works normally, packets from Host A to Host B are forwarded through Switch A. When VRRP finds that there is a fault on the uplink of Switch A through NQA, packets from Host A to Host B are forwarded through Switch B. Network diagram Figure 46 Network diagram for VRRP-track-NQA collaboration configuration...
Page 187
[SwitchA] nqa schedule admin test start-time now lifetime forever Configure a track entry on Switch A Configure track entry 1, and associate it with Reaction entry 1 of the NQA test group (with the administrator admin, and the operation tag test). [SwitchA] track 1 nqa entry admin test reaction 1 Configure VRRP on Switch A Create VRRP group 1, and configure the virtual IP address 10.1.1.10 for the group.
Page 188
Interface Vlan-interface2 VRID Adver Timer Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time Auth Type : Simple : hello Virtual IP : 10.1.1.10 Virtual MAC : 0000-5e00-0101 Master IP : 10.1.1.1 VRRP Track Information:...
Preempt Mode : Yes Delay Time Auth Type : Simple : hello Virtual IP : 10.1.1.10 Master IP : 10.1.1.2 VRRP Track Information: Track Object State : Negative Pri Reduced : 30 Display detailed information about VRRP group 1 on Switch B when there is a fault on the link between Switch A and Switch C.
Page 190
Figure 47 Network diagram for monitoring the master on the backup Internet Virtual router Switch A Switch B Virtual IP address: Master Backup 192.168.0.10 Vlan-int2 Vlan-int2 192.168.0.101/24 192.168.0.102/24 L2 switch BFD probe packets VRRP packets Configuration procedure Create VLANs, and assign IP addresses to VLAN interfaces, as shown in Figure 47. (Details not shown.) Add ports to related VLANs.
Page 191
Create track entry 1 to be associated with the BFD session to check whether Switch A is reachable. [SwitchB] track 1 bfd echo interface vlan-interface 2 remote ip 192.168.0.101 local ip 192.168.0.102 Configure VRRP on Switch B Create VRRP group 1, and configure the virtual IP address 192.168.0.10 for the group. VRRP group 1 monitors the status of track entry 1.
Page 192
Virtual IP : 192.168.0.10 Master IP : 192.168.0.101 VRRP Track Information: Track Object State : Positive Switchover Display information about track entry 1 on Switch B. <SwitchB> display track 1 Track ID: 1 Status: Positive Notification delay: Positive 0, Negative 0 (in seconds) Reference object: BFD session: Packet type: Echo...
Virtual IP : 192.168.0.10 Virtual MAC : 0000-5e00-0101 Master IP : 192.168.0.102 VRRP Track Information: Track Object State : Negative Switchover The above output shows that when BFD detects that Router A fails, it notifies VRRP through the track module to change the status of Router B to master, without waiting for the VRRP advertisement interval timer, so that a backup can quickly preempt as the master.
Page 194
Configuration procedure Create VLANs, and assign IP addresses to VLAN interfaces, as shown in Figure 48. (Details not shown.) Add ports to related VLANs. (Details not shown.) Configure BFD on Switch A. Configure the source address of BFD echo packets as 10.10.10.10. <SwitchA>...
Page 195
Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : 192.168.0.10 Virtual MAC : 0000-5e00-0101 Master IP : 192.168.0.101 VRRP Track Information: Track Object State : Positive Pri Reduced : 20 Display the information of track entry 1 on Switch A. <SwitchA>...
Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer Admin Status : Up State : Backup Config Pri : 110 Running Pri : 90 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : 192.168.0.10 Master IP : 192.168.0.102 VRRP Track Information:...
Page 197
Network diagram Figure 49 Network diagram for static routing-track-NQA collaboration configuration Switch B Vlan-int3 Vlan-int2 10.2.1.1/24 10.1.1.1/24 Vlan-int3 Vlan-int2 10.2.1.2/24 10.1.1.2/24 Switch A Switch C Configuration procedure Create VLANs, and assign IP addresses to VLAN interfaces, as shown in Figure 49. (Details not shown.) Add ports to related VLANs.
Page 198
Configure track entry 1, and associate it with Reaction entry 1 of the NQA test group (with the administrator admin, and the operation tag test). [SwitchA] track 1 nqa entry admin test reaction 1 Verify the configuration Display information of the track entry on Switch A. [SwitchA] display track all Track ID: 1 Status: Positive...
[SwitchA] display ip routing-table Routing Tables: Public Destinations : 4 Routes : 4 Destination/Mask Proto Cost NextHop Interface 10.2.1.0/24 Direct 0 10.2.1.2 Vlan3 10.2.1.2/32 Direct 0 127.0.0.1 InLoop0 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 The output information above shows the NQA test result, that is, the next hop 10.2.1.1 is unreachable (the status of the track entry is Negative), and the configured static route is invalid.
Page 200
Configure basic BFD functions on Switch A Configure the source address of BFD echo packets as 10.10.10.10. [SwitchA] bfd echo-source-ip 10.10.10.10 Configure a track entry on Switch A Configure track entry 1, and associate it with the BFD session. Check whether Switch A can be interoperated with the next hop of static route: Switch B.
[SwitchA] display track all Track ID: 1 Status: Negative Notification delay: Positive 0, Negative 0 (in seconds) Reference object: BFD Session: Packet type: Echo Interface : Vlan-interface3 Remote IP : 10.2.1.1 Local IP : 10.2.1.2 Display the routing table of Switch A. [SwitchA] display ip routing-table Routing Tables: Public Destinations : 4...
Page 202
Figure 51 Network diagram for VRRP-track-interface management collaboration configuration Virtual IP address: 10.1.1.10/24 Vlan-int2 Vlan-int3 10.1.1.1/24 10.1.2.1/24 Vlan-int3 10.1.2.2/24 Switch A Switch C 20.1.1.1/24 10.1.1.3/24 Internet Host B Host A Vlan-int3 Vlan-int2 10.1.3.1/24 10.1.1.2/24 Vlan-int3 10.1.3.2/24 Switch B Switch D Configuration procedure Create VLANs, and assign IP addresses to VLAN interfaces, as shown in Figure 51.
Page 203
Display detailed information about VRRP group 1 on Switch A. [SwitchA-Vlan-interface2] display vrrp verbose IPv4 Standby Information: Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer Admin Status : Up State : Master...
Page 204
After shutting down the uplink interface on Switch A, display detailed information about VRRP group 1 on Switch A. [SwitchA-Vlan-interface3] display vrrp verbose IPv4 Standby Information: Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer...
Contact your authorized reseller or 3Com for a complete list of the value-added services available in your area. Troubleshoot online You will find support tools posted on the web site at http://www.h3cnetworks.com/ under Support, Knowledgebase. The Knowledgebase helps you troubleshoot H3C products. This query-based interactive tool contains thousands of technical solutions.
Access software downloads Software Updates are the bug fix / maintenance releases for the version of software initially purchased with the product. In order to access these Software Updates you must first register your product on the web site at http://www.h3cnetworks.com, go to Support, Product Registration.
Acronyms # A B C D E F G H I K L M N O P Q R S T U V W X Z Acronym Full spelling Return 10GE Ten-GigabitEthernet Return Authentication, Authorization and Accounting Activity Based Costing Area Border Router Alternating Current Acknowledgement...
Page 208
Acronym Full spelling Auxiliary (port) Active Virtual Forwarder Return Bearer Control Backup Designated Router Best Effort Bidirectional Forwarding Detection Border Gateway Protocol BIMS Branch Intelligent Management System BOOTP Bootstrap Protocol BPDU Bridge Protocol Data Unit Basic Rate Interface Bootstrap Router BitTorrent BSR State Burst Tolerance...
Page 209
Acronym Full spelling CIDR Classless Inter-Domain Routing Committed Information Rate CIST Common and Internal Spanning Tree Command Line Interface CLNP Connectionless Network Protocol Customer Premise Equipment CPOS Channelized POS Central Processing Unit Custom Queuing Carriage Return Cyclic Redundancy Check CR-LSP Constraint-based Routing LSP CR-LDP Constraint-based Routing LDP...
Page 210
Acronym Full spelling Designated Router DSCP Differentiated Services Code point Priority Digital Signal Processor Data Terminal Equipment Downstream Unsolicited DUID DHCP Unique Identifier DUID-LL DUID based Link Layer address Distance Vector Routing Algorithm DVMRP Distance Vector Multicast Routing Protocol DWDM Dense Wavelength Division Multiplexing Return EBGP...
Page 211
Acronym Full spelling Frame Relay Fast Reroute FRTT Fairness Round Trip Time Finite State Machine Functional Test File Transfer Protocol Return GARP Generic Attribute Registration Protocol Gigabit Ethernet Graceful Restart Generic Routing Encapsulation Generic Traffic Shaping GVRP GARP VLAN Registration Protocol Return High Availability HABP...
Page 212
Acronym Full spelling IEEE Institute of Electrical and Electronics Engineers IETF Internet Engineering Task Force IGMP Internet Group Management Protocol IGMP-Snooping Internet Group Management Protocol Snooping Interior Gateway Protocol Incoming Label Map Internet Locator Service Intelligent Network IntServ Integrated Service Internet Protocol IPng IP Next Generation...
Page 213
Acronym Full spelling LACP Link Aggregation Control Protocol LACPDU Link Aggregation Control Protocol Data Unit Local Area Network Link Control Protocol LDAP Lightweight Directory Access Protocol Label Distribution Protocol Label Edge Router LFIB Label Forwarding Information Base Label Information Base Link Layer Control LLDP Link Layer Discovery Protocol...
Page 214
Acronym Full spelling Multi-VPN instance Customer Edge Multicast Domain Medium Dependent Interface Multicast Distribution Tree Multi-Exit Discriminator MAC Forced Forwarding Management Information Base Multicast Listener Discovery Protocol MLD-Snooping Multicast Listener Discovery Snooping Meet-Me Conference MODEM Modulator/Demodulator Multilink PPP MP-BGP Multiprotocol extensions for BGP-4 Middle-level PE MP-group Multilink Point to Point Protocol group...
Page 215
Acronym Full spelling NBMA Non Broadcast Multi-Access NetBIOS over TCP/IP Network Control Protocol Neighborhood discovery NetStream Data Analyzer Network Data Collector Neighbor Discovery Protocol NetBIOS Network Basic Input/Output System NHLFE Next Hop Label Forwarding Entry Network Load Balancing NLPID Network Layer Protocol Identifier NLRI Network Layer Reachability Information Network Management Station...
Page 216
Acronym Full spelling Provider P2MP Point to MultiPoint Point To Point Password Authentication Protocol Printed Circuit Board Pulse Code Modulation Powered Device, Prefix Delegation or Pure Data Protocol Data Unit Provider Edge Penultimate Hop Popping Physical layer Protocol Independent Multicast PIM-DM Protocol Independent Multicast-Dense Mode PIM-SM...
Page 217
Acronym Full spelling QACL QoS/ACL QinQ 802.1Q in 802.1Q Quality of Service QQIC Querier's Query Interval Code Querier's Robustness Variable Return Registration Authority or Router Advertisement RADIUS Remote Authentication Dial in User Service random-access memory Routing Domain Router Distinguisher Random Early Detection Request For comments Routing Information Protocol RIPng...
Page 218
Acronym Full spelling Return Source Active Sub-network Bandwidth Management SCFF Single Choke Fairness Frame Signal Degrade Synchronous Digital Hierarchy SETS Synchronous Equipment Timing Source Sampling Frequency Source-Filtered Multicast SFTP Secure FTP Share-MDT Share-Multicast Distribution Tree Session Initiation Protocol Site-of-Origin Site-of-Origin Service Level Agreement Standby Main Board SMTP...
Page 219
Acronym Full spelling STM-16c SDH Transport Module -16c STM-4c SDH Transport Module -4c Spanning Tree Protocol Signaling Virtual Connection SVLAN Service Provider Virtual Local Area Network Switch-MDT Switch-Multicast Distribution Tree Synchronize Return Terminal Adapter TACACS Terminal Access Controller Access Control System Time Division Multiplexing Transmission Control Protocol Topology Change Notification...
Page 220
Acronym Full spelling Virtual Channel Identifier Virtual Ethernet Virtual Forwarder Virtual File System VLAN Virtual Local Area Network Virtual Leased Lines Video On Demand VoIP Voice over IP Virtual Operate System VPDN Virtual Private Dial-up Network VPDN Virtual Private Data Network Virtual Path Identifier VPLS Virtual Private Local Switch...
Index "last mile"........... 20 operation ..........170 active and standby switchover ......17 packet format ......... 173 automatic ..........17 protocols and standards ......175 display and maintain ......... 19 session modes ........172 manual ..........17, 19 static routing-track-BFD configuration example ............
Page 222
track and VRRP ........179 non-authentication ........35 track module and application modules ..179 plain text authentication ......35 track module and detection modules ..178 DLDP link states ..........32 track/detection module configuration ..179 active ............32 advertisement ...........
Page 223
errored frame seconds event detection ..26 signalling to GR Helper ......168 errored symbol event detection ....25 GR concepts ..........166 link monitoring ........23, 25 group remote fault detection ......... 23 monitor link group ........104 multiple groups load sharing configuration remote loopback .........
Page 224
control packet mode (BFD) ......172 roles of RRPP ring nodes ......48 demand mode (BFD) ........ 172 transit node ..........49 echo mode (BFD)........172 effect on track-VRRP collaboration ....181 static routing-track-NQA configuration example ............196 load balancing mode (VRRP) ..... 1 16 VRRP-track-NQA configuration example ..
Page 225
VRRP ............16 timers ............51 protocol troubleshooting ......... 87 restart (GR) ..........166 VLAN ............48 protocols RRPP configuration control VLAN ..........58 supported for GR (by the switch) ....169 receive control VLAN (Smart Link) ....90 domain ............ 58 release examples ..
Page 226
operating mechanismSee Smart Link operating terminology mechanism GR ............166 overview ..........89 topology ......See network topology terminology ..........90 track Smart Link configuration collaboration with application modules ..179 enabling flush messages ......94 collaboration with detection modules ..178 member ports ...........
Page 227
fiber disconnected or not connected .... 32 displaying and maintaining (IPv4) ..... 126 twisted pair ..........32 displaying and maintaining (IPv6) ....131 uplink group ............. 1 10 monitor link ..........104 load balancing mode ....... 1 16 overview ..........109 view member portSmart Link configuration in group packet format ..........
Page 228
virtual IP address and MAC address association multiple VRRP group ......137, 138 ............121 single VRRP group ........132 VRRP group creation ........ 122 VRRP interface tracking ......135 working mode ........121 VRRP load balancing mode ....... 141 VRRP configuration (IPv6) VRRP configuration examples (IPv6) group creation ........
Need help?
Do you have a question about the S9500E Series and is the answer not in the manual?
Questions and answers