From: hSzeto Jeff (jytszeto@xxxxxxxxxxx)
Date: Sat Apr 13 2002 - 11:03:07 GMT-3
Hi Group,
Thank you for your responses and you all help me to make it works.
I have removed the "ip pim nbma" in the serial interfaces, add an loopback
to the
pim agent and make the lookback 0 participating in the pim process.
The following is the config and show commands
R1
ip multicast-routing
interface Loopback0
ip address 140.100.1.1 255.255.255.0
ip pim sparse-dense-mode
interface Serial0/0
ip address 140.100.123.1 255.255.255.192
ip pim sparse-dense-mode
encapsulation frame-relay
frame-relay map ip 140.100.123.2 102 broadcast
!
interface FastEthernet0/1
ip address 140.100.11.1 255.255.255.0
ip pim sparse-dense-mode
ip igmp join-group 230.0.0.1
duplex auto
speed auto
ip pim send-rp-announce Loopback0 scope 15 group-list 81
ip pim send-rp-discovery Loopback0 scope 15
access-list 81 permit 230.0.0.1
R1#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, 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
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.0.1.39), 00:00:42/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, 00:00:42/00:00:00
FastEthernet0/1, Forward/Sparse-Dense, 00:00:42/00:00:00
Serial0/0, Forward/Sparse-Dense, 00:00:42/00:00:00
(140.100.1.1, 224.0.1.39), 00:00:35/00:02:24, flags: CLT
Incoming interface: Loopback0, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0, Forward/Sparse-Dense, 00:00:35/00:00:00
FastEthernet0/1, Forward/Sparse-Dense, 00:00:35/00:00:00
(*, 224.0.1.40), 00:00:42/00:00:00, RP 0.0.0.0, flags: DJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/1, Forward/Sparse-Dense, 00:00:44/00:00:00
Serial0/0, Forward/Sparse-Dense, 00:00:44/00:00:00
(140.100.1.1, 224.0.1.40), 00:00:17/00:02:42, flags: CLT
Incoming interface: Loopback0, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0, Forward/Sparse-Dense, 00:00:17/00:00:00
FastEthernet0/1, Forward/Sparse-Dense, 00:
FastEthernet0/1, Forward/Sparse-Dense, 00:00:17/00:00:00
(*, 230.0.0.1), 00:00:44/00:00:00, RP 140.100.1.1, flags: SJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/1, Forward/Sparse-Dense, 00:00:44/00:02:21
R1#sh ip pim rp map
PIM Group-to-RP Mappings
This system is an RP (Auto-RP)
This system is an RP-mapping agent (Loopback0)
Group(s) 230.0.0.1/32
RP 140.100.1.1 (?), v2v1
Info source: 140.100.1.1 (?), via Auto-RP
Uptime: 08:18:51, expires: 00:02:07
R2
ip multicast-routing
interface Serial0
ip address 140.100.123.2 255.255.255.192
ip pim sparse-dense-mode
encapsulation frame-relay
frame-relay map ip 140.100.123.1 201 broadcast
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned
R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT
X - Proxy Join Timer Running
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.0.1.39), 00:08:13/00:02:59, RP 0.0.0.0, flags: DJC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial1, Forward/Sparse-Dense, 00:08:13/00:00:00
Serial0, Forward/Sparse-Dense, 00:08:13/00:00:00
(140.100.1.1, 224.0.1.39), 00:08:13/00:02:46, flags: CT
Incoming interface: Serial0, RPF nbr 140.100.123.1
Outgoing interface list:
Serial1, Forward/Sparse-Dense, 00:08:13/00:00:00
(*, 224.0.1.40), 00:08:47/00:00:00, RP 0.0.0.0, flags: DJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial1, Forward/Sparse-Dense, 00:08:47/00:00:00
Serial0, Forward/Sparse-Dense, 00:08:47/00:00:00
(140.100.1.1, 224.0.1.40), 00:05:56/00:02:01, flags: CLT
Incoming interface: Serial0, RPF nbr 140.100.123.1
Outgoing interface list:
Serial1, Forward/Sparse-Dense, 00:05:56/00:00:00
R2#sh ip pim rp map
PIM Group-to-RP Mappings
Group(s) 230.0.0.1/32
RP 140.100.1.1 (?), v2v1
Info source: 140.100.1.1 (?), via Auto-RP
Uptime: 08:24:25, expires: 00:02:47
R2#
R2#ping 230.0.0.1
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 230.0.0.1, timeout is 2 seconds:
Reply to request 0 from 140.100.123.1, 48 ms
Reply to request 0 from 140.100.123.1, 48 ms
Is it normal to have 2 respones while sending 1 ping?
Thank you
Jeff
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:07 GMT-3