Cisco PIM Sparse Mode with Static RP Configuration
In PIM Sparse Mode (PIM-SM), multicast traffic is only forwarded to group members which explicitly request it via join requests.Multicast flooding is much less than PIM Dense Mode(PIM-DM).PIM Sparse Mode is the recommended version.
We will provide an example for PIM Sparse Mode with static RP(rendezvous point):
Here is the topology for this example:
R1 is the multicast client for group 224.1.1.1
Configuration of R2
ip multicast-routing
interface Loopback0
ip address 2.2.2.2 255.255.255.255
ip ospf 1 area 0
!
interface FastEthernet0/0
ip address 192.168.23.2 255.255.255.0
ip pim sparse-mode
no ip mroute-cache
!
interface FastEthernet0/1
ip address 192.168.12.2 255.255.255.0
ip pim dense-mode
no ip mroute-cache
!
interface FastEthernet1/0
ip address 192.168.24.2 255.255.255.0
ip pim sparse-mode
no ip mroute-cache
!
router ospf 1
log-adjacency-changes
network 192.168.0.0 0.0.255.255 area 0
!
ip pim rp-address 3.3.3.3
Configuration of R3:
ip multicast-routing
interface Loopback0
ip address 3.3.3.3 255.255.255.255
ip pim sparse-mode
ip ospf 1 area 0
!
interface FastEthernet0/0
ip address 192.168.23.3 255.255.255.0
ip pim sparse-mode
!
interface FastEthernet0/1
ip address 192.168.34.3 255.255.255.0
ip pim sparse-mode
!
router ospf 1
log-adjacency-changes
network 192.168.0.0 0.0.255.255 area 0
!
ip pim rp-address 3.3.3.3
R4 is the source and its configuration is similar to R2
Lets start the traffic from R4:
R4#ping
Protocol [ip]:
Target IP address: 224.1.1.1
Repeat count [1]: 10000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: yes
Interface [All]: FastEthernet1/0
Time to live [255]:
Source address: 4.4.4.4
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 10000, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:
Packet sent with a source address of 4.4.4.4
Reply to request 0 from 192.168.12.1, 172 ms
Reply to request 1 from 192.168.12.1, 144 ms
Reply to request 2 from 192.168.12.1, 80 ms
Reply to request 3 from 192.168.12.1, 88 ms
Ping results are OK.Lets show some verifying commands:
R2#show ip pim neighbor
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
S - State Refresh Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
192.168.23.3 FastEthernet0/0 01:16:17/00:01:36 v2 1 / DR S
192.168.24.4 FastEthernet1/0 01:16:12/00:01:19 v2 1 / DR S
R2# show ip pim rp mapping
PIM Group-to-RP Mappings
Group(s): 224.0.0.0/4, Static
RP: 3.3.3.3 (?)
R2#show ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.1.1.1), 00:47:12/stopped, RP 3.3.3.3, flags: SJC
Incoming interface: FastEthernet0/0, RPF nbr 192.168.23.3
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:47:12/00:00:00
(4.4.4.4, 224.1.1.1), 00:16:47/00:01:51, flags: JT
Incoming interface: FastEthernet1/0, RPF nbr 192.168.24.4
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:16:47/00:00:00
(*, 224.0.1.40), 00:47:14/00:02:10, RP 3.3.3.3, flags: SJPCL
Incoming interface: FastEthernet0/0, RPF nbr 192.168.23.3
Outgoing interface list: Null
In PIM Sparse Mode (PIM-SM), multicast traffic is only forwarded to group members which explicitly request it via join requests.Multicast flooding is much less than PIM Dense Mode(PIM-DM).PIM Sparse Mode is the recommended version.
We will provide an example for PIM Sparse Mode with static RP(rendezvous point):
Here is the topology for this example:
R1 is the multicast client for group 224.1.1.1
Configuration of R2
ip multicast-routing
interface Loopback0
ip address 2.2.2.2 255.255.255.255
ip ospf 1 area 0
!
interface FastEthernet0/0
ip address 192.168.23.2 255.255.255.0
ip pim sparse-mode
no ip mroute-cache
!
interface FastEthernet0/1
ip address 192.168.12.2 255.255.255.0
ip pim dense-mode
no ip mroute-cache
!
interface FastEthernet1/0
ip address 192.168.24.2 255.255.255.0
ip pim sparse-mode
no ip mroute-cache
!
router ospf 1
log-adjacency-changes
network 192.168.0.0 0.0.255.255 area 0
!
ip pim rp-address 3.3.3.3
Configuration of R3:
ip multicast-routing
interface Loopback0
ip address 3.3.3.3 255.255.255.255
ip pim sparse-mode
ip ospf 1 area 0
!
interface FastEthernet0/0
ip address 192.168.23.3 255.255.255.0
ip pim sparse-mode
!
interface FastEthernet0/1
ip address 192.168.34.3 255.255.255.0
ip pim sparse-mode
!
router ospf 1
log-adjacency-changes
network 192.168.0.0 0.0.255.255 area 0
!
ip pim rp-address 3.3.3.3
R4 is the source and its configuration is similar to R2
Lets start the traffic from R4:
R4#ping
Protocol [ip]:
Target IP address: 224.1.1.1
Repeat count [1]: 10000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: yes
Interface [All]: FastEthernet1/0
Time to live [255]:
Source address: 4.4.4.4
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 10000, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:
Packet sent with a source address of 4.4.4.4
Reply to request 0 from 192.168.12.1, 172 ms
Reply to request 1 from 192.168.12.1, 144 ms
Reply to request 2 from 192.168.12.1, 80 ms
Reply to request 3 from 192.168.12.1, 88 ms
Ping results are OK.Lets show some verifying commands:
R2#show ip pim neighbor
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
S - State Refresh Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
192.168.23.3 FastEthernet0/0 01:16:17/00:01:36 v2 1 / DR S
192.168.24.4 FastEthernet1/0 01:16:12/00:01:19 v2 1 / DR S
R2# show ip pim rp mapping
PIM Group-to-RP Mappings
Group(s): 224.0.0.0/4, Static
RP: 3.3.3.3 (?)
R2#show ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.1.1.1), 00:47:12/stopped, RP 3.3.3.3, flags: SJC
Incoming interface: FastEthernet0/0, RPF nbr 192.168.23.3
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:47:12/00:00:00
(4.4.4.4, 224.1.1.1), 00:16:47/00:01:51, flags: JT
Incoming interface: FastEthernet1/0, RPF nbr 192.168.24.4
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:16:47/00:00:00
(*, 224.0.1.40), 00:47:14/00:02:10, RP 3.3.3.3, flags: SJPCL
Incoming interface: FastEthernet0/0, RPF nbr 192.168.23.3
Outgoing interface list: Null
No comments:
Post a Comment