Skip to main content

Single arm troubleshooting

This is usually a single-arm configuration, where CE is connected to PE onone interface. Troubleshooting usually involves verification of gateway and networking interface correct configurations, routing, and communication toward hiCLOUDS. Common symptoms include failure to reach destinations beyond the local network, connectivity drops or registration failures with hiCLOUDS. This guide will walk you through the essential troubleshooting steps.

Troubleshooting Steps​

Access the CE Terminal​

Log in to the CE (Customer Edge) terminal and gain superuser privileges:

sudo su -

Checking Gateway Configuration:​

Check the gateway configuration by viewing the last configuration response. This command will extract the gateway Config section from last_config_response.json using jq:

cat last_config_response.json | jq .gatewayConfig

Example Response​

root@manual-test:/tmp# cat last_config_response.json | jq .gatewayConfig
[
  {
    "mode": "CE_PEGW",
    "translationAddress": "masquerade",
    "ceDeviceIp": "100.100.0.9/30",
    "sourceSubnet": [
      "192.168.1.0/24",
      "192.168.10.0/24"
    ],
    "zone": "in",
    "localSeqId": 2,
    "peDeviceIp": "100.100.0.10/30",
    "id": 1,
    "gatewayMode": "GLOBAL",
    "singleArm": true,
    "cid": 38
  }
]

This command will extract the gateway configuration from last_config_response.json using jq, a JSON processor. Look at the output to make sure the gateway IP address and other pertinent settings are set up correctly.

Trace Route to Destination:​

To test this, perform the following traceroutes:

tracroute x.x.x.x

Replace x.x.x.x with the IP of a destination server of the device. This command follows the network trace to the final destination and sometimes can display whether connectivity might break at potential hops along the trace. ADD actual output by running this command in case of the use of the above command, in the output: check for timing out and reachable hosts.

Check System Logs​

If the unexpected behavior persists, review the system log for errors or anomalies using:

logread

Analyze logs to identify problems such as policy misconfigurations, connectivity errors, or authentication failures.