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 2091 to Favourites
    image text
    Enable zoom 
    							 28 
 NOTE: 
•  The TST function takes effect only in CFD IEEE 802.1ag.  
•   To view the test result, use the  display cfd tst command on the target MEP.  
 
Displaying and maintaining CFD 
 
Task Command  Remarks 
Display CFD and AIS status.  display cfd status
 [ | { begin |  exclude | 
include  } regular-expression ]  Available in any view 
Display the CFD protocol version. display cfd version
 [ | { begin |  exclude | 
include  } regular-expression ]   Available in any view 
Display MD configuration 
information. display cfd md
 [ | { begin |  exclude | 
include  } regular-expression ]  Available in any view 
Display MA configuration 
information. display cfd ma 
[ [ ma-name  ]  md {  md-name 
|  level  level-value  } ] [ |  { begin  | exclude  | 
include  } regular-expression ]   Available in any view 
Display service instance 
configuration information. display cfd service-instance 
[ instance-id ] 
[ |  { begin |  exclude | include } 
regular-expression  ]   Available in any view 
Display MEP list in a service 
instance.  display cfd meplist [
 service-instance 
instance-id  ] [  | {  begin | exclude | include  } 
regular-expression  ]  Available in any view 
Display MP information.  display cfd mp 
[ interface  interface-type 
interface-number ] [ |  { begin | exclude  | 
include  } regular-expression ]   Available in any view 
Display the attribute and running 
information of the MEPs. display cfd mep 
mep-id service-instance 
instance-id  [ | { begin | exclude | include  } 
regular-expression  ]  Available in any view 
Display LTR information received 
by a MEP.  display cfd linktrace-reply
 [ service-instance 
instance-id  [  mep  mep-id  ] ] [ |  { begin | 
exclude  | include  } regular-expression ]   Available in any view 
Display the information of a remote 
MEP.  display cfd remote-mep service-instance 
instance-id
 mep mep-id  [ | { begin  | exclude  
|  include  } regular-expression  ] Available in any view 
Display the content of the LTR 
messages received as responses to 
the automatically sent LTMs.  display cfd linktrace-reply auto-detection 
[ size 
size-value  ] [ |  { begin  | exclude  | 
include  } regular-expression ]  Available in any view 
Display the AIS configuration and 
information on the specified MEP. display cfd ais
 [ service-instance  instance-id 
[ mep  mep-id  ] ] [ | { begin | exclude  | 
include  } regular-expression ]   Available in any view 
Display the one-way DM result on 
the specified MEP. display cfd dm one-way history
 
[ service-instance  instance-id [ mep 
mep-id  ] ] [ | { begin |  exclude |  include } 
regular-expression  ]   Available in any view
    Add page 2092 to Favourites
    image text
    Enable zoom 
    							 29 
Task Command  Remarks 
Display the TST result on the 
specified MEP. display cfd tst
 [ service-instance  instance-id 
[ mep  mep-id  ] ] [ | { begin | exclude  | 
include  } regular-expression ]   Available in any view 
Clear the one-way DM result on the 
specified MEP. reset cfd dm one-way history
 
[ service-instance  instance-id [ mep 
mep-id  ] ]  Available in user view 
Clear the TST result on the 
specified MEP.  reset cfd tst
 [ service-instance  instance-id 
[ mep  mep-id  ] ]  Available in user view 
 
