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
    							 105 
    commands configured in PIM view can still take effect. In addition, in IGMPv1, the designated router (DR) 
    i s  e l e c t e d  b y  t h e  w o r k i n g  m u l t i c a s t  ro u t i n g  p ro t o c o l  ( s u c h  a s  P I M )  t o  s e r v e  a s  t h e  I G M P  q u e r i e r.  T h e re f o re ,  
    a downstream interface running IGMPv1 cannot be elec ted as the DR and thus cannot serve as the IGMP 
    querier.  
    You cannot enable IGMP proxying on a VLAN interface with IGMP snooping enabled, or vice versa. 
    Configuration procedure 
    To enable IGMP proxying:  
    Step Command Remarks 
    1.   Enter system view. 
    system-view  N/A 
    2.  Enter interface view. 
    interface interface-type interface-number N/A 
    3.  Enable the IGMP 
    proxying feature.  igmp proxying enable 
    Disabled by default 
     
    Configuring multicast forwarding on a downstream interface 
    Only queriers can forward multicast traffic but non-queriers have no multicast forwarding capabilities. 
    This design helps avoid duplicate multicast flows.  It is the same on IGMP proxy switches. Only the 
    downstream interfaces acting as a querier can forward multicast traffic to downstream hosts.  
    However, when a downstream interface of a proxy switch fails to win the querier election, you must 
    enable multicast forwarding on this interface.  
     
      IMPORTANT: 
    On a multi-access network with more than one 
    IGMP proxy switch, you cannot enable multicast 
    forwarding on any other non-querier downstream inte rface after one of the downstream interfaces of 
    these IGMP proxy switches has been elected as the querier. Otherwise, duplicate multicast flows mi
    ght be
    received on the multi-access network.  
     
    To enable multicast forwarding on a downstream interface:  
    Step Command Remarks 
    1.   Enter system view. 
    system-view  N/A 
    2.  Enter interface view.  interface 
    interface-type 
    interface-number   N/A 
    3.
      Enable multicast forwarding on 
    a non-querier downstream 
    interface.  igmp proxying forwarding 
    Disabled by default 
     
    Displaying and maintaining IGMP 
      
    						
    							 106 
    Task   Command  
    Display IGMP group information.  display igmp [ 
    all-instance | 
    vpn-instance  vpn-instance-name  ] 
    group  [ group-address  | interface  
    interface-type interface-number  ] 
    [ static  |  verbose  ] [ | { begin | 
    exclude  | include  } 
    regular-expression  ]
      Available in any view 
    Display the Layer 2 port 
    information of IGMP groups. 
    display igmp group port-info
     [ vlan  
    vlan-id  ] [ slot  slot-number  ] 
    [ verbose  ] [ | { begin |  exclude | 
    include  } regular-expression ]
     Available in any view
     
    Display information about the hosts 
    tracked by IGMP on an interface.  display igmp host interface
     
    interface-type interface-number  
    group  group-address  [ source 
    source-address ] [  | { begin | 
    exclude  | include  } 
    regular-expression  ]  Available in any view 
    Display information about the hosts 
    tracked by IGMP on the Layer 2 
    ports.  display igmp host port-info
     vlan  
    vlan-id  group  group-address  
    [ source  source-address ] [ vlan 
    vlan-id  ] [ slot  slot-number  ] [ | 
    {  begin |  exclude | include  } 
    regular-expression  ]  Available in any view 
    Display IGMP configuration and 
    operation information.  display igmp
     [ all-instance | 
    vpn-instance  vpn-instance-name  ] 
    interface  [ interface-type 
    interface-number  ] [ verbose ] [ | 
    {  begin |  exclude | include  } 
    regular-expression  ]
      Available in any view
     
    Display the information of IGMP 
    proxying groups.  display igmp [ 
    all-instance | 
    vpn-instance  vpn-instance-name  ] 
    proxying group [  group-address ] 
    [ verbose  ] [ | { begin |  exclude | 
    include  } regular-expression ]  Available in any view 
    Display information in the IGMP 
    routing table.  display igmp [ 
    all-instance | 
    vpn-instance  vpn-instance-name  ] 
    routing-table  [ source-address 
    [ mask  { mask  | mask-length  } ] | 
    group-address  [ mask { mask | 
    mask-length  } ] | flags { act | suc  } ] 
    * [ |  { begin |  exclude | include  } 
    regular-expression  ]
      Available in any view
     
    Display IGMP SSM mappings.  display igmp
     [ all-instance | 
    vpn-instance  vpn-instance-name  ] 
    ssm-mapping  group-address  [ | 
    {  begin |  exclude | include  } 
    regular-expression  ]  Available in any view  
    						
    							 107 
    Task   Command  
    Display the multicast group 
    information created from IGMPv1 
    and IGMPv2 reports based on the 
    configured IGMP SSM mappings.  display igmp
     [ all-instance | 
    vpn-instance  vpn-instance-name  ] 
    ssm-mapping  group  
    [ group-address  | interface 
    interface-type  interface-number  ] 
    [ verbose  ] [ | { begin |  exclude | 
    include  } regular-expression ]  Available in any view 
    Display information about the hosts 
    that join the group based on IGMP 
    SSM mappings on an interface.  display igmp ssm-mapping host 
    interface
     interface-type 
    interface-number  group  
    group-address  source 
    source-address [  | { begin | 
    exclude  | include  } 
    regular-expression  ]  Available in any view 
    Remove all the dynamic IGMP 
    group entries of IGMP groups.  reset igmp [ all-instance
     | 
    vpn-instance  vpn-instance-name  ] 
    group  { all  |  interface  
    interface-type interface-number 
    {  all  | group-address  [ mask  { mask  
    |  mask-length  } ] [ source-address 
    [  mask  { mask  | mask-length  } ] ] } }Available in user view
     
    Remove all the dynamic Layer 2 
    port entries of IGMP groups.  reset igmp group port-info { all
     |  
    group-address  } [ vlan vlan-id  ]  Available in user view 
    Clear IGMP SSM mappings.  reset igmp
     [ all-instance  | 
    vpn-instance  vpn-instance-name  ] 
    ssm-mapping  group  { all | 
    interface  interface-type  
    interface-number  { all | 
    group-address  [ mask { mask | 
    mask-length  } ] [ source-address 
    [  mask  { mask  | mask-length  } ] ] } }
     
    Available in user view 
     
     IMPORTANT: 
    The 
    reset igmp group  command might cause an interruption of  receivers’ reception of multicast data. 
     
    The reset igmp group  command cannot remove static IGMP group entries. 
    The  display igmp host interface  command can display information about the hosts tracked by IGMP on 
    Layer 3 interfaces other than VLAN interfaces.  
    The  display igmp ssm-mapping host interface command can display information about the hosts that 
    join the group based on IGMP SSM mappings on  Layer 3 interfaces other than VLAN interfaces.  
    						
    							 108 
    IGMP configuration examples 
    Basic IGMP functions configuration example 
    Network requirements 
    Receivers receive VOD information through multicast. Receivers of different organizations form stub 
    networks N1 and N2, and Host A and Host C are receivers in N1 and N2 respectively.  
    IGMPv2 runs between Switch A and N1. IGMPv2 runs  between the other two switches and N2. Switch 
    B acts as the IGMP querier in N2 because it has a lower IP address.   
    The hosts in N1 can join only multicast group 224.1.1.1, and the hosts in N2 can join any multicast 
    groups. 
    Figure 35  Network diagram 
     
     
    Configuration procedure 
    1. Configure IP addresses and unicast routing:  
    # Configure the IP address and subnet mask of each interface as per  Figure 35. (Details not 
    shown.)
    
     
    # Configure the OSPF protocol for interoperation  on the PIM network. Ensure the network-layer 
    interoperation on the PIM network and dynamic u pdate of routing information among the switches 
    through a unicast routing protocol. (Details not shown.) 
    2.  Enable IP multicast routing, and enable PIM-DM and IGMP: 
    # Enable IP multicast routing on Switch A, enable  PIM-DM on each interface, and enable IGMP on 
    VLAN-interface 100.  
     system-view 
    [SwitchA] multicast routing-enable 
    [SwitchA] interface vlan-interface 100 
    [SwitchA-Vlan-interface100] igmp enable 
    Switch A
    Switch B
    Switch C Querier
    PIM network
    N1
    N2
    Receiver Receiver
    Host A
    Host B
    Host C
    Host DVlan-int100
    10.110.1.1/24
    Vlan-int200
    10.110.2.1/24
    Vlan-int200
    10.110.2.2/24
    Vlan-int101
    Vlan-int201
    Vlan-int202 
    						
    							 109 
    [SwitchA-Vlan-interface100] pim dm 
    [SwitchA-Vlan-interface100] quit 
    [SwitchA] interface vlan-interface 101 
    [SwitchA-Vlan-interface101] pim dm 
    [SwitchA-Vlan-interface101] quit 
    # Enable IP multicast routing on Switch B, enable PIM-DM on each interface, and enable IGMP on 
    VLAN-interface 200.  
     system-view 
    [SwitchB] multicast routing-enable 
    [SwitchB] interface vlan-interface 200 
    [SwitchB-Vlan-interface200] igmp enable 
    [SwitchB-Vlan-interface200] pim dm 
    [SwitchB-Vlan-interface200] quit 
    [SwitchB] interface vlan-interface 201 
    [SwitchB-Vlan-interface201] pim dm 
    [SwitchB-Vlan-interface201] quit 
    # Enable IP multicast routing on Switch C, enable PIM-DM on each interface, and enable IGMP on 
    VLAN-interface 200.  
     system-view 
    [SwitchC] multicast routing-enable 
    [SwitchC] interface vlan-interface 200 
    [SwitchC-Vlan-interface200] igmp enable 
    [SwitchC-Vlan-interface200] pim dm 
    [SwitchC-Vlan-interface200] quit 
    [SwitchC] interface vlan-interface 202 
    [SwitchC-Vlan-interface202] pim dm 
    [SwitchC-Vlan-interface202] quit 
    3. Configure a multicast group filter: 
    # Configure a multicast group filter on Switch A,  so that the hosts connected to VLAN-interface 100 
    can join only multicast group 224.1.1.1. 
    [SwitchA] acl number 2001 
    [SwitchA-acl-basic-2001] rule permit source 224.1.1.1 0 
    [SwitchA-acl-basic-2001] quit 
    [SwitchA] interface vlan-interface 100 
    [SwitchA-Vlan-interface100] igmp group-policy 2001 
    [SwitchA-Vlan-interface100] quit 
    4.  Verify the configuration:  
    # Display IGMP information on VLAN-interface 200 of Switch B.  
    [SwitchB] display igmp interface vlan-interface 200 
     Vlan-interface200(10.110.2.1): 
       IGMP is enabled 
       Current IGMP version is 2 
       Value of query interval for IGMP(in seconds): 60 
       Value of other querier present interval for IGMP(in seconds): 125 
       Value of maximum query response time for IGMP(in seconds): 10 
       Querier for IGMP: 10.110.2.1 (this router) 
      Total 1 IGMP Group reported  
    						
    							 110 
    SSM mapping configuration example 
    Network requirements 
    The PIM-SM domain applies both the ASM model and SSM model for multicast delivery. Switch D’s 
    VLAN-interface 104 serves as the C-BSR and C-RP. The SSM group range is 232.1.1.0/24. 
    IGMPv3 runs on Switch D’s VLAN-interface 400. The receiver host runs IGMPv2, and does not support 
    IGMPv3. Therefore, the Receiver host cannot specify expected multicast sources in its membership 
    reports.  
    S o u r c e  1,  S o u r c e  2,  a n d  S o u r c e  3  s e n d  m u l t i c a s t  p a c k e t s  t o  m u l t i c a s t  g r o u p s  i n  t h e  S S M  g r o u p  r a n g e .  Yo u  
    can configure the IGMP SSM mapping feature on Switch D so that the receiver host will receive multicast 
    data from Source 1 and Source 3 only.  
    Figure 36  Network diagram 
     
    Device  Interface   IP address   Device  Interface   IP address 
    Source 1 —  133.133.1.1/24  Source 3 —  133.133.3.1/24 
    Source 2 —  133.133.2.1/24  Receiver —  133.133.4.1/24  
    Switch A Vlan-int100  133.133.1.2/24  Switch C Vlan-int300  133.133.3.2/24  
     Vlan-int101 192.168.1.1/24    Vlan-int103 192.168.3.1/24  
     Vlan-int104 192.168.4.2/24    Vlan-int102 192.168.2.2/24  
    Switch B Vlan-int200  133.133.2.2/24  Switch D Vlan-int400  133.133.4.2/24  
     Vlan-int101 192.168.1.2/24   Vlan-int103 192.168.3.2/24 
      Vlan-int102 192.168.2.1/24    Vlan-int104 192.168.4.1/24   
    Configuration procedure 
    1. Configure IP addresses and unicast routing: 
    # Configure the IP address and subnet mask of each interface as per  Figure 36. (Details not 
    shown.)
    
     
    # Configure OSPF for interoperability among the sw itches. Ensure the network-layer interoperation 
    on the PIM-SM domain and dynamic update of ro uting information among the switches through a 
    unicast routing protocol. (Details not shown.) 
    2.  Enable IP multicast routing, enable PIM-SM on  each interface, and enable IGMP and IGMP SSM 
    mapping on the host-side interface: 
    # Enable IP multicast routing on Switch D, enabl e PIM-SM on each interface, and enable IGMPv3 
    and IGMP SSM mapping on VLAN-interface 400. 
      
    						
    							 111 
     system-view 
    [SwitchD] multicast routing-enable 
    [SwitchD] interface vlan-interface 400 
    [SwitchD-Vlan-interface400] igmp enable 
    [SwitchD-Vlan-interface400] igmp version 3 
    [SwitchD-Vlan-interface400] igmp ssm-mapping enable 
    [SwitchD-Vlan-interface400] pim sm 
    [SwitchD-Vlan-interface400] quit 
    [SwitchD] interface vlan-interface 103 
    [SwitchD-Vlan-interface103] pim sm 
    [SwitchD-Vlan-interface103] quit 
    [SwitchD] interface vlan-interface 104 
    [SwitchD-Vlan-interface104] pim sm 
    [SwitchD-Vlan-interface104] quit 
    # Enable IP multicast routing on Switch A, and enable PIM-SM on each interface. 
     system-view 
    [SwitchA] multicast routing-enable 
    [SwitchA] interface vlan-interface 100 
    [SwitchA-Vlan-interface100] pim sm 
    [SwitchA-Vlan-interface100] quit 
    [SwitchA] interface vlan-interface 101 
    [SwitchA-Vlan-interface101] pim sm 
    [SwitchA-Vlan-interface101] quit 
    [SwitchA] interface vlan-interface 104 
    [SwitchA-Vlan-interface104] pim sm 
    [SwitchA-Vlan-interface104] quit 
    The configuration on Switch B and Switch C is similar to that on Switch A. 
    3. Configure a C-BSR and a C-RP: 
    # Configure C-BSR and C-RP interfaces on Switch D. 
    [SwitchD] pim 
    [SwitchD-pim] c-bsr vlan-interface 104 
    [SwitchD-pim] c-rp vlan-interface 104 
    [SwitchD-pim] quit 
    4. Configure the SSM group range: 
    # Configure the SSM group range 232.1.1.0/24 on Switch D. 
    [SwitchD] acl number 2000 
    [SwitchD-acl-basic-2000] rule permit source 232.1.1.0 0.0.0.255 
    [SwitchD-acl-basic-2000] quit 
    [SwitchD] pim 
    [SwitchD-pim] ssm-policy 2000 
    [SwitchD-pim] quit 
    The configuration on Switch A, Switch B and Switch C is similar to that on Switch D. 
    5. Configure IGMP SSM mappings: 
    # Configure IGMP SSM mappings on Switch D. 
    [SwitchD] igmp 
    [SwitchD-igmp] ssm-mapping 232.1.1.0 24 133.133.1.1  
    						
    							 112 
    [SwitchD-igmp] ssm-mapping 232.1.1.0 24 133.133.3.1 
    [SwitchD-igmp] quit 
    6. Verify the configuration: 
    # Display the IGMP SSM mapping information fo r multicast group 232.1.1.1 on Switch D. 
    [SwitchD] display igmp ssm-mapping 232.1.1.1 
    Vpn-Instance: public net 
    Group: 232.1.1.1 
    Source list:  
                 133.133.1.1 
                 133.133.3.1 
    # Display the IGMP group information created based on the IGMP SSM mappings on Switch D. 
    [SwitchD] display igmp ssm-mapping group 
    Total 1 IGMP SSM-mapping Group(s). 
    Interface group report information of VPN-Instance: public net 
     Vlan-interface400(133.133.4.2): 
      Total 1 IGMP SSM-mapping Group reported 
       Group Address       Last Reporter   Uptime      Expires 
       232.1.1.1           133.133.4.1     00:02:04    off 
    # Display PIM routing table information on Switch D. 
    [SwitchD] display pim routing-table 
    Vpn-instance: public net 
    Total 0 (*, G) entry; 2 (S, G) entry 
     
     (133.133.1.1, 232.1.1.1) 
         Protocol: pim-ssm, Flag: 
         UpTime: 00:13:25 
         Upstream interface: Vlan-interface104 
             Upstream neighbor: 192.168.4.2 
             RPF prime neighbor: 192.168.4.2 
         Downstream interface(s) information: 
           Total number of downstreams: 1 
             1: Vlan-interface400 
                     Protocol: igmp, UpTime: 00:13:25, Expires: - 
     
     (133.133.3.1, 232.1.1.1) 
         Protocol: pim-ssm, Flag: 
         UpTime: 00:13:25 
         Upstream interface: Vlan-interface103 
             Upstream neighbor: 192.168.3.1 
             RPF prime neighbor: 192.168.3.1 
         Downstream interface(s) information: 
           Total number of downstreams: 1 
             1: Vlan-interface400 
                     Protocol: igmp, UpTime: 00:13:25, Expires: -  
    						
    							 113 
    IGMP proxying configuration example 
    Network requirements 
    PIM-DM is required to run on the core network. Host A and Host C in the stub network receive VOD 
    information destined to multicast group 224.1.1.1.  
    Configure the IGMP proxying feature on Switch B so that Switch B can maintain group memberships and 
    forward multicast traffic without running PIM-DM.  
    Figure 37  Network diagram  
     
     
    Configuration procedure 
    1. Configure IP addresses: 
    # Configure the IP address and subnet mask of each interface as per  Figure 37. (Details not 
    shown.)
    
     
    2.  Enable IP multicast routing, PIM-DM, IGMP, and IGMP proxying: 
    # Enable IP multicast routing on Switch A, PIM-DM on VLAN-interface 101, and IGMP on 
    VLAN-interface 100.  
     system-view 
    [SwitchA] multicast routing-enable 
    [SwitchA] interface vlan-interface 101 
    [SwitchA-Vlan-interface101] pim dm 
    [SwitchA-Vlan-interface101] quit 
    [SwitchA] interface vlan-interface 100 
    [SwitchA-Vlan-interface100] igmp enable 
    [SwitchA-Vlan-interface100] pim dm 
    [SwitchA-Vlan-interface100] quit 
    # Enable IP multicast routing on Switch B, IGMP Proxying on VLAN-interface 100, and IGMP on 
    VLAN-interface 200.  
     system-view 
    [SwitchB] multicast routing-enable 
    [SwitchB] interface vlan-interface 100 
    [SwitchB-Vlan-interface100] igmp proxying enable 
    [SwitchB-Vlan-interface100] quit 
    [SwitchB] interface vlan-interface 200 
      
    						
    							 114 
    [SwitchB-Vlan-interface200] igmp enable 
    [SwitchB-Vlan-interface200] quit 
    3. Verify the configuration: 
    # Display IGMP information on VLAN-interface 100 of Switch B.  
    [SwitchB] display igmp interface vlan-interface 100 verbose 
     Vlan-interface100(192.168.1.2): 
       IGMP proxy is enabled 
       Current IGMP version is 2 
       Multicast routing on this interface: enabled 
       Require-router-alert: disabled 
       Version1-querier-present-timer-expiry: 00:00:20 
    # Display IGMP group information on Switch A.  
    [SwitchA] display igmp group 
    Total 1 IGMP Group(s). 
    Interface group report information of VPN-Instance: public net 
     Vlan-interface100(192.168.1.1): 
      Total 1 IGMP Groups reported 
       Group Address   Last Reporter   Uptime      Expires 
       224.1.1.1       192.168.1.2     00:02:04    00:01:15 
    The output shows that IGMP reports from the ho sts are forwarded to Switch A through the proxy 
    interface, VLAN-interface 100 on Switch B.  
    Troubleshooting IGMP  
    No membership information on  the receiver-side router 
    Symptom 
    When a host sends a report for joining multicast gr oup G, no membership information of the multicast 
    group G exists on the router closest to that host.  
    Analysis  
    •   The correctness of networking and interface conn ections and whether the protocol layer of the 
    interface is up directly affect the genera tion of group membership information.  
    •   Multicast routing must be enabled on the router, and IGMP must be enabled on the interface 
    connecting to the host.  
    •   If the IGMP version on the router interface is lower than that on the host, the router will not be able 
    to recognize the IGMP report from the host.  
    •   If the  igmp group-policy  command has been configured on th e interface, the interface cannot 
    receive report messages that fail to pass filtering.  
    Solution  
    1.  Use the display igmp interface  command to verify that the networking, interface connection, and 
    IP address configuration are correct.  If no information is output, the interface is in an abnormal 
    state. The reason is that you have configured the  shutdown command on the interface, the 
    interface is not properly connected, or th e IP address configuration is not correct.   
    						
    All HP manuals Comments (0)

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