My guess is they are doing vrf-lite and using frame-relay or dot1q to bring these 3 VRFs to you. Which means the RD (used for MPLS L3VPNs) are only locally significant in the case of vrf-lite and are arbitrary numbers. It would be nice if Cisco didn't require RD's for vrf-lite cause they service no purpose.
Now the import and export statements in vrf-lite also serve no purpose, but also not required. Interesting that they exist in the config. As long as no interfaces are configured with 'mpls ip' and you don't have a 'address-family vpnv4' configured under BGP those values are meaningless outside of the local router. HTH, Brandon On Thu, Apr 2, 2009 at 9:59 AM, ChrisSerafin <[email protected]> wrote: > I have 3 VRF's on a CE router: > > > > ip vrf xxx-General > rd 1:10 > route-target export 1:10 > route-target import 1:10 > ! > ip vrf xxx-Guest > rd 1:30 > route-target export 1:30 > route-target import 1:30 > ! > ip vrf xxx-Voice > rd 1:20 > route-target export 1:20 > route-target import 1:20 > > I just got 3 new VRF's from the ISP confgured, and I'm wondering what > numbers I need to have for the 'rd' and 'route-target xxport' commands...? > Are these arbitrary, come from the ISP, or can I just use 40, 50, and 60? > > > Thanks, > > chris > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