CFD configuration example 
Network requirements 
As shown in 
Figure 8: 
•   T
he network comprises five devices and is divided into two MDs: MD_A (level 5) and MD_B (level 
3). All ports belong to VLAN 100, and the MAs  in the two MDs all serve VLAN 100. Suppose the 
MAC addresses of Device A through Device E are 0010-FC00-651 1,  0 010 - F C 0 0 - 6 512 ,  
0 010 - F C 0 0 - 6 513 ,  0 010 - F C 0 0 - 6 514 ,  a n d  0 010 - F C 0 0 - 6 515 .   
•   MD_A has three edge ports: GigabitEthernet 1/0/1 on Device A, GigabitEthernet 1/0/3 on 
Device D, and GigabitEthernet 1/0/4 on Device E, and they are all inward-facing MEPs. MD_B has 
two edge ports: GigabitEthernet 1/0/3 on Device B and GigabitEthernet 1/0/1 on Device D, and 
they are both outward-facing MEPs. 
•   In MD_A, Device B is designed to have MIPs when its port is configured with low level MEPs. Port 
GigabitEthernet 1/0/3 is configured with ME Ps of MD_B, and the MIPs of MD_A can be 
configured on this port. You should configure the MIP generation rule of MD_A as explicit. 
•   The MIPs of MD_B are designed on Device C, and are configured on all ports. You should configure 
the MIP generation rule as default. 
•   Configure CC to monitor the connectivity among all the MEPs in MD_A and MD_B. Configure to 
use LB to locate link faults, and use the AIS function to suppress the error alarms reported.  
•   After the status information of the entire network is obtained, use LT, LM, one-way DM, two-way DM, 
and TST to detect link faults.
    Add page 2093 to Favourites
    image text
    Enable zoom 
    							 30 
Figure 8 Network diagram 
 
 
Configuration procedure 
1. Configure a VLAN and assign ports to it: 
On each device shown in  Figure 8, c
reate VLAN 100, and assign ports GigabitEthernet 1/0/1 
through GigabitEthernet 1/0/4 to VLAN 100. 
2.  Enable CFD: 
# Enable CFD on Device A. 
 system-view 
[DeviceA] cfd enable 
Enable CFD on Device B through De vice E using the same method.  
3. Configure service instances: 
# Create MD_A (level 5) on Device A, create  MA_A, which serves VLAN 100, in MD_A, and 
create service instance 1 for MD_A and MA_A. 
[DeviceA] cfd md MD_A level 5 
[DeviceA] cfd ma MA_A md MD_A vlan 100 
[DeviceA] cfd service-instance 1 md MD_A ma MA_A 
Configure Device E as you configure Device A.  
# Create MD_A (level 5) on Device B, create  MA_A, which serves VLAN 100, in MD_A, and then 
create service instance 1 for MD_A and MA_A. In  addition, create MD_B (level 3), create MA_B, 
which serves VLAN 100, in MD_B, and then cr eate service instance 2 for MD_B and MA_B. 
[DeviceB] cfd md MD_A level 5 
[DeviceB] cfd ma MA_A md MD_A vlan 100 
[DeviceB] cfd service-instance 1 md MD_A ma MA_A 
[DeviceB] cfd md MD_B level 3 
[DeviceB] cfd ma MA_B md MD_B vlan 100 
[DeviceB] cfd service-instance 2 md MD_B ma MA_B 
Configure Device D as you configure Device B.  
# Create MD_B (level 3) on Device C, create  MA_B, which serves VLAN 100, in MD_B, and then 
create service instance 2 for MD_B and MA_B. 
[DeviceC] cfd md MD_B level 3
    Add page 2094 to Favourites
    image text
    Enable zoom 
    							 31 
