Hi Erik,

That is the default of XR.

Best Regards
Ted

Sent while walking

> On 29 May 2018, at 18:53, Erik Sundberg <[email protected]> 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=CNSemail
>
>
>
> 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:[email protected]] On Behalf Of James 
> Bensley
> Sent: Tuesday, May 29, 2018 3:30 AM
> To: Cisco-nsp <[email protected]>
> Subject: Re: [c-nsp] ASR9k from 6.1.4 to 6.2.3
>
>> On 28 May 2018 at 19:54, George Giannousopoulos <[email protected]> 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  [email protected] 
> 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  [email protected]
> 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.
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to