top of page
Writer's pictureSherry Wei

Endpoint Node and Service Node deployment requirements

Updated: Mar 4

This document describes the Endpoint Node and Service deployment requirements checklist.


An Endpoint Node or Service Node is a virtual machine downloaded from the Bumblebee Networks platform in .ova format as a single file. It deploys on a VMware hypervisor ESXi environment. Once deployed, it boots up and automatically registers to the Bumblebee platform. Neither endpoint node or service node require public IP addresses.


Alternatively, both Endpoint Node and Service Node can be hardwares delivered by Bumblebee Networks. In such case, virtual environment is not required.



Endpoint node and service node
Endpoint Node and Service Node


1. Endpoint Node deployment requirements checklist

​Endpoint Node deployment requirements

Details

  1. Hypervisor environments: VMware ESXi, Linux KVM or window's hyper-V on the host machine (Not required for hardware version)

​The default Endpoint Node virtual machine expects a VMware ESXi environment. For KVM and hyper-V, contact support@bumblebeenet.com for help

2. DHCP enabled. (Reserve the IP address on DHCP server once the Endpoint Node registers)

​The subnet where the Endpoint Node is deployed should have DHCP option enabled. The Endpoint Node obtains its IP address via DHCP

3. Outbound Internet access to *.bumblebeenet.com from the Endpoint Node

Open outbound TCP and UDP port 443. Source address: The IP of the Endpoint Node. Destination address: *.bumblebeenet.com Ports: TCP 443 and UDP 443

​4. Allow *.bumblebeenet.com for DNS resolution

​ If DNS filter is enabled for the site, allow DNS queries for *.bumblebeenet.com



2. Service Node deployment checklist


​Service Node deployment requirements

Details

  1. Hypervisor environment: VMware ESXi, Linux KVM or Window's hyper-V (Not required for hardware version)

​​The default Endpoint Node virtual machine expects a VMware ESXi environment. For KVM and hyper-V contact support@bumblebeenet.com for help.

2. DHCP enabled. (Reserve the IP address on the DHCP server once the Endpoint registers)

​​The subnet where the Endpoint Node is deployed should have DHCP option enabled. The Endpoint Node obtains its IP address via DHCP

3. Outbound Internet access to *.bumblebeenet.com from the Service Node

  • Open outbound TCP 443 and UDP 443 - 448

  • Source address: Service Node IP address

  • Destination address: *.bumblebeenet.com

  • Ports: TCP 443 and UDP 443 - 448

​4. Allow *.bumblebeenet.com for DNS resolution

​ If DNS filter is enabled for the site, allow DNS queries for *.bumblebeenet.com


3. Troubleshooting Tips

Follow the instructions on How to troubleshoot Endpoint Node or Service Node to make sure your node is successfully registered and ready for use.



4. Try out in other test environments

  • If you like to try out Endpoint Node or Service Node on your laptop or a lab environment, you can use vmware Workstation on a Window's server, vmware Workstation Pro on a Linux server or vmware Fusion on a MAC for Intel based processors. Note if in a lab environment you should remember to deploy the virtual machine in a Bridge mode as opposed to the default NAT mode so that it can interact with the rest of the lab hosts.

  • If you have a MAC on ARM processor, follow the instructions here to convert the .ova file to emulate ARM processor.

  • If you have other scenarios, contact support@bumblebeenet.com for help.



119 views0 comments

Comments


bottom of page