Home > HP > Printer > HP 5500 Ei 5500 Si Switch Series Configuration Guide

HP 5500 Ei 5500 Si Switch Series Configuration Guide

Add to Favourites
    Download as PDF Print this page Share this page

    Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    View all the pages
    Page
    of 2513
    Add page 2061 to Favourites
    image text
    Enable zoom 
    							iii 
How Smart Link works ··················\
··················\
··················\
··················\
··················\
················ ··················\
·············· 99 
Smart Link collaboration mechanisms ··················\
··················\
··················\
··················\
··················\
· ··················\
···· 99 
Smart Link configuration task list ··················\
··················\
··················\
··················\
··················\
·· ··················\
··················\
 100 
Configuring a Smart Link device ··················\
··················\
··················\
··················\
··················\
····· ··················\
··············· 100 
Configuration prerequisites ··················\
··················\
··················\
··················\
··················\
········· ··················\
··········· 100 
Configuring protected VLANs for a smart li nk group ··················\
··················\
··················\
··················\
···· ·········· 101 
Configuring member ports  for a smart link group ··················\
··················\
··················\
··················\
······· ············ 102 
Configuring role preemption  for a smart link group··················\
··················\
··················\
··················\
····· ··········· 102 
Enabling the sending  of flush messages ··················\
··················\
··················\
··················\
················ ··················\
· 103 
Configuring the collaboration betw een Smart Link and CC of CFD ··················\
··················\
··················\
········  103 
Configuring an associated device ··················\
··················\
··················\
··················\
··················\
···· ··················\
············· 104 
Configuration prerequisites ··················\
··················\
··················\
··················\
··················\
········· ··················\
··········· 104 
Enabling the receiving  of flush messages ··················\
··················\
··················\
··················\
·············· ··················\
· 104 
Displaying and maintaining Smart Link ··················\
··················\
··················\
··················\
················· ··················\
·········· 104 
Smart Link configuration examples ··················\
··················\
··················\
··················\
··················\
··· ··················\
············· 105 
Single smart link group  configuration example ··················\
··················\
··················\
··················\
········· ·············· 105 
Multiple smart link groups load  sharing configuration example ··················\
··················\
··················\
··········· ··· 109 
Smart Link and CFD collaboration configuration example ··················\
··················\
··················\
··················\
 ····· 113 
Configuring Mo nitor Link ··················\
··················\
··················\
··················\
··················\
············ ··················\
················ 119 
Monitor Link overview ··················\
··················\
··················\
··················\
··················\
··············· ··················\
··················\
···· 119 
Terminology ··················\
··················\
··················\
··················\
··················\
··················\
······· ··················\
··················\
·· 119 
How Monitor Link works ··················\
··················\
··················\
··················\
··················\
·············· ··················\
··········· 120 
Configuring Monitor Link ··················\
··················\
··················\
··················\
··················\
············ ··················\
··················\
·· 120 
Configuration prerequisites ··················\
··················\
··················\
··················\
··················\
········· ··················\
··········· 120 
Creating a monito r link group ··················\
··················\
··················\
··················\
··················\
······· ··················\
········ 120 
Configuring monitor link  group member ports ··················\
··················\
··················\
··················\
··········· ·············· 120 
Displaying and mainta ining Monitor Link ··················\
··················\
··················\
··················\
··············· ··················\
········ 121 
Monitor Link configuration example ··················\
··················\
··················\
··················\
··················\
·· ··················\
············ 121 
Configuring VRRP (available  only on the HP 5500 EI) ··················\
··················\
··················\
··················\
··· ············· 125 
VRRP over view ··················\
··················\
··················\
··················\
··················\
··················\
····· ··················\
··················\
········· 125 
VRRP standard protocol mode ··················\
··················\
··················\
··················\
··················\
········· ··················\
··············· 126 
Introduction to VRRP group  ··················\
··················\
··················\
··················\
··················\
··················\
··················\
···  126 
VRRP timers ··················\
··················\
··················\
··················\
··················\
··················\
······· ··················\
··················\
··· 127 
Packet format ··················\
··················\
··················\
··················\
··················\
··················\
····· ··················\
··················\
·· 128 
Principles of VRRP ··················\
··················\
··················\
··················\
··················\
··················\
··················\
··················  129 
VRRP tracking ··················\
··················\
··················\
··················\
··················\
··················\
··················\
···················\
······  129 
VRRP application (taking IPv4-based VRRP for example) ··················\
··················\
··················\
··················\
· ······· 130 
VRRP load balancing mode ··················\
··················\
··················\
··················\
··················\
············ ··················\
················ 131 
Overview ··················\
··················\
··················\
··················\
··················\
··················\
·········· ··················\
··················\
···· 131 
Assigning virtual MAC addresses ··················\
··················\
··················\
··················\
··················\
····· ··················\
···· 132 
Virtual forwarder ··················\
··················\
··················\
··················\
··················\
··················\
· ··················\
··················\
 134 
