The MPLS WG Archive

["Adrian Farrel" <afarrel@movaz.com>]

Hi Fang,

L1 is tunneled through L2.

L2 is installed in the TE MIB with an ifindex using mplsTunnelIsIf and
mplsTunnelIfIndex.  This means that it can be found within the implementation as
an interface and available bandwidth can be examined just as though it was a
physical interface.

L1 shows in the LSR MIB with an outsegment that contains mplsOutSegmentIfIndex.
This is the outgoing interface for L1 and is not the physical interface - it is
the interface index of L2.

So, from L1 you can get to L2.

Adrian

----- Original Message -----
From: "Fang Hao" <fangh@research.bell-labs.com>
To: "Adrian Farrel" <afarrel@movaz.com>
Cc: <mpls@uu.net>
Sent: Friday, July 19, 2002 2:44 PM
Subject: RE: Question on MIB info for LSP tunneling


> Adrian,
>
> Thanks for your reply. But I am still missing something -
> the tunnel creation part is fine, but when I need to
> access information about L2 (the LSP tunnel), I have a problem.
> What I would need is: given LSP L1 (i.e., knowing its
> mplsTunnelIndex), I need to find out which tunnel it is
> going through, how much bandwidth is left on this tunnel L2,
> what is the ingress/egress LSR id, etc.  For those info
> I would probably need the mplsTunnelIndex for L2.
>
> If I am not misunderstanding the MIBs, this mplsTunnelIndex
> (of L2) does not appear in either interface table or
> out segment table. - any comments?
>
> Thanks,
> Fang