Difference between revisions of "HP4000M - configuration"

From Perswiki
Jump to: navigation, search
(→‎Updating configuration from file)
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
In August 2012 I acquired a number of HP4000M switches - these are really quite elderly 100Mbit switches.
 
In August 2012 I acquired a number of HP4000M switches - these are really quite elderly 100Mbit switches.
−
100Mbit/s is hardly an impressive speed today, but for me it is sufficient. More importantly, the switches come with a complete set of professional management features, which is perfect for my purposes.  
+
When 1Gbit/s is typical in even SOHO desktop switches, 100Mbit/s is hardly an impressive speed, but for me it is sufficient. More importantly, the switches come with a complete set of professional management features (SNMP, VLANs, monitoring, filtering), which is perfect for my purposes.  
  
 
When I started configuring them, I went to look for a way to download the configuration file (as a backup)
 
When I started configuring them, I went to look for a way to download the configuration file (as a backup)
−
as well as a way to upload a new one (mass changes are easier done with an editor).  Google did eventually lead me to summary procedure, but  
+
as well as a way to upload a new one (mass changes are easier done with an editor).  Google did eventually lead me to some information, but  
 
it wasn't exactly well documented.  
 
it wasn't exactly well documented.  
  
−
==Download configuration file==
+
==Retrieving the configuration file==
 
The HP4000m uses TFTP so you will need a TFTP-server on your network. How to set up a TFTP server is outside the scope of this article.  
 
The HP4000m uses TFTP so you will need a TFTP-server on your network. How to set up a TFTP server is outside the scope of this article.  
−
 
−
===Step by step===
 
−
Because the file transfer must be initiated from the switch, it looks more like a file upload. I prefer to think of the switch as the target or the client, hence I think of this as downloading the config file. Apologies if that sounds confusing.
 
  
 
<ol>
 
<ol>
Line 20: Line 17:
 
<li>Choose "Diagnostics"</li>
 
<li>Choose "Diagnostics"</li>
 
<li>Choose "Command prompt"</li>
 
<li>Choose "Command prompt"</li>
−
<li>Enter: "put <tftp-server> CONFIG <remote filename></li>
+
<li>Enter "put <tftp-server> CONFIG <tftpdir>/hp4000m/switch.config</li>
 +
</ol>
 +
 
 +
==Updating configuration from file==
 +
When making mass changes, it is much easier to retrieve the current configuration file and use an editor
 +
to make the changes, then upload the configuration file to the switch.
 +
 
 +
<ol>
 +
<li>telnet <switch-address></li>
 +
<li>Choose "Diagnostics"</li>
 +
<li>Choose "Command prompt"</li>
 +
<li>Enter "get <tftp-server> CONFIG <tftpdir>/hp4000m/switch.config</li>
 
</ol>
 
</ol>
  
Line 29: Line 37:
  
 
First of all, retrieve the lastest firmware from the HP support website.  At the moment, the latest version is C.09.30. The zip archive contains two
 
First of all, retrieve the lastest firmware from the HP support website.  At the moment, the latest version is C.09.30. The zip archive contains two
−
file - release note and the firmware file.
+
file - release note and the firmware file. I extracted the C-09_30.swi file into <tt><tftpdir>/hp4000m/</tt>.
 +
The rest is straight forward:
 +
<ol>
 +
<li>telnet <switch-address></li>
 +
<li>Choose "Download OS"</li>
 +
<li>Enter TFTP server address, and <tftpdir>/hp4000m/C_09_30.swi</li>
 +
<li>Hit eXecute</li>
 +
</ol>
 +
The server will automatically reboot with the new firmware.

Latest revision as of 06:28, 7 August 2012

In August 2012 I acquired a number of HP4000M switches - these are really quite elderly 100Mbit switches. When 1Gbit/s is typical in even SOHO desktop switches, 100Mbit/s is hardly an impressive speed, but for me it is sufficient. More importantly, the switches come with a complete set of professional management features (SNMP, VLANs, monitoring, filtering), which is perfect for my purposes.

When I started configuring them, I went to look for a way to download the configuration file (as a backup) as well as a way to upload a new one (mass changes are easier done with an editor). Google did eventually lead me to some information, but it wasn't exactly well documented.

Retrieving the configuration file

The HP4000m uses TFTP so you will need a TFTP-server on your network. How to set up a TFTP server is outside the scope of this article.

  1. On your TFTP server, create the target file:
    touch <tftpdir>/hp4000m/switch.config
    chmod 777 <tftpdir>/hp4000m/switch.config
  2. telnet <switch-address>
  3. Choose "Diagnostics"
  4. Choose "Command prompt"
  5. Enter "put <tftp-server> CONFIG <tftpdir>/hp4000m/switch.config

Updating configuration from file

When making mass changes, it is much easier to retrieve the current configuration file and use an editor to make the changes, then upload the configuration file to the switch.

  1. telnet <switch-address>
  2. Choose "Diagnostics"
  3. Choose "Command prompt"
  4. Enter "get <tftp-server> CONFIG <tftpdir>/hp4000m/switch.config

The server will automatically reboot to activate the new config.

Upgrading firmware

Firmware upgrade is also done via TFTP, but you don't need the command line interface.

First of all, retrieve the lastest firmware from the HP support website. At the moment, the latest version is C.09.30. The zip archive contains two file - release note and the firmware file. I extracted the C-09_30.swi file into <tftpdir>/hp4000m/. The rest is straight forward:

  1. telnet <switch-address>
  2. Choose "Download OS"
  3. Enter TFTP server address, and <tftpdir>/hp4000m/C_09_30.swi
  4. Hit eXecute

The server will automatically reboot with the new firmware.

Retrieved from "https://wiki.jessen.ch/index?title=HP4000M_-_configuration&oldid=250"