Debugging

Use the following workflow as an aid to collecting information about the

Example Network Diagram: Edge 8300 Model

Prerequisites

• Login access to the
  Unable to show "metadata-from": No such page "_space_variables"
  Command Line Interface (CLI), as user sysadm and then as user root, using an SSH client such as Putty. (Some actions require you to capture the CLI output using the Putty collection function.)

Workflow

Log in to the Edge 8000 CLI

1. From the Edge 8000 CLI, log in as user system administrator (sysadm).

2. Change to user root.

   $ sudo -i
   

Collect Logs from the SIPUA

1. As root user in the CLI, access the SIP User Agent (SIPUA) module.

   db-manager-ctl cli

2. Enter number 4 to access the SIPUA.

3. Run the following command to enable log collection.
   Make sure that the Putty session is set to capture the output.

   debugsipgw 7 <enable debug>

4. After completing your test calls, run the following command to disable log collection.

   debugsipgw 0 <disable debug> 

Collect PCAPS from the SIPGW or SIPUA

1. As root user in the CLI, access the SIP Gateway (SIPGW) or SIPUA module.
   

   db-manager-ctl cli

   1. Enter number 9 to access the SIPGW.
   2. Enter number 4 to access the SIPUA.

2. Mount the filesystem to provide a memory disk area for writing pcaps. 
   Note that the /etc/images directory already exists on the host. When setting the size, do not exceed 10 Mb (10m).

   mount -t tmpfs tmpfs /etc/images -o size=4m   
   tcpdump -s 0 -ni eth0 port 5060 -w /etc/images/sip1.pcap

3. After completing your test calls, open a new session to transfer the captured file to the host. Note the different internal IP addresses for SIPGW and SIPUA:
   IP address for SIPGW: 192.168.188.250
   IP address for SIPUA: 192.168.188.100

   cd /E8000/backup_config
   scp root@<IP>:/etc/images/sip1.pcap 
   Password - <shift key plus 234567890>

4. Change permissions on the pcap file so you can delete it.

   chmod 770 sip1.pcap

5. Delete the pcap file and unmount the filesystem from the session where pcaps data was captured.

   rm /etc/images/sip1.pcap
   umount /etc/images

Collect Logs and PCAPS from the SWE Edge

For collecting logs and packet captures (PCAPS) from the SWE Edge, refer to Working with Logging in the SBC Edge Portfolio 12.1.x Documentation.

Generate a System Report

As root user in the CLI, generate a system report using the following command:

sys-tools report <reportName>

The report format is <reportName>_<year>-<month>-<day>-<time>.tgz

For example, SBC_NODE_1_2024-08-31-00.12.14.tgz

The system report file is saved in the /e8k-data/reports directory. The file contains information about the Setup Wizard configuration, software versions, ifconfig, iptables, route, bridge, arp, dmesg, systemctl, memory information, and NTP information, plus a config backup and various other Linux level files, for example,/var/log/messages.

Generate a System Debug Report

As root user in the CLI, generate a system debug report using the following command:

sys-tools debug

The system debug report file is displayed in the terminal window. The file contains information about the Setup Wizard configuration, software versions, ifconfig, iptables, route, bridge, arp, dmesg, systemctl, memory information, NTP information, and other data useful for the support engineer.

Make sure that the Putty session is set to capture the output.

View 6WIND Router Logs

Refer to 6WIND Router Documentation. Once in the documents, search the User Guide for System Logging to learn about logging services, local logging configuration, remote syslog configuration, and transport layer security for syslog messages.