Yes, all management vlans are set to "1".
Your second question: yes. I had both variants checked. I think.
I have fixed it by now anyway: that roof switch "D" being managed via cloud being the "lazy" setup, I decided to reset it and set it up locally according to the 3 cellar switches. It would have been neccesary anyway somewhen in the near future.
So, that AP port on D switch got its vlan1(T)/vlan100(U) setting and got its IP from the vlan1 subnet! I set it to static immediately and now all is working fine!
It's just a shame that switches still don't provide CLI for local management, I am so used to the CLI of the decomissioned HP 5400zl switch.. And those AP15 even can't be managed locally?! I was like w-t-f?
Edit: so, I think the "fix" was changing the D switch from being managed via cloud to local management. That particular "DG1" AP is connected to it, and had trouble getting an ip from that D switch (the others are connected to the cellar switches A/B/C).
Original Message:
Sent: 08-13-2024 07:03 PM
From: travatine
Subject: 1930 and AP15 - messing with vlans
Hi,
Just to check, is the management VLAN number the same on all the 1930s?
E.g. "1"
( It you point a web browser at the cloud managed switch's IP address, it should also display its current management VLAN number).
2 just to check:
"...Switches A/B/C are connected via trunk to D. Trunk is transporting vlan 100 untagged and vlans 1, 108 as tagged...."
For just the trunk between a/b/c and d, Have you tried setting VLAN 1 as untagged , and all other VLANs as tagged?
Thanks,
Travis
------------------------------
Travis Thorne
Original Message:
Sent: 08-12-2024 10:33 AM
From: k1ck
Subject: 1930 and AP15 - messing with vlans
Hello,
I am new to networking so pls be kind. I've got 4 switches of the same kind: 1930 48G Class 4 PoE 4SFP/SFP+ 370W. And I've got 4 access points AP15. All running on latest softwares.
Now, I installed 3 switches in the basement, as a stack and one under the roof. Let's name the basement ones A, B, C and the roof D. Access points accordingly being just A, B, C and D.
Switches A/B/C are connected via trunk to D. Trunk is transporting vlan 100 untagged and vlans 1, 108 as tagged.
All my 4 APs are configured with static ips in (management) vlan1 and providing a wlan which is offering vlan100 connections.
So, in order to connect 3 APs to the basement switches I've set up 3 ports to have vlan1 untagged and vlan100 tagged. They work fine, wlan up and ready 👍.
Same config is present for the roof switch D: one port is dedicated to untagged vlan1 and tagged vlan100, yet that ap D won't work. When I prepare a 4th port in the basement switches like the others - ap D would go online!
So, my guess is that I have overseen an obvious logical aspect that prevents my ap D to connect via switch D - can you help me out of this?
Edit: I've set up the basement switches via local management, while the roof switch is still cloud managed. Reason: Roof switch is 1 month old, I wanted to get it into operation quickly, so I went the clound mgmt way (I already regret it). The latter 3 switches I went the local way from the start.
Also, roof switch is working fine, providing lan to workplaces and voip phones and printers etc. Just the ap won't connect.
edit: so, my thesis is, due to the 3 switches A/B/C being managed locally and that D via cloud, I think somehow that particular AP15 had trouble getting its IP from D (the other 3 AP15 are connected to the A/B/C). Switching D from cloud to local management seems to have fixed it somehow.
------------------------------
Alexander Reichel
------------------------------