[DeviceC] cfd ma MA_B md MD_B vlan 100 
[DeviceC] cfd service-instance 2 md MD_B ma MA_B 
4. 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 GigabitEthernet 1/0/1.  
[DeviceA] cfd meplist 1001 4002 5001 service-instance 1 
[DeviceA] interface gigabitethernet 1/0/1 
[DeviceA-GigabitEthernet1/0/1] cfd mep 1001 service-instance 1 inbound 
[DeviceA-GigabitEthernet1/0/1] cfd mep service-instance 1 mep 1001 enabl\
e 
[DeviceA-GigabitEthernet1/0/1] quit 
# On Device B, configure a MEP list in service  instances 1 and 2, respectively. Create and enable 
outward-facing MEP 2001 in service instance 2 on GigabitEthernet 1/0/3. 
[DeviceB] cfd meplist 1001 4002 5001 service-instance 1 
[DeviceB] cfd meplist 2001 4001 service-instance 2 
[DeviceB] interface gigabitethernet 1/0/3 
[DeviceB-GigabitEthernet1/0/3] cfd mep 2001 service-instance 2 outbound \
[DeviceB-GigabitEthernet1/0/3] cfd mep service-instance 2 mep 2001 enabl\
e 
[DeviceB-GigabitEthernet1/0/3] quit 
# On Device D, configure a MEP list in service  instances 1 and 2, respectively. Create and enable 
outward-facing MEP 4001 in service instance 2 on  GigabitEthernet 1/0/1, and then create and 
enable inward-facing MEP 4002 in service instance 1 on GigabitEthernet 1/0/3. 
[DeviceD] cfd meplist 1001 4002 5001 service-instance 1 
[DeviceD] cfd meplist 2001 4001 service-instance 2 
[DeviceD] interface gigabitethernet 1/0/1 
[DeviceD-GigabitEthernet1/0/1] cfd mep 4001 service-instance 2 outbound \
[DeviceD-GigabitEthernet1/0/1] cfd mep service-instance 2 mep 4001 enabl\
e 
[DeviceD-GigabitEthernet1/0/1] quit 
[DeviceD] interface gigabitethernet 1/0/3 
[DeviceD-GigabitEthernet1/0/3] cfd mep 4002 service-instance 1 inbound 
[DeviceD-GigabitEthernet1/0/3] cfd mep service-instance 1 mep 4002 enabl\
e 
[DeviceD-GigabitEthernet1/0/3] quit 
# On Device E, configure a MEP list in service instance 1. Create and  enable inward-facing MEP 
5001 in service instance 1 on GigabitEthernet 1/0/4. 
[DeviceE] cfd meplist 1001 4002 5001 service-instance 1 
[DeviceE] interface gigabitethernet 1/0/4 
[DeviceE-GigabitEthernet1/0/4] cfd mep 5001 service-instance 1 inbound 
[DeviceE-GigabitEthernet1/0/4] cfd mep service-instance 1 mep 5001 enabl\
e 
[DeviceE-GigabitEthernet1/0/4] quit 
5.  Configure MIPs: 
# Configure the MIP generation rule in serv ice instance 1 on Device B as explicit.  
[DeviceB] cfd mip-rule explicit service-instance 1 
# Configure the MIP generation rule in service instance 2 on Device C as default. 
[DeviceC] cfd mip-rule default service-instance 2 
6. Configure CC: 
# On Device A, enable the sending of CCM frames for MEP 1001 in service instance 1 on 
GigabitEthernet 1/0/1. 
[DeviceA] interface gigabitethernet 1/0/1
    Add page 2095 to Favourites
    image text
    Enable zoom 
    							 32 
[DeviceA-GigabitEthernet1/0/1] cfd cc service-instance 1 mep 1001 enable\
 
[DeviceA-GigabitEthernet1/0/1] quit 
# On Device B, enable the sending of CCM frames for MEP 2001 in service instance 2 on 
GigabitEthernet 1/0/3. 
[DeviceB] interface gigabitethernet 1/0/3 
[DeviceB-GigabitEthernet1/0/3] cfd cc service-instance 2 mep 2001 enable\
 
[DeviceB-GigabitEthernet1/0/3] quit 
# On Device D, enable the sending of CCM frames for MEP 4001 in service instance 2 on 
GigabitEthernet 1/0/1, and enable the sending of CCM frames for MEP 4002 in service instance 
1 on GigabitEthernet 1/0/3. 
[DeviceD] interface gigabitethernet 1/0/1 
[DeviceD-GigabitEthernet1/0/1] cfd cc service-instance 2 mep 4001 enable\
 
[DeviceD-GigabitEthernet1/0/1] quit 
[DeviceD] interface gigabitethernet 1/0/3 
[DeviceD-GigabitEthernet1/0/3] cfd cc service-instance 1 mep 4002 enable\
 
