Contention issue between Omada and local router view

Contention issue between Omada and local router view

Contention issue between Omada and local router view
Contention issue between Omada and local router view
a week ago - last edited a week ago
Model: ER707-M2  
Hardware Version: V1
Firmware Version: 1.2.3 Build 20240822 Rel.52946

Problem statement:  Omada Cloud Essential management of a router locks admin out if connectivity is lost.  

 

Router is either Omada managed or locally managed.  Switching between the two requries wipe and start again.  Using Cloud Essentials (controller-less) for a simple network creates a contention issue, in that connection issues (setting up PPoE, vs Dynamic) are only visible through Cloud Essentials while a connection is up and operating.  Trying to troubleshoot intermittent connectivity issues is not possible through the cloud while the connection is down.  Until a connection is up and existing to Omada Cloud, there is no web visibility possible locally.  Logging into the router directly yields NO status info, and the message that the device is managed by Omada.  A factory reset is required to manage locally.   

 

Options: 

  • Get connectivity up and confirmed locally before switch to Omada.  Then finish configuring the device through Omada.  
  • Be careful to have secondary connectivity enabled.  PPPoE on WAN1 and Dynamic on WAN2.  Else you lock yourself out of the router.  Example, PPPoE through ISP modem in BRIDGE mode, but backup is dynamic IP and double NAT through ISP modem.  
  • Hardware or Software controller is required for local admin of the router in Omada controlled mode.  Else no visibility at all, no getting into the router if connectivity down.  

 

Consider:

  • Can SSH be used to obtain local access to a router?
  • Even under Omada Cloud control, logging into the router locally should provide at least view access to connection status and logs.  Ability to adjust connection to get back up and operating.  
  • Ability to see WAN connection status.  I think others have complained that there is no simple way to view WAN connection info, IP, etc.  Locally managed GW does provide connection status view.  Just to confirm WAN address is a PITA and not straightforward.  

 

Using Omada Remote Control Terminal Session, >enable  #config (config)# a list of SHOW commands are available.  Some insight is provided, but it is a circuitious route... 

(config)#show interface switchport 2

Port name..................2.5G WAN/LAN2

Belonged vlan..............35

Pvid.......................35

Vlan35 config

Vlan type..................wan

Routing Interface Status...UP

Primary IP Address.........184.147.64.000/255.255.255.255

MAC Address................B0-19-21-CB-AA-AA

Proto......................pppoe

Mtu........................1492

Bandwidth..................2500kbps

Uplink.....................1000000kbps

Downlink...................1000000kbps

Default Gateway............142.124.36.203

Primary DNS................67.69.235.1

Secondary DNS..............0.0.0.0

 

Thanks!  

  0      
  0      
#1
Options
1 Reply
Re:Contention issue between Omada and local router view
Thursday

Hi @RF_Dude 

Thanks for posting in our business forum.

RF_Dude wrote

Problem statement:  Omada Cloud Essential management of a router locks admin out if connectivity is lost.  

 

Router is either Omada managed or locally managed.  Switching between the two requries wipe and start again.  Using Cloud Essentials (controller-less) for a simple network creates a contention issue, in that connection issues (setting up PPoE, vs Dynamic) are only visible through Cloud Essentials while a connection is up and operating.  Trying to troubleshoot intermittent connectivity issues is not possible through the cloud while the connection is down.  Until a connection is up and existing to Omada Cloud, there is no web visibility possible locally.  Logging into the router directly yields NO status info, and the message that the device is managed by Omada.  A factory reset is required to manage locally.   

 

Briefly summarize this paragraph, you'd face the same issue on every router if they adopt and manage in the same way.

 

RF_Dude wrote

 

Consider:

  • Can SSH be used to obtain local access to a router?
  • Even under Omada Cloud control, logging into the router locally should provide at least view access to connection status and logs.  Ability to adjust connection to get back up and operating.  
  • Ability to see WAN connection status.  I think others have complained that there is no simple way to view WAN connection info, IP, etc.  Locally managed GW does provide connection status view.  Just to confirm WAN address is a PITA and not straightforward.  

 

The system always provides the SSH but you need to enable the access before you try to access it via the SSH.

 

SSH does not generate the backup. The system access is not unrestricted. I mean access the /etc/ and the trees of the LINUX. As you are aware of that if you SSH to any LINUX or similar machines, they generate the log in the /temp/ or other paths. We do not offer any of the solutions or methods for getting full access.

Getting full access without the technical support and modified system leading to boot issues, are not under the warranty.

 

Submit a request.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  1  
  1  
#2
Options