Biwa, it is most commonly used in L3VPN scenarios where you want to perform IBGP between the PE and CE instead of the more common EBGP.
It would look similar to this: someone@R1> show configuration routing-options | match autonomous autonomous-system 65412; So, my internal backbone ASN is 65412, but in this case the customer wants to do IBGP with me and their ASN is 65600. someone@R1> show configuration routing-instances VPNC instance-type vrf; interface ge-0/0/1.411; vrf-target target:65412:600; routing-options { autonomous-system 65600 independent-domain; } protocols { bgp { group IBGP { type internal; neighbor 192.168.30.1; } } } someone@R1> show route table VPNC VPNC.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.5.0.0/16 *[BGP/170] 00:05:26, localpref 100 AS path: I > to 192.168.30.1 via ge-0/0/1.411 10.6.0.0/16 *[BGP/170] 00:04:12, localpref 100, from 10.200.16.3 AS path: I > to 10.200.2.2 via ge-0/0/0.110, label-switched-path R1-R9 192.168.30.0/24 *[Direct/0] 00:05:28 > via ge-0/0/1.411 192.168.30.2/32 *[Local/0] 00:05:31 Local via ge-0/0/1.411 192.168.31.0/24 *[BGP/170] 00:04:12, localpref 100, from 10.200.16.3 AS path: I > to 10.200.2.2 via ge-0/0/0.110, label-switched-path R1-R9 Hope this helps. -Jeff On Jul 27, 2011, at 12:05 AM, biwa net wrote: > Dear All > > I am having a hard time understanding the concept of "independent-domain " , > > Although I read the doc about it , the explanation, is not very clearly > explained and not very clear in practical terms > > Anyone can explain in leman terms what is the role of it , and especially > can anyone give me some real life example where and how this would be > applied ? > > Thanks > > Biwa > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp