Using SNMP to Upgrade Software on a Management Module

Release Notes for 07.8.04

5.Reboot the routing switch to load software release 07.8.04a from the area of flash memory (primary or secondary) where you stored it.

NOTE: When you reload the software after upgrading the software to release 07.8.04a, the routing switch displays a message to say that the configuration has changed and prompts you to save the changes. This message is displayed even if you do not make any configuration changes because the software records its release number in the running-config file when the software is loaded onto the switch. Enter Y to reload without saving the change or save the change and reload.

Using SNMP to Upgrade Software on a Management Module

Third-party SNMP management applications such as HP OpenView can upgrade software on a routing switch.

NOTE: In software releases earlier than 07.5.04, the SNMP agent does not check for type validity with the SNMP version. In software release 07.5.04 and greater, the SNMP agent does not send a reply for a varbind, if the type of the varbind is not a known type for that version of SNMP. For example, MIB objects of type Counter64 cannot be retrieved using a v1 packet, as Counter64 is a v2c and v3 type.

Make sure you use the correct procedure for your device and processor type. For example, do not use the Management Processor procedure to upgrade the switching processors on a T-Flow module.

The syntax shown in this section assumes that you have installed HP OpenView in the “/usr” directory.

ProCurve recommends that you make a backup copy of the startup-config file before you upgrade the software. If you need to run an older release, you will need to use the backup copy of the startup-config file.

Upgrading a Management Processor using SNMP

Use the following procedure to upgrade:

•An M2, M4, or EP module

•Management processor on the T-Flow module

To upgrade software code on the Management Processor:

1.Configure a read-write community string on the ProCurve device, if one is not already configured. To configure a read-write community string, enter the following command from the global CONFIG level of the CLI:

snmp-server community <string> rw

where <string> is the community string and can be up to 32 characters long.

2.On the ProCurve device, enter the following command from the global CONFIG level of the CLI: no snmp-serverpw-check

This command disables password checking for SNMP set requests. If a third-party SNMP management application does not add a password to the password field when it sends SNMP set requests to an ProCurve device, by default the ProCurve device rejects the request.

3.From the command prompt in the UNIX shell, enter the following command:

/usr/OV/bin/snmpset -c<rw-community-string><hp-ip-addr>1.3.6.1.4.1.1991.1.1.2.1.5.0 ipaddress <tftp-ip-addr>1.3.6.1.4.1.1991.1.1.2.1.6.0 octetstringascii <file-name>1.3.6.1.4.1.1991.1.1.2.1.7.0 integer <command-integer>

Where:

<rw-community-string> is a read-write community string configured on the ProCurve device. <hp-ip-addr> is the ProCurve device’s IP address.

10