> so it seems that having an EoMPLS configuration on a "shutdown" interface > can block an unrelated EoMPLS VC on the same router, but on a different VC!
could this be due to internal vlan consumption for the attachment circuit? I've noted the ability of newly created internal vlans to block traffic and become "stuck" whilst new ones assigned around them work fine, of course, if your new stuck intvlan is on a port and you move this port, you can end up moving the stuck intvlan with it! the last time I came across this it was with IP traffic and was down to a misprogrammed internal ACL being applied (remote command switch show tcam interface vlan XX acl in ip), could be related, just a thought... Dave. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
