Hi Jason, Leigh, Adam & Aivars. These are serious issues. From the thread it seems 15.3(2)S has multiple issues, VRF ping, IPv6 enable causes L3VPN issue & management issues. Any other issues seen with 15.3(2)S? Jason, you mentioned that you have seen similar issues with other releases, can you please list them? If I can get a list of issues faced in 15.3(2)S or other releases, it will help me to get them fixed soon. Please send me all the details and I would have them fixed ASAP.
Best Regards, [http://www.cisco.com/web/europe/images/email/signature/horizontal06.jpg] Waris Sagheer Technical Marketing Manager Service Provider Access Group wa...@cisco.com<mailto:wa...@cisco.com> Phone: +1 408 853 6682 Mobile: +1 408 835 1389 CCIE - 19901 <http://www.cisco.com/> [Think before you print.] Think before you print. This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/index.html From: Jason Lixfeld <ja...@lixfeld.ca<mailto:ja...@lixfeld.ca>> Date: Friday, May 10, 2013 3:54 PM To: Leigh Harrison <lharri...@convergencegroup.co.uk<mailto:lharri...@convergencegroup.co.uk>> Cc: "cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net>" <cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net>> Subject: Re: [c-nsp] ME3600x L3VPN MPLS problems with 15.3.2S Interesting. 15.1(2)EY1a doesn't support IPv6, so it's doubtful that unless you made any configuration changes at the time of the upgrade to support IPv6, the triggers reported by Adam and Aivars aren't consistent with whatever triggered your issues. In fact, I'm not 100% sure yet whether they are consistent with whatever triggered mine either. If you are willing to share your config and topology, I'll pass it off to my SE who is the acting as the funnel for the dev team handling this issue (and a few others as well). BTW: There are some pretty high level Cisco folks watching this thread, so anyone else who has been having issues along these lines, I encourage you to chime in. Any info you can share offline with me will make it's way upstream in kind. On 2013-05-10, at 5:04 PM, Leigh Harrison <lharri...@convergencegroup.co.uk<mailto:lharri...@convergencegroup.co.uk>> wrote: Evening all, We went to upgrade our estate to 15.3(2) last weekend, but after the first upgrade, we hit the same issue with being up able to ping directly connected CPE . Unable to get the management back up on the CPE, we rolled the change back out, reverting to 15.1(2)EY1a and all of our management issues vanished. Leigh -----Original Message----- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Adam Vitkovsky Sent: 10 May 2013 13:07 To: 'Jason Lixfeld' Cc: 'cisco-nsp' Subject: Re: [c-nsp] ME3600x L3VPN MPLS problems with 15.3.2S I was just playing with this further and it appears that as soon as I configure ipv6 address or "ipv6 enable" the interface gets stuck and removing ipv6 won't help. The only cure is to remove the ipv6 address/ipv6 enable and shut and no shut the interface than the ping starts to work again. I don't understand why just ping doesn't work as BGP is not affected by this. I have this in the lab so I can send you the complete configs offline. adam -----Original Message----- From: Jason Lixfeld [mailto:ja...@lixfeld.ca] Sent: Friday, May 10, 2013 1:46 PM To: Adam Vitkovsky Cc: Aivars; cisco-nsp Subject: Re: [c-nsp] ME3600x L3VPN MPLS problems with 15.3.2S I have seen this on a bunch of different ME3600s across my network from 15.2 all the way up to and including 15.3. I haven't actually been able to readily duplicate this, so I'm very intrigued that you both are able to replicate it, seemingly at will. I actually have a call scheduled at 11am with a fleet of Dev engineers from India and SJ. I will be bringing this up with them, because this is one of our big mystery issues that we can't replicate but have seen multiple times. Can either of you share a *complete* device config? (Passwords, SNMP comma and IPs sanitized, if required). I'd be grateful and hopefully with your help we'll be able to put a bugid to this issue. Thanks. -- Sent from my mobile device On 2013-05-10, at 7:26 AM, Adam Vitkovsky <adam.vitkov...@swan.sk<mailto:adam.vitkov...@swan.sk>> wrote: Just ran into a similar problem with 15.2(4)S2 and 15.3(1)S -can't even ping the other end of the link -funny is that bgp session works on the CE-PE ip addresses. So routing vise everything works just fine I just can't pass any data. However this problem started only when I enabled ipv6 in addition to the ipv4 setup. Debug ip packets for the CE to PE ping shows that the PE got the icmp and replied back. Though the ACL in OUT direction on the PE side did not catch any outgoing icmp traffic and neither the CE received any. adam -----Original Message----- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Aivars Sent: Friday, May 10, 2013 10:39 AM To: cisco-nsp Subject: [c-nsp] ME3600x L3VPN MPLS problems with 15.3.2S I tried to deploy Me3600x as MPLS PE with IOS 15.3.2S and failed. It is a straight forward MPLS L3VPN configuration with OSPF in the core and static routes between PE - CE. With 15.3 I was not able to ping even a directly connected CE IP from another PE (7600) in the network. I was able however ping IP on ME3600 from the same PE - CE subnet. All routes and labels seem to be fine on both PEs and P as well. I was able however ping IP on ME3600 from the same PE - CE subnet. The exact same configuration on the same switch works fine with 15.2S. Just saved config, rebooted with 15.2 and the ping to the CE direct IP and statically routed subnet was fine. I was able to replicate the same behavior using a test ME3600 connected to MPLS core. Has anybody seen something like this? I am not able to find any similar bug in the bug toolkit. Aivars _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ______________________________________________________________________ This email has been scanned by the Symantec Email Security Cloud System, Managed and Supported by TekNet Solutions (http://www.teknet.co.uk) ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the Symantec Email Security Cloud System, Managed and Supported by TekNet Solutions (http://www.teknet.co.uk) ______________________________________________________________________ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
