Hi Michel,
May be it is not ready yet?
Here are some facts:
Each BGP instance is a separate process.
The BGP instances do not share any prefix table between them
The BGP instances do not communicate with each other and do not set up peering with each other
Only VPNv4/VPNv6/RT-Constrain address-families can be shared between more than one BGP instances. VPNv4/VPNv6 if shared across instance can not share any VRF tables
All VRFs with extranet dependencies must be restricted to a single BGP instance. It will not be possible to import between instances.
MDT SAFI, MVPN SAFI and MVPN-specific BGP knob should be configured on a single instance only. Users need to make sure that all multicast VRFs are configured on the same instance. This instance will communicate with multicast processes.
IPv4 /IPv6 Unicast and corresponding IPv4/IPv6 Labeled-unicast should be configured on the same instance. It is possible to have IPv4 Unicast and IPv4 Labeled-unicast on one instance and IPv6 Unicast and IPv6 Labeled-Unicast on another instance
All global peering addresses must be unique across instances.
Each instance must be configured with an unique BGP router-id
Current maximum number of recommended instances that can be placed on a single RP is limited to 2
Config Example
!
router bgp 3 instance vpn2
bgp router-id 20.0.0.2
address-family vpnv4 unicast
neighbor 20.0.101.2
remote-as 200
address-family vpnv4 unicast
route-policy inbound in
route-policy outbound out
!
!
!
router bgp 3 instance vpn1
bgp router-id 20.0.0.1
address-family vpnv4 unicast
neighbor 20.0.101.1
remote-as 200
address-family vpnv4 unicast
route-policy inbound in
route-policy outbound out
!
!
!
Regards,
/A
Please visit http://cisco.com/go/testdrive or contact your account rep to schedule nV tech demo.
