12-4
Configuring for Network Management Applications
Overview
Monitoring and Managing
the Switch
Configuring for SNMP Access to the Switch
SNMP access requires an IP address and subnet mask configured on the
switch. (See “IP Configuration” on page 7-3.) If you are using DHCP/Bootp to
configure the switch, ensure that the DHCP/Bootp process provides the IP
address. (See “DHCP/Bootp Operation” on page 7-10.)
Once an IP address has been configured, the general st eps to configuring for
SNMP access to the preceding features are:
1. From the Main menu, select
2. Switch Configuration . . .
6. SNMP Community Names
2. Configure the appropriate SNMP communities. (T he “public” community
exists by default and is used by HP’s network management applications.)
(For more on configuring SNMP communities, see “Menu: Viewing and
Configuring SNMP Communities” on page 12-5.)
3. Configure the appropriate trap receivers. (For more on configuring t rap
receivers, see “CLI: Configuring and Displaying Trap Receivers” on page
12-9.)
In some networks, authorized IP manager addresses are not used. In this c ase,
all management stations using the correct co mmunity name may access the
switch with the View and Access le vels that have been set for tha t community.
If you want to restrict access to one or more specific nodes, y ou can use the
switch’s IP Authorized Manager feature. (See “Using Authorized IP Managers
for Increased Management Security” on page 10-1.)
Caution Deleting the community named “public” disables many network management
functions (such as auto-discovery, traffic monitoring, SNMP trap generation,
and threshold setting). If security for network management is a concern, it is
recommended that you change the write a ccess for the “public” community
to “Restricted”.