LC75: TP Link Omada Layer 3 Switch DHCP Relay, DHCP Reservation, DHCP Server Configuration
HTML-код
- Опубликовано: 19 авг 2024
- In this video, I am showing how to configure TP Link Omada Swith for DHCP Server, DHCP Relay, and DHCP Reservation
Written Guide: community.tp-l...
Layer 3 Switching (Walk Thru): • LC67: Layer 3 Switchin...
Layer 3 Switching (Step by Step): • LC67: Layer 3 Switchin...
Layer 3 Switching with DHCP Relay: • LC75: TP Link Omada La...
#arciesabode #omada #tplink
Index:
00:00 - Intro
===
Hello and welcome! This video is part of my adventure towards learning how to configure certain device, gadget, software, or whatever it may be. I hope that you learn from my failures, and of course, learn from my learnings!
For any correction or mistake, please post in the comments!
If you need technical assistance:
* Official Forum - community.tp-l...
* Official Tech Support - www.tp-link.co...
* Reddit - / tplink_omada
* Big YT Channels - www.youtube.co...
Products:
TL-ER-8411 - www.amazon.com...
TL-ER-707-M2 - www.amazon.com...
TL-ER7206 - www.amazon.com...
TL-ER605 - www.amazon.com...
SG-2210P - www.amazon.com...
OC-200 - www.amazon.com...
OC-300 - www.amazon.com...
EAP-610 - www.amazon.com...
SG-2210MP - www.amazon.com...
SG-3428 - www.amazon.com...
EAP-235 - www.amazon.com...
Omada SDN - www.tp-link.co...
OpenVPN - openvpn.net/
OpenVPN Client - openvpn.net/vp...
ZyXEL GS1900-16 - www.amazon.com...
Speedefy - www.amazon.com...
LAN Design and Concept (c) 2022 by Arcie’s Abode
You’re free to use the design and configuration in any of your videos/contents/documentations/articles (and the likes), the only thing I ask in return is to provide a link back in your content/documentation/article (and the likes) to my channel [copy/paste below]:
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
LAN Design and Configuration by Arcie’s Abode: / @deadmeats
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
The publication and information included in this video are not intended to substitute for consultation and working with IT professionals.
All the information in this video is for general information purpose only.
Arcie's Abode do not make any warranties about the safety, reliability, accuracy and completeness of the topics covered here.
Actions taken based on this video is at your own risk. Arcie's Abode will not be liable for any losses, or damages in connection with this video.
this is fantastic - really helpful as your other videos, I literally raised a query about this on omada forum yesterday. :)
would you mind just sharing a wiring diagram for this setup?
Hey there @HonzaOdPotoka, thanks for dropping by the channel and for the kind words. The physical wiring, can be seen at 01:25 (the black arrow lines). So it's ER605 SG2008. The SG2008 connects to all other Switches. You can see the cabling at the very start of the video as well, the top device is ER605, underneath it is the SG2008, they are linked via the red/orange cable; the green cables are uplink/downlink to all the switches!
Good hunting!
hey, congratulations on your channel. more informative, knowledgeable and helpful than tp-link customer support. I am sure you have the knowledge and expertise in the problem I have. I would be grateful if you could advise.
I have set up a multiVLAN network using your helpful videos and I am much grateful for that. The router is ER605, it has only one WAN connection, it is trunked to a TL-SG2008P which in turn connects 3 Omada EAPs. All is nicely integrated and controlled using OC200. I am trying to replace ER605 with another VLAN aware router (non-Omada non-TPLink), while preserving the VLANs on the switch and EAPs and also the control of OC200 over the switch and EAPs. The third party router is meant to provide internet connection, as well as DHCP and interVLAN firewall rules. Is this possible while preserving the control of OC200 over the switch and EAPs? I'm trying for days and I can't make it work unless the switch is disconnected from Omada environment and is set up in standalone mode (making OC200 redundant).
hey there @sorinlakatos6361, thanks for dropping by the channel. thank you for the kind words. i do not want to mislead you, i am not an expert with Omada (as I always put it out on all my videos) so I still recommend you go check with the "big channels" (search Omada in YT and these channels mostly offer paid technical support). Of course, you can still go with Omada Tech support (I know you mentioned you probably don't like them too much, but still...).
As for your issue, I am not sure if you can preserve your VLAN configuration because what you currently have there is a "Gateway VLAN Interface" and it only works because you have an Omada Gateway. You can re-create your VLANs as Layer2 only VLAN (see 9:41 of this video) and do the connection the old-school way. This means, if you have 3 VLANs, you will have a total of 4: VLAN 1 (untag/default), plus 3 other VLANs (tagged). Connect your 3rd party router to SG2008, making sure you are using the Profile "All" in the SG2008 uplink. Same thing for your EAPs, connect to SG2008 with Profile "All".
You can also use my other videos as reference where I used an Omada Gateway to connect to a non-Omada Switch (it is very similar, except, in reverse). Check this out ruclips.net/video/GwzFDOoaxig/видео.htmlsi=NUMWJw6Rxrt9SZas&t=259
Good hunting!!!
@deadmeats many thanks for your reply.
Actually, I connected a Netgear switch and integrated it with the Omada network (of course, without being able to adopt it in the controller environment) after watching your video that you referred to in your answer. And that's when I started thinking of replacing the TP-Link router with the third party one. So you're the fire starter 🤣 as The Prodigy would say.
I'm a bit confused about what the management VLAN implications are in my project. The default is the same as the main network 192.168.0.1/24, and the native VLAN1. I wonder if I would have to separate the management VLAN from the native (untagged) VLAN, to make sure the native VLAN is the same on the router as well as on the switch (VLAN1). This way the native VLAN is the same on the whole network, while the management VLAN is a different "channel". I'm not sure what the management VLAN does really, and what its connection and interaction is with the default Omada network. Any idea?
Anyway, keep up the good work, and thanks again for your efforts and postings. People like you help a lot people like me 🏆🏆🙌👍❤️
@@sorinlakatos6361 hey there, good to know the videos are helping you. Don't worry too much about the concept of "management VLAN", this is mostly a concern for enterprise network and not much for the home. In the most basic terms, in a huge company, they have a dedicated VLAN just for all network devices which is not VLAN 1. Omada offers such capability, but again, just use the default VLAN 1.
As for your case, VLAN 1 just means the default untagged VLAN. Meaning, if you are going to create a list of VLANs in your new router, just make sure that VLAN 1 is untagged because Omada network devices are expecting it to be untagged. If you are just learning about network, start small.
a) In your new router, create two VLANs, default VLAN 1 and, for the sake of example, VLAN 10. Make sure DHCP is enabled for both.
b) Make sure VLAN 1 is untagged and VLAN 10 is tagged
c) In your Omada switch, create a Layer2-only VLAN 10 (refer to 9:40)
d) Connect router to SG2008 (make sure the SG2008 port profile is set to "All")
e) Configure 1 port of SG2008 AS Profile VLAN 1, another port as Profile VLAN 10
f) Use a test PC, connect to either port, observe the IP you get.
Good hunting!
@@deadmeats millions of thanks. much appreciated you taking your time to look into my matter and give custom advice, rather than just throw in some links. Top man 👍👍👍
@@sorinlakatos6361 most welcome!
Hi this means that there is no way to get DHCP reservation work on a single VLAN when the switch is managed by Omada controller?
So basically i can reserve some ip for specific VLAN clients only when the switch is in stand-alone mode?
I thought i would find the "DHCP reserve service" under DEVICES -> SWITCH -> CONFIG -> SERVICES !!!!!
If i cannot adopt the switch i could not follow your guide LC73
hey there @beniaminoprofeta, welcome to my channel and thanks for dropping by. I am not sure how familiar you are with Omada so I will just suggest that if you have not done the basics Omada, that you watch those videos first (either my channel or others). If you are familiar with Omada, let me answer your inquires below:
a) there is no way to get DHCP reservation work on a single VLAN when the switch is managed by Omada controller? - No, you can still get DHCP reservation. At 3:27 I have shown where you can do DHCP Reservation in Controller Mode.
b) So basically i can reserve some ip for specific VLAN clients only when the switch is in stand-alone mode? No. At 3:27, I have shown DHCP reservation using Omada works. And at 5:34, I have shown a quick walk thru of how to do it. And at 9:09, I have shown how to do DHCP Reservation using a combination of Controller Mode and Stand Alone Mode.
c) I thought i would find the "DHCP reserve service" under DEVICES -> SWITCH -> CONFIG -> SERVICES !!!!! - I don't have control over it, you can request TP Link to add it,
d) If i cannot adopt the switch i could not follow your guide LC73 - You don't really need to have this configured in your network to be able to follow LC73. LC73 is about Switch Static routing and doesn't require a dedicated DHCP server for the Switch to work since you can always assign static IP on them as shown in various areas of the videos.
Hope that clears your inquires. Good hunting!
Very cool DBZ figures. Where you from?
hey @javajav3004 , thanks for dropping by the channel. Yeah, I love these DBZ figures. I am from East Coast, US of A :)
The problem about dhcp reservations is if the router is down there is no way to connect to your server, because they rely on dhcp server i have that issue on proxmox communicating with nfs that is on dhcp. Yes its very convenient on other devices, you dont need to go and get the physical devices tp set an ip but if a scenario happens like above happens you will wish that you set a static ip.😂
hey there @kylelaker539, I agree with you 100%, and that is why I mentioned in the intro that it is a "complimentary" way to configure it. This topic is mostly to address the concern of Omada users who lost the capability to do DHCP reservation when they moved to Layer 3 Switching. For Enterprise or Business, I doubt if anyone uses DHCP IP for any of their critical servers so DHCP reservation will either be a back up or not used at all.
Thanks for dropping by the channel and good hunting!
How can I create different vlans for multiple clients connected to the same port? Which device should I use? I would be very happy if you answer. I can not find
hey there @necatibilen4130, a switch port with multiple VLANs is normally referred to as "trunk" port. Traditionally, trunk port is used to connect between two switches. However, trunk ports can be used with non-switch devices as well for example, one cable going to your VoIP Phone and that phone have another port that goes to the PC. Because the switch port the Phone is connected to have 2 (or more) VLANs, the switch port can support both the Phone and the PC with just one port port on the switch.
If you are new to networking, I suggest you start with basics and there are many topics covering that in YT!
Good hunting!
Hi bro, I have two OC200, one i keep for spare. Anyway to link them together for HA/redudancy in case one fails?
hey there @allenperera6158 , thanks for dropping by the channel. I am not aware if that settings is available or can be configured. You can reach out to TP Link customer support (link below) and maybe they know how to configure such capability. In the meantime, I suggest you use a USB storage to back up your settings. You can set the Controller to do auto-back up settings.
Official Customer Support
www.tp-link.com/us/support/contact-technical-support/
Good hunting!
@@deadmeats thanks
@@allenperera6158 always welcome man!