11. Routing
All ChiefNET devices come preconfigured with dynamic routing among all the branch sites. There is no action needed from the user to configure dynamic routing.
As soon as the ChiefNET CPE device is powered up, and connected to the Internet, the user will notice that the LAN devices on all the sites are able to communicate with each other, based on the traffic engineering rules.
It is still possible to fine-tune certain parameters for highly-specific and uncommon use cases.
11.1 Static Routing
Static IP routing is a method of network routing where routes are manually configured and set up by a network administrator. Unlike dynamic routing protocols that automatically adjust to changes in the network topology, static routing requires the administrator to manually update the routing table whenever a change occurs, such as adding or removing a network segment.
On ChiefNET, it is not necessary to configure static routing at all. However, in some highly-specific use cases, it is possible to add some static routes.
Redistribution: It is possible to redistribute static routes, into the dynamic routing protocol so that these static routes are known to other devices in the cloud WAN as well.
Static routes are specific to a device.
- Click on the device that needs the static routes.
- Select the "Static Routing' tab.
On this page, you will see a flag titled, 'Redistribute'. Enable it when you want the static routes to be advertised (aka redistributed) over the dynamic routing protocols, so that the other devices in your cloud-wan (i.e. in other sites) also need to know about these static routes.
The list of configured static routes are displayed on this page.
You can add, delete or edit the static routes by clicking the appropriate icons on the table. Online help is available by selecting the ? icon.
11.2 Current Route Table
This page also displays the current routing table on ChiefNET's device. This is useful for troubleshooting purposes. A customer administrator does not have to know much about this detail.