[c-nsp] BGP Peering with new client for vrf's

[John Elliot]

> 
> wow, what type of customer is this? If they are using MPLS-VPN
> themselves, provisioning a CsC service might be a more suitable option,
> depending on their requirements? 
> There is a new Inter-AS option ("AB"), where you can maintain control
> over the traffic using distinct (sub)-interfaces per VRF, but scale the
> control plane using a single eBGP session between the ASBRs. Take a look
> at " MPLS VPN - Inter-AS Option AB" feature
> (http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_vpn_ias
> _optab.html). 
> If you trust your client, a simple Inter-AS option B connection (vpnv4
> eBGP, labelled interface between ASBRs) would also work.
> 
> oli
> 


 

Thanks for the reply - Client is wireless provider....they state they would need to scale to this number of vrfs, hence not wanting to go the subint/vlan per vrf route....whether this is a reality is debateable.

 

So we use there existing AS and ours, but add them under vpnv4?(based on http://www.cisco.com/en/US/tech/tk436/tk428/technologies_configuration_example09186a0080094472.shtml#PEsaro)

 

router bgp xxxxx
neighbour 10.10.10.2 remote as yyyyy
address family vpnv4
neighbour 10.10.10.2 activate
neighbor 10.10.10.2 send-community extended

 

And on inter-as link, we do not enable mpls?

 

Then, how do we restrict which routes they can see?

 

Simply with route-target export/imports?

 

ip vrf CLIENTA
 rd xxxxx:108
 route-target export xxxxx:108
 route-target import xxxxx:108
 route-target import yyyyy:108
 maximum routes 256 75

 

And they would do similiar on there side?

 

ip vrf CLIENTA
 rd yyyyy:108
 route-target export yyyyy:108
 route-target import yyyyy:108
 route-target import xxxxx:108
 maximum routes 256 75

 

But then what would stop them route-target import xxxxxx:109 etc?