Configuration procedure, Configuring snmp logging, Configuring snmp traps – H3C Technologies H3C WX5500E Series Access Controllers User Manual
Page 68
60
Configuration procedure
To switch the NM-specific ifindex format:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Switch the format of an
NM-specific ifindex from
16-bit to 32-bit.
snmp-agent ifmib long-ifindex
enable
Optional.
By default, an NM-specific ifindex
is in 16-bit format.
3.
Switch the format of an
NM-specific ifindex from
32-bit to 16-bit.
undo snmp-agent ifmib
long-ifindex enable
Optional.
By default, an NM-specific ifindex
is in 16-bit format.
Configuring SNMP logging
Disable SNMP logging in normal cases to prevent a large amount of SNMP logs from decreasing device
performance.
The SNMP logging function logs Get requests, Set requests, and Set responses, but does not log Get
responses.
•
Get operation—The agent logs the IP address of the NMS, name of the accessed node, and node
OID.
•
Set operation—The agent logs the NMS' IP address, name of accessed node, node OID, variable
value, and error code and index for the Set operation.
The SNMP module sends these logs to the information center as informational messages. You can
configure the information center to output these messages to certain destinations, for example, the
console and the log buffer. The total output size for the node field (MIB node name) and the value field
(value of the MIB node) in each log entry is 1024 bytes. If this limit is exceeded, the information center
truncates the data in the fields. For more information about the information center, see "Configuring the
information center."
To configure SNMP logging:
Step Command
Remarks
1.
Enter system view.
system-view N/A
2.
Enable SNMP logging.
snmp-agent log { all |
get-operation | set-operation }
By default, SNMP logging is
disabled.
Configuring SNMP traps
The SNMP agent sends traps to inform the NMS of important events, such as a reboot.
Traps fall into generic traps and vendor-specific traps. Generic traps include authentication, coldstart,
linkdown, linkup and warmstart. All other traps are vendor-defined.