ZXR10 ZSR V2 Configuration Guide (IPv6)
Network
Next Hop
Metric
LocPrf
RtPrf
Path
i4:4::/64
1:2::1
100
200
1011 i
i5:5::/64
1:2::1
100
200
1011 i
i6:6::/64
1:2::1
100
200
1011 i
i7:7::/64
1:2::1
100
200
1011 i
i8:8::/64
1:2::1
100
200
1011 i
Verify that R2 can only learn routes 4:4:::/64 and 7:7::/64 permitted in route-map test1.
The logical relationships between match items in a routing policy is AND. If
route-map
test2 permit 10
is not matched, route 4:4:::/64 cannot be advertised to R3.
After the BGP routing policy is enabled, the sample output is as follows.
R2(config)#show bgp ipv6 unicast
/*R2 learns two BGP routes from R1*/
Status codes: * valid, > best, i - internal, s - stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network
Next Hop
Metric
LocPrf
RtPrf
Path
*> 4:4::/64
1:2::1
30000
20
1011 i
*> 7:7::/64
1:2::1
30000
20
1011 i
The detailed information about the two BGP routes is as follows.
R2#show bgp ipv6 unicast detail 4:4::/64
BGP routing table entry for 4:4::/64
08:50:07 received from 1:2::1 (11.1.1.1)
origin i, global nexthop 1:2::1, link-local nexthop FE80::220:23FF:FE1D:E0E,
localpref 30000 rtpref 20
as path [1011]
as4 path
R2#show bgp ipv6 unicast detail 7:7::/64
BGP routing table entry for 7:7::/64
08:50:07 received from 1:2::1 (11.1.1.1)
origin i, global nexthop 1:2::1, link-local nexthop FE80::220:23FF:FE1D:E0E,
localpref 30000 rtpref 20
as path [1011]
as4 path
08:41:38 advertised to 2:3::3 (1.1.1.1)
origin ?, global nexthop 1:2::1, localpref 200
as path [2 1011]
as4 path
9.1.2.5 Example: Configuring a Routing Policy for 6VPE
Configuration Description
shows a basic L3VPN networking topology. An MP-IBGP neighbor relationship
is established between PE1 and PE2 that are in the same AS. VRF test1 that resides
on PE1 advertises the Address routes generated by the local Loopback address and
9-20
SJ-20140504150128-018|2014-05-10 (R1.0)
ZTE Proprietary and Confidential