From: Prakash H Somani (pdsccie@rediffmail.com)
Date: Wed Sep 18 2002 - 13:46:50 GMT-3
Hi Beda,
Thanks for response...it will work then OK..but why should I make
R2 as RP ?? I accept i will have to make R2 as RP-agent but why RP
also ?? Why cant I keep RP on R1...is there any explanation link
on this ?
Also I have one more router connected on R2 on S0/0.104 P-T-P
subinterface (Samy physical as that of S0/0.256). If I give some
join- group on R4 E0...then even if R2 is RP...pinging does not
work....
Regards....Prakash
On Wed, 18 Sep 2002 beda jain wrote :
>make fram-relay hub as RP for 228.1.1.1 then it will work
>
>Thanks,
>Beda
>
>At 12:38 PM 9/18/2002 +0000, Prakash H Somani wrote:
>>Hi Friends....
>>
>>I am struggling with multicasting...can anyone please help ?
>>
>>Following is the Scenario:
>>
>>E2--R1 ------Ethernet-----R2
>> / \
>> / \
>> / \
>> R5 R6
>>
>>R2 is FrHUB and R5 n R6 are spoke to R2 with single DLCI.
>>
>>R1 Loopback is my RP. (10.1.1.1)
>>R2 Mapping agent.
>>R2 E2 address: 172.31.10.1 is igmp join-group 228.1.1.1
>>Running Sparse-mode. (Actually tried with Static RP and
>>Sparse-Dense mode also)
>>
>>I dont understand why I m not able to ping 228.1.1.1 from R5 or
>>R6. Following is the config:
>>
>>R2 Serial interface:
>>
>>interface Serial0/0.256 multipoint
>> ip address 172.31.100.2 255.255.255.248
>> no ip directed-broadcast
>> ip pim nbma-mode
>> ip pim sparse-mode
>> ip ospf message-digest-key 10 md5 wipro
>> ipx network 256
>> no ipx split-horizon eigrp 10
>> no arp frame-relay
>> frame-relay map llc2 106 broadcast
>> frame-relay map ipx 256.0000.0000.0005 105 broadcast
>> frame-relay map ipx 256.0000.0000.0006 106 broadcast
>> frame-relay map ip 172.31.100.2 105
>> frame-relay map ip 172.31.100.5 105 broadcast
>> frame-relay map ip 172.31.100.6 106 broadcast
>> no frame-relay inverse-arp
>>end
>>
>>ip pim send-rp-discovery scope 10
>>=============================
>>R6 Serial Interface:
>>
>>interface Serial0/0
>> ip address 172.31.100.6 255.255.255.248
>> no ip directed-broadcast
>> ip pim sparse-mode
>> encapsulation frame-relay
>> ip ospf message-digest-key 10 md5 wipro
>> ip ospf priority 0
>> no ip mroute-cache
>> ipx network 256
>> no fair-queue
>> frame-relay map llc2 601 broadcast
>> frame-relay map ipx 256.0000.0000.0002 601 broadcast
>> frame-relay map ipx 256.0000.0000.0005 601 broadcast
>> frame-relay map ip 172.31.100.2 601 broadcast
>> frame-relay map ip 172.31.100.5 601 broadcast
>> frame-relay map ip 172.31.100.6 601
>> no frame-relay inverse-arp
>> frame-relay lmi-type cisco
>>end
>>
>>======================
>>
>>R5 Config
>>
>>r5#sh runn int s0/0
>>Building configuration...
>>
>>Current configuration:
>>!
>>interface Serial0/0
>> ip address 172.31.100.5 255.255.255.248
>> ip directed-broadcast
>> ip pim sparse-mode
>> encapsulation frame-relay
>> ip ospf message-digest-key 10 md5 wipro
>> ip ospf priority 0
>> no ip mroute-cache
>> logging event subif-link-status
>> logging event dlci-status-change
>> ipx network 256
>> no fair-queue
>> frame-relay map ipx 256.0000.0000.0002 501 broadcast
>> frame-relay map ipx 256.0000.0000.0006 501 broadcast
>> frame-relay map ip 172.31.100.2 501 broadcast
>> frame-relay map ip 172.31.100.6 501 broadcast
>> no frame-relay inverse-arp
>> frame-relay lmi-type cisco
>>end
>>
>>===============
>>
>>R1 Config:
>>
>>Current configuration : 161 bytes
>>!
>>interface Ethernet5/0
>> ip address 172.31.10.1 255.255.255.0
>> ip pim sparse-mode
>> ip mobile arp
>> ip igmp join-group 228.1.1.1
>> half-duplex
>> ipx network 10
>>end
>>
>>r1#sh runn int fa0/0
>>Building configuration...
>>
>>Current configuration : 132 bytes
>>!
>>interface FastEthernet0/0
>> ip address 172.31.12.1 255.255.255.0
>> ip pim sparse-mode
>> duplex auto
>> speed auto
>> ipx network 12
>>end
>>
>>RP is available everywhere following is output from R5:
>>
>>04:49:23: Auto-RP: Received RP-discovery, from 172.31.100.2,
>>RP_cnt 1, ht 180
>>04:49:23: Auto-RP: Update (224.0.0.0/4, RP:10.1.1.1), PIMv2 v1
>>r5#
>>r5#
>>r5#sh ip pim rp m
>>04:50:22: Auto-RP: Received RP-discovery, from 172.31.100.2,
>>RP_cnt 1, ht 180
>>04:50:22: Auto-RP: Update (224.0.0.0/4, RP:10.1.1.1), PIMv2 v1
>>r5#sh ip pim rp ma
>>r5#sh ip pim rp mapping
>>r5#sh ip pim rp mapping
>>PIM Group-to-RP Mappings
>>
>>Group(s) 224.0.0.0/4
>> RP 10.1.1.1 (?), v2v1
>> Info source: 172.31.100.2 (?), via Auto-RP
>> Uptime: 04:29:37, expires: 00:02:50
>>Group(s): 224.0.0.0/4, Static
>> RP: 10.1.1.1 (?)
>>
>>r5#sh ip pim rp-ha
>>r5#sh ip pim rp-hash 228.1.1.1
>> RP 10.1.1.1 (?), v2v1
>> Info source: 172.31.100.2 (?), via Auto-RP
>> Uptime: 04:30:03, expires: 00:02:24
>>
>>Following is the mroute table at R2:
>>
>>r2#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 - Advertised via MSDP
>>Outgoing interface flags: H - Hardware switched
>>Timers: Uptime/Expires
>>Interface state: Interface, Next-Hop or VCD, State/Mode
>>
>>(*, 224.0.1.39), 04:23:50/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, 04:23:50/00:00:00
>> Serial0/0.104, Forward/Sparse-Dense, 04:23:50/00:00:00
>> Ethernet0/0, Forward/Sparse, 04:23:50/00:02:48
>>
>>(10.1.1.1, 224.0.1.39), 04:23:50/00:02:59, flags: CLT
>> Incoming interface: Ethernet0/0, RPF nbr 172.31.12.1
>> Outgoing interface list:
>> Serial0/0.104, Forward/Sparse-Dense, 04:23:50/00:00:00
>> Loopback0, Forward/Sparse-Dense, 04:23:50/00:00:00
>>(10.1.1.1, 224.0.1.39), 04:23:50/00:02:59, flags: CLT
>> Incoming interface: Ethernet0/0, RPF nbr 172.31.12.1
>> Outgoing interface list:
>> Serial0/0.104, Forward/Sparse-Dense, 04:23:50/00:00:00
>> Loopback0, Forward/Sparse-Dense, 04:23:50/00:00:00
>>
>>(*, 224.0.1.40), 04:23:50/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, 04:24:02/00:00:00
>> Serial0/0.104, Forward/Sparse-Dense, 04:24:02/00:00:00
>>
>>(10.2.2.2, 224.0.1.40), 04:23:13/00:02:55, flags: CLTA
>> Incoming interface: Loopback0, RPF nbr 0.0.0.0
>> Outgoing interface list:
>> Serial0/0.104, Forward/Sparse-Dense, 04:23:13/00:00:00
>>
>>(172.31.24.2, 224.0.1.40), 00:02:05/00:01:24, flags: CLT
>> Incoming interface: Serial0/0.104, RPF nbr 172.31.24.4
>> Outgoing interface list:
>> Ethernet0/0, Forward/Sparse, 00:02:06/00:03:25
>> Loopback0, Forward/Sparse-Dense, 00:02:06/00:00:00
>>
>>(*, 229.1.1.1), 04:24:02/00:00:00, RP 10.1.1.1, flags: SJCL
>> Incoming interface: Ethernet0/0, RPF nbr 172.31.12.1
>> Outgoing interface list:
>> Loopback0, Forward/Sparse-Dense, 04:24:02/00:02:25
>>
>>(*, 228.1.1.1), 00:01:07/00:02:59, RP 10.1.1.1, flags: SP
>> Incoming interface: Ethernet0/0, RPF nbr 172.31.12.1
>> Outgoing interface list: Null
>>
>>(172.31.100.5, 228.1.1.1), 00:01:31/00:01:28, flags: PT
>> Incoming interface: Serial0/0.256, RPF nbr 0.0.0.0
>> Outgoing interface list: Null
>>
>>
>>I know the last mroute should show me outgoing interface as e0/0
>>but it has been prunned ...I dont knwo why ??
>>
>>Thanks in advance.
>>
>>Regards....Prakash
This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:56 GMT-3