[c-nsp] ASR9k from 6.1.4 to 6.2.3
Erik Sundberg
ESundberg at nitelusa.com
Tue May 29 15:13:48 EDT 2018
In looking at the doc's just now it said it's enabled by default, but that is not what it was doing. I had to configure it for the router to download the routes in the vpnv4 table.
This was TAC's response to my ticket.
-The reason for not seeing any routes being imported is due to the absence of CLI : “ retain route-target [all]” under BGP vpnv4 AF section.
Also here is the terminal log file about what I am talking about before and after configuring "retain route-target all" with TAC on the phone back in January.
Let me know if you have any questions
################CONFIG BEFORE
20180122_13:48:51.923 router bgp 12345
20180122_13:48:51.938 nsr
20180122_13:48:51.938 bgp router-id 1.2.3.72
20180122_13:48:51.938 bgp log neighbor changes detail
20180122_13:48:51.939 address-family ipv4 unicast
20180122_13:48:51.939 bgp dampening
20180122_13:48:51.939 bgp attribute-download
20180122_13:48:51.939 redistribute connected route-policy IPV4-BGP-REDISTRIBUTE-CONNECTED
20180122_13:48:51.939 !
20180122_13:48:51.939 address-family vpnv4 unicast
20180122_13:48:51.939 !
20180122_13:48:51.939 address-family ipv6 unicast
20180122_13:48:51.940 redistribute connected route-policy IPV6-BGP-REDISTRIBUTE-CONNECTED
20180122_13:48:51.940 !
20180122_13:48:51.940 address-family vpnv6 unicast
################ BEFORE
20180122_16:38:05.432 RP/0/RSP1/CPU0:ASR9906-6.3.1#sh bgp vpnv4 unicast summary
20180122_16:38:05.652 Mon Jan 22 16:38:05.657 CST
20180122_16:38:06.601 BGP router identifier 1.2.3.72, local AS number 12345
20180122_16:38:06.601 BGP generic scan interval 60 secs
20180122_16:38:06.602 Non-stop routing is enabled
20180122_16:38:06.602 BGP table state: Active
20180122_16:38:06.602 Table ID: 0x0 RD version: 0
20180122_16:38:06.602 BGP main routing table version 6
20180122_16:38:06.602 BGP NSR Initial initsync version 1 (Reached)
20180122_16:38:06.603 BGP NSR/ISSU Sync-Group versions 6/0
20180122_16:38:06.603 BGP scan interval 60 secs
20180122_16:38:06.603
20180122_16:38:06.603 BGP is operating in STANDALONE mode.
20180122_16:38:06.603
20180122_16:38:06.603
20180122_16:38:06.603 Process RcvTblVer bRIB/RIB LabelVer ImportVer SendTblVer StandbyVer
20180122_16:38:06.604 Speaker 6 6 6 6 6 6
20180122_16:38:06.618
20180122_16:38:06.618 Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd
20180122_16:38:06.618 1.2.3.11 0 12345 93410 934 6 0 0 15:25:27 0
20180122_16:38:06.619 1.2.3.12 0 12345 223090 194 6 0 0 01:37:37 0
20180122_16:38:06.619 1.2.3.13 0 12345 170726 893 6 0 0 14:44:30 0
20180122_16:38:06.619 1.2.3.17 0 12345 156649 904 6 0 0 14:55:24 0
20180122_16:38:06.619 1.2.3.18 0 12345 85676 903 6 0 0 14:54:29 0
20180122_16:38:06.619 1.2.3.22 0 12345 156959 909 6 0 0 14:59:59 0
20180122_16:38:06.619 1.2.3.23 0 12345 84755 909 6 0 0 15:00:04 0
20180122_16:38:06.619 1.2.3.28 0 12345 154990 885 6 0 0 14:36:15 0
20180122_16:38:06.620 1.2.3.29 0 12345 117593 885 6 0 0 14:36:17 0
20180122_16:38:06.620 1.2.3.41 0 12345 93364 894 6 0 0 14:45:08 0
20180122_16:38:06.620 1.2.3.50 0 12345 122056 897 6 0 0 14:48:37 0
20180122_16:38:06.620 1.2.3.51 0 12345 138105 897 6 0 0 14:48:38 0
20180122_16:38:06.620 1.2.3.62 0 12345 935 854 6 0 0 14:04:59 0
20180122_16:38:06.620
20180122_16:42:46.469 RP/0/RSP1/CPU0:ASR9906-6.3.1#conf t
20180122_16:42:46.667 Mon Jan 22 16:42:46.676 CST
20180122_16:42:55.470 RP/0/RSP1/CPU0:ASR9906-6.3.1(config)#router bgp 12345
20180122_16:43:04.781 RP/0/RSP1/CPU0:ASR9906-6.3.1(config-bgp)#address-family vpnv4 unicast
20180122_16:43:24.925 RP/0/RSP1/CPU0:ASR9906-6.3.1(config-bgp-af)#retain route-target all
20180122_16:43:27.791 RP/0/RSP1/CPU0:ASR9906-6.3.1(config-bgp-af)#commit
20180122_16:43:27.985 Mon Jan 22 16:43:27.997 CST
20180122_16:43:29.720 RP/0/RSP1/CPU0:ASR9906-6.3.1(config-bgp-af)#end
################ AFTER
20180122_16:52:56.607 RP/0/RSP1/CPU0:ASR9906-6.3.1#sh bgp vpnv4 unicast summary
20180122_16:52:56.806 Mon Jan 22 16:52:56.817 CST
20180122_16:52:57.854 BGP router identifier 1.2.3.72, local AS number 12345
20180122_16:52:57.854 BGP generic scan interval 60 secs
20180122_16:52:57.854 Non-stop routing is enabled
20180122_16:52:57.854 BGP table state: Active
20180122_16:52:57.854 Table ID: 0x0 RD version: 0
20180122_16:52:57.854 BGP main routing table version 35442
20180122_16:52:57.854 BGP NSR Initial initsync version 1 (Reached)
20180122_16:52:57.854 BGP NSR/ISSU Sync-Group versions 35442/0
20180122_16:52:57.856 BGP scan interval 60 secs
20180122_16:52:57.856
20180122_16:52:57.856 BGP is operating in STANDALONE mode.
20180122_16:52:57.856
20180122_16:52:57.856
20180122_16:52:57.856 Process RcvTblVer bRIB/RIB LabelVer ImportVer SendTblVer StandbyVer
20180122_16:52:57.856 Speaker 35442 35442 35442 35442 35442 35442
20180122_16:52:57.873
20180122_16:52:57.874 Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd
20180122_16:52:57.874 1.2.3.11 0 12345 94011 950 35442 0 0 15:40:18 834
20180122_16:52:57.874 1.2.3.12 0 12345 226770 210 35442 0 0 01:52:28 3748
20180122_16:52:57.874 1.2.3.13 0 12345 174317 909 35442 0 0 14:59:21 3032
20180122_16:52:57.874 1.2.3.17 0 12345 157958 920 35442 0 0 15:10:15 2596
20180122_16:52:57.875 1.2.3.18 0 12345 86544 919 35442 0 0 15:09:21 2148
20180122_16:52:57.875 1.2.3.22 0 12345 158198 925 35442 0 0 15:14:50 2603
20180122_16:52:57.875 1.2.3.23 0 12345 85426 925 35442 0 0 15:14:55 1153
20180122_16:52:57.875 1.2.3.28 0 12345 156259 901 35442 0 0 14:51:07 4272
20180122_16:52:57.876 1.2.3.29 0 12345 119006 901 35442 0 0 14:51:08 3680
20180122_16:52:57.876 1.2.3.41 0 12345 93887 910 35442 0 0 14:59:59 125
20180122_16:52:57.876 1.2.3.50 0 12345 122894 913 35442 0 0 15:03:28 980
20180122_16:52:57.876 1.2.3.51 0 12345 139575 913 35442 0 0 15:03:30 3600
20180122_16:52:57.876 1.2.3.62 0 12345 951 870 35442 0 0 14:19:50 0
-----Original Message-----
From: Ted Pelas Johansson [mailto:ted.johansson at tele2.com]
Sent: Tuesday, May 29, 2018 12:58 PM
To: Erik Sundberg <ESundberg at nitelusa.com>
Cc: James Bensley <jwbensley at gmail.com>; Cisco-nsp <cisco-nsp at puck.nether.net>
Subject: Re: [c-nsp] ASR9k from 6.1.4 to 6.2.3
Hi Erik,
That is the default of XR.
Best Regards
Ted
Sent while walking
> On 29 May 2018, at 18:53, Erik Sundberg <ESundberg at nitelusa.com> wrote:
>
> I ran into this bug going from 6.3.1 to 6.3.2.... Very simple fix by applying to smu patch files.
> https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvf01652?emailclick=CN
> Semail
>
>
>
> Not sure when this change in behavior happened, but by default BGP
> doesn't install/download/show VPNv4 routes unless the VRF is built on
> the system. You need to configure 'retain route-target all' under the
> vpnv4 address family
>
> router bgp 12345
> address-family vpnv4 unicast
> retain route-target all
>
>
>
> Currently running a new deployment on 6.3.2 (64bit) No issues so far.
>
>
>
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf
> Of James Bensley
> Sent: Tuesday, May 29, 2018 3:30 AM
> To: Cisco-nsp <cisco-nsp at puck.nether.net>
> Subject: Re: [c-nsp] ASR9k from 6.1.4 to 6.2.3
>
>> On 28 May 2018 at 19:54, George Giannousopoulos <ggiannou at gmail.com> wrote:
>> We recently upgraded without any issue.
> ...
>> Beware of some rather minor syntax changes in the BNG config
>
> Same here, we're migrating from 5.3.3 to 6.2.3.
>
> Everything seems fine for us too, we're also not doing anything crazy,
> L2/L3 VPNs, RRs, ASBRs, OSPF, LDP, MP-BGP etc. (no multicast or BNG on the boxes being tested with 6.2.3). Also same with us, a few syntax changes between our 5.3.3 templates and 6.2.3 templates so best to test in the lab first, only minor changes though. So far no issues.
>
> Cheers,
> James.
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> ________________________________
>
> CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error please notify the sender immediately by replying to this e-mail. You must destroy the original transmission and its attachments without reading or saving in any manner. Thank you.
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
******** IMPORTANT NOTICE ********
The content of this e-mail is intended for the addressee(s) only and may contain information that is confidential and/or otherwise protected from disclosure. If you are not the intended recipient, please note that any copying, distribution or any other use or dissemination of the information contained in this e-mail (and its attachments) is strictly prohibited. If you have received this e-mail in error, kindly notify the sender immediately by replying to this e-mail and delete the e-mail and any copies thereof.
Tele2 AB (publ) and its subsidiaries (“Tele2 Group”) accepts no responsibility for the consequences of any viruses, corruption or other interference transmitted by e-mail.
________________________________
CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error please notify the sender immediately by replying to this e-mail. You must destroy the original transmission and its attachments without reading or saving in any manner. Thank you.
More information about the cisco-nsp
mailing list