Basic Diagnostics

One basic function in Orchestrator is checking the health of a network. If you have problems performing this check, consider the diagnostic steps below before calling Support.

NOTE: In addition to the methods described below, you can run Ping, Traceroute, and Packet Capture (tcpdump) from the command line interface (CLI). You can access the CLI via SSH or the CLI session option when right-clicking an appliance in Orchestrator’s appliance tree.

Ping

By default, all pings are sourced from the mgmt0 interface. To troubleshoot from the actual source interface, initiate pings using the “-I“ flag to test connectivity along the data path between different locations.

To run a ping:

1. Right-click an appliance in tree view, and then click Appliance Manager.
2. Click Maintenance, and then click Ping / Traceroute.
3. Select the Ping option, enter the required information, and then click Start.

Traceroute

Traceroute is another important tool to identify latency along the path, as well as identify the broken path where traffic stops.

To run a traceroute:

1. Right-click an appliance in tree view, and then click Appliance Manager.
2. Click Maintenance, and then click Ping / Traceroute.
3. Select the Traceroute option, enter the required information, and then click Start.

NOTE: Not all intermediate routers respond all the time. In some cases, firewall rules or other device configuration can block responses.

Performance Testing

Performance testing can be done from the appliance itself by selecting two appliances from the tree view, clicking Administration, and then clicking Link Integrity Test.

CAUTION: This test impacts performance. Use this method only when necessary.

Packet Capture

Orchestrator provides the option to run packet capture from the appliance. Capture files are in standard .pcap format, which can be read easily with Wireshark. To begin packet capture, select one to five appliances, click Support, and then click Packet Capture.

---