Re: DS3/E3-MIB

David Fowler <davef@newbridge.com> Wed, 04 March 1998 16:23 UTC

Delivery-Date: Wed, 04 Mar 1998 11:23:33 -0500
Return-Path: davef@ca.newbridge.com
Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id LAA10044 for <ietf-archive@ietf.org>; Wed, 4 Mar 1998 11:23:32 -0500 (EST)
Received: from trix.cisco.com (trix-hme0.cisco.com [171.69.63.45]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id LAA13230 for <ietf-archive@cnri.reston.va.us>; Wed, 4 Mar 1998 11:26:09 -0500 (EST)
Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by trix.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id IAA27352 for <extdom.trunk-mib@aliashost.cisco.com>; Wed, 4 Mar 1998 08:18:05 -0800 (PST)
Received: from proxy1.cisco.com (proxy1.cisco.com [192.31.7.88]) by hubbub.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id IAA18874 for <trunk-mib@external.cisco.com>; Wed, 4 Mar 1998 08:18:05 -0800 (PST)
Received: (from smap@localhost) by proxy1.cisco.com (8.8.7/8.8.5) id IAA04048 for <trunk-mib@external.cisco.com>; Wed, 4 Mar 1998 08:18:04 -0800 (PST)
Received: from ns.newbridge.com(192.75.23.67) by proxy1.cisco.com via smap (V2.0) id xma004042; Wed, 4 Mar 98 16:18:01 GMT
Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id LAA01378 for <trunk-mib@external.cisco.com>; Wed, 4 Mar 1998 11:14:13 -0500 (EST)
Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma001191; Wed Mar 4 11:12:20 1998
Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 4 Mar 1998 16:12:20 UT
Received: (from smap@localhost) by ca.newbridge.com. (8.8.6/8.8.6) id LAA01865; Wed, 4 Mar 1998 11:12:19 -0500 (EST)
Received: from thor.ca.newbridge.com(138.120.100.14) by kanmaster.ca.newbridge.com via smap (V1.3) id sma001720; Wed Mar 4 11:11:46 1998
Received: from newbridge.com (macdavef [138.120.55.103]) by thor.ca.newbridge.com (8.6.12/8.6.12) with ESMTP id LAA27528; Wed, 4 Mar 1998 11:11:44 -0500
Message-ID: <34FD701A.D36C115@newbridge.com>
Date: Wed, 04 Mar 1998 11:16:01 -0400
From: David Fowler <davef@newbridge.com>
X-Mailer: Mozilla 4.04 (Macintosh; I; PPC)
MIME-Version: 1.0
To: Bernhard.Staudacher@oen.siemens.de
CC: trunk-mib@external.cisco.com
Subject: Re: DS3/E3-MIB
References: <0000txhphtlf.0000lzvtlfvx@oen.siemens.de>
Content-Type: text/plain; charset="us-ascii"; x-mac-type="54455854"; x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit

Bernhard

The latest version of the ds3 MIB (08), is currently in IETF last call.  What
I recommend is that you use the standard MIB for the objects that are there
and a proprietary MIB for additional objects.

Regards,
David

Bernhard.Staudacher@oen.siemens.de wrote:

> Hello,
>
> at the moment we are developing an ATM-switch that uses DS3/E3 as physical
> layer. It will be managed using SNMP and the appropriate MIBs (for the
> physical layer: draft-ietf-trunkmib-ds3-mib-07). But there are some
> problems with this MIB and the E3-standard:
>
> On the one hand, the ATM forum requests that performance monitoring shall
> be done according to ITU G.826.
> On the other hand, the DS3-MIB is based on ANSI T1.231 and does not provide
> all objects for E3-performance monitoring (e.g. SES).
>
> Of course, we don't want to generate our own solution, if there is any
> (quasi-) standard. So my question is:
> Do we have to define our own private MIB, or are there any other solutions
> (e.g. ignore the ATMF-requirement, redefine MIB-objects) ?
>
> Best regards
>         Bernhard Staudacher



David Fowler
Newbridge Networks
613-591-3600