HP 5500 Ei 5500 Si Switch Series Configuration Guide
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+.
![Page 2076
13
Displaying and maintaining Ethernet OAM
configuration
Task Command Remarks
Display global Ethernet OAM
configuration. display oam configuration
[ |
{ begin | exclude | include }
regular-expression ] Available in any view
Display the statistics on critical
events after an Ethernet OAM
connection is established. display oam critical-event
[
interface interface-type
interface-number ] [ | { begin |
exclude | include }
regular-expression ] Available in any view
Display...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-2075.png "Page 2076
13
Displaying and maintaining Ethernet OAM
configuration
Task Command Remarks
Display global Ethernet OAM
configuration. display oam configuration
[ |
{ begin | exclude | include }
regular-expression ] Available in any view
Display the statistics on critical
events after an Ethernet OAM
connection is established. display oam critical-event
[
interface interface-type
interface-number ] [ | { begin |
exclude | include }
regular-expression ] Available in any view
Display...")
8 A second in which errored frames appear is called an errored frame second. Remote fault detection Information OAMPDUs are exchanged periodically among Ethernet OAM entities across established OAM connections. In a network where traffic is interrupted due to device failures or unavailability, the flag field defined in information OAMPDUs allows an Ethernet OAM entity to send error information—the critical link event type—to its peer. You can use the log information to track ongoing link status and troubleshoot problems promptly. Table 8 Critical link events T ype Description OAMPDU transmission frequencies Link Fault Peer link signal is lost. Once per second Dying Gasp A power failure or other unexpected error occurred. Non-stop Critical Event An undetermined critical event occurred. Non-stop Th i s Swi tch S e ri e s i s a b l e t o re c eive i n fo rm a t io n OA M PD Us c a rr yi n g t h e cri t ic a l l i n k eve n t s l i s te d i n Tabl e 8 . Onl y the Gigabit fiber ports are able to send information OAMPDUs carrying Link Fault events. Th i s Swi tch S e ri e s i s a b l e t o s e n d i n fo rm a t io n OA M PD Us c a rr yi n g D yi n g G a s p eve n t s wh e n t h e d evic e i s rebooted or relevant ports are manually shut down. Physical IRF ports, however, are unable to send this type of OAMPDU. For more information about physical IRF ports, see IRF Configuration Guide. This Switch Series is unable to send information OAMPDUs carrying Critical Events. Remote loopback Remote loopback is available only after the Ethern et OAM connection is established. With remote loopback enabled, the Ethernet OAM entity op erating in active Ethernet OAM mode sends non-OAMPDUs to its peer. After receiving these fram es, the peer does not forward them according to their destination addresses. Instead, it returns them to the sender along the original path. Remote loopback enables you to check the link stat us and locate link failures. Performing remote loopback periodically helps to detect network faults promptly. Furthermore, performing remote loopback by network segments helps to locate network faults. Standards and protocols Ethernet OAM is defined in IEEE 802.3ah (Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications. Ethernet OAM configuration task list Task Remarks Configuring basic Ethernet OAM functions Required Configuring the Ethernet OAM connection detection timers Optional Configuring link monitoring Configuring errored symbol event detection Optional Configuring errored frame event detection Optional
9
Task Remarks
Configuring errored frame period event detection Optional
Configuring errored frame seconds event detection Optional
Configuring Ethernet
OAM remote
loopback Enabling Ethernet OAM remote loopback
Optional
Rejecting the Ethernet OAM remote loopback
request from a remote port Optional
Configuring basic Ethernet OAM functions
For Ethernet OAM connection establishment, an Ethern
et OAM entity operates in active mode or passive
mode. Only an Ethernet OAM entity in active mode ca n initiate connection establishment. After Ethernet
OAM is enabled on an Ethernet port, according to it s Ethernet OAM mode, the Ethernet port establishes
an Ethernet OAM connection with its peer port.
To change the Ethernet OAM mode on an Ethernet OAM-enabled port, you must first disable Ethernet
OAM on the port.
To configure basic Ethernet OAM functions:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter Layer 2 Ethernet
interface view. interface
interface-type
interface-number N/A
3.
Set the Ethernet OAM mode.
oam mode { active | passive } Optional.
The default is active Ethernet OAM
mode.
4.
Enable Ethernet OAM on the
current port. oam enable Ethernet OAM is disabled by
default.
Configuring the Ethernet OAM connection
detection timers
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.
By adjusting the handshake packet transmission interval and the connection timeout timer, you can
change the detection time resolution for Ethernet OAM connections.
After the timeout timer of an Ethernet OAM connec tion expires, the local OAM entity ages out its
connection with the peer OAM entity, causing the OAM connection to be disconnected. HP recommends
that you set the connection timeout timer to at least five times the handshake packet transmission interval,
ensuring the stability of Ethernet OAM connections.
To configure the Ethernet OA M connection detection timers:
10 Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the Ethernet OAM handshake packet transmission interval. oam timer hello interval Optional. 1000 millisecond by default. 3. Configure the Ethernet OAM connection timeout timer. oam timer keepalive interval Optional. 5000 milliseconds by default. Configuring link monitoring After Ethernet OAM connections are established, the link monitoring periods and thresholds configured in this section take effect on all Ethernet ports automatically. Configuring errored symbol event detection Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the errored symbol event detection interval. oam errored-symbol period period-value Optional. 1 second by default. 3. Configure the errored symbol event triggering threshold. oam errored-symbol threshold threshold-value Optional. 1 by default. Configuring errored frame event detection Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the errored frame event detection interval. oam errored-frame period period-value Optional. 1 second by default. 3. Configure the errored frame event triggering threshold. oam errored-frame threshold threshold-value Optional. 1 by default. Configuring errored frame period event detection Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the errored frame period event detection period. oam errored-frame-period period period-value Optional. 1000 milliseconds by default. 3. Configure the errored frame period event triggering threshold. oam errored-frame-period threshold threshold-value Optional. 1 by default.
11 Configuring errored frame seconds event detection IMPORTANT: Make sure the errored frame seconds tri ggering threshold is less than the errored frame seconds detection interval. Otherwise, no errored fram e seconds event can be generated. To configure errored frame seconds event detection: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the errored frame seconds event detection interval. oam errored-frame-seconds period period-value Optional. 60 second by default. 3. Configure the errored frame seconds event triggering threshold. oam errored-frame-seconds threshold threshold-value Optional. 1 by default. Configuring Ethernet OAM remote loopback Enabling Ethernet OAM remote loopback CAUTION: Use this function with caution, because enabling Ethernet OAM remote loopback impacts other services. When you enable Ethernet OAM remote loopback on a port, the port sends Loopback Control OAMPDUs to a remote port, and the remote port ente rs the loopback state. The port then sends test frames to the remote port. By observing how many of these test frames return, you can calculate the packet loss ratio on the link to evaluate the link performance. You can enable Ethernet OAM remote loopback on a spec ific port in user view, system view, or Layer 2 Ethernet interface view. The configuration effects are the same. Configuration guidelines • Ethernet OAM remote loopback is available only after the Ethernet OAM connection is established and can be performed only by Ethernet OAM enti ties operating in active Ethernet OAM mode. • Remote loopback is available only on full-duplex li nks that support remote loopback at both ends. • Ethernet OAM remote loopback must be supported by both the remote port and the sending port. • Enabling Ethernet OAM remote loopback interrupts data communications. After Ethernet OAM remote loopback is disabled, all the ports involved will shut down and then come up. Ethernet OAM remote loopback can be disabled by any of the following actions: executing the undo oam enable command to disable Ethernet OAM; executing the undo oam loopback interface or undo oam loopback command to disable Ethernet OAM remote loopback; and Ethernet OAM connection timing out. • Ethernet OAM remote loopback is only applicable to individual links. It is not applicable to link aggregation member ports or service loopback gr oup member ports. In addition, do not assign ports where Ethernet OAM remote loopback is be ing performed to link aggregation groups or
12 service loopback groups. For more information about link aggregation groups and service loopback groups, see Layer 2—LAN Switching Configuration Guide . • Enabling internal loopback test on a port in remote loopback test can terminate the remote loopback test. For more information about loopback test, see Layer 2—LAN Switching Configuration Guide . Configuration procedure To enable Ethernet OAM remote loopback in user view: Task Command Remarks Enable Ethernet OAM remote loopback on a specific port. oam loopback interface interface-type interface-number Disabled by default. To enable Ethernet OAM remote loopback in system view: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable Ethernet OAM remote loopback on a specific port. oam loopback interface interface-type interface-number Disabled by default. To enable Ethernet OAM remote loopback in Layer 2 Ethernet interface view: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 Ethernet interface view. interface interface-type interface-number N/A 3. Enable Ethernet OAM remote loopback on the port. oam loopback Disabled by default. Rejecting the Ethernet OAM remote loopback request from a remote port The Ethernet OAM remote loopback function impacts other services. To solve this problem, you can disable a port from being controlled by the Loopback Control OAMPDUs sent by a remote port. The local port then rejects the Ethernet OAM remote loopback request from the remote port. To reject the Ethernet OAM remote loopback request from a remote port: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 Ethernet interface view. interface interface-type interface-number N/A 3. Reject the Ethernet OAM remote loopback request from a remote port. oam loopback reject-request By default, a port does not reject the Ethernet OAM remote loopback request from a remote port.
13
Displaying and maintaining Ethernet OAM
configuration
Task Command Remarks
Display global Ethernet OAM
configuration. display oam configuration
[ |
{ begin | exclude | include }
regular-expression ] Available in any view
Display the statistics on critical
events after an Ethernet OAM
connection is established. display oam critical-event
[
interface interface-type
interface-number ] [ | { begin |
exclude | include }
regular-expression ] Available in any view
Display the statistics on Ethernet
OAM link error events after an
Ethernet OAM connection is
established. display oam link-event
{ local |
remote } [ interface interface-type
interface-number ] [ | { begin |
exclude | include }
regular-expression ] Available in any view
Display the information about an
Ethernet OAM connection. display oam
{ local | remote }
[ interface interface-type
interface-number ] [ | { begin |
exclude | include }
regular-expression ] Available in any view
Clear statistics on Ethernet OAM
packets and Ethernet OAM link
error events.
reset oam
[ interface interface-type
interface-number ] Available in user view
Ethernet OAM configuration example
Network requirements
On the network shown in
Figure 2, per form the following operations:
• E n ab l e E t h e rn e t OA M o n D evic e A a n d D evic e B to au to - d e te ct l i n k erro rs b e t we e n t h e t wo d evic es
• Monitor the performance of the link between Device A and Device B by collecting statistics about
the error frames received by Device A
Figure 2 Network diagram
Configuration procedure
1. Configure Device A:
# Configure GigabitEthernet 1/0/1 to operat e in passive Ethernet OAM mode and enable
Ethernet OAM for it.
system-view
[DeviceA] interface gigabitethernet 1/0/1
14 [DeviceA-GigabitEthernet1/0/1] oam mode passive [DeviceA-GigabitEthernet1/0/1] oam enable [DeviceA-GigabitEthernet1/0/1] quit # Set the errored frame detection interval to 20 seconds and set the errored frame event triggering threshold to 10. [DeviceA] oam errored-frame period 20 [DeviceA] oam errored-frame threshold 10 2. Configure Device B: # Configure GigabitEthernet 1/0/1 to operate in active Ethernet OAM mode (the default) and enable Ethernet OAM for it. system-view [DeviceB] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] oam mode active [DeviceB-GigabitEthernet1/0/1] oam enable [DeviceB-GigabitEthernet1/0/1] quit 3. 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. [DeviceA] display oam configuration Configuration of the link event window/threshold : ------------------------------------------------------------------------\ -- Errored-symbol Event period(in seconds) : 1 Errored-symbol Event threshold : 1 Errored-frame Event period(in seconds) : 20 Errored-frame Event threshold : 10 Errored-frame-period Event period(in ms) : 1000 Errored-frame-period Event threshold : 1 Errored-frame-seconds Event period(in seconds) : 60 Errored-frame-seconds Event threshold : 1 Configuration of the timer : ------------------------------------------------------------------------\ -- Hello timer(in ms) : 1000 Keepalive timer(in ms) : 5000 The output shows that the detection period of e rrored frame events is 20 seconds, the detection threshold is 10 seconds, and all the other parameters use the default values. You can 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 Port : GigabitEthernet1/0/1 Link Status : Up Event statistic : ------------------------------------------------------------------------\ - Link Fault :0 Dying Gasp : 0 Critical Event : 0
15 The output shows that no critical link event occurred on the link between Device A and Device B. You can use the display oam link-event command to display the statistics of Ethernet OAM link error events. For example: # Display Ethernet OAM link event statistics of the remote end of Device B. [DeviceB] display oam link-event remote Port :GigabitEthernet1/0/1 Link Status :Up OAMRemoteErrFrameEvent : (ms = milliseconds) --------------------------------------------------------------------- Event Time Stamp : 5789 Errored FrameWindow : 10(100m\ s) Errored Frame Threshold : 1 Errored Frame : 3 Error Running Total : 35 Event Running Total : 17 The output shows that 35 errors occurred since Ethernet OAM was enabled on Device A, 17 of which are caused by error frames. The link is unstable.
16 Configuring CFD 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 Operations, Administration and Maintenance (OAM) mechanism used for link connectivity detection, fault verification, and fault location. Basic concepts in CFD Maintenance domain A maintenance domain (MD) defines the network where CFD plays its role. The MD boundary is defined by some maintenance association end points (MEPs) configured on the ports. An MD is identified by its MD name. To accurately locate faults, CFD introduces eight levels (from 0 to 7) to MDs. The bigger the number, the higher the level and the larger the area covered. Domains can touch or nest (if the outer domain has a higher level than the nested one) but cannot intersect or overlap. MD levels facilitate fault location and make fault location more accurate. As shown in Figure 3, MD_A in light blue nests MD_B in dark blue. If a connectivity fault is detected at the boundary of MD_A, any of the devices in MD_A, including Device A through Device E, may fail. If a connectivity fault is also detected at the boundary of MD_B, the failure points may be any of Device B through Device D. If the devices in MD_B can operate properly, at least Device C is operational. Figure 3 Two nested MDs CFD exchanges messages and performs operations on a per-domain basis. By planning MDs properly in a network, you can use CFD to rapidly locate failure points. Maintenance association A maintenance association (MA) is a set of maintenance points (MPs) in an MD. An MA is identified by the MD name + MA name. You can configure multiple MAs in an MD as needed.
17 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. Maintenance point An MP is configured on a port and belongs to an MA. MPs fall into two types: maintenance association end points (MEPs) and maintenance association intermediate points (MIPs). • MEP E a c h M E P i s i d e n t i f i e d b y a n i n t e g e r c a l l e d a M E P I D . T h e M E P s o f a n M D d e f i n e t h e r a n g e a n d boundary of the MD. The MA and MD that a MEP be longs to define the VLAN attribute and level of the packets sent by the MEP. MEPs fall into inward-facing MEPs and outward-facing MEPs. The level of a MEP determines the levels of packets that the MEP can process. The packets transmitted from a MEP carry the level of the MEP. A MEP forwards packets at a higher level and processes packet of its level or lower. The processi ng procedure is specific to packets in the same VLAN. Packets of different VLANs are independent. The direction of a MEP (outward-facing or inward -facing) determines the position of the MD relative to the port. Figure 4 Outward-facing MEP As shown in Figure 4, an out ward-facing MEP sends packets to its host port. Figure 5 Inward-facing MEP As shown in Figure 5, an i nward-facing MEP does not send packets to its host port. Rather, it sends packets to other ports on the device. • MIP A MIP is internal to an MD. It cannot send CF D packets actively. However, it can handle and respond to CFD packets. The MA and MD to whic h a MIP belongs define the VLAN attribute and level of the packets received.