Packet types ··················\
··················\
··················\
··················\
··················\
··················\
······ ··················\
··················\
··· 136 
Configuring VRRP for IPv4  ··················\
··················\
··················\
··················\
··················\
··················\
··················\
·············  136 
VRRP for IPv4 configuration task list ··················\
··················\
··················\
··················\
················· ··················\
······· 136 
Configuring a VRRP  operation mode ··················\
··················\
··················\
··················\
··················\
··· ··················\
· 137 
Specifying the type of MAC addresses mapped to virtual IP addresses  ··················\
··················\
··················\
· 137 
Creating a VRRP group and conf iguring virtual IP address ··················\
··················\
··················\
················ ······ 138 
Configuring router priority, preempt ive mode and tracking function ··················\
··················\
··················\
······  140 
Configuring VF tracking  ··················\
··················\
··················\
··················\
··················\
··················\
··················\
········  141 
Configuring VRRP packet attributes ··················\
··················\
··················\
··················\
··················\
·· ··················\
····· 142 
Enabling the trap fu nction for VRRP·················\
··················\
··················\
··················\
··················\
··· ··················\
····· 142 
Displaying and maintaining VRRP for IPv4  ··················\
··················\
··················\
··················\
··················\
·············  143 
Configuring VRRP for IPv6 ··················\
··················\
··················\
··················\
··················\
··················\
··················\
·············  143 
    Add page 2062 to Favourites
    image text
    Enable zoom 
    							iv 
VRRP for IPv6 configuration task list ··················\
··················\
··················\
··················\
················· ··················\
······· 143 
Specifying the type of MAC addresses  mapped to virtual IPv6 addresses ··················\
··················\
··············  144 
Creating a VRRP group and configuring a virtual IPv6 address ··················\
··················\
··················\
············ ·· 144 
Configuring router priority, preempt ive mode and tracking function ··················\
··················\
··················\
······  145 
Configuring VF tracking  ··················\
··················\
··················\
··················\
··················\
··················\
··················\
········  146 
Configuring VRRP packet attributes ··················\
··················\
··················\
··················\
··················\
·· ··················\
····· 147 
Displaying and maintaining VRRP for IPv6  ··················\
··················\
··················\
··················\
··················\
·············  148 
IPv4-based VRRP configuration examples ··················\
··················\
··················\
··················\
················ ··················\
······· 148 
Single VRRP group co nfiguration example ··················\
··················\
··················\
··················\
··············· ················ 148 
VRRP interface tracking  configuration example ··················\
··················\
··················\
··················\
········· ·············· 151 
VRRP with multiple VLANs configuration example  ··················\
··················\
··················\
··················\
··················\
·  155 
VRRP load balancing mode configuration example ··················\
··················\
··················\
··················\
········ ········ 157 
IPv6-based VRRP conf iguration examples ··················\
··················\
··················\
··················\
················ ··················\
······· 167 
Single VRRP group co nfiguration example ··················\
··················\
··················\
··················\
··············· ················ 167 
VRRP interface tracking  configuration example ··················\
··················\
··················\
··················\
········· ·············· 170 
VRRP with multiple VLANs configuration example  ··················\
··················\
··················\
··················\
··················\
·  174 
VRRP load balancing mode configuration example ··················\
··················\
··················\
··················\
········ ········ 178 
Troubleshooting VRRP ·················\
··················\
··················\
··················\
··················\
················· ··················\
··················\
···· 187 
The screen frequently di splays error prompts. ··················\
··················\
··················\
··················\
········· ················ 187 
Multiple masters are present  in the same VRRP group. ··················\
··················\
··················\
··················\
·· ········· 187 
Frequent VRRP state transition.  ··················\
··················\
··················\
··················\
··················\
··················\
···············  187 
Configuring stateful failover (available only on the HP 5500 EI) ··················\
··················\
··················\
··················\
 188 
