Configuration of CisSDWInterfaceTest

In the Cisco SD-WAN overlay network, you can configure network interfaces within individual VPNs. For each network interface, you can configure a number of interface-specific properties, such as DHCP clients and servers, VRRP, interface MTU and speed, and PPPoE. You can configure up to 512 interfaces on each component of the Cisco SD-WAN appliance. This number includes physical interfaces, loopback interfaces, and subinterfaces.

For each such network interface configured, this test reports the following:

• The current admin and operational state of the interface;

• The duration for which the interface was up;

• The bandwidth utilized by the interface and the nature of traffic handled by the interface-i.e., packets, data etc.;

• Errors experienced by the interface during transmission/reception of data/packets.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the host for which the test is to be configured has to be specified.

• In the PORT text box, enter the port number at which the target host being monitored listens. By default, this is set to NULL.

• By default, the eG agent executes REST APIs on the target appliance to collect the required metrics. For the eG agent to execute the REST APIs, a special user with monitoring privilege is required. Specify the name of such a user in the USERNAME text box.

• Specify the password corresponding to the user mentioned in the USERNAME text box here.

• Confirm the Password by retyping it here.

• By default, the REST API Port is set to none. This implies that by default, this test connects to the default port to execute the REST API commands and collect the required metrics. In some environments however, a different port can be used to execute the REST API commands. In such case, specify that port number against the REST API PORT text box.

• The eG agent collects performance metrics by executing REST APIs on the target appliance. Typically, the REST APIs can be invoked through HTTP or HTTPS mode. By default, the eG agent invokes REST APIs using the HTTPS mode. This is why, the SSL flag is set to Yes by default. If the target appliance is not SSL-enabled, then the REST APIs can be accessed through HTTP mode only. In this case, set the SSL flag to No.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.