Enabling/Disabling Snmp - HP procurve 8100fl series Management And Configuration Manual

N o t e
N o t e
Targets are defined by their IP addresses. Each target that is defined receives
a copy of the notifications generated and sent by the ProCurve 8100fl agent.
In addition, you need to specify a community string for the notifications. For
security reasons, the community strings in notifications should be different
from the read/write community strings. So when the 8100fl switch sends
notifications, unauthorized users who capture the notifications will not be
able to use the community string to access the MIB modules.
In the following example, the notifications will be sent to the target with
address 10.10.10.1 (and a community string of "western"
ProCurve(config)#snmp community community1 ro
ProCurve(config)#snmp host 10.10.10.1 western
If the IP address of the target is more than one hop away from the switch,
configure the switch with a static route to the target. If the switch is rebooted,
the static route allows a cold-start notification to be sent to the target. Without
a static route, the cold-start notification is lost while the routing protocols are
converging.

Enabling/Disabling SNMP

By default, SNMP is active and monitoring UDP port 161. You can turn off
SNMP by entering:
ProCurve(config)#no snmp active
To restart SNMP, enter:
ProCurve(config)#snmp active
SNMP will issue a warmStart notification and resume monitoring port 161.
The snmp active command runs independently of your SNMP configuration.
You must still configure SNMP. The no snmp active command is a useful
alternative to negating lines in your configuration file when you need to
disable SNMP.
SNMP Configuration
Configuring Access to MIB Objects
):
18-5