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 2081 to Favourites
    image text
    Enable zoom 
    							 18 
By cooperating with MEPs, a MIP can perform a function similar to ping and traceroute. Like a MEP, 
a MIP forwards packets of a diffe rent level without any processing and only processes packets of 
its level.  
Figure 6  dem
 onstrates a grading example of the CF D module. Six devices, labeled A through F 
respectively, exist. Suppose each device has tw o ports, and MEPs and MIPs are configured on 
some of these ports. Four levels of MDs are desi gned in this example, the bigger the number, the 
higher the level and the larger the area covered. In  this example, Port 1 of device B is configured 
with the following MPs—a level 5 MIP, a level 3  inward-facing MEP, a level 2 inward-facing MEP, 
and a level 0 outward-facing MEP.  
Figure 6  Levels of MPs 
 
 
MEP list 
A MEP list is a collection of local MEPs allowed to be configured and the remote MEPs to be monitored 
in the same MA. It lists all the MEPs configured on different devices in the same MA. The MEPs all have 
unique MEP IDs. When a MEP receives from a remote device a continuity check message (CCM) that 
carries a MEP ID not included in the MEP list of the MA, it drops the message.  
CFD functions 
CFD works effectively only in properly-configured networks. Its functions, which are implemented through 
the MPs, include: 
•   Continuity check (CC) 
•   Loopback (LB) 
•   Linktrace (LT) 
•   Alarm indication signal (AIS) 
•   Loss measurement (LM) 
•   Delay measurement (DM) 
•   Test (TST)
    Add page 2082 to Favourites
    image text
    Enable zoom 
    							 19 
Continuity check 
Connectivity faults are usually caused by device faults or configuration errors. Continuity check checks 
the connectivity between MEPs. This function is implemented through periodic sending of continuity 
check messages (CCMs) by the MEPs. As a multicast message, a CCM sent by one MEP is intended to 
be received by all the other MEPs in the same MA. If a MEP fails to receive the CCMs within 3.5 times 
the sending interval, the link is considered faulty and a log is generated. When multiple MEPs send 
CCMs at the same time, the multipoint-to-multipoint link check is achieved. CCM frames are multicast 
frames.  
Loopback 
Similar to ping at the IP layer, loopback verifies  the connectivity between a local device and a remote 
device. To implement this function, the local MEP se nds loopback messages (LBMs) to the remote MEP. 
Depending on whether the local MEP can receive a l oopback reply message (LBR) from the remote MEP, 
the link state between the two can be verified.  LBM frames and LBR frames are unicast frames.  
Linktrace  
Linktrace identifies the path between the source MEP an d the target MEP. This function is implemented in 
the following way—the source MEP sends the linktrace messages (LTMs) to the target MEP. After 
receiving the messages, the target MEP and the MIPs that the LTM frames pass send back linktrace reply 
messages (LTRs) to the source MEP. Based on the re ply messages, the source MEP can identify the path 
to the target MEP. LTM frames are multicast frames and LTRs are unicast frames.  
AIS 
The AIS function suppresses the number of error alarms reported by MEPs. If a local MEP receives no 
CCM frames from its peer MEP within 3.5 times the CC M transmission interval, it immediately starts to 
send AIS frames periodically in the opposite direction of CCM frames. Upon receiving the AIS frames, 
the peer MEP suppresses the error alarms locally, and continues to send the AIS frames. If the local MEP 
receives CCM frames within 3.5 times the CCM transm ission interval, it stops sending AIS frames and 
restores the error alarm function. AIS frames are multicast frames.  
LM 
The LM function measures the frame loss in a cert ain direction between a pair of MEPs. The source MEP 
sends loss measurement messages (LMMs) to the ta rget MEP, the target MEP responds with loss 
measurement replies (LMRs), and the source MEP calcul ates the number of lost frames according to the 
counter values of the two consecutive LMRs (the current LMR and the previous LMR). LMMs and LMRs are 
multicast frames.  
DM 
The DM function measures frame delays between two MEPs, including one-way and two-way frame 
delays.  
1.  One-way frame delay measurement 
The source MEP sends a one-way delay measuremen t (1DM) frame, which carries the transmission 
time, to the target MEP. Upon receiving the 1DM  frame, the target MEP records the reception time, 
and calculates and records the link transmission de lay and jitter (delay variation) according to the 
transmission time and reception time. 1DM frames are multicast frames.  
2.  Two-way frame delay measurement 
The source MEP sends a delay measurement message (DMM), which carries the transmission time, 
to the target MEP. Upon receiving the DMM, the target MEP resp onds with a delay measurement 
reply (DMR), which carries the reception time  and transmission time of the DMM and the 
transmission time of the DMR.  Upon receiving the DMR, the source MEP records the DMR reception
    Add page 2083 to Favourites
    image text
    Enable zoom 
    							 20 
