Filter
Top Products
UPS Network Management Card 2 User’s Guide82
SNMP Issues
Synchronization Problems
Problem Solution
Unable to perform a
GET
• Verify the read (GET) community name (SNMPv1) or the user profile configuration
(SNMPv3).
• Use the command line interface or user interface to ensure that the NMS has access.
See “SNMP” on page 58.
Unable to perform a
SET
• Verify the read/write (SET) community name (SNMPv1) or the user profile
configuration (SNMPv3).
• Use the command line interface or user interface to ensure 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” on page 58.
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 command line interface or user
interface to correct the trap receiver definition.
• For SNMPv3, check the user profile configuration for the NMS, and run a trap test.
See “SNMP” on page 58, “Trap Receivers” on page 65, and “SNMP Trap Test” on
page 66.
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.
Problem Solution
A Synchronized Control Group
member does not participate in a
synchronized action.
Make sure the group member’s status is set to Enabled. Also check the
group member’s battery capacity, if the synchronized action required
UPSs to turn on.
An attempt to add a member to a
Synchronized Control Group fails.
The values for Multicast IP Address, Synchronized Control Group
Number, and firmware version must match those of other members of
the group.