H3C S5120-EI Series Configuration Manual
  1. Manuals
  2. Brands
  3. H3C Manuals
  4. Switch
  5. S5120-EI Series
  6. Configuration manual

H3C S5120-EI Series Configuration Manual

Hide thumbs Also See for S5120-EI Series:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual, Operating Manual
H3C S5120-EI Switch Series
High Availability Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release 2220
Document version: 6W100-20130810

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the S5120-EI Series and is the answer not in the manual?

Questions and answers

Related Manuals for H3C S5120-EI Series

Summary of Contents for H3C S5120-EI Series

  • Page 1 H3C S5120-EI Switch Series High Availability Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Software version: Release 2220 Document version: 6W100-20130810...
  • Page 2 Copyright © 2013, Hangzhou H3C Technologies Co., Ltd. and its licensors All rights reserved No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Hangzhou H3C Technologies Co., Ltd.
  • Page 3 The H3C S5120-EI documentation set includes 10 configuration guides, which describe the software features for the H3C S5120-EI Switch Series Release 2220, 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: Command Conventions

    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. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
  • Page 5 Layer 2 forwarding and other Layer 2 features. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. About the S5120-EI documentation set The H3C S5120-EI documentation set includes: Category Documents Purposes Marketing brochure Describe product specifications and benefits.

  • Page 6: Obtaining Documentation

    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] –...

  • Page 7: Table Of Contents

    Contents High availability overview ··········································································································································· 1   Availability requirements ·················································································································································· 1   Availability evaluation ······················································································································································ 1   High availability technologies ········································································································································· 2   Fault detection technologies ···································································································································· 2   Protection switchover technologies ························································································································· 3   Configuring Ethernet OAM ········································································································································· 4  ...
  • Page 8 CFD configuration example ·········································································································································· 27   Configuring DLDP ······················································································································································· 33   DLDP overview ································································································································································ 33   Background ···························································································································································· 33   How DLDP works ··················································································································································· 34   DLDP configuration task list ··········································································································································· 40   Configuring the duplex mode and speed of an Ethernet interface ··········································································· 40  ...
  • Page 9 How Smart Link works ·········································································································································· 98   Smart Link collaboration mechanisms ················································································································· 98   Smart Link configuration task list ·································································································································· 99   Configuring a Smart Link device ·································································································································· 99   Configuration prerequisites ·································································································································· 99   Configuring protected VLANs for a smart link group ······················································································ 100  ...

  • Page 10: High Availability Overview

    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. The following are the effective ways to improve availability: Increasing fault tolerance •...

  • Page 11: High Availability Technologies

    High availability technologies Increasing MTBF or decreasing MTTR can enhance the availability of a network. The high availability technologies described in this section meet the level 2 and level 3 high availability requirements by decreasing MTTR. High availability technologies can be classified as fault detection technologies or protection switchover technologies.

  • Page 12: Protection Switchover Technologies

    Technology Introduction Reference The track module is used to implement collaboration between different modules. The collaboration here involves three parts: the application modules, the track module, and the detection modules. These modules collaborate with one another through collaboration entries. That is, the detection modules trigger the application modules to perform certain operations through the "Configuring track"...

  • Page 13: Configuring Ethernet Oam

    Configuring Ethernet OAM Ethernet OAM overview Ethernet Operation, Administration and Maintenance (OAM) is a tool that monitors Layer 2 link status and addresses common link-related issues on the "last mile." You can use it to monitor the status of the point-to-point link between two directly connected devices.

  • Page 14: How Ethernet Oam Works

    Field Description The specific protocol being encapsulated in the Ethernet OAMPDU Subtype The value is 0x03. Flags Status information of an Ethernet OAM entity Code Type of the Ethernet OAMPDU NOTE: Throughout this document, a port with Ethernet OAM enabled is an Ethernet OAM entity or an OAM entity.
  • Page 15 Item Active Ethernet OAM mode Passive Ethernet OAM mode Transmitting Event Notification Available Available OAMPDUs Transmitting Information Available Available OAMPDUs without any TLV Transmitting Loopback Control Available Unavailable OAMPDUs Responding to Loopback Control Available—if both sides operate in Available OAMPDUs active OAM mode NOTE: Only OAM entities operating in active OAM mode can initiate OAM connections.

  • Page 16: Standards And Protocols

    A second in which errored frames appear is called an "errored frame second." Remote fault detection Information OAMPDUs are exchanged periodically among Ethernet OAM entities across established OAM connections. In a network where traffic is interrupted due to device failures or unavailability, the flag field defined in information OAMPDUs allows an Ethernet OAM entity to send error information—the critical link event type—to its peer.

  • Page 17: Configuring Basic Ethernet Oam Functions

    After the timeout timer of an Ethernet OAM connection expires, the local OAM entity ages out its connection with the peer OAM entity, causing the OAM connection to be disconnected. H3C recommends that you set the connection timeout timer to at least five times the handshake packet transmission interval, ensuring the stability of Ethernet OAM connections.

  • Page 18: Configuring Link Monitoring

    Step Command Remarks Enter system view. system-view Configure the Ethernet OAM Optional. handshake packet oam timer hello interval 1000 millisecond by default. transmission interval. Optional. Configure the Ethernet OAM oam timer keepalive interval connection timeout timer. 5000 milliseconds by default. 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.

  • Page 19: Configuring Errored Frame Seconds Event Detection

    Step Command Remarks Configure the errored Optional. oam errored-frame-period threshold frame period event threshold-value 1 by default. triggering threshold. Configuring errored frame seconds event detection IMPORTANT: Make sure the errored frame seconds triggering threshold is less than the errored frame seconds detection interval.

  • Page 20: Rejecting The Ethernet Oam Remote Loopback Request From A Remote Port

    loopback command to disable Ethernet OAM remote loopback; and Ethernet OAM connection timing out. Ethernet OAM remote loopback is only applicable to individual links. It is not applicable to link • aggregation member ports. In addition, do not assign ports where Ethernet OAM remote loopback is being performed to link aggregation groups.

  • Page 21: Displaying And Maintaining Ethernet Oam Configuration

    Step Command Remarks By default, a port does not reject Reject the Ethernet OAM the Ethernet OAM remote remote loopback request from oam loopback reject-request loopback request from a remote a remote port. port. Displaying and maintaining Ethernet OAM configuration Task Command Remarks...
  • Page 22 Configuration procedure Configure Device A: # Configure GigabitEthernet 1/0/1 to operate in passive Ethernet OAM mode and enable Ethernet OAM for it. <DeviceA> system-view [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] oam mode passive [DeviceA-GigabitEthernet1/0/1] oam enable [DeviceA-GigabitEthernet1/0/1] quit # Set the errored frame detection interval to 20 seconds and set the errored frame event triggering threshold to 10.
  • Page 23 [DeviceA] display oam critical-event Port : GigabitEthernet1/0/1 Link Status : Up Event statistic : ------------------------------------------------------------------------- Link Fault Dying Gasp Critical Event The output shows that no critical link event occurred on the link between Device A and Device B. You can use the display oam link-event command to display the statistics of Ethernet OAM link error events.

  • Page 24: Configuring Cfd

    Configuring CFD Overview Connectivity Fault Detection (CFD) is an end-to-end per-VLAN link layer OAM mechanism used for link connectivity detection, fault verification, and fault location. It conforms to IEEE 802.1ag CFM and ITU-T Y.1731. Basic CFD concepts This section explains the concepts of CFD. A maintenance domain (MD) defines the network or part of the network where CFD plays its role.
  • Page 25 An MA serves a VLAN. Packets sent by the MPs in an MA carry the relevant VLAN tag. An MP can receive packets sent by other MPs in the same MA. The level of an MA equals the level of the MD that the MA belongs to.

  • Page 26: Cfd Functions

    configured on the ports of device A through device F. Port 1 of device B is configured with the following MPs—a level 5 MIP, a level 3 inward-facing MEP, a level 2 inward-facing MEP, and a level 0 outward-facing MEP. Figure 5 CFD grading example MEP list A MEP list is a collection of configurable local MEPs and the remote MEPs to be monitored in the same...
  • Page 27 is considered faulty and a log is generated. When multiple MEPs send CCMs at the same time, the multipoint-to-multipoint link check is achieved. CCM frames are multicast frames. Similar to ping at the IP layer, LB verifies the connectivity between a source device and a target device. To implement this function, the source MEP sends loopback messages (LBMs) to the target MEP.

  • Page 28: Protocols And Standards

    the TST frame, the target MEP determines the bit errors by calculating and comparing the content of the TST frame. TST frames are unicast frames. Protocols and standards • IEEE 802.1ag, Virtual Bridged Local Area Networks Amendment 5: Connectivity Fault Management ITU-T Y.1731, OAM functions and mechanisms for Ethernet based networks •...

  • Page 29: Configuring Basic Cfd Settings

    The port is configured as a MIP or an inward-facing MEP that can still receive and send CFD • messages except CCM messages. For more information about the spanning tree feature, see Layer 2—LAN Switching Configuration Guide. Configuring basic CFD settings This section provides procedures for configuring basic CFD settings.

  • Page 30: Configuring Meps

    Service instance without the MD name, which takes effect in only CFD IEEE 802.1ag. • You can create either type of service instance as needed. Creating a service instance with the MD name To create a service instance with the MD name, create the MD and MA for the service instance first. To configure a service instance with the MD name: Step Command...

  • Page 31: Configuring Mip Generation Rules

    Step Command Remarks cfd mep mep-id service-instance Create a MEP. By default, no MEP is created. instance-id { inbound | outbound } cfd mep service-instance Enable the MEP. By default, the MEP is disabled. instance-id mep mep-id enable 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.

  • Page 32: Configuring Lb On Meps

    Table 9 Relationship between the interval field value in the CCM message, the interval between CCM messages, and the timeout time of the remote MEP The interval field value in The interval between CCM The timeout time of the remote MEP the CCM message messages 1 second...

  • Page 33: Configuring Ais

    TTL field in the LTM frames set to the maximum value 255. Based on the LTRs that the MIPs return, the fault source can be located. To configure LT on MEPs: Step Command Remarks cfd linktrace service-instance Find the path between a source instance-id mep mep-id { target-mep Available in any view.

  • Page 34: Configuring One-Way Dm

    Step Command Remarks Enter system view. system-view cfd slm service-instance instance-id mep mep-id { target-mac Configure LM. By default, LM is disabled. mac-address | target-mep target-mep-id } [ number number ] Configuring one-way DM The one-way DM function measures the one-way frame delay between two MEPs, and monitors and manages the link transmission performance.

  • Page 35: Configuring Tst

    Configuring TST The TST function detects bit errors on a link, and monitors and manages the link transmission performance. The TST function takes effect only in CFD IEEE 802.1ag. To configure TST: Step Command Remarks Enter system view. system-view cfd tst service-instance instance-id mep mep-id { target-mac By default, TST is disabled.

  • Page 36: Cfd Configuration Example

    Task Command Remarks display cfd linktrace-reply Display LTR information received [ service-instance instance-id [ mep Available in any view by a MEP. mep-id ] ] [ | { begin | exclude | include } regular-expression ] display cfd remote-mep Display the information of a remote service-instance instance-id mep Available in any view MEP.
  • Page 37 The MIPs of MD_B are designed on Device C, and are configured on all ports. You should configure • the MIP generation rule as default. Configure CC to monitor the connectivity among all the MEPs in MD_A and MD_B. Configure LB to •...
  • Page 38 [DeviceB] cfd md MD_B level 3 [DeviceB] cfd ma MA_B md MD_B vlan 100 [DeviceB] cfd service-instance 2 md MD_B ma MA_B Configure Device D in the same way as Device B. # Create MD_B (level 3) on Device C, create MA_B that serves VLAN 100, in MD_B, and then create service instance 2 for MD_B and MA_B.

  • Page 39: Verifying The Configuration

    [DeviceB] cfd mip-rule explicit service-instance 1 # Configure the MIP generation rule in service instance 2 on Device C as default. [DeviceC] cfd mip-rule default service-instance 2 Configure CC: # On Device A, enable the sending of CCM frames for MEP 1001 in service instance 1 on GigabitEthernet 1/0/1.
  • Page 40 Send:5 Received:5 Lost:0 After the whole network status is obtained with the CC function, use the LT function to identify the paths between source and target MEPs and to locate faults. Verify the LT function: # Identify the path between MEP 1001 and MEP 5001 in service instance 1 on Device A. [DeviceA] cfd linktrace service-instance 1 mep 1001 target-mep 5001 Linktrace to MEP 5001 with the sequence number 1001-43462 MAC Address...
  • Page 41 # Test the two-way frame delay from MEP 1001 to MEP 4002 in service instance 1 on Device A. [DeviceA] cfd dm two-way service-instance 1 mep 1001 target-mep 4002 Frame delay: Reply from 0010-FC00-6514: 10ms Reply from 0010-FC00-6514: 9ms Reply from 0010-FC00-6514: 11ms Reply from 0010-FC00-6514: 5ms Reply from 0010-FC00-6514: 5ms Average: 8ms...

  • Page 42: Configuring Dldp

    Configuring DLDP DLDP 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.

  • Page 43: How Dldp Works

    performs operations such as identifying peer devices, detecting unidirectional links, and shutting down unreachable ports. The auto-negotiation mechanism and DLDP work together to make sure that physical/logical unidirectional links are detected and shut down, and to prevent failure of other protocols such as STP.
  • Page 44 DLDP timer Description This timer is set to 10 seconds. It is triggered when a device transits to the Probe state or when 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 set to unidirectional and the device transits to the Disable state.
  • Page 45 Table 12 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 neighbor entry ages out Entry timer expires expires Normal DLDP mode Enhanced DLDP mode...
  • Page 46 Non-authentication: • 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 where the two fields conflict with the corresponding local configuration. Simple authentication: •...
  • Page 47 Packet type Processing procedure If the corresponding neighbor entry already exists, resets the Entry timer and transits to Probe state. If the corresponding neighbor entry does not exist, creates the neighbor entry, triggers the Entry timer, and transits to Probe Normal Retrieves the state.
  • Page 48 Packet type Processing procedure local port operates If yes and the local port is not in Disable state, sets the state of in Enhanced mode the corresponding neighbor to unidirectional, and then checks the state of other neighbors. If all the neighbors are unidirectional, transitions the local port to the Disable state.

  • Page 49: Dldp Configuration Task List

    Table 17 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. It transits to Two way state or Unidirectional state after the probe operation finishes.

  • Page 50: Enabling Dldp

    STP convergence time. If the interval is too long, STP loops may occur before unidirectional links are detected and shut down. If the interval is too short, the number of advertisement packets will increase. H3C recommends that you use the default interval in most cases.

  • Page 51: Setting The Delaydown Timer

    Instead, the DLDP state machine generates log and traps to prompt you to manually shut down unidirectional link ports with the shutdown command. H3C recommends that you do as prompted. Then the DLDP state machine transits to the Disable state.

  • Page 52: Configuring Dldp Authentication

    If the device is busy, or the CPU usage is high, normal links may be treated as unidirectional links. In this case, you can set the port shutdown mode to manual mode to alleviate the impact caused by false unidirectional link report. To set port shutdown mode: Step Command...

  • Page 53: Displaying And Maintaining Dldp

    Step Command Enter system view. system-view Reset DLDP state. dldp reset Resetting DLDP state in interface view/port group view Resetting DLDP state in interface view or port group view applies to the current port or all ports in the port group.
  • Page 54 Figure 9 Network diagram Configuration procedure Configure Device A: # Enable DLDP globally. <DeviceA> system-view [DeviceA] dldp enable # Configure GigabitEthernet 1/0/49 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port. [DeviceA] interface gigabitethernet 1/0/49 [DeviceA-GigabitEthernet1/0/49] duplex full [DeviceA-GigabitEthernet1/0/49] speed 1000 [DeviceA-GigabitEthernet1/0/49] dldp enable...

  • Page 55: Verify The Configuration

    # Enable DLDP globally. <DeviceB> system-view [DeviceB] dldp enable # Configure GigabitEthernet 1/0/49 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it. [DeviceB] interface gigabitethernet 1/0/49 [DeviceB-GigabitEthernet1/0/49] duplex full [DeviceB-GigabitEthernet1/0/49] speed 1000 [DeviceB-GigabitEthernet1/0/49] dldp enable [DeviceB-GigabitEthernet1/0/49] quit # Configure GigabitEthernet 1/0/50 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.
  • Page 56 Neighbor mac address : 0023-8956-3600 Neighbor port index : 60 Neighbor state : two way Neighbor aged time : 12 The output shows 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.

  • Page 57: Manually Shutting Down Unidirectional Links

    %Jan 18 17:47:35:894 2013 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/50 link status is UP. The output shows that the link status of both GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50 is now up. Manually shutting down unidirectional links Network requirements • As shown in Figure 10, Device A and Device B are connected with two fiber pairs.
  • Page 58 # Configure GigabitEthernet 1/0/50 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port. [DeviceA] interface gigabitethernet 1/0/50 [DeviceA-GigabitEthernet1/0/50] duplex full [DeviceA-GigabitEthernet1/0/50] speed 1000 [DeviceA-GigabitEthernet1/0/50] dldp enable [DeviceA-GigabitEthernet1/0/50] quit # Set the DLDP mode to enhanced. [DeviceA] dldp work-mode enhance # Set the port shutdown mode to manual.
  • Page 59 Interface GigabitEthernet1/0/49 DLDP port state : advertisement DLDP link state : up The neighbor number of the port is 1. Neighbor mac address : 0023-8956-3600 Neighbor port index : 59 Neighbor state : two way Neighbor aged time : 11 Interface GigabitEthernet1/0/50 DLDP port state : advertisement DLDP link state : up...

  • Page 60: Troubleshooting Dldp

    <DeviceA> system-view [DeviceA] interface gigabitethernet 1/0/49 [DeviceA-GigabitEthernet1/0/49] shutdown %Jan 18 18:16:12:044 2013 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/49 link status is DOWN. [DeviceA-GigabitEthernet1/0/49] quit [DeviceA] interface gigabitethernet 1/0/50 [DeviceA-GigabitEthernet1/0/50] shutdown %Jan 18 18:18:03:583 2013 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/50 link status is DOWN. The output shows that the link status of both GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50 is down.

  • Page 61: Configuring Rrpp

    Configuring RRPP RRPP overview The Rapid Ring Protection Protocol (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. Background Metropolitan area networks (MANs) and enterprise networks usually use the ring structure to improve reliability.
  • Page 62 RRPP ring A ring-shaped Ethernet topology is called an "RRPP ring". RRPP rings fall into two types: primary ring and subring. You can configure a ring as either the primary ring or a subring by specifying its ring level. The primary ring is of level 0, and a subring is of level 1.

  • Page 63: Rrppdus

    Primary port and secondary port Each master node or transit node has two ports connected to an RRPP ring, one serving as the primary port and the other serving as the secondary port. You can determine the port’s role. In terms of functionality, the primary port and the secondary port of a master node have the following differences: The primary port and the secondary port are designed to play the role of sending and receiving loop-detect packets respectively.

  • Page 64: Rrpp Timers

    Type Description The master node initiates Common-Flush-FDB packets to instruct the transit nodes Common-Flush-FDB to update their own MAC entries and ARP/ND entries when an RRPP ring transits to Disconnect state. FDB stands for Forwarding Database. The master node initiates Complete-Flush-FDB packets to instruct the transit nodes Complete-Flush-FDB to update their own MAC entries and ARP/ND entries and release blocked ports from being blocked temporarily when an RRPP ring transits to Health state.
  • Page 65 VLANs and sending Common-Flush-FDB packets to instruct all transit nodes to update their own MAC entries and ARP/ND entries. Link down alarm mechanism The transit node, the edge node or the assistant-edge node sends Link-Down packets to the master node immediately when they find any of its own ports belonging to an RRPP domain are down.

  • Page 66: Typical Rrpp Networking

    packets frequently. If more subrings are configured or if load balancing is configured for multiple domains, Device B and Device C will send or receive a mass of Edge-Hello packets. To reduce Edge-Hello traffic, you can assign Ring 2 and Ring 3 to an RRPP ring group configured on the edge node Device B and assign Ring 2 and Ring 3 to an RRPP ring group configured on Device C.
  • Page 67 Figure 13 Schematic diagram for a tangent-ring network Intersecting rings As shown in Figure 14, two or more rings are in the network topology and two common nodes exist between rings. You only need to define an RRPP domain and configure one ring as the primary ring and the other rings as subrings.
  • Page 68 Figure 15 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 16, 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.

  • Page 69: Protocols And Standards

    Figure 17 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.

  • Page 70: Creating An Rrpp Domain

    Task Remarks Optional. Configuring an RRPP ring group Perform this task on the edge node and assistant-edge node in the RRPP domain. NOTE: RRPP does not have an auto election mechanism, so you must configure each node in the ring network •...

  • Page 71: Configuration Procedure

    Configuration procedure To configure control VLANs: Step Command Enter system view. system-view Enter RRPP domain view. rrpp domain domain-id Configure the primary control VLAN for the RRPP control-vlan vlan-id domain. Configuring protected VLANs Before configuring RRPP rings in an RRPP domain, configure the same protected VLANs for all nodes in the RRPP domain first.

  • Page 72: Configuring Rrpp Rings

    Step Command Remarks Optional. Available in any view. Display the currently activated display stp region-configuration [ | The command output includes configuration information of { begin | exclude | include } VLAN-to-instance mappings. the MST region. regular-expression ] For more information about the command, see Layer 2—LAN Switching Command Reference.

  • Page 73: Configuring Rrpp Nodes

    Configuration procedure To configure RRPP ports: Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregation interface view. Configure the link type of the By default, the link type of an port link-type trunk interface as trunk.

  • Page 74: Activating An Rrpp Domain

    Step Command Specify the current device as a transit node of the ring ring-id node-mode transit [ primary-port ring, and specify the primary port and the interface-type interface-number ] [ secondary-port secondary port. interface-type interface-number ] level level-value Specifying an edge node When configuring an edge node, you must first configure the primary ring before configuring the subrings.

  • Page 75: 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: •...

  • Page 76: Configuration Restrictions And Guidelines

    Configuration restrictions and guidelines You can assign a subring to only one RRPP ring group. Make sure the RRPP ring group configured • on the edge node and the RRPP ring group configured on the assistant-edge node contain the same subrings.

  • Page 77: Rrpp Configuration Examples

    RRPP configuration examples Single ring configuration example Networking requirements As shown in Figure Device A, Device B, Device C, and Device D form RRPP domain 1. Specify the primary control VLAN • of RRPP domain 1 as VLAN 4092. RRPP domain 1 protects VLANs 1 through 30. •...
  • Page 78 [DeviceA-GigabitEthernet1/0/1] qos trust dot1p [DeviceA-GigabitEthernet1/0/1] port link-type trunk [DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [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] qos trust dot1p [DeviceA-GigabitEthernet1/0/2] port link-type trunk [DeviceA-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/2] quit # Create RRPP domain 1.

  • Page 79: Intersecting Ring Configuration Example

    [DeviceB-GigabitEthernet1/0/2] port link-type trunk [DeviceB-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceB-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 MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceB] rrpp domain 1 [DeviceB-rrpp-domain1] control-vlan 4092 [DeviceB-rrpp-domain1] protected-vlan reference-instance 1...
  • Page 80 Figure 19 Network diagram Configuration procedure Configure Device A: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. <DeviceA> system-view [DeviceA] vlan 1 to 30 [DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 1 to 30 [DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/1 and...
  • Page 81 [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 primary port and GigabitEthernet 1/0/2 as the secondary port, and enable ring 1. [DeviceA-rrpp-domain1] ring 1 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0 [DeviceA-rrpp-domain1] ring 1 enable [DeviceA-rrpp-domain1] quit...
  • Page 82 # Configure Device B as a 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 # Configure Device B as the edge node of subring 2, with GigabitEthernet 1/0/3 as the edge port, and enable ring 2.
  • Page 83 [DeviceC] rrpp domain 1 [DeviceC-rrpp-domain1] control-vlan 4092 [DeviceC-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device C as a 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. [DeviceC-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0 [DeviceC-rrpp-domain1] ring 1 enable...
  • Page 84 # Configure Device D 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. [DeviceD-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0 [DeviceD-rrpp-domain1] ring 1 enable [DeviceD-rrpp-domain1] quit # Enable RRPP.

  • Page 85: Dual Homed Rings Configuration Example

    [DeviceE] rrpp enable Verify the configuration: Use the display command to view RRPP configuration and operational information on each device. Dual homed rings configuration example Networking requirements As shown in Figure Device A through Device H form RRPP domain 1. Specify the primary control VLAN of RRPP domain •...
  • Page 86 Figure 20 Network diagram Configuration procedure Configure Device A: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. <DeviceA> system-view [DeviceA] vlan 1 to 30 [DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 1 to 30 [DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/1 through...
  • Page 87 [DeviceA] interface gigabitethernet 1/0/3 [DeviceA-GigabitEthernet1/0/3] undo link-delay [DeviceA-GigabitEthernet1/0/3] undo stp enable [DeviceA-GigabitEthernet1/0/3] qos trust dot1p [DeviceA-GigabitEthernet1/0/3] port link-type trunk [DeviceA-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/3] quit [DeviceA] interface gigabitethernet 1/0/4 [DeviceA-GigabitEthernet1/0/4] undo link-delay [DeviceA-GigabitEthernet1/0/4] undo stp enable [DeviceA-GigabitEthernet1/0/4] qos trust dot1p [DeviceA-GigabitEthernet1/0/4] port link-type trunk [DeviceA-GigabitEthernet1/0/4] port trunk permit vlan 1 to 30...
  • Page 88 to 802.1p priority. Configure the four ports as trunk ports, and assign them to VLANs 1 through [DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] undo link-delay [DeviceB-GigabitEthernet1/0/1] undo stp enable [DeviceB-GigabitEthernet1/0/1] qos trust dot1p [DeviceB-GigabitEthernet1/0/1] port link-type trunk [DeviceB-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/1] quit [DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] undo link-delay...
  • Page 89 [DeviceB-rrpp-domain1] ring 3 node-mode assistant-edge edge-port gigabitethernet 1/0/3 [DeviceB-rrpp-domain1] ring 3 enable [DeviceB-rrpp-domain1] quit # Enable RRPP. [DeviceB] rrpp enable Configure Device C: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration.
  • Page 90 # Create RRPP domain 1. Configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceC] rrpp domain 1 [DeviceC-rrpp-domain1] control-vlan 4092 [DeviceC-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device C 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.
  • Page 91 [DeviceD-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/2] quit [DeviceD] interface gigabitethernet 1/0/3 [DeviceD-GigabitEthernet1/0/3] undo link-delay [DeviceD-GigabitEthernet1/0/3] undo stp enable [DeviceD-GigabitEthernet1/0/3] qos trust dot1p [DeviceD-GigabitEthernet1/0/3] port link-type trunk [DeviceD-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/3] quit [DeviceD] interface gigabitethernet 1/0/4 [DeviceD-GigabitEthernet1/0/4] undo link-delay [DeviceD-GigabitEthernet1/0/4] undo stp enable [DeviceD-GigabitEthernet1/0/4] qos trust dot1p...
  • Page 92 # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2, disable the spanning tree feature, and set the trusted packet priority type to 802.1p priority. Configure the two ports as trunk ports, and assign them to VLANs 1 through [DeviceE] interface gigabitethernet 1/0/1 [DeviceE-GigabitEthernet1/0/1] undo link-delay [DeviceE-GigabitEthernet1/0/1] undo stp enable...
  • Page 93 [DeviceF-GigabitEthernet1/0/1] port link-type trunk [DeviceF-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceF-GigabitEthernet1/0/1] quit [DeviceF] interface gigabitethernet 1/0/2 [DeviceF-GigabitEthernet1/0/2] undo link-delay [DeviceF-GigabitEthernet1/0/2] undo stp enable [DeviceF-GigabitEthernet1/0/2] qos trust dot1p [DeviceF-GigabitEthernet1/0/2] port link-type trunk [DeviceF-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceF-GigabitEthernet1/0/2] quit # Create RRPP domain 1.
  • Page 94 [DeviceG-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceG-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 MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceG] rrpp domain 1 [DeviceG-rrpp-domain1] control-vlan 4092 [DeviceG-rrpp-domain1] protected-vlan reference-instance 1...

  • Page 95: Intersecting-Ring Load Balancing Configuration Example

    # Configure Device H as the master node of subring 5, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port, and enable subring 5. [DeviceH-rrpp-domain1] ring 5 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 1 [DeviceH-rrpp-domain1] ring 5 enable [DeviceH-rrpp-domain1] quit # Enable RRPP.
  • Page 96 Figure 21 Network diagram Configuration procedure Configure Device A: # Create VLANs 1 and 2, map VLAN 1 to MSTI 1 and VLAN 2 to MSTI 2, and activate MST region configuration. <DeviceA> system-view [DeviceA] vlan 1 to 2 [DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 1 [DeviceA-mst-region] instance 2 vlan 2 [DeviceA-mst-region] active region-configuration...
  • Page 97 [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 primary port and GigabitEthernet 1/0/2 as the secondary port, and enable ring 1.
  • Page 98 [DeviceB-GigabitEthernet1/0/2] undo link-delay [DeviceB-GigabitEthernet1/0/2] undo stp enable [DeviceB-GigabitEthernet1/0/2] qos trust dot1p [DeviceB-GigabitEthernet1/0/2] port link-type trunk [DeviceB-GigabitEthernet1/0/2] port trunk permit vlan 1 2 [DeviceB-GigabitEthernet1/0/2] quit # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/3, disable the spanning tree feature, and set the trusted packet priority type to 802.1p priority. Configure the port as a trunk port, and assign it to VLAN 2.
  • Page 99 # 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 GigabitEthernet 1/0/3 as the edge port, and enable subring 2.
  • Page 100 [DeviceC-GigabitEthernet1/0/3] qos trust dot1p [DeviceC-GigabitEthernet1/0/3] port link-type trunk [DeviceC-GigabitEthernet1/0/3] undo port trunk permit vlan 1 [DeviceC-GigabitEthernet1/0/3] port trunk permit vlan 2 [DeviceC-GigabitEthernet1/0/3] port trunk pvid vlan 2 [DeviceC-GigabitEthernet1/0/3] quit # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/4, disable the spanning tree feature, and set the trusted packet priority type to 802.1p priority.
  • Page 101 [DeviceC] rrpp enable Configure Device D: # Create VLANs 1 and 2, map VLAN 1 to MSTI 1 and VLAN 2 to MSTI 2, and activate MST region configuration. <DeviceD> system-view [DeviceD] vlan 1 to 2 [DeviceD] stp region-configuration [DeviceD-mst-region] instance 1 vlan 1 [DeviceD-mst-region] instance 2 vlan 2 [DeviceD-mst-region] active region-configuration [DeviceD-mst-region] quit...
  • Page 102 [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 # Enable RRPP. [DeviceD] rrpp enable Configure Device E: # Create VLAN 2, map VLAN 2 to MSTI 2, and activate MST region configuration. <DeviceE>...
  • Page 103 # Enable RRPP. [DeviceE] rrpp enable Configure Device F: # Create VLAN 1, map VLAN 1 to MSTI 1, and activate MST region configuration. <DeviceF> system-view [DeviceF] vlan 1 [DeviceF-vlan1] quit [DeviceF] stp region-configuration [DeviceF-mst-region] instance 1 vlan 1 [DeviceF-mst-region] active region-configuration [DeviceF-mst-region] quit # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2, disable the spanning tree feature, and set the trusted packet priority type...

  • Page 104: Troubleshooting

    # Create RRPP ring group 1 on Device C, and add subrings 2 and 3 to the RRPP ring group. [DeviceC] rrpp ring-group 1 [DeviceC-rrpp-ring-group1] domain 2 ring 2 [DeviceC-rrpp-ring-group1] domain 1 ring 3 Verify the configuration: 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...

  • Page 105: Configuring Smart Link

    Configuring Smart Link Smart Link overview Background To avoid single-point failures and guarantee network reliability, downstream devices are usually dual-homed to upstream devices, as shown in Figure Figure 22 Diagram for a dual uplink network To remove network loops on a dual-homed network, you can use a spanning tree protocol or the Rapid Ring Protection Protocol (RRPP).

  • Page 106: Terminology

    Dedicated to dual uplink networks • • Subsecond convergence Easy to configure • Terminology Smart link group A smart link group consists of only two member ports: the master and the slave ports. At a time, only one port is active for forwarding, and the other port is blocked and in standby state. When link failure occurs on the active port due to port shutdown or presence of unidirectional link, the standby port becomes active to take over and the original active port transits to the blocked state.

  • Page 107: How Smart Link Works

    How Smart Link works Link backup mechanism As shown in Figure 22, the link on Port1 of Device C is the master link, and the link on Port2 of Device C is the slave link. Typically, Port1 is in forwarding state, and Port2 is in standby state. When the master link fails, Port2 takes over to forward traffic and Port1 is blocked and placed in standby state.

  • Page 108: Smart Link Configuration Task List

    function to monitor the uplink ports of the upstream devices. Monitor Link adapts the up/down state of downlink ports to the up/down state of uplink ports, triggering Smart Link to perform link switchover on the downstream device. For more information about Monitor Link, see "Configuring Monitor Link."...

  • Page 109: Configuring Protected Vlans For A Smart Link Group

    Disable the spanning tree feature and RRPP on the ports that you want to add to the smart link group, • and make sure the ports are not member ports of any aggregation group. NOTE: A loop may occur on the network during the time when the spanning tree feature is disabled but Smart Link has not yet taken effect on a port.

  • Page 110: Configuring Member Ports For A Smart Link Group

    Step Command Remarks Configure protected VLANs protected-vlan reference-instance By default, no protected VLAN is for the smart link group. instance-id-list configured for a smart link group. 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.

  • Page 111: Enabling The Sending Of Flush Messages

    Enabling the sending of flush messages The control VLAN configured for a smart link group must be different from that configured for any other smart link group. Make sure the configured control VLAN already exists, and assign the smart link group member ports to the control VLAN.

  • Page 112: Configuring An Associated Device

    Configuring an associated device Configuration prerequisites Disable the spanning tree feature on the associated device’s ports that connect to the member ports of the smart link group; otherwise, the ports will discard flush messages when they are not in the forwarding state in case of a topology change.

  • Page 113: Smart Link Configuration Examples

    Task Command Remarks Clear the statistics about flush reset smart-link statistics Available in user view messages. Smart Link configuration examples Single smart link group configuration example Network requirements As shown in Figure 23, Device C and Device D are smart link devices, and Device A, Device B, and Device E are associated devices.
  • Page 114 [DeviceC-GigabitEthernet1/0/1] undo stp enable [DeviceC-GigabitEthernet1/0/1] port link-type trunk [DeviceC-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/1] quit [DeviceC] interface gigabitethernet 1/0/2 [DeviceC-GigabitEthernet1/0/2] shutdown [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 VLANs mapped to MSTI 1 as the protected VLANs.
  • Page 115 [DeviceD-GigabitEthernet1/0/2] shutdown [DeviceD-GigabitEthernet1/0/2] undo stp enable [DeviceD-GigabitEthernet1/0/2] port link-type trunk [DeviceD-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/2] quit # Create smart link group 1, and configure all VLANs mapped to MSTI 1 as the protected VLANs. [DeviceD] smart-link group 1 [DeviceD-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 116 [DeviceB] interface gigabitethernet 1/0/3 [DeviceB-GigabitEthernet1/0/3] port link-type trunk [DeviceB-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/3] undo stp enable [DeviceB-GigabitEthernet1/0/3] smart-link flush enable control-vlan 10 [DeviceB-GigabitEthernet1/0/3] quit Configure Device E: # Create VLANs 1 through 30. <DeviceE> system-view [DeviceE] vlan 1 to 30 # Configure GigabitEthernet 1/0/1 as a trunk port, and assign it to VLANs 1 through 30.

  • Page 117: 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 control-vlan 10 20 [DeviceA-GigabitEthernet1/0/2] quit Verify the configuration: You can use the display smart-link group command to display the smart link group configuration on a device.
  • Page 118 Figure 24 Network diagram Configuration procedure Configure Device C: # Create VLAN 1 through VLAN 200. Map VLANs 1 through 100 to MSTI 1. Map VLANs 101 through 200 to MSTI 2, and activate MST region configuration. <DeviceC> system-view [DeviceC] vlan 1 to 200 [DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 1 to 100 [DeviceC-mst-region] instance 2 vlan 101 to 200...
  • Page 119 # Enable role preemption in smart link group 1, enable flush message sending, and configure VLAN 10 as the transmit control VLAN. [DeviceC-smlk-group1] preemption mode role [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.
  • Page 120 # Create VLAN 1 through VLAN 200. <DeviceD> system-view [DeviceD] vlan 1 to 200 # Configure GigabitEthernet 1/0/1 as a trunk port and assign it to VLANs 1 through 200. Enable flush message receiving and configure VLAN 10 and VLAN 110 as the receive control VLANs on GigabitEthernet 1/0/1.

  • Page 121: Smart Link And Cfd Collaboration Configuration Example

    Protected VLAN: Reference Instance 1 Member Role State Flush-count Last-flush-time ----------------------------------------------------------------------------- GigabitEthernet1/0/1 MASTER ACTVIE 16:37:20 2013/02/21 GigabitEthernet1/0/2 SLAVE STANDBY 17:45:20 2013/02/21 Smart link group 2 information: Device ID: 000f-e23d-5af0 Preemption mode: ROLE Preemption delay: 1(s) Control VLAN: 110 Protected VLAN: Reference Instance 2 Member Role State...
  • Page 122 Figure 25 Network diagram Configuration procedure Configure 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 and configure VLAN 10 and VLAN 110 as the receive control VLANs on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2.
  • Page 123 [DeviceA-GigabitEthernet1/0/1] cfd mep 1002 service-instance 1 outbound [DeviceA-GigabitEthernet1/0/1] cfd mep service-instance 1 mep 1002 enable [DeviceA-GigabitEthernet1/0/1] cfd cc service-instance 1 mep 1002 enable [DeviceA-GigabitEthernet1/0/1] quit # Create MA MA_B for the MD and configure the MA to serve VLAN 110, and create service instance 2 for the MD and MA.
  • Page 124 # Shut down GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2, disable the spanning tree feature on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 separately, configure the ports as trunk ports, and assign them to VLAN 1 through VLAN 200. [DeviceC] interface gigabitethernet 1/0/1 [DeviceC-GigabitEthernet1/0/1] shutdown [DeviceC-GigabitEthernet1/0/1] undo stp enable [DeviceC-GigabitEthernet1/0/1] port link-type trunk [DeviceC-GigabitEthernet1/0/1] port trunk permit vlan 1 to 200...
  • Page 125 [DeviceC] cfd service-instance 1 md MD ma MA_A # Create a MEP list in service instance 1, create and enable outward-facing MEP 1001, and enable CCM sending in service instance 1 on GigabitEthernet 1/0/1. [DeviceC] cfd meplist 1001 1002 service-instance 1 [DeviceC] interface gigabitethernet 1/0/1 [DeviceC-GigabitEthernet1/0/1] cfd mep 1001 service-instance 1 outbound [DeviceC-GigabitEthernet1/0/1] cfd mep service-instance 1 mep 1001 enable...
  • Page 126 # Configure GigabitEthernet 1/0/2 as a trunk port and assign it to VLANs 1 through 200. Disable the spanning tree feature and enable flush message receiving on it, and configure VLAN 10 and VLAN 110 as the receive control VLANs. [DeviceD] interface gigabitethernet 1/0/2 [DeviceD-GigabitEthernet1/0/2] port link-type trunk [DeviceD-GigabitEthernet1/0/2] port trunk permit vlan 1 to 200...

  • Page 127: Configuring Monitor Link

    Configuring Monitor Link Monitor Link 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 128: How Monitor Link Works

    When any uplink port goes up, the monitor link group goes up and brings up all the downlink ports. H3C does not recommend manually shutting down or bringing up the downlink ports in a monitor link group.

  • Page 129: Displaying And Maintaining Monitor Link

    Step Command Enter system view. system-view Enter monitor link group view. monitor-link group group-id port interface-type interface-number { uplink | Configure member ports for the monitor link group. downlink } In interface view To configure member ports for a monitor link group in interface view: Step Command Enter system view.
  • Page 130 Figure 27 Network diagram Configuration procedure Configure Device C: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate MST region configuration. <DeviceC> system-view [DeviceC] vlan 1 to 30 [DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 1 to 30 [DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit # Disable the spanning tree feature on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2...
  • Page 131 Configure Device A: # Create VLANs 1 through 30. <DeviceA> system-view [DeviceA] vlan 1 to 30 # Configure GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 as trunk ports, assign them to VLANs 1 through 30, and enable flush message receiving on them. [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] port link-type trunk [DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30...
  • Page 132 # Configure GigabitEthernet 1/0/1 as a trunk port, assign it to VLANs 1 through 30, and enable flush message receiving on it. [DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] port link-type trunk [DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/1] smart-link flush enable [DeviceD-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 as a trunk port, assign it to VLANs 1 through 30, disable the spanning tree feature, and enable flush message receiving on it.

  • Page 133: Configuring Track

    Configuring track Track overview Introduction to collaboration The track module works between application and detection modules, as shown in Figure 28. It shields the differences between various detection modules from application modules. Collaboration is enabled after you associate the track module with a detection module and an application module.

  • Page 134: Collaboration Application Example

    • • Interface management module Collaboration between the track module and an application module After being associated with an application module, when the status of the track entry changes, the track module notifies the application module, which then takes proper actions. Only static routing can be associated with the track module.

  • Page 135: Associating Track With Interface Management

    If the consecutive failures reach the specified threshold, the NQA module tells the track module that • the tracked object malfunctions. Then the track module sets the track entry to the Negative state. If the specified threshold is not reached, the NQA module tells the track module that the tracked •...

  • Page 136: Associating The Track Module With An Application Module

    Step Command Remarks Create a track entry, associate it with the interface management module to monitor the physical status of an interface, and specify the delay time for the track module to notify the associated application module when the track entry status changes: track track-entry-number interface interface-type interface-number [ delay...

  • Page 137: Displaying And Maintaining Track Entries

    The Invalid state of the track entry shows that the accessibility of the next hop of the static route is • unknown and that the static route is valid. If a static route needs route recursion, the associated track entry must monitor the next hop of the recursive route instead of that of the static route;...
  • Page 138 Similarly, Switch D is the default gateway of the hosts in segment 30.1.1.0/24. Two static routes to 20.1.1.0/24 exist on Switch D, with the next hop being Switch B and Switch C, respectively. These two static routes back up each other as follows: •...
  • Page 139 [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. [SwitchA-nqa-admin-test-icmp-echo] frequency 100 # Configure reaction entry 1, specifying that five consecutive probe failures trigger the track module. [SwitchA-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only [SwitchA-nqa-admin-test-icmp-echo] quit # Start the NQA test.
  • Page 140 [SwitchD-nqa-admin-test-icmp-echo] frequency 100 # Configure reaction entry 1, specifying that five consecutive probe failures trigger the track module. [SwitchD-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only [SwitchD-nqa-admin-test-icmp-echo] quit # Start the NQA test. [SwitchD] nqa schedule admin test start-time now lifetime forever # 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).
  • Page 141 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 Cost NextHop Interface 10.1.1.0/24...
  • Page 142 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/1/2 ms...

  • Page 143: Index

    Index A C D E H M O R S T Displaying and maintaining Smart Link,103 Displaying and maintaining track entries,128 Activating an RRPP domain,65 DLDP configuration examples,44 Associating the track module with a detection DLDP configuration task list,40 module,125 DLDP overview,33 Associating the track module with an application...
  • Page 144 Troubleshooting DLDP,51...

Table of Contents