[[nsp] more confused routing]
jlewis at lewis.org
jlewis at lewis.org
Fri Oct 24 22:38:24 EDT 2003
On Fri, 24 Oct 2003, joshua sahala wrote:
> > 2 orldflma-br-2-s2-1.atlantic.net (69.28.66.17) [MPLS: Label 208 Exp
> > 0] 24 msec
> > 3 andc-br-2.atlantic.net (69.28.68.3) 88 msec
> > 4 orldflma-br-2.atlantic.net (69.28.68.8) [MPLS: Label 1235 Exp 0] 24
>
> my mpls skills are rudimentary, but the first time it hits orldflma-br
> there is a different mpls label than the second time, so perhaps the
> first time it receives it, mpls tells it to go the other way (see if
> the interfaces are configured similarly for 69.28.66.17 & 69.28.66.8)
That's something I've noticed for a while, but generally haven't lost
sleep over since it didn't seem to break anything. I'm not sure why these
packets are getting MPLS tagged at all. They're not to/from/inside a vrf.
Can the MPLS tag on a packet influence routing decisions for packets that
are not part of a MPLS VPN vrf?
----------------------------------------------------------------------
Jon Lewis *jlewis at lewis.org*| I route
Senior Network Engineer | therefore you are
Atlantic Net |
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
More information about the cisco-nsp
mailing list