Switch getting multiple IPs assigned in router?
Replaced AP and switches with Omada products. Omada controller running on RPI4. Switch and 2 EAP 670 adopted and configured in controller.
Router is not TP-Link but a Peplink Balance 20x. Multiple vlans setup in the router and switch .. management vlan is set and all is working.
However, I'm seeing the POE Switch in my router client list with different IPs, 1 for each VLAN. Is this expected? This is not something i was seeing with Peplink APs.
I have trunk profiles for all vlans assigned to the EAP ports on the switch, and the uplink port to router.
All Vlan interfaces are also enabled in the switch config.. a little confused about this config.. should only the management vlan interface be enabled here? This may explain why I' seeing multiple IPs.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @stego
Thanks for posting in our business forum.
stego wrote
@Clive_A Thanks for the quick reply.
So I disabled the vlan interfaces in the switch config except for the management vlan (.77)
Now I no longer see each of vlan IP assignments for the switch and only see the DHCP reservation I setup in my .77 subnet for the switch management clan. Each EAP gets a dhcp reservation in the same management vlan along with controller.
Just wondering the purposes of disabling/enabling VLAN interfaces in the actual switch itself. Doesn't seem to affect routing.
I assume that you mean the VLAN interface section on the config page? That does not affect anything and is used for the DHCP service if you use the switch as a server. See this as a reference: How to Set Up Switch as DHCP Server on Omada SDN Controller
- Copy Link
- Report Inappropriate Content
Hi @stego
Thanks for posting in our business forum.
Here's a question from me, will this IP redirect to the page of the switch web GUI? I think not.
So, let's say you have an IP address for each VLAN interface you created, you should be accessible in that VLAN because you have trunked it. But what strange and does not make sense is that you only have one PVID and which represents the VLAN to the switch it belongs to.
I would assume that it is a display problem on your router client list. Only one VLAN IP is accessible to the switch GUI. And it is an untagged VLAN.
- Copy Link
- Report Inappropriate Content
@Clive_A Thanks for the quick reply.
So I disabled the vlan interfaces in the switch config except for the management vlan (.77)
Now I no longer see each of vlan IP assignments for the switch and only see the DHCP reservation I setup in my .77 subnet for the switch management clan. Each EAP gets a dhcp reservation in the same management vlan along with controller.
Just wondering the purposes of disabling/enabling VLAN interfaces in the actual switch itself. Doesn't seem to affect routing.
- Copy Link
- Report Inappropriate Content
Hi @stego
Thanks for posting in our business forum.
stego wrote
@Clive_A Thanks for the quick reply.
So I disabled the vlan interfaces in the switch config except for the management vlan (.77)
Now I no longer see each of vlan IP assignments for the switch and only see the DHCP reservation I setup in my .77 subnet for the switch management clan. Each EAP gets a dhcp reservation in the same management vlan along with controller.
Just wondering the purposes of disabling/enabling VLAN interfaces in the actual switch itself. Doesn't seem to affect routing.
I assume that you mean the VLAN interface section on the config page? That does not affect anything and is used for the DHCP service if you use the switch as a server. See this as a reference: How to Set Up Switch as DHCP Server on Omada SDN Controller
- Copy Link
- Report Inappropriate Content
@Clive_A Thanks yes the vlan interface in the switch config.
My understanding though is this needs to be enabled to set a custom management vlan ID which I do. I enabled the management VLAN intereface only, but left the DHCP configuration to "none".
I set a DHCP reservation in my router for all my devices in the management VLAN and they're getting that IP assigned correctly. (Omada controller, 2 switches and 2 EAPs)
I've now added a second switch to the mix (SG2218) with LAGG for uplink and all seems to be working correctly.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 283
Replies: 4
Voters 0
No one has voted for it yet.