UCM6302a and TP Link Omada VLAN

Have an Omada network at the church and we’re finally upgrading our early-90s phone system to a Grandstream UCM6302a with GRP phones.

In prep for deploying it, I was doing some initial setup on the UCM as well as the network to create a VLAN for the phones and so that computers connected to the passthrough remain on the main network. Instructions online and via ChatGPT have been helpful. However, when I enabled the VLAN and then set the UCM and phones to use it (VLAN 99), they would not pull an IP. The UCM6302a would say “No IP” on the screen and the phone would just say something about no network or network unreachable or something.

Any idea what I did wrong? It’s basically like DHCP wasn’t working but by all appearances I had it set right. I mean, obviously not but it seemed like I did. I’m open to questions, suggestions, etc. Likely something simple somewhere but I got to the point where I am tired of trying so I’m seeking help.

What is doing the DHCP for that VLAN? Do the PC’s work on the passthrough?

I haven’t had a chance to do much more investigating after I got the No IP error. I deleted the VLAN I had created and added it again, thinking I may have missed a step. I hope to test it this weekend and have a little more time to investigate if it doesn’t work. Threw me off because I felt like I had followed the steps but when it wouldn’t work I didn’t have time to dig into it. Mostly posted here in case there was someone who came along and said “oh yeah, the same thing happened to me and I had failed to _________” or something. I’m no networking expert, but certainly more experienced than your average guy so when it doesn’t work as expected I kind of just get lost.

You mentioned setting up a VLAN for the phones (99), what is assigning the IP’s on that VLAN? If you plug a PC into an untagged port for 99, does it get an IP address?

So…this morning I just logged on the Omada network and looked at devices and the phone phone I have connected (for testing) now has a 192.168.99.xx address. The UCM is still on a 39.xx address so it can’t see the phone as it is looking for it at the old address. But maybe I’m on the right track.

The computer connected to the phone’s passthrough does have a .39.xx IP so that seemed to work correctly.

The switch port that you have the PBX on needs to be set with a default vlan of 99.

Or you can configure the vlan in the ucm’s network settings as long as the switch port is setup as a trunk with 99 being on that trunk.

Personally I like to just set the ports default vlan to be 99.

OK thanks for that tip. I do now have the UCM sans the one phone I have connected for testing both on the VOIP VLAN. I fully admit that some of this, or all, is mostly due to my ignorance but I like to learn new things and I’m not afraid to ask for guidance along the way. Hadn’t dug into VLANs or deploying a VOIP system until now but I’m learning.

Appreciate the tips and help.