SNMP on the OnBoard
26 AlterPath OnBoard Administrator’s Guide
Considerations When Deciding Whether to Use
DHCP to Configure Device Addresses
Before deciding whether to use the DHCP server to configure addresses for
connected devices, the OnBoard administrator should understand the
available options for assigning IP addresses to connected devices, which are
described in “Address Configuration for Connected Devices” on page 372.
SNMP on the OnBoard
The administrator can activate Simple Network Management Protocol
(SNMP) agent software that resides on the OnBoard. The SNMP agent
provides access to the OnBoard by an SNMP management application, such
as HP Openview, Novell NMS, IBM NetView, or Sun Net Manager, and
provides proxied access to SNMP data from connected service processors that
implement SNMP agents. The OnBoard SNMP agent can be configured to
send notifications (also known as traps) about significant events on the
OnBoard and on connected devices.
The OnBoard administrator must configure the SNMP agent to use the
version of SNMP supported by the management application, either SNMP v1,
v2c, and 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 OnBoard and its proxied connected
devices is available in two ways:
• The recommended access method for agents which support only SNMP
version 1 or 2c is through a VPN tunnel to the OnBoard. The OnBoard
provides the authentication and encryption lacking in those protocol
versions. The management application can then be used to for SNMP
management of the device.
When versions 1 or 2c agents are used to obtain native management
access to a device, no SNMP configuration is needed. Support is
implemented entirely through the VPN connection limited by iptables
rules that restrict access to particular devices.
Commentaires sur ces manuels