time, and calculates the link transmission delay and jitter according to the DMR reception time and 
DMM transmission time. DMM frames an d DMR frames are multicast frames.  
TST 
The TST function tests the bit errors between two MEPs. The source MEP sends a TST frame, which carries 
t h e  t e s t  p a t t e r n ,  s u c h  a s  p s e u d o  r a n d o m  b i t  s e q u e n c e  ( P R B S )  o r  a l l - z e r o ,  t o  t h e  t a r g e t  M E P.  U p o n  r e c e i v i n g  
the TST frame, the target MEP determines the bit errors by calculating and comparing the content of the 
TST frame. TST frames are unicast frames.  
Protocols and standards 
•  IEEE 802.1ag,  Virtual Bridged Local Area Networks Amendment 5: Connectivity Fault 
Management  
•   ITU-T Y.1731,  OAM functions and mechanisms for Ethernet based networks  
CFD configuration task list 
For CFD to work properly, design the network by performing the following tasks: 
•  Grade the MDs in the entire network, and define the boundary of each MD 
•   A s s i g n  a  n a m e  f o r  e a c h  M D.  M a ke  s u re  t h a t  t h e  s a m e  M D  h a s  t h e  s a m e  n a m e  o n  d i f f e re n t  d evi c e s .    
•   Define the MA in each MD according to the VLAN you want to monitor 
•   Assign a name for each MA. Make sure that the same MA in the same MD has the same name on 
different devices. 
•   Determine the MEP list of each MA in each MD. Make sure that devices in the same MA maintain 
the same MEP list.  
•   At the edges of MD and MA, MEPs should be designed at the device port. MIPs can be designed 
on devices or ports that are not at the edges. 
Complete the following tasks to configure CFD: 
 
Tasks Remarks 
Configuring basic CFD 
settings   Enabling CFD  
Required 
Configuring the CFD protocol version  Optional 
Configuring service 
instances  Creating a service instance 
with the MD na

me  Required 
Perform either task 
Creating a service instance 
without the MD name 
Configuring MEPs   Required 
Configuring MIP generation rules  Required 
Configuring CFD 
functions  Configuring CC on MEPs  
Required Configuring LB on MEPs  Optional 
Configuring LT on MEPs Optional 
Configuring AIS Optional
    Add page 2084 to Favourites
    image text
    Enable zoom 
    							 21 
Tasks Remarks 
Configuring LM Optional 
Configuring one-way DM Optional 
Configuring two-way DM Optional 
Configuring TST Optional 
 
 NOTE: 
Typically, a port blocked by STP cannot receive or  send CFD messages except in the following cases: 
•   The port is configured as an outward-facing MEP.  
•   The port is configured as a MIP or inward-facin
g MEP, which can still receive and send CFD messages
except CCM messages.  
 
Configuring basic CFD settings 
Enabling CFD 
Enable CFD on all concerned devices.  
To enable CFD on a device: 
 
Step Command Remarks 
1.   Enter system view.  system-view  N/A 
2.  Enable CFD. 
cfd enable  CFD is disabled by default.  
 
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. Devices in a same MD must use the same CFD protocol 
version. Otherwise, they cannot exchange CFD protocol packets. 
To configure the CFD protocol version: 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Configure the CFD protocol 
version.  cfd version
 { draft5 | draft5-plus  | 
standard  }  Optional. 
By default, CFD uses the standard 
version of IEEE 802.1ag. 
 
