Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

HP 2910al Setup Queries

churchhouse
Occasional Advisor

HP 2910al Setup Queries

We are goign voip.

 

Existing Data network is on a 172.19.0.0/24.  Works fine.

We also have 2x external site to site vpns going to 192.168.1.0/24 and 192.168.2.0/24

 

I have a 2910al 48 port for the 172. site and a 24 port 2910al for the 192 site.

 

We plan to seperate the voice from the data networks on the 172 lan.  So Cisco to Firewall, firewall lan01 to data and lan02 to voice.

I have configured 2x vlans on the new switch.

 

I am now stuck.

Here is the current config:

 

HP-E2910al-48G-PoE(config)# show config

Startup configuration:

; J9148A Configuration Editor; Created on release #W.15.08.0012
; Ver #02:11.05:16
hostname "HP-E2910al-48G-PoE"
module 1 type j9148a
power-over-ethernet pre-std-detect
interface 1
name "HP1910"
no power-over-ethernet
exit
interface 2
no power-over-ethernet
exit
interface 3
no power-over-ethernet
exit
interface 4
no power-over-ethernet
exit
interface 5
no power-over-ethernet
exit
interface 6
no power-over-ethernet
exit
interface 7
name "Shoretel E1k"
exit
interface 8
name "Shoretel SG90"
exit
interface 9
name "Shoretel SG90Bri"
exit
interface 48
name "vlan20 to Firewall"
exit
snmp-server community "public" unrestricted
snmp-server contact "IT" location ""
vlan 1
name "DEFAULT_VLAN"
no untagged 7-48
untagged 1-6
ip address 172.19.4.5 255.255.0.0
exit
vlan 20
name "Voice"
untagged 7-48
ip address 172.16.4.5 255.255.0.0
ip helper-address 172.19.10.17
ip helper-address 172.19.10.18
exit
no autorun
password manager

 

DHCP scope of 172.16.0.0 has been configured on the Win2k8 server..

 

The client machine i am testing isnt getting an ip.

 

IDeas?

1 REPLY
Vince_Whirlwind
Trusted Contributor

Re: HP 2910al Setup Queries

What's goin on with your subnet masks?

 

You say you have an existing 172.19.0.0/24 network that works fine.

 

Then you describe a VLAN 1 subnet on this switch that clashes with that network. A /16 mask is probably never a good idea anyway.

 

I would always test my setup with a static address on the networks first, before worrying about DHCP.

When setting up a new network, I tend to follow this pattern:

 

Setup physical infrastructure

 - install each switch

 - observe link light

 - test L2 connectivity with its neighbours with LLDP

Setup Data VLAN,

  - Create VLAN

  - assign Data subnet router/def.GW address

  - extend Data VLAN where required.

Use my laptop to test Data VLAN accessibility

 - between devices on same switch,

 - between devices on different switches, (test every switch)

 - between devices and any WAN resources they require

 - test DHCP

 - test any other services

Setup Voice VLAN

 - (same)

Use my laptop to test Voice VLAN accessibility

 - (same)

 

A couple of things:

Best not to use VLAN1

Ideally when setting up the infrastructure, setup a dedicated management network for your switches, so they are in their own VLAN/subnet.

 

How are the 192. subnets relevant to this problem, BTW?