Omada SDN as service

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada SDN as service
Omada SDN as service
2021-01-23 17:45:38 - last edited 2021-01-23 17:46:49
Model: EAP245
Hardware Version: V3
Firmware Version: 5.0.0

I've got SDN set up as a service on Windows 10, which all starts well. However, even though the SDN starts, the 4 EAP245 I have remain disconnected. It's as if the service did not connect to the network? I can login to the web mgmt page and use all the functions etc but the devices show as disconnected.

 

If I launch the SDN as normal through the start menu, then everything works fine, all EAP245 adopt and connect.

 

My Omada controller version is 4.2.8. My EAP245 are v3 and on firmware 5.0.0.

 

Any ideas what makes the service start not connect?

 

In the logs, I see the below difference...

 

Main Administrator logged in to the controller from 0:0:0:0:0:0:0:1.

this is when i launch from the start menu, and everything works

Main Administrator logged in to the controller from 192.168.0.181. 

this is when i launch as a service, and eap245 don't connect

 

Thanks

 

0
0
#1
Options
3 Reply
Re:Omada SDN as service
2021-01-27 08:48:59

Dear @suh4ail,

 

I've got SDN set up as a service on Windows 10, which all starts well. However, even though the SDN starts, the 4 EAP245 I have remain disconnected. It's as if the service did not connect to the network? I can login to the web mgmt page and use all the functions etc but the devices show as disconnected.

 

When the controller shows the EAP is disconnected, it only indicates that the controller is unable to communicate with the EAP for more than 5 minutes. If you can get Internet access from the EAP's SSID, then the EAP is still connected to the network properly.

 

If I launch the SDN as normal through the start menu, then everything works fine, all EAP245 adopt and connect.

 

Not sure what may cause the issue, perhaps you could refer to the FAQ below to confirm it's properly configured as windows service.

How to Configure Omada Controller as a Windows Service(above Controller 4.1.5)

Get Started Here: https://community.tp-link.com/en/business/forum/topic/551684 https://community.tp-link.com/en/business/forum/topic/552406
0
0
#2
Options
Re:Omada SDN as service
2021-10-26 16:21:49

@suh4ail 

Wondering if you ever got this resolved?  I'm having the exact same symptoms.

 

To clarify, here are some knowns:

1) When I use the desktop icon and let the program start the service, my APs are connected and I can manage them.

2) When I run my service, Java and Mongod are both confirmed to be running. I can log in to the management console, but the devices show disconnected.

3) This does not affect connectivity of clients to the access points. Even with the NSSM-made service running, clients can access the network through the access points.

4) When using the desktop icon to start the service and reach the management console, the browser address is: http://localhost:8088.  Then it changes to https://localhost:8043  When I use my NSSM-made service and open the broswer, I use 127.0.0.1:8043  The IP address of my server also works. I only bring this up because you did.  IN any case, the address I use in the browser does not make a difference for the APs connecting.  It's all about which method is used to start the service. In other words, if I let the desktop icon start the service, I can access the management console from any of the addresses and the APs show connected.  And vice-versa.

5) I've been running my controller as a service for probably five years now, and editing the service parameters as needed as the controller has upgraded.

6) I've made notations in different logs to check differences in startup methods.  in the tp-link/controller/logs folder is logfile "mongod.log"  When I compare the log entries from NSSM-made service startup method versus the desktop icon startup method, they are very close to the same, but there are differences. I haven't parsed everything yet, but the NSSM-made service definitely seems to have more entries and has some errors in it.  I think this will be my next avenue of pursuit. 

7) I am running Java verision 1.8.0_301   The guide on the forums here discusses a previous version, but it's still 1.8.0 and I don't think it's the main cause.  I still might remove java and reinstall the older version for testing. 

8) The service guide on the forums starts out great.  But when it gets to the part about the alternate method, nothing is explained well and it doesn't match what I'm seeing.

9) I'm using EAP660HD APs.  I have two of them.  I've taken my older EAPs out of service for now so they are not part of the equation.

 

Thoughts:

a) The server.log file I think will be key.  Something is going on in the service startup that is not- allowing AP connections properly and there may be clues in the log.

b) I feel like there's something missing in the java calls when we create the service, like maybe we need to add arguments or environment tables. But I'm not fluent enough in any of this to know with confidence what I'm talking about.  I might get lucky and stumble upon something, but it's not likely.

