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 1371 to Favourites
    image text
    Enable zoom 
    							 235 
Step Command Remarks 
1.  Enter system view. 
system-view N/A 
2.  Enter BGP view. 
bgp as-number   N/A 
3.  Enter IPv4 MBGP address 
family view.  ipv4-family multicast
 N/A 
4.  Configure the router as a 
route reflector and specify an 
MBGP peer or a peer group 
as its client.  peer { group-name 
| peer -address  } 
reflect-client  Not configured by default. 
5.
  Enable route reflection 
between clients.  reflect 
between -clients   Optional. 
Enabled by default. 
6.
  Configure the cluster ID of the 
route reflector.  reflector cluster-id
 cluster-id   Optional. 
By default, a route reflector uses its 
router ID as the cluster ID. 
 
Displaying and maintaining MBGP 
Displaying MBGP  
Task Command Remarks 
Display the IPv4 MBGP 
routing table. 
display ip multicast routing-table 
[ verbose ] [ | {  begin | 
exclude  | include  } regular-expression ]  Available in any 
view 
Display the IPv4 MBGP 
routing information matching 
the specified destination IP 
address. display ip multicast routing-table
 ip-address 
[ mask-length |  mask ] [ longer-match  ] [ verbose ] [ | 
{  begin |  exclude | include  } regular-expression  ] Available in any 
view 
Display MBGP peer group 
information. 
display
 bgp  multicast  group  [ group-name  ] [ | { begin | 
exclude  | include  } regular-expression ]  Available in any 
view
 
Display the advertised 
networks.  display bgp multicast network [ 
| { begin |  exclude | 
include  } regular-expression ]  Available in any 
view
 
Display AS path information.  display bgp multicast
 paths  [ as-regular-expression |  | 
{  begin |  exclude  | include  } regular-expression  ] Available in any 
view
 
Display MBGP peer 
information or peer group 
information.  display
 bgp  multicast  peer [  [ ip-address  ] verbose ] [ | 
{  begin |  exclude  | include  } regular-expression  ] Available in any 
view
 
Display the prefix entries in 
the ORF information from the 
specified BGP peer.  display bgp
 multicast peer ip-address  received ip-prefix 
[ |  { begin |  exclude | include } regular-expression  ] Available in any 
view 
Display MBGP routing 
information.  display bgp multicast
 routing-table  [ ip-address [ { mask  
|  mask-length } [ longer-prefixes  ] ] ] [ | { begin  | 
exclude  | include  } regular-expression ]  Available in any 
view
 
Display MBGP routing 
information matching the AS 
path ACL.  display bgp
 multicast  routing-table as-path-acl 
as-path-acl-number  [ | { begin |  exclude | include  } 
regular-expression  ]  Available in any 
view
    Add page 1372 to Favourites
    image text
    Enable zoom 
    							 236 
Task Command Remarks 
Display MBGP CIDR routing 
information. display bgp
 multicast  routing-table cidr  [ | { begin | 
exclude  | include  } regular-expression ]  Available in any 
view
 
Display MBGP routing 
information matching the 
specified BGP community.  display bgp
 multicast  routing-table 
community [ aa:nn& ] [  no-advertise | no-export 
|  no-export-subconfed  ] * [ whole-match  ] [ | { begin | 
exclude  | include  } regular-expression ]  Available in any 
view
 
Display MBGP routing 
information matching an 
MBGP community list.  display bgp multicast routing-table
 community-list 
{  {  basic-community-list-number |  comm-list-name } 
[ whole-match  ] | adv-community-list-number  } [ | 
{  begin |  exclude  | include  } regular-expression  ] Available in any 
view
 
Display MBGP dampened 
routing information.  display bgp multicast routing-table dampened
 [ | 
{  begin |  exclude | include  } regular-expression  ] Available in any 
view
 
Display MBGP dampening 
parameter information.  display bgp multicast routing-table dampening 
parameter
 [ | { begin |  exclude | include  } 
regular-expression  ]  Available in any 
view
 
Display MBGP routing 
information originating from 
different ASs.  display bgp multicast
  routing-table different-origin-as  
[ |  { begin |  exclude | include } regular-expression  ] Available in any 
view
 
Display IPv4 MBGP routing 
flap statistics.  display bgp multicast
 routing-table  flap-info 
[ regular-expression  as-regular-expression  | 
[  as-path-acl  as-path-acl-number  | ip-address  [ { mask | 
mask-length  } [  longer-match  ] ] ] [ | { begin  | exclude  | 
include  } regular-expression ] ]  Available in any 
view
 
