From: alsontra@hotmail.com
Date: Thu Feb 05 2004 - 22:48:44 GMT-3
Sorry about that. I was running a similar configuration yesterday, and there
are a few things I notice right off about yours. Sparse-dense mode is not
recommended for NBMA interfaces, I think sparse should be used. Also you need
to issue the ip pim nbma-mode command on the serial interfaces( I used this
command on all NBMA attached interfaces)
ip pim nbma-mode <------This allows multipule mappings on your serial
ip pim sparse-mode
After you've add those, I would verify that the RP address is registering with
the spoke clients.
(sh ip pim rp )
Should look like this: Group: 228.1.1.1, RP: 223.1.1.2, v1, uptime 04:01:38,
expires 00:03:18
There are some exellent post regarding this topic, do a search for Brian
McGahan's last post regarding multicast.
Hope this helps,
Alsontra
----- Original Message -----
From: Hossam
To: alsontra@hotmail.com
Cc: ccielab@groupstudy.com
Sent: Thursday, February 05, 2004 3:26 PM
Subject: Re: Multicast over NBMA again!
Configurations are at the bottom of the original mail.
thanks
SAM
From: alsontra@hotmail.com Add to Address Book
To: ccielab@groupstudy.com, "Hossam" <sam6626@yahoo.com>
Subject: Re: Multicast over NBMA again!
Date: Thu, 5 Feb 2004 17:21:35 -0800
Can you post the configs for R5 and R2...
Alsontra
----- Original Message -----
From: "Hossam" <sam6626@yahoo.com>
To: <ccielab@groupstudy.com>
Sent: Thursday, February 05, 2004 3:12 PM
Subject: Multicast over NBMA again!
> Guys,
> I have been stuck all day with this. For me it is so strange. I hope
someone can help.
>
> R1 -----Ethernet----- R2 --S0/0.24----------------------S0/0-R4
> |
> S0/0.256
> |
> | |
> | NMBA |
>
> s0/0 S0/0
> Ether - R5 R6--- Ether
>
> I am running Auto-RP with R2 as the RP and the Agent.
> I configure mrm with R1 looback as the source and both R5 and R6
ethernet
as recievers AT R2.
>
> R5 is ok. It creats the (*.G) entry. It joins the shared treee. and
it
joins the SPT too. And it gets the muticast traffic with no problems.
>
> R6 is a bit lose. From the debug i can tell that R6 creats the shared
tree
entry and it joins it successfuly. BUT it joins the SPT INTIALLY (when
it
recieve the FIRST multicast packet for the group)
>
> Then (for some reason) it does't CONTINUE recieving the multicast
traffic
(ONE PACKET only is recieved for any group) . So it keeps counting down
for
the SPT entry and it prunes it eventually. And i stay with the (*,G)
entry
alone. And ofcourse no traffic is reaching the Ethernet behind R6 even
when
the SPT entry is still in the mroute table!!
>
>
>
> The NBMA is running OSPF. I tried both default NMBA and multipoint
options. In both cases all interfaces are reachable. But I get same
problem
with R6.
>
> I tried two hardwares with two Different IOSs in R6 positon. Both
gave the
same symptons.
>
> Can any one help!! (configurations r below)
>
> Thanks
> SAM
>
> R2:
>
> ip multicast-routing
> mpls ldp logging neighbor-changes
> !
> !
> !
> !
> !
> !
> !
> !
> !
> no voice hpi capture buffer
> no voice hpi capture destination
> !
> !
> mta receive maximum-recipients 0
> !
> !
> controller E1 1/0
> !
> !
> !
> interface Loopback0
> ip address 200.0.0.6 255.255.255.255
> ip pim sparse-dense-mode
> ip mrm test-receiver
> ip ospf network point-to-point
> !
> interface Ethernet0/0
> ip address 150.50.7.6 255.255.255.128
> ip pim sparse-dense-mode
> ip mrm test-receiver
> half-duplex
> !
> interface Serial0/0
> ip address 150.50.100.6 255.255.255.224
> ip pim sparse-dense-mode
> ip mrm test-receiver
> encapsulation frame-relay
> ip ospf network point-to-multipoint
> frame-relay map ip 150.50.100.2 162 broadcast
> frame-relay map ip 150.50.100.5 162 broadcast
> frame-relay map ip 150.50.100.6 162 broadcast
> no frame-relay inverse-arp
> !
> interface Serial0/1
> no ip address
> shutdown
> !
> interface Serial0/2
> no ip address
> encapsulation atm-dxi
> no keepalive
> !
> interface Serial0/3
> no ip address
> clockrate 128000
> !
> router ospf 1
> log-adjacency-changes
> network 150.50.7.6 0.0.0.0 area 0
> network 150.50.100.6 0.0.0.0 area 0
> network 200.0.0.6 0.0.0.0 area 0
> !
> ip http server
> ip classless
> !
> ip pim rp-address 200.0.0.4 10 override
> !
> ip mrm manager TEST1 ==============This is for another TEST
> manager Loopback0 group 224.11.11.2
> senders 1
> receivers 2 sender-list 1
> !
> !
> access-list 1 permit 150.50.17.1
> access-list 1 permit 224.88.88.88
> access-list 2 permit 150.50.7.7
> access-list 10 permit 224.44.44.44
> !
>
> ___________________________________________________
>
> R5
>
> ip multicast-routing
> mpls ldp logging neighbor-changes
> !
> !
> !
> !
> !
> !
> !
> !
> !
> no voice hpi capture buffer
> no voice hpi capture destination
> !
> !
> mta receive maximum-recipients 0
> !
> !
> !
> !
> interface Loopback0
> ip address 200.0.0.5 255.255.255.0
> ip pim sparse-dense-mode
> ip mrm test-receiver
> ip ospf network point-to-point
> !
> interface Ethernet0/0
> ip address 150.50.77.5 255.255.255.0
> ip pim sparse-dense-mode
> ip mrm test-receiver
> half-duplex
> !
> interface Serial0/0
> ip address 150.50.100.5 255.255.255.224
> ip pim sparse-dense-mode
> encapsulation frame-relay
> ip ospf network point-to-multipoint
> no fair-queue
> frame-relay map ip 150.50.100.2 152 broadcast
> frame-relay map ip 150.50.100.5 152 broadcast
> frame-relay map ip 150.50.100.6 152 broadcast
> no frame-relay inverse-arp
> !
> interface Serial0/1
> no ip address
> shutdown
> !
> router ospf 1
> log-adjacency-changes
> network 150.50.7.5 0.0.0.0 area 0
> network 150.50.77.5 0.0.0.0 area 111
> network 150.50.100.5 0.0.0.0 area 0
> network 200.0.0.5 0.0.0.0 area 0
> !
> ip http server
> ip classless
> !
> ip pim rp-address 200.0.0.4 10 override
> !
> !
> access-list 10 permit 224.44.44.44
> access-list 33 permit 224.44.44.44
> !
> ______________________________________________________-----
>
> R2
>
> ip multicast-routing
> mpls ldp logging neighbor-changes
> !
> !
> voice call carrier capacity active
> !
> !
> !
> !
> !
> !
> !
> no voice hpi capture buffer
> no voice hpi capture destination
> !
> !
> mta receive maximum-recipients 0
> !
> !
> !
> !
> interface Loopback0
> ip address 200.0.0.2 255.255.255.255
> ip pim sparse-dense-mode
> ip mrm test-receiver
> ip ospf network point-to-point
> !
> interface Ethernet0/0
> ip address 150.50.17.2 255.255.255.0
> ip pim sparse-dense-mode
> ip mrm test-sender
> half-duplex
> !
> interface Serial0/0
> no ip address
> encapsulation frame-relay
> no fair-queue
> no frame-relay inverse-arp
> frame-relay lmi-type cisco
> !
> interface Serial0/0.24 point-to-point
> ip address 150.50.24.2 255.255.255.0
> ip pim sparse-dense-mode
> frame-relay interface-dlci 124
> !
> interface Serial0/0.256 multipoint
> ip address 150.50.100.2 255.255.255.224
> ip pim sparse-dense-mode
> ip ospf network point-to-multipoint
> ip ospf priority 10
> frame-relay map ip 150.50.100.2 125 broadcast
> frame-relay map ip 150.50.100.5 125 broadcast
> frame-relay map ip 150.50.100.6 126 broadcast
> !
> interface Serial0/1
> no ip address
> shutdown
> !
> router ospf 1
> router-id 200.0.0.2
> log-adjacency-changes
> network 150.50.17.2 0.0.0.0 area 3
> network 150.50.24.2 0.0.0.0 area 1
> network 150.50.100.2 0.0.0.0 area 0
> network 200.0.0.2 0.0.0.0 area 0
> !
> ip http server
> ip classless
> !
> ip pim rp-address 200.0.0.4 10 override
> ip pim send-rp-announce Loopback0 scope 10
> ip pim send-rp-discovery Loopback0 scope 10
> !
> ip mrm manager TEST1
> manager Loopback0 group 224.11.11.2
> senders 1
> receivers 2 sender-list 1
> ip mrm manager TEST3
> manager Loopback0 group 224.45.45.45
> senders 1
> receivers 2 sender-list 1
> ip mrm manager TEST4
> manager Loopback0 group 224.33.33.33
> senders 1
> receivers 2 sender-list 1
> !
> !
> access-list 1 permit 200.0.0.1
> access-list 2 permit 150.50.7.6
> access-list 2 permit 150.50.77.5
> access-list 10 permit 224.44.44.44
>
>
>
>
-----------------------------------------------------------------------------
-
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online
This archive was generated by hypermail 2.1.4 : Fri Mar 05 2004 - 07:13:46 GMT-3