HP ProCurve 2910al switch

[The_Librarian]

Lovely piece of kit

However, when I got it, some ijit's already programmed an IP.

So, to make it easier for me, I downloaded a small open-source DHCP server for Windows, set it up, and connect the switch to my laptop.

Said open-source DHCP server also got a web interface. http://sourceforge.net/projects/dhcp-dns-server/

Then I factory-reset the switch to its default state. In this state it'll obtain a DHCP address lease.

I was then able to determine which IP the switch got, and was able to change its configuration without any further issues. Added an admin password too. And documented this.


I opted for the single DHCP server on my laptop as it'll be quicker (and easier) to determine what IP was taken, rather than connecting the switch to the network, and trying to guess which IP it took... (using server2003).

I know in Server2003 you can view the DHCP leases etc, but there's a ton of leases Not lus to sift through them all to get recently acquired IP's

[dabouncer]

You could have saved yourself all that and just connected to the switch with a console cable.
conf
vlan 1
no ip add
ip add 192.168.0.1 255.255.255.0
unt 1-48
exit
no pass all
pass all
xyz
xyz
xyz
xyz
wr mem

There is also a means of resetting the switch password from the front of the switch with the little button. This feature can be turned off via config. front-panel-security i think it is called.

I hope after all that you did not use vlan 1 and instead opted for a different vlan id. Never use vlan 1.

[ponder]

I hope after all that you did not use vlan 1 and instead opted for a different vlan id. Never use vlan 1.

Just to add http://www.cisco.com/en/US/products/....shtml#wp39009

[nivek]

Lovely piece of kit

However, when I got it, some ijit's already programmed an IP.

So, to make it easier for me, I downloaded a small open-source DHCP server for Windows, set it up, and connect the switch to my laptop.

Said open-source DHCP server also got a web interface. http://sourceforge.net/projects/dhcp-dns-server/

Then I factory-reset the switch to its default state. In this state it'll obtain a DHCP address lease.

I was then able to determine which IP the switch got, and was able to change its configuration without any further issues. Added an admin password too. And documented this.


I opted for the single DHCP server on my laptop as it'll be quicker (and easier) to determine what IP was taken, rather than connecting the switch to the network, and trying to guess which IP it took... (using server2003).

I know in Server2003 you can view the DHCP leases etc, but there's a ton of leases Not lus to sift through them all to get recently acquired IP's

TFTPD also has a nice lil dhcp client built in