Stateful failover overview ··················\
··················\
··················\
··················\
··················\
·········· ··················\
··················\
···· 188 
Operating procedure ··················\
··················\
··················\
··················\
··················\
················· ··················\
············· 188 
Stateful failover states ··················\
··················\
··················\
··················\
··················\
············ ··················\
················· 189 
Introduction to stateful  failover configuration ··················\
··················\
··················\
··················\
······· ··················\
··········· 189 
Enabling stateful failover ··················\
··················\
··················\
··················\
··················\
·········· ··················\
··················\
····· 190 
Configuring the backup VLAN ··················\
··················\
··················\
··················\
··················\
········· ··················\
·············· 190 
Displaying and maintaining stateful failover  ··················\
··················\
··················\
··················\
··················\
··················\
·  191 
Stateful failover configuration example ··················\
··················\
··················\
··················\
··············· ··················\
············ 191 
Configuration guidelines ··················\
··················\
··················\
··················\
··················\
············ ··················\
··················\
··· 192 
Configuring BFD (available  only on the HP 5500 EI) ··················\
··················\
··················\
··················\
···· ·············· 193 
BFD overview  ··················\
··················\
··················\
··················\
··················\
··················\
··················\
···················\
···············  193 
How BFD works ··················\
··················\
··················\
··················\
··················\
··················\
····· ··················\
················ 193 
BFD packet format ··················\
··················\
··················\
··················\
··················\
··················\
· ··················\
················ 195 
Supported features ·················\
··················\
··················\
··················\
··················\
··················\
· ··················\
················ 197 
Protocols and standards ··················\
··················\
··················\
··················\
··················\
············· ··················\
············ 197 
Configuring BFD bas ic functions ··················\
··················\
··················\
··················\
··················\
····· ··················\
··············· 198 
Configuration prerequisites ··················\
··················\
··················\
··················\
··················\
········· ··················\
··········· 198 
Configuration procedure ··················\
··················\
··················\
··················\
··················\
············· ··················\
··········· 198 
Displaying and maintaining BFD  ··················\
··················\
··················\
··················\
··················\
··················\
··················\
··  199 
Configuring track ··················\
··················\
··················\
··················\
··················\
··················\
· ··················\
··················\
··· 200 
Track overview ··················\
··················\
··················\
··················\
··················\
··················\
···· ··················\
··················\
········· 200 
Introduction to collaboration ··················\
··················\
··················\
··················\
··················\
······· ··················\
··········· 200 
Collaboration fundamentals ··················\
··················\
··················\
··················\
··················\
·········· ··················\
········· 200 
Collaboration application example  ··················\
··················\
··················\
··················\
··················\
··················\
·······  201 
Track configuration task list ··················\
··················\
··················\
··················\
··················\
··················\
··················\
···········  201 
Associating the track module with a detection module ··················\
··················\
··················\
··················\
·· ················· 202 
Associating trac k with NQA ··················\
··················\
··················\
··················\
··················\
·········· ··················\
········ 202 
Associating track with BFD (avail able only on the HP 5500 EI) ··················\
··················\
··················\
··········· ··· 203 
Associating track with  interface management ··················\
··················\
··················\
··················\
··········· ·············· 203 
Associating the track module with an application module  ··················\
··················\
··················\
··················\
·············· 204 
Associating track with VRRP (available only on the HP 5500 EI) ··················\
··················\
··················\
·········· ·· 204 
    Add page 2063 to Favourites
    image text
    Enable zoom 
    							v 
Associating track with static routing ··················\
··················\
··················\
··················\
················· ··················\
······· 206 
Associating track with PBR (avail able only on the HP 5500 EI) ··················\
··················\
··················\
··········· ··· 207 
Displaying and mainta ining track entries ··················\
··················\
··················\
··················\
·············· ··················\
·········· 208 
Track configuration examples ··················\
··················\
··················\
··················\
··················\
········ ··················\
················· 208 
VRRP-track-NQA collaboration configuration example (the master monitors the uplink) (available only on the 
HP 5500 EI) ··················\
··················\
··················\
··················\
··················\
··················\
······· ··················\
··················\
·· 208
 
Configuring BFD for a VRRP backup to monitor the  master (available only on the HP 5500 EI) ··············· 212 
Configuring BFD for the VRRP master to monitor the uplinks (available only on the HP 5500 EI)  ············· 215 
Static routing-track-NQA collabo ration configuration example ··················\
··················\
··················\
············ ··· 218 
Static routing-Track-BFD collaboration configurati on example (available only on the HP 5500 EI) ··········  223 
VRRP-track-interface management collaboration config uration example (the master monitors the uplink 
interface) (available only on the HP 5500 EI)  ··················\
··················\
··················\
··················\
··················\
········  226
 
Index ··················\
··················\
··················\
··················\
··················\
··················\
············· ··················\
··················\
··········· 230 
    Add page 2064 to Favourites
    image text
    Enable zoom 
    							1 
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  
•   Speeding up fault recovery  
•   Reducing impact of faults on services 
Availability requirements 
Availability requirements fall into three  levels based on purpose and implementation. 
Table 1  Availability requirements 
Level Re
quirement Solution 
1  Decrease system software and 
hardware faults 
•
 Hardware —Simplifying circuit design, enhancing 
production techniques, and performing reliability tests. 
•  Software —Reliability design and test 
2  Protect system functions from being 
affected if faults occur  Device and link redundancy and deployment of switchover 
strategies 
3 
Enable the system to recover as fast 
as possible  Performing fault detection, diagnosis, isolation, and 
recovery technologies 
 
The level 1 availability requirement should be consid
ered during the design and production process of 
network devices. Level 2 should be considered during network design. Level 3 should be considered 
during network deployment, according to the network infrastructure and service characteristics. 
Availability evaluation 
Mean Time Between Failures (MTBF) and Mean Ti me to Repair (MTTR) are used to evaluate the 
availability of a network. 
MTBF 
MTBF is the predicted elapsed time between inherent fail u res  of  a system du ri ng  o peration. I t  i s  t ypic al ly 
in the unit of hours. A higher MTBF means a high availability. 
MTTR 
MTTR is the average time required to repair a failed  system. MTTR in a broad sense also involves spare 
parts management and customer services. 
MTTR = fault detection time + hardware replacement time  + system initialization time + link recovery time 
+ routing time + forwarding recovery time. A smalle r value of each item means a smaller MTTR and a 
higher availability.
    Add page 2065 to Favourites
    image text
    Enable zoom 
    							2 
High availability technologies 
Increasing MTBF or decreasing MTTR can enhance the availability of a network. The high availability 
technologies described in this section meet the level 2 and level 3 high availability requirements by 
decreasing MTTR. 
High availability technologies can be classified as fault detection technologies or protection switchover 
technologies. 
Fault detection technologies 
Fault detection technologies enable detection and di agnosis of network faults. CFD, DLDP, and Ethernet 
OAM are data link layer fault detection technologies.  BFD is a generic fault detection technology that 
can be used at any layer. NQA is used for diagnosis  and evaluation of network quality. Monitor Link and 
Track work along with other high availability tech nologies to detect faults through a collaboration 
mechanism. 
Table 2  Fault detection technologies 
Technolo
gy Introduction  Reference 
CFD 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 Operations, 
Administration and Maintenance (OAM) mechanism used for link 
connectivity detection, fault verification, and fault location.  Configuring CFD in 
High Availability 
Configuration Guide
 
DLDP The Device link detection protocol (DLDP) deals with unidirectional 
links that may occur in a network.
 Upon detecting a unidirectional 
link, DLDP, as configured, can shut down the related port 
automatically or prompt users to  take actions to avoid network 
problems.  Configuring DLDP in 
High Availability 
Configuration Guide
 
