ES210X-M2 not showing I.P addresses when adopted in the software controller
Good Day,
I recently purchased an ES210X-M2 switch, upon adopting it in the software controller (windows based) I am unable to see the IP addresses with the devices connected to the switch. I only see their MAC addresses, if I leave the switch in standalone mode the IP addresses shows up fine but the topology is messed up. Does anyone know a fix for this or what the issue is?
I recently purchased this, if there's no fix I'll like to return it and get another one than can work.
My network is pretty simple: ER706W>SX3008F>ES210X-M2
Thanks.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@J_D_42 In controller mode, that feature is supported on Access Switches and above. You can find equivalent models here.
Access | TP-Link
- Copy Link
- Report Inappropriate Content
NeilR_M wrote
@J_D_42 In controller mode, that feature is supported on Access Switches and above. You can find equivalent models here.
Access | TP-Link
@NeilR_M So I'm confused as to why this information isn't clearly stated, it would make a drastic input in decision making before purchase. It's also very silly to not have a feature like that which should be a standard feature, for a switch. Very poor on TP-link's part, so what am I supposed to do now with this switch? Can I return it? What's the procedure for this? Can this be rectified in a feature update?
Would this switch carry the feature? SG3210X-M2 or SG2210XMP-M2 or TL-SG2210MP?
Very confusing.
- Copy Link
- Report Inappropriate Content
@J_D_42 I completely understand; it looks like we do have a feature comparison article for these devices, but I can pass some feedback along to clarify the wording on the feature table.
With regards to next steps, I would recommend returning and going with either of the options you listed, as both will support the feature you are looking for. As for whether or not it will be fixed in a future update, unfortunately, no, it appears to be a chipset limitation on the switches.
- Copy Link
- Report Inappropriate Content
NeilR_M wrote
@J_D_42 I completely understand; it looks like we do have a feature comparison article for these devices, but I can pass some feedback along to clarify the wording on the feature table.
With regards to next steps, I would recommend returning and going with either of the options you listed, as both will support the feature you are looking for. As for whether or not it will be fixed in a future update, unfortunately, no, it appears to be a chipset limitation on the switches.
Ok thanks for the feedback, in the comparison chart I am seeing this at the end:
PS: 1. Agile switch can't show client IP, unless client support and enable LLDP.
2. The number of clients reported by the Agile switch to the Omada Controller is max 4/ports, if clients number exceeds this limit, it will not show at Controller client list.
can you explain a bit further? especially the ""Omada Controller is max 4/ports"?
Is this the information that points out the capability of the client IP reporting:
- Access switches also support many other critical features missing from the Agile series, such as LACP (for link aggregation), MSTP (advanced spanning tree), Static Routing, DHCP Server/Relay, and IP Interfaces.
Also, this page: https://community.tp-link.com/en/business/forum/topic/845926
has different information to this page: https://store.omadanetworks.com/blogs/news/agile-switches-vs-access-switches-which-omada-switch-do-you-need
at the end of the table.
With this switch: SG2210XMP-M2, would i be able to have all ports show up when in use with their IP address information as well as the POE information in the controller?
Please clarify for better understanding.
- Copy Link
- Report Inappropriate Content
NeilR_M wrote
@J_D_42 I completely understand; it looks like we do have a feature comparison article for these devices, but I can pass some feedback along to clarify the wording on the feature table.
With regards to next steps, I would recommend returning and going with either of the options you listed, as both will support the feature you are looking for. As for whether or not it will be fixed in a future update, unfortunately, no, it appears to be a chipset limitation on the switches.
Hello Neil. any feedback on my post above?
- Copy Link
- Report Inappropriate Content
@J_D_42 Perfect timing, I actually just got the information. Regarding those notes, what that second point means is that the number of clients reported by the switch to the Omada Controller is 4 clients per switch port, so it can't report any more clients after that.
Regarding the Access feature list, I believe that IP Interfaces is meant to specify that feature. However, they are still looking into actively developing the feature for those switches in order to get around that chipset limitation. I unfortunately don't have any estimate as to when it will be released, but of course, will be happy to break the news when it is!
Lastly, regarding the SG2210XMP-M2, yes, you should be able to see all that information in the controller. Please let me know if I can clarify any further, but I hope this answered your questions!
- Copy Link
- Report Inappropriate Content
NeilR_M wrote
@J_D_42 Perfect timing, I actually just got the information. Regarding those notes, what that second point means is that the number of clients reported by the switch to the Omada Controller is 4 clients per switch port, so it can't report any more clients after that.
Regarding the Access feature list, I believe that IP Interfaces is meant to specify that feature. However, they are still looking into actively developing the feature for those switches in order to get around that chipset limitation. I unfortunately don't have any estimate as to when it will be released, but of course, will be happy to break the news when it is!
Lastly, regarding the SG2210XMP-M2, yes, you should be able to see all that information in the controller. Please let me know if I can clarify any further, but I hope this answered your questions!
Ha! Great information, it makes things so much clearer. I'm tryng to understand how Tp-link describes their feature set, for clarification:
(1) Regarding those notes, what that second point means is that the number of clients reported by the switch to the Omada Controller is 4 clients per switch port, so it can't report any more clients after that.
So, for this part, if the switch has 3 ports, the maximum is 4 clients per port which is 12 clients max?
(2) Regarding the Access feature list, I believe that IP Interfaces is meant to specify that feature. However, they are still looking into actively developing the feature for those switches in order to get around that chipset limitation. I unfortunately don't have any estimate as to when it will be released, but of course, will be happy to break the news when it is!
This is excellent news! This switch is an excellent device, I wanted to add a POE switch in addition to this, really didn't want to replace it with the POE one. I'll hold onto it for a while, I wish the team luck in this venture for a speedy resolve. The Ip Interfaces make sense now, for some reason i thought it meant DNS resolve for naming.
(3) Lastly, regarding the SG2210XMP-M2, yes, you should be able to see all that information in the controller. Please let me know if I can clarify any further, but I hope this answered your questions!
Ok great! I'll look into adding this device to my topology and yes my questions are answered.
Great support by Tp-link, thanks for the updates!
- Copy Link
- Report Inappropriate Content
@J_D_42 Regarding 1, yes, that appears to be correct.
Good luck with your network!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 293
Replies: 8
Voters 0
No one has voted for it yet.