RFC1666.TXT (SNANAU MIB)
cheng@vnet.ibm.com Tue, 07 March 1995 15:24 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05636; 7 Mar 95 10:24 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa05632; 7 Mar 95 10:24 EST
Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa07199; 7 Mar 95 10:24 EST
Received: from VNET.IBM.COM (vnet.ibm.com [199.171.26.4]) by thumper.bellcore.com (8.6.9/8.6.10) with SMTP id KAA13722 for <snanaumib@thumper.bellcore.com>; Tue, 7 Mar 1995 10:17:30 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: cheng@vnet.ibm.com
Message-Id: <199503071517.KAA13722@thumper.bellcore.com>
Received: from RALVM6 by VNET.IBM.COM (IBM VM SMTP V2R2) with BSMTP id 5687; Tue, 07 Mar 95 10:17:09 EST
Date: Tue, 07 Mar 1995 10:16:23 -0500
To: snanaumib@thumper.bellcore.com
Subject: RFC1666.TXT (SNANAU MIB)
Dear SNA MIBers:
This may be late, but if it is a defect, it has to be fixed.
By using SNMCng to check some SNMPv2 MIBs,
I think I have found a defect in RFC1666 (SNANAU MIB). I suspect that
snanauMIB module does not have the proper IMPORTS statements.
In particular, I think it missed:
--
IMPORTS
mib-2
FROM RFC1213-MIB
--
I believe this is required because
snanauMIB MODULE-IDENTITY
...
::= { mib-2 34 }
Robin Cheng, IBM Networking Systems
phone: (919)254-4434
cheng@vnet.ibm.com
- RFC1666.TXT (SNANAU MIB) cheng