DS3/E3-MIB
Bernhard.Staudacher@oen.siemens.de Wed, 04 March 1998 13:38 UTC
Delivery-Date: Wed, 04 Mar 1998 08:38:45 -0500
Return-Path: Bernhard.Staudacher@oen.siemens.de
Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id IAA01880 for <ietf-archive@ietf.org>; Wed, 4 Mar 1998 08:38:44 -0500 (EST)
From: Bernhard.Staudacher@oen.siemens.de
Received: from mailgate-rtp-1.cisco.com (mailgate-rtp-1.cisco.com [171.69.160.46]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id IAA12095 for <ietf-archive@cnri.reston.va.us>; Wed, 4 Mar 1998 08:41:20 -0500 (EST)
Received: from proxy1.cisco.com (proxy1.cisco.com [192.31.7.88]) by mailgate-rtp-1.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id IAA10008 for <trunk-mib@external.cisco.com>; Wed, 4 Mar 1998 08:32:24 -0500 (EST)
Received: (from smap@localhost) by proxy1.cisco.com (8.8.7/8.8.5) id FAA11082 for <trunk-mib@external.cisco.com>; Wed, 4 Mar 1998 05:32:23 -0800 (PST)
Received: from gorilla.mchh.siemens.de(194.138.158.18) by proxy1.cisco.com via smap (V2.0) id xma011067; Wed, 4 Mar 98 13:32:19 GMT
Received: from moody.mchh.siemens.de (moody-i.mchh.siemens.de [194.138.158.26]) by gorilla.mchh.siemens.de (8.8.7/8.8.7) with ESMTP id OAA19801 for <trunk-mib@external.cisco.com>; Wed, 4 Mar 1998 14:23:42 +0100 (MET)
Received: from DESCN122.oen.siemens.de (descn122 [180.1.155.98]) by moody.mchh.siemens.de (8.8.7/8.8.7) with SMTP id OAA00101 for <trunk-mib@external.cisco.com>; Wed, 4 Mar 1998 14:24:20 +0100 (MET)
Received: FROM DESCN122.DESCN122.oen.siemens.de BY DESCN122.oen.siemens.de ; 4 Mar 98 14:22:19 MEZ
Date: Wed, 04 Mar 1998 14:22:30 -0000
Subject: DS3/E3-MIB
To: trunk-mib@external.cisco.com
Message-ID: <0000txhphtlf.0000lzvtlfvx@oen.siemens.de>
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 ---------------------------------------------------- Bernhard Staudacher Siemens OEN SN EP C15 Tel.: +49 89 722-48881 Fax.: +49 89 722-62211 Internet: Bernhard.Staudacher@oen.siemens.de Banyan: Bernhard Staudacher@EVP35@Siemens OEVE D ---------------------------------------------------- Bernhard Staudacher Siemens OEN SN EP C15 Tel.: +49 89 722-48881 Fax.: +49 89 722-62211 Internet: Bernhard.Staudacher@oen.siemens.de Banyan: Bernhard Staudacher@EVP35@Siemens OEVE D
- DS3/E3-MIB Bernhard.Staudacher
- Re: DS3/E3-MIB David Fowler