What I have:
HP A5120-48G EI (JE069A)
Dell PowerConnect 6248P
SonicWall NSA 4500 (router/firewall/content filter/magic box)
Technically I have 3 of the HP switches in a stack and 2 of the Dells in a stack, but for the purposes of setting this stuff up it's just 3 vendors and 3 models we have to worry about.
Ok, my understanding of VLANs is shaky. When I refer to "I" I mean the network at 192.168.100.x. Here's what the physical connections look like:
Internet
|
SonicWall
|
HP --- servers and workstations 192.168.100.x
|
Dell --- pbx and voip phones 192.168.60.x (not using SIP, have two PRI going directly into the PBX)
Now in the old days, I had this:
Internet
|
SonicWall
|
HP (old stanky switch) --- servers and workstations 192.168.100.x
|
VLAN to old pbx and stanky old phones 192.168.50.x
There was the default VLAN and the phone VLAN, the HP switch had routing enabled and 192.168.50.1 assigned to the phone VLAN interface, the SonicWall had a routing rule to dump everything going to the 192.168.50.x subnet into the HP switch and things worked.
On the new setup, I initially fumbled my way to the same thing. The new HP switch had the 192.168.60.1 gateway for the phone VLAN (VLAN 30) and the Dell had various horrible things done to make it talk to the HP. So it was like thus:
Internet
|
SonicWall
|
HP --- 192.168.100.x --- HPstank --- 192.168.50.x (keeping old phone server around for access to call recordings)
|
VLAN 30 192.168.60.1 interface on HP
VLAN 30 tagged port
|
Dell --- 192.168.60.x
I started to get some crappy call quality and thought maybe it's because the VoIP phones have to go from the Dell to the HP to get routed to the PBX and that's over 1 Gbps. Not like the PBX is on anything faster to the switch but hey. I got the Dells and physically isolated the VoIP phones and PBX from the network to minimize any drop in quality from network contention by running them all piggybacked on the regular data connection. So anyway, what I want to do is this:
Internet
|
SonicWall
|
HP --- 192.168.100.x --- HPstank --- 192.168.50.x (keeping old phone server around for access to call recordings)
|
VLAN 30 tagged port
|
Dell --- 192.168.60.1 interface on Dell --- 192.168.60.x
That way everything VoIP-related stays inside the Dell switches. Now, however, I can't access the PBX servers on the Dells. Phone system works fine. Looking at this written out, the link from HP to HPstank doesn't have a tagged/trunk VLAN and it works fine. Maybe I need to elimate the tagged port between HP and Dell? I can access the Dell on the default VLAN 1 management IP just fine so the switch itself is still connecting to the HP, just maybe not the VLAN? And to clarify, not using SIP at all, I have two PRI going directly into the PBX so this is all about getting the PBX managed from the "normal" network.
Any ideas or suggestions? Network admin work is not my area of expertise. I was a CCNA 15+ years ago and haven't touched anything since so I'm waaay rusty on this kind of stuff, especially the CLI. I've mainly been doing stuff via web management thus far. I would call the respective support lines, but my experience in setting up the initial VLAN configuration was thus:
SonicWall - we are a bunch of Indians and will always sound irate and don't want to help you the device cannot do what you are asking do not bother us thank you goodbye (after 45 minutes of transferring a few times and taking down the wrong information multiple times)
HP - oh that's an H3C switch, we don't know how to do anything with those. We'll offer suggestions if ya want and we can discover things together! (US-based, nice folks)
Dell - well that should be working, dunno why it ain't. (US-based, nice folks)
I Googled my way into getting things working, manually change port VLAN mode to "general" and frame type to "admit all" on the Dell for instance, but I'm stumbling in the dark with a lot of this stuff.