HP 5500 Ei 5500 Si Switch Series Configuration Guide
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+.
165 Task Command Remarks Reset PIM control message counters. reset pim [ all-instance | vpn-instance vpn-instance-name ] control-message counters [ interface interface-type interface-number ] Available in user view PIM configuration examples PIM-DM configuration example Network requirements As shown in Figure 51, 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 dense mode. Host A and Host C are multicast receivers in two stub networks. IGMPv2 runs between Switch A and N1 and between Switch B/Switch C and N2. Figure 51 Network diagram Device Interface IP address Device Interface IP address Switch A Vlan-int100 10.110.1.1/24 Switch D Vlan-int300 10.110.5.1/24 Vlan-int103 192.168.1.1/24 Vlan-int103 192.168.1.2/24 Switch B Vlan-int200 10.110.2.1/24 Vlan-int101 192.168.2.2/24 Vlan-int101 192.168.2.1/24 Vlan-int102 192.168.3.2/24 Switch C Vlan-int200 10.110.2.2/24 Vlan-int102 192.168.3.1/24 Ethernet Ethernet Ethernet N1 N2 Vl an -int102 Vl an- int102 Vlan-i nt103 Vlan-int10 3
166 Configuration procedure 1. Configure IP addresses and unicast routing: Configure the IP address and subnet mask for each interface as per Figure 51. (Details not sh own.) Configure OSPF on the switches in the PIM-DM domain to ensure network-layer reachability among them. (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, which connects Switch A to the stub network. system-view [SwitchA] multicast routing-enable [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] pim dm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 103 [SwitchA-Vlan-interface103] pim dm [SwitchA-Vlan-interface103] quit The configuration on Switch B and Switch C is similar to that on Switch A. # Enable IP multicast routing on Switch D, and enable PIM-DM on each interface. system-view [SwitchD] multicast routing-enable [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] pim dm [SwitchD-Vlan-interface300] quit [SwitchD] interface vlan-interface 103 [SwitchD-Vlan-interface103] pim dm [SwitchD-Vlan-interface103] quit [SwitchD] interface vlan-interface 101 [SwitchD-Vlan-interface101] pim dm [SwitchD-Vlan-interface101] quit [SwitchD] interface vlan-interface 102 [SwitchD-Vlan-interface102] pim dm [SwitchD-Vlan-interface102] quit 3. Verify the configuration: # Display PIM configuration information on Switch D. [SwitchD] display pim interface VPN-Instance: public net Interface NbrCnt HelloInt DR-Pri DR-Address Vlan300 0 30 1 10.110.5.1 (local\ ) Vlan103 1 30 1 192.168.1.2 (local\ ) Vlan101 1 30 1 192.168.2.2 (local\ ) Vlan102 1 30 1 192.168.3.2 (local\ ) # Display PIM neighboring relationships on Switch D. [SwitchD] display pim neighbor VPN-Instance: public net Total Number of Neighbors = 3
167 Neighbor Interface Uptime Expires Dr-Priority 192.168.1.1 Vlan103 00:02:22 00:01:27 1 192.168.2.1 Vlan101 00:00:22 00:01:29 3 192.168.3.1 Vlan102 00:00:23 00:01:31 5 Assume that Host A needs to receive the information addressed to multicast group G (225.1.1.1). After multicast source S (10.110.5.100/24) sends mu lticast packets to the multicast group G, an SPT is established through traffic flooding. Switches on the SPT path (Switch A and Switch D) have their (S, G) entries. Host A sends an IGMP report to Switch A to join the multicast group G, and a (*, G) entry is generated on Switch A. You can use the display pim routing-table command to view the PIM routing table information on each switch. For example: # Display PIM routing table information on Switch A. [SwitchA] display pim routing-table VPN-Instance: public net Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.1) Protocol: pim-dm, Flag: WC UpTime: 00:04:25 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: igmp, UpTime: 00:04:25, Expires: never (10.110.5.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: Vlan-interface103 Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: pim-dm, UpTime: 00:04:25, Expires: never # Display PIM routing table information on Switch D. [SwitchD] display pim routing-table VPN-Instance: public net Total 0 (*, G) entry; 1 (S, G) entry (10.110.5.100, 225.1.1.1) Protocol: pim-dm, Flag: LOC ACT UpTime: 00:03:27 Upstream interface: Vlan-interface300 Upstream neighbor: NULL RPF prime neighbor: NULL
168 Downstream interface(s) information: Total number of downstreams: 2 1: Vlan-interface103 Protocol: pim-dm, UpTime: 00:03:27, Expires: never 2: Vlan-interface102 Protocol: pim-dm, UpTime: 00:03:27, Expires: never PIM-SM non-scoped zone configuration example Network requirements As shown in Figure 52, 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-SM domain contains only one BSR. Host A and Host C are multicast receivers in two stub networks. VLAN-interface 105 on Switch D and VLAN-interface 102 on Switch E act as C-BSRs and C-RPs. The C-BSR on Switch E has a higher priority. The multicast group range served by the C-RP is 225.1.1.0/24. Modify the hash mask length to map a certain number of consecutive group addresses within the range to the two C-RPs. IGMPv2 runs between Switch A and N1 and between Switch B/Switch C and N2. Figure 52 Network diagram Device Interface IP address Device Interface IP address Switch A Vlan-int100 10.110.1.1/24 Switch D Vlan-int300 10.110.5.1/24 Vlan-int101 192.168.1.1/24 Vlan-int101 192.168.1.2/24 Vlan-int102 192.168.9.1/24 Vlan-int105 192.168.4.2/24 Switch B Vlan-int200 10.110.2.1/24 Switch E Vlan-int104 192.168.3.2/24 Ethernet Ethernet Ethernet N1 N2 Vlan- i n t10 1 Vlan- int101
169 Vlan-int103 192.168.2.1/24 Vlan-int103 192.168.2.2/24 Switch C Vlan-int200 10.110.2.2/24 Vlan-int102 192.168.9.2/24 Vlan-int104 192.168.3.1/24 Vlan-int105 192.168.4.1/24 Configuration procedure 1. Configure IP addresses and unicast routing: Configure the IP address and subnet mask for each interface as per Figure 52. (Details not sh own.) Configure OSPF on the switches in the PIM-SM domain to ensure network-layer reachability among them. (Details not shown.) 2. Enable IP multicast routing, and enable PIM-SM and IGMP: # Enable IP multicast routing on Switch A, enable PIM-SM on each interface, and enable IGMP on VLAN-interface 100, which connects Switch A to the stub network. system-view [SwitchA] multicast routing-enable [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [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 102 [SwitchA-Vlan-interface102] pim 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 IGMP on the corresponding interfaces on these two switches. 3. Configure a C-BSR and a C-RP: # On Switch D, configure the service scope of RP, specify a C-BSR and a C-RP, and set the hash mask length to 32 and the priority of the C-BSR to 10. system-view [SwitchD] acl number 2005 [SwitchD-acl-basic-2005] rule permit source 225.1.1.0 0.0.0.255 [SwitchD-acl-basic-2005] quit [SwitchD] pim [SwitchD-pim] c-bsr vlan-interface 105 32 10 [SwitchD-pim] c-rp vlan-interface 105 group-policy 2005 [SwitchD-pim] quit # On Switch E, configure the service scope of RP advertisements, specify a C-BSR and a C-RP, and set the hash mask length to 32 and the priority of the C-BSR to 20. system-view [SwitchE] acl number 2005 [SwitchE-acl-basic-2005] rule permit source 225.1.1.0 0.0.0.255 [SwitchE-acl-basic-2005] quit [SwitchE] pim [SwitchE-pim] c-bsr vlan-interface 102 32 20
170 [SwitchE-pim] c-rp vlan-interface 102 group-policy 2005 [SwitchE-pim] quit 4. Verify the configuration: # Display PIM configuration information on Switch A. [SwitchA] display pim interface VPN-Instance: public net Interface NbrCnt HelloInt DR-Pri DR-Address Vlan100 0 30 1 10.110.1.1 (local\ ) Vlan101 1 30 1 192.168.1.2 Vlan102 1 30 1 192.168.9.2 # Display BSR information and the locally configur ed C-RP information in effect on Switch A. [SwitchA] display pim bsr-info VPN-Instance: public net Elected BSR Address: 192.168.9.2 Priority: 20 Hash mask length: 32 State: Accept Preferred Scope: Not scoped Uptime: 00:40:40 Expires: 00:01:42 # Display BSR information and the locally configured C-RP information in effect on Switch D. [SwitchD] display pim bsr-info VPN-Instance: public net Elected BSR Address: 192.168.9.2 Priority: 20 Hash mask length: 32 State: Accept Preferred Scope: Not scoped Uptime: 00:05:26 Expires: 00:01:45 Candidate BSR Address: 192.168.4.2 Priority: 10 Hash mask length: 32 State: Candidate Scope: Not scoped Candidate RP: 192.168.4.2(Vlan-interface105) Priority: 192 HoldTime: 150 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:34 # Display BSR information and the locally configured C-RP information in effect on Switch E. [SwitchE] display pim bsr-info VPN-Instance: public net Elected BSR Address: 192.168.9.2 Priority: 20 Hash mask length: 32
171 State: Elected Scope: Not scoped Uptime: 00:01:18 Next BSR message scheduled at: 00:01:52 Candidate BSR Address: 192.168.9.2 Priority: 20 Hash mask length: 32 State: Elected Scope: Not scoped Candidate RP: 192.168.9.2(Vlan-interface102) Priority: 192 HoldTime: 150 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:48 # Display RP information on Switch A. [SwitchA] display pim rp-info VPN-Instance: public net PIM-SM BSR RP information: Group/MaskLen: 225.1.1.0/24 RP: 192.168.4.2 Priority: 192 HoldTime: 150 Uptime: 00:51:45 Expires: 00:02:22 RP: 192.168.9.2 Priority: 192 HoldTime: 150 Uptime: 00:51:45 Expires: 00:02:22 Assume that Host A needs to receive information addressed to the multicast group G (225.1.1.0). The RP corresponding to the multicast group G is Swit ch E as a result of hash calculation, so an RPT will be built between Switch A and Switch E. When the multicast source S (10.110.5.100/24) registers with the RP, an SPT will be built between Switch D and Switch E. After receiving multicast data, Switch A immediately switches from the RPT to the SPT. Switches on the RPT path (Switch A and Switch E) have a (*, G) entry, and switches on the SPT path (Switch A and Switch D) have an (S, G) entry. You can use the display pim routing-table command to view the PIM routing table information on the switches. For example: # Display PIM routing table information on Switch A. [SwitchA] display pim routing-table VPN-Instance: public net Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.0) RP: 192.168.9.2 Protocol: pim-sm, Flag: WC UpTime: 00:13:46
172 Upstream interface: Vlan-interface102 Upstream neighbor: 192.168.9.2 RPF prime neighbor: 192.168.9.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: igmp, UpTime: 00:13:46, Expires: 00:03:06 (10.110.5.100, 225.1.1.0) RP: 192.168.9.2 Protocol: pim-sm, Flag: SPT ACT UpTime: 00:00:42 Upstream interface: Vlan-interface101 Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: pim-sm, UpTime: 00:00:42, Expires: 00:03:06 The information on Switch B and Switch C is similar to that on Switch A. # Display PIM routing table information on Switch D. [SwitchD] display pim routing-table VPN-Instance: public net Total 0 (*, G) entry; 1 (S, G) entry (10.110.5.100, 225.1.1.0) RP: 192.168.9.2 Protocol: pim-sm, Flag: SPT LOC ACT UpTime: 00:00:42 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-sm, UpTime: 00:00:42, Expires: 00:02:26 # Display PIM routing table information on Switch E. [SwitchE] display pim routing-table VPN-Instance: public net Total 1 (*, G) entry; 0 (S, G) entry (*, 225.1.1.0) RP: 192.168.9.2 (local) Protocol: pim-sm, Flag: WC UpTime: 00:13:16 Upstream interface: Register Upstream neighbor: 192.168.4.2 RPF prime neighbor: 192.168.4.2
173 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface102 Protocol: pim-sm, UpTime: 00:13:16, Expires: 00:03:22 PIM-SM admin-scope zone configuration example Network requirements As shown in Figure 53, receivers receive VOD information through multicast. The entire PIM-SM domain is divided into admin-scope zone 1, admin-scope zone 2, and the global zone. Switch B, Switch C, and Switch D are ZBRs of these three domains respectively. Source 1 and Source 2 send different multicast inform a t i o n t o m u l t i c a s t g r o u p 2 3 9 .1.1.1. H o s t A r e c e i v e s the multicast information only from Source 1, and Host B receives the multicast information only from Source 2. Source 3 sends multicast information to multicast group 224.1.1.1. Host C is a multicast receiver for this multicast group. VLAN-interface 101 of Switch B acts as a C-BSR an d C-RP of admin-scope zone 1, which serves the multicast group range 239.0.0.0/8. VLAN-interface 104 of Switch D acts as a C-BSR and C-RP of admin-scope zone 2, which also serves the multicast group range 239.0.0.0/8. VLAN-interface 109 of Switch F acts as C-BSRs and C-RPs of the global scope zone, which serves all the multicast groups other than those in the 239.0.0.0/8 range. IGMPv2 runs between Switch A, Switch E, Switch I, and their respective receivers.
174 Figure 53 Network diagram Device Interface IP address Device Interface IP address Switch A Vlan-int100 192.168.1.1/24 Switch D Vlan-int104 10.110.4.2/24 Vlan-int101 10.110.1.1/24 Vlan-int108 10.110.7.1/24 Switch B Vlan-int200 192.168.2.1/24 Vlan-int107 10.110.8.1/24 Vlan-int101 10.110.1.2/24 Switch E Vlan-int400 192.168.4.1/24 Vlan-int103 10.110.2.1/24 Vlan-int105 10.110.5.2/24 Vlan-int102 10.110.3.1/24 Vlan-int108 10.110.7.2/24 Switch C Vlan-int300 192.168.3.1/24 Switch F Vlan-int109 10.110.9.1/24 Vlan-int104 10.110.4.1/24 Vlan-int107 10.110.8.2/24 Vlan-int105 10.110.5.1/24 Vlan-int102 10.110.3.2/24 Vlan-int103 10.110.2.2/24 Switch G Vlan-int500 192.168.5.1/24 Vlan-int106 10.110.6.1/24 Vlan-int109 10.110.9.2/24 Switch H Vlan-int110 10.110.10.1/24 Source 1 — 192.168.2.10/24 Vlan-int106 10.110.6.2/24 Source 2 — 192.168.3.10/24 Switch I Vlan-int600 192.168.6.1/24 Source 3 — 192.168.5.10/24 Vlan-int110 10.110.10.2/24 Configuration procedure 1. Configure IP addresses and unicast routing: Configure the IP address and subnet mask for each interface as per Figure 53. (Details not sh own.) Configure OSPF on the switches in the PIM-SM domain to ensure network-layer reachability among them. (Details not shown.) 2. Enable IP multicast routing and administrat ive scoping, and enable PIM-SM and IGMP: Vlan -i n t105 Vl a n-int10 3 Vl an- in t300V l an-i n t105 Vla n -int600 V lan-int103