Special Considerations; Mibs And Mib Objects - 3Com 3C10402B Administrator's Manual

378 C 16: N
HAPTER ETWORK
Special
Considerations
MIBs and MIB
Objects
M
ANAGEMENT
5 Edit the fields appropriately.
6 Click Apply.
Enterprise notifications use an snmpTrapOID, which consists of the 3Com
enterprise number (43), a zero, and the SNMPv1 trap number.
Make sure you understand this information as you plan to use SNMP in
your network:
The system does not back up SNMPv3 Engine ID, privacy keys, or
■
authentication.
If you restore keys, you might need to reinitialize them on both the
client and the server before they are usable. However, the system does
back up notification targets.
You must back up SNMP as a part of your general system backup
■
operations.
The system does not display Authentication and Privacy keys.
■
You cannot use the same password for the Authentication and Privacy
■
keys.
When you enable Syslog, the system logs the results of a SNMPv1,
■
SNMPv2, and SNMPv3
The SNMPv1 Read community string is logged. (SNMPv1).
■
The Security Name is logged (SNMPv2, SNMPv3).
■
The Set result codes are the enhanced SNMPv2/3 error codes.
■
Updates to the user passwords and keys are not logged.
■
This section lists the MIBs and MIB objects that the system uses as a part
of its standard operations.
MIBs Used on the System
■
Standard SNMPv3 MIBs
■
Other IEEE/RFC MIBs
■
3Com MIB Objects
■
Diagnostics for 3Com MIB Objects
■
Persistent Storage
■
operation. In this case:
set