1. Shipping ChiefNET CPE Devices to Customers
ChiefNET devices are shipped to the customers using the following simple steps.
- Obtain a list of locations and the number of devices
- For each location, find out if the customer has a requirement for static IP address. Though it is possible to change this at a customer site, ChiefNET can configure this in advance before shipping to the customers. If there is no static IP address requirement, ChiefNET is, as a default, configured to obtain IP address using DHCP on the WAN ports, from the ISP-router.
- For each location, as the device is prepared by the ChiefNET team (on ChiefNET premises), record the mac-address, device model, serial number, on the master inventory spreadsheet. The IP address may change over time, and it is important that these customer inventory is kept up to date. The inventory spreadsheet is kept on SharePoint. This is accessible only to the ChiefNET team.
- Inform the customers to ensure that the mac-address/IP-address combination is allowed through their firewall. This is the single-most common impediment to a smooth installation of ChiefNET.
- Check if the backend services need to be installed on cloud, on premises or as a hybrid.
The above steps are essential to get the devices powered up on-site.
For each customer, the on-cloud backend is pre-installed before shipping the CPE devices to the customers. In this case, the device immediately connects itself to the configured Cloud-SDWAN tunnel and to the other branches/HQ/sites immediately.
For some customers, the backend support needs to be built on-site/on-prem. This is offered as a one-time service by ChiefNET.
1.1 HA Requirement for CPE Devices
Some locations require high-availability or redundancy support for the CPE devices. It is possible to add a standby-devices to an existing installation where there is only one device.
1.2 Device Replacement
It is also possible to replace an existing device entirely with a new device. Upon unexpected failures or environmental problems or disasters like flood and fire, we may have to ship a new device to the customer. ChiefNET backend includes the ability to immediately reconfigure a new device identical to the damaged device.
The "Device Replacement" feature is accessible only to the 'superadmin' i.e. the ChiefNET support team only. It is not available to the customers.
1.3 Deployment at the Customer Site
As soon as the device is
- powered up
- WAN port is connected to the ISP router
the device becomes visible on the ChiefNET Orchestrator as ONLINE.
If the device is not reported ONLINE, ensure that the customer's firewall configuration is updated. This is the single most common impediment to a smooth installation of ChiefNET.
In some cases, ChiefNET is connected to the ISP router and that is usually not an issue. These ISP routers by default act as DHCP servers. ChiefNET's WAN ports act as DHCP clients. Once ChiefNET's WAN ports acquire the IP address, ChiefNET establishes the management layer connectivity with the Orchestrator.
In some cases, ChiefNET is connected to the firewall, which is then connected to the ISP router. In this case, the firewall may have to be configured or reconfigured to allow ChiefNET's outgoing connection.
No ports need to be opened on the firewall from the WAN/Internet side. The firewalls only need to allow ChiefNET's outgoing connections.
1.4 ChiefNET's LAN and WAN Subnets
The LAN and WAN subnets of ChiefNET need to be distinct, and non-overlapping. It is an insecure network configuration to keep those identical or overlapping.
In some cases, customers might not want to connect ChiefNET's WAN port to the Internet side. In this case, ChiefNET's LAN port needs to be connected, but ths is NOT a supported configuration. It is insecure to share a subnet between the LAN and the WAN. ChiefNET does not support it. If necessary, an additional router will need to be shipped to the customer to create a LAN-WAN topology each with a different subnet. This will need to be added to the customer's PO.