Display IPv4 MBGP routing 
information sent to or 
received from an MBGP peer.  display bgp
 multicast  routing-table peer  ip-address 
{  advertised-routes  | received-routes } 
[  network-address  [ mask |  mask-length  ] | statistic ] [ | 
{  begin |  exclude | include  } regular-expression  ] Available in any 
view
 
Display IPv4 MBGP routing 
information matching an AS 
regular expression.  display bgp
 multicast   routing-table regular-expression  
as-regular-expression   Available in any 
view
 
Display IPv4 MBGP routing 
statistics.  display bgp multicast
  routing-table statistic  [ | { begin | 
exclude  | include  } regular-expression ]  Available in any 
view
 
 
Resetting MBGP connections  
Task Command Remarks 
Reset specified MBGP 
connections.  reset bgp
 ipv4  multicast  { all | as-number  | ip-address 
|  group  group-name  | external  | internal  }  Available in user 
view
 
 
Clearing MBGP information  
Task Command Remarks 
Clear dampened routing information 
and release suppressed routes.  reset bgp ipv4 multicast dampening
 [ ip-address 
[ mask  | mask-length  ] ]  Available in user 
view
    Add page 1373 to Favourites
    image text
    Enable zoom 
    							 237 
Task Command Remarks 
Clear MBGP route flap statistics. reset bgp ipv4 multicast flap-info
 [ regexp 
as-path-regexp  | as-path-acl  as-path-acl-number  
|  ip-address  [ mask  |  mask-length  ] ]  Available in user 
view
 
 
MBGP configuration example 
Network requirements 
As shown in the following figure: 
•  PIM-SM 1 is in AS 100, and PIM-SM 2 is in AS 200. OSPF is the IGP in the two ASs, and MBGP 
runs between the two ASs to exchange multicast route information.  
•   The multicast source belongs to PIM-SM 1, and the receiver belongs to PIM-SM 2. 
•   Configure the respective Loopback 0 of Switch  A and Switch B as the C-BSR and C-RP of the 
respective PIM-SM domains. 
•   Set up an MSDP peer relationship between Switch A and Switch B through MBGP.  
Figure 64  Network diagram 
 
Device Interface  IP address Device Interface IP address 
Source N/A  10.110.1.100/24 Switch C Vlan-int200 10.110.2.1/24 
Switch A  Vlan-int100  10.110.1.1/24  Vlan-int102 192.168.2.2/24 
 Vlan-int101 192.168.1.1/24  Vlan-int104 192.168.4.1/24 
  Loop0 1.1.1.1/32   Loop0 3.3.3.3/32 
Switch B  Vlan-int101  192.168.1.2/24 Switch D Vlan-int103 192.168.3.2/24 
 Vlan-int102 192.168.2.1/24  Vlan-int104 192.168.4.2/24 
 Vlan-int103 192.168.3.1/24  Loop0 4.4.4.4/32 
 Loop0 2.2.2.2/32     
Configuration procedure 
1. Configure IP addresses for interfaces as shown in  Figure 64. (Details not shown.) 
2. Configure OSPF. (Details not shown.) 
MBGP peers
AS 100
AS 200
Source Receiver
Switch A Switch B
Switch C
Switch D
Vlan-int101
Vlan-int101
Vlan-int104
Vlan-int104
Vlan-int100
PIM-SM 1
PIM-SM 2
Loop0Loop0
Loop0Loop0
    Add page 1374 to Favourites
    image text
    Enable zoom 
    							 238 
3.
 
Enable IP multicast routing, PIM-SM and IG MP, and configure a PIM-SM domain border: 
# 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 
The configuration on Switch B and Switch D is similar to the configuration on Switch A. 
# Enable IP multicast routing on Switch C, enable  PIM-SM on each interface, and enable IGMP on 
the host-side interface VLAN-interface 200. 
 system-view 
