| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Does anyone have experiences using SNMP AM with 3COM Bridges ?
Or alternatively (based on attached description of 3COM MIB support)
can say how DECmcc works with 3COM gear ?
HW : 3COM IB/3001
SW : V3.1 SW/NB-20
3COM implements in Net Builder sw RFCs 1098, 1065 and 1066.
Only parameters described in RFCs 1065 and 1066 can be accessed
by remote host.
3COM documentation says:
The SNMP agent supports all MIB variables referenced in
RFC 1066 with the following restrictions:
o Interfaces
ifAdminStatus (ifEntry 7) is Read Only
ifOutQLen (ifEntry 21) returns the maximum value of queue length
o Address translation
atPhysAddress (atEntry 2) is the only attribute changed by a set
operation.
The other attributes are:
- atIfIndex (atEntry 1)
- atNetAddress (atEntry 3)
These other attributes may be specified as part of the VarBindList
of a SET PDU. However, if they are specified, the values must match
the existing entry; otherwise, an error is returned.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 724.1 | SNMP AM V1.0 | DANZO::CARR | Wed Feb 20 1991 12:05 | 10 | |
V1.0 of the SNMP AM supports getting and setting (where possible)
of MIB I variables. Therefore, if 3COM bridges implement
RFC's 1098 (SNMP), 1065 (SMI) and 1066 (MIB I) then they should be
"managable" using MCC and the SNMP AM.
For an object that the RFC defines as read/write but 3COM implements
otherwise, an error message to the effect "attribute not settable"
will be returned if an MCC user attempts to change it.
| |||||