[c-nsp] ME3600x L3VPN MPLS problems with 15.3.2S

Adam Vitkovsky adam.vitkovsky at swan.sk
Fri May 10 08:06:32 EDT 2013


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:jason at 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.vitkovsky at 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-bounces at 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 at 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 at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list