Re: OSPF-TE link parameters
Ben Niven-Jenkins <benjamin.niven-jenkins@BT.COM> Wed, 21 August 2002 16:21 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 MAA15046 for <ospf-archive@LISTS.IETF.ORG>; Wed, 21 Aug 2002 12:21:21 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <23.006E3D35@cherry.ease.lsoft.com>; Wed, 21 Aug 2002 12:22:43 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 81315 for OSPF@DISCUSS.MICROSOFT.COM; Wed, 21 Aug 2002 12:22:43 -0400
Received: from 217.32.166.19 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Wed, 21 Aug 2002 12:22:43 -0400
Received: from cbibipnt02.HC.BT.COM ([147.149.196.178]) by relhubc01-ukbr.tcrelay.net with Microsoft SMTPSVC(5.0.2195.2966); Wed, 21 Aug 2002 17:20:51 +0100
Received: by cbibipnt02.hc.bt.com with Internet Mail Service (5.5.2654.89) id <RK8VXB1R>; Wed, 21 Aug 2002 17:22:43 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.89)
Content-Type: text/plain
X-OriginalArrivalTime: 21 Aug 2002 16:20:51.0916 (UTC) FILETIME=[B7B438C0:01C2492E]
Message-ID: <5104D4DBC598D211B5FE0000F8FE7EB216C27C25@mbtlipnt02.btlabs.bt.co.uk>
Date: Wed, 21 Aug 2002 17:17:43 +0100
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Ben Niven-Jenkins <benjamin.niven-jenkins@BT.COM>
Subject: Re: OSPF-TE link parameters
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list
Acee, Thanks for your prompt response. I will investigate the draft you mention. This might be slightly off topic for this list, but anyway: As I see it (this maybe implementation specific), the additional TE parameters have to be configured on the router and associated with an interface. These additional parameters are then advertised through OSPF. Assuming that the router is not running OSPF at all or the router is only running vanilla OSPF not OSPF-TE, but the TE parameters are still configured. Is there a MIB that can be used to extract the general TE parameters without resorting to an OSPF specific MIB. If not, assuming I would like to extract the TE parameters from routers running OSPF and ISIS, is my only alternative to have one piece of code to extract them from the OSPF MIB and another to extract them from the ISIS MIB? > -----Original Message----- > From: Acee Lindem [SMTP:acee@redback.com] > Sent: 21 August 2002 17:06 > To: Mailing List > 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)