Sho ip pim RP Mapping

[mikegrous]

I understand the command. But is there a way to make the time so it doesnt take a minute to refresh to its neighbors?

R7(config)#do sho ip pim rp mapp

PIM Group-to-RP Mappings

This system is an RP-mapping agent (Loopback1)

Group(s) 224.0.0.0/4

RP 103.103.103.103 (?), v2v1

Info source: 103.103.103.103 (?), elected via Auto-RP

Uptime: 00:07:31, expires: 00:02:24

RP 99.99.99.8 (?), v2v1

Info source: 99.99.99.8 (?), via Auto-RP

Uptime: 00:07:04, expires: 00:02:54

Group(s) 236.1.1.1/32

RP 104.104.104.104 (?), v2v1

Info source: 104.104.104.104 (?), elected via Auto-RP

Uptime: 00:03:56, expires: 00:01:59

Group(s) 239.0.0.0/8

RP 104.104.104.104 (?), v2v1

Info source: 104.104.104.104 (?), elected via Auto-RP

Uptime: 00:03:56, expires: 00:02:02

[Harold Ritter]

Michael,

Try configuring "no ip domain-lookup" in global configuration mode. This will stop the router from attempting to reverse lookup the addresses, which explains the longer response time.

Regards

[Harold Ritter]

Michael,

Sorry I misunderstood your question. I thought it was in relations to the time it takes sometimes to get the full output when you type this command.

Regards

[Jerry Ye]

Hi Mike,

With Auto-RP, there are two places to adjust the timer:

1) the RP by default will announce itself every 60 sec

http://www.cisco.com/en/US/docs/ios/ipmulti/command/reference/imc_04.html#wp1014843

2) the mapping agent by default send out the discovery message every 60 sec

http://www.cisco.com/en/US/docs/ios/ipmulti/command/reference/imc_04.html#wp1019374

Personally, I will make both timer to match.

HTH,

jerry

[mikegrous]

Ok after playing with multicast even more i have another question. According to ciscos site: (This is using BRS)

priority

(Optional) Integer from 0 to 255. The bootstrap router with the larger priority is preferred. If the priority values are the same, the router with the larger IP address is the bootstrap router. The default value is 0.

However it seems from the output of show ip mrouter that the higher lower RP is preferred. Or am i reading this wrong?

____SHOW IP RP MAPPING (104.104.104.104 pri higher)____

Group(s) 224.0.0.0/4

RP 103.103.103.103 (?), v2

Info source: 99.99.99.7 (?), via bootstrap, priority 199, holdtime 150

Uptime: 00:31:17, expires: 00:02:23

RP 104.104.104.104 (?), v2

Info source: 99.99.99.7 (?), via bootstrap, priority 200, holdtime 150

Uptime: 00:40:20, expires: 00:02:21

__SHOW IP MROUTE (104.104.104.104 pri higher)____

(*, 239.0.1.1), 00:11:21/00:00:35, RP 103.103.103.103, flags: SP

Incoming interface: FastEthernet1/4, RPF nbr 146.46.134.30

Outgoing interface list: Null

(*, 239.2.2.2), 00:17:19/00:02:56, RP 103.103.103.103, flags: SJCL

Incoming interface: FastEthernet1/4, RPF nbr 146.46.134.30

Outgoing interface list:

Loopback1, Forward/Sparse-Dense, 00:17:19/00:02:56

____SHOW IP RP MAPPING (104.104.104.104 pri lower)____

Group(s) 224.0.0.0/4

RP 104.104.104.104 (?), v2

Info source: 99.99.99.7 (?), via bootstrap, priority 200, holdtime 150

Uptime: 00:40:47, expires: 00:02:26

RP 103.103.103.103 (?), v2

Info source: 99.99.99.7 (?), via bootstrap, priority 201, holdtime 150

Uptime: 00:31:44, expires: 00:02:23

__SHOW IP MROUTE (104.104.104.104 pri lower)____

(*, 239.0.1.1), 00:00:23/00:03:06, RP 104.104.104.104, flags: S

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

FastEthernet1/4, Forward/Sparse-Dense, 00:00:23/00:03:06

(*, 239.2.2.2), 00:18:55/00:02:35, RP 104.104.104.104, flags: SJCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Loopback1, Forward/Sparse-Dense, 00:18:55/00:02:35

[Harold Ritter · Accepted solution]

Michael,

The priority you are referring to is the BSR priority, not the RP priority.

RFC5059 defines 0 as the highest priority for the RP priority (the lower the better).

Regards

[mikegrous]

ahhhh its great when things just make sence :).

Thanks alow