If an MD is created by using the 
cfd md command or automatically generated by using the  cfd 
service-instance maid format  command on a device, you cannot switch between the standard and 
non-standard versions (draft5.2 version and draft5.2 interim version). However, you can switch between 
the draft5.2 version and draft5.2 interim version. This restriction does not apply to the device without an 
MD configured.
    Add page 2085 to Favourites
    image text
    Enable zoom 
    							 22 
Configuring service instances 
Before configuring the MEPs and MIPs, you must first configure service instances. A service instance is a 
set of service access points (SAPs), and it belongs to an MA in an MD.  
A service instance is indicated by an integer to represent an MA in an MD. The MD and MA define the 
level and VLAN attribute of the messages handled by the MPs in a service instance. 
Service instances fall into two types: 
•   Service instance with the MD name, which  takes effect in any version of CFD.  
•   Service instance without the MD name, which takes effect in only CFD IEEE 802.1ag.  
You can create either type of service instance as needed.  
Creating a service instance with the MD name 
To create a service instance with the MD name, create the MD and MA for the service instance first.   
  CAUTION: 
You must create the MD, MA, and service instance by 
strictly following the order stated in the table.  
 
To configure a service instance with the MD name:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Create an MD. 
cfd md md-name  level  level-value  Not created by default. 
3.  Create an MA.  cfd ma 
ma-name  md md-name  vlan 
vlan-id   Not created by default. 
4.
  Create a service instance with 
the MD name.  cfd service-instance 
instance-id md 
md-name  ma ma-name   Not created by default. 
 
Creating a service instance without the MD name 
When you create a service instance without the MD name, the system automatically creates the MA and 
MD for the service instance.  
To create a service instance without the MD name: 
 
Step Command Remarks 
1.
  Enter system view.  system-view  N/A 
2.  Create a service instance 
without the MD name.  cfd service-instance
 instance-id 
maid format  { icc-based ma-name 
|  string  ma-name  } level level-value  
vlan  vlan-id   Not created by default. 
 
Configuring MEPs 
CFD is implemented through various operations on ME
Ps. As a MEP is configured on a service instance, 
the MD level and VLAN attribute of the servic e instance become the attribute of the MEP.
    Add page 2086 to Favourites
    image text
    Enable zoom 
    							 23 
Before creating MEPs, configure the MEP list. An MEP list is a collection of local MEPs allowed to be 
configured in an MA and the remote MEPs to be monitored. 
 
 IMPORTANT: 
You cannot create a MEP if the MEP ID is not incl
uded in the MEP list of the service instance.  
 
To  c o n fig u re  a  M E P :   
Step Command Remarks 
1.  Enter system view.  system-view  N/A 
2.  Configure a MEP list.  cfd meplist 
mep-list 
service-instance  instance-id  By default, no MEP list is 
configured.  
3.
  Enter Layer 2 Ethernet 
interface view.  interface
 interface-type 
interface-number   N/A 
4.
  Create a MEP.  cfd mep 
mep-id service-instance 
instance-id  { inbound  | outbound  } Not configured by default. 
5.  Enable the MEP.  cfd mep service-instance 
instance-id 
mep mep-id  enable  Disabled by default. 
 
Configuring MIP generation rules 
As functional entities in a service instance, MIPs respond to various CFD frames, such as LTM frames, LBM 
frames, 1DM frames, DMM frames, and TST frames.  
MIPs are generated on each port automatically accord
ing to related MIP generation rules. If a port has 
no MIP, the system will check the MAs in each MD (from low to high levels) and follow the procedure 
described in  Figure 7 to
 create or not to create MIPs (within the same VLAN): 
Figure 7  Procedure of creating MIPs 
 
 
You can choose appropriate MIP generation rules based on your network design. 
To configure the rules for generating MIPs:  
 
