Unless you're running nonstop active routing (NSR), you can get away with simply setting the global route-distinguisher-id value to the loopback IP of your box at [edit routing-options] instead of manually specifying the RD in every routing-instance. Then, all routing-instances will import it and generate the 2nd value for you (ie. ip:some_value). That said, if you are planning on enabling NSR in the future, just create RDs in each routing-instance now to save yourself a headache later.
David 2008/6/17 Christian Koch <[EMAIL PROTECTED]>: > if you're using bgp signaling for auto discovery then you need RD, if you > are using LDP, you do not > > if you still dont know why you need an RD when using bgp, i suggest you read > the following RFC's > > > > http://tools.ietf.org/html/rfc4761 > http://tools.ietf.org/html/rfc4762 > > > > > > > > > > > > > On Tue, Jun 17, 2008 at 8:07 AM, narasimha murthy <[EMAIL PROTECTED]> > wrote: > >> Hi can any one tell me why RD is required for BGP based VPLS configaration. >> in case of L3 vpn RD is used to make customer ipv4 address globally unique >> in MPLS domain. >> But i dont understand the usage of RD in case of VPLS. >> >> Murthy >> >> _______________________________________________ >> juniper-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