[DeviceD-GigabitEthernet1/0/3] quit 
# On Device E, enable the sending of CCM frames for MEP 5001 in service instance 1 on 
GigabitEthernet 1/0/4. 
[DeviceE] interface gigabitethernet 1/0/4 
[DeviceE-GigabitEthernet1/0/4] cfd cc service-instance 1 mep 5001 enable\
 
[DeviceE-GigabitEthernet1/0/4] quit 
7.  Configure AIS: 
# Enable AIS on Device B, and configure the AI S frame transmission level as 2 and AIS frame 
transmission interval as 1 second in service instance 2.  
[DeviceB] cfd ais enable 
[DeviceB] cfd ais level 5 service-instance 2 
[DeviceB] cfd ais period 1 service-instance 2 
Verifying the configuration 
1.  Verify the LB function: 
When the CC function detects a link fault, us e the LB function to locate the fault.  
# Enable LB on Device A to check the status of the link between MEP 1001 and MEP 5001 in 
service instance 1.  
[DeviceA] cfd loopback service-instance 1 mep 1001 target-mep 5001 
Loopback to 0010-FC00-6515 with the sequence number start from 1001-4340\
4: 
Reply from 0010-FC00-6515: sequence number=1001-43404 time=5ms 
Reply from 0010-FC00-6515: sequence number=1001-43405 time=5ms 
Reply from 0010-FC00-6515: sequence number=1001-43406 time=5ms 
Reply from 0010-FC00-6515: sequence number=1001-43407 time=5ms 
Reply from 0010-FC00-6515: sequence number=1001-43408 time=5ms 
Send:5        Received:5        Lost:0 
After the whole network status is obtained with th e CC function, use the LT function to identify the 
paths between source and target MEPs or locate faults.  
2.  Verify the LT function: 
# Identify the path between MEP 1001 and MEP 5001 in service instance 1 on Device A. 
[DeviceA] cfd linktrace service-instance 1 mep 1001 target-mep 5001 
Linktrace to MEP 5001 with the sequence number 1001-43462
    Add page 2096 to Favourites
    image text
    Enable zoom 
    							 33 
