I have an issue with an MPLS design on the 6500's new sup2t's (12.2(50)SY), in that the standby supervisor seems to be dropping VPLS traffic one way. See the diagram below;
In this topology everything else works fine, internal routing between sites, vrfs/MP-BGP all work fine - VPLS is the only thing that is affected.
We have eigrp peering between all 3 nodes advertising the loopbacks, mpls ip on the interfaces, ldp as the protocol.
The VPLS circuits are showing as being up, the ldp neighbor and route to the loopback is over the directly connected link however the standby supervisor seems to ignore VPLS traffic inbound on its port.
If i move the ports from the standby to the spare port on the active supervisor at the 3 sites the VPLS traffic is fine in all directions.
Can anyone comment on this design on wether this should work in principle and we are looking at a code/bug issue or a limitation of the architecture of the sup2t?
No answer as yet, I'm awaiting our support contract to be organized to log this with TAC, i will post an update with cisco's response when i get it, or if anyone has any thoughts on this i would love to hear from them.
1. Introduction Internet security is important with the increasing
attacks that are happening every day. Many internet and browsing
security solutions exist, but some are not very easy to use or maybe the
question is how can I enable them? In this referen...
Cisco Software Manager Server API Guide This document describes the
programmatic interfaces, RESTful APIs, which are supported by Cisco
Software Manager Server (CSM Server). Overview CSM Server supports a set
of finite RESTful APIs. The first step to use ...
If you are using Cisco's new linux-based Cisco Software Manager server,
then you probably want to make sure there is a startup service for
it.I'll assume that you've already installed the CSM server on a
systemd-based linux system. The commands given belo...