Skip to main content
Version: v25.07.31

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​

Cloud Configuration Verification​

Access the CE Terminal​

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

sudo su -

Checking Gateway Configuration:​

This command is used to check the gateway configuration. For example, when the WAN/Internet connection is not working and the last received configuration of the CE needs to be verified, this command can be used.

cat last_config_response.json | jq .gatewayConfig

The given one is just an example output; when this command is run, it will show something like this.

Example Response​


[
  {
    "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.

Q:1 What information does the gateway configuration output provide?

Q:2 What should I do if the configuration does not match the expected settings?

Q:3 What is jq and why is it used here?