APC AP95500 Datasheet Page 11

  • Download
  • Add to my manuals
  • Print
  • Page
    / 300
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 10
a.
Select Server Administration Settings > Server Access in the System
menu.
b.
Enable the SOCKS Server option in the SOCKS Proxy tab.
7. Add a remote NFS or Windows share repository the StruxureWare Central server can
use instead of the local repository.
a.
Select Server Administration Settings > Storage Settings in the System
menu.
b.
Use the Repositories tab to add a remote repository.
c.
Use the Purge Settings tab to define the purge settings you want the repository
to use.
8. Define at least one NFS or Windows share location to be used for backup files of
the StruxureWare Central server configuration data, or its configuration and
repositories data.
a.
Select Server Administration Settings in the System menu.
b.
Select Server Backup/Restore in the "Server Administration Settings" display.
c. Identify the NFS or Windows share location at which backup files will be saved.
d. Schedule how often those files will be created automatically.
Note: By default, backup files will be created every Friday at 1:00 AM.
9. Discover the SNMPv1, SNMPv3, Modbus devices, and NetBotz Appliances you want
your server to monitor.
Note: All four device types require their own discovery process, not only on the public
LAN, but on the private LAN, as well.
a.
Select Add Devices in the Device menu, or click the green + icon in the Device
View.
b. Select which type of device you want to discover (SNMPv1, SNMPv3, NetBotz
Appliance, or Modbus TCP), and click Next.
c. Define the parameters to be used for the discovery process.
d. Run the discovery process.
e. Repeat steps a through d, as needed, to discover all the types of devices you
want the StruxureWare Central server to monitor (SNMPv1, SNMPv3, NetBotz
Appliance, or Modbus TCP), on both the public and private LANs.
10. Define any or all the alarm notifications you want available to the StruxureWare
Central server for any SNMPv1, SNMPv3, and Modbus devices discovered during
step 9.
Note: Additionally, each NetBotz Appliance has its own unique profiles it can use for
alarm conditions at the devices it monitors (see step 13).
The StruxureWare Central server has a Default notification policy. Device alarms
and communication link status thresholds for all monitored devices are included in
the Default notification policy at device discovery.
You must create at least one alarm action, and add it to the Default notification policy,
or another notification policy you create, before the StruxureWare Central server can
generate alarm notifications for conditions that occur at monitored SNMP and Modbus
devices.
a.
Select Manage Alarm Actions in the Alarm Configuration menu.
b.
Click Create to access the Alarm Action wizard.
c. In the "Choose Alarm Action Type" display, select the type of alarm you want to
create, and click Next.
d. In the "Configure Alarm Action" display for the selected action, define the settings
you want the action to use, and click Finish to exit the wizard.
11.
Add alarm actions to the Default notification policy.
a.
In the Alarm Configuration perspective, in the Notification Policies view,
select the Default notification policy. Right-click and select Edit.
Note: To create a new notification policy, right-click or use the Create
Notification Policy icon.
StruxureWare Central 6.3.0
11
Page view 10
1 2 ... 6 7 8 9 10 11 12 13 14 15 16 ... 299 300

Comments to this Manuals

No comments