MAC Address               TTL     Last MAC         Relay Action 
0010-FC00-6515            63      0010-FC00-6512   Hit 
3. Verify the LM function: 
After the CC function obtains the status information of  the entire network, use the LM function to test 
the link status. For example: 
# Test the frame loss from MEP 1001 to MEP 4002 in service instance 1 on Device A.  
[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 
 
Average 
Far-end frame loss: 20    Near-end frame loss: 25 
Far-end frame loss rate: 25%    Near-end frame loss rate: 32% 
Send LMMs: 5        Received: 5        Lost: 0 
4.  Verify the one-way DM function: 
After the CC function obtains the status informat ion of the entire network, use the one-way DM 
function to test the one-way frame delay of a link. For example: 
# Test the one-way frame delay from MEP 1001 to  MEP 4002 in service instance 1 on Device A.  
[DeviceA] cfd dm one-way service-instance 1 mep 1001 target-mep 4002 
Info: 5 1DM frames process is done, please check the result on the remot\
e device. 
# Display the one-way DM result on MEP 4002 in service instance 1 on Device D.  
[DeviceD] display cfd dm one-way history service-instance 1 mep 4002 
Service instance: 1 
MEP ID: 4002 
Send 1DM total number: 0 
Received 1DM total number: 5 
Frame delay: 10ms  9ms  11ms  5ms  5ms 
Delay average: 8ms 
Delay variation: 5ms  4ms  6ms  0ms  0ms 
Variation average: 3ms 
5. Verify the two-way DM function: 
After the CC function obtains the status informat ion of the entire network, use the two-way DM 
function to test the two-way fram e delay of a link. For example: 
# Test the two-way frame delay from MEP 1001 to  MEP 4002 in service instance 1 on Device A.  
[DeviceA] cfd dm two-way service-instance 1 mep 1001 target-mep 4002 
Frame delay: 
Reply from 0010-FC00-6514: 10ms 
Reply from 0010-FC00-6514: 9ms 
Reply from 0010-FC00-6514: 11ms 
Reply from 0010-FC00-6514: 5ms
    Add page 2097 to Favourites
    image text
    Enable zoom 
    							 34 
Reply from 0010-FC00-6514: 5ms 
Average: 8ms 
Send DMMs: 5       Received: 5        Lost: 0 
 
Frame delay variation: 5ms  4ms  6ms  0ms  0ms 
Average: 3ms 
6. Verify the TST function: 
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. Please check the result on the remote device.\
 
# Display the TST result on MEP 4002 in service instance 1 on Device D.  
[DeviceD] display cfd tst service-instance 1 mep 4002 
Service instance: 1 
MEP ID: 4002 
Send TST total number: 0 
Received TST total number: 5 
Received from 0010-FC00-6511, sequence number 1: Bit True 
Received from 0010-FC00-6511, sequence number 2: Bit True 
Received from 0010-FC00-6511, sequence number 3: Bit True 
Received from 0010-FC00-6511, sequence number 4: Bit True 
Received from 0010-FC00-6511, sequence number 5: Bit True
    Add page 2098 to Favourites
    image text
    Enable zoom 
    							 35 
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. 
For example, the link between two switches, Switch A and Switch B, is a bidirectional link when they are 
connected via a fiber pair, with one fiber used for sending packets from A to B and the other for sending 
packets from B to A. This link is a two-way link. If one of the fibers gets broken, the link becomes a 
unidirectional link (one-way link).  
There are two types of unidirectional fiber links. One occurs when fibers are cross-connected. The other 
occurs when a fiber is not connected at one end, or when one fiber of a fiber pair gets broken.  Figure 
9  sho

ws a correct fiber connection and the tw o types of unidirectional fiber connection. 
Figure 9  Correct and incorrect  fiber connections 
 
 
The Device link detection protocol (DLDP) detects unidirectional links (fiber links or twisted-pair links) and 
can be configured to shut down the related port automatically or prompt users to take actions to avoid 
network problems. 
As a data link layer protocol, DLDP cooperates with ph ysical layer protocols to monitor link status. When 
the auto-negotiation mechanism provided by the physic al layer detects physical signals and faults, DLDP
    Add page 2099 to Favourites
    image text
    Enable zoom 
    							 36 
performs operations such as identifying peer devices, detecting unidirectional links, and shutting down 
unreachable ports. The auto-negotiation mechanis m and DLDP work together to make sure that 
physical/logical unidirectional links are detected  and shut down, and to prevent failure of other 
protocols such as STP. If both ends of a link are operating normally at the physical layer, DLDP detects 
whether the link is correctly connect ed at the link layer and whether the two ends can exchange packets 
properly. This is beyond the capability of the au to-negotiation mechanism at the physical layer. 
How DLDP works 
DLDP link states 
A device is in one of these DLDP link states: Initial, Inactive, Active, Advertisement, Probe, Disable, and 
DelayDown, as described in Tabl e  10. 
Table 10  DLDP link stat

es 
State Indicates…
 
Initial  DLDP is disabled. 
Inactive  DLDP is enabled, and the link is down.  
Active  DLDP is enabled and the link is up,  or the neighbor entries have been cleared. 
Advertisement All neighbors are bi-directionally reachabl
e or DLDP has been in active state for 
m o r e  t h a n  f i v e  s e c o n d s .  T h i s  i s  a  r e l a t i v e l y  s t a b l e  s t a t e  w h e r e  n o  u n i d i r e c t i o n a l  l i n k  
has been detected. 
Probe  DLDP enters this state if it receives a packet from an unknown neighbor. In this 
state, DLDP sends packets to check whether 
the link is unidirectional. As soon as 
DLDP transits to this state, a probe timer starts and an echo timeout timer starts for 
each neighbor to be probed. 
Disable  A port enters this state when: •
 A unidirectional link is detected. 
• The contact with the neighbor in enhanced mode gets lost. 
• In this state, the port does not receive or send packets other than DLDPDUs.   
DelayDown A port in the Active, Advertisement, or Prob
e DLDP link state transits to this state 
rather than removes the corresponding neig hbor entry and transits to the Inactive 
state when it detects a port-down event. Wh en a port transits to this state, the 
DelayDown timer is triggered. 
 
DLDP timers 
Table 11  DLDP timers 
DLDP timer  Descri
ption 
Active timer  Determines the interval for sending Adve
rtisement packets with RSY tags, which 
defaults to 1 second. By default, a device  in the active DLDP link state sends one 
Advertisement packet with RSY tags ev ery second. The maximum number of 
advertisement packets with RSY tags that can be sent successively is 5. 
Advertisement timer  Determines the interval for sending 
common advertisement packets, which 
defaults to 5 seconds. 
Probe timer  Determines the interval for sending Probe packets, which defaults to 1 second. By 
default, a device in the probe state se
nds one Probe packet every second. The 
maximum number of Probe packets that  can be sent successively is 10.
    Add page 2100 to Favourites
    image text
    Enable zoom 
    							 37 
DLDP timer Description 
Echo timer  This timer is set to 10 seconds. It is tr
iggered when a device transits to the Probe 
state or when an enhanced detect is la unched. 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. In this case, the 
device does the following: 
Sends Disable packets. 
Either prompts the user to shut down the po rt or shuts down the port automatically 
(depending on the DLDP  down mode configured). 
Removes the corresponding neighbor entries. 
Entry timer  When a new neighbor joins, a neighbor entry is created and the corresponding 
entry timer is triggered. When a DLDP pa
cket is received, the device updates the 
corresponding neighbor entry and the entry timer. 
In normal mode, if no packet is received from a neighbor when the corresponding 
entry timer expires, DLDP  sends advertisement packets with RSY tags and removes 
the neighbor entry. 
In enhanced mode, if no packet is receiv ed from a neighbor when the Entry timer 
expires, DLDP triggers  the enhanced timer. 
The setting of an Entry timer is three times that of the Advertisement timer. 
Enhanced timer  In enhanced mode, this timer is triggered if no packet is received from a neighbor 
when the entry timer expires. Enhanced timer is set to 1 second. 
After the Enhanced timer is triggered, th
e device sends up to eight probe packets 
to the neighbor at a frequenc y of one packet per second.  
DelayDown timer A device in Active, Advertisement, or Prob
e DLDP link state transits to DelayDown 
state rather than removes the correspondi ng neighbor entry and transits to the 
Inactive state when it detects a port-down event. 
When a device transits to this state, the  DelayDown timer is triggered. A device in 
DelayDown state only responds to port-up events. 
If a device in the DelayDown state dete cts a port-up event before the DelayDown 
timer expires, it resumes its original DLDP  state. If not, when the DelayDown timer 
expires, the device removes the corresp onding DLDP neighbor information and 
transits to the Inactive state. 
RecoverProbe timer  This timer is set to 2 seconds. A port in
 the Disable state sends one RecoverProbe 
packet every two seconds to detect whethe r a unidirectional link has restored.  
 
DLDP mode 
DLDP can operate in normal or enhanced mode: 
•  In normal DLDP mode, when an entry timer expire s, the device removes the corresponding neighbor 
entry and sends an Advertisement packet with the RSY tag. 
•   In enhanced DLDP mode, when an entry timer expires, the Enhanced timer is triggered and the 
device tests the neighbor by sending up to eight Probe packets at the frequency of one packet per 
second. If no Echo packet has been received from  the neighbor when the Echo timer expires, the 
device transits to the Disable state.  
Tabl e  12  sh
ows the relationship between the DLDP modes and neighbor entry aging.
    All HP manuals Comments (0)

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