test packet-interface
Issue 5 October 2002
575
555-233-119
test packet-interface
Use test packet-interface to run hardware diagnostic tests on the packet
interface circuit packs in a carrier. Tests performed include local memory
checksum tests and checks of failure counters.
Feature Interactions
If the packet-interface circuit pack is in the “out-of-service” or “uninstalled” states,
no demand, scheduled, periodic, or error tests can run. See also
‘‘reset
packet-interface’’
and
‘‘status packet-interface’’
.
Output
The following example is the output for test packet-interface 1a1. The responses
appear on a test-by-test basis with one line of data for each test result.
Action/
Object
Qualifier
Qualifier Description
Logins
Defaults
Feature
Interactions
test
pkt-interface
location
short
long
repeat
number
clear
schedule
The packet interface to be tested: nn
(cabinet 1-3 + carrier letter)
Option for a brief series of
nondestructive diagnostic tests.
Option for a longer, more
comprehensive series of both
destructive and nondestructive
diagnostic tests.
How many times each test in the
sequence is repeated (1-100)
This option causes the test sequence
(short or long) to repeat until the alarm
(if any) is cleared or a single test in the
sequence fails.
1
Use the screen to schedule execution
of the command. The command is
placed in the command queue and is
executed at the specified time. The
information displayed by the command
is sent to the system printer instead of
the screen.
2
Examples:
test packet-interface 01a
1
If no alarms are registered against the maintenance object then the test sequence is run only once. The long
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only
clears alarms pertinent to tests in the short sequence.
2
See the Report Scheduler and System Printer feature specification for more details.
init
inads
craft
test
sequence =
short;
repeat
number = 1
see below