If you sniff that vlan do you see packets coming in with 0x8847 on them? If could be bogus packets with that on them and no valid label stack behind them.
Rodney On Tue, May 19, 2009 at 11:57:46AM -0400, Lobo wrote: > I've search on Cisco's website to help understand the following message > but I'm not 100% clear on how to find the network/router responsible for > generating these error messages: > > .May 19 08:39:06.235 EDT: %MPLS_PACKET-4-NOLFDSB: MPLS packet received > on non MPLS enabled interface Vlan101 L3 type 0x8847 label {586 0 0 255} > .May 19 08:39:39.175 EDT: %MPLS_PACKET-4-NOLFDSB: MPLS packet received > on non MPLS enabled interface Vlan101 L3 type 0x8847 label {587 0 0 255} > .May 19 08:40:19.392 EDT: %MPLS_PACKET-4-NOLFDSB: MPLS packet received > on non MPLS enabled interface Vlan101 L3 type 0x8847 label {587 0 0 255} > .May 19 08:41:26.413 EDT: %MPLS_PACKET-4-NOLFDSB: MPLS packet received > on non MPLS enabled interface Vlan101 L3 type 0x8847 label {587 0 0 255} > .May 19 08:42:02.225 EDT: %MPLS_PACKET-4-NOLFDSB: MPLS packet received > on non MPLS enabled interface Vlan101 L3 type 0x8847 label {586 6 1 255} > > Since it's giving multiple labels, which one should I do a "mpls > forwarding-table label" command on and will that point me to the > offending block? FYI, Vlan101 is part of our NMS network and does not > have LDP enabled on it. > > > Thanks. > > Jose > _______________________________________________ > 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/ _______________________________________________ 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/