The
can be managed remotely by an SNMP network management system.
Info |
---|
|
If you are using Service Control Center ( SCC), and SNMP polling is enabled, SNMP v1 must be enabled and the community must be identical on both ends. |
The following figure shows an example of the
configured for an SNMP Network.
SNMP Configuration Example
![SNMP_Configuration_Example.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
The following table lists SNMP management support.
Caption |
---|
|
Item | Description |
---|
SNMP | SNMP version support. SNMPv1—Can be configured by itself or with SNMPv3. Supports multiple SNMPv1 and SNMPv2 trap destination configurations. Traps are sent to each of the configured destination using the appropriate protocol version and community string. Refer to Use the Services Configuration Page. SNMPv2—Supported as part of SNMPv1. Choose Show Trap Destinations > Add a Trap Destination and enter “2” in the Version field to tell the to send a message to every remote host in the list when errors are present. Refer to Use the Services Configuration Page.SNMPv3—Supports password-protected security. Can be configured by itself or with SNMPv1. Supports only one trap destination. Refer to Use the Services Configuration Page. | MIBS | read-only MIB support. • MIB-II (RFC 1213) • IF-MIB (RFC 2863) • SNMPv2-MIB (RFC 3418) • TCP-MIB (RFC 4022) • IP-MIB (RFC 2011) • UDP-MIB (RFC 4113) • SNMP-VIEW-BASED-ACM-MIB (RFC 3415) • SNMP-MPD-MIB (RFC 3412) • SNMP-USER-BASED-SM-MIB (RFC 3414) • SNMP-FRAMEWORK-MIB (RFC 3411) | Traps | trap support. • coldStart • authenticationFailure • linkup • linkDown |
|