Using CPSIP and SIP Debug Logging in Legacy VX Systems

Updated by Bryan Jones

Scope

This article explains how to set up and execute CPSIP and SIP logging at the debug level on Legacy VX and VX Prime systems. This article only applies to VX and VX Prime on the older fanless style (2RU) hardware platform.

Description

Sometimes a problem will occur with the VX that no one can explain from the user interfaces. Sometimes the problem is with a peripheral device, a SIP server, an Internet connection, etc., which may look like a problem with the VX. To narrow the scope of the search, it's often necessary to take some logs at the debug level to see where the problem might be. Here we'll tell you how to do that.

Set Up the Logging Configuration

  1. Log in to your VX's web interface and navigate to the Configuration -> Logging page.
  2. Click ADVANCED to enter the Customize Log Levels menu.
  3. Set CPSIP to DEBUG
  4. Set SIP to DEBUG
  5. Set all other values to DO NOT LOG
Stay away from logging other information. Setting too many items to the debug log level adds resource use to the system and creates extremely hard-to-read logs.
  1. Click APPLY

Clear Internal Logs

  1. Navigate to the System -> Logs page
  2. Click CLEAR

Record the Problem and Dump the Log

  1. Reproduce the issue with the equipment
  2. Refresh the System -> Logs page in your browser to show the event
  3. Scroll all the way to the bottom of the web page
  4. Click SAVE

Save will write the log information to a text file on your computer containing a dump of the log you've just recorded. Attach this file to an email and send it to support@telosalliance.com

Using Syslog

If the VX is configured to send data to a Syslog, this recording will also appear in your syslog history.

For information about setting up a syslog server, see this technote here.

Let us know how we can help

If you have further questions on this topic or have ideas about improving this document please contact us

How did we do?