SNMP MIB Objects
E-2
3166-A2-GB20-20
March 1999
MIB II (RFC 1213)
The objects defined by MIB II are organized into 10 different groups. The
DSU/CSU implements only those groups where the semantics of the group are
applicable to the implementation of a DSU/CSU. The MIB II object groups
supported or not supported by the 3100 Series devices are as follows:
System
Group
Supported.
Interface
Group
Supported for the network interface, the synchronous data
port, and the COM port. Interface statistics (counters) apply to
the port defined as the SNMP management link.
Address
Translation
Group
Not supported since this group is not supported in MIB II.
IP Group
Supported.
ICMP Group
Supported.
TCP Group
Supported.
UDP Group
Supported.
EGP Group
Not supported since the EGP protocol is not supported by the
DSU/CSU.
Transmission
Group
Supported on the synchronous data port using the RS-232-like
MIB. Supported on the COM port using the RS-232-like MIB.
SNMP Group
Supported.
System Group, MIB II
The System Group objects are fully supported by the DSU/CSU. The following
sections provide clarification for objects contained in the System Group where it
is not otherwise clear how the object definition in MIB II is related to the
DSU/CSU. Objects not mentioned are supported as stated in the MIB.
System Group – “sysDescr” Object (system 1)
This object provides the full name and version identification for the system
hardware and software. This object displays the following string:
[
Company Name] T1 DSU/CSU; model xxxx-xx-xxx; S/W Release: yy.yy.yy; H/W
CCA1:
zzzz-zzz; H/W CCA2: zzzz-zzz; Serial number: ssssssss.
Where:
xxxx-xx-xxx represents the full model number of the unit.
yy.yy.yy represents the software revision number of the unit.
zzzz-zzz represents the hardware revision number of the unit.
ssssssss represents the serial number of the unit.
Summary of Contents for 3166 CSU
Page 1: ...ACCULINK 3166 DSU CSU USER S GUIDE Document No 3166 A2 GB20 20 March 1999...
Page 16: ...About This Guide x 3166 A2 GB20 20 March 1999 This page intentionally left blank...
Page 20: ...Introduction 1 4 3166 A2 GB20 20 March 1999 This page intentionally left blank...
Page 68: ...SDCP Operation 3 42 3166 A2 GB20 20 March 1999 This page intentionally left blank...
Page 102: ...SDCP Menu A 2 3166 A2 GB20 20 March 1999 This page intentionally left blank...
Page 140: ...Pin Assignments D 12 3166 A2 GB20 20 March 1999 This page intentionally left blank...
Page 166: ...SNMP MIB Objects E 26 3166 A2 GB20 20 March 1999 This page intentionally left blank...
Page 192: ...Equipment List I 2 3166 A2 GB20 20 March 1999 This page intentionally left blank...