MIP exists on low level MA?
Create MIPNot create MIP
Yes
No
MIP generation rule
Default
Explicit
Start to decide whether to create MIP
MEP exists on low level MA?NoYes
    Add page 2087 to Favourites
    image text
    Enable zoom 
    							 24 
Step Command Remarks 
1.  Enter system view.  system-view  N/A 
2.  Configure the rules for 
generating MIPs.  cfd mip-rule 
{ explicit  | default  } 
service-instance  instance-id By default, neither MIPs nor the 
rules for generating MIPs are 
configured.  
 
Any of the following actions or cases can cause MIPs to be created or deleted after you have configured 
the 
cfd mip-rule  command: 
•   Enabling CFD (use the  cfd enable command) 
•   Creating or deleting the MEPs on a port 
•   Changes occur to the VLAN attribute of a port 
•   The rule specified in the  cfd mip-rule command changes 
Configuring CFD functions 
Configuration prerequisites 
Complete basic CFD settings.  
Configuring CC on MEPs 
After the CC function is configured, MEPs can send CCM frames to one another to check the connectivity 
between them. 
You must configure CC before configuring other CFD functions. 
 
 CAUTION: 
On different devices, the MEPs belonging to the same
 MD and MA should be configured with the same 
CCM transmission interval. 
 
To configure CC on a MEP:  
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Configure the interval field 
value in the CCM messages 
sent by MEPs.  cfd cc interval
 interval-value  
service-instance  instance-id Optional. 
By default, the interval field value is 
4. 
3.
  Enter Layer 2 Ethernet 
interface view.  interface
 interface-type 
interface-number   N/A 
4.
  Enable CCM sending on a 
MEP.  cfd cc service-instance 
instance-id 
mep  mep-id  enable  Disabled by default.
    Add page 2088 to Favourites
    image text
    Enable zoom 
    							 25 
Table 9 Relationship between the interval field value, the interval between CCM messages, and the 
timeout time of the remote MEP 
The interval field value  The interval between CCM 
messa
ges 
The timeout time of the remote 
MEP
 
4 
1 second  3.5 seconds 
5 10 second  35 seconds 
6 60 seconds  210 seconds 
7 600 seconds  2100 seconds 
 
Configuring LB on MEPs 
The LB function can verify the link state between the local MEP and the remote MEP or MIP. 
To configure LB on a MEP: 
 
Task Command Remarks 
Enable LB. cfd loopback service-instance 
instance-id
 mep mep-id  {  target-mep 
target-mep-id  |  target-mac 
mac-address  } [ number  number ]  Disabled by default. 
Available in any view 
The 
target-mep  target-mep-id  option is not 
supported if an outward-facing MEP is 
configured on the switch.  
 
Configuring LT on MEPs 
LT can trace the path between the source and target MEPs and can also locate link faults by sending LT 
messages automatically. The two functions are implemented in the following way: 
•   To implement the first function, the source MEP first sends LTM messages to the target MEP. Based 
on the LTR messages in response to the LTM messages, the path between the two MEPs can be 
identified.  
•   I n  t h e  l a t t e r  c a s e,  a f t e r  LT  m e s s a g e s  a u t o m a t ic  s e n d i n g  i s  e n a b l e d,  i f  t h e  s o u rc e  M E P  fa i l s  t o  re c eive  
the CCM frames from the target MEP within 3.5 times the transmission interval, the link between the 
two is considered faulty, and LTM frames (with the target MEP as the destination and the TTL field 
in the LTM frames set to the maximum value 255) will be sent out. Based on the LTRs that the MIPs 
return, the fault source can be located. 
To configure LT on MEPs: 
 
Step Command Remarks 
1.   Find the path between 
a source MEP and a 
target MEP.  cfd linktrace service-instance 
instance-id
 mep mep-id  
{  target-mep  target-mep-id  | 
target-mac  mac-address  } [ ttl 
ttl-value  ] [ hw-only  ]  Available in any view 
The 
target-mep  target-mep-id  option is not 
supported if an outward-facing MEP is 
configured on the switch.  
2.   Enter system view. 
system-view  N/A 
3.  Enable LT messages 
automatic sending.  cfd linktrace auto-detection 
[ size 
size-value  ]  Disabled by default.
    Add page 2089 to Favourites
    image text
    Enable zoom 
    							 26 
