Cabling and Verifying Media Cards
Running media card hardware diagnostics
GRF 400/1600 Getting Started - 1.4 Update 2
October, 1998
5-35
Running media card hardware diagnostics
You can run a basic diagnostic command that will tell you if a media card has a hardware
problem. The grdiag command performs internal BIST-level diagnostics. A media card that
fails this grdiag must be replaced and returned to Lucent. You can run grdiag on one or more
cards without interrupting other media cards or system operation. Only HIPPI media cards do
not support the grdiag command
The grdiag script puts the selected media card(s) into diagnostic mode and runs the
diagnostics. After the diagnostics complete, grdiag reloads the media card’s software and
configuration currently saved in flash memory, then reboots the card. For this reason, it is very
important that you save any configuration changes before you run grdiag. Unsaved media card
changes will be lost.
For grdiag to run, a card must be able to boot. If the grcard display does not include the slot in
which the problem card resides, grdiag cannot operate on that card.
More information is available in the “Management Tools” chapter of the GRF Configuration
and Management manual.
Special login
Do not log in directly as
root
to use the grdiag command. To use grdiag, you must log in as
a user and then su to
root
.
This example uses the
netstar
login (password =
Ascend
) that a GRF is shipped with:
User: netstar
Password: ......
erase ^H, kill ^U, intr ^C status ^T
$
If you changed the default password as recommended, use the new password.
At the next prompt, enter su and use the
root
password at the prompt. You will see the UNIX
prompt appear:
$ su
Password:
#
Now you can run grdiag.
Running grdiag
The grdiag command starts a script. The script is simple to run. Here are the choices you
make:
–
choose to save unsaved changes – y / n ?
–
enter slot number(s) of media card(s) to test
Enter the grdiag command:
# grdiag
