top of page

How to troubleshoot Endpoint Node or Service Node

Updated: Jan 30

Endpoint Node or Service Node are virtual machines deployed in on-premise location. They host Endpoints and App Services for remote networks to access applications on-prem. Once deployed, they registers with the Bumblebee Networks automatically. You should see them listed on Endpoint Nodes page or Service Nodes page in a "registered" admin state and "up" Op state.


To troubleshoot an Endpoint Node or Service Node when you have trouble bringing them up, follow these steps. For simplicity, only the name Node is used for the rest of the document.


Step 1 in troubleshooting Endpoint or Service Node) Make sure DHCP is configured (troubleshooting a node)

The Node requires a DHCP environment where it obtains its primary IP address automatically. There is no work around if DHCP is not configured.


You should find its IP address at the virtual machine console, it looks similar to the screen shot below. (Reserve the IP address once the node boots up.)



Troubleshoot Endpoint Node or Service Node
Node bootup screen


Step 2. Make sure *.bumblebeenet.com is reachable on both TCP port 443 and UDP ports 443 - 448

While the Node does not have a public IP address, it requires outbound access to *.bumblebeenet.com on both TCP port 443 and UDP ports range 443 - 448.


Once the Node obtained its IP address, go to http://node_primary_ip:8080 to view diagnostics. The diagnostics page shows if the connection to Bumblebee Networks is successful. If it is not, it shows what the problem is.



Troubleshoot Endpoint Node and Service Node
Node Diagnostics

Step 3. (last resort) Contact support

If you still help, contact support@bumblebeenet.com

29 views0 comments

Comments


bottom of page