Acme Packet 4500
 
Net-Net 3810
 
Net-Net 9200
 
Acme Packet 3820
 
Net-Net 4250
 

PLA-Support>Sun Systems>CommsGBU>Session Delivery Network>SN-SND: Acme Service Provider
 

In this Document

Purpose

Troubleshooting Steps

References

Applies to:

Purpose

 This document describes how to troubleshoot console connection issues.

Troubleshooting Steps

The Net-Net systems use these console settings by default:

Baud Rate 115,200 bps
Date Bits 8
Parity No
Stop Bit 1
Flow Control None

A few common mistakes:
The SBCs use a different console pinout than Cisco, so the standard baby-blue Cisco console adapter won't work straight out of the box. Refer to Document 1591563.1.

The console pinout for the SBCs is detailed in Document 1591568.1.

Troubleshooting console connections:

Were there any changes made to the hardware or bootloader prior to the system becoming unresponsive? Has this console setup worked in the past?

Are you connecting directly with a laptop using an Acme Packet console adapter, or through a terminal server? Please test your console cable and setup with a known-good system, then do the following on the non-working system. This is a lengthy procedure, but in many cases recovers the system's connectivity:

1. Connect console cable to the front port
2. Change the baud rate in your laptop's terminal client / console server to one of the following (9600, 14400, 19200, 38400, 57600, 115200), then restart your terminal client
3. Fully power off and power on the SBC and check for any output displayed to the console terminal client.
4. Retest with each Baud rate (9600, 14400, 19200, 38400, 57600, 115200) on the front port.
5. Connect console cable to the rear console port, and retest the steps above

Once you've established the console connection you can continue with recovering the system by interrupting boot, etc. If you're unable to restore console or need more info please open a ticket with Acme Packet support. If you think a hardware replacement may be necessary, contact Acme Packet support.

ADDENDUM: 

Note that we have seen instances where a problem/failure on the HDD, when present could lead to a system failing to start properly, preventing even console connection activity. If you have a HDD in your system, you may try to remove that and restart to determine if the system will boot without the HDD present. See the related KM document, Diagnosing problems with an Acme Packet 4500 (3800/4600/6300) which has a hard drive when it fails to boot up(Document 2172091.1)

References

This solution has no attachment