Change HP Switch Configuration

[Ignatius]

A colleague and I look after a business network. The switching infrastructure was installed and configured quite some time ago by an external company. That company is long gone and the documentation they provided isn't available. We need to reconfigure our network to accommodate a wider DHCP range. There are 5 data and 5 voice switches and another which is the default gateway. All switches are HP Procurve 2610-24.

 

The running config of the default gateway is:

 

; J9085A Configuration Editor; Created on release #R.11.107

 

hostname "HOSTNAME-REMOVED"

ip default-gateway 192.168.3.1

ip routing

snmp-server community "public" Unrestricted

vlan 1

name "DEFAULT_VLAN"

ip address dhcp-bootp

tagged 14-28

no untagged 1-13

exit

vlan 10

name "DATA"

untagged 1-13

ip address 192.168.3.254 255.255.255.0

tagged 14-28

exit

vlan 20

name "VOICE"

ip address 192.168.4.254 255.255.255.0

tagged 14-28

exit

vlan 100

name "MANAGEMENT"

ip address 192.168.5.254 255.255.255.0

tagged 14-28

exit

vlan 2

name "GUEST-WIFI"

exit

fault-finder bad-driver sensitivity high

fault-finder bad-transceiver sensitivity high

fault-finder bad-cable sensitivity high

fault-finder too-long-cable sensitivity high

fault-finder over-bandwidth sensitivity high

fault-finder broadcast-storm sensitivity high

fault-finder loss-of-link sensitivity high

fault-finder duplex-mismatch-HDx sensitivity high

fault-finder duplex-mismatch-FDx sensitivity high

ip route 0.0.0.0 0.0.0.0 192.168.3.1

snmp-server host 192.168.3.133 community "public"

snmp-server host 192.168.3.16 community "public"

snmp-server host 192.168.3.177 community "public"

spanning-tree

spanning-tree priority 0

password manager

password operator

 

This has connections from the other data and voice switches into ports 14 upwards from their individual port 26. The running configuration of one of the data switches is:

 

; J9085A Configuration Editor; Created on release #R.11.107

 

hostname "HOSTNAME-REMOVED"

ip default-gateway 192.168.5.254

snmp-server community "public" Unrestricted

vlan 1

name "DEFAULT_VLAN"

ip address dhcp-bootp

tagged 25-28

no untagged 1-24

exit

vlan 10

name "DATA"

untagged 1-24

tagged 25-28

exit

vlan 20

name "VOICE"

tagged 25-28

exit

vlan 100

name "MANAGEMENT"

ip address 192.168.5.9 255.255.255.0

tagged 25-28

exit

vlan 2

name "GUEST-WIFI"

exit

snmp-server host 192.168.3.133 community "public"

snmp-server host 192.168.3.16 community "public"

snmp-server host 192.168.3.177 community "public"

spanning-tree

spanning-tree priority 15

password manager

password operator

 

I have a TFTP server set up and have a separate switch for testing purposes. I have uploaded the Default Gateway startup-config and changed the ip address of this test switch to 192.168.3.253, 192.168.4.253 and 192.168.5.253 in the hope that I could plug a laptop and live network into the test switch then be able to ping out to 8.8.8.8 but this only works if I use a port in the range 1 to 13 for the laptop and live network. This does not simulate the ethernet connections to the default gateway (1 - 13 are empty and 14+ are all connected to other switches).

 

May I have some guidance about what I'll need to do? I thought it would be a matter of changing the DHCP scope in our DHCP server and changing the IP Address of the default gateway to 192.168.3 254 / 23 (from 192.168.3.254 / 24) but, needless to say, it's not working as I expected. It's ages since I did my CCNA and haven't played seriously with switch configuration since then.

 

Thanks in advance.

[FN-GM]

In the config you posted, the default gateway marked below is a DG for the switch for management purposes not for the VLAN itself. So changing this won't achieve what you want.

 

hostname "HOSTNAME-REMOVED"

ip default-gateway 192.168.3.1

ip routing

 

 

 

What range do you want to extend? To do that you can change one of the subnet masks in the below section of the configuration, however you might struggle doing this if it is VLAN 10 or 20 as the new range will overlap with the others. It might be easier to create a new VLAN in addition to what you have.

 

vlan 10

name "DATA"

untagged 1-13

ip address 192.168.3.254 255.255.255.0

tagged 14-28

exit

vlan 20

name "VOICE"

ip address 192.168.4.254 255.255.255.0

tagged 14-28

exit

vlan 100

name "MANAGEMENT"

ip address 192.168.5.254 255.255.255.0

tagged 14-28

exit

[Ignatius]

Hmm, that's interesting. All the client devices have 192.168.3.254 set as their DG. The 192.168.3.1 that you noted in the first config is the address of the SonicWall.

 

Ultimately, we'd like to extend our data network from 192.168.3.0 / 24 to 192.168.2.0 / 23. The IP Phones are on 192.168.4.0 / 24 so we can't extend upwards.

[FN-GM]

Hmm, that's interesting. All the client devices have 192.168.3.254 set as their DG

 

That is correct, the DG for clients should be the VLAN interface IP.

 

Ultimately, we'd like to extend our data network from 192.168.3.0 / 24 to 192.168.2.0 / 23

 

Modify the bold line to what is below. This will give you that range and your clients will keep the existing DG, but the subnet mask will need to change. You will need to modify the DHCP scope as well. You might also need to modify the static routes in your Sonicwall, or the clients won't have access to the internet. Test with static IP addresses first and modify DHCP last, this will avoid any downtime.

 

 

vlan 10

name "DATA"

untagged 1-13

ip address 192.168.3.254 255.255.254.0

tagged 14-28

exit

 

 

In the Cisco world you would do this, not sure in HP. It will be similar I should imagine.

 

En

Conf t

Int vlan 10

no ip address 192.168.3.254 255.255.255.0

ip address 192.168.3.254 255.255.254.0

Edited December 28, 2017 by FN-GM

[Ignatius]

Yes, I figured it should be necessary to take the SNM down from /24 to /23. I'll tinker with the test switch that I have.

 

As a matter of interest, it is similar to the Cisco syntax:

 

config

vlan 10

no ip address

ip address 192.168.3.254 255.255.254.0

exit

exit