Ethernet OAM As a tool monitoring Layer 2 link
 status, Ethernet OAM is mainly 
used to address common link-related  issues on the last mile. You 
can monitor the status of the point-to-point link between two 
directly connected devices by enabling Ethernet OAM on them.  Configuring Ethernet 
OAM in 
High 
Availability 
Configuration Guide  
BFD (available 
only on the HP 
5500 EI) Bidirectional forwarding detection (BFD) provides a single 
mechanism to quickly detect and monitor the connectivity of links 
or IP forwarding in networks. To improve network performance, 
devices must quickly detect communication failures to restore 
communication through backup pa
ths as soon as possible. Configuring BFD in 
High Availability 
Configuration Guide
 
NQA Network Quality Analyzer (NQA) analyzes network 
performance, services and service quality through sending test 
packets, and provides you with network performance and service 
quality parameters such as jitte
r, TCP connection delay, FTP 
connection delay and file transfer rate.  Configuring NQA 
in Network 
Management and 
Monitoring 
Configuration Guide
 
Monitor Link Monitor Link works together with Layer 2 topology protocols to 
adapt the up/down state of a downlink port to the state of an 
uplink port. This feature enables fast link switchover on a 
downstream device in response to the uplink state change on its 
upstream device.  Configuring Monitor 
Link in 
High 
Availability 
Configuration Guide
    Add page 2066 to Favourites
    image text
    Enable zoom 
    							3 
Technology Introduction Reference 
Track The track module is used to implement collaboration between 
different modules. The collaboration here involves three parts: the 
application modules, the track module, and the detection 
modules. These modules collaborate with one another through 
collaboration entries. That is, the detection modules trigger the 
application modules to perform certain operations through the 
track module. More specifically, the detection modules probe the 
link status, network performance and so on, and inform the 
application modules of the detection result through the track 
module. Once notified of networ
k status changes, the application 
modules deal with the changes to avoid communication 
interruption and network performance degradation.  Configuring track in 
High Availability 
Configuration Guide
 
 
Protection switchover technologies 
Protection switchover technologies aim at recovering  network faults. They back up hardware, link, routing, 
and service information for switchover in case of network faults, to ensure continuity of network services. 
Table 3  Protection switchover technologies 
Technolo
gy Introduction  Reference 
Ethernet Link 
Aggregation Ethernet link aggregation, most often simply called link 
aggregation, aggregates multiple 
physical Ethernet links into one 
logical link to increase link bandwidth beyond the limits of any 
one single link. This logical link is  an aggregate link. It allows for 
link redundancy because the member physical links can 
dynamically back up one another.  Configuring Ethernet 
ink aggregation in 
Layer 2—LAN 
Switching 
Configuration Guide  
Smart Link Smart Link is a feature developed to address the slow 
convergence issue with STP. It provides link redundancy as well as 
fast convergence in a dual uplink
 network, allowing the backup 
link to take over quickly when the primary link fails.  Configuring Smart 
Link in 
High 
Availability 
Configuration Guide  
MSTP As a Layer 2 management protoc
ol, the Multiple Spanning Tree 
Protocol (MSTP) eliminates Layer 2 loops by selectively blocking 
redundant links in a network, and in  the mean time, allows for link 
redundancy.  Configuring 
spanning tree in 
Layer 2—LAN 
Switching 
Configuration Guide
 
RRPP 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.  Configuring RRPP in 
High Availability 
Configuration Guide
 
FRR (available 
only on the HP 
5500 EI) Fast Reroute (FRR) provides a quick 
per-link or per-node protection 
on an LSP. In this approach, once  a link or node fails on a path, 
FRR comes up to reroute the path to a new link or node to bypass 
the failed link or node. This can  happen as fast as 50 milliseconds 
minimizing data loss. Protocols such as RIP, OSPF, IS-IS, and static 
routing support this technology.  Layer 3—IP Routing 
Configuration 
Guide
/Configuration 
Guide of the 
corresponding 
protocols
    Add page 2067 to Favourites
    image text
    Enable zoom 
    							4 
Technology Introduction Reference 
GR (available 
only on the HP 
5500 EI) Graceful Restart (GR) ensures the continuity of packet forwarding 
when a protocol, such as BGP, IS-IS, OSPF, IPv6 BGP, IPv6 IS-IS, 
or OSPFv3, restarts or during an active/standby switchover 
process. It needs other devices 
to implement routing information 
backup and recovery.  Layer 3—IP Routing 
Configuration 
Guide
/Configuration 
Guide of the 
corresponding 
protocols 
NSR (available 
only on the HP 
5500 EI)  Non-stop Routing (NSR) is a new feature used to ensure non-stop 
data transmission during an active/standby switchover. Devices 
that have formed an IRF fabric suppo
rt this feature. It backs up IP 
forwarding information from the  master to the slave. Upon an 
active/standby switchover, NSR can complete link state recovery 
and route re-generation without re quiring the cooperation of other 
devices. Only IS-IS supports this feature.  Configuring IS-IS in 
Layer 3—IP Routing 
Configuration Guide
 
Stateful Failover 
(available only 
on the HP 5500 
EI) Two devices back up the services of
 each other to ensure that the 
services on them are consistent.  If one device fails, the other 
device can take over the servic es by using VRRP or dynamic 
routing protocols. Because the other device has already backed 
up the services, service traffic ca n pass through the other device, 
avoiding service interruption.  Configuring stateful 
failover in High 
Availability 
Configuration Guide
 
VRRP (available 
only on the HP 
5500 EI) Virtual Router Redundancy Protocol
 (VRRP) is an error-tolerant 
protocol that provides highly reliable default links on multicast and 
broadcast LANs such as Ethernet, avoiding network interruption 
due to failure of a single link.  Configuring VRRP in 
High Availability 
Configuration Guide
 
 
A single availability technology cannot solve all problems. Therefore, a combination of availability 
technologies, chosen on the basis of detailed analysis of network environments and user requirements, 
should be used to enhance network availability. For  example, access-layer devices should be connected 
to distribution-layer devices over redundant links,  and core-layer devices should be fully meshed. Also, 
network availability should be considered du ring planning prior to building a network.
    Add page 2068 to Favourites
    image text
    Enable zoom 
    							 5 
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: 
•   Link performance monitoring —Monitors the performance indices of a link, including packet loss, 
delay, and jitter, and collects traffic statistics of various types 
•   Fault  detection  and  alarm —Checks the connectivity of a link by sending OAM protocol data units 
(OAMPDUs) and reports to the network administrators when a link error occurs 
•   Remote  loopback —Checks link quality and locates link errors by looping back OAMPDUs 
Ethernet OAMPDUs 
Ethernet OAM works on the data link layer. Ethernet OAM reports the link status by periodically 
exchanging OAMPDUs between devices so that the administrator can effectively manage the network.  
Ethernet OAMPDUs fall into the following types: Info rmation, Event Notification, and Loopback Control. 
Figure 1  Formats of different type s of Ethernet OAMPDUs 
 
 
Table 4 Fields in an OAMPDU 
Field Descri
ption 
Dest addr  Destination MAC address of the Ethernet OAMPDU 
It is a slow protocol multicast address, 0180c2000002. Bridges cannot forward 
slow protocol packets, so Ethernet OAMPDUs cannot be forwarded.  
Source addr 
Source MAC address of the Ethernet OAMPDU 
It is the bridge MAC address of the sending side and is a unicast MAC address. 
Type Type of the encapsulated protocol in the Ethernet OAMPDU 
The value is 0x8809.
    Add page 2069 to Favourites
    image text
    Enable zoom 
    							 6 
Field Description 
Subtype The specific protocol being encapsulated in the Ethernet OAMPDU 
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 OA M enabled is an Ethernet OAM entity or an OAM 
entity. 
 
Table 5  Functions of different types of OAMPDUs 
OAMPDU t
ype Function 
Information OAMPDU  Used for transmitting state information of
 an Ethernet OAM entity—including the 
information about the local device and remote devices and customized 
information—to the remote Ethernet OAM entity and maintaining OAM connections.
 
