HP 5130 EI Switch Series
Part number: 5998-5475a
Software version: Release 31xx
Document version: 6W100-20150731

Advertising

   Related Manuals for HP 5130 EI Series

   Summary of Contents for HP 5130 EI Series

  • Page 1: High Availability, Configuration Guide

    HP 5130 EI Switch Series High Availability Configuration Guide Part number: 5998-5475a Software version: Release 31xx Document version: 6W100-20150731...

  • Page 2

    The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.

  • Page 3: Table Of Contents

    Contents Configuring Ethernet OAM ········································································································································· 1   Overview ············································································································································································ 1   Major functions of Ethernet OAM ·························································································································· 1   Ethernet OAMPDUs ·················································································································································· 1   How Ethernet OAM works ······································································································································ 1   Protocols and standards ·········································································································································· 3   Ethernet OAM configuration task list ······························································································································ 4  ...

  • Page 4: Table Of Contents

    CFD configuration example ·········································································································································· 26   Configuring DLDP ······················································································································································· 32   Overview ········································································································································································· 32   Basic concepts ······················································································································································· 33   How DLDP works ··················································································································································· 34   Configuration restrictions and guidelines ···················································································································· 36   DLDP configuration task list ··········································································································································· 36   Enabling DLDP ································································································································································...

  • Page 5: Table Of Contents

    Static routing-Track-NQA collaboration configuration example ···································································· 136   Static routing-Track-BFD collaboration configuration example ······································································· 141   Smart Link-Track-CFD collaboration configuration example ··········································································· 144   Support and other resources ·································································································································· 145   Contacting HP ······························································································································································ 145   Subscription service ············································································································································ 145  ...

  • Page 6

    Related information ······················································································································································ 145   Documents ···························································································································································· 145   Websites ······························································································································································· 145   Conventions ·································································································································································· 146   Index ········································································································································································ 148  ...

  • Page 7: Configuring Ethernet Oam

    Configuring 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." Ethernet OAM improves Ethernet management and maintainability. You can use it to monitor the status of the point-to-point link between two directly connected devices.

  • Page 8

    Ethernet OAM connection establishment Ethernet OAM connection is the basis of all the other Ethernet OAM functions. OAM connection establishment is also known as the Discovery phase, where an Ethernet OAM entity discovers the remote OAM entity to establish a session. In this phase, two connected OAM entities exchange Information OAMPDUs to advertise their OAM configuration and capabilities to each other for a comparison.

  • Page 9: Protocols And Standards

    Ethernet OAM link events Description An errored frame event occurs when the number of detected error frames in Errored frame event the detection window (specified detection interval) exceeds the predefined threshold. An errored frame period event occurs when the number of frame errors in Errored frame period event the detection window (specified number of received frames) exceeds the predefined threshold.

  • Page 10: Ethernet Oam Configuration Task List

    Ethernet OAM configuration task list Tasks at a glance (Required.) Configuring basic Ethernet OAM functions (Optional.) Configuring the Ethernet OAM connection detection timers (Optional.) Configuring link monitoring • Configuring errored symbol event detection • Configuring errored frame event detection • Configuring errored frame period event detection •...

  • Page 11: Configuring Link Monitoring

    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 disconnect. To keep the Ethernet OAM connections stable, HP recommends that you set the connection timeout timer to be at least five times the handshake packet transmission interval.

  • Page 12: Configuring Errored Frame Event Detection

    To configure errored symbol event detection globally: Step Command Remarks Enter system view. system-view By default, the errored symbol Configure the errored symbol oam global errored-symbol-period event detection window is event detection window. window window-value 100000000. Configure the errored symbol oam global errored-symbol-period By default, the errored symbol event triggering threshold.

  • Page 13: Configuring Errored Frame Period Event Detection

    Step Command Remarks Configure the errored frame oam errored-frame window By default, an interface uses the event detection window. window-value value configured globally. Configure the errored frame oam errored-frame threshold By default, an interface uses the event triggering threshold. threshold-value value configured globally.

  • Page 14: Configuring The Action A Port Takes After It Receives An Ethernet Oam Event From The Remote End

    An errored frame seconds event occurs when the number of times that errored frame seconds are detected on a port in the detection window (specified detection interval) exceeds the predefined threshold. You can configure this command in system view or port view. The configuration in system view takes effect on all ports, and the configuration in port view takes effect on the specified port.

  • Page 15: Configuring Ethernet Oam Remote Loopback

    Step Command Remarks Configure the action the port oam remote-failure By default, the port only logs the takes after it receives an { connection-expired | Ethernet OAM event it receives Ethernet OAM event from the critical-event | dying-gasp | from the remote end. remote end.

  • Page 16: Enabling Ethernet Oam Remote Loopback On The Port

    Enabling Ethernet OAM remote loopback on the port Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet port interface interface-type view. interface-number Enable Ethernet OAM remote By default, Ethernet OAM remote oam remote-loopback start loopback on the port. loopback is disabled.

  • Page 17: Ethernet Oam Configuration Example

    Purpose Command Display the statistics on Ethernet OAM link error display oam link-event { local | remote } [ interface events after an Ethernet OAM connection is interface-type interface-number ] established. Clear statistics on Ethernet OAM packets and Ethernet reset oam [ interface interface-type interface-number ] OAM link error events.

  • Page 18

    Use the display oam critical-event command to display the statistics of Ethernet OAM critical link events. For example: # Display the statistics of Ethernet OAM critical link events on all the ports of Device A. [DeviceA] display oam critical-event -----------[GigabitEthernet1/0/1] ----------- Local link status : UP Event statistics...

  • Page 19: Configuring Cfd

    Configuring CFD Overview Connectivity Fault Detection (CFD), which conforms to IEEE 802.1ag Connectivity Fault Management (CFM) and ITU-T Y.1731, is an end-to-end per-VLAN link layer OAM mechanism. CFD is used for link connectivity detection, fault verification, and fault location. Basic CFD concepts Maintenance domain A maintenance domain (MD) defines the network or part of the network where CFD plays its role.

  • Page 20

    An MA serves the specified VLAN or no VLAN. An MA that serves a VLAN is considered to be carrying VLAN attribute. An MA that serves no VLAN is considered to be carrying no VLAN attribute. 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 21

    Figure 3 Procedure of creating MIPs Figure 4 demonstrates a grading example of the CFD module. Four levels of MDs (0, 2, 3, and 5) are designed. The bigger the number, the higher the level and the larger the area covered. MPs are configured on the ports of Device A through Device F.

  • Page 22: Cfd Functions

    LBM frames and LBR frames are unicast frames. LBM frames are multicast and unicast frames. HP devices support sending and receiving unicast LBM frames and receiving multicast LBM frames. HP devices do not support sending multicast LBM frames. LBR frames are unicast frames.

  • Page 23

    NOTE: This function is supported only by Release 3108P01 and later versions. The LM function measures the frame loss in a certain direction between a pair of MEPs. The source MEP sends loss measurement messages (LMMs) to the target MEP. The target MEP responds with loss measurement replies (LMRs).

  • Page 24: Eais

    EAIS Ethernet Alarm Indication Signal (EAIS) enables collaboration between the Ethernet port status and the AIS function. When a port on the device (not necessarily an MP) goes down, it immediately starts to send EAIS frames periodically to suppress the error alarms. When the port goes up again, it immediately stops sending EAIS frames.

  • Page 25: Configuring Basic Cfd Settings

    Tasks at a glance • (Optional.) Configuring LB on MEPs • (Optional.) Configuring LT on MEPs • (Optional.) Configuring AIS • (Optional.) Configuring LM • (Optional.) Configuring one-way DM • (Optional.) Configuring two-way DM • (Optional.) Configuring TST (Optional.) Configuring EAIS Typically, a port blocked by the spanning tree feature cannot receive or send CFD messages except in the following cases: The port is configured as an outward-facing MEP.

  • Page 26: Configuring Meps

    Configuring MEPs CFD is implemented through various operations on MEPs. As a MEP is configured on a service instance, the MD level and VLAN attribute of the service instance become the attribute of the MEP. Before creating MEPs, configure the MEP list. A MEP list is a collection of local MEPs that can be configured in an MA and the remote MEPs to be monitored.

  • Page 27: Configuring Cfd Functions

    Step Command Remarks Enter system view. system-view By default, no rules for generating Configure MIP cfd mip-rule { default | explicit } MIPs are configured, and the auto-generation rules. service-instance instance-id system does not automatically create any MIP. Configuring CFD functions Configuration prerequisites Complete basic CFD settings.

  • Page 28: Configuring Lb On Meps

    Step Command Remarks Enter system view. system-view (Optional.) Set the CCM cfd cc interval interval-value By default, the interval field value is interval field. service-instance instance-id Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. Enable CCM sending on a cfd cc service-instance instance-id By default, CCM sending is...

  • Page 29: Configuring Ais

    Step Command Remarks Enter system view. system-view Enable LT messages automatic cfd linktrace auto-detection [ size By default, LT messages sending. size-value ] automatic sending is disabled. Configuring AIS The AIS function suppresses the number of error alarms reported by MEPs. For a MEP in the service instance to send AIS frames, set the AIS frame transmission level to be higher than the MD level of the MEP.

  • Page 30: Configuring Two-way Dm

    One-way DM requires that the clocks at the transmitting MEP and the receiving MEP be synchronized. For the purpose of frame delay variation measurement, the requirement for clock synchronization can be relaxed. To view the test result, use the display cfd dm one-way history command on the target MEP. To configure one-way DM: Task Command...

  • Page 31: Configuring Eais

    EAIS frame is sent. If the intersection contains more than 70 VLANs and the EAIS frame transmission interval is 1 second, the CPU usage will be too high. In this case, HP recommends that you set the EAIS frame transmission interval to 60 seconds.

  • Page 32: Cfd Configuration Example

    Purpose Command Display the AIS configuration and information on the display cfd ais [ service-instance instance-id [ mep specified MEP. mep-id ] ] Display the AIS configuration and information display cfd ais-track link-status [ interface associated with the status of the specified port. interface-type interface-number ] display cfd dm one-way history [ service-instance Display the one-way DM result on the specified MEP.

  • Page 33

    The MIPs of MD_B are designed on Device C, and are configured on all ports. You must 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 34

    [DeviceB] cfd md MD_B level 3 [DeviceB] cfd service-instance 2 ma-id vlan-based md MD_B vlan 100 # Configure Device D in the same way Device B is configured. (Details not shown.) # Create MD_B (level 3) on Device C, and create service instance 2 (in which the MA is identified by a VLAN and serves VLAN 100).

  • Page 35

    # On Device A, enable the sending of CCM frames for MEP 1001 in service instance 1 on GigabitEthernet 1/0/1. [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] cfd cc service-instance 1 mep 1001 enable [DeviceA-GigabitEthernet1/0/1] quit # On Device B, enable the sending of CCM frames for MEP 2001 in service instance 2 on GigabitEthernet 1/0/3.

  • Page 36

    [DeviceA] cfd loopback service-instance 1 mep 1001 target-mep 5001 Loopback to 0010-FC05-6515 with the sequence number start from 1001-43404: Reply from 0010-FC05-6515: sequence number=1001-43404 time=5ms Reply from 0010-FC05-6515: sequence number=1001-43405 time=5ms Reply from 0010-FC05-6515: sequence number=1001-43406 time=5ms Reply from 0010-FC05-6515: sequence number=1001-43407 time=5ms Reply from 0010-FC05-6515: sequence number=1001-43408 time=5ms Sent: 5 Received: 5...

  • Page 37

    # 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 38: Configuring Dldp

    Configuring DLDP Overview 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 fiber links occur in the following cases: Fibers are cross-connected. •...

  • Page 39: Basic Concepts

    Basic concepts DLDP neighbor states If port A and B are on the same link and port A can receive link-layer packets from port B, port B is a DLDP neighbor of port A. Two ports that can exchange packets are neighbors. Table 6 DLDP neighbor states DLDP timer Description...

  • Page 40: How Dldp Works

    DLDP timer Description If a port is physically down, the device triggers the DelayDown timer (the default is 1 second and is configurable), rather than removing the corresponding neighbor entry. DelayDown timer When the DelayDown timer expires, the device removes the corresponding DLDP neighbor information if the port is down, and does not perform any operation if the port is up.

  • Page 41

    Port 1 receives the RecoverProbe packet from Port 4, and returns a RecoverEcho packet. Port 4 cannot receive any RecoverEcho packet from Port 1, so Port 4 cannot become the neighbor of Port 1. Port 3 can receive the RecoverEcho packet from Port 1, but Port 3 is not the intended destination, so Port 3 cannot become the neighbor of Port 1.

  • Page 42: Configuration Restrictions And Guidelines

    packet to Port 2. At the same time, Port 1 deletes the neighborship with Port 2, and starts the RecoverProbe timer. Port 2 stays in Inactive state during this process. When an interface is physically down, but the Tx end of the interface is still operating, DLDP sends a LinkDown packet to inform the peer to delete the relevant neighbor entry.

  • Page 43: Enabling Dldp

    Setting the interval to send advertisement packets To make sure DLDP can detect unidirectional links before network performance deteriorates, set the advertisement interval appropriate for your network environment. (HP recommends that you use the default interval.) To set the Advertisement packet sending interval:...

  • Page 44: Setting The Port Shutdown Mode

    Setting the port shutdown mode On detecting a unidirectional link, the ports can be shut down in one of the following modes: • Auto mode—When a unidirectional link is detected, DLDP changes the DLDP port state to Unidirectional. The unidirectional port periodically sends RecoverProbe packets. When a correct RecoverEcho packet is received, the link is restored to a bidirectional link, and the port state changes from Unidirectional to Bidirectional.

  • Page 45: Displaying And Maintaining Dldp

    Displaying and maintaining DLDP Execute display commands in any view and the reset command in user view. Task Command display dldp [ interface interface-type Display the DLDP configuration globally and of a port. interface-number ] Display the statistics on DLDP packets passing through display dldp statistics [ interface interface-type a port.

  • Page 46

    # Configure GigabitEthernet 1/0/2 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port. [DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] duplex full [DeviceA-GigabitEthernet1/0/2] speed 1000 [DeviceA-GigabitEthernet1/0/2] dldp enable [DeviceA-GigabitEthernet1/0/2] quit # Set the port shutdown mode to auto. [DeviceA] dldp unidirectional-shutdown auto Configure Device B: # Enable DLDP globally.

  • Page 47

    Neighbor aged time: 11s Interface GigabitEthernet1/0/2 DLDP port state: Bidirectional Number of the port’s neighbors: 1 Neighbor MAC address: 0023-8956-3600 Neighbor port index: 2 Neighbor state: Confirmed Neighbor aged time: 12s The output shows that both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are in Bidirectional state, which means both links are bidirectional.

  • Page 48: Manually Shutting Down Unidirectional Links

    The output shows that the DLDP port status of both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 is unidirectional, which indicates that DLDP detects unidirectional links on them and automatically shuts down the two ports. The unidirectional links are caused by cross-connected fibers. Correct the fiber connections. As a result, the ports shut down by DLDP automatically recover, and Device A displays the following log information: <DeviceA>%Jul 11 17:42:57:709 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/1...

  • Page 49

    Configuration procedure Configure Device A: # Enable DLDP globally. <DeviceA> system-view [DeviceA] dldp enable # Configure GigabitEthernet 1/0/1 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port. [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] duplex full [DeviceA-GigabitEthernet1/0/1] speed 1000 [DeviceA-GigabitEthernet1/0/1] dldp enable [DeviceA-GigabitEthernet1/0/1] quit...

  • Page 50

    DLDP global status: Enabled DLDP advertisement interval: 5s DLDP authentication-mode: None DLDP unidirectional-shutdown mode: Manual DLDP delaydown-timer value: 1s Number of enabled ports: 2 Interface GigabitEthernet1/0/1 DLDP port state: Bidirectional Number of the port’s neighbors: 1 Neighbor MAC address: 0023-8956-3600 Neighbor port index: 1 Neighbor state: Confirmed Neighbor aged time: 11s...

  • Page 51

    <DeviceA> display dldp DLDP global status: Enabled DLDP advertisement interval: 5s DLDP authentication-mode: None DLDP unidirectional-shutdown mode: Manual DLDP delaydown-timer value: 1s Number of enabled ports: 2 Interface GigabitEthernet1/0/1 DLDP port state: Unidirectional Number of the port’s neighbors: 0 (Maximum number ever detected: 1) Interface GigabitEthernet1/0/2 DLDP port state: Unidirectional Number of the port’s neighbors: 0 (Maximum number ever detected: 1)

  • Page 52

    %Jul 12 08:46:17:959 2014 DeviceA DLDP/6/DLDP_NEIGHBOR_CONFIRMED: A neighbor was confirmed on interface GigabitEthernet1/0/2. The neighbor's system MAC is 0023-8956-3600, and the port index is 2. %Jul 12 08:46:17:959 2014 DeviceA DLDP/6/DLDP_LINK_BIDIRECTIONAL: DLDP detected a bidirectional link on interface GigabitEthernet1/0/2. The output shows that the port status and link status of GigabitEthernet 1/0/2 are now up and its DLDP neighbors are determined.

  • Page 53: Configuring Rrpp

    Configuring RRPP For the HP 5130 EI Switch Series, RRPP is supported only by Release 3108P01 and later versions. The support for RRPP varies by device model. • HP 5130-24G-SFP-4SFP+ EI Switch (JG933A)—All interfaces support RRPP. HP 5130-24G-4SFP+ EI Switch (JG932A), HP 5130-24G-4SFP+ EI Brazil Switch (JG975A), HP •...

  • Page 54: Basic Rrpp Concepts

    Basic RRPP concepts Figure 12 shows a typical RRPP network with two Ethernet rings and multiple nodes. RRPP detects ring status and sends topology change information by exchanging Rapid Ring Protection Protocol Data Units (RRPPDUs) among the nodes. Figure 12 RRPP networking diagram RRPP domain An RRPP domain is uniquely identified by a domain ID.

  • Page 55

    In an RRPP domain, a control VLAN is dedicated to transferring RRPPDUs. On a device, the ports accessing an RRPP ring belong to the control VLANs of the ring, and only these ports can join the control VLANs. An RRPP domain is configured with the following control VLANs: One primary control VLAN, which is the control VLAN for the primary ring.

  • Page 56: Rrppdus

    When an RRPP ring is in Disconnect state, the secondary port forwards packets from data VLANs. In terms of functionality, the primary port and the secondary port of a transit node are the same. Both are designed for transferring protocol packets and data packets over an RRPP ring. As shown in Figure 12, Device A is the master node of Ring 1.

  • Page 57: Rrpp Timers

    Type Description The edge node initiates Edge-Hello packets to examine the SRPTs between the edge Edge-Hello node and the assistant edge node. The assistant edge node initiates Major-Fault packets to notify the edge node of SRPT Major-Fault failure when an SRPT between assistant edge node and edge node is disconnected. RRPP timers When RRPP determines the link state of an Ethernet ring, it uses the following timers: Hello timer—Specifies the interval at which the master node sends Hello packets out of the primary...

  • Page 58

    Link down alarm mechanism In an RRPP domain, when the transit node, edge node, or assistant edge node finds that any of its ports is down, it immediately sends Link-Down packets to the master node. When the master node receives a Link-Down packet, it takes the following actions: •...

  • Page 59: Typical Rrpp Networking

    Typical RRPP networking Single ring As shown in Figure 13, only a single ring exists in the network topology. You need only define an RRPP domain. Figure 13 Schematic diagram for a single-ring network Tangent rings As shown in Figure 14, two or more rings exist in the network topology and only one common node exists between rings.

  • Page 60

    Figure 15 Schematic diagram for an intersecting-ring network Dual-homed rings As shown in Figure 16, two or more rings exist in the network topology and two similar common nodes exist between rings. You need only define an RRPP domain and configure one ring as the primary ring and the other rings as subrings.

  • Page 61

    Figure 17 Schematic diagram for a single-ring load balancing network Intersecting-ring load balancing In an intersecting-ring network, you can also achieve load balancing by configuring multiple domains. As shown in Figure • Ring 1 is the primary ring and Ring 2 is the subring in both Domain 1 and Domain 2. Domain 1 and Domain 2 are configured with different protected VLANs.

  • Page 62: Rrpp Configuration Task List

    RRPP configuration task list You can configure RRPP in the following order: • Create RRPP domains based on service planning. Specify control VLANs and data VLANs for each RRPP domain. • Determine the ring roles and node roles based on the traffic paths in each RRPP domain. •...

  • Page 63: Configuring Protected Vlans

    secondary control VLAN ID. For the control VLAN configuration to succeed, make sure the IDs of the two control VLANs are consecutive and have not been previously assigned. Follow these guidelines when you configure control VLANs: Do not configure the default VLAN of a port accessing an RRPP ring as the control VLAN, and do •...

  • Page 64: Configuring Rrpp Rings

    Step Command Remarks Enter system view. system-view Not required if the device is operating in PVST mode. Enter MST region view. stp region-configuration For more information about the command, see Layer 2—LAN Switching Command Reference. Use either method. By default, all VLANs in an MST •...

  • Page 65: Configuring Rrpp Nodes

    To accelerate topology convergence, HP recommends that you use the link-delay command to • enable link status rapid report function on an RRPP port. Use this command (or the undo link-delay command, depending on the device model) to set the physical state change suppression interval to 0 seconds.

  • Page 66

    Specifying a transit node Step Command Remarks Enter system view. system-view Enter RRPP domain view. rrpp domain domain-id Specify the current ring ring-id node-mode transit device as a transit node [ primary-port interface-type By default, the device is not a of the ring, and specify interface-number ] [ secondary-port node of the RRPP ring.

  • Page 67: Activating An Rrpp Domain

    Step Command Remarks Specify the current device ring ring-id node-mode assistant-edge as the assistant edge node By default, the device is not a [ edge-port interface-type of the subring, and specify node of the RRPP ring. interface-number ] an edge port. Activating an RRPP domain Before you activate an RRPP domain on the current device, enable the RRPP protocol and RRPP rings for the RRPP domain on the current device.

  • Page 68: Configuring An Rrpp Ring Group

    Configuring an RRPP ring group To reduce Edge-Hello traffic, assign subrings with the same edge node and assistant edge node to an RRPP ring group. An RRPP ring group must be configured on both the edge node and the assistant edge node.

  • Page 69: Rrpp Configuration Examples

    RRPP configuration examples Single ring configuration example Network 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. Specify the protected VLANs of RRPP domain 1 as VLANs 1 through 30.

  • Page 70

    # Disable the spanning tree feature on the port. [DeviceA-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceA-GigabitEthernet1/0/1] port link-type trunk # Assign the port to VLANs 1 through 30. [DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

  • Page 71: Intersecting Ring Configuration Example

    # Assign the port to VLANs 1 through 30. [DeviceB-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured. [DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] link-delay 0 [DeviceB-GigabitEthernet1/0/2] undo stp enable [DeviceB-GigabitEthernet1/0/2] port link-type trunk [DeviceB-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/2] quit...

  • Page 72

    Device B is the transit node of primary ring 1 and the edge node of subring 2, with GigabitEthernet • 1/0/3 as the edge port. Device C is the transit node of primary ring 1 and the assistant edge node of subring 1, with •...

  • Page 73

    [DeviceA-GigabitEthernet1/0/2] undo stp enable [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. [DeviceA] rrpp domain 1 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1. [DeviceA-rrpp-domain1] control-vlan 4092 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

  • Page 74

    # Configure GigabitEthernet 1/0/3 in the same way GigabitEthernet 1/0/1 is configured. [DeviceB] interface gigabitethernet 1/0/3 [DeviceB-GigabitEthernet1/0/3] link-delay 0 [DeviceB-GigabitEthernet1/0/3] undo stp enable [DeviceB-GigabitEthernet1/0/3] port link-type trunk [DeviceB-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/3] quit # Create RRPP domain 1. [DeviceB] rrpp domain 1 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

  • Page 75

    # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured. [DeviceC] interface gigabitethernet 1/0/2 [DeviceC-GigabitEthernet1/0/2] link-delay 0 [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 # Configure GigabitEthernet 1/0/3 in the same way GigabitEthernet 1/0/1 is configured. [DeviceC] interface gigabitethernet 1/0/3 [DeviceC-GigabitEthernet1/0/3] link-delay 0 [DeviceC-GigabitEthernet1/0/3] undo stp enable...

  • Page 76

    # Disable the spanning tree feature on the port. [DeviceD-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceD-GigabitEthernet1/0/1] port link-type trunk # Assign the port to VLANs 1 through 30. [DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

  • Page 77: Dual-homed Rings Configuration Example

    # Assign the port to VLANs 1 through 30. [DeviceE-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceE-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured. [DeviceE] interface gigabitethernet 1/0/2 [DeviceE-GigabitEthernet1/0/2] link-delay 0 [DeviceE-GigabitEthernet1/0/2] undo stp enable [DeviceE-GigabitEthernet1/0/2] port link-type trunk [DeviceE-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceE-GigabitEthernet1/0/2] quit...

  • Page 78

    IMPORTANT: Configure the primary and secondary ports on the master nodes correctly to make sure other protocols still operate correctly when data VLANs are denied by the secondary ports. Figure 21 Network diagram Configuration procedure Configure Device A: # Create VLANs 1 through 30. <DeviceA>...

  • Page 79

    [DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] link-delay 0 [DeviceA-GigabitEthernet1/0/2] undo stp enable [DeviceA-GigabitEthernet1/0/2] port link-type trunk [DeviceA-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/2] quit # Configure GigabitEthernet 1/0/3 in the same way GigabitEthernet 1/0/1 is configured. [DeviceA] interface gigabitethernet 1/0/3 [DeviceA-GigabitEthernet1/0/3] link-delay 0 [DeviceA-GigabitEthernet1/0/3] undo stp enable [DeviceA-GigabitEthernet1/0/3] port link-type trunk...

  • Page 80

    # Map these VLANs to MSTI 1. [DeviceB] stp region-configuration [DeviceB-mst-region] instance 1 vlan 1 to 30 # Activate the MST region configuration. [DeviceB-mst-region] active region-configuration [DeviceB-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1. [DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] link-delay 0 # Disable the spanning tree feature on the port.

  • Page 81

    [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 assistant edge node of subring 2, with GigabitEthernet 1/0/4 as the edge port. Enable subring 2. [DeviceB-rrpp-domain1] ring 2 node-mode assistant-edge edge-port gigabitethernet 1/0/4 [DeviceB-rrpp-domain1] ring 2 enable # Configure Device B as the assistant edge node of subring 3, with GigabitEthernet 1/0/3 as the...

  • Page 82

    [DeviceC-GigabitEthernet1/0/3] undo stp enable [DeviceC-GigabitEthernet1/0/3] port link-type trunk [DeviceC-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/3] quit # Configure GigabitEthernet 1/0/4 in the same way GigabitEthernet 1/0/1 is configured. [DeviceC] interface gigabitethernet 1/0/4 [DeviceC-GigabitEthernet1/0/4] link-delay 0 [DeviceC-GigabitEthernet1/0/4] undo stp enable [DeviceC-GigabitEthernet1/0/4] port link-type trunk [DeviceC-GigabitEthernet1/0/4] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/4] quit...

  • Page 83

    [DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] link-delay 0 # Disable the spanning tree feature on the port. [DeviceD-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceD-GigabitEthernet1/0/1] port link-type trunk # Assign the port to VLANs 1 through 30. [DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

  • Page 84

    # Configure Device D as the edge node of subring 5, with GigabitEthernet 1/0/4 as the edge port. Enable subring 5. [DeviceD-rrpp-domain1] ring 5 node-mode edge edge-port gigabitethernet 1/0/4 [DeviceD-rrpp-domain1] ring 5 enable [DeviceD-rrpp-domain1] quit # Enable RRPP. [DeviceD] rrpp enable Configure Device E: # Create VLANs 1 through 30.

  • Page 85

    [DeviceE-rrpp-domain1] quit # Enable RRPP. [DeviceE] rrpp enable Configure Device F: # Create VLANs 1 through 30. <DeviceF> system-view [DeviceF] vlan 1 to 30 # Map these VLANs to MSTI 1. [DeviceF] stp region-configuration [DeviceF-mst-region] instance 1 vlan 1 to 30 # Activate the MST region configuration.

  • Page 86

    # Create VLANs 1 through 30. <DeviceG> system-view [DeviceG] vlan 1 to 30 # Map these VLANs to MSTI 1. [DeviceG] stp region-configuration [DeviceG-mst-region] instance 1 vlan 1 to 30 # Activate the MST region configuration. [DeviceG-mst-region] active region-configuration [DeviceG-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

  • Page 87: Load-balanced Intersecting-ring Configuration Example

    [DeviceH] stp region-configuration [DeviceH-mst-region] instance 1 vlan 1 to 30 # Activate the MST region configuration. [DeviceH-mst-region] active region-configuration [DeviceH-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1. [DeviceH] interface gigabitethernet 1/0/1 [DeviceH-GigabitEthernet1/0/1] link-delay 0 # Disable the spanning tree feature on the port.

  • Page 88

    Device A, Device B, Device C, Device D, and Device F form RRPP domain 1. VLAN 100 is the • primary control VLAN of the RRPP domain. Device A is the master node of the primary ring, Ring 1. Device D is the transit node of Ring 1. Device F is the master node of the subring Ring 3. Device C is the edge node of the subring Ring 3.

  • Page 89

    # Disable the spanning tree feature on the port. [DeviceA-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceA-GigabitEthernet1/0/1] port link-type trunk # Remove the port from VLAN 1, and assign it to VLANs 11 and 12. [DeviceA-GigabitEthernet1/0/1] undo port trunk permit vlan 1 [DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 11 12 # Configure VLAN 11 as the default VLAN.

  • Page 90

    # Create VLANs 11 and 12. <DeviceB> system-view [DeviceB] vlan 11 to 12 # Map VLAN 11 to MSTI 1 and VLAN 12 to MSTI 2. [DeviceB] stp region-configuration [DeviceB-mst-region] instance 1 vlan 11 [DeviceB-mst-region] instance 2 vlan 12 # Activate the MST region configuration. [DeviceB-mst-region] active region-configuration [DeviceB-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

  • Page 91

    # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/4. [DeviceB] interface gigabitethernet 1/0/4 [DeviceB-GigabitEthernet1/0/4] link-delay 0 # Disable the spanning tree feature on the port. [DeviceB-GigabitEthernet1/0/4] undo stp enable # Configure the port as a trunk port. [DeviceB-GigabitEthernet1/0/4] port link-type trunk # Remove the port from VLAN 1, and assign it to VLAN 11.

  • Page 92

    [DeviceC-rrpp-domain2] quit # Enable RRPP. [DeviceB] rrpp enable Configure Device C: # Create VLANs 11 and 12. <DeviceC> system-view [DeviceC] vlan 11 to 12 # Map VLAN 11 to MSTI 1 and VLAN 12 to MSTI 2. [DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 11 [DeviceC-mst-region] instance 2 vlan 12 # Activate the MST region configuration.

  • Page 93

    [DeviceC-GigabitEthernet1/0/3] port trunk permit vlan 12 # Configure VLAN 12 as the default VLAN. [DeviceC-GigabitEthernet1/0/3] port trunk pvid vlan 12 [DeviceC-GigabitEthernet1/0/3] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/4. [DeviceC] interface gigabitethernet 1/0/4 [DeviceC-GigabitEthernet1/0/4] link-delay 0 # Disable the spanning tree feature on the port.

  • Page 94

    # Configure Device C as the edge node of subring 2 in RRPP domain 2, with GigabitEthernet 1/0/3 as the edge port. Enable subring 2. [DeviceC-rrpp-domain2] ring 2 node-mode edge edge-port gigabitethernet 1/0/3 [DeviceC-rrpp-domain2] ring 2 enable [DeviceC-rrpp-domain2] quit # Enable RRPP. [DeviceC] rrpp enable Configure Device D: # Create VLANs 11 and 12.

  • Page 95

    [DeviceD-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device D as the transit node of primary ring 1 in RRPP domain 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. 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...

  • Page 96

    # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured. [DeviceE] interface gigabitethernet 1/0/2 [DeviceE-GigabitEthernet1/0/2] link-delay 0 [DeviceE-GigabitEthernet1/0/2] undo stp enable [DeviceE-GigabitEthernet1/0/2] port link-type trunk [DeviceE-GigabitEthernet1/0/2] undo port trunk permit vlan 1 [DeviceE-GigabitEthernet1/0/2] port trunk permit vlan 12 [DeviceE-GigabitEthernet1/0/2] port trunk pvid vlan 12 [DeviceE-GigabitEthernet1/0/2] quit # Create RRPP domain 2.

  • Page 97: Troubleshooting Rrpp

    [DeviceF-GigabitEthernet1/0/1] port trunk pvid vlan 11 [DeviceF-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured. [DeviceF] interface gigabitethernet 1/0/2 [DeviceF-GigabitEthernet1/0/2] link-delay 0 [DeviceF-GigabitEthernet1/0/2] undo stp enable [DeviceF-GigabitEthernet1/0/2] port link-type trunk [DeviceF-GigabitEthernet1/0/2] undo port trunk permit vlan 1 [DeviceF-GigabitEthernet1/0/2] port trunk permit vlan 11 [DeviceF-GigabitEthernet1/0/2] port trunk pvid vlan 11 [DeviceF-GigabitEthernet1/0/2] quit...

  • Page 98

    RRPP is not enabled on some nodes in the RRPP ring. • • The domain ID or primary control VLAN ID is not the same on the nodes in the RRPP ring. Some ports are abnormal. • Solution • Use the display rrpp brief command to determine whether RRPP is enabled for all nodes. If it is not, use the rrpp enable command and the ring enable command to enable RRPP and RRPP rings for all nodes.

  • Page 99: Configuring Smart Link

    Configuring Smart Link Overview To avoid single-point failures and guarantee network reliability, downstream devices are typically dual-homed to upstream devices, as shown in Figure Figure 23 Dual uplink network diagram To remove network loops on a dual-homed network, you can use a spanning tree protocol. However, convergence time is long with spanning tree protocols, which makes it unsuitable for users who have high demand on convergence speed.

  • Page 100: Terminology

    Terminology Smart link group A smart link group consists of only two member ports: the primary and the secondary ports. Only one port is active for forwarding at a time, and the other port is blocked and in standby state. When link failure occurs on the active port due to port shutdown or the presence of unidirectional link, the standby port becomes active and takes over, and the original active port transits to the blocked state.

  • Page 101: Smart Link Collaboration Mechanisms

    When a port switches to the forwarding state, the system outputs log information to notify the user of the port state change. Topology change Link switchover can outdate the MAC address forwarding entries and ARP/ND entries on all devices, so a forwarding entry update mechanism is required to ensure proper transmission.

  • Page 102: Smart Link Configuration Task List

    Smart Link collaborates with link detection protocols through track entries. It supports only the Continuity Check (CC) function of Connectivity Fault Detection (CFD) to implement link detection. CFD notifies the smart link group member ports of fault detection events by using detection VLANs and detection ports. A port responds to a continuity check event only when the control VLAN of the smart link group to which it belongs matches the detection VLAN.

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

    Step Command Remarks Enter system view. system-view For more information about the Enter MST region view. stp region-configuration command, see Layer 2—LAN Switching Command Reference. • Method 1: All VLANs in an MST region are instance instance-id vlan mapped to CIST (MSTI 0) by default. Configure the vlan-list VLAN-to-instance mapping...

  • Page 104: Configuring Role Preemption For A Smart Link Group

    Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface interface-type view or Layer 2 aggregate interface-number interface view. Configure member ports for a port smart-link group group-id By default, a port is not a smart smart link group. { primary | secondary } link group member.

  • Page 105: Configuring The Collaboration Between Smart Link And Track

    Configuring the collaboration between Smart Link and Track Smart Link collaborates with the CC function of CFD through track entries to implement link detection. Before configuring the collaboration between Smart Link and Track on a port, make sure the port has been added to the specified smart link group.

  • Page 106: Displaying And Maintaining Smart Link

    Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. Configure the control VLANs smart-link flush enable By default, no control VLAN for receiving flush messages. [ control-vlan vlan-id-list ] receives flush messages.

  • Page 107

    Figure 24 Network diagram Configuration procedure Configure Device C: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the 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 # Shut down GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2, disable the spanning tree...

  • Page 108

    [DeviceC-smlk-group1] port gigabitethernet 1/0/2 secondary # Enable flush message sending in smart link group 1, and configure VLAN 10 as the transmit control VLAN. [DeviceC-smlk-group1] flush enable control-vlan 10 [DeviceC-smlk-group1] quit # Bring up GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 again. [DeviceC] interface gigabitethernet 1/0/1 [DeviceC-GigabitEthernet1/0/1] undo shutdown [DeviceC-GigabitEthernet1/0/1] quit...

  • Page 109

    # Bring up GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 again. [DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] undo shutdown [DeviceD-GigabitEthernet1/0/1] quit [DeviceD] interface gigabitethernet 1/0/2 [DeviceD-GigabitEthernet1/0/2] undo shutdown [DeviceD-GigabitEthernet1/0/2] quit Configure Device B: # Create VLANs 1 through 30. <DeviceB> system-view [DeviceB] vlan 1 to 30 # Configure GigabitEthernet 1/0/1 as a trunk port, and assign it to VLANs 1 through 30.

  • Page 110

    # Configure GigabitEthernet 1/0/2 as a trunk port, and assign it to VLANs 1 through 30. Disable the spanning tree feature and enable flush message receiving on it, and configure VLAN 10 as the receive control VLAN. [DeviceE] interface gigabitethernet 1/0/2 [DeviceE-GigabitEthernet1/0/2] port link-type trunk [DeviceE-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceE-GigabitEthernet1/0/2] undo stp enable...

  • Page 111: Multiple Smart Link Groups Load Sharing Configuration Example

    ----------------------------------------------------------------------------- GE1/0/1 PRIMARY ACTIVE 16:45:20 2014/04/21 GE1/0/2 SECONDARY STANDBY 1 16:37:20 2014/04/21 Use the display smart-link flush command to display the flush messages received on a device. # Display the flush messages received on Device B. [DeviceB] display smart-link flush Received flush packets Receiving interface of the last flush packet : GigabitEthernet1/0/3...

  • Page 112

    [DeviceC-mst-region] quit # Shut down GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2, disable the spanning tree feature on them, configure them 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 [DeviceC-GigabitEthernet1/0/1] quit...

  • Page 113

    [DeviceC-GigabitEthernet1/0/2] quit Configure Device B: # Create VLAN 1 through VLAN 200. <DeviceB> system-view [DeviceB] vlan 1 to 200 # Configure GigabitEthernet 1/0/1 as a trunk port, assign it to VLANs 1 through 200, enable flush message receiving, and configure VLAN 10 and VLAN 110 as the receive control VLANs on the port.

  • Page 114

    # Configure GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 as trunk ports, assign them to VLANs 1 through 200, enable flush message receiving, and configure VLAN 10 and VLAN 110 as the receive control VLANs on the ports. [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] port link-type trunk [DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 1 to 200 [DeviceA-GigabitEthernet1/0/1] smart-link flush enable control-vlan 10 110...

  • Page 115: Smart Link And Track Collaboration Configuration Example

    Receiving time of the last flush packet : 16:25:21 2014/04/21 Device ID of the last flush packet : 000f-e23d-5af0 Control VLAN of the last flush packet : 10 Smart Link and Track collaboration configuration example Network requirements As shown in Figure Device A, Device B, Device C, and Device D form maintenance domain (MD) MD_A of level 5.

  • Page 116

    [DeviceA-GigabitEthernet1/0/1] port link-type trunk [DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 1 to 200 [DeviceA-GigabitEthernet1/0/1] smart-link flush enable control-vlan 10 110 [DeviceA-GigabitEthernet1/0/1] quit [DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] port link-type trunk [DeviceA-GigabitEthernet1/0/2] port trunk permit vlan 1 to 200 [DeviceA-GigabitEthernet1/0/2] smart-link flush enable control-vlan 10 110 [DeviceA-GigabitEthernet1/0/2] quit # Enable CFD and create MD MD_A of level 5.

  • Page 117

    [DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] port link-type trunk [DeviceB-GigabitEthernet1/0/2] port trunk permit vlan 1 to 200 [DeviceB-GigabitEthernet1/0/2] undo stp enable [DeviceB-GigabitEthernet1/0/2] smart-link flush enable control-vlan 10 110 [DeviceB-GigabitEthernet1/0/2] quit Configure Device C: # Create VLAN 1 through VLAN 200, map VLANs 1 through 100 to MSTI 1 and VLANs 101 through 200 to MSTI 2, and activate MST region configuration.

  • Page 118

    [DeviceC-smlk-group2] protected-vlan reference-instance 2 # Configure GigabitEthernet 1/0/1 as the secondary port and GigabitEthernet 1/0/2 as the primary port for smart link group 2. [DeviceC-smlk-group2] port gigabitethernet 1/0/2 primary [DeviceC-smlk-group2] port gigabitethernet 1/0/1 secondary # Enable role preemption in smart link group 2, enable flush message sending, and configure VLAN 110 as the transmit control VLAN.

  • Page 119

    [DeviceC] interface gigabitethernet 1/0/2 [DeviceC-GigabitEthernet1/0/2] port smart-link group 2 track 2 [DeviceC-GigabitEthernet1/0/2] undo shutdown [DeviceC-GigabitEthernet1/0/2] quit Configure Device D: # 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 120

    Control VLAN : 110 Protected VLAN : Reference Instance 2 Member Role State Flush-count Last-flush-time ----------------------------------------------------------------------------- GE1/0/2 PRIMARY ACTIVE 16:45:20 2014/04/21 GE1/0/1 SECONDARY STANDBY 1 16:37:20 2014/04/21 The output shows that primary port GigabitEthernet 1/0/1 of smart link group 1 fails, and secondary port GigabitEthernet 1/0/2 is in forwarding state.

  • Page 121: Configuring Monitor Link

    Configuring Monitor Link Overview Monitor Link associates the state of downlink interfaces with the state of uplink interfaces in a monitor link group. When Monitor Link shuts down the downlink interfaces because of an uplink failure, the downstream device changes connectivity to another link. Figure 27 Monitor Link application scenario A monitor link group contains uplink and downlink interfaces.

  • Page 122

    A monitor link group works independently of other monitor link groups. When a monitor link group does not contain any uplink interface or all its uplink interfaces are down, the monitor link group goes down. It forces all downlink interfaces down at the same time. When any uplink interface comes up, the monitor link group comes up and brings up all the downlink interfaces.

  • Page 123: Configuring Monitor Link Group Member Interfaces

    Configuring monitor link group member interfaces You can configure member interfaces for a monitor link group in monitor link group view or interface view. Configurations made in these views have the same effect. The following interfaces can be configured as member interfaces of a monitor link group: •...

  • Page 124: Displaying And Maintaining Monitor Link

    Step Command Remarks By default, the switchover delay is Configure the switchover delay 0 seconds. The downlink for the downlink interfaces in downlink up-delay delay interfaces come up as soon as an the monitor link group. uplink interface comes up. Displaying and maintaining Monitor Link Execute the display command in any view: Task...

  • Page 125

    [DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 1 to 30 # Activate MST region configuration. [DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit # Shut down GigabitEthernet 1/0/1. [DeviceC] interface gigabitethernet 1/0/1 [DeviceC-GigabitEthernet1/0/1] shutdown # Disable the spanning tree feature on the interface. [DeviceC-GigabitEthernet1/0/1] undo stp enable # Configure the interface as a trunk port.

  • Page 126

    [DeviceA-GigabitEthernet1/0/1] port link-type trunk # Assign the interface to VLANs 1 through 30. [DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 # Enable flush message receiving on the interface. [DeviceA-GigabitEthernet1/0/1] smart-link flush enable [DeviceA-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured. [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...

  • Page 127

    # Configure GigabitEthernet 1/0/1 as a trunk port. [DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] port link-type trunk # Assign the interface to VLANs 1 through 30. [DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 # Enable flush message receiving on the interface. [DeviceD-GigabitEthernet1/0/1] smart-link flush enable [DeviceD-GigabitEthernet1/0/1] quit # Disable the spanning tree feature on GigabitEthernet 1/0/2.

  • Page 128

    Member Role Status -------------------------------------------- GE1/0/1 UPLINK DOWN GE1/0/2 DOWNLINK DOWN...

  • Page 129: Configuring Bfd

    Configuring BFD The term "interface" in this chapter collectively refers to VLAN interfaces. Overview Bidirectional forwarding detection (BFD) provides a general-purpose, standard, medium- and protocol-independent fast failure detection mechanism. It can detect and monitor the connectivity of links in IP to detect communication failures quickly so that measures can be taken to ensure service continuity and enhance network availability.

  • Page 130: Supported Features

    Control packets—Encapsulated into UDP packets with port number 3784 for single-hop detection • or port number 4784 for multihop detection. Echo packet mode The local end of the link sends echo packets to establish BFD sessions and monitor link status. The peer end does not establish BFD sessions and only forwards the packets back to the originating end.

  • Page 131: Configuring Bfd Basic Functions

    Configuring BFD basic functions Before configuring BFD basic functions, configure the network layer addresses of the interfaces so that adjacent nodes are reachable to each other at the network layer. After a BFD session is established, the two ends negotiate BFD parameters, including minimum sending interval, minimum receiving interval, initialization mode, and packet authentication, by exchanging negotiation packets.

  • Page 132

    Step Command Remarks • For Release 3106: bfd authentication-mode simple key-id { cipher cipher-string | plain plain-string } Configure the authentication • By default, single-hop BFD packets For Release 3108P01 and later mode for single-hop control are not authenticated. versions: packets.

  • Page 133: Configuring A Bfd Template

    Step Command Remarks • For Release 3106: bfd multi-hop authentication-mode simple key-id { cipher cipher-string | plain plain-string } Configure the authentication • For Release 3108P01 and later By default, no authentication is mode for multihop BFD versions: performed. control packets. bfd multi-hop authentication-mode { m-md5 | m-sha1 | md5 | sha1 |...

  • Page 134: Displaying And Maintaining Bfd

    Displaying and maintaining BFD Execute the display command in any view and the reset command in user view. Task Command Display BFD session information. display bfd session [ discriminator value | verbose ] Clear BFD session statistics. reset bfd session statistics...

  • Page 135: Configuring Track

    Configuring Track Overview The Track module works between application modules and detection modules, as shown in Figure 29. 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 136: Collaboration Application Example

    If the detection result is not valid, the state of the track entry is NotReady. For example, the track • entry state is NotReady if its associated NQA operation does not exist. The following detection modules can be associated with the Track module: NQA.

  • Page 137: Associating The Track Module With A Detection Module

    Tasks at a glance (Required.) Associating the Track module with an application module: • Associating Track with static routing • Associating Track with PBR • Associating Track with Smart Link Associating the Track module with a detection module Associating Track with NQA NQA supports multiple operation types to analyze network performance, services, and service quality.

  • Page 138: Associating Track With Cfd

    If the BFD detects that the link fails, it informs the track entry of the link failure. The Track module sets • the track entry to Negative state. If the BFD detects that the link is operating correctly, the Track module sets the track entry to Positive •...

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

    When the link or network-layer protocol status of the interface changes to down, the interface • management module informs the Track module of the change. The Track module sets the track entry to Negative. To associate Track with interface management: Step Command Remarks...

  • Page 140: Associating Track With Pbr

    The next hop of the static route is not reachable. The configured static route is invalid. If the track entry is in NotReady state, the following conditions exist: • The accessibility of the next hop of the static route is unknown. The static route is valid.

  • Page 141

    The Negative state of the track entry shows that the object is not available, and the apply clause is • invalid. The NotReady state of the track entry shows that the apply clause is valid. • In PBR, only next hop can be associated. Configuration prerequisites Before you associate Track with PBR, create a policy or a policy node and configure the match criteria as well.

  • Page 142: Associating Track With Smart Link

    Step Command Remarks By default, the next hop is not specified. Set the next hop, and associate it with a track You can configure a Associate Track with IPv6 entry: maximum of two next PBR. apply next-hop { ipv6-address [ direct ] [ track hops for backup.

  • Page 143

    the backup route. When the master route is unavailable, the backup route takes effect. Switch D forwards packets to 20.1.1.0/24 through Switch C. Figure 30 Network diagram Configuration procedure Create VLANs and assign ports to them. Configure the IP address of each VLAN interface as shown in Figure 30.

  • Page 144

    [SwitchA-nqa-admin-test-icmp-echo] quit # Start the NQA operation. [SwitchA] nqa schedule admin test start-time now lifetime forever # Configure track entry 1, and associate it with reaction entry 1 of the NQA operation. [SwitchA] track 1 nqa entry admin test reaction 1 Configure Switch B: # Configure a static route to 30.1.1.0/24 with the next hop 10.2.1.4.

  • Page 145

    [SwitchD] track 1 nqa entry admin test reaction 1 Verifying the configuration # Display information about the track entry on Switch A. [SwitchA] display track all Track ID: 1 State: Positive Duration: 0 days 0 hours 0 minutes 32 seconds Notification delay: Positive 0, Negative 0 (in seconds) Tracked object: NQA entry: admin test...

  • Page 146

    # 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 Direct 0 10.1.1.1 Vlan2 10.1.1.1/32 Direct 0 127.0.0.1 InLoop0 10.2.1.0/24 Static 60 10.1.1.2 Vlan2 10.3.1.0/24 Direct 0...

  • Page 147: Static Routing-track-bfd Collaboration Configuration Example

    Static routing-Track-BFD collaboration configuration example Network requirements As shown in Figure Switch A is the default gateway of the hosts in subnet 20.1.1.0/24. • Switch B is the default gateway of the hosts in subnet 30.1.1.0/24. • • Hosts in the two subnets communicate with each other through static routes. To ensure network availability, configure route backup and static routing-Track-BFD collaboration on Switch A and Switch B as follows: •...

  • Page 148

    Configure Switch B: # Configure a static route to 20.1.1.0/24, with the next hop 10.2.1.1 and the default priority 60, and associate this static route with track entry 1. <SwitchB> system-view [SwitchB] ip route-static 20.1.1.0 24 10.2.1.1 track 1 # Configure a static route to 20.1.1.0/24 with the next hop 10.4.1.3 and the priority 80. [SwitchB] ip route-static 20.1.1.0 24 10.4.1.3 preference 80 # Configure the source address of BFD echo packets as 1.1.1.1.

  • Page 149

    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 shows that Switch A forwards packets to 30.1.1.0/24 through Switch B. The master static route has taken effect. # Remove the IP address of VLAN-interface 2 on Switch B. <SwitchB>...

  • Page 150: Smart Link-track-cfd Collaboration Configuration Example

    Reply from 30.1.1.1: bytes=56 Sequence=4 ttl=254 time=2 ms Reply from 30.1.1.1: bytes=56 Sequence=5 ttl=254 time=1 ms --- Ping statistics for 30.1.1.1 --- 5 packet(s) transmitted, 5 packet(s) received, 0.00% packet loss round-trip min/avg/max/std-dev = 1/1/2/1 ms # Verify that the hosts in 30.1.1.0/24 can communicate with the hosts in 20.1.1.0/24 when the master route fails.

  • Page 151: Support And Other Resources

    Related information Documents To find related documents, browse to the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals For related documentation, navigate to the Networking section, and select a networking category. •...

  • Page 152: 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 153

    Network topology icons 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.

  • Page 154: Index

    Index Numerics high availability Track+NQA, high availability Track+policy-based routing, 1-way DM high availability Track+Smart Link, CFD 1-way DM configuration, high availability Track+static routing, 2-way DM Smart Link associated device, CFD 2-way DM configuration, association high availability CFD maintenance association, activating RRPP domain, authenticating advertising high availability DLDP MD5 authentication,...

  • Page 155

    bidirectional high availability NQA+Track+static routing collaboration, forwarding detection. Use high availability Smart Link+Track+CFD high availability DLDP port state, collaboration, broadcast (RRPP storm suppression mechanism), high availability static routing+Track+BFD collaboration, high availability static routing+Track+NQA collaboration, 1-way DM configuration, high availability Track configuration, 129, 130, 2-way DM configuration, high availability Track+application modules, AIS configuration,...

  • Page 156

    high availability Ethernet OAM errored frame Smart Link group protected VLAN, event detection, Smart Link group role preemption, high availability Ethernet OAM errored frame Smart Link+Track collaboration, period event detection, Smart Link-Track collaboration, high availability Ethernet OAM errored seconds confirmed DLDP neighbor state, period event detection, connecting high availability Ethernet OAM errored symbol...

  • Page 157

    high availability Ethernet OAM errored frame high availability Ethernet OAM, seconds event detection, high availability Track entries, high availability Ethernet OAM errored symbol Monitor Link, 1 18 event detection, RRPP, high availability Ethernet OAM fault Smart Link, detection, DLDP high availability Ethernet OAM remote fault advertisement packet send interval, detection, authentication configuration,...

  • Page 158

    high availability CFD, protocols and standards, high availability DLDP, remote fault detection, high availability Ethernet OAM remote remote loopback, loopback on port, remote loopback configuration, high availability Ethernet OAM remote remote loopback on port, loopback on specific port, remote loopback on specific port, Smart Link flush message reception, remote loopback request rejection, Smart Link flush message send,...

  • Page 159

    Smart Link group configuration (single), maintaining Ethernet OAM, Smart Link group member ports, maintaining RRPP, Smart Link group protected VLAN, Monitor Link configuration, 1 18 Smart Link group role preemption, Monitor Link display, 1 18 Monitor Link downlink interface switchover delay, 1 17 hardware...

  • Page 160

    Track+static routing association, high availability Ethernet OAM performance monitoring, high availability Ethernet OAM port action inactive configuration, high availability DLDP port state, Monitor Link configuration, 1 18 initial DLDP port state, RRPP link down mechanism, intersecting rings Smart Link backup, RRPP load balancing, Smart Link configuration, 93, 96, RRPP network,...

  • Page 161

    high availability DLDP, CFD TST configuration, high availability Ethernet OAM, high availability CFD, RRPP, high availability CFD continuity check on MEP, Smart Link, high availability CFD linktrace on MEP configuration, maintenance high availability CFD loopback on MEP association end point. See configuration, association intermediate point.

  • Page 162

    high availability static routing+Track+NQA high availability DLDP single neighbor collaboration, detection, high availability Track network configuration, 129, 130, activating RRPP domain, high availability Track+application module CFD 1-way DM configuration, association, CFD 2-way DM configuration, high availability Track+application module CFD AIS configuration, collaboration, CFD EAIS configuration, high availability Track+detection module...

  • Page 163

    high availability Ethernet OAM errored frame Smart Link flush message send, period event detection, Smart Link group member ports, high availability Ethernet OAM errored frame Smart Link group protected VLAN, seconds event detection, Smart Link group role preemption, high availability Ethernet OAM errored symbol Smart Link links, event detection, Smart Link load sharing,...

  • Page 164

    RRPP intersecting rings topology, high availability DLDP authentication, RRPP single ring load balancing, high availability DLDP authentication mode, RRPP single ring topology, point RRPP tangent rings topology, high availability CFD maintenance point, node high availability CFD MEP, configuring RRPP node, high availability CFD MEP configuration, RRPP assistant edge type, high availability CFD MEP list,...

  • Page 165

    primary configuring high availability CFD MEPs, RRPP master port, configuring high availability CFD MIP auto-generation rules, RRPP transit port, configuring high availability CFD service probe timer (DLDP), instance, procedure configuring high availability DLDP, 36, activating RRPP domain, configuring high availability DLDP associating high availability Track+application authentication, module,...

  • Page 166

    configuring RRPP ring, rejecting high availability Ethernet OAM remote loopback request, configuring RRPP ring group, setting high availability DLDP advertisement packet configuring RRPP single ring, send interval, configuring Smart Link, 96, setting high availability DLDP DelayDown timer, configuring Smart Link associated device, setting high availability DLDP port shutdown configuring Smart Link device, mode,...

  • Page 167

    high availability Ethernet OAM remote basic concepts, loopback request rejection, broadcast storm suppression, restrictions common port, high availability DLDP configuration, common-flush-FDB RRPPDU, ring complete-flush-FDB RRPPDU, configuring (RRPP), configuration, 47, 56, configuring RRPP group, configuring control VLAN, disconnect state (RRPP), configuring fail timer, health state (RRPP), configuring hello timer, recovery (RRPP),...

  • Page 168

    primary transit port, high availability BFD control packet active operating mode, protocols and standards, high availability BFD control packet asynchronous ring group, 50, operating mode, ring recovery, high availability BFD control packet demand ring topology, operating mode, secondary master port, high availability BFD control packet mode, secondary transit port, high availability BFD control packet passive...

  • Page 169

    group protected VLAN configuration, high availability Track+static routing association, group role preemption configuration, switchover high availability Smart Link+Track+CFD collaboration, Monitor Link downlink interface switchover delay, 1 17 high availability Track+Smart Link association, how it works, tangent rings (RRPP network), link backup, timer links, configuring RRPP fail,...

  • Page 170

    application module association, high availability DLDP manual unidirectional link shutdown, application module collaboration, high availability DLDP port state, BFD association, updating CFD association, Smart Link flush update, configuration, 129, 130, Smart Link uplink traffic triggered MAC address detection module association, learning, detection module collaboration, uplink...

Comments to this Manuals

Symbols: 0
Latest comments: