Cato Networks Knowledge Base

Using the Socket WebUI Tools

Overview of Troubleshooting Tools

The Tools tab in the Socket WebUI has these network tools that you can use to troubleshoot the Socket links:

Note: The network tools described in this article are supported on Socket version 9.0 and higher.

Logging In to the Socket WebUI

To log in to the Socket WebUI:

  1. Show the IP address for the Native Range Gateway to connect to the Socket WebUI:
    1. From the Cato Management Application, click Network > Sites and select the Socket site.
    2. Expand the Site Configuration > Networks section, and locate the row for the Native Range.
    3. In the Characteristics column, the Local IP setting shows the IP address for the Socket WebUI.
  2. From an Internet browser, enter the following URL: https://[your Cato Socket's IP address].

    For example, https://10.0.0.15

  3. Enter the login credentials for the Socket WebUI.

Using the Network Tools

Note: The Force Recovery via Internet Bypass Section is for advanced troubleshooting. For more about this feature, contact Support.

To show the network tools:

  • From the menu bar, click Tools. The Socket WebUI shows the Network Tools section.

 

Using the Ping Tool

Choose the Socket link and enter the hostname or IP address that you are pinging.

These are the types of Socket links that you can use as the egress interface:

  • LAN - The packets are sent using the internal LAN network for the site.
  • ALT WAN - The packets are sent using the Alt. WAN tunnel over the MPLS network.
  • WAN via Cato - The packets are sent using the DTLS tunnel over the Cato Cloud.
  • WAN <ISP> directly - The packets are sent directly over the Internet using the ISP. The Cato Cloud is bypassed.

To ping the destination from a Socket link:

  1. From the Network Tools section, click the Ping tab.

  2. In Route via, select the link that is sending the packets.
  3. Enter the Hostname/IP that is the destination you are pinging.
  4. Click Run.
    The window shows the results of the ping test.

The UI only sends 10 ping requests, so if you need more pings you will need to click the Ping button again. 

 

Using the Traceroute Tool

Choose the Socket link you want to run traceroute and enter the destination hostname or IP address.

These are the types of Socket links that you can run traceroute:

  • LAN - The packets are sent using the internal LAN network for the site.
  • ALT WAN - The packets are sent using the Alt. WAN tunnel over the MPLS network.
  • WAN via Cato - The packets are sent using the DTLS tunnel over the Cato Cloud.
  • WAN <ISP> directly - The packets are sent directly over the Internet using the ISP. The Cato Cloud is bypassed.

To run traceroute from a Socket link:

  1. From the Network Tools section, click the Traceroute tab.

  2. In Route via, select the link that is sending the packet.
  3. Enter the Hostname/IP that is the destination for the traceroute.
  4. Click Run.
    The window shows the results of the traceroute test.

Traceroute is used to identify the routers (hops) between a source and destination. Traceroute works by first sending a packet to the destination IP with a time-to-live (TTL) value of 1. When the packet hits the first router in the path, the router decrements the TTL by 1. Since the new TTL is 0, the router drops the packet and responds with an ICMP time-to-live exceeded message sourced from its own IP address. Traceroute now has the IP address of the first router in the path, so it sends out another packet with the TTL value of 2 (the original TTL incremented by 1), and the second router in the path responds with a TTL exceeded message.

This process is repeated until traceroute reaches the destination IP address.

 

Using the Speedtest Tool

The Socket WebUI lets you use the Speedtest client that is installed on the Socket to troubleshoot the network performance of the Socket links. The Speedtest tool can be used with a randomly chosen Speedtest server on the public Internet, or with the server running directly on the connected PoP in the Cato Cloud.

These are the types of Socket links that you can run the Speedtest:

  • WAN via Cato - The packets are sent using the DTLS tunnel over the Cato Cloud.
  • WAN <ISP> directly - The packets are sent directly over the Internet using the ISP. The Cato Cloud is bypassed.

Known Limitations for Speedtest

The same Socket CPU is responsible for generating the traffic for the Speedtest and sending the site traffic. These are the recommended link network speeds for accurate Speedtest results:

  • X1500 Socket results are accurate for link speeds up to 300 Mbps
  • X1700 Socket results are accurate for link speeds up to 2000 Mbps
  • Virtual Socket (vSocket) - the accuracy depends on the VM and cloud platform specifications

For the most accurate results, run the Speedtest tool when there is minimal traffic over the link. Other traffic has higher QoS priority than the Speedtest traffic.

To run Speedtest for a Socket link:

  1. From the Network Tools section, click the Speedtest tab.

  2. In Server, select the server that is running the Speedtest:
    • Cato Connected PoP - the Speedtest client is hosted on a PoP in the Cato Cloud
    • Internet - the Speedtest client is hosted on a random server in the public Internet
  3. In Route via, select the WAN link that is sending the traffic for the Speedtest.
  4. Click Run.
    The window shows the results of the Speedtest.

Using the iPerf Tool

The Socket WebUI lets you use the iPerf tool to troubleshoot last mile performance issues between the Socket and the connected PoP in the Cato Cloud. The Socket that is running the iPerf client performs the test against the iPerf server that is running on the connected PoP. Use the Direction option to test the upstream or downstream connectivity performance for a WAN link.

These are the types of Socket links that you can run the iPerf tests:

  • WAN via Cato - The packets are sent using the DTLS tunnel over the Cato Cloud.
  • WAN <ISP> directly - The packets are sent directly over the Internet using the ISP. The Cato Cloud is bypassed.

You can also select TCP or UDP traffic, and the amount of time (seconds) in between each data stream.

Known Limitations for iPerf

The same Socket CPU is responsible for generating the traffic for the iPerf test and sending the site traffic. These are the recommended link network speeds for accurate iPerf results:

  • X1500 Socket results are accurate for link speeds up to 300 Mbps
  • X1700 Socket results are accurate for link speeds up to 2000 Mbps
  • Virtual Socket (vSocket) - the accuracy depends on the VM and cloud platform specifications

For the most accurate results, run the iPerf tool when there is minimal traffic over the link. Other traffic has higher QoS priority than the iPerf traffic.

To run an iPerf test for a Socket link:

  1. From the Network Tools section, click the iPerf tab.

  2. The option for Server is Cato Connected PoP, the iPerf tool is hosted on a PoP in the Cato Cloud.
  3. In Route via, select the WAN link that you are using to run iPerf.
  4. Select the Protocol for the iPerf test, TCP or UDP.
  5. Set the Direction of the test traffic, and the Measurement Interval between data streams.
  6. For TCP protocol, select if this test uses Parallel flows.
  7. For UDP protocol, enter the Target rate (bandwidth) for the UDP traffic.
  8. Click Run.
    The window shows the results of the iPerf test.

Showing the Socket CPU Usage

The HW Status page shows real-time information about your Socket CPU utilization. You can use this page to monitor CPU changes while troubleshooting the Socket.

socket_cpu.png

To show the Socket CPU Usage:

  1. From the menu bar, click the HW Status tab.

Was this article helpful?

1 out of 3 found this helpful

Comments

1 comment

Please sign in to leave a comment.