RE: need help with manually specifying RP

From: Michael Zuo (mzuo@ixiacom.com)
Date: Tue Nov 21 2006 - 18:03:05 ART


Thanks guys. This means I need "ip pim rp-address" on all the routers
involved when autoRP and BSR are not used, just to be on the safe side?

thanks

-----Original Message-----
From: srdja blagojevic [mailto:srdja1@pexim.co.yu]
Sent: Tuesday, November 21, 2006 12:51 PM
To: Michael Zuo; ccielab@groupstudy.com
Subject: RE: need help with manually specifying RP

R2 would not "tell" R1 that it is RP. You need to manually "tell" R1
that it
is RP with command:

  ip pim rp-address 150.1.14.1

If you want to automatically exchange RP info between routers, you
should
use AutoRP or BSR.

HTH,
Srdja

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Michael Zuo
Sent: Tuesday, November 21, 2006 20:58
To: ccielab@groupstudy.com
Subject: need help with manually specifying RP

Hi Group

I have

R1------------R2

|

|

150.1.14.1

And on R2:

Rack1R2(config)#do sh ip pim rp

Group: 239.1.1.1, RP: 150.1.14.1, uptime 00:02:28, expires never

Group: 224.0.1.40, RP: 150.1.14.1, uptime 00:06:28, expires never

Rack1R2(config)#do sh run | in pim

 ip pim sparse-mode

 ip pim sparse-mode

ip pim rp-address 150.1.14.1

Rack1R2(config)#do ping 150.1.14.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 150.1.14.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 28/60/104 ms

Rack1R2(config)#

And on R1:

Rack1R1(config)#do sh run int e0/1

Building configuration...

Current configuration : 149 bytes

!

interface Ethernet0/1

 ip address 150.1.14.1 255.255.255.0

 ip pim sparse-mode

 ip igmp join-group 239.1.1.1

 no ip mroute-cache

 half-duplex

end

Rack1R1(config)#do sh ip pim rp

Group: 239.1.1.1, RP: 0.0.0.0

Rack1R1(config)#

My understanding is that if R2 tells R1 that R1 is the RP, R1 should
automatically behave like a RP. I don't understand why my R1 is not
considering itself as the RP?

Thanks a lot....



This archive was generated by hypermail 2.1.4 : Fri Dec 01 2006 - 08:05:48 ART