Avocent MERGEPOINT 53XX SP MANAGER User's Guide Page 75

  • Download
  • Add to my manuals
  • Print
  • Page
    / 236
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 74
e. From the Time menu(s), select the day, hour and minute for the task to occur. Options
in the Time menus vary according to your selections.
f. Choose Once, Daily, Weekly or Monthly, then specify the task schedule accordingly.
4. Click Apply.
To edit a scheduled task:
1. Click System - Schedules.
2. Click Edit next to the task you wish to edit and follow the on-screen instructions.
To delete a scheduled task:
1. Click System - Schedules.
2. Select the task to delete and click Delete.
SNMP Access
The SNMP agent provides access to the MergePoint SP manager through an SNMP
management application, such as HP Openview, Novell NMS, IBM NetView or Sun Net
Manager, and provides proxy access to SNMP data from connected service processors that
implement SNMP agents.
NOTE: The SNMP agent can also be configured to send notifications (also known as traps) about significant events
on the MergePoint SP manager and on SPs. See Using the Alerts Viewer on page 58.
The administrator must configure the SNMP agent to use the version of SNMP supported by the
management application, SNMP v1, v2c or v3. The use of v3 is strongly encouraged wherever
possible because it provides authentication and encryption of data that is lacking in v1 and
v2c.
Access to information provided by the MergePoint SP manager and its proxy SPs can be
obtained in either of the two following ways:
The recommended access method for agents which support only SNMP version 1 or 2c is
through a proxy on the MergePoint SP manager. The MergePoint SP manager provides the
authentication and encryption lacking in those protocol versions. The SNMP management
application can then be used for SNMP management of the SP.
NOTE: Running the SNMP daemon (snmpd) on the MergePoint SP manager allows you to access the proxy data
using the v1 and 2c protocols without going through a VPN tunnel. However, this method is inherently unsecure.
The access method agent which supports version 3 is via a local Net-SNMP daemon. The
proxying of traps is not supported by Net-SNMP.
Chapter 3: Operations 63
Page view 74
1 2 ... 70 71 72 73 74 75 76 77 78 79 80 ... 235 236

Comments to this Manuals

No comments