Configuring AIS 
The AIS function suppresses the number of error alarms reported by MEPs.  
To make an MEP in the service instance send AIS frames, you must configure the AIS frame transmission 
level to be higher than the MD level of the MEP.  
Enable AIS and configure the proper AIS frame transmission level on the target MEP, so the target MEP 
can suppress the error alarms and send the AIS frame to the MD of a higher level. If you enable AIS but 
do not configure the proper AIS frame transmission level on the target MEP, the target MEP can suppress 
the error alarms, but cannot send the AIS frames.  
To  c o n fig u re  A IS :  
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enable AIS. 
cfd ais enable  Disabled by default. 
3.  Configure the AIS 
frame transmission 
level.  cfd ais level 
level-value service-instance 
instance-id   Not configured by default. 
4.
  Configure the AIS 
frame transmission 
interval.  cfd ais period 
period-value 
service-instance  instance-id  Optional. 
1 second by default. 
 
Configuring LM 
The LM function measures frame loss between MEPs, including the number of lost frames, the frame loss 
ratio, and the average number of lost frames for the source and target MEPs.  
To configure LM: 
 
Step Command Remarks 
1.
  Enter system view. 
system-view  N/A 
2.  Configure LM.  cfd slm service-instance 
instance-id 
mep  mep-id  { target-mac 
mac-address |  target-mep 
target-mep-id  } [ number number ]  Disabled by default. 
The 
target-mep  target-mep-id  option is 
not supported if an outward-facing MEP 
is configured on the switch.  
 
  NOTE: 
The LM function takes effect only in CFD IEEE 802.1ag.  
 
Configuring one-way DM 
The one-way DM function measures the one-way frame delay between two MEPs, and monitors and 
manages the link transmission performance.  
The one-way DM function takes effect only in CFD IEEE 802.1ag.  
One-way DM requires that the clocks at the transmitting MEP and the receiving MEP be synchronized. 
For the purpose of frame delay variation measurement, the requirement for clock synchronization can be 
relaxed.
    Add page 2090 to Favourites
    image text
    Enable zoom 
    							 27 
To view the test result, use the display cfd dm one-way history command on the target MEP.  
To configure one-way DM: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Configure one-way 
DM.  cfd dm one-way service-instance 
instance-id
 mep mep-id  { target-mac 
mac-address |  target-mep 
target-mep-id  } [ number number ]  Disabled by default. 
The 
target-mep  target-mep-id  option is 
not supported if an outward-facing MEP 
is configured on the switch.  
 
Configuring two-way DM 
The two-way DM function measures the two-way frame delay, average two-way frame delay, and 
two-way frame delay variation between two MEPs, an d monitors and manages the link transmission 
performance.  
To  c o n fig u re  t wo - way  DM : 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Configure two-way 
DM.  cfd dm two-way service-instance 
instance-id
 mep mep-id  { target-mac 
mac-address |  target-mep 
target-mep-id  } [ number number ]  Disabled by default. 
The 
target-mep  target-mep-id  option is 
not supported if an outward-facing MEP 
is configured on the switch.  
 
  NOTE: 
The two-way DM function is available only un der the IEEE 802.1ag standard version of CFD.  
 
Configuring TST 
The TST function detects bit errors on a link, and monitors and manages the link transmission 
performance.  
To  c o n fig u re  TST:  
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Configure TST.  cfd tst service-instance instance-id
 
mep  mep-id  { target-mac 
mac-address |  target-mep 
target-mep-id  } [ number number ] 
[ length-of-test  length ] 
[ pattern-of-test  { all-zero  | prbs  } 
[ with-crc  ] ]  Disabled by default. 
The 
target-mep  target-mep-id  option is 
not supported if an outward-facing MEP 
is configured on the switch.
    All HP manuals Comments (0)

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