Xtreme Power Conversion Corporation
Web/SNMP Cards
Page 25
UPS Management
Password page
This page allows the currently connected user to modify its password. Clearly, this page only allows modification
to the current users. The account of other users can be managed only by the supervisor users in the User section.
NOTE
: The password length is limited to 8 chars.
Configuration page
In this page, the SNMP/Web adapter configuration file is shown in a text area. The configuration file can be ex-
ported by pressing the Highlight button and copying the selected text (e.g. CTRL+C) to a separate application.
Upgrade page
This page shall only be accessed when the SNMP/Web adapter SW is to be upgraded. Refer to the section for de-
tails on the SW upgrade process.
SNMP Section
The SNMP section deals with SNMP and trap configuration.
SNMP settings page
The most relevant SNMP settings are the following:
Parameter Name
Description
Port Number
Set SNMP server listening port. Default port is 161.
Get Community
Defines the community name for receiving SNMP information (GET). The get com-
munity name controls access to the SNMP Agent – the community in the request
must match the getcommunity parameter. The default value is public.
Set Community
Defines the community name for writing SNMP information (SET). The set commu-
nity name controls access to the SNMP Agent – the community in the request must
match the setcommunity parameter. The default value is private.
Trap settings page
This page allows to configure up to 20 recipients of SNMP traps. The most relevant settings are the following:
Parameter Name
Description
Trap destination
IP-address of the trap target
Community
Community name (optional – default is public)
V2
Controls SNMP trap version:
If unchecked, v1 traps are sent (default)
If checked, V2 traps are sent
Port
Port to which the trap will be sent (optional – default 162)
Alarm notification page
This page is used to configure the alarm notification via trap and/or e-mail. Every alarm is listed, and the user may
enable the notification via trap and/or e-mail upon alarm (de)activation. Further to this, alarm handling can be
enabled/disabled through the Enable checkbox. When disabled, an alarm occurrence is totally filtered – the alarm
will never appear active, it will not be reported by any mean and it will not be logged.