c) I might start reading into the .jar files.

 

I'm using:

Windows Server 2012R2.

Omada Controller 4.4.6, downgraded to 4.4.4 with same symptom

Java 1.8.0_301

EAP 660 HD  x2

 

 

 

 

 

0
0
#3
Options
Re:Omada SDN as service
2022-02-09 00:03:11

Has there been a fix or at least an update to this issue? As of controller v5.0.30, this still happens. Devices already in the network are not detected when the controller is ran as a Windows service.

 

I found some difference in the server.log:

 

Here is the log when ran as a service:

 

02-09-2022 07:28:58.276 INFO [facade-msg-thread] [] c.t.s.f.s.FacadeMessageHandler(40): Device connector server started.
02-09-2022 07:28:58.277 INFO [main] [] c.t.s.o.s.t.SuccessExitTask(23): Omada Controller started
02-09-2022 07:28:58.277 INFO [facade-msg-thread] [] c.t.s.f.s.FacadeMessageHandler(40): Omada Controller started
02-09-2022 07:29:03.979 INFO [Thread-8] [] c.t.e.c.c.CloudClient(100): CloudClient is started.
02-09-2022 07:29:03.979 INFO [Thread-8] [] c.t.e.c.c.CloudClient(110): Connect SEF server automatically.
-
02-09-2022 07:29:04.893 INFO [Thread-8] [] c.t.e.c.c.n(194): The result of connection is true, service host is n-devs-smb.tplinkcloud.com, port is 443.
02-09-2022 07:29:04.895 INFO [Thread-8] [] c.t.e.c.c.CloudClient(114): Close connection to SEF server.
02-09-2022 07:29:04.903 INFO [Thread-11] [] c.t.e.c.c.n(407): ssl recv thread is stopped.
02-09-2022 07:29:04.930 INFO [Thread-8] [] c.t.e.c.c.CloudClient(127): Connect service server automatically, ConnectionType is PERSISTENT_CONNECTION.
-
02-09-2022 07:29:05.569 INFO [Thread-8] [] c.t.e.c.c.q(366): The result of connection is true.
-
02-09-2022 07:29:28.078 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.d.d.m.u.t.CheckDeviceFwTask(151): Start sync Cloud Users.
02-09-2022 07:29:28.310 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.d.d.m.u.t.CheckDeviceFwTask(92): Start checking last firmwares of managed devices.
02-09-2022 07:29:28.310 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.b.a(93): Checking Device Last Firmware...
02-09-2022 07:29:28.315 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.d.d.m.u.t.CheckDeviceFwTask(102): Checking last firmwares of managed devices succeed.

 

----------------------------------------------------------------------------------------------------------------------------------------------

And this is the log when ran normally:

 

