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
    							 405 
    # On Switch B, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, enable MLD 
    in VLAN interface 200, and enable IPv6 BIDIR-PIM. 
     system-view 
    [SwitchB] multicast ipv6 routing-enable 
    [SwitchB] interface vlan-interface 200 
    [SwitchB-Vlan-interface200] mld enable 
    [SwitchB-Vlan-interface200] pim ipv6 sm 
    [SwitchB-Vlan-interface200] quit 
    [SwitchB] interface vlan-interface 101 
    [SwitchB-Vlan-interface101] pim ipv6 sm 
    [SwitchB-Vlan-interface101] quit 
    [SwitchB] interface vlan-interface 102 
    [SwitchB-Vlan-interface102] pim ipv6 sm 
    [SwitchB-Vlan-interface102] quit 
    [SwitchB] pim ipv6 
    [SwitchB-pim6] bidir-pim enable 
    [SwitchB-pim6] quit 
    # On Switch C, enable IPv6 multicast routing, en able IPv6 PIM-SM on each interface, and enable 
    IPv6 BIDIR-PIM.  
     system-view 
    [SwitchC] multicast ipv6 routing-enable 
    [SwitchC] interface vlan-interface 102 
    [SwitchC-Vlan-interface102] pim ipv6 sm 
    [SwitchC-Vlan-interface102] quit 
    [SwitchC] interface vlan-interface 103 
    [SwitchC-Vlan-interface103] pim ipv6 sm 
    [SwitchC-Vlan-interface103] quit 
    [SwitchC] interface loopback 0 
    [SwitchC-LoopBack0] pim ipv6 sm 
    [SwitchC-LoopBack0] quit 
    [SwitchC] pim ipv6 
    [SwitchC-pim6] bidir-pim enable 
    # On Switch D, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, enable MLD 
    in VLAN interface 300, an d enable IPv6 BIDIR-PIM. 
     system-view 
    [SwitchD] multicast ipv6 routing-enable 
    [SwitchD] interface vlan-interface 300 
    [SwitchD-Vlan-interface300] mld enable 
    [SwitchD-Vlan-interface300] pim ipv6 sm 
    [SwitchD-Vlan-interface300] quit 
    [SwitchD] interface vlan-interface 400 
    [SwitchD-Vlan-interface400] pim ipv6 sm 
    [SwitchD-Vlan-interface400] quit 
    [SwitchD] interface vlan-interface 103 
    [SwitchD-Vlan-interface103] pim ipv6 sm 
    [SwitchD-Vlan-interface103] quit 
    [SwitchD] pim ipv6 
    [SwitchD-pim6] bidir-pim enable  
    						
    							 406 
    [SwitchD-pim6] quit 
    3. Configure C-BSR and C-RP: 
    # On Switch C, configure VLAN interface 102 as  a C-BSR, and loopback interface 0 as a C-RP for 
    the entire IPv6 BIDIR-PIM domain. 
    [SwitchC-pim6] c-bsr 2002::2 
    [SwitchC-pim6] c-rp 6001::1 bidir 
    [SwitchC-pim6] quit 
    4.  Verify the configuration: 
    To view the DF information of IPv6 BIDIR-PIM on a switch, use the  display pim ipv6 df-info 
    command: 
    # Display the DF information of  IPv6 BIDIR-PIM on Switch A.  
    [SwitchA] display pim ipv6 df-info 
     RP Address: 6001::1 
      Interface           State   DF-Pref    DF-Metric  DF-Uptime DF-Address\
     
      Vlan100             Win     100        2          01:08:50  FE80::200:\
    5EFF: 
                                                                  FE71:2800 \
    (local) 
      Vlan101             Lose    100        1          01:07:49  FE80::20F:\
    E2FF: 
                                                                  FE38:4E01 \
    # Display the DF information of IPv6 BIDIR-PIM on Switch B.  
    [SwitchB] display pim ipv6 df-info 
     RP Address: 6001::1 
      Interface           State   DF-Pref    DF-Metric  DF-Uptime DF-Address\
     
      Vlan200             Win     100        1          01:24:09  FE80::200:\
    5EFF: 
                                                                  FE71:2801 \
    (local) 
      Vlan101             Win     100        1          01:24:09  FE80::20F:\
    E2FF: 
                                                                  FE38:4E01 \
    (local) 
      Vlan102             Lose    0          0          01:23:12  FE80::20F:\
    E2FF: 
                                                                  FE15:5601 \
    # Display the DF information of IPv6 BIDIR-PIM on Switch C.  
    [SwitchC] display pim ipv6 df-info 
     RP Address: 6001::1 
      Interface           State   DF-Pref    DF-Metric  DF-Uptime DF-Address\
     
      Loop0               -       -          -          -         - 
      Vlan102             Win     0          0          01:06:07  FE80::20F:\
    E2FF: 
                                                                  FE15:5601 \
    (local) 
      Vlan103             Win     0          0          01:06:07  FE80::20F:\
    E2FF: 
                                                                  FE15:5602 \
    (local) 
    # Display the DF information of IPv6 BIDIR-PIM on Switch D.  
    [SwitchD] display pim ipv6 df-info 
     RP Address: 6001::1 
      Interface           State   DF-Pref    DF-Metric  DF-Uptime DF-Address\
     
      Vlan300             Win     100        1          01:19:53  FE80::200:\
    5EFF: 
                                                                  FE71:2803 \
    (local) 
      Vlan400             Win     100        1          00:39:34  FE80::200:\
    5EFF: 
                                                                  FE71:2802 \
    (local) 
      Vlan103             Lose    0          0          01:21:40  FE80::20F:\
    E2FF: 
                                                                  FE15:5602 \
     
    						
    							 407 
    To view the DF information of the IPv6 multicast forwarding table on a switch, use the  display 
    multicast ipv6 forwarding-table df-info  command. For more information about this command, see 
    IP Multicast Command Reference .  
    # Display the DF information of the IPv6 multicast forwarding table on Switch A. 
    [SwitchA] display multicast ipv6 forwarding-table df-info 
    Multicast DF information 
    Total 1 RP 
      
    Total 1 RP matched 
      
    00001. RP Address: 6001::1 
         MID: 0, Flags: 0x2100000:0 
         Uptime: 00:08:32 
         RPF interface: Vlan-interface101 
         List of 1 DF interfaces: 
           1: Vlan-interface100 
    # Display the DF information of the IPv6 multicast forwarding table on Switch B. 
    [SwitchB] display multicast ipv6 forwarding-table df-info 
    Multicast DF information 
    Total 1 RP 
      
    Total 1 RP matched 
      
    00001. RP Address: 6001::1 
         MID: 0, Flags: 0x2100000:0 
         Uptime: 00:06:24 
         RPF interface: Vlan-interface102 
         List of 2 DF interfaces: 
           1: Vlan-interface101 
           2: Vlan-interface200 
    # Display the DF information of the IPv6 multicast forwarding table on Switch C. 
    [SwitchC] display multicast ipv6 forwarding-table df-info 
    Multicast DF information 
    Total 1 RP 
      
    Total 1 RP matched 
      
    00001. RP Address: 6001::1 
         MID: 0, Flags: 0x2100000:0 
         Uptime: 00:07:21 
         RPF interface: LoopBack0 
         List of 2 DF interfaces: 
           1: Vlan-interface102 
           2: Vlan-interface103 
    # Display the DF information of the IPv6  multicast forwarding table on Switch D. 
    [SwitchD] display multicast ipv6 forwarding-table df-info 
    Multicast DF information 
    Total 1 RP  
    						
    							 408 
      
    Total 1 RP matched 
      
    00001. RP Address: 6001::1 
         MID: 0, Flags: 0x2100000:0 
         Uptime: 00:05:12 
         RPF interface: Vlan-interface103 
         List of 2 DF interfaces: 
           1: Vlan-interface300 
           2: Vlan-interface400 
    IPv6 PIM-SSM configuration example  
    Network requirements 
    Receivers receive VOD information through multicast. The receiver groups of different organizations form 
    stub networks, and one or more receiver hosts exist in each stub network. The entire PIM domain is 
    operating in the SSM mode. 
    Host A and Host C are IPv6 multicast receivers in two stub networks, N1 and N2. 
    The SSM group range is FF3E::/64. 
    MLDv2 runs between Switch A and N1 and between Switch B/Switch C and N2. 
    Figure 107 Network diagram 
     
    Device Interface IPv6 address Device Interface IPv6 address 
    Switch A  Vlan-int100  1001::1/64 Switch D Vlan-int300 4001::1/64 
     Vlan-int101 1002::1/64  Vlan-int101  1002::2/64 
     Vlan-int102 1003::1/64  Vlan-int105 4002::1/64 
    Ethernet
    Ethernet
    Ethernet
    N1
    N2
    Vlan-
    int101
    Vlan-
    int
    101 
    						
    							 409 
    Switch B  Vlan-int200  2001::1/64
     Switch E Vlan-int104 3001::2/64 
     Vlan-int103 
    2002::1/64  Vlan-int103  2002::2/64 
    Switch C  Vlan-int200  2001::2/64  Vlan-int102 1003::2/64 
     Vlan-int104 3001::1/64  Vlan-int105 4002::2/64  
    Configuration procedure 
    1. Enable IPv6 forwarding and configure IPv6 addresses and IPv6 unicast routing: 
    Enable IPv6 forwarding on each switch and config ure the IPv6 address and prefix length for each 
    interface as per  Figure 107. (Details not shown.) 
    Conf
    
    igure OSPFv3 on the switches in the IPv6 PIM-SSM domain to ensure network-layer 
    reachability among them. (Details not shown.) 
    2.  Enable IPv6 multicast routing, and enable IPv6 PIM-SM and MLD: 
    # Enable IPv6 multicast routing on Switch A, enable IPv6 PIM-SM on each interface, and run 
    MLDv2 on VLAN-interface 100, which connects Switch A to N1.  
     system-view 
    [SwitchA] multicast ipv6 routing-enable 
    [SwitchA] interface vlan-interface 100 
    [SwitchA-Vlan-interface100] mld enable 
    [SwitchA-Vlan-interface100] mld version 2 
    [SwitchA-Vlan-interface100] pim ipv6 sm 
    [SwitchA-Vlan-interface100] quit 
    [SwitchA] interface vlan-interface 101 
    [SwitchA-Vlan-interface101] pim ipv6 sm 
    [SwitchA-Vlan-interface101] quit 
    [SwitchA] interface vlan-interface 102 
    [SwitchA-Vlan-interface102] pim ipv6 sm 
    [SwitchA-Vlan-interface102] quit 
    The configuration on Switch B and Switch C is similar to that on Switch A. The configuration on 
    Switch D and Switch E is also similar to that on Switch A except that it is not necessary to enable 
    MLD on the corresponding interf aces on these two switches.  
    3. Configure the IPv6 SSM group range: 
    # Configure the IPv6 SSM group range to be FF3E::/64 on Switch A.  
    [SwitchA] acl ipv6 number 2000 
    [SwitchA-acl6-basic-2000] rule permit source ff3e:: 64 
    [SwitchA-acl6-basic-2000] quit 
    [SwitchA] pim ipv6 
    [SwitchA-pim6] ssm-policy 2000 
    [SwitchA-pim6] quit 
    The configuration on Switch B, Switch C, Switch D, and Switch E is similar to that on Switch A.  
    4. Verify the configuration: 
    Use the  display pim ipv6 interface  command to view the IPv6 PIM configuration and running status 
    on each interface. For example:  
    # Display IPv6 PIM configuration information on Switch A. 
    [SwitchA] display pim ipv6 interface 
     Interface             NbrCnt HelloInt   DR-Pri   DR-Address 
     Vlan100               0      30         1        1001::1  
    						
    							 410 
                                                      (local) 
     Vlan101               1      30         1        1002::2 
     Vlan102               1      30         1        1003::2 
    Assume that Host A needs to receive the information a specific IPv6 multicast source S 
    (4001::100/64) sends to IPv6 multicast group G (FF3E::101). Switch A builds an SPT toward the 
    IPv6 multicast source. Switches on the SPT path (S witch A and Switch D) have generated an (S, G) 
    entry, but Switch E, which is not on the SPT path,  does not have IPv6 multicast routing entries. You 
    can use the  display pim ipv6 routing-table command to view the IPv6 PIM routing table 
    information on each switch.  For example:  
    # Display IPv6 PIM multicast routing table information on Switch A.  
    [SwitchA] display pim ipv6 routing-table 
     Total 0 (*, G) entry; 1 (S, G) entry 
     
     (4001::100, FF3E::101) 
         Protocol: pim-ssm, Flag: 
         UpTime: 00:00:11 
         Upstream interface: Vlan-interface101 
             Upstream neighbor: 1002::2 
             RPF prime neighbor: 1002::2 
         Downstream interface(s) information: 
         Total number of downstreams: 1 
             1: Vlan-interface100 
                 Protocol: mld, UpTime: 00:00:11, Expires: 00:03:25 
    # Display IPv6 PIM multicast routing table information on Switch B.  
    [SwitchD] display pim ipv6 routing-table 
     Total 0 (*, G) entry; 1 (S, G) entry   
     
     (4001::100, FF3E::101) 
         Protocol: pim-ssm, Flag: LOC 
         UpTime: 00:08:02 
         Upstream interface: Vlan-interface300 
             Upstream neighbor: NULL 
             RPF prime neighbor: NULL 
         Downstream interface(s) information: 
         Total number of downstreams: 1 
             1: Vlan-interface105 
                 Protocol: pim-ssm, UpTime: 00:08:02, Expires: 00:03:25 
    Troubleshooting IPv6 PIM configuration 
    Failure to build a multicast distribution tree correctly 
    Symptom 
    None of the routers in the network (including routers directly connected with IPv6 multicast sources and 
    receivers) have IPv6 multicast forwarding entries. That is, a multicast distribution tree cannot be built 
    correctly and clients cannot receive IPv6 multicast data.   
    						
    							 411 
    Analysis 
    •  An IPv6 PIM routing entry is created based on an IPv6 unicast route, whichever IPv6 PIM mode is 
    running. Multicast works only when unicast does.  
    •   IPv6 PIM must be enabled on the RPF interface. An RPF neighbor must be an IPv6 PIM neighbor as 
    well. If IPv6 PIM is not enabled on the RPF interface or the RPF neighbor, the establishment of a 
    multicast distribution tree will fail, resulting in abnormal multicast forwarding.  
    •   I P v 6  P I M  re q u i re s  t h a t  t h e  s a m e  I P v 6  P I M  m o d e  ( n a m e l y,  D M  o r  S M )  m u s t  r u n  o n  t h e  e n t i re  n e t w o r k .  
    Otherwise, the establishment of a multicast distribution tree will fail, resulting in abnormal multicast 
    forwarding.  
    Solution 
    1. Use the  display ipv6 routing-table  command to verify that a unicast route exists to the IPv6 
    multicast source or the RP.  
    2.  Use the  display pim ipv6 interface  command to verify that the RPF interface is IPv6 PIM enabled. 
    If IPv6 PIM is not enabled on the interface, use the  pim ipv6 dm or pim ipv6 sm  command to enable 
    IPv6 PIM.  
    3.  Use the  display pim ipv6 neighbor  command to verify that the RPF neighbor is an IPv6 PIM 
    neighbor. 
    4.  Verify that IPv6 PIM and MLD are enabled on the in terfaces that are directly connected to the IPv6 
    multicast source and to the receiver. 
    5.  Use the  display pim ipv6 interface verbose  c o mmand to ve r i f y that the s ame  P I M  mode  i s  e nabl e d 
    on the RPF interface and the corresponding interface of the RPF neighbor router.  
    6.  Use the  display current-configuration  command to verify that the same IPv6 PIM mode is enabled 
    on all the routers in the entire network. Make sure that the same IPv6 PIM mode is enabled on all 
    the routers: IPv6 PIM-SM on all routers, or IPv6 PIM-DM on all routers.  
    IPv6 multicast data abnormally terminated on an intermediate 
    router 
    Symptom 
    An intermediate router can receive IPv6 multicast  data successfully, but the data cannot reach the last 
    hop router. An interface on the intermediate router receives data, but no corresponding (S, G) entry is 
    created in the IPv6 PIM routing table. 
    Analysis 
    •   If an IPv6 multicast forwarding boundary has been configured through the  multicast ipv6 boundary 
    command, any IPv6 multicast packet will be kept from crossing the boundary, and no routing entry 
    can be created in the IPv6 PIM routing table. 
    •   In addition, the  source-policy command filters received IPv6 multicast packets. If the IPv6 multicast 
    data fails to pass the IPV6 ACL rule defined in th is command, IPv6 PIM cannot create the route entry 
    either. 
    Solution 
    1.  Use the  display current-configuration  command to verify the IPv6 multicast forwarding boundary 
    settings. Use the  multicast ipv6 boundary  command to change the IP v6 multicast forwarding 
    boundary settings.  
    						
    							 412 
    2.
     
    Use the  display current-configuration  command to verify the IPv6 mu lticast filter configuration. 
    Change the IPv6 ACL rule defined in the source-policy  command so that the source/group address 
    of the IPv6 multicast data can pass ACL filtering. 
    RPS cannot join SPT in IPv6 PIM-SM 
    Symptom 
    An RPT cannot be established correctly, or the RPs  cannot join the SPT to the IPv6 multicast source.  
    Analysis 
    •  As the core of an IPv6 PIM-SM domain, the RPs serves specific IPv6 multicast groups. Multiple RPs 
    can coexist in a network. Make sure that the RP information on all routers is exactly the same and 
    that a specific group is mapped to the same RP. Otherwise, IPv6 multicast will fail.  
    •   In the case of the static RP mechanism, the same RP address must be configured on all the routers 
    in the entire network, including static RPs, by means of the static RP command. Otherwise, IPv6 
    multicast will fail.  
    Solution 
    1. Use the  display ipv6 routing-table  command to verify that a route is available on each router to the 
    RP.  
    2.  Use the  display pim ipv6 rp-info  command to verify that the RP  information is consistent on all 
    routers. In the case of inconsistent RP inform ation, configure consistent RP address on all the 
    routers.  
    3.  Use the  display pim ipv6 rp-info  command to verify that the same RP address has been configured 
    on all the routers throughout the network.  
    RPT establishment failure or source registration failure in IPv6 
    PIM-SM 
    Symptom 
    C-RPs cannot unicast advertise messages to the BS R. The BSR does not advertise bootstrap messages 
    containing C-RP information and has no unicast route to  any C-RP. An RPT cannot be established correctly, 
    or the DR cannot perform source registration with the RP.  
    Analysis 
    •   C-RPs periodically send advertisement messages to  the BSR by unicast. If a C-RP does not have a 
    route to the BSR, the BSR cannot receive the advertisements from the C-RP, and the bootstrap 
    messages of the BSR will not contain the information about that C-RP.  
    •   The RP is the core of an IPv6 PIM-SM domain. Make sure that the RP information on all routers is 
    exactly the same, a specific group is mapped to the  same RP, and a unicast route is available to the 
    RP.  
    Solution 
    1.  Use the  display ipv6 routing-table  command to verify that routes are available on each router to 
    the RP and the BSR, and whether a route is available between the RP and the BSR. Make sure that 
    each C-RP has a unicast route to the BSR, the BS R has a unicast route to each C-RP, and all the 
    routers in the entire network have a unicast route to the RP.   
    						
    							 413 
    2.
     
    IPv6 PIM-SM needs the support of the RP and BSR. Use the  display pim ipv6 bsr-info command to 
    verify that the BSR information is available on each router, and then use the  display pim ipv6 
    rp-info  command to check whether the RP information is correct.  
    3. Use the  display pim ipv6 neighbor  command to verify that normal  neighboring relationships have 
    been established among the routers.   
    						
    							 414 
    Configuring IPv6 MBGP (available only on the 
    HP 5500 EI) 
    IPv6 MBGP overview 
    This chapter covers configuration tasks related to multiprotocol BGP for IPv6 multicast. For information 
    about BGP and IPv6 BGP, see  Layer 3—IP Routing Configuration Guide . The term router in this chapter 
    refers to both routers and Layer 3 switches. 
    IETF defined Multiprotocol BGP (MP-BGP) to carry routing information for multiple network-layer 
    protocols.  
    For an IPv6 network, the topology for IPv6 multicast might be different from that for IPv6 unicast. To 
    distinguish them, the MP-BGP enables BGP to carry the IPv6 unicast Network Layer Reachability 
    Information (NLRI) and IPv6 multicast NLRI separately, and the multicast NLRI performs reverse path 
    forwarding (RPF) exclusively. In this way, route selection for a destination through the IPv6 unicast routing 
    table and through the IPv6 multicast routing table ha ve different results, ensuring consistent unicast 
    forwarding and normal multicast between domains. For information about RPF, see  Configuring 
    m
    
    ulticast routing and forwarding (available only on the HP 5500 EI) . 
    MP-BGP is defined in RFC 2858 (Multiprotocol Extens ions for BGP-4). The application of MP-BGP on IPv6 
    multicast is called IPv6 Multicast BGP (IPv6 MBGP). 
    IPv6 MBGP configuration task list 
     
    Task   Remarks 
    Configuring basic 
    IPv6 MBGP functions  Configuring an IPv6 MBGP peer 
    Required
     Configuring a preferred value for  routes from a peer or a peer 
    group  Optional
     
    Controlling route 
    distribution and 
    reception  Injecting a local IPv6 MBGP route 
    Optional
     
    Configuring IPv6 MBGP route redistribution  Optional
     
    Configuring IPv6 MBGP route summarization  Optional
     
    Advertising a default route to a peer or peer group  Optional
     
    Configuring outbound IPv6 MBGP route filtering  Optional
     
    Configuring inbound IPv6 MBGP route filtering  Optional
     
    Configuring IPv6 MBGP route dampening  Optional
     
    Configuring IPv6 
    MBGP route 
    attributes  Configuring IPv6 MBGP route preferences 
    Optional Configuring the default local preference  
    Configuring the MED attribute 
    Configuring the next hop attribute   Optional
     
    Configuring the as_path attribute  Optional
     
    Tuning and  Configuring IPv6 MBGP soft reset 
    Optional
      
    						
    All HP manuals Comments (0)

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