Re: OSPF-TE link parameters
"Joyal, Daniel R (Daniel)" <joyal@LUCENT.COM> Wed, 21 August 2002 16:30 UTC
Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15285 for <ospf-archive@LISTS.IETF.ORG>; Wed, 21 Aug 2002 12:30:17 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <11.006E3C7F@cherry.ease.lsoft.com>; Wed, 21 Aug 2002 12:31:39 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 81374 for OSPF@DISCUSS.MICROSOFT.COM; Wed, 21 Aug 2002 12:31:39 -0400
Received: from 192.11.226.161 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Wed, 21 Aug 2002 12:31:39 -0400
Received: from ma8117exch001p.wins.lucent.com (h152-148-89-177.lucent.com [152.148.89.177]) by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g7LGVc904885 for <OSPF@DISCUSS.MICROSOFT.COM>; Wed, 21 Aug 2002 12:31:38 -0400 (EDT)
Received: by ma8117exch001p.inse.lucent.com with Internet Mail Service (5.5.2653.19) id <RJQYBMP0>; Wed, 21 Aug 2002 12:31:37 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Message-ID: <C77B73BC1A3ED4118C2000508BAD8A7C04A57E41@ma8117exch001u.inse.lucent.com>
Date: Wed, 21 Aug 2002 12:31:36 -0400
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: "Joyal, Daniel R (Daniel)" <joyal@LUCENT.COM>
Subject: Re: OSPF-TE link parameters
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list
Ben, Acee, Since the TE Opaque LSAs are of area scope, I think the RFC1850 MIB should work as Acee describes. The MIB update does not invent a new area LSDB table for opaque LSAs. It just specifies a textual identifier for type-10s in the existing Area LSDB table so that management systems or MIB browsers can translate the type number 10 to "type-10" for display. Type-11s go in the extLSDB table. The update does define a new LSDB table for type-9s, though, because the other two tables don't have a link/interface index component. -Dan -----Original Message----- From: Acee Lindem [mailto:acee@REDBACK.COM] Sent: Wednesday, August 21, 2002 12:06 PM To: OSPF@DISCUSS.MICROSOFT.COM Subject: Re: OSPF-TE link parameters Ben Niven-Jenkins wrote: > draft-katz-yeung-ospf-traffic describes a Link TLV that contains various TE > parameters such Resource colour & TE metric. I would like to know if there > is a current MIB that can be used to extract this information from a > router/LSR using SNMP? > > If a MIB doesn't already exist is any work being done on a MIB that will > contain this information. Ben, The update to the OSPF MIB (draft-ietf-ospf-mib-update-05.txt) supports the retrieval of opaque LSAs. An application would need to parse ospfLsdbAdvertisement to exact the TE TLVs. Has anyone implemented this MIB update? > > Thanks > Ben > > -- Acee
- OSPF-TE link parameters Ben Niven-Jenkins
- Re: OSPF-TE link parameters Acee Lindem
- Re: OSPF-TE link parameters Ben Niven-Jenkins
- Re: OSPF-TE link parameters Joyal, Daniel R (Daniel)
- Re: OSPF-TE link parameters Acee Lindem
- Re: OSPF-TE link parameters Joyal, Daniel R (Daniel)