Issue
If your Vega's software appears to be rebooting, use the below steps to troubleshoot and capture the logs:
Steps
This entire procedure must be performed on the Vega serial port. The correct output will not
be generated on a telnet sessionLogin via the Vega's serial port before the problem will occur and type the following commands:
Code Block debug watchon udb mode auto (Vega ISDN) debug enable _isdn 89 (Vega Analog) debug enable _pots 12346 (Vega CAS-R2) debug enable _cas 4567 debug memory 25000 w
Wait for the problem to occur such that the Vega reboots.
...
It is possible that the above commands won't produce the desired dump.
If this is the case, then try this:
|
| Info |
|---|
NOTE: The above features a "debug softwatchon" CLI command as well |
as all the others in the previous attempt. |
Then wait for the problem to occur such that the Vega reboots.
When the Vega reboots you should now see lots of output similar to the sample below.
The The reason for the possible two-stage approach, and the reason why we don’t go straight to
the to the second set of commands is that if there is no output from the first stage that narrows down
the down the problem, making it easier to diagnose.
Sample Output
memory at locations pointed to by register values:
|