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

HP 5500 Ei 5500 Si Switch Series Configuration Guide

    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+.

    Page
    of 2513
    							 48 
    # Enable DLDP globally. 
     system-view 
    [DeviceB] dldp enable 
    # Configure GigabitEthernet 1/0/49 to operate in full duplex mode and at 1000 Mbps, and 
    enable DLDP on it. 
    [DeviceB] interface gigabitethernet 1/0/49 
    [DeviceB-GigabitEthernet1/0/49] duplex full 
    [DeviceB-GigabitEthernet1/0/49] speed 1000 
    [DeviceB-GigabitEthernet1/0/49] dldp enable 
    [DeviceB-GigabitEthernet1/0/49] quit 
    # Configure GigabitEthernet 1/0/50 to operate  in full duplex mode and at 1000 Mbps, and 
    enable DLDP on it. 
    [DeviceB] interface gigabitethernet 1/0/50 
    [DeviceB-GigabitEthernet1/0/50] duplex full 
    [DeviceB-GigabitEthernet1/0/50] speed 1000 
    [DeviceB-GigabitEthernet1/0/50] dldp enable 
    [DeviceB-GigabitEthernet1/0/50] quit 
    # Set the DLDP mode to enhanced. 
    [DeviceB] dldp work-mode enhance 
    # Set the port shutdown mode to auto. 
    [DeviceB] dldp unidirectional-shutdown auto 
    3.  Verify the configuration: 
    After the configurations are complete, you can use the display dldp  command to display the DLDP 
    configuration information on ports.  
    # Display the DLDP configuration information on  all the DLDP-enabled ports of Device A. 
    [DeviceA] display dldp 
     DLDP global status : enable 
     DLDP interval : 5s 
     DLDP work-mode : enhance 
     DLDP authentication-mode : none 
     DLDP unidirectional-shutdown : auto 
     DLDP delaydown-timer : 1s 
     The number of enabled ports is 2. 
     
    Interface GigabitEthernet1/0/49 
     DLDP port state : advertisement 
     DLDP link state : up 
     The neighbor number of the port is 1. 
             Neighbor mac address : 0023-8956-3600 
             Neighbor port index : 59 
             Neighbor state : two way 
             Neighbor aged time : 11 
     
    Interface GigabitEthernet1/0/50 
     DLDP port state : advertisement 
     DLDP link state : up 
     The neighbor number of the port is 1.  
    						
    							 49 
             Neighbor mac address : 0023-8956-3600 
             Neighbor port index : 60 
             Neighbor state : two way 
             Neighbor aged time : 12 
    The output shows that both GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50 are in 
    Advertisement state, which means both links are bidirectional. 
    # Enable system information monitoring on Devi ce A, and enable the display of log and trap 
    information. 
    [DeviceA] quit 
     terminal monitor 
     terminal logging 
     terminal trapping 
    The following log and trap informat ion is displayed on Device A: 
     
    #Jan 18 17:36:18:798 2010 DeviceA DLDP/1/TrapOfUnidirectional: -Slot=1; \
    Trap 
    1.3.6.1.4.1.25506.2.43.2.1.1 : DLDP detects a unidirectional link in port 17825792. 
     
    %Jan 18 17:36:18:799 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/\
    0/49 link 
    status is DOWN. 
    %Jan 18 17:36:18:799 2010 DeviceA DLDP/3/DLDP_UNIDIRECTION_AUTO: -Slot=1\
    ; DLDP 
    detects a unidirectional link on port GigabitEthernet1/0/49. The transce\
    iver has 
    malfunction in the Tx direction or cross-connected links exist between the local device 
    and its neighbor. The shutdown mode is AUTO. DLDP shuts down the port. 
    #Jan 18 17:36:20:189 2010 DeviceA DLDP/1/TrapOfUnidirectional: -Slot=1; \
    Trap 
    1.3.6.1.4.1.25506.2.43.2.1.1 : DLDP detects a unidirectional link in port 17825793. 
     
    %Jan 18 17:36:20:189 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/\
    0/50 link 
    status is DOWN. 
    %Jan 18 17:36:20:190 2010 DeviceA DLDP/3/DLDP_UNIDIRECTION_AUTO: -Slot=1\
    ; DLDP 
    detects a unidirectional link on port GigabitEthernet1/0/50. The transce\
    iver has 
    malfunction in the Tx direction or cross-connected links exist between the local device 
    and its neighbor. The shutdown mode is AUTO. DLDP shuts down the port. 
     
    %Jan 15 16:54:56:040 2010 DeviceA DLDP/3/DLDP_UNIDIRECTION_AUTO_ENHANCE: -Slot=1; In 
    enhanced DLDP mode, port GigabitEthernet1/0/49 cannot detect its aged-out neighbor. 
    The transceiver has malfunction in the Tx direction or cross-connected l\
    inks exist 
    between the local device and its neighbor. The shutdown mode is AUTO. DLDP shuts down 
    the port. 
    The output shows that the link status of both  GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50 
    is down, and DLDP has detected a unidirectional  link on both ports and has automatically shut 
    them down.  
    Assume that in this example, the unidirectional links are caused by cross- connected fibers. Correct 
    the fiber connections on detecting the unidirectional  link problem. As a result, the ports shut down 
    by DLDP automatically recover, and Device  A displays the following log information: 
     
    %Jan 18 17:47:33:869 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/\
    0/49 link 
    status is UP. 
    %Jan 18 17:47:35:894 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/\
    0/50 link 
    status is UP.  
    						
    							 50 
    The output shows that the link status of both GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50 
    is now up. 
    Manually shutting down unidirectional links 
    Network requirements 
    •   As shown in  Figure 12, D evice A and Device B are connected with two fiber pairs. 
    •   Configure DLDP to send information when a unidirectional link is detected, to remind the network 
    administrator to manually shut down the faulty port. 
    Figure 12  Network diagram 
     
     
    Configuration procedure 
    1. Configure Device A: 
    # Enable DLDP globally. 
     system-view 
    [DeviceA] dldp enable 
    # Configure GigabitEthernet 1/0/49 to operate  in full duplex mode and at 1000 Mbps, and 
    enable DLDP on the port. 
    [DeviceA] interface gigabitethernet 1/0/49 
    [DeviceA-GigabitEthernet1/0/49] duplex full 
    [DeviceA-GigabitEthernet1/0/49] speed 1000 
    [DeviceA-GigabitEthernet1/0/49] dldp enable 
    [DeviceA-GigabitEthernet1/0/49] quit 
    # Configure GigabitEthernet 1/0/50 to operate  in full duplex mode and at 1000 Mbps, and 
    enable DLDP on the port. 
    [DeviceA] interface gigabitethernet 1/0/50  
    						
    							 51 
    [DeviceA-GigabitEthernet1/0/50] duplex full 
    [DeviceA-GigabitEthernet1/0/50] speed 1000 
    [DeviceA-GigabitEthernet1/0/50] dldp enable 
    [DeviceA-GigabitEthernet1/0/50] quit 
    # Set the DLDP mode to enhanced. 
    [DeviceA] dldp work-mode enhance 
    # Set the port shutdown mode to manual. 
    [DeviceA] dldp unidirectional-shutdown manual 
    2. Configure Device B: 
    # Enable DLDP globally. 
     system-view 
    [DeviceB] dldp enable 
    # Configure GigabitEthernet 1/0/49 to operate  in full duplex mode and at 1000 Mbps, and 
    enable DLDP on it. 
    [DeviceB] interface gigabitethernet 1/0/49 
    [DeviceB-GigabitEthernet1/0/49] duplex full 
    [DeviceB-GigabitEthernet1/0/49] speed 1000 
    [DeviceB-GigabitEthernet1/0/49] dldp enable 
    [DeviceB-GigabitEthernet1/0/49] quit 
    # Configure GigabitEthernet 1/0/50 to operate  in full duplex mode and at 1000 Mbps, and 
    enable DLDP on it. 
    [DeviceB] interface gigabitethernet 1/0/50 
    [DeviceB-GigabitEthernet1/0/50] duplex full 
    [DeviceB-GigabitEthernet1/0/50] speed 1000 
    [DeviceB-GigabitEthernet1/0/50] dldp enable 
    [DeviceB-GigabitEthernet1/0/50] quit 
    # Set the DLDP mode to enhanced. 
    [DeviceB] dldp work-mode enhance 
    # Set the port shutdown mode to manual. 
    [DeviceB] dldp unidirectional-shutdown manual 
    3.  Verify the configuration: 
    After the configurations are complete, you can use the display dldp  command to display the DLDP 
    configuration information on ports.  
    # Display the DLDP configuration information on  all the DLDP-enabled ports of Device A. 
    [DeviceA] display dldp 
     DLDP global status : enable 
     DLDP interval : 5s 
     DLDP work-mode : enhance 
     DLDP authentication-mode : none 
     DLDP unidirectional-shutdown : manual 
     DLDP delaydown-timer : 1s 
     The number of enabled ports is 2. 
     
    Interface GigabitEthernet1/0/49 
     DLDP port state : advertisement 
     DLDP link state : up  
    						
    							 52 
     The neighbor number of the port is 1. 
             Neighbor mac address : 0023-8956-3600 
             Neighbor port index : 59 
             Neighbor state : two way 
             Neighbor aged time : 11 
     
    Interface GigabitEthernet1/0/50 
     DLDP port state : advertisement 
     DLDP link state : up 
     The neighbor number of the port is 1. 
             Neighbor mac address : 0023-8956-3600 
             Neighbor port index : 60 
             Neighbor state : two way 
             Neighbor aged time : 12 
    The output shows that both GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50 are in 
    Advertisement state, which means both links are bidirectional. 
    # Enable system information monitoring on Devi ce A, and enable the display of log and trap 
    information. 
    [DeviceA] quit 
     terminal monitor 
     terminal logging 
     terminal trapping 
    The following log and trap informat ion is displayed on Device A: 
     
    #Jan 18 18:10:38:481 2010 DeviceA DLDP/1/TrapOfUnidirectional: -Slot=1; \
    Trap 
    1.3.6.1.4.1.25506.2.43.2.1.1 : DLDP detects a unidirectional link in port 17825792. 
     
    %Jan 18 18:10:38:481 2010 DeviceA DLDP/3/DLDP_UNIDIRECTION_MANUAL: -Slot\
    =1; DLDP 
    detects a unidirectional link on port GigabitEthernet1/0/49. The transce\
    iver has 
    malfunction in the Tx direction or cross-connected links exist between the local device 
    and its neighbor. The shutdown mode is MANUAL. The port needs to be shut down by the 
    user. 
    #Jan 18 18:10:38:618 2010 DeviceA DLDP/1/TrapOfUnidirectional: -Slot=1; \
    Trap 
    1.3.6.1.4.1.25506.2.43.2.1.1 : DLDP detects a unidirectional link in port 17825793. 
     
    %Jan 18 18:10:38:618 2010 DeviceA DLDP/3/DLDP_UNIDIRECTION_MANUAL: -Slot\
    =1; DLDP 
    detects a unidirectional link on port GigabitEthernet1/0/50. The transce\
    iver has 
    malfunction in the Tx direction or cross-connected links exist between the local device 
    and its neighbor. The shutdown mode is MANUAL. The port needs to be shut down by the 
    user. 
    The output shows that DLDP has detected a unidir ectional link on both GigabitEthernet 1/0/49 
    and GigabitEthernet 1/0/50, and  is asking you to shut down the faulty ports manually.  
    After you shut down GigabitEthernet 1/0/49 an d GigabitEthernet 1/0/50, the following log 
    information is displayed: 
     system-view 
    [DeviceA] interface gigabitethernet 1/0/49 
    [DeviceA-GigabitEthernet1/0/49] shutdown 
    %Jan 18 18:16:12:044 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/\
    0/49 link 
    status is DOWN.  
    						
    							 53 
    [DeviceA-GigabitEthernet1/0/49] quit 
    [DeviceA] interface gigabitethernet 1/0/50 
    [DeviceA-GigabitEthernet1/0/50] shutdown 
    %Jan 18 18:18:03:583 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/\
    0/50 link 
    status is DOWN. 
    The output shows that the link status of both GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50 
    is down. 
    Assume that in this example, the unidirectional links are caused by cross- connected fibers. Correct 
    the fiber connections, and then brin g up the ports shut down earlier. 
    # On Device A, bring up GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50: 
    [DeviceA-GigabitEthernet1/0/50] undo shutdown 
    [DeviceA-GigabitEthernet1/0/50] 
    %Jan 18 18:22:11:698 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/\
    0/50 link 
    status is UP. 
    [DeviceA-GigabitEthernet1/0/50] quit 
    [DeviceA] interface gigabitethernet 1/0/49 
    [DeviceA-GigabitEthernet1/0/49] undo shutdown 
    [DeviceA-GigabitEthernet1/0/49] 
    %Jan 18 18:22:46:065 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/\
    0/49 link 
    status is UP. 
    The output shows that the link status of both GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50 is 
    now up. 
    Troubleshooting DLDP 
    Symptom 
    Two DLDP-enabled devices, Device A and Device B, are connected through two fiber pairs, in which two 
    fibers are cross-connected. The unidirectional links cannot be detected; all the four ports involved are in 
    Advertisement state. 
    Analysis 
    The problem can be caused by the following. 
    •   The intervals to send Advertisement packets on Device A and Device B are not the same. 
    •   DLDP authentication modes/passwords on Device A and Device B are not the same. 
    Solution 
    Make sure the interval to send Advertisement packets, the authentication mode, and the password 
    configured on Device A and Device B are the same.  
    						
    							 54 
    Configuring RRPP 
    RRPP overview 
    The Rapid Ring Protection Protocol (RRPP) is a link layer protocol designed for Ethernet rings. RRPP can 
    prevent broadcast storms caused by data loops when an Ethernet ring is healthy, and rapidly restore the 
    communication paths between the nodes in the event that a link is disconnected on the ring. 
    Background 
    Metropolitan area networks (MANs) and enterprise  networks usually use the ring structure to improve 
    reliability. However, services will be interrupted if any node in the ring network fails. A ring network 
    usually uses Resilient Packet Ring (RPR) or Ethernet rings. RPR is high in cost because it needs dedicated 
    hardware. Contrarily, the Ethernet ring technology is more mature and economical, so it is increasingly 
    widely used in MANs and enterprise networks.  
    Rapid Spanning Tree Protocol (RSTP), Per VLAN Spa nning Tree (PVST), Multiple Spanning Tree Protocol 
    (MSTP), and RRPP can eliminate Layer-2 loops. RSTP, PVST, and MSTP are mature. However, they take 
    several seconds to converge. RRPP is an Ethernet ring-specific data link layer protocol, and it converges 
    faster than RSTP, PVST, and MSTP. Additionally, th e convergence time of RRPP is independent of the 
    number of nodes in the Ethernet ring. RRPP  can be applied to large-diameter networks. 
    Basic concepts in RRPP 
    Figure 13 RRPP networking diagram 
     
     
    RRPP domain 
    The interconnected devices with the same domain ID and control VLANs constitute an RRPP domain. An 
    RRPP domain contains the following elements—primary  ring, subring, control VLAN, master node, transit 
    node, primary port, secondary port, common port, edge port, and so on.  
    As shown in  Figure 13, Do
     main 1 is an RRPP domain, including two RRPP rings: Ring 1 and Ring 2. All 
    the nodes on the two RRPP rings belong to the RRPP domain.  
    Device A
    Master node
    Device D
    Transit node Domain 1
    Ring 1
    Port 2 Port 1
    Port 2
    Port 1
    Port 2 Port 1
    Port 2 Port 1
    Device C
    Assistant edge node Device B
    Edge node
    Ring 2
    Port 3
    Port 3 Port 1
    Port 2
    Device E
    Master node 
    						
    							 55 
    RRPP ring 
    A ring-shaped Ethernet topology is called an RRPP ring. RRPP rings fall into two types: primary ring and 
    subring. You can configure a ring as either the primary ring or a subring by specifying its ring level. The 
    primary ring is of level 0, and a subring is of level 1. A n  R R P P  d o m a i n  c o n t a i n s  o n e  o r  m u l t i p l e  R R P P  r i n g s ,  
    one serving as the primary ring and the others serving as subrings. A ring can be in one of the following 
    states: 
    •   Health state —All the physical links on the Ethernet ring are connected 
    •   Disconnect state —Some physical links on the Ethernet ring are broken  
    As shown in  Figure 13, D
     omain 1 contains two RRPP rings: Ring 1 and Ring 2. The level of Ring 1 is set 
    to 0, and that of Ring 2 is set to 1. Ring 1 is configured as the primar y ring, and Ring 2 is configured as 
    a subring.  
    Control VLAN and data VLAN 
    1.  Control VLAN 
    In an RRPP domain, a control VLAN is a VLAN de dicated to transferring Rapid Ring Protection 
    Protocol Data Units (RRPPDUs). On a device, the po rts accessing an RRPP ring belong to the control 
    VLANs of the ring, and only such ports can join the control VLANs.  
    An RRPP domain is configured with two control VLANs: one primary control VLAN, which is the 
    control VLAN for the primary ring, and one secon dary control VLAN, which is the control VLAN for 
    subrings. All subrings in the same RRPP domain  share the same secondary control VLAN. After you 
    specify a VLAN as the primary control VLAN, the system automatically configures the VLAN whose 
    ID is the primary control VLAN ID plus one as the secondary control VLAN.  
    IP address configuration is prohibited on the control VLAN interfaces.  
    2.  Data VLAN 
    A data VLAN is a VLAN dedicated to transfe rring data packets. Both RRPP ports and non-RRPP 
    ports can be assigned to a data VLAN.  
    Node 
    Each device on an RRPP ring is a node. The role of  a node is configurable. RRPP has the following node 
    roles: 
    •   Master node —Each ring has one and only one master no de. The master node initiates the polling 
    mechanism and determines the op erations to be performed after a change in topology.  
    •   Transit  node —Transit nodes include all the nodes except the master node on the primary ring and 
    all the nodes on subrings except the master nodes and the nodes where the primary ring intersects 
    with the subrings. A transit node monitors the state  of its directly-connected RRPP links and notifies 
    the master node of the link state  changes, if any. Based on the link state changes, the master node 
    decides the operations to be performed. 
    •   Edge  node —A node residing on both the primary ring  and a subring at the same time. An edge 
    node is a special transit node that  serves as a transit node on the primary ring and an edge node 
    on the subring.  
    •   Assistant-edge node —A node residing on both the primary ri ng and a subring at the same time. An 
    assistant-edge node is a special transit node that serves as a transit node on the primary ring and 
    an assistant-edge node on the subr i n g .  T h i s  n o d e  w o r k s  i n  c o n j u n c t i o n  w i t h  t h e  e d g e  n o d e  t o  d e t e c t  
    the integrity of the primary ring and to perform loop guard.  
    As shown in  Figure 13, R
     ing 1 is the primary ring and Ring 2 is a subring. Device A is the master node 
    of Ring 1, and Device B, Device C, and Device D are the transit nodes of Ring 1. Device E is the master 
    no de  of  Ri ng  2, D evic e  B  i s  the  e dg e  no de  of  Ri ng  2, and D evic e  C  i s the  ass i stant -edg e  no de  of  Ri ng  2.  
    						
    							 56 
    Primary port and secondary port 
    Each master node or transit node has two ports connected to an RRPP ring, one serving as the primary 
    port and the other serving as the secondary port. You can determine the port’s role.  
    1.  In terms of functionality, the primary port and  the secondary port of a master node have the 
    following differences: 
    {  The primary port and the secondary port are designed to play the role of sending and 
    receiving loop-detect packets respectively. 
    { When an RRPP ring is in Health state, the seco ndary port of the master node will logically deny 
    data VLANs and permit only the packets of the control VLANs.  
    {  When an RRPP ring is in Disconnect state, the  secondary port of the master node will permit 
    data VLANs (forward packets of data VLANs). 
    2.  In terms of functionality, the primary port and  the secondary port of a transit node have no 
    difference. Both are designed fo r transferring protocol packets and data packets over an RRPP 
    ring.  
    As shown in  Figure 13, D
     evice A is the master node of Ring 1. Port 1 and Port 2 are the primary port and 
    the secondary port of the master node on Ring 1 respectively. Device B, Device C, and Device D are the 
    transit nodes of Ring 1. Their Port 1 and Port 2 are the primary port and the secondary port on Ring 1 
    respectively.  
    Common port and edge port 
    The ports connecting the edge node  and assistant-edge node to the primary ring are common ports. The 
    ports connecting the edge node  and assistant-edge node only to the subrings are edge ports. 
    As shown in Figure 13 , D
    evice B and Device C lie on Ring 1 and Ring 2. Device B’s Port 1 and Port 2 and 
    Device C’s Port 1 and Port 2 access the primary ring, so they are common ports. Device B’s Port 3 and 
    Device C’s Port 3 access only the subring, so they are edge ports.  
    RRPP ring group 
    To reduce Edge-Hello traffic, you can configure a grou p of subrings on the edge node or assistant-edge 
    node. For more information about Edge-Hello packets, see  RRPPDUS.
     You must configure a device as 
    the edge node of these subrings, and another device  as the assistant-edge node of these subrings. 
    Additionally, the subrings of the edge node and assi stant-edge node must connect to the same subring 
    packet tunnels in major ring (SRPTs) so that Edge-Hello  packets of the edge node of these subrings travel 
    to the assistant-edge node of thes e subrings over the same link.  
    An RRPP ring group configured on the edge node is an edge node RRPP ring group, and an RRPP ring 
    group configured on an assistant-edge node is an  assistant-edge node RRPP ring group. Up to one 
    subring in an edge node RRPP ring group is allowed to send Edge-Hello packets.  
    RRPPDUS 
    Table 18  RRPPDU types and their functions 
    T
    ype Description 
    Hello  The master node initiates Hello packets to detect the integrity of a ring in a 
    network. 
    Link-Down The transit node, the edge node, or the assistant-edge node initiates Link-Down 
    packets to notify the master node of the disappearance of a ring in case of a link 
    failure.   
    						
    							 57 
    Type Description 
    Common-Flush-FDB The master node initiates Common-Fl
    ush-FDB (FDB stands for Forwarding 
    Database) packets to instruct the transi t nodes to update their own MAC entries 
    and ARP/ND entries when an RRPP ring  transits to Disconnect state.  
    Complete-Flush-FDB The master node initiates Complete-Flush-FDB packets to instruct the transit nodes 
    to update their own MAC entries and ARP/
    ND entries and release blocked ports 
    from being blocked temporarily when an  RRPP ring transits to Health state. 
    Edge-Hello The edge node initiates Edge-Hello pa
    ckets to examine the SRPTs between the 
    edge node and the assistant-edge node.  
    Major-Fault  The assistant-edge node initiates Major-Fa
    ult packets to notify the edge node of 
    SRPT failure when an SRPT between edge node and assistant-edge node is torn 
    down.  
     
      NOTE:  
    RRPPDUs of subrings are transmitted as data packets  in the primary ring, and RRPPDUs of the primary 
    ring can only be transmitte d within the primary ring. 
     
    RRPP timers 
    When RRPP checks the link state of an Ethernet ring, the master node sends Hello packets out of the 
    primary port according to the Hello timer and determines whether its secondary port receives the Hello 
    packets based on the Fail timer.  
    •  The Hello timer specifies the interval at which the master node sends Hello packets out of the 
    primary port.  
    •   The Fail timer specifies the maximum delay betwee n the master node sending Hello packets out of 
    the primary port and the secondary port receiving the Hello packets from the primary port. If the 
    secondary port receives the Hello packets sent by th e local master node before the Fail timer expires, 
    the overall ring is in Health state. Otherwise, the ring transits into the Disconnect state.  
     
      NOTE:  
    In an RRPP domain, a transit node learns the Hello timer value and the Fail timer value on the master node
    through the received Hello packets, ensuring that all  nodes in the ring network are consistent in the two 
    timer settings. 
     
    How RRPP works 
    Polling mechanism 
    The polling mechanism is used by the master node of an RRPP ring to check the Health state of the ring 
    network. 
    The master node periodically sends Hello packets out  of its primary port, and these Hello packets travel 
    through each transit node on the ring in turn:  
    •   If the ring is complete, the secondary port of the  master node will receive Hello packets before the 
    Fail timer expires and the master node will keep the secondary port blocked.  
    •   If the ring is torn down, the secondary port of  the master node will fail to receive Hello packets 
    before the Fail timer expires. The master node  will release the secondary port from blocking data  
    						
    All HP manuals Comments (0)

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