Using CPSIP and SIP Debug Logging in Legacy VX Systems
Updated 9 months ago
by
John (JP) Powell
Scope
This article explains how to set up and execute CPSIP and SIP logging at the debug level on Legacy VX and Legacy 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, Internet connection, etc. that may look like a problem with the VX. Sometimes the problem is caused by the VX itself. In order to narrow the scope of the search, it's often necessary to take some logs at the debug level so that we can take a look and see where the problem might be. Here we'll tell you how to do that
Step 1: Set Up the Logging Configuration
- Log in to your VX's web interface and navigate to the Configuration -> Logging page.
- Click ADVANCED to enter the Customize Log Levels menu.
- Set CPSIP to DEBUG
- Set SIP to DEBUG
- Set all other values to DO NOT LOG
- Click APPLY
Step 2: Clear Internal Logs
- Navigate to the System -> Logs page
- Click CLEAR
Step 3: Record the Problem and Dump the Log
- Reproduce the issue with the equipment
- Refresh the System -> Logs page in your browser
- Scroll all the way to the bottom of the web page
- Click SAVE
This will save a text file to 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 you have the VX 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 how we can improve this document, please contact us.
