Writing assessments that examine the correctness of community system configurations is tough (overview, extra particulars). It’s additionally an fascinating train in getting the timing good:
- Routing protocols are an eventually-consistent distributed system, and issues finally seem in the correct place (should you bought the configurations proper), however you by no means know when precisely that may occur.
- You possibly can subsequently set some affordable higher bounds on when issues ought to occur, and declare failure if the timeouts are exceeded. Even then, you’ll get false positives (as in: the check is telling you the configurations are incorrect, when it’s only a system having a nasty hair day).
And simply whenever you suppose you nailed it, you encounter a tool that blows your assumptions out of the water.
The check was purported to be easy: examine whether or not the route redistribution into BGP works. The preliminary lab topology had a tool beneath check (DUT) that redistributed OSPF into BGP, an OSPF-speaking router (R2), and a BGP-speaking router (X1). The validation assessments fastidiously progressed down the joyful path:
- Do we’ve got IPv4 and IPv6 EBGP classes between X1 and DUT?
- Do we’ve got OSPFv2 and OSPFv3 classes between R2 and DUT?
- Can we see an OSPFv2 prefix marketed by R2 within the IPv4 BGP desk on X1 (and likewise for IPv6)?
It labored on all of the gadgets we examined, after which we added the static routes on the DUT to the combination. Not a giant deal, proper? Simply add one other check to examine whether or not the static routes are propagated into BGP. The timing doesn’t matter, proper? In spite of everything, if a router manages to redistribute OSPF routes into BGP, it shouldn’t have any drawback redistributing its static routes into BGP on the identical time.
And at that time, I entered a bizarre parallel universe of Cisco IOS/XE. Let’s begin with the OSPF-to-BGP redistribution state of affairs. Listed below are the IPv4 debugging printouts (generated with debug ip routing and debug bgp all updates) for 10.0.0.3/32 (the loopback interface of R1):
*Jul 15 12:08:48.766: %OSPF-5-ADJCHG: Course of 1, Nbr 10.0.0.3 on Ethernet0/2 from LOADING to FULL, Loading Finished
*Jul 15 12:08:51.223: %OSPFv3-5-ADJCHG: Course of 1, IPv6, Nbr 10.0.0.3 on Ethernet0/2 from LOADING to FULL, Loading Finished
*Jul 15 12:08:51.424: BGP: topo international:IPv4 Unicast:base Remove_fwdroute for 10.0.0.3/32
*Jul 15 12:08:51.424: BGP(0): (base) 10.1.0.2 ship UPDATE (format) 10.0.0.3/32, subsequent 10.1.0.1, metric 10, path Native
*Jul 15 12:08:51.475: BGP(0): 10.1.0.2 rcv UPDATE about 10.0.0.3/32 -- DENIED because of: AS-PATH comprises our personal AS;
As you possibly can see, it takes roughly three seconds from the OSPF adjacency institution to the BGP UPDATE message.
What about IPv6? Listed below are the same printouts for R1 IPv6 loopback:
*Jul 15 12:08:51.473: [OSPFv3R-1/6/0]IPv6RT[default]: ospf 1, Replace 2001:DB8:1:3::/64 [110/10], 1 paths (legitimate:1 invalid:0) tag 0 common paths: Sure
*Jul 15 12:08:51.473: [OSPFv3R-1/6/0]IPv6RT[default]: ospf 1, Route add 2001:DB8:1:3::/64 [new 110/10]
*Jul 15 12:08:51.473: [OSPFv3R-1/6/0]IPv6RT[default]: ospf 1, RIB change occasion queued 2001:DB8:1:3::/64 'ospf' , code:0x1 nh_count:1 distance:110 metric:10 flags:0x0 tag:0
*Jul 15 12:08:51.473: [IPv6 RIB Event Handler]IPv6RT[default]: Occasion: 2001:DB8:1:3::/64, Add, proprietor ospf, earlier None
*Jul 15 12:08:51.473: BGP(1): redist occasion (1) request for 2001:DB8:1:3::/64
*Jul 15 12:08:51.473: BGP(1) route 2001:DB8:1:3::/64 nh-1 FE80::A8C1:ABFF:FE05:56EB src_proto (ospf) path-limit 1
*Jul 15 12:08:51.473: BGP(1): sourced route for 2001:DB8:1:3::/64 created
*Jul 15 12:08:51.473: BGP(1): sourced route for 2001:DB8:1:3::/64 path 0x7FD4B09182A0 id 0 nh FE80::A8C1:ABFF:FE05:56EB created (weight 32768)
*Jul 15 12:08:51.473: BGP(1): redistributed route 2001:DB8:1:3::/64 modified added-nh FE80::A8C1:ABFF:FE05:56EB
*Jul 15 12:08:51.473: BGP(1): 2001:DB8:1:3::/64 route sourced domestically
*Jul 15 12:08:51.473: BGP: topo international:IPv6 Unicast:base Remove_fwdroute for 2001:DB8:1:3::/64
*Jul 15 12:08:51.473: [BGP Router]IPv6RT[default]: bgp 65000, Delete request for route 2001:DB8:1:3::/64 from 'bgp'(0x0) metric:10 distance:110 tag:0 paths:1 route-type:0x2
*Jul 15 12:08:51.473: BGP(1): (base) 2001:DB8:3::2 ship UPDATE (format) 2001:DB8:1:3::/64, subsequent 2001:DB8:3::1, metric 10, path Native
*Jul 15 12:08:51.475: BGP(1): 2001:DB8:3::2 rcv UPDATE about 2001:DB8:1:3::/64 -- DENIED because of: AS-PATH comprises our personal AS;
*Jul 15 12:09:43.223: BGP(1): redistributed route 2001:DB8:1:3::/64 modified rib-nh FE80::A8C1:ABFF:FE05:56EB path-nh FE80::A8C1:ABFF:FE05:56EB [0x7FD4B09182A0:0]
IPv6 debugging is far more verbose than IPv4 debugging (however hey, it has 4 instances as many bits in its addresses), however the gist is identical: it takes milliseconds to redistribute OSPFv3 routes into BGP IPv6 AF and ship the BGP replace message.
Now let’s add the static routes to the combination. DUT has two static routes (10.0.0.42/32 and 2001:DB8:42::42/128). They’re configured and redistributed utilizing these configuration instructions:
ip route 10.0.0.42 255.255.255.255 Ethernet0/2 10.1.0.6
ipv6 route 2001:DB8:42::42/128 Ethernet0/2 2001:DB8:3:1::2
!
router bgp 65000
bgp nopeerup-delay cold-boot 1
bgp nopeerup-delay user-initiated 1
bgp update-delay 5
!
address-family ipv4
bgp scan-time 5
redistribute static
!
address-family ipv6
redistribute static
bgp scan-time 5
The IPv4 static route works as anticipated:
- It’s redistributed into BGP
- It’s marketed to the BGP neighbors as quickly because the BGP session is up:
*Jul 15 12:24:40.392: RT: updating static 10.0.0.42/32 (0x0) omp-tag:0 :
*Jul 15 12:24:40.392: RT: add 10.0.0.42/32 by way of 10.1.0.6, static metric [1/0]
*Jul 15 12:24:47.805: BGP(0): sourced route for 10.0.0.42/32 created
*Jul 15 12:24:47.805: bgp_ipv4set_origin: redist 1, opaque 0x0, internet 10.0.0.42
*Jul 15 12:24:47.805: ndb_get_local_label_info: SR native label data for prefix 10.0.0.42/32 is just not owned by the proprietor of the route (ndb-pdb-index:1 label-pdb-index:0)
*Jul 15 12:24:47.805: BGP(0): sourced route for 10.0.0.42/32 path 0x7F8BC2E693D8 id 0 gw 10.1.0.6 created (weight 32768)
*Jul 15 12:24:47.805: BGP(0): redistributed route 10.0.0.42/32 added gw 10.1.0.6
*Jul 15 12:24:51.721: %BGP-5-ADJCHANGE: neighbor 10.1.0.2 Up
*Jul 15 12:24:55.081: BGP: topo international:IPv4 Unicast:base Remove_fwdroute for 10.0.0.42/32
*Jul 15 12:24:55.082: BGP(0): (base) 10.1.0.2 ship UPDATE (format) 10.0.0.42/32, subsequent 10.1.0.1, metric 0, path Native
*Jul 15 12:24:55.133: BGP(0): 10.1.0.2 rcv UPDATE about 10.0.0.42/32 -- DENIED because of: AS-PATH comprises our personal AS;
Nevertheless, the BGP course of ignores the IPv6 static route for nearly a minute whereas it fortunately redistributes the OSPFv3 routes.
*Jul 15 12:24:40.642: [SSH Process]IPv6RT[default]: static, Replace 2001:DB8:42::42/128 [1/0], 1 paths (legitimate:1 invalid:0) tag 0 common paths: Sure
*Jul 15 12:24:40.642: [SSH Process]IPv6RT[default]: static, Route add 2001:DB8:42::42/128 [new 1/0]
*Jul 15 12:24:40.642: [SSH Process]IPv6RT[default]: static, RIB change occasion queued 2001:DB8:42::42/128 'static' , code:0x1 nh_count:1 distance:1 metric:0 flags:0x0 tag:0
*Jul 15 12:24:40.642: [IPv6 RIB Event Handler]IPv6RT[default]: Occasion: 2001:DB8:42::42/128, Add, proprietor static, earlier None
*Jul 15 12:24:51.722: %BGP-5-ADJCHANGE: neighbor 2001:DB8:3::2 Up
*Jul 15 12:25:46.879: BGP(1): sourced route for 2001:DB8:42::42/128 created
*Jul 15 12:25:46.879: BGP(1): sourced route for 2001:DB8:42::42/128 path 0x7F8BC2EE7260 id 0 nh 2001:DB8:3:1::2 created (weight 32768)
*Jul 15 12:25:46.879: BGP(1): redistributed route 2001:DB8:42::42/128 modified added-nh 2001:DB8:3:1::2
*Jul 15 12:25:46.894: BGP(1): 2001:DB8:42::42/128 route sourced domestically
*Jul 15 12:25:46.894: BGP: topo international:IPv6 Unicast:base Remove_fwdroute for 2001:DB8:42::42/128
*Jul 15 12:25:46.894: [BGP Router]IPv6RT[default]: bgp 65000, Delete request for route 2001:DB8:42::42/128 from 'bgp'(0x0) metric:0 distance:1 tag:0 paths:1 route-type:0x0
*Jul 15 12:25:46.895: BGP(1): (base) 2001:DB8:3::2 ship UPDATE (format) 2001:DB8:42::42/128, subsequent 2001:DB8:3::1, metric 0, path Native
*Jul 15 12:25:46.945: BGP(1): 2001:DB8:3::2 rcv UPDATE about 2001:DB8:42::42/128 -- DENIED because of: AS-PATH comprises our personal AS;
Making an attempt to determine what’s taking place, I added debug bgp * all import occasions and debug bgp * all occasions to the combination. Right here’s what occurs on the 1-minute mark:
*Jul 15 12:37:52.804: BGP(1): redistributed route 2001:DB8:1:3::1/128 modified rib-nh FE80::A8C1:ABFF:FE93:3614 path-nh FE80::A8C1:ABFF:FE93:3614 [0x7FD225EE9778:0]
*Jul 15 12:37:52.804: BGP(1): redistributed route 2001:DB8:1:3::/64 modified rib-nh FE80::A8C1:ABFF:FE93:3614 path-nh FE80::A8C1:ABFF:FE93:3614 [0x7FD225EE96D0:0]
*Jul 15 12:37:52.804: BGP(1): redistributed route 2001:DB8:3:1::2/128 modified rib-nh FE80::A8C1:ABFF:FE93:3614 path-nh FE80::A8C1:ABFF:FE93:3614 [0x7FD225EE9820:0]
*Jul 15 12:37:52.804: BGP(1): sourced route for 2001:DB8:42::42/128 created
*Jul 15 12:37:52.804: BGP(1): sourced route for 2001:DB8:42::42/128 path 0x7FD225EE9628 id 0 nh 2001:DB8:3:1::2 created (weight 32768)
*Jul 15 12:37:52.804: BGP(1): redistributed route 2001:DB8:42::42/128 modified added-nh 2001:DB8:3:1::2
*Jul 15 12:37:52.804: BGP(1): native route 2001:DB8:1:1::/64 modified rib-nh :: path-nh :: [0x7FD225EE9970:0]
*Jul 15 12:37:52.804: BGP: tbl IPv6 Unicast:base Performing BGP Nexthop scanning for basic scan
*Jul 15 12:37:52.804: BGP(1): Future scanner model: 2, present scanner model: 1
*Jul 15 12:37:52.804: BGP: tbl IPv6 Unicast:base IMP Preliminary export full.
*Jul 15 12:37:52.819: BGP(1): 2001:DB8:42::42/128 route sourced domestically
*Jul 15 12:37:52.819: BGP: topo international:IPv6 Unicast:base Remove_fwdroute for 2001:DB8:42::42/128
*Jul 15 12:37:52.819: [BGP Router]IPv6RT[default]: bgp 65000, Delete request for route 2001:DB8:42::42/128 from 'bgp'(0x0) metric:0 distance:1 tag:0 paths:1 route-type:0x0
*Jul 15 12:37:52.819: BGP(1): (base) 2001:DB8:3::2 ship UPDATE (format) 2001:DB8:42::42/128, subsequent 2001:DB8:3::1, metric 0, path Native
In the event you occur to know what the above phrase salad means, please write a remark. In any other case, we’ll be left with the thriller of Cisco IOS/XE hating redistributed IPv6 static routes a lot that it procrastinates for a minute earlier than it begins dealing with them.
Writing assessments that examine the correctness of community system configurations is tough (overview, extra particulars). It’s additionally an fascinating train in getting the timing good:
- Routing protocols are an eventually-consistent distributed system, and issues finally seem in the correct place (should you bought the configurations proper), however you by no means know when precisely that may occur.
- You possibly can subsequently set some affordable higher bounds on when issues ought to occur, and declare failure if the timeouts are exceeded. Even then, you’ll get false positives (as in: the check is telling you the configurations are incorrect, when it’s only a system having a nasty hair day).
And simply whenever you suppose you nailed it, you encounter a tool that blows your assumptions out of the water.
The check was purported to be easy: examine whether or not the route redistribution into BGP works. The preliminary lab topology had a tool beneath check (DUT) that redistributed OSPF into BGP, an OSPF-speaking router (R2), and a BGP-speaking router (X1). The validation assessments fastidiously progressed down the joyful path:
- Do we’ve got IPv4 and IPv6 EBGP classes between X1 and DUT?
- Do we’ve got OSPFv2 and OSPFv3 classes between R2 and DUT?
- Can we see an OSPFv2 prefix marketed by R2 within the IPv4 BGP desk on X1 (and likewise for IPv6)?
It labored on all of the gadgets we examined, after which we added the static routes on the DUT to the combination. Not a giant deal, proper? Simply add one other check to examine whether or not the static routes are propagated into BGP. The timing doesn’t matter, proper? In spite of everything, if a router manages to redistribute OSPF routes into BGP, it shouldn’t have any drawback redistributing its static routes into BGP on the identical time.
And at that time, I entered a bizarre parallel universe of Cisco IOS/XE. Let’s begin with the OSPF-to-BGP redistribution state of affairs. Listed below are the IPv4 debugging printouts (generated with debug ip routing and debug bgp all updates) for 10.0.0.3/32 (the loopback interface of R1):
*Jul 15 12:08:48.766: %OSPF-5-ADJCHG: Course of 1, Nbr 10.0.0.3 on Ethernet0/2 from LOADING to FULL, Loading Finished
*Jul 15 12:08:51.223: %OSPFv3-5-ADJCHG: Course of 1, IPv6, Nbr 10.0.0.3 on Ethernet0/2 from LOADING to FULL, Loading Finished
*Jul 15 12:08:51.424: BGP: topo international:IPv4 Unicast:base Remove_fwdroute for 10.0.0.3/32
*Jul 15 12:08:51.424: BGP(0): (base) 10.1.0.2 ship UPDATE (format) 10.0.0.3/32, subsequent 10.1.0.1, metric 10, path Native
*Jul 15 12:08:51.475: BGP(0): 10.1.0.2 rcv UPDATE about 10.0.0.3/32 -- DENIED because of: AS-PATH comprises our personal AS;
As you possibly can see, it takes roughly three seconds from the OSPF adjacency institution to the BGP UPDATE message.
What about IPv6? Listed below are the same printouts for R1 IPv6 loopback:
*Jul 15 12:08:51.473: [OSPFv3R-1/6/0]IPv6RT[default]: ospf 1, Replace 2001:DB8:1:3::/64 [110/10], 1 paths (legitimate:1 invalid:0) tag 0 common paths: Sure
*Jul 15 12:08:51.473: [OSPFv3R-1/6/0]IPv6RT[default]: ospf 1, Route add 2001:DB8:1:3::/64 [new 110/10]
*Jul 15 12:08:51.473: [OSPFv3R-1/6/0]IPv6RT[default]: ospf 1, RIB change occasion queued 2001:DB8:1:3::/64 'ospf' , code:0x1 nh_count:1 distance:110 metric:10 flags:0x0 tag:0
*Jul 15 12:08:51.473: [IPv6 RIB Event Handler]IPv6RT[default]: Occasion: 2001:DB8:1:3::/64, Add, proprietor ospf, earlier None
*Jul 15 12:08:51.473: BGP(1): redist occasion (1) request for 2001:DB8:1:3::/64
*Jul 15 12:08:51.473: BGP(1) route 2001:DB8:1:3::/64 nh-1 FE80::A8C1:ABFF:FE05:56EB src_proto (ospf) path-limit 1
*Jul 15 12:08:51.473: BGP(1): sourced route for 2001:DB8:1:3::/64 created
*Jul 15 12:08:51.473: BGP(1): sourced route for 2001:DB8:1:3::/64 path 0x7FD4B09182A0 id 0 nh FE80::A8C1:ABFF:FE05:56EB created (weight 32768)
*Jul 15 12:08:51.473: BGP(1): redistributed route 2001:DB8:1:3::/64 modified added-nh FE80::A8C1:ABFF:FE05:56EB
*Jul 15 12:08:51.473: BGP(1): 2001:DB8:1:3::/64 route sourced domestically
*Jul 15 12:08:51.473: BGP: topo international:IPv6 Unicast:base Remove_fwdroute for 2001:DB8:1:3::/64
*Jul 15 12:08:51.473: [BGP Router]IPv6RT[default]: bgp 65000, Delete request for route 2001:DB8:1:3::/64 from 'bgp'(0x0) metric:10 distance:110 tag:0 paths:1 route-type:0x2
*Jul 15 12:08:51.473: BGP(1): (base) 2001:DB8:3::2 ship UPDATE (format) 2001:DB8:1:3::/64, subsequent 2001:DB8:3::1, metric 10, path Native
*Jul 15 12:08:51.475: BGP(1): 2001:DB8:3::2 rcv UPDATE about 2001:DB8:1:3::/64 -- DENIED because of: AS-PATH comprises our personal AS;
*Jul 15 12:09:43.223: BGP(1): redistributed route 2001:DB8:1:3::/64 modified rib-nh FE80::A8C1:ABFF:FE05:56EB path-nh FE80::A8C1:ABFF:FE05:56EB [0x7FD4B09182A0:0]
IPv6 debugging is far more verbose than IPv4 debugging (however hey, it has 4 instances as many bits in its addresses), however the gist is identical: it takes milliseconds to redistribute OSPFv3 routes into BGP IPv6 AF and ship the BGP replace message.
Now let’s add the static routes to the combination. DUT has two static routes (10.0.0.42/32 and 2001:DB8:42::42/128). They’re configured and redistributed utilizing these configuration instructions:
ip route 10.0.0.42 255.255.255.255 Ethernet0/2 10.1.0.6
ipv6 route 2001:DB8:42::42/128 Ethernet0/2 2001:DB8:3:1::2
!
router bgp 65000
bgp nopeerup-delay cold-boot 1
bgp nopeerup-delay user-initiated 1
bgp update-delay 5
!
address-family ipv4
bgp scan-time 5
redistribute static
!
address-family ipv6
redistribute static
bgp scan-time 5
The IPv4 static route works as anticipated:
- It’s redistributed into BGP
- It’s marketed to the BGP neighbors as quickly because the BGP session is up:
*Jul 15 12:24:40.392: RT: updating static 10.0.0.42/32 (0x0) omp-tag:0 :
*Jul 15 12:24:40.392: RT: add 10.0.0.42/32 by way of 10.1.0.6, static metric [1/0]
*Jul 15 12:24:47.805: BGP(0): sourced route for 10.0.0.42/32 created
*Jul 15 12:24:47.805: bgp_ipv4set_origin: redist 1, opaque 0x0, internet 10.0.0.42
*Jul 15 12:24:47.805: ndb_get_local_label_info: SR native label data for prefix 10.0.0.42/32 is just not owned by the proprietor of the route (ndb-pdb-index:1 label-pdb-index:0)
*Jul 15 12:24:47.805: BGP(0): sourced route for 10.0.0.42/32 path 0x7F8BC2E693D8 id 0 gw 10.1.0.6 created (weight 32768)
*Jul 15 12:24:47.805: BGP(0): redistributed route 10.0.0.42/32 added gw 10.1.0.6
*Jul 15 12:24:51.721: %BGP-5-ADJCHANGE: neighbor 10.1.0.2 Up
*Jul 15 12:24:55.081: BGP: topo international:IPv4 Unicast:base Remove_fwdroute for 10.0.0.42/32
*Jul 15 12:24:55.082: BGP(0): (base) 10.1.0.2 ship UPDATE (format) 10.0.0.42/32, subsequent 10.1.0.1, metric 0, path Native
*Jul 15 12:24:55.133: BGP(0): 10.1.0.2 rcv UPDATE about 10.0.0.42/32 -- DENIED because of: AS-PATH comprises our personal AS;
Nevertheless, the BGP course of ignores the IPv6 static route for nearly a minute whereas it fortunately redistributes the OSPFv3 routes.
*Jul 15 12:24:40.642: [SSH Process]IPv6RT[default]: static, Replace 2001:DB8:42::42/128 [1/0], 1 paths (legitimate:1 invalid:0) tag 0 common paths: Sure
*Jul 15 12:24:40.642: [SSH Process]IPv6RT[default]: static, Route add 2001:DB8:42::42/128 [new 1/0]
*Jul 15 12:24:40.642: [SSH Process]IPv6RT[default]: static, RIB change occasion queued 2001:DB8:42::42/128 'static' , code:0x1 nh_count:1 distance:1 metric:0 flags:0x0 tag:0
*Jul 15 12:24:40.642: [IPv6 RIB Event Handler]IPv6RT[default]: Occasion: 2001:DB8:42::42/128, Add, proprietor static, earlier None
*Jul 15 12:24:51.722: %BGP-5-ADJCHANGE: neighbor 2001:DB8:3::2 Up
*Jul 15 12:25:46.879: BGP(1): sourced route for 2001:DB8:42::42/128 created
*Jul 15 12:25:46.879: BGP(1): sourced route for 2001:DB8:42::42/128 path 0x7F8BC2EE7260 id 0 nh 2001:DB8:3:1::2 created (weight 32768)
*Jul 15 12:25:46.879: BGP(1): redistributed route 2001:DB8:42::42/128 modified added-nh 2001:DB8:3:1::2
*Jul 15 12:25:46.894: BGP(1): 2001:DB8:42::42/128 route sourced domestically
*Jul 15 12:25:46.894: BGP: topo international:IPv6 Unicast:base Remove_fwdroute for 2001:DB8:42::42/128
*Jul 15 12:25:46.894: [BGP Router]IPv6RT[default]: bgp 65000, Delete request for route 2001:DB8:42::42/128 from 'bgp'(0x0) metric:0 distance:1 tag:0 paths:1 route-type:0x0
*Jul 15 12:25:46.895: BGP(1): (base) 2001:DB8:3::2 ship UPDATE (format) 2001:DB8:42::42/128, subsequent 2001:DB8:3::1, metric 0, path Native
*Jul 15 12:25:46.945: BGP(1): 2001:DB8:3::2 rcv UPDATE about 2001:DB8:42::42/128 -- DENIED because of: AS-PATH comprises our personal AS;
Making an attempt to determine what’s taking place, I added debug bgp * all import occasions and debug bgp * all occasions to the combination. Right here’s what occurs on the 1-minute mark:
*Jul 15 12:37:52.804: BGP(1): redistributed route 2001:DB8:1:3::1/128 modified rib-nh FE80::A8C1:ABFF:FE93:3614 path-nh FE80::A8C1:ABFF:FE93:3614 [0x7FD225EE9778:0]
*Jul 15 12:37:52.804: BGP(1): redistributed route 2001:DB8:1:3::/64 modified rib-nh FE80::A8C1:ABFF:FE93:3614 path-nh FE80::A8C1:ABFF:FE93:3614 [0x7FD225EE96D0:0]
*Jul 15 12:37:52.804: BGP(1): redistributed route 2001:DB8:3:1::2/128 modified rib-nh FE80::A8C1:ABFF:FE93:3614 path-nh FE80::A8C1:ABFF:FE93:3614 [0x7FD225EE9820:0]
*Jul 15 12:37:52.804: BGP(1): sourced route for 2001:DB8:42::42/128 created
*Jul 15 12:37:52.804: BGP(1): sourced route for 2001:DB8:42::42/128 path 0x7FD225EE9628 id 0 nh 2001:DB8:3:1::2 created (weight 32768)
*Jul 15 12:37:52.804: BGP(1): redistributed route 2001:DB8:42::42/128 modified added-nh 2001:DB8:3:1::2
*Jul 15 12:37:52.804: BGP(1): native route 2001:DB8:1:1::/64 modified rib-nh :: path-nh :: [0x7FD225EE9970:0]
*Jul 15 12:37:52.804: BGP: tbl IPv6 Unicast:base Performing BGP Nexthop scanning for basic scan
*Jul 15 12:37:52.804: BGP(1): Future scanner model: 2, present scanner model: 1
*Jul 15 12:37:52.804: BGP: tbl IPv6 Unicast:base IMP Preliminary export full.
*Jul 15 12:37:52.819: BGP(1): 2001:DB8:42::42/128 route sourced domestically
*Jul 15 12:37:52.819: BGP: topo international:IPv6 Unicast:base Remove_fwdroute for 2001:DB8:42::42/128
*Jul 15 12:37:52.819: [BGP Router]IPv6RT[default]: bgp 65000, Delete request for route 2001:DB8:42::42/128 from 'bgp'(0x0) metric:0 distance:1 tag:0 paths:1 route-type:0x0
*Jul 15 12:37:52.819: BGP(1): (base) 2001:DB8:3::2 ship UPDATE (format) 2001:DB8:42::42/128, subsequent 2001:DB8:3::1, metric 0, path Native
In the event you occur to know what the above phrase salad means, please write a remark. In any other case, we’ll be left with the thriller of Cisco IOS/XE hating redistributed IPv6 static routes a lot that it procrastinates for a minute earlier than it begins dealing with them.