Event Notification 
OAMPDU  Used by link monitoring to notify the remo
te OAM entity when it detects problems on 
the link in between. 
Loopback Control 
OAMPDU  Used for remote loopback control. 
By inserting the information used to 
enable/disable loopback to a loopback control OAMPDU, you can enable/disable 
loopback on a remote OAM entity.  
 
How Ethernet OAM works 
This section describes the working procedures of Ethernet OAM.  
Ethernet OAM connection establishment 
Ethernet OAM connection is the basis of all th e other Ethernet OAM functions. OAM connection 
establishment is also known as the Discovery phase, where an Ethernet OAM entity discovers remote 
OAM entities and establishe s sessions with them.  
In this phase, interconnected OAM entities determine whether Ethernet OAM connections can be 
established, by exchanging Information OAMPDUs  to notify the peer of their OAM configuration 
information and the OAM capabilities of the local nodes. An Ethernet OAM connection can be 
established between entities that ha ve matching Loopback, link detecting, and link event settings. After 
an Ethernet OAM connection is established, Ethernet OAM takes effect on both sides. 
For Ethernet OAM connection establishment, a devi ce can operate in active Ethernet OAM mode or 
passive Ethernet OAM mode, but a switch role will  be somewhat different depending on the mode.  
Table 6  Active Ethernet OAM mode an d passive Ethernet OAM mode 
Item  Active Ethernet OAM mode
 Passive Ethernet OAM mode 
Initiating OAM Discovery  Available  Unavailable 
Responding to OAM Discovery   Available  Available 
Transmitting Information 
OAMPDUs Available Available
    Add page 2070 to Favourites
    image text
    Enable zoom 
    							 7 
Item Active Ethernet OAM mode Passive Ethernet OAM mode 
Transmitting Event Notification 
OAMPDUs  Available Available 
Transmitting Information 
OAMPDUs without any TLV Available Available 
Transmitting Loopback Control 
OAMPDUs Available Unavailable 
Responding to Loopback Control 
OAMPDUs Available—if both sides operate in 
active OAM mode 
Available 
 
 
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.  
•   No OAM connection can be established between OAM entities operating in passive OAM mode. 
 
After an Ethernet OAM connection is established,  the Ethernet OAM entities on both sides exchange 
Information OAMPDUs at the handshake packet transmission interval to check whether the Ethernet 
OAM connection is normal. If an Ethernet OAM entity receives no Information OAMPDU within the 
Ethernet OAM connection timeout time, the Ethern et OAM connection is considered disconnected.  
Link monitoring 
Error detection in an Ethernet is difficult, especially when the physical connection in the network is not 
disconnected but network performance is degrading gr adually. Link monitoring is used to detect and 
indicate link faults in various environments. Ethernet OAM implements link monitoring through the 
exchange of Event Notification OAMPDUs. When detecting one of the link error events listed in  Table 7, 
the local O

AM entity sends an Event Notification OAMPDU to notify the remote OAM entity. With the 
log information, network administrators can keep track of network status promptly.  
Table 7  Ethernet OAM link error events 
Ethernet OAM link events  Descri
ption 
Errored symbol event  An errored symbol event occurs when
 the number of detected symbol 
errors during a specified detectio n interval exceeds the predefined 
threshold. 
Errored frame event  An errored frame event occurs when the number of detected error 
frames during a specified interval 
exceeds the predefined threshold.  
Errored frame period event  An errored frame period event occurs 
if the number of frame errors in 
a specific number of received  frames exceeds the predefined 
threshold.  
Errored frame seconds event  An errored frame seconds event occurs when the number of error 
frame seconds detected on a port during a specified detection 
interval reaches the error threshold. 
 
The system transforms the period of detecting errore
d frame period events into the maximum number of 
64-byte frames (excluding the interframe spacing an d preamble) that a port can send in the specified 
period. The system takes the maximum number of frames sent as the period. The maximum number of 
frames sent is calculated using this formula: the maximum number of frames = interface bandwidth (bps) 
× errored frame period event detection period (in ms)/(64 × 8 × 1000).
    All HP manuals Comments (0)

    Related Manuals for HP 5500 Ei 5500 Si Switch Series Configuration Guide