SG3428XPP-M2 & OC200 not VLAN 1
Hi,
I have a big struggle with my X-mas gift (SG3428XPP-M2) which should replace my zyxel poe switch
so i had everything connected to my zyxel and added the SG3428XPP-M2 it was detected and adopted. But if I try to plug the oc200 to the SG3428XPP-M2 I loose connction/lock myself out
the zyxel has set PVID to 144 as this is my main/mgmt VLAN.
if I try this on the SG3428XPP-M2 im always cutting the branche im sitting on and lock myself out
what is the correct procedure to make VLAN 144 the mgmt VLAN for the switch and make it work with the oc200?
I feel like I missed some tiny but important detail and this makes me faining over and over again
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @ASD_AuZ
Thanks for posting in our business forum.
This article could be helpful.
How to configure Management VLAN in Omada SDN Controller (4.4.4 or above)
- Copy Link
- Report Inappropriate Content
thanks for your reply I found already this doc and tried to follow it even i don't have only the oc200, the switch and some EAP but not a gateway.
i also found in one doc what default vlan 1 can't be change... but i think this is the think i need to do... i'm verry confused by this... i thought i understand vlans but this make me feel i didnt unterstand it even partialy :(
- Copy Link
- Report Inappropriate Content
@ASD_AuZ the gateway is not needed. There are two basic config items to make it work. One is the PVID needs to be set to your management VLAN on the port that connects to your oc200 (set in the Port Profile). The second is that the management VLAN interface needs to exist on the switch with the Management VLAN option enabled (set in the switch's VLAN intrface config). After you confirm that you can access it via the management VLAN the default VLAN interface on the switch can be disabled. The configuration article shows this although the screen shots looked a little dated.
- Copy Link
- Report Inappropriate Content
Hi,
thanks for your reply
I maybe did it not the correct way but i got it working by changing the vlan ID of the "default" vlan to 144
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@ASD_AuZ , as long as you don't think you still have a management network...
Dealing with a management network is actually easier without a tp-link gateway because you don't have to tell the gateway where the controller is.
The article on MGMT VLAN is badly outdated. IME, batch config no longer allows you to set it.
And the UX is also quite different.
After you create the MGMT VLAN (not interface) in Site > Settings > Wired Networks > LAN, you need to prepare a port with the MGMT profile (to reconnect the OC after you've set the VLAN as MGMT for the switch).
Then click on the switch in Devices, go to the Config tab, VLAN Interface pane.
There, you need to enable the MGMT VLAN, edit it and enable Management VLAN. Apply then move the OC to the prepared port so the OC and switch can communicate again.
Note that if your OC and switch get IP via DHCP, you need to create an interface in your router to handle that for your management network and set up the uplink port of the switch as a trunk (All profile).
Or you can use compatible static IPs for each.
HTH
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 119
Replies: 6
Voters 0
No one has voted for it yet.