[SwitchC] multicast routing-enable 
[SwitchC] interface vlan-interface 102 
[SwitchC-Vlan-interface102] pim sm 
[SwitchC-Vlan-interface102] quit 
[SwitchC] interface vlan-interface 104 
[SwitchC-Vlan-interface104] pim sm 
[SwitchC-Vlan-interface104] quit 
[SwitchC] interface vlan-interface 200 
[SwitchC-Vlan-interface200] pim sm 
[SwitchC-Vlan-interface200] igmp enable 
[SwitchC-Vlan-interface200] quit 
# Configure a PIM domain border on Switch A. 
[SwitchA] interface vlan-interface 101 
[SwitchA-Vlan-interface101] pim bsr-boundary 
[SwitchA-Vlan-interface101] quit 
# Configure a PIM domain border on Switch B. 
[SwitchB] interface vlan-interface 101 
[SwitchB-Vlan-interface101] pim bsr-boundary 
[SwitchB-Vlan-interface101] quit 
4.  Configure Loopback 0 and the posi tion of C-BSR, and C-RP:  
# Configure Loopback 0 and configure it as the C-BSR and C-RP on Switch A. 
[SwitchA] interface loopback 0 
[SwitchA-LoopBack0] ip address 1.1.1.1 32 
[SwitchA-LoopBack0] pim sm 
[SwitchA-LoopBack0] quit 
[SwitchA] pim 
[SwitchA-pim] c-bsr loopback 0 
[SwitchA-pim] c-rp loopback 0 
[SwitchA-pim] quit 
# Configure Loopback 0 and configure it as the C-BSR and C-RP on Switch B. 
[SwitchB] interface loopback 0 
[SwitchB-LoopBack0] ip address 2.2.2.2 32 
[SwitchB-LoopBack0] pim sm
    Add page 1375 to Favourites
    image text
    Enable zoom 
    							 239 
[SwitchB-LoopBack0] quit 
[SwitchB] pim 
[SwitchB-pim] c-bsr loopback 0 
[SwitchB-pim] c-rp loopback 0 
[SwitchB-pim] quit 
5. Configure BGP, specify the MBGP peer and enable direct route redistribution: 
# On Switch A, configure the MBGP peer  and enable direct route redistribution. 
[SwitchA] bgp 100 
[SwitchA-bgp] router-id 1.1.1.1 
[SwitchA-bgp] peer 192.168.1.2 as-number 200 
[SwitchA-bgp] import-route direct 
[SwitchA-bgp] ipv4-family multicast 
[SwitchA-bgp-af-mul] peer 192.168.1.2 enable 
[SwitchA-bgp-af-mul] import-route direct 
[SwitchA-bgp-af-mul] quit 
[SwitchA-bgp] quit 
# On Switch B, configure the MBGP peer and enable route redistribution from OSPF. 
[SwitchB] bgp 200 
[SwitchB-bgp] router-id 2.2.2.2 
[SwitchB-bgp] peer 192.168.1.1 as-number 100 
[SwitchB-bgp] import-route ospf 1 
[SwitchB-bgp] ipv4-family multicast 
[SwitchB-bgp-af-mul] peer 192.168.1.1 enable 
[SwitchB-bgp-af-mul] import-route ospf 1 
[SwitchB-bgp-af-mul] quit 
[SwitchB-bgp] quit 
6. Configure MSDP peer: 
# Specify the MSDP peer on Switch A. 
[SwitchA] msdp 
[SwitchA-msdp] peer 192.168.1.2 connect-interface vlan-interface 101 
[SwitchA-msdp] quit 
# Specify the MSDP peer on Switch B. 
[SwitchB] msdp 
[SwitchB-msdp] peer 192.168.1.1 connect-interface vlan-interface 101 
[SwitchB-msdp] quit 
7. Verify the configuration: 
You can use the  display bgp multicast peer  command to display MBGP peers on a switch. For 
example, display MBGP peers on Switch B. 
[SwitchB] display bgp multicast peer 
 
 BGP local router ID : 2.2.2.2 
 Local AS number : 200 
 Total number of peers : 3                 Peers in established state : \
3 
 
  Peer            AS  MsgRcvd  MsgSent  OutQ PrefRcv Up/Down  State 
 
  192.168.1.1    100       56       56     0       0 00:40:54 Establishe\
d
    Add page 1376 to Favourites
    image text
    Enable zoom 
    							 240 
You can use the display msdp brief  command to display MSDP peers on a switch. For example, 
display brief information about MSDP peers on Switch B. 
[SwitchB] display msdp brief 
MSDP Peer Brief Information of VPN-Instance: public net 
  Configured   Up           Listen       Connect      Shutdown     Down \
  1            1            0            0            0            0 
  Peers Address    State    Up/Down time    AS     SA Count   Reset Cou\
nt 
  192.168.1.1       Up       00:07:17        100    1          0
    Add page 1377 to Favourites
    image text
    Enable zoom 
    							 241 
Configuring MLD snooping 
Overview 
Multicast Listener Discovery (MLD) snooping is an IPv6 multicast constraining mechanism that runs on 
Layer 2 devices to manage and control IPv6 multicast groups. 
By analyzing received MLD messages, a Layer 2 devi ce that runs MLD snooping establishes mappings 
between ports and multicast MAC addresses and forwards IPv6 multicast data based on these 
mappings.  
As shown in  Figure 65, w
 hen MLD snooping does not run on the Layer 2 switch, IPv6 multicast packets 
are flooded to all devices at Layer 2. When MLD snooping runs on the Layer 2 switch, multicast packets 
for known IPv6 multicast groups are multicast to the receivers, rather than flooded to all hosts at Layer 2. 
Figure 65  Before and after MLD snooping is  enabled on the Layer 2 device 
 
 
MLD snooping enables the Layer 2 switch to forward IPv6 multicast data to only the receivers that require 
the data at Layer 2. It has the following advantages: 
•   Reducing Layer 2 broadcast packets, thus saving network bandwidth  
•   Enhancing the security of multicast traffic 
•   Facilitating the implementation of per-host accounting 
Basic concepts in MLD snooping 
MLD snooping related ports 
As shown in Figure 66 , Router A connects to the multicast source, MLD snooping runs on Switch A and 
Switch B, and Host A and Host C are receiver hosts (namely, members of an IPv6 multicast group).
    Add page 1378 to Favourites
    image text
    Enable zoom 
    							 242 
Figure 66 MLD snooping related ports  
 
 
Ports involved in MLD snooping, as shown in Figure 66, ar e described as follows:  
•   Router port —A router port is a port on the Ethernet switch that leads switch toward the Layer-3 
multicast device (designated router or MLD querier). In the figure, GigabitEthernet 1/0/1 of Switch 
A and GigabitEthernet 1/0/1 of Switch B are router  ports. The switch registers all its local router 
ports in its router port list.  
In this document, a router port is port on a swit ch that leads the switch toward a Layer 3 multicast 
device. It is not a port on an ordinary router.  
•   Member port —A member port (also known as IPv6 multicast group member port) is a port on the 
Ethernet switch that leads toward multicast group members. In the figure, GigabitEthernet 1/0/2 
and GigabitEthernet 1/0/3 of Switch A and GigabitEthernet 1/0/2 of Switch B are member ports. 
The switch registers all the member ports on the lo cal device in its MLD snooping forwarding table.   
Unless otherwise specified, router ports and member  ports in this document include both static and 
dynamic router ports and member ports. 
 
  NOTE: 
An MLD snooping-enabled switch deems that the all it s ports that receive MLD general queries with the 
source address other than 0::0 or that receive IPv6 PIM hello messages  are dynamic router ports. For more
information about IPv6 PIM hello messages, see  Configuring IPv6 PIM (available only on the HP 5500
EI). 
 
Aging timers for dynamic ports in MLD snooping and related messages and actions  
 
Timer Description    Message before expiry Action after expiry 
Dynamic router 
port aging timer  For each dynamic router port, 
the switch sets an aging timer. 
When the timer expires, the 
dynamic router port ages out.
 MLD general query of 
which the source address 
is not 0::0 or IPv6 PIM 
hello. 
  The switch removes this 
port from its router port 
list.
    Add page 1379 to Favourites
    image text
    Enable zoom 
    							 243 
Timer Description   Message before expiry Action after expiry 
Dynamic member 
port aging timer 
 When a port dynamically joins 
a multicast group, the switch 
starts an aging timer for the 
port. When the timer expires, 
the dynamic member port ages 
out. 
MLD report message. 
The switch removes this 
port from the MLD 
snooping forwarding 
table.  
 
 
NOTE: 
In MLD snooping, only dynamic ports ag e out. Static ports never age out.  
 
How MLD snooping works 
In this section, the involved ports are dynamic ports. For information about how to configure and remove 
static ports, see Configuring static ports .
  
A switch that runs MLD snooping pe rforms different actions when it receives different MLD messages, as 
follows:  
When receiving a general query 
The MLD querier periodically sends MLD general querie s to all hosts and routers (FF02::1) on the local 
subnet to determine whether any active IPv6 multicast group members exist on the subnet.  
After receiving an MLD general query, the switch forwards it to all ports in the VLAN, except the port that 
received the query. The switch also performs the following judgment:  
•   If the port that received the query is a dynamic router port in the router port list of the switch, the 
switch restarts the aging timer for the port.  
•   If the port is not in the router port list, the switch  adds it into the router port list as a dynamic router 
port and starts an aging timer for the port.  
When receiving a membership report 
A host sends an MLD report to the MLD querier in the following circumstances:  
•   If the host has been a member of an IPv6 multicast group, after receiving an MLD query, the host 
responds to the query with an MLD report. 
•   When the host wants to join an IPv6 multicast group, it sends an MLD report to the MLD querier, 
specifying the IPv6 multicast group to join.  
After receiving an MLD report, the switch forwards it  through all the router ports in the VLAN, resolves the 
address of the reported IPv6 multicast group, and performs the following judgment:  
•   If no forwarding entry matches the group address,  the switch creates a forwarding entry for the 
group, adds the port that received the MLD report as a dynamic member port to the forwarding 
entry for the group, and starts an aging timer for the port. 
•   If a forwarding entry matches the group address, but  the port that received the MLD report is not in 
the forwarding entry for the group, the switch  adds the port as a dynamic member port to the 
forwarding entry, and starts an aging timer for the port. 
•   If a forwarding entry matches the group address and  the port that received the MLD report is in the 
forwarding entry for the group, the switch restarts the aging timer for the port. 
A switch does not forward an MLD report through a non-router port. The reason is that if the switch 
forwards a report message through a member port, all  the attached hosts that monitor the reported IPv6
    Add page 1380 to Favourites
    image text
    Enable zoom 
    							 244 
multicast address suppress their own reports after receiving this report according to the MLD report 
suppression mechanism. This prevents the switch from confirming whether the reported multicast group 
still has active members attached to that port.  
For more information about the MLD report suppression mechanism of hosts, see  Configuring MLD 
(

available only on the HP 5500 EI) . 
When receiving a done message 
When a host leaves an IPv6 multicast group, the host sends an MLD done message to the multicast 
routers. When the switch receives the MLD done me ssage on a dynamic member port, the switch first 
checks whether a forwarding entry matches the IPv6 multicast group address in the message, and, if a 
match is found, whether the forwarding entry contains the dynamic member port.  
•   If no forwarding entry matches the IPv6 multicast group address, or if the forwarding entry does not 
contain the port, the switch directly discards the MLD done message. 
•   If a forwarding entry matches the IPv6 multicast group address and contains the port, the switch 
forwards the done message to a ll router ports in the native VLAN. Because the switch does not 
know whether any other hosts attached to the port are still listening to that IPv6 multicast group 
address, the switch does not immediately remove the  port from the forwarding entry for that group. 
Instead, it restarts the aging timer for the port. 
After receiving the MLD done message, the MLD querie r resolves the IPv6 multicast group address in the 
message and sends an MLD multicast-address-specific query to that IPv6 multicast group through the port 
that received the MLD done message. After receiving  the MLD multicast-address-specific query, the switch 
forwards it through all its router ports in the VLAN  and all member ports of the IPv6 multicast group. The 
switch also performs the following judgment for  the port that received the MLD done message:  
•   If the port (assuming that it is a dynamic member  port) receives an MLD report in response to the 
MLD multicast-address-specific query before its aging timer expires, it indicates that some host 
attached to the port is receiving or expecting to receive IPv6 multicast data for that IPv6 multicast 
group. The switch restarts the aging timer for the port. 
•   If the port receives no MLD report in response to the MLD multicast-address-specific query before its 
aging timer expires, it indicates that no hosts atta ched to the port are still monitoring that IPv6 
multicast group address. The switch removes the port from the forwarding entry for the IPv6 
multicast group when the aging timer expires. 
MLD snooping proxying 
Yo u  c a n  c o n fig u re  t h e  M L D  s n o o pi n g  p rox yi n g  fu n c t io n  o n  a n  e d g e  d evic e  t o  re d u c e  t h e  nu m b e r  o f  M L D  
reports and done messages sent to its upstream  device. The device configured with MLD snooping 
proxying is called an MLD snooping proxy. It is a host from the perspective of its upstream device. 
 
  NOTE: 
Even though an MLD snooping proxy is a host from  the perspective of its upstream device, the MLD 
membership report suppression mechanism for hosts do es not take effect on it. For more information 
about the MLD report suppression  mechanism for hosts, see Configuring MLD (available only on the HP
5500 EI).
    All HP manuals Comments (0)

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