No idea what happened to the formating of the last Email, so here it is again,
pasted from Word this time! Hope you can read it!
Hello all,
Ages ago, I posted a query regarding multicast and pim NBMA
mode on frame. Well, finally today, I
got back to doing another test on proctorlabs kit...and the suggested solution
STILL did not work!
Again, this was a homemade lab:
TOPOLOGY
-------------
classic WB 2 topology of R2/R4/R5 being a frame hub and
spoke, R2 hub. Pim set up on all routers
and auto-rp RP and mapping agent live behing R5.
R8 (RP) -> R7 (Mapping agent) -> R5 -> DLC502 ->
R2 -> DLCI 204 -> R4.
All interfaces set to PIM SM. All can see each other as neighbours. R2 set to
be PIM DR on frame (suggestion from
last time I tried this!). R2 set for pim
NBMA mode on its frame interface.
SYMPTOMS
--------------
R8 can see rp mapping, R7 can see RP mapping, R5 can see RP
mapping, R2 can see RP mapping, R4 cannot.
All these were configured:
OSPF in point-to-multipoint mode on frame and broadcast on
LANs. Full IP connectivity within this
small cloud.
PIM NBMA mode on R2 frame interface
R2 PIM DR priority 0f 255, 0 on R4 and R5.
Debug ip mpacket details and debug pim auto (forget exact
syntax but it is the auto-rp debug)
Results:
R4 is not receiving ANY multicast whatsoever. R2 is receiving auto-rp info,
but is not
sending back out its frame interface again to R4.
My solution was to configure a GRE tunnel from R2 to R4,
move PIM onto that adjust static mroute accordingly. Yes I know, could have
used PPPoFr but that
was more typing!
However, this to me seems like a frig. I thought the whole point of pim NBMA
mode is
that is...sort of...acted like "no ip split-horizon" does for
routing, and R2 should advertise the RP and mapping agent advertisements back
out its frame interface again. It just
did not do this.....
Is my understanding flawed here, or have a stumbled across
one of those "a reload should fix that" things?
Configs below:
R2
--
ip multicast-routing
ip pim autorp listener
int ser0/1/0
encap frame
no frame inverse
ip address 10.1.1.1 255.255.255.0
frame map ip 10.1.1.1 204 broad
frame map ip 10.1.1.4 204
frame map ip 10.1.1.5 205 broad
ip ospf net point-to-multipoint
ip ospf 1 area 0
ip pim sparse-mode
ip pim nbma-mode
ip pim dr-priority 255
R4
--
ip multicast-routing
ip pim autorp listener
int ser0/0/0
encap frame
no frame inverse
ip address 10.1.1.4 255.255.255.0
frame map ip 10.1.1.1 402 broad
frame map ip 10.1.1.4 402
frame map ip 10.1.1.5 402
ip ospf net point-to-multipoint
ip ospf 1 area 0
ip pim sparse-mode
ip pim dr-pri 0
int f0/0
ip address 10.1.4.4 255.255.255.0
ip pim sparse-mode
ip ospf 1 area 0
R5
---
ip multicast-routing
ip pim autorp listener
int ser0/1/0
encap frame
no frame inverse
ip address 10.1.1.5 255.255.255.0
frame map ip 10.1.1.1 502 broad
frame map ip 10.1.1.4 502
frame map ip 10.1.1.5 502
ip ospf net point-to-multipoint
ip ospf 1 area 0
ip pim sparse-mode
ip pim dr-prior 0
int f0/0
ip address 10.1.5.5 255.255.255.0
ip ospf 1 area 0
descr RP and Mapping agent live out here.....
Regards, George.
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
Are you a CCNP or CCIE and looking for a job? Check out
www.PlatinumPlacement.com
http://onlinestudylist.com/mailman/listinfo/ccie_rs
