Quantcast
Channel: Web and Unmanaged topics
Viewing all articles
Browse latest Browse all 1308

VLAN Issues on ProCurve 1920

$
0
0

Hello,

 

Hopefully I have this posted in the correct section. I'm having some issues getting multiple VLANs working on a ProCurve 1920 switch. The most puzzling part of this issue is that everything worked fine until I moved the switch to a different part of our building (but had it connected to the same trunk port on its neighbor switch, yes I saved the config before relocating the switch). 

 

So, here's the overall problem: The devices on my voice VLAN ports are unable to communicate with pretty much anything on the network (unable to obtain an IP address via DHCP, issue persists with static IP configured). Everything on the data VLAN works fine so far.

 

 Here are some details on my network's setup: 

 

We have two VLANS configured. One is for voice (100) and the other is for data (1). I started this job a couple of months ago and we were in the process of rolling out a new phone system. The previous phone system was on the data VLAN, so I'm assuming this was all one big flat network until just before I started this job. The data VLAN uses 172.16.0.xxx addresses while the voice VLAN uses 172.16.100.xxx addresses. I believe either a router or firewall handles DHCP for the voice VLAN. A domain controller handles DHCP for the data VLAN. Our desktops and phones directly connect to their own network drops. Our desktops do not connect to the PC ports on our phones. 

 

Our existing switches (ProCurve 2810, 2910) are working fine with this configuration: trunk ports (switch to switch links) are set to be tagged members on both VLAN 1 and 100, access ports are set to be untagged members of either VLAN 1 or 100 (depending on the device connected). When I initially set up the 1920 (after assigning it an IP address for remote access), I set ports 1-16 to be untagged members of VLAN 1 (ports for desktops and such only), ports 17-23 to be untagged members of VLAN 100 only (ports for phones only), and port 24 to be tagged on both VLAN 1 and 100. Port 24 on the 1920 connects to port 7 on our 2910 (set to be tagged on both VLAN 1 and 100). 

 

This configuration worked fine on the 1920 until I relocated it to a different part of our building. It is connected to a different network drop, but I have this drop connected to the same port 7 on the 2910 that worked perfectly fine during my testing. Since then, I have been pulling my hair out with all sorts of configuration changes, but I have made no progress. The issue persists on VLAN 100, but VLAN 1 works perfectly fine.

 

Any ideas on what to try or change to get this up and running? I've looked through the manual, set PVIDs, set static routes, made an interface for VLAN 100 (all of these were reverted since), but nothing has resolved the issue. I've got a copy of the manual and have been studying it since then. I am unable to un-deploy the switch and bring it back to a testing environment as we don't have a temporary replacement ready. 

 

Thanks


Viewing all articles
Browse latest Browse all 1308

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>