From: gladston@br.ibm.com
Date: Tue Apr 20 2004 - 09:54:36 GMT-3
Hi,
Trying to reproduce the example using ip pim nbma-mode with success, but not understanding how the dense groups (224.0.1.39 and 224.0.1.40) used by Auto-RP works, because the connection between A<->B and A<->C is configured for PIM SPARSE-MODE.
http://www.cisco.com/en/US/tech/tk828/tk363/technologies_white_paper09186a00800d6b61.shtml#xtocid3
Any reading suggestion?
A#sh 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 - Advertised via MSDP, U - URD,
I - Received Source Specific Host Report
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.0.1.39), 16:01:31/00:00:00, RP 0.0.0.0, flags: DJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Loopback0, Forward/Sparse-Dense, 16:01:31/00:00:00
(*, 224.0.1.40), 16:01:32/00:00:00, RP 0.0.0.0, flags: DJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Loopback0, Forward/Sparse-Dense, 16:01:32/00:00:00
A# show ip pim rp ma
sh ip pim rp ma
PIM Group-to-RP Mappings
This system is an RP (Auto-RP)
This system is an RP-mapping agent (Loopback0)
Group(s) 224.0.0.0/4
RP 150.20.5.5 (?), v2v1
Info source: 150.20.5.5 (?), via Auto-RP
Uptime: 00:22:59, expires: 00:02:00
A# show run
ip multicast-routing
!
interface Loopback0
ip address 150.20.5.5 255.255.255.0
ip pim sparse-dense-mode
!
interface Serial0/0
bandwidth 1000
ip address 150.20.125.5 255.255.255.0
ip pim nbma-mode
ip pim sparse-mode
encapsulation frame-relay
no ip route-cache
ip ospf priority 255
no ip mroute-cache
frame-relay map ip 150.20.125.1 511 broadcast
frame-relay map ip 150.20.125.2 512 broadcast
!
ip pim send-rp-announce Loopback0 scope 10
ip pim send-rp-discovery Loopback0 scope 10
!
end
B# show run
ip multicast-routing
!
interface Loopback0
ip address 150.20.1.1 255.255.255.0
ip pim sparse-dense-mode
!
interface Serial0.125 multipoint
ip address 150.20.125.1 255.255.255.0
ip pim nbma-mode
ip pim sparse-mode
no ip route-cache
ip ospf priority 0
no ip mroute-cache
frame-relay map ip 150.20.125.1 115
frame-relay map ip 150.20.125.2 115
frame-relay map ip 150.20.125.5 115 broadcast
!
end
B# show ip pim rp ma
#sh ip pim rp ma
PIM Group-to-RP Mappings
Group(s) 224.0.0.0/4
RP 142.20.5.5 (?), v2v1
Info source: 142.20.5.5 (?), via Auto-RP
Uptime: 00:06:38, expires: 00:02:17
#sh 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 - Advertised via MSDP, U - URD,
I - Received Source Specific Host Report
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.0.1.39), 00:08:45/00:02:59, RP 0.0.0.0, flags: DJP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null
(150.20.5.5, 224.0.1.39), 00:02:45/00:00:14, flags: PT
Incoming interface: Serial0.125, RPF nbr 150.20.125.5
Outgoing interface list: Null
(*, 224.0.1.40), 16:10:13/00:02:59, RP 0.0.0.0, flags: DJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Loopback0, Forward/Sparse-Dense, 16:10:13/00:00:00
(150.20.5.5, 224.0.1.40), 00:06:54/00:02:05, flags: CLT
Incoming interface: Serial0.125, RPF nbr 150.20.125.5
Outgoing interface list:
Loopback0, Forward/Sparse-Dense, 00:06:54/00:00:00
This archive was generated by hypermail 2.1.4 : Mon May 03 2004 - 19:48:50 GMT-3