HPE 3100 v2 Series Configuration Manual
  1. Manuals
  2. Brands
  3. HPE Manuals
  4. Switch
  5. 3100 v2 Series
  6. Configuration manual
HPE 3100 v2 Series Configuration Manual

HPE 3100 v2 Series Configuration Manual

High availability
Hide thumbs Also See for 3100 v2 Series:
Table of Contents

Advertisement

Quick Links

Download this manual
HPE 3100 v2 Switch Series

High Availability

Configuration Guide

Part number: 5998-5997s
Software version: Release 5213 and Release 5213P02
Document version: 6W101-20160506

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 3100 v2 Series and is the answer not in the manual?

Questions and answers

Related Manuals for HPE 3100 v2 Series

Summary of Contents for HPE 3100 v2 Series

  • Page 1: High Availability

    HPE 3100 v2 Switch Series High Availability Configuration Guide Part number: 5998-5997s Software version: Release 5213 and Release 5213P02 Document version: 6W101-20160506...
  • Page 2 © Copyright 2016 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

  • Page 3: Table Of Contents

    Rejecting the Ethernet OAM remote loopback request from a remote port ············································· 11   Displaying and maintaining Ethernet OAM configuration ················································································· 11   Ethernet OAM configuration example ·············································································································· 12 Configuring CFD (available only on the HPE 3100 v2 EI) ····························· 15     Overview ·························································································································································· 15  ...
  • Page 4 Dual homed rings configuration example ································································································· 74   Intersecting-ring load balancing configuration example ··········································································· 83   Troubleshooting ··············································································································································· 91 Configuring Smart Link (available only on the HPE 3100 v2 EI) ··················· 93     Smart Link overview ········································································································································· 93  ...
  • Page 5   Single smart link group configuration example ······················································································ 100   Multiple smart link groups load sharing configuration example ······························································ 104 Configuring Monitor Link (available only on the HPE 3100 v2 EI) ·············· 109     Monitor Link overview ···································································································································· 109  ...

  • Page 6: 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 7: High Availability Technologies

    Connectivity Fault Detection (CFD), which conforms to IEEE 802.1ag Connectivity Fault Management (CFM) and ITU-T CFD (available only "Configuring CFD" in Y.1731, is an end-to-end per-VLAN link layer Operations, on the HPE 3100 High Availability Administration and Maintenance (OAM) mechanism used for v2 EI) Configuration Guide link connectivity detection, fault verification, and fault location.
  • Page 8 STP. It provides link redundancy as (available only on Link" in High well as fast convergence in a dual uplink network, allowing the HPE 3100 v2 Availability the backup link to take over quickly when the primary link Configuration Guide fails.

  • Page 9: 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. Major functions of Ethernet OAM Ethernet OAM provides the following functions: •...

  • Page 10: 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 11 Passive Ethernet OAM Item Active Ethernet OAM mode mode Transmitting Information Available Available OAMPDUs without any TLV Transmitting Loopback Control Available Unavailable OAMPDUs Responding to Loopback Control Available—if both sides operate Available OAMPDUs in active OAM mode NOTE: • Only OAM entities operating in active OAM mode can initiate OAM connections. OAM entities operating in passive mode wait and respond to the connection requests sent by their peers.

  • Page 12: Standards And Protocols

    information—the critical link event type—to its peer. You can use the log information to track ongoing link status and troubleshoot problems promptly. Table 8 Critical link events OAMPDU transmission Type Description frequencies Link Fault Peer link signal is lost. Once per second A power failure or other unexpected error Dying Gasp Non-stop...

  • Page 13: Configuring Basic Ethernet Oam Functions

    Configuring basic Ethernet OAM functions For Ethernet OAM connection establishment, an Ethernet OAM entity operates in active mode or passive mode. Only an Ethernet OAM entity in active mode can initiate connection establishment. After Ethernet OAM is enabled on an Ethernet port, according to its Ethernet OAM mode, the Ethernet port establishes an Ethernet OAM connection with its peer port.

  • Page 14: Configuring Link Monitoring

    Configuring link monitoring After Ethernet OAM connections are established, the link monitoring periods and thresholds configured in this section take effect on all Ethernet ports automatically. Configuring errored symbol event detection Step Command Remarks Enter system view. system-view Configure the errored Optional.

  • Page 15: Configuring Ethernet Oam Remote Loopback

    To configure errored frame seconds event detection: Step Command Remarks Enter system view. system-view Configure the errored frame Optional. oam errored-frame-seconds seconds event detection period period-value 60 second by default. interval. Configure the errored frame Optional. oam errored-frame-seconds seconds event triggering threshold threshold-value 1 by default.

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

    Task Command Remarks Enable Ethernet OAM remote oam loopback interface Disabled by default. loopback on a specific port. interface-type interface-number To enable Ethernet OAM remote loopback in system view: Step Command Remarks Enter system view. system-view Enable Ethernet OAM oam loopback interface remote loopback on a Disabled by default.

  • Page 17: Ethernet Oam Configuration Example

    Task Command Remarks display oam critical-event [ interface interface-type Display the statistics on critical events after an Ethernet OAM interface-number ] [ | { begin | Available in any view connection is established. exclude | include } regular-expression ] display oam link-event { local | Display the statistics on Ethernet remote } [ interface OAM link error events after an...
  • Page 18 # Configure Ethernet 1/0/1 to operate in active Ethernet OAM mode (the default) and enable Ethernet OAM for it. <DeviceB> system-view [DeviceB] interface ethernet 1/0/1 [DeviceA-Ethernet1/0/1] oam mode active [DeviceB-Ethernet1/0/1] oam enable [DeviceB-Ethernet1/0/1] quit Verify the configuration: Use the display oam configuration command to display the Ethernet OAM configuration. For example: # Display the Ethernet OAM configuration on Device A.
  • Page 19 Errored Frame Threshold : 10 Errored Frame : 13 Error Running Total : 350 Event Running Total : 17 The output shows that 350 errors occurred since Ethernet OAM was enabled on Device A, 17 of which are caused by error frames. The link is unstable.

  • Page 20: Configuring Cfd (Available Only On The Hpe 3100 V2 Ei)

    Configuring CFD (available only on the HPE 3100 v2 EI) 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.
  • Page 21 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 22: Cfd Functions

    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 MA. It lists all MEPs configured on different devices in the same MA. The MEPs all have unique MEP IDs.

  • Page 23: Protocols And Standards

    target MEP, the link state between the two can be verified. LBM frames and LBR frames are unicast frames. LT is similar to traceroute. It identifies the path between the source MEP and the target MP. This function is implemented in the following way—the source MEP sends the linktrace messages (LTMs) to the target MP.

  • Page 24: Cfd Configuration Task List

    CFD configuration task list For CFD to operate properly, design the network by performing the following tasks: • Grade the MDs in the entire network and define the boundary of each MD. • Assign a name for each MD. Make sure the same MD has the same name on different devices. •...

  • Page 25: Enabling Cfd

    Enabling CFD Enable CFD before you perform other configuration tasks. To enable CFD on a device: Step Command Remarks Enter system view. system-view Enable CFD. cfd enable By default, CFD is disabled. Configuring the CFD protocol version Three CFD protocol versions are available: IEEE 802.1ag draft5.2 version, IEEE 802.1ag draft5.2 interim version, and IEEE 802.1ag standard version.

  • Page 26: Configuring Meps

    Step Command Remarks cfd md md-name level Create an MD. By default, no MD is created. level-value cfd ma ma-name md md-name Create an MA. By default, no MA is created. vlan vlan-id Create a service instance cfd service-instance instance-id By default, no service instance with the MD name md md-name ma ma-name...

  • Page 27: Configuring Cfd Functions

    Any of the following actions or cases can cause MIPs to be created or deleted after you configure the cfd mip-rule command: • Enabling or disabling CFD (use the cfd enable command). • Creating or deleting the MEPs on a port. •...

  • Page 28: Configuring Lb On Meps

    Step Command Remarks cfd cc interval Configure the interval field Optional. interval-value value in the CCM messages service-instance By default, the interval field value is 4. sent by MEPs. instance-id Enter Layer 2 Ethernet interface interface-type interface view. interface-number cfd cc service-instance Enable CCM sending on a By default, CCM sending on a MEP is instance-id mep mep-id...

  • Page 29: Configuring Ais

    Configuring AIS The AIS function suppresses the number of error alarms reported by MEPs. Configuration guidelines • To have a MEP in the service instance send AIS frames, configure the AIS frame transmission level to be higher than the MD level of the MEP. •...

  • Page 30: Configuring Two-Way Dm

    • To view the test result, use the display cfd dm one-way history command on the target MEP. Configuration procedure To configure one-way DM: Step Command Remarks Enter system view. system-view cfd dm one-way service-instance instance-id mep mep-id { target-mac By default, one-way DM is Configure one-way DM.

  • Page 31: Displaying And Maintaining Cfd

    Displaying and maintaining CFD Task Command Remarks display cfd status [ | { begin | Display CFD and AIS status. exclude | include } Available in any view regular-expression ] display cfd version [ | { begin | Display the CFD protocol version. exclude | include } Available in any view regular-expression ]...

  • Page 32: Cfd Configuration Example

    Task Command Remarks display cfd dm one-way history [ service-instance instance-id Display the one-way DM result on [ mep mep-id ] ] [ | { begin | Available in any view the specified MEP. exclude | include } regular-expression ] display cfd tst [ service-instance instance-id Display the TST result on the...
  • Page 33 Figure 6 Network diagram Port Inward-facing MEP Outward-facing MEP MIP with explicit rule MIP with default rule Eth1/0/2 Eth1/0/2 Eth1/0/2 Eth1/0/2 Eth1/0/1 Eth1/0/3 Eth1/0/1 Eth1/0/3 Eth1/0/1 Eth1/0/3 Eth1/0/1 Eth1/0/3 Device A Device B Device C Device D Eth1/0/4 Eth1/0/4 Eth1/0/4 Eth1/0/4 MD_B Eth1/0/2...
  • Page 34 Configure MEPs: # On Device A, configure a MEP list in service instance 1. Create and enable inward-facing MEP 1001 in service instance 1 on Ethernet 1/0/1. [DeviceA] cfd meplist 1001 4002 5001 service-instance 1 [DeviceA] interface ethernet 1/0/1 [DeviceA-Ethernet1/0/1] cfd mep 1001 service-instance 1 inbound [DeviceA-Ethernet1/0/1] cfd mep service-instance 1 mep 1001 enable [DeviceA-Ethernet1/0/1] quit # On Device B, configure a MEP list in service instances 1 and 2 respectively.

  • Page 35: Verifying The Configuration

    [DeviceB] interface ethernet 1/0/3 [DeviceB-Ethernet1/0/3] cfd cc service-instance 2 mep 2001 enable [DeviceB-Ethernet1/0/3] quit # On Device D, enable the sending of CCM frames for MEP 4001 in service instance 2 on Ethernet 1/0/1. Enable the sending of CCM frames for MEP 4002 in service instance 1 on Ethernet 1/0/3.
  • Page 36 [DeviceA] cfd slm service-instance 1 mep 1001 target-mep 4002 Reply from 0010-FC00-6514 Far-end frame loss: 10 Near-end frame loss: 20 Reply from 0010-FC00-6514 Far-end frame loss: 40 Near-end frame loss: 40 Reply from 0010-FC00-6514 Far-end frame loss: 0 Near-end frame loss: 10 Reply from 0010-FC00-6514 Far-end frame loss: 30 Near-end frame loss: 30...
  • Page 37 After the CC function obtains the status information of the entire network, use the TST function to test the bit errors of a link. For example: # Test the bit errors on the link from MEP 1001 to MEP 4002 in service instance 1 on Device A. [DeviceA] cfd tst service-instance 1 mep 1001 target-mep 4002 Info: TST process is done.

  • Page 38: 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 39: How Dldp Works

    failure of other protocols such as STP. If both ends of a link are operating normally at the physical layer, DLDP detects whether the link is correctly connected at the link layer and whether the two ends can exchange packets properly. This is beyond the capability of the auto-negotiation mechanism at the physical layer.
  • Page 40 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 41 Table 12 DLDP mode and neighbor entry aging Detecting a neighbor after the Removing the neighbor Triggering the DLDP mode corresponding entry immediately after Enhanced timer after an neighbor entry ages the Entry timer expires Entry timer expires Normal DLDP mode Enhanced DLDP mode...
  • Page 42 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. •...
  • Page 43 Packet type Processing procedure packet If the corresponding neighbor entry already exists, resets the Entry timer. Determines If yes, performs no processing. whether or not the Flush packet local port is in If no, removes the corresponding neighbor entry (if any). Disable state If the corresponding neighbor entry does not exist, creates the neighbor entry, transits to Probe state, and returns Echo...
  • Page 44 Table 16 DLDP process when no echo packet is received from the neighbor No echo packet received from the Processing procedure neighbor In normal mode, no echo packet is DLDP sets the state of the corresponding neighbor to received when the Echo timer expires. unidirectional, and then checks the state of other neighbors: •...

  • Page 45: Dldp Configuration Task List

    DLDP configuration task list For DLDP to work properly, enable DLDP on both sides and make sure these settings are consistent: the interval to send Advertisement packets, DLDP authentication mode, and password. DLDP does not process any link aggregation control protocol (LACP) events. The links in an aggregation are treated as individual links in DLDP.

  • Page 46: Setting Dldp Mode

    Step Command Remarks Enter Layer 2 Ethernet interface view: Use either approach. interface interface-type Enter Layer 2 Ethernet Configurations made in Layer 2 Ethernet interface-number interface view or port interface view apply to the current port only. group view. Enter port group view: Configurations made in port group view port-group manual apply to all ports in the port group.

  • Page 47: Setting The Delaydown Timer

    NOTE: • The interval for sending Advertisement packets applies to all DLDP-enabled ports. • To enable DLDP to operate properly, make sure the intervals for sending Advertisement packets on both sides of a link are the same. Setting the delaydown timer On some ports, when the Tx line fails, the port goes down and then comes up again, causing optical signal jitters on the Rx line.

  • Page 48: Configuring Dldp Authentication

    Configuring DLDP authentication You can guard your network against attacks and malicious probes by configuring an appropriate DLDP authentication mode, which can be simple authentication or MD5 authentication. If your network is safe, you can choose not to authenticate. To enable DLDP to operate properly, make sure that DLDP authentication modes and passwords on both sides of a link are the same.

  • Page 49: Displaying And Maintaining Dldp

    Step Command Remarks Enter Layer 2 Ethernet interface Use either approach. view: Configurations made in Layer 2 interface interface-type Enter Layer 2 Ethernet Ethernet interface view apply to the interface-number interface view or port group current port only. Configurations view. Enter port group view: made in port group view apply to all port-group manual...
  • Page 50 Figure 9 Network diagram Correct fiber connection Cross-connected fibers Device A Device A GE1/0/25 GE1/0/26 GE1/0/25 GE1/0/26 GE1/0/25 GE1/0/26 GE1/0/25 GE1/0/26 Device B Device B Ethernet Fiber link Tx end Rx end optical port Configuration procedure Configure Device A: # Enable DLDP globally. <DeviceA>...
  • Page 51 <DeviceB> system-view [DeviceB] dldp enable # Configure GigabitEthernet 1/0/25 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it. [DeviceB] interface gigabitethernet 1/0/25 [DeviceB-GigabitEthernet1/0/25] duplex full [DeviceB-GigabitEthernet1/0/25] speed 1000 [DeviceB-GigabitEthernet1/0/25] dldp enable [DeviceB-GigabitEthernet1/0/25] quit # Configure GigabitEthernet 1/0/26 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.
  • Page 52 Neighbor state : two way Neighbor aged time : 12 The output shows that both GigabitEthernet 1/0/25 and GigabitEthernet 1/0/26 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 53: Manually Shutting Down Unidirectional Links

    Manually shutting down unidirectional links Network requirements • As shown in Figure 10, Device A and Device B are connected with two fiber pairs. • Configure DLDP to send information when a unidirectional link is detected, to remind the network administrator to manually shut down the faulty port. Figure 10 Network diagram Correct fiber connection Cross-connected fibers...
  • Page 54 # Set the DLDP mode to enhanced. [DeviceA] dldp work-mode enhance # Set the port shutdown mode to manual. [DeviceA] dldp unidirectional-shutdown manual Configure Device B: # Enable DLDP globally. <DeviceB> system-view [DeviceB] dldp enable # Configure GigabitEthernet 1/0/25 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.
  • Page 55 Interface GigabitEthernet1/0/26 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 : 60 Neighbor state : two way Neighbor aged time : 12 The output shows that both GigabitEthernet 1/0/25 and GigabitEthernet 1/0/26 are in Advertisement state, which means both links are bidirectional.

  • Page 56: Troubleshooting Dldp

    The output shows that the link status of both GigabitEthernet 1/0/25 and GigabitEthernet 1/0/26 is down. Assume that in this example, the unidirectional links are caused by cross-connected fibers. Correct the fiber connections, and then bring up the ports shut down earlier. # On Device A, bring up GigabitEthernet 1/0/25 and GigabitEthernet 1/0/26: [DeviceA-GigabitEthernet1/0/26] undo shutdown [DeviceA-GigabitEthernet1/0/26]...

  • Page 57: Configuring Rrpp

    Configuring RRPP This Switch Series cannot be configured as the master node on an RRPP ring. 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.
  • Page 58 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. An RRPP domain contains one or multiple RRPP rings, one serving as the primary ring and the others serving as subrings.

  • Page 59: Rrppdus

    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. When an RRPP ring is in Health state, the secondary port of the master node will logically deny data VLANs and permit only the packets of the control VLANs.

  • Page 60: Rrpp Timers

    Type Description The assistant-edge node initiates Major-Fault packets to notify the edge node Major-Fault of SRPT failure when an SRPT between edge node and assistant-edge node is torn down. NOTE: RRPPDUs of subrings are transmitted as data packets in the primary ring, and RRPPDUs of the primary ring can only be transmitted within the primary ring.

  • Page 61: Typical Rrpp Networking

    Ring recovery The master node may find that the ring is restored after a period of time after the ports belonging to the RRPP domain on the transit nodes, the edge nodes, or the assistant-edge nodes are brought up again. A temporary loop may arise in the data VLAN during this period. As a result, broadcast storm occurs.
  • Page 62 Figure 12 Schematic diagram for a single-ring network Tangent rings As shown in Figure 13, two or more rings are in the network topology and only one common node exists between rings. You must define an RRPP domain for each ring. Figure 13 Schematic diagram for a tangent-ring network Intersecting rings As shown in...
  • Page 63 Figure 14 Schematic diagram for an intersecting-ring network Dual homed rings As shown in Figure 15, two or more rings are in the network topology and two similar 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 64: Protocols And Standards

    Figure 16 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 17, Ring 1 is the primary ring, and Ring 2 is the subring in both Domain 1 and Domain 2.

  • Page 65: Rrpp Configuration Task List

    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. Complete the following tasks to configure RRPP: Task Remarks...

  • Page 66: Configuring Control Vlans

    Configuring control VLANs Before configuring RRPP rings in an RRPP domain, configure the same control VLANs for all nodes in the RRPP domain first. When configuring control VLANs for an RRPP domain, you only need to configure the primary control VLAN. The system automatically configures the secondary control VLAN, and it uses the primary control VLAN ID plus 1 as the secondary control VLAN ID.

  • Page 67: Configuring Rrpp Rings

    Step Command Remarks 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. Optional. Use either approach. All VLANs in an MST region are Approach 1: mapped to MSTI 0 (the CIST) by instance instance-id vlan...

  • Page 68: Configuring Rrpp Ports

    Specifying a master node Select another HPE device for this configuration task. For more information, see the configuration guide of the device. Specifying a transit node Perform this configuration on a device to be configured as a transit node.

  • Page 69: Activating An Rrpp Domain

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

  • Page 70: Configuring An Rrpp Ring Group

    • Enable the primary ring of an RRPP domain before enabling the subrings of the RRPP domain. • Disable the primary ring of an RRPP domain after disabling all subrings of the RRPP domain. Perform this operation on all nodes in the RRPP domain. To activate an RRPP domain: Step Command...

  • Page 71: Displaying And Maintaining Rrpp

    RRPP configuration examples This Switch Series cannot be configured as the master node on the RRPP ring. The master nodes in the following configuration examples are configured on the HPE 3600 v2 Switch Series. Single ring configuration example Networking requirements...
  • Page 72 Figure 18 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 Ethernet 1/0/1 and Ethernet...
  • Page 73 # Configure Device A as the master node of primary ring 1, with Ethernet 1/0/1 as the primary port and Ethernet 1/0/2 as the secondary port, and enable ring 1. [DeviceA-rrpp-domain1] ring 1 node-mode master primary-port ethernet 1/0/1 secondary-port ethernet 1/0/2 level 0 [DeviceA-rrpp-domain1] ring 1 enable [DeviceA-rrpp-domain1] quit # Enable RRPP.

  • Page 74: Intersecting Ring Configuration Example

    Configure Device D: The configuration on Device D is similar to that on Device B and is not shown here. Verify the configuration: Use the display command to view RRPP configuration and operational information on each device. Intersecting ring configuration example Networking requirements As shown in Figure...
  • Page 75 [DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit # Cancel the physical state change suppression interval setting on Ethernet 1/0/1 and Ethernet 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 30. [DeviceA] interface ethernet 1/0/1 [DeviceA-Ethernet1/0/1] undo link-delay [DeviceA-Ethernet1/0/1] undo stp enable...
  • Page 76 [DeviceB-Ethernet1/0/1] port link-type trunk [DeviceB-Ethernet1/0/1] port trunk permit vlan 1 to 30 [DeviceB-Ethernet1/0/1] quit [DeviceB] interface ethernet 1/0/2 [DeviceB-Ethernet1/0/2] undo link-delay [DeviceB-Ethernet1/0/2] undo stp enable [DeviceB-Ethernet1/0/2] port link-type trunk [DeviceB-Ethernet1/0/2] port trunk permit vlan 1 to 30 [DeviceB-Ethernet1/0/2] quit [DeviceB] interface ethernet 1/0/3 [DeviceB-Ethernet1/0/3] undo link-delay [DeviceB-Ethernet1/0/3] undo stp enable [DeviceB-Ethernet1/0/3] port link-type trunk...
  • Page 77 [DeviceC-Ethernet1/0/1] port link-type trunk [DeviceC-Ethernet1/0/1] port trunk permit vlan 1 to 30 [DeviceC-Ethernet1/0/1] quit [DeviceC] interface ethernet 1/0/2 [DeviceC-Ethernet1/0/2] undo link-delay [DeviceC-Ethernet1/0/2] undo stp enable [DeviceC-Ethernet1/0/2] port link-type trunk [DeviceC-Ethernet1/0/2] port trunk permit vlan 1 to 30 [DeviceC-Ethernet1/0/2] quit [DeviceC] interface ethernet 1/0/3 [DeviceC-Ethernet1/0/3] undo link-delay [DeviceC-Ethernet1/0/3] undo stp enable [DeviceC-Ethernet1/0/3] port link-type trunk...
  • Page 78 [DeviceD-Ethernet1/0/1] port link-type trunk [DeviceD-Ethernet1/0/1] port trunk permit vlan 1 to 30 [DeviceD-Ethernet1/0/1] quit [DeviceD] interface ethernet 1/0/2 [DeviceD-Ethernet1/0/2] undo link-delay [DeviceD-Ethernet1/0/2] undo stp enable [DeviceD-Ethernet1/0/2] port link-type trunk [DeviceD-Ethernet1/0/2] port trunk permit vlan 1 to 30 [DeviceD-Ethernet1/0/2] quit # Create RRPP domain 1. Configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

  • Page 79: Dual Homed Rings Configuration Example

    # Create RRPP domain 1. Configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceE] rrpp domain 1 [DeviceE-rrpp-domain1] control-vlan 4092 [DeviceE-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device E as the master node of subring 2, with Ethernet 1/0/1 as the primary port and Ethernet 1/0/2 as the secondary port, and enable ring 2.
  • Page 80 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 Ethernet 1/0/1 through...
  • Page 81 [DeviceA-Ethernet1/0/3] undo stp enable [DeviceA-Ethernet1/0/3] qos trust dot1p [DeviceA-Ethernet1/0/3] port link-type trunk [DeviceA-Ethernet1/0/3] port trunk permit vlan 1 to 30 [DeviceA-Ethernet1/0/3] quit [DeviceA] interface ethernet 1/0/4 [DeviceA-Ethernet1/0/4] undo link-delay [DeviceA-Ethernet1/0/4] undo stp enable [DeviceA-Ethernet1/0/4] qos trust dot1p [DeviceA-Ethernet1/0/4] port link-type trunk [DeviceA-Ethernet1/0/4] port trunk permit vlan 1 to 30 [DeviceA-Ethernet1/0/4] quit # Create RRPP domain 1.
  • Page 82 [DeviceB-Ethernet1/0/1] undo stp enable [DeviceB-Ethernet1/0/1] port link-type trunk [DeviceB-Ethernet1/0/1] port trunk permit vlan 1 to 30 [DeviceB-Ethernet1/0/1] quit [DeviceB] interface ethernet 1/0/2 [DeviceB-Ethernet1/0/2] undo link-delay [DeviceB-Ethernet1/0/2] undo stp enable [DeviceB-Ethernet1/0/2] port link-type trunk [DeviceB-Ethernet1/0/2] port trunk permit vlan 1 to 30 [DeviceB-Ethernet1/0/2] quit [DeviceB] interface ethernet 1/0/3 [DeviceB-Ethernet1/0/3] undo link-delay...
  • Page 83 [DeviceC-mst-region] instance 1 vlan 1 to 30 [DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit # Configure the device to trust the 802.1p priority of packets globally. [DeviceC] qos trust dot1p # Cancel the physical state change suppression interval setting on Ethernet 1/0/1 through Ethernet 1/0/4, and disable the spanning tree feature.
  • Page 84 [DeviceC-rrpp-domain1] ring 5 enable [DeviceC-rrpp-domain1] quit # Enable RRPP. [DeviceC] rrpp enable Configure Device D: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. <DeviceD> system-view [DeviceD] vlan 1 to 30 [DeviceD] stp region-configuration [DeviceD-mst-region] instance 1 vlan 1 to 30 [DeviceD-mst-region] active region-configuration...
  • Page 85 [DeviceD-rrpp-domain1] ring 1 node-mode transit primary-port ethernet 1/0/1 secondary-port ethernet 1/0/2 level 0 [DeviceD-rrpp-domain1] ring 1 enable # Configure Device D as the edge node of subring 4, with Ethernet 1/0/3 as the edge port, and enable subring 4. [DeviceD-rrpp-domain1] ring 4 node-mode edge edge-port ethernet 1/0/3 [DeviceD-rrpp-domain1] ring 4 enable # Configure Device D as the edge node of subring 5, with Ethernet 1/0/4 as the edge port, and enable subring 5.
  • Page 86 [DeviceE-rrpp-domain1] ring 2 enable [DeviceE-rrpp-domain1] quit # Enable RRPP. [DeviceE] rrpp enable Configure Device F: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. <DeviceF> system-view [DeviceF] vlan 1 to 30 [DeviceF] stp region-configuration [DeviceF-mst-region] instance 1 vlan 1 to 30 [DeviceF-mst-region] active region-configuration...
  • Page 87 [DeviceG-mst-region] instance 1 vlan 1 to 30 [DeviceG-mst-region] active region-configuration [DeviceG-mst-region] quit # Cancel the physical state change suppression interval setting on Ethernet 1/0/1 and Ethernet 1/0/2, disable the spanning tree feature, and set the trusted packet priority type to 802.1p priority.

  • Page 88: Intersecting-Ring Load Balancing Configuration Example

    [DeviceH-Ethernet1/0/1] port link-type trunk [DeviceH-Ethernet1/0/1] port trunk permit vlan 1 to 30 [DeviceH-Ethernet1/0/1] quit [DeviceH] interface ethernet 1/0/2 [DeviceH-Ethernet1/0/2] undo link-delay [DeviceH-Ethernet1/0/2] undo stp enable [DeviceH-Ethernet1/0/2] qos trust dot1p [DeviceH-Ethernet1/0/2] port link-type trunk [DeviceH-Ethernet1/0/2] port trunk permit vlan 1 to 30 [DeviceH-Ethernet1/0/2] quit # Create RRPP domain 1.
  • Page 89 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 90 # 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 Ethernet 1/0/1 as the primary port and Ethernet 1/0/2 as the secondary port, and enable ring 1.
  • Page 91 [DeviceB-Ethernet1/0/2] port trunk permit vlan 1 2 [DeviceB-Ethernet1/0/2] quit # Cancel the physical state change suppression interval setting on Ethernet 1/0/3, and disable the spanning tree feature. Configure the port as a trunk port, and assign it to VLAN 2. [DeviceB] interface ethernet 1/0/3 [DeviceB-Ethernet1/0/3] undo link-delay [DeviceB-Ethernet1/0/3] undo stp enable...
  • Page 92 [DeviceB] rrpp enable Configure Device C: # Create VLANs 1 and 2, map VLAN 1 to MSTI 1 and VLAN 2 to MSTI 2, and activate MST region configuration. <DeviceC> system-view [DeviceC] vlan 1 to 2 [DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 1 [DeviceC-mst-region] instance 2 vlan 2 [DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit...
  • Page 93 [DeviceC] rrpp domain 1 [DeviceC-rrpp-domain1] control-vlan 100 [DeviceC-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device C as the transit node of primary ring 1 in RRPP domain 1, with Ethernet 1/0/1 as the primary port and Ethernet 1/0/2 as the secondary port, and enable ring 1. [DeviceC-rrpp-domain1] ring 1 node-mode transit primary-port ethernet 1/0/1 secondary-port ethernet 1/0/2 level 0 [DeviceC-rrpp-domain1] ring 1 enable...
  • Page 94 [DeviceD-Ethernet1/0/1] port trunk permit vlan 1 2 [DeviceD-Ethernet1/0/1] quit [DeviceD] interface ethernet 1/0/2 [DeviceD-Ethernet1/0/2] undo link-delay [DeviceD-Ethernet1/0/2] undo stp enable [DeviceD-Ethernet1/0/2] port link-type trunk [DeviceD-Ethernet1/0/2] port trunk permit vlan 1 2 [DeviceD-Ethernet1/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.
  • Page 95 [DeviceE-Ethernet1/0/1] port link-type trunk [DeviceE-Ethernet1/0/1] undo port trunk permit vlan 1 [DeviceE-Ethernet1/0/1] port trunk permit vlan 2 [DeviceE-Ethernet1/0/1] port trunk pvid vlan 2 [DeviceE-Ethernet1/0/1] quit [DeviceE] interface ethernet 1/0/2 [DeviceE-Ethernet1/0/2] undo link-delay [DeviceE-Ethernet1/0/2] undo stp enable [DeviceE-Ethernet1/0/2] qos trust dot1p [DeviceE-Ethernet1/0/2] port link-type trunk [DeviceE-Ethernet1/0/2] undo port trunk permit vlan 1 [DeviceE-Ethernet1/0/2] port trunk permit vlan 2...

  • Page 96: Troubleshooting

    [DeviceF-Ethernet1/0/2] qos trust dot1p [DeviceF-Ethernet1/0/2] port link-type trunk [DeviceF-Ethernet1/0/2] port trunk permit vlan 1 [DeviceF-Ethernet1/0/2] quit # Create RRPP domain 1. Configure VLAN 100 as the primary control VLAN, and configure the VLAN mapped to MSTI 1 as the protected VLAN. [DeviceF] rrpp domain 1 [DeviceF-rrpp-domain1] control-vlan 100 [DeviceF-rrpp-domain1] protected-vlan reference-instance 1...
  • Page 97 • Use the display rrpp brief command to examine whether the domain ID and primary control VLAN ID are the same for all nodes. If they are not, set the same domain ID and primary control VLAN ID for the nodes. •...

  • Page 98: Configuring Smart Link (Available Only On The Hpe 3100 V2 Ei)

    Configuring Smart Link (available only on the HPE 3100 v2 EI) 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 99: Terminology

    • 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 100: Smart Link Collaboration Mechanisms

    NOTE: When a port switches to the forwarding state, the system outputs log information to notify the user of the port state change. Topology change mechanism Because link switchover can outdate the MAC address forwarding entries and ARP/ND entries on all devices, you need a forwarding entry update mechanism to ensure proper transmission.

  • Page 101: Configuring A Smart Link Device

    An associated device is a device that supports Smart Link and receives flush messages sent from the specified control VLAN. Device A, Device B, and Device E in Figure 22 are examples of associated devices. Complete the following tasks to configure Smart Link: Task Remarks Configuring protected VLANs for a smart link...

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

    Step Command Remarks Optional. Use either approach. All VLANs in an MST region are Approach 1: Configure the mapped to CIST (MSTI 0) by instance instance-id vlan vlan-list VLAN-to-instance mapping default. Approach 2: table. Not required in PVST mode. vlan-mapping modulo modulo For more information about the commands, see Layer 2—LAN Switching Command Reference.

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

    Step Command Enter Layer 2 Ethernet interface view or layer 2 interface interface-type interface-number aggregate interface view. Configure member ports for a smart link group. port smart-link group group-id { master | slave } Configuring role preemption for a smart link group Step Command Remarks...

  • Page 104: 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 105: 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 106: Control Vlan

    [DeviceC-Ethernet1/0/1] port trunk permit vlan 1 to 30 [DeviceC-Ethernet1/0/1] quit [DeviceC] interface ethernet 1/0/2 [DeviceC-Ethernet1/0/2] shutdown [DeviceC-Ethernet1/0/2] undo stp enable [DeviceC-Ethernet1/0/2] port link-type trunk [DeviceC-Ethernet1/0/2] port trunk permit vlan 1 to 30 [DeviceC-Ethernet1/0/2] quit # Create smart link group 1, and configure all VLANs mapped to MSTI 1 as the protected VLANs.
  • Page 107 [DeviceD-Ethernet1/0/2] port trunk permit vlan 1 to 30 [DeviceD-Ethernet1/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 Ethernet 1/0/1 as the master port and Ethernet 1/0/2 as the slave port for smart link group 1.
  • Page 108 [DeviceB-Ethernet1/0/3] quit Configure Device E: # Create VLANs 1 through 30. <DeviceE> system-view [DeviceE] vlan 1 to 30 # Configure Ethernet 1/0/1 as a trunk port, and assign it to VLANs 1 through 30. Enable flush message receiving on it, and configure VLAN 10 and VLAN 20 as the receive control VLANs. [DeviceE] interface ethernet 1/0/1 [DeviceE-Ethernet1/0/1] port link-type trunk [DeviceE-Ethernet1/0/1] port trunk permit vlan 1 to 30...

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

    You can use the display smart-link group command to display the smart link group configuration on a device. # Display the smart link group configuration on Device C. [DeviceC] display smart-link group 1 Smart link group 1 information: Device ID: 000f-e23d-5af0 Preemption mode: NONE Preemption delay: 1(s) Control VLAN: 10...
  • Page 110 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 111 [DeviceC-smlk-group2] preemption mode role [DeviceC-smlk-group2] flush enable control-vlan 110 [DeviceC-smlk-group2] quit # Bring up Ethernet 1/0/1 and Ethernet 1/0/2 again. [DeviceC] interface ethernet 1/0/1 [DeviceC-Ethernet1/0/1] undo shutdown [DeviceC-Ethernet1/0/1] quit [DeviceC] interface ethernet 1/0/2 [DeviceC-Ethernet1/0/2] undo shutdown [DeviceC-Ethernet1/0/2] quit Configure Device B: # Create VLAN 1 through VLAN 200.
  • Page 112 [DeviceD-Ethernet1/0/2] undo stp enable [DeviceD-Ethernet1/0/2] smart-link flush enable control-vlan 10 110 [DeviceD-Ethernet1/0/2] quit Configure Device A: # Create VLAN 1 through VLAN 200. <DeviceA> system-view [DeviceA] vlan 1 to 200 # Configure Ethernet 1/0/1 and Ethernet 1/0/2 as trunk ports and assign them to VLANs 1 through 200.
  • Page 113 Ethernet1/0/1 SLAVE STANDBY 17:45:20 2010/02/21 You can 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 : Ethernet1/0/2 Receiving time of the last flush packet : 16:25:21 2010/02/21...

  • Page 114: Configuring Monitor Link (Available Only On The Hpe 3100 V2 Ei)

    Configuring Monitor Link (available only on the HPE 3100 v2 EI) 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...

  • Page 115: How Monitor Link Works

    • Downlink ports are the monitoring ports. The state of the downlink ports in a monitor link group adapts to that of the monitor link group. When the state of a monitor link group changes, the state of its member downlink ports change accordingly. The state of the downlink ports in a monitor link group is always consistent with that of the monitor link group.

  • Page 116: Displaying And Maintaining Monitor Link

    Device B (or Device D) fails, Device C can sense the link fault and perform uplink switchover in the smart link group. For more information about Smart Link, see "Configuring Smart Link (available only on the HPE 3100 v2 EI)."...
  • Page 117 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 Ethernet 1/0/1 and Ethernet 1/0/2 separately, configure them as trunk ports, and assign them to VLANs 1 through 30.
  • Page 118 [DeviceA-Ethernet1/0/2] quit Configure Device B: # Create VLANs 1 through 30. <DeviceB> system-view [DeviceB] vlan 1 to 30 # Configure Ethernet 1/0/1 as a trunk port, assign it to VLANs 1 through 30, and enable flush message receiving on it. [DeviceB] interface ethernet 1/0/1 [DeviceB-Ethernet1/0/1] port link-type trunk [DeviceB-Ethernet1/0/1] port trunk permit vlan 1 to 30...
  • Page 119 [DeviceD-mtlk-group1] port ethernet 1/0/1 uplink [DeviceD-mtlk-group1] port ethernet 1/0/2 downlink [DeviceD-mtlk-group1] quit Verify the configuration: Use the display monitor-link group command to display the monitor link group information on devices. For example, when Ethernet 1/0/2 on Device A goes down due to a link fault: # Display information about monitor link group 1 on Device B.

  • Page 120: Document Conventions And Icons

    Document conventions and icons Conventions This section describes the conventions used in the documentation. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown.

  • Page 121: Network Topology Icons

    Network topology icons Convention Description Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.

  • Page 122: Support And Other Resources

    Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: www.hpe.com/support/hpesc Information to collect •...

  • Page 123: Websites

    For more information and device support details, go to the following website: www.hpe.com/info/insightremotesupport/docs Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title,...
  • Page 124 part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.

  • Page 125: Index

    Index A C D E H M N O R S T DLDP configuration task list,40 DLDP overview,33 Accessing Hewlett Packard Enterprise Support,117 Accessing updates,117 Activating an RRPP domain,64 Enabling DLDP,40 Availability evaluation,1 Ethernet OAM configuration example,12 Availability requirements,1 Ethernet OAM configuration task list,7 Ethernet OAM overview,4...

Table of Contents