Upgrading firmware on HP ProCurve 1800-24G / J9028B

A recent inventory of network switches showed that the one that is in most active use was on an outdated firmware revision.

I really like the switch in question, an HP ProCurve 1800-24G, as it is fanless and thus completely silent. It’s been in 24/7 use for 5-6 years now, and hasn’t failed once. It also supports things like SNMP, trunking and LACP  (which comes in handy when optimising the network for fast NAS transfers. More on that later..), and configurable LLDP and VLANs. All in all, more than enough for a small network like the one around here.
Oh – the password is not changed or reset by the upgrade – log in as previously.

 

5 thoughts on “Upgrading firmware on HP ProCurve 1800-24G / J9028B

  1. David Killingsworth

    I have this switch with these details:

    Hardware Version R01
    Software Version PB.03.02

    Where did you find the latest firmware for it. I can’t find it through google search or HP’s website.

    Any tip would be appreciated.

    Reply
  2. sputnik

    Hello,

    I have the same model of switch. Can you tell me how to configure vlan with it?
    I’ve tried to do it for myself but it doesn’t work. I have the last firmware R01 PB.03.10
    I am only have one switch and I want create a vlan for ports 3,4 for Windows Server 2012 Nic Teaming and 5,6 for VMware and the result is any comunication when I configure vlan in this ports. I’ve tried with other computers to discard a problem with Windows Server 2012 and vSphere 6.0 but I have the same problem.

    I follow this steps:
    1. Go to VLAN Setup.
    2. Add new vlan number and select add.
    3. Select ports 3,4,5,6 and select apply.
    4. Go to VLAN Port Config and for ports 3,4,5 and 6 for column Packed Type is selected All and for PVID only the number of new vlan, then I Applied

    The result is nothing work

    Reply
    1. Dmitry

      A bit late, but might still help.
      When you add ports to new VLAN make sure that you remove them from VLAN1(default) after that.
      Looks like it assigns the ports to VLAN1 and doesnt automatically remove it from there when you add ports to another vlan(s)

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *