3. Configure and Use ChiefNET CPE
This page describes how to configure the ChiefNET CPE for most general applications or deployments. Read the frequently asked questions as well for answers that point to the appropriate sections in the documentation.
3.1 Prerequisites
All configuration is done using the Orchestrator WebUI available at https://chiefnet.yavar.in This will soon change to https://prod.chiefnet.io.
The physical device (or the virtual CPE or the cloud CPE) is in contact with the Orchestrator and the device status is ONLINE.
Note that a ChiefNET CPE may be configured in advance, even before you have received the device. When you place the order for the ChiefNET CPE, it is prepared in the factory, and it is pre-provisioned on the ChiefNET Network Orchestrator.
3.2 Initial User Accounts
When a new customer signs on,
- a new "Organization" is created
- a user account is using the email address of a responsible person from the customer organization
This account is used to log into the Orcehstrator WebUI, using OTP to their email. This can be a personal email, but it is highly discouraged. This should be the corporate email address.
This account has the privileges of an administrator, also known as, 'a customer administrator'. The customer administrator can manage all aspects of all devices assigned to the customer organization.
In addition to an administrator account, 'customer user accounts' may also be created for additional personnel within the customer organization. With this privilege level, one can view the configuration, receive notifications, monitor the devices and the network, and similar operations, but they are not allowed to modify any network configuration or modify user profiles.
The customer administrator can set up any number of administrator accounts or user accounts, but it needs to be kept to a reasonable minimum. The customer must also ensure that they keep track of the personnel that have access to their network and are responsible to remove those accounts when the employee is no longer administering ChiefNET.
3.3 Logging In
Access https://chiefnet.yavar.in (soon to be https://prod.chiefnet.io)
After log in, all features of ChiefNET are available. Use the "?" icon to access the context-sensitive help on any page.
3.4 ChiefNET CPE WAN Connection Variations
3.4.1 ChiefNET connected to ISP Directly
Some customers connect the ChiefNET CPE device directly to the ISP-supplied devices. In this model, the ISP-supplied devices are typically gateway devices, customized and fully supported by the ISP. These ISP-supplied devices are made available to the customers as part of their Internet Service subscription. They may be Internet Leased Lines, MPLS Lines, Wired Broadband lines, or Wireless broadband lines.
When ChiefNET is connected to the ISPs, ChiefNET's WAN ports are typically configured with DHCP. Ths is the default, and the most recommended setting on ChiefNET.
In some cases, the ISP may stipulate a specific static IP address. Please let your sales rep know in advance if this is the scenario. The device will then be delivered to you with that IP address preconfigured for your convenience.
If there is a firewall between the device and the on-prem network, ensure that the firewall allows traffic from the device. We have noticed that some firewalls have been configured with white-listed mac-addresses. ChiefNET's mac-address may have to be added to the white-list on the firewall.
VLANs and Bridges are supported on ChiefNET to isolate certain subnets or to have multiple Ethernet segments on your LAN side or if all LAN segments should be combined into a single Ethernet network. We recommend that you keep the network very very simple in the default settings so that administration and troubleshooting could be done by any junior networking personnel as well, without requiring advanced networking training.
Question:
Does ChiefNET provide appropriate security and stay protected from security threats?
Answer:
Yes. ChiefNET does not have any open ports on the WAN side. It allows only outgoing connections. All outgoing connections (management channel, data channels) are secure or directed to the Internet (local Internet Breakout). We periodically perform penetration tests on all deployed ChiefNET devices to identify any new vulnerabilities and are prepared to close those vulnerabilities with patches or upgrades.
ChiefNET's SDWAN/VPN tunnels use state-of-the-art AES-256-GCM/SHA-256/384/512 bit algorithms for encryption.
3.4.2 ChiefNET connected to ISP Through a Firewall
Some customers do not wish to connect all the on-prem traffic through ChiefNET CPE. In this case, there may be a firewall that handles all the on-prem traffic. ChiefNET CPE is then introduced into the network as a LAN device. Only a selection of the on-prem traffic is passed through ChiefNET. As an example, this is typically the case when ChiefNET network is acquired for site surveillance (security cameras) and for IOT monitoring. The standard Internet-bound traffic may or may not go through ChiefNET CPE.
The most important distinction to note here is that ChiefNET does not have direct access to the ISP WAN links and hence it may not be able to detect failures on the WAN side. The firewalls are then responsible for such WAN resiliency features such as failover and load-balancing.
The firewall should be configured to allow outgoing connections from ChiefNET. For instance, ChiefNET's WAN side mac-address may have to be white-listed.
3.5 Installation Tips and Guidelines
Always start with a simple connection, make small configuration changes and ensure they work before applying large configuration changes. This allows you to isolate problems as changes are made. Note that when ChiefNET CPE reports certain issues, specifically related to WAN links, it is almost always an issue with the ISP, in our experience.
If there is a firewall in your network, between ChiefNET device and the ISPs, ensure that the firewall is configured to allow traffic to and from the ChiefNET device.
We have found that many ISPs do not have a minimum bandwidth or a maximum bandwidth in their offering. The typical bandwidth is sometimes significantly more than the maximum they promise. While that is almost always a good thing, the WAN bandwidth usage alert should be disabled as it would not be a reliable measure of the WAN link utilization.
Set up a few user accounts on the Orchestrator so as to receive the appropriate alerts either through email or through SMS, upon certain conditions such as the loss of connectivity or events such as user-login and user-logout on the WebUI.
3.6 Configuration Steps
The following is the general series of guidelines to configure a CPE device that is online.
- Verify that the cloud WAN is up and running. One should be able to use ICMP echo or other traffic to verify connectivity between the LAN networks of multiple sites.
- Add traffic steering rules to support local Internet Breakout and to prevent unwanted traffic from the LAN side
- Use Split DNS feature if you have custom domains and custom name servers in your organization.
- Use DNAT feature if you have any servers in your network (e.g. IPsec VPN servers for road-warriors)
3.7 Monitoring Steps
- Visit Orchestrator WebUI Summary Page
- Verify that all devices are online.
- Verify that the WAN links are up and running on both ISPs
- Verify that the ISP-supplied devices are fully functional order
- Use the summary page to view all the devices and all the WAN interfaces for their overall status.
Should your users complain that certain applications are not working or that Internet is slow, run through the troubleshooting guide.
When adjusting the firewall settings, pay special attention to the traffic steering rules.
3.8 Security Settings
Two levels of access privileges are supported on ChiefNET WebUI.
A 'customer-admin' may be assigned to one or more users in your organization. They are able to manage all the devices and are able to modify the configuration, and able to manage other user accounts. We recommend that you keep more than one customer-admin to allow for availability of the administrative personnel.
A 'customer-user' privilege may be assigned to one or more users that are then allowed to verify if the network is in proper operating condition. Users in this role cannot modify the configuration or manage the users.
A user is identified by their email address. One user may either be a customer-admin or a customer-user. You can create additional user accounts in your organization, by contacting the person that has the customer-admin privileges. In an urgent setting, you may also contact ChiefNET customer support by email to perform some tasks for your network, in case people with the admin privileges are not available.
3.9 Troubleshooting
The most typical issues raised by the end users are
- Internet is not working
- The other branches are not reachable
- Internet is slow. Network access is slow. Server access is slow. Applications have slow responses.
In most cases, the best thing to verify is to document the changes done recently in your entire network, including ChiefNET. Sometimes changes in done in one branch may inadvertently affect systems in other branch.
We recommend that you keep an inventory of the IP subnets at various branches. Avoid using overlapping subnet as it introduces complexities in troubleshooting an IP network. There is almost always a simple solution available, where overlapping subnets seem to be a requirement.
VERIFY INTERNET LINK QUALITY:
Always verify Internet connectivity first. Watch for alerts from ChiefNET Orchestrator indicating the quality or status of the WAN links. ISP failures are the single most commonly occurring failures in the network deployments, be it MPLS, ILL or Broadband. The downtimes last for a very short time usually. Certain ISPs tend to be more reliable in some locations than others, but less reliable in other locations.
PING, TRACEROUTE:
Ping and traceroute are commonly available tools to verify connectivity. Use ping from one LAN device to check connectivity to each device using the IP.
Usually if a device does not respond, it is very likely that the response may be taking a different route. Use wireshark or tcpdump command at different locations. Here is a sample tcpdump command that can be immensely helpful.
tcpdump icmp and host <ip>
Replace
For instance, if you want to test Internet connectivity,
tcpdump icmp and host 8.8.8.8
and running the command 'ping 8.8.8.8' will log all ICMP echo and echo reply packets.
PACKET CAPTURE AT ENDPOINTS:
Use wireshark on PCs (at endpoints) to check if packets are being received and transmitted on your LAN side.
ChiefNET also supports packet-capture on its ports accessible using the webui. Once the packet-capture is done, the file may be downloaded and analyzed using Wireshark software.
3.10 Frequently Asked Questions
3.10.1 Why is the ChiefNET CPE not able to reach the Internet through the firewall?
In some organizations, the IT department hard-codes the mac-address into the firewalls, so that only specific devices are allowed to go through the firewall. This implies that the customer would have to configure the mac-address of ChiefNET in the firewall configuration.
Many a time, we have noticed that the customers modify the configurations of the firewalls which sometimes blocks ChiefNET. This needs to be verified as part of problem isolation, should issues be reported.
- Check mac-address whitelist on the firewall.
- Check logs on firewall (if any) to see if CPE device is blocked for any reason.
3.10.2 Why is the Internet slow?
In most cases, the Internet is slow due to the service provider's network and not necessarily with any of the equipment online.
If traffic bandwidth is suspected of slowing down the Internet for critical applications (e.g. branch locations trying to update the inventory and sales data at the HQ), it can be resolved by configuring QoS for critical applications. ChiefNET's QoS features provide minimum bandwidth quarantee, as well as limit the maximum for a given class of applications.