From: Ozgur Guler (Garanti Teknoloji) (OzgurG@garanti.com.tr)
Date: Tue Oct 07 2003 - 11:52:13 GMT-3
"ip pim nbma-mode"
works for sparse-mode only...
Ozgur
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
SANCHEZ-MONGE,ANTONIO (HP-France,ex2)
Sent: Tuesday, October 07, 2003 4:30 PM
To: 'ccielab@groupstudy.com'
Subject: RE: Multicast in NBMA
Hi Lee,
Thanks a lot for the tip.
Unfortunately it does not seem to fix my problem by itself:
r2#sh run int se 0/0.30
Building configuration...
Current configuration : 343 bytes
!
interface Serial0/0.30 multipoint
ip address 192.168.30.2 255.255.255.240
ip pim sparse-dense-mode
no ip route-cache
ip ospf network point-to-multipoint
no ip mroute-cache
frame-relay map ip 192.168.30.3 283 broadcast
frame-relay map ip 192.168.30.4 284 broadcast
frame-relay map ip 192.168.30.5 285 broadcast
end
r2# clear ip mroute *
After ping from r4 to 225.6.7.8
r2# show ip mroute 225.6.7.8
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
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 225.6.7.8), 00:03:13/00:00:00, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Loopback0, Forward/Sparse-Dense, 00:03:13/00:00:00
Serial0/0.30, Forward/Sparse-Dense, 00:03:13/00:00:00
(192.168.30.4, 225.6.7.8), 00:02:40/00:00:19, flags: CLT
Incoming interface: Serial0/0.30, RPF nbr 192.168.30.4
Outgoing interface list:
Loopback0, Forward/Sparse-Dense, 00:02:40/00:00:00
I don't know what else I am missing.
Thanks in advance.
Cheers,
Antonio.
-----Original Message-----
From: Carter, Lee [mailto:Lee.Carter@CommerceBank.com]
Sent: martes, 07 de octubre de 2003 15:10
To: 'SANCHEZ-MONGE,ANTONIO (HP-France,ex2)'; 'ccielab@groupstudy.com'
Subject: RE: Multicast in NBMA
Not real strong with multicast but I do know that if you have a multipoint
interface running pim you should also add the command:
ip pim nbma-mode <<-- think that's the syntax.
This informs the router that there is more than one multicast capable device
off of that interface.
P.S. This command only goes on the hub router too. (R2's multipoint
interface).
HTH
Lee
-----Original Message-----
From: SANCHEZ-MONGE,ANTONIO (HP-France,ex2)
[mailto:antonio.sanchez-monge@hp.com]
Sent: Tuesday, October 07, 2003 7:32 AM
To: 'ccielab@groupstudy.com'
Subject: Multicast in NBMA
Hi All,
Nice to meet you. I am beginning to prepare CCIE lab.
Could you please help me with this problem?
My topology: Frame-relay multipoint
r2 192.168.30.2(lo0 = 192.168.2.2)
/ / \
/ / \
/ / \
/ / \
(r4)(r3) (r5)
|________|
OSPF is running everywhere, every router can ping the others' loopbacks.
Also PIM Sparse-Dense is running everywhere. The frame-relay maps are all
configured for broadcast.
The Ethernet interface of r3 (192.168.20.3) and r2 loopback (192.168.2.2)
are multicast group 225.6.7.8 receivers.
When the multicast sender is r4, only r2 replies, whereas if it is r2 the
sender, r3 replies too.
I think this has to do with the multipoint architecture, but I cannot see
how to get a reply from r3 r4 (or how to get r2 forwarding the multicast
packet originated by r4 to r3). Any clues?
r2#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 - Candidate for MSDP Advertisement,
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.40), 00:44:09/00:00:00, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.30, Forward/Sparse-Dense, 00:44:09/00:00:00
(*, 225.6.7.8), 00:15:22/00:00:00, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Loopback0, Forward/Sparse-Dense, 00:07:56/00:00:00
Serial0/0.30, Forward/Sparse-Dense, 00:15:22/00:00:00
(192.168.2.2, 225.6.7.8), 00:00:07/00:02:52, flags: CLT
Incoming interface: Loopback0, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.30, Forward/Sparse-Dense, 00:00:10/00:00:00
(192.168.30.4, 225.6.7.8), 00:02:57/00:00:03, flags: CLT
Incoming interface: Serial0/0.30, RPF nbr 192.168.30.4
Outgoing interface list:
Loopback0, Forward/Sparse-Dense, 00:02:57/00:00:00
r2#i
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static
route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
192.168.30.0/24 is variably subnetted, 4 subnets, 2 masks
O 192.168.30.4/32 [110/64] via 192.168.30.4, 00:30:40, Serial0/0.30
O 192.168.30.5/32 [110/64] via 192.168.30.5, 00:30:40, Serial0/0.30
O 192.168.30.3/32 [110/64] via 192.168.30.3, 00:30:40, Serial0/0.30
C 192.168.30.0/28 is directly connected, Serial0/0.30
192.168.4.0/32 is subnetted, 1 subnets
O 192.168.4.4 [110/65] via 192.168.30.4, 00:30:40, Serial0/0.30
192.168.2.0/32 is subnetted, 1 subnets
C 192.168.2.2 is directly connected, Loopback0
192.168.3.0/32 is subnetted, 1 subnets
O 192.168.3.3 [110/65] via 192.168.30.3, 00:30:41, Serial0/0.30
Thanks & Cheers,
Antonio.
***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
This archive was generated by hypermail 2.1.4 : Mon Nov 24 2003 - 07:52:58 GMT-3