Managing and Troubleshooting the Universal Port and Dial-Only Feature Cards
Troubleshooting
10
Cisco AS5350XM and Cisco AS5400XM Universal Gateways Software Configuration Guide
test port modem back-to-back
slot
/
port slot
/
port
[
num-packets
]—Performs internal back-to-back port
tests between two ports, sending test packets of the specified size.
You might need to execute this command on several different combinations of ports to determine which
one is not functioning properly. A pair of operable ports successfully connects and transmits data in both
directions. An operable port and an inoperable port do not successfully connect with each other.
A sample back-to-back test might look like the following:
AS5400#
test port modem back-to-back 2/10 3/20
Repetitions (of 10-byte packets) [1]:
*Mar 02 12:13:51.743:%PM_MODEM_MAINT-5-B2BCONNECT:Modems (2/10) and (3/20) connected in
back-to-back test:CONNECT33600/V34/LAP
*Mar 02 12:13:52.783:%PM_MODEM_MAINT-5-B2BMODEMS:Modems (3/20) and (2/10) completed
back-to-back test:success/packets = 2/2
A port that has been confirmed to have problems can often be fixed using the
clear spe
command. For
more information, see the
“Clear an SPE” section on page 11
.
The results of the
test port modem back-to-back
command are displayed in the
show port modem test
command output:
AS5400#
show port modem test
Date Time Modem Test Reason State Result
3/02 12:00:57 PM 2/01 Back-To-Back :STARTUP TEST Idle PASS
3/02 12:00:57 PM 2/00 Back-To-Back :STARTUP TEST Idle PASS
3/02 12:00:58 PM 2/02 Back-To-Back :STARTUP TEST Idle PASS
3/02 12:00:58 PM 2/03 Back-To-Back :STARTUP TEST Idle PASS
3/02 12:00:58 PM 2/04 Back-To-Back :STARTUP TEST Idle PASS
3/02 12:00:58 PM 2/05 Back-To-Back :STARTUP TEST Idle PASS
...
3/02 12:01:14 PM 3/95 Back-To-Back :STARTUP TEST Idle PASS
3/02 12:01:14 PM 3/94 Back-To-Back :STARTUP TEST Idle PASS
3/02 12:01:15 PM 3/75 Back-To-Back :STARTUP TEST Idle PASS
3/02 12:01:15 PM 3/74 Back-To-Back :STARTUP TEST Idle PASS
3/02 12:13:52 PM 3/20 Back-To-Back :USER INITIATED Idle PASS
3/02 12:13:52 PM 2/10 Back-To-Back :USER INITIATED Idle PASS
...
3/02 12:44:00 PM 3/102 No Test (Time) :MIN IDLE MODEMS Idle NOTST
3/02 12:44:00 PM 3/103 No Test (Time) :MIN IDLE MODEMS Idle NOTST
3/02 12:44:00 PM 3/104 No Test (Time) :MIN IDLE MODEMS Idle NOTST
3/02 12:44:00 PM 3/105 No Test (Time) :MIN IDLE MODEMS Idle NOTST
3/02 12:44:00 PM 3/106 No Test (Time) :MIN IDLE MODEMS Idle NOTST
3/02 12:44:00 PM 3/107 No Test (Time) :MIN IDLE MODEMS Idle NOTST
3/02 12:44:21 PM 2/73 Back-To-Back :TIME INTERVAL Idle PASS
3/02 12:44:21 PM 2/72 Back-To-Back :TIME INTERVAL Idle PASS
3/02 12:44:21 PM 2/33 Back-To-Back :TIME INTERVAL Idle PASS
3/02 12:44:21 PM 2/32 Back-To-Back :TIME INTERVAL Idle PASS
3/02 12:44:21 PM 3/37 Back-To-Back :TIME INTERVAL Idle PASS
Note
The
Reason
column indicates why the test was started. The
TIME INTERVAL
is one of the triggers under
autotest; the other is the error threshold.
SPE Recovery
You can configure automatic recovery (removal from service and reloading of SPE firmware) of ports
on an SPE at any available time from global configuration mode (the prompt is
AS5350(config)#
or
AS5400(config)#
):