lo0 { unit 16 { family inet { address 192.168.1.100/32; } } unit 25 { family inet { address 202.162.208.1/32; } } } } ..... routing-instances { vpn1 { instance-type vrf; interface fxp0.10; interface lo0.16; <----------------------------- route-distinguisher 2500:100; vrf-import vpn1-import; vrf-export vpn1-export; vrf-target target:2500:100; vrf-table-label; protocols { bgp { group to_ce3 { type external; peer-as 65000; as-override; neighbor 192.168.1.1; } } } } }
Aldur wrote: » There's a few rules you'll want to keep in mind here. First, as previously noted, you can add as many IP addresses to the loopback interface as you want but only if this is under the same logical unit. Second you can only have 1 logical unit per loopback interface per routing instance. The later is what you saw in the link that you provided. Below is a section of the config from the link that was provided. Notice that there are 2 unit's defined under the loopback interface and that unit 16 is placed inside the vpn1 routing instance. This leaves only unit 25 under the main routing instance inside the logical router. lo0 { unit 16 { family inet { address 192.168.1.100/32; } } unit 25 { family inet { address 202.162.208.1/32; } } } } ..... routing-instances { vpn1 { instance-type vrf; interface fxp0.10; interface lo0.16; <----------------------------- route-distinguisher 2500:100; vrf-import vpn1-import; vrf-export vpn1-export; vrf-target target:2500:100; vrf-table-label; protocols { bgp { group to_ce3 { type external; peer-as 65000; as-override; neighbor 192.168.1.1; } } } } } HTH