The following
example shows how to configure the translate-update feature for an IPv4 VRF
address-family named v1 and BGP neighbor n2 peer-group for VRF configuration:
Note |
Peer-template
configuration for BGP neighbor is not supported for this feature due to
conflicts with the earlier versions of Cisco software.
|
Device> enable
Device# configure terminal
Device(config)# router bgp 65000
Device(config-router)# address-family ipv4 vrf v1
Device(config-router-af)# neighbor n2 peer-group
Device(config-router-af)# neighbor n2 remote-as 4
Device(config-router-af)# neighbor 10.1.1.1 peer-group n2
Device(config-router-af)# neighbor 10.1.1.1 activate
Device(config-router-af)# neighbor 10.1.1.1 translate-update multicast unicast
Device(config-router-af)# end
The following is
sample output from the
show bgp vpnv4 multicast
vrf command. As the VRF aware BGP translate-update feature is
configured, the state of the neighbor displays “NoNeg”:
Device# show bgp vpnv4 multicast vrf v1 summary
BGP router identifier 10.1.3.1, local AS number 65000
BGP table version is 8, main routing table version 8
7 network entries using 1792 bytes of memory
8 path entries using 960 bytes of memory
5/3 BGP path/bestpath attribute entries using 1280 bytes of memory
3 BGP AS-PATH entries using 88 bytes of memory
2 BGP extended community entries using 48 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 4168 total bytes of memory
BGP activity 23/2 prefixes, 33/9 paths, scan interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.1.1.1 4 4 5 10 1 0 0 00:01:10 (NoNeg)
10.1.3.2 4 2 12 10 8 0 0 00:01:33
The following is
sample output from the
show ip route multicast
vrf command:
Note |
The routes
configured using the translate-update feature does not have the “+” symbol
against the prefixes in the Routing Information Base (RIB) table. Appearance of
the symbol in the first entry indicates that the unicast route has leaked into
the multicast table. However, the second entry is a translate-update route,
which appears to be a multicast route.
|
Device# show ip route multicast vrf v1
B + 10.1.1.0/24 [20/0] via 10.1.1.1 (v1), 00:00:08
B 10.1.1.0/24 [20/0] via 10.1.1.1 (v1), 00:00:42
The following is
sample output from the
show
running-config command:
Note |
The
provider-edge (PE) device must activate its BGP neighbor under the multicast
address-family even though the neighbor is not capable of multicast routing. If
the unicast address-family identifier has the route-map configured and
multicast address-family identifier has no route-map configured, the unicast
route-map controls the route under the unicast table but not the route under
multicast table.
|
Device# show running-config
address-family ipv4 vrf v1
redistribute connected
redistribute static
neighbor 10.1.1.1 remote-as 4
neighbor 10.1.1.1 activate
neighbor 10.1.1.1 translate-update multicast unicast
neighbor 10.1.1.1 remote-as 4
neighbor 10.1.1.1 activate
exit-address-family
!
address-family ipv4 multicast vrf v1
redistribute connected
redistribute static
neighbor 10.1.1.1 remote-as 4
neighbor 10.1.1.1 activate
neighbor 10.1.1.1 soft-reconfiguration inbound
neighbor 10.1.1.1 route-map x in
exit-address-family
Note |
The “neighbor
10.1.1.1 soft-reconfiguration inbound” and the “ neighbor 10.1.1.1 route-map x
in” field in the output indicate that only the routes in the BGP multicast
table are affected.
|
The following is
sample output from the
show
running-config command when you configure a neighbor under
different address-families:
Note |
Configuring
the BGP neighbor under different address-families manipulates the unicast
routes and multicast routes advertised to the neighbor.
|
Configuration for
IPv4/IPv6 unicast address-family:
Device# show running-config
address-family ipv4
neighbor 20.2.2.1 activate
neighbor 20.2.2.1 translate-update multicast unicast
exit-address-family
!
address-family ipv4 multicast
neighbor 20.2.2.1 activate
exit-address-family
!
Configuration for
IPv4/IPv6 VRF unicast address-family:
Device# show running-config
address-family ipv4 vrf v1
neighbor 20.2.2.1 remote-as 4
neighbor 20.2.2.1 activate
neighbor 20.2.2.1 translate-update multicast unicast
exit-address-family
!
address-family ipv4 multicast vrf v1
neighbor 20.2.2.1 remote-as 4
neighbor 20.2.2.1 activate
exit-address-family
!
The following is
sample configuration of the translate-update feature from a device with the old
version of Cisco Software. The neighbor, in this case, is configured for
IPv4/IPv6 unicast address-family, without running the
address-family command:
Configuration in
the old format, without an address-family configured:
Device> enable
Device# configure terminal
Device(config)# router bgp 65000
Device(config-router)# neighbor 20.2.2.1 remote-as 4
Device(config-router)# neighbor 20.2.2.1 translate-update nlri ipv4 multicast unicast
Device(config-router-af)# end
Configuration in
the new format, without an address-family configured:
Device> enable
Device# configure terminal
Device(config)# router bgp 65000
Device(config-router)# neighbor 20.2.2.1 remote-as 4
Device(config-router)# neighbor 20.2.2.1 translate-update nlri multicast unicast
Device(config-router-af)# end
Feedback