Check System Logs; How To Submit Trouble Reports To Patton - Patton electronics SmartNode Series Software Configuration Manual

SmartWare Software Configuration Guide
Step
5 node #debug dsp t30
Depending on the type of problem, use also:
node #debug dsp events
node #debug dsp ifp

Check system logs

See section "Displaying the system logs"

How to submit trouble reports to Patton

Due the wealth of functionality and complexity of the products there remains a certain number of problems,
either pertaining to the Patton product or the interoperability with other vendor's products.
If you have a problem for which you need supplier help please prepare and send the following information:
• Problem description—Add a description of the problem, if possible together with applicable augmented
information with a diagram of the network setup (with Microsoft tools).
• Running configuration and software and hardware version information—With the Command Line Inter-
face commands 'show running-config' and 'show version' you can display the currently active configuration
of the system (in a Telnet and/or console session). When added to the submitted trouble report this will
help us analyze the configuration and preclude possible configuration problems.
In the unlikely case of a suspected hardware problem also submit the serial number of the SmartNode(s)
and/or interface cards.
• Event logs—Add the system event logs, which you can display with the Command Line Interface com-
mands 'show log' and 'show log supervisor'. That the logs are useful, it is necessary to set on startup the
clock to actual date and time (by hand or by enabling SNTP client)
• Your location—For further enquiries please add your email address and phone number.
If possible, add the following information in addition to the above:
• Logs of protocol monitors—Protocol traces contain a wealth of additional information which may be very
helpful in finding or at least pinpointing the problem. Various protocol monitors with different levels of
detail are an integral part of SmartWare and can be started (in a Telnet and/or console session) individually
('debug' command).
Note In order to correlate the protocol monitors at the different levels in Smart-
Ware (e.g. ISDN layer3 and Session-Router monitors) run the monitors
concurrently.
• Network traffic traces—In certain cases it may be helpful to have a trace of the traffic on the IP network in
order to inspect packet contents. Please use one of the following tools (supporting trace file formats which
our tools can read):
Debugging task list
Command
Command
on page 97.
Purpose
Enable the T.30 flow monitor
Purpose
Enable the DSP event monitor
Enable the IFP decoding monitor
31 • VoIP debugging
405