[c-nsp] Invalid MOI?
Bruce Pinsky
bep at whack.org
Thu Oct 26 01:26:12 EDT 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jason Koh wrote:
> Hi
>
> Would like to know what causes Invalid MOI (MPLS output information). From what I know MOI is used when there is IP over MPLS, and it includes next hop, outgoing interface and outgoing labels.
>
> Well, I keep getting Invalid MOIs in my pseudowires. However all the necessary information for label switching is already there. Anybody knows of any other factors why there is an Invalid MOI here?
>
> Here are the outputs.
>
> #sh mpls l2transport vc 700 detail
> Local interface: Se2/0 up, line protocol up, HDLC up
> Destination address: 20.20.20.1, VC ID: 700, VC status: down
> Output interface: if-?(0), imposed label stack {}
> Preferred path: not configured
> Default path: no route
> Next hop: Invalid MOI
> Create time: 00:03:10, last status change time: 00:03:06
> Signaling protocol: LDP, peer 20.20.20.1:0 up
> MPLS VC labels: local 1298, remote 16
> Group ID: local 0, remote 0
> MTU: local 1500, remote 1500
> Remote interface description:
> Sequencing: receive disabled, send disabled
> VC statistics:
> packet totals: receive 0, send 0
> byte totals: receive 0, send 0
> packet drops: receive 0, seq error 0, send 0
>
> #sh ip cef 20.20.20.1/32
> 20.20.20.1/32
> nexthop 192.168.38.4 GigabitEthernet0/1.11 label 734272
>
> sh mpls forwarding-table 20.20.20.1
>
> Local Outgoing Prefix Bytes Label Outgoing Next Hop
> Label Label or VC or Tunnel Id Switched interface
> None 734272 20.20.20.1/32 0 Gi0/1.11 192.168.38.4
>
>
Well, the next hop for that label is 192.168.38.4. What does the
reachability for that prefix look like?
- --
=========
bep
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFQEb0E1XcgMgrtyYRAkh8AJ4rR0QiKNzc5cHqtUI7yu+7wIbJEACgleRd
l5iAjn2aqO28jhb80NyP930=
=A02T
-----END PGP SIGNATURE-----
More information about the cisco-nsp
mailing list