02-08-2022 11:17:57.424 INFO [facade-msg-thread] [] c.t.s.f.s.FacadeMessageHandler(40): Device connector server started.
02-08-2022 11:17:57.425 INFO [main] [] c.t.s.o.s.t.SuccessExitTask(23): Omada Controller started
02-08-2022 11:17:57.426 INFO [facade-msg-thread] [] c.t.s.f.s.FacadeMessageHandler(40): Omada Controller started
02-08-2022 11:18:00.911 INFO [Thread-8] [] c.t.e.c.c.CloudClient(100): CloudClient is started.
02-08-2022 11:18:00.912 INFO [Thread-8] [] c.t.e.c.c.CloudClient(110): Connect SEF server automatically.
02-08-2022 11:18:01.641 INFO [discovery-work-group-0] [] c.t.s.o.m.d.d.m.a.a(302): MANAGED_BY_OWN Device 3C-84-6A-52-02-91 on omadac dfd8bf3966a630ae8d8557f2df06504d is discoveried.
02-08-2022 11:18:01.988 INFO [Thread-8] [] c.t.e.c.c.n(194): The result of connection is true, service host is n-devs-smb.tplinkcloud.com, port is 443.
02-08-2022 11:18:01.992 INFO [Thread-8] [] c.t.e.c.c.CloudClient(114): Close connection to SEF server.
02-08-2022 11:18:01.994 INFO [Thread-11] [] c.t.e.c.c.n(407): ssl recv thread is stopped.
02-08-2022 11:18:02.008 INFO [Thread-8] [] c.t.e.c.c.CloudClient(127): Connect service server automatically, ConnectionType is PERSISTENT_CONNECTION.
02-08-2022 11:18:02.263 INFO [discovery-work-group-2] [] c.t.s.o.m.d.d.m.a.a(302): MANAGED_BY_OWN Device 3C-84-6A-F7-DE-DC on omadac dfd8bf3966a630ae8d8557f2df06504d is discoveried.
02-08-2022 11:18:02.371 INFO [Thread-8] [] c.t.e.c.c.q(366): The result of connection is true.
02-08-2022 11:18:03.568 INFO [discovery-work-group-3] [] c.t.s.o.m.d.d.m.a.a(302): MANAGED_BY_OWN Device 3C-84-6A-F7-DD-B0 on omadac dfd8bf3966a630ae8d8557f2df06504d is discoveried.
02-08-2022 11:18:04.015 INFO [discovery-work-group-5] [] c.t.s.o.m.d.d.m.a.a(302): MANAGED_BY_OWN Device 60-32-B1-12-E6-18 on omadac dfd8bf3966a630ae8d8557f2df06504d is discoveried.
02-08-2022 11:18:09.435 INFO [adopt-work-group-14] [] c.t.s.o.m.d.d.m.a.c(157): send empty setting to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-52-02-91)
02-08-2022 11:18:09.440 INFO [adopt-work-group-3] [] c.t.s.o.m.d.d.m.a.c(157): send empty setting to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DD-B0)
02-08-2022 11:18:09.447 INFO [adopt-work-group-2] [] c.t.s.o.m.d.d.m.a.c(157): send empty setting to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(60-32-B1-12-E6-18)
02-08-2022 11:18:09.454 INFO [adopt-work-group-0] [] c.t.s.o.m.d.d.m.a.c(157): send empty setting to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DE-DC)
02-08-2022 11:18:09.503 INFO [adopt-work-group-2] [] c.t.s.o.m.d.d.m.m.d(640): refreshApCredential for OmadacId(dfd8bf3966a630ae8d8557f2df06504d) child[DeviceMac(60-32-B1-12-E6-18)] parent[DeviceMac(3C-84-6A-F7-DE-DC)]
02-08-2022 11:18:09.503 INFO [adopt-work-group-2] [] c.t.s.o.m.d.d.m.m.d(572): sendAddCommand[child=DeviceMac(60-32-B1-12-E6-18)] to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DE-DC), refreshCredential true
02-08-2022 11:18:09.506 INFO [adopt-work-group-3] [] c.t.s.o.m.d.d.m.m.d(640): refreshApCredential for OmadacId(dfd8bf3966a630ae8d8557f2df06504d) child[DeviceMac(3C-84-6A-F7-DD-B0)] parent[DeviceMac(3C-84-6A-F7-DE-DC)]
02-08-2022 11:18:09.506 INFO [adopt-work-group-3] [] c.t.s.o.m.d.d.m.m.d(572): sendAddCommand[child=DeviceMac(3C-84-6A-F7-DD-B0)] to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DE-DC), refreshCredential true
02-08-2022 11:18:09.538 INFO [adopt-work-group-2] [] c.t.s.o.m.d.d.m.m.s.e(796): send setMsg to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DE-DC), status is PROVISIONING, no need sync full config, cache it
02-08-2022 11:18:09.648 INFO [manage-work-group-4] [] c.t.s.o.m.d.d.m.i.a(96): got first inform of OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-52-02-91)
02-08-2022 11:18:09.737 INFO [adopt-work-group-3] [] c.t.s.o.m.d.d.m.m.s.e(796): send setMsg to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DE-DC), status is PROVISIONING, no need sync full config, cache it
02-08-2022 11:18:09.843 INFO [manage-work-group-5] [] c.t.s.o.m.d.d.m.i.a(96): got first inform of OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DE-DC)
02-08-2022 11:18:09.854 INFO [manage-work-group-8] [] c.t.s.o.m.d.d.m.i.a(96): got first inform of OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DD-B0)
02-08-2022 11:18:09.870 INFO [manage-work-group-9] [] c.t.s.o.m.d.d.m.i.a(96): got first inform of OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(60-32-B1-12-E6-18)
02-08-2022 11:18:09.889 INFO [manage-work-group-6] [] c.t.s.o.m.d.d.m.i.d(169): first inform send same version config to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-52-02-91)
02-08-2022 11:18:09.891 INFO [manage-work-group-10] [] c.t.s.o.m.d.d.m.i.d(169): first inform send same version config to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DD-B0)
02-08-2022 11:18:09.891 INFO [manage-work-group-7] [] c.t.s.o.m.d.d.m.m.s.e(577): start send cached set msg for provision, OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DE-DC)
02-08-2022 11:18:09.926 INFO [manage-work-group-11] [] c.t.s.o.m.d.d.m.i.d(169): first inform send same version config to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(60-32-B1-12-E6-18)
02-08-2022 11:18:09.955 INFO [manage-work-group-7] [] c.t.s.o.m.d.d.m.m.s.e(614): finish send cached set msg for provision, OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DE-DC)
02-08-2022 11:18:09.955 INFO [manage-work-group-7] [] c.t.s.o.m.d.d.m.i.d(169): first inform send same version config to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DE-DC)
02-08-2022 11:18:09.974 INFO [manage-work-group-15] [] c.t.s.o.m.d.p.t.c(129): Device 3C-84-6A-F7-DD-B0 OmadacId(dfd8bf3966a630ae8d8557f2df06504d) changed to status CONNECTED, which don't need to handle.
02-08-2022 11:18:09.977 INFO [manage-work-group-14] [] c.t.s.o.m.d.p.t.c(129): Device 3C-84-6A-F7-DE-DC OmadacId(dfd8bf3966a630ae8d8557f2df06504d) changed to status CONNECTED, which don't need to handle.
02-08-2022 11:18:09.977 INFO [manage-work-group-13] [] c.t.s.o.m.d.p.t.c(129): Device 60-32-B1-12-E6-18 OmadacId(dfd8bf3966a630ae8d8557f2df06504d) changed to status CONNECTED, which don't need to handle.
02-08-2022 11:18:09.977 INFO [manage-work-group-12] [] c.t.s.o.m.d.p.t.c(129): Device 3C-84-6A-52-02-91 OmadacId(dfd8bf3966a630ae8d8557f2df06504d) changed to status CONNECTED, which don't need to handle.
02-08-2022 11:18:09.980 INFO [manage-work-group-0] [] c.t.s.o.m.d.d.m.d.a.M(94): syncConfigurationForSameVersion to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(60-32-B1-12-E6-18), result:SendDeviceMsgResult(success=true, deviceResponse=com.tplink.smb.omada.device.manage.message.body.manage.BaseConfigRespBody@1e6edde)
02-08-2022 11:18:10.035 INFO [async-business-pool-1] [] c.t.s.o.m.d.d.m.m.s.e(539): receive sendForCacheAsync watch result of OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DE-DC) BusinessId(topic=smb_omada_business_918310b9-db25-4901-920e-03ef2de3492d, id=dfd8bf3966a630ae8d8557f2df06504d_3C-84-6A-F7-DE-DC_1), result:{"sequenceId":1,"errcode":0,"configVersion":593}
02-08-2022 11:18:09.992 INFO [manage-work-group-2] [] c.t.s.o.m.d.d.m.d.a.M(94): syncConfigurationForSameVersion to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-52-02-91), result:SendDeviceMsgResult(success=true, deviceResponse=com.tplink.smb.omada.device.manage.message.body.manage.BaseConfigRespBody@1e6edde)
02-08-2022 11:18:09.999 INFO [manage-work-group-1] [] c.t.s.o.m.d.d.m.d.a.M(94): syncConfigurationForSameVersion to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DD-B0), result:SendDeviceMsgResult(success=true, deviceResponse=com.tplink.smb.omada.device.manage.message.body.manage.BaseConfigRespBody@1e6edde)
02-08-2022 11:18:10.037 WARN [async-business-pool-1] [] c.t.s.o.m.d.d.m.m.d(595): refreshCredential for OmadacId(dfd8bf3966a630ae8d8557f2df06504d) child[DeviceMac(60-32-B1-12-E6-18)] parent[DeviceMac(3C-84-6A-F7-DE-DC)] failed
02-08-2022 11:18:10.037 INFO [manage-work-group-4] [] c.t.s.o.m.d.d.m.d.a.M(94): syncConfigurationForSameVersion to OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DE-DC), result:SendDeviceMsgResult(success=true, deviceResponse=com.tplink.smb.omada.device.manage.message.body.manage.BaseConfigRespBody@1e87998)
02-08-2022 11:18:10.037 INFO [async-business-pool-2] [] c.t.s.o.m.d.d.m.m.s.e(539): receive sendForCacheAsync watch result of OmadacId(dfd8bf3966a630ae8d8557f2df06504d) DeviceMac(3C-84-6A-F7-DE-DC) BusinessId(topic=smb_omada_business_918310b9-db25-4901-920e-03ef2de3492d, id=dfd8bf3966a630ae8d8557f2df06504d_3C-84-6A-F7-DE-DC_2), result:{"sequenceId":2,"errcode":0,"configVersion":594}
02-08-2022 11:18:10.037 WARN [async-business-pool-2] [] c.t.s.o.m.d.d.m.m.d(595): refreshCredential for OmadacId(dfd8bf3966a630ae8d8557f2df06504d) child[DeviceMac(3C-84-6A-F7-DD-B0)] parent[DeviceMac(3C-84-6A-F7-DE-DC)] failed
02-08-2022 11:18:18.125 INFO [http-nio-8088-exec-1] [] c.t.s.o.p.w.c.b(235): Handling GET /portal/entry... PortalEntranceQueryDTO :PortalEntranceQueryDTO(clientMac=D8-B0-53-1C-F9-EC, clientIp=192.168.0.111, apMac=60-32-B1-12-E6-18, osgMac=null, ssid=The Happy Shop Wifi, radioId=1, vid=null, timestamp=1644290297, originUrl=connect.rom.miui.com/generate_204, serverLocation=192.168.0.2, serverPort=8088)
02-08-2022 11:18:20.023 WARN [manage-work-group-8] [] c.t.s.o.m.d.d.m.i.a.UpdateApImageCommonInfoService(112): omadacId:OmadacId(dfd8bf3966a630ae8d8557f2df06504d), siteId:SiteId(61bc8337da133b16d0b5ffb9), deviceMac:3C-84-6A-52-02-91, apImage wlanId is null, need query database
02-08-2022 11:18:20.097 WARN [monitor-roaming-pool-0] [] c.t.s.o.m.r.p.e.a.b(182): First reported roaming pat stat is null, ap 3C-84-6A-F7-DD-B0, omadacId=dfd8bf3966a630ae8d8557f2df06504d, siteId=61bc8337da133b16d0b5ffb9
02-08-2022 11:18:20.434 WARN [manage-work-group-14] [] c.t.s.o.m.d.d.m.i.a.UpdateApImageCommonInfoService(112): omadacId:OmadacId(dfd8bf3966a630ae8d8557f2df06504d), siteId:SiteId(61bc8337da133b16d0b5ffb9), deviceMac:3C-84-6A-F7-DE-DC, apImage wlanId is null, need query database
02-08-2022 11:18:20.444 WARN [monitor-roaming-pool-2] [] c.t.s.o.m.r.p.e.a.b(182): First reported roaming pat stat is null, ap 3C-84-6A-F7-DE-DC, omadacId=dfd8bf3966a630ae8d8557f2df06504d, siteId=61bc8337da133b16d0b5ffb9
02-08-2022 11:18:20.724 WARN [monitor-roaming-pool-3] [] c.t.s.o.m.r.p.e.a.b(182): First reported roaming pat stat is null, ap 60-32-B1-12-E6-18, omadacId=dfd8bf3966a630ae8d8557f2df06504d, siteId=61bc8337da133b16d0b5ffb9
02-08-2022 11:18:27.070 INFO [log-device-status-push-info-event-pool-0] [] c.t.s.o.l.c.b(50): Start pushing new connected devices.
02-08-2022 11:18:27.070 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.d.d.m.u.t.CheckDeviceFwTask(151): Start sync Cloud Users.
02-08-2022 11:18:27.303 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.d.d.m.u.t.CheckDeviceFwTask(92): Start checking last firmwares of managed devices.
02-08-2022 11:18:27.304 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.b.a(93): Checking Device Last Firmware...
02-08-2022 11:18:27.748 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.d.d.m.u.t.CheckDeviceFwTask(102): Checking last firmwares of managed devices succeed.

 

 

 

0
0
#4
Options