User Manual

Rack ATS AP44xx User Manual128
SNMP Issues
Problem Solution
Unable to perform a GET • Verify the read (GET) community name (SNMPv1) or the user profile configuration
(SNMPv3).
• Use the CLI or Web UI to confirm that the NMS has access.
See “SNMP options” on page 96
Unable to perform a SET • Verify the read/write (SET) community name (SNMPv1) or the user profile
configuration (SNMPv3).
• Use the CLI or Web UI to confirm that the NMS has write (SET) access (SNMPv1)
or is granted access to the target IP address through the access control list
(SNMPv3). See “SNMP options” on page 96.
Unable to receive traps at
the NMS
• Make sure the trap type (SNMPv1 or SNMPv3) is correctly configured for the NMS
as a trap receiver.
• For SNMP v1, query the mconfigTrapReceiverTable MIB OID to verify that the
NMS IP address is listed correctly and that the community name defined for the
NMS matches the community name in the table. If either is not correct, use SETs
to the mconfigTrapReceiverTable OIDs, or use the CLI or Web UI to correct the
trap receiver definition.
• For SNMPv3, check the user profile configuration for the NMS, and run a trap test.
See “SNMP options” on page 96, “Configure Notifications” on page 100, and
“SNMP traps” on page 105.
Traps received at an NMS
are not identified
See your NMS documentation to verify that the traps are properly integrated in the
alarm/trap database.