28.06.2014 Views

Discussion

Discussion

Discussion

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The anycast PIM configuration is quite similar to that for anycast RP. On the RP<br />

routers, configure the loopback interface with the shared RP address. This address<br />

tells other routers in the PIM-SM domain what IP address to use for the RP address.<br />

Mark the regular loopback address as the primary address so that address is used as<br />

the router ID by unicast routing protocols. Verify the loopback interface configuration:<br />

aviva@RouterA> show configuration interfaces lo0<br />

unit 0 {<br />

family inet {<br />

address 192.168.13.1/32 {<br />

primary;<br />

}<br />

address 10.0.1.1/32;<br />

}<br />

}<br />

On RouterA, 192.168.13.1 is the primary loopback address, to be used by BGP and<br />

OSPF as the router ID, and 10.0.1.1 is the shared RP address.<br />

Instead of configuring the shared RP address at the [edit pim rp local] hierarchy as<br />

you did with anycast RP, you do this one level lower, at [edit pim rp local family<br />

inet]. You must configure three parameters: the shared RP address, a list of all the<br />

RP routers in the PIM-SM domain (called the RP set), and the primary loopback<br />

address of the local router. The RP set must be the same on all RP routers in the<br />

domain so that all the RPs have a consistent view of the active sources. If the lists are<br />

different, anycast PIM will not work. The configuration shown in this recipe looks<br />

like this:<br />

[edit protocols]<br />

aviva@RouterA# show<br />

pim {<br />

rp {<br />

local {<br />

family inet {<br />

address 10.0.1.1; #

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!