ServerNet/DA Troubleshooting

ServerNet/DA Troubleshooting
Follow this procedure to test a ServerNet/DA, its PICs (SACs), or the ServerNet
communications with the ServerNet/DA. Refer to ServerNet/DA Troubleshooting Overview
for lists of possible problem sources, associated alarms, testing tools, and useful
commands.
Verify ServerNet/DA Troubleshooting Prerequisites.1.
Log on to either the OSM Service Connection or TSM Service Application. The
Management Window appears, displaying a tree pane, view pane, and details pane.
2.
In the tree pane, click the system enclosure where the ServerNet/DA resides. The
enclosure appears in the view pane.
3.
If the ServerNet/DA is not displayed in the view pane, check the hardware as
described in the 6760 ServerNet/DA Manual (this manual has not yet been revised for
OSM).
4.
If the ServerNet/DA is displayed in the view pane, click it and perform the following
actions:
Note: Some of the OSM or TSM tests used in this procedure make the
ServerNet/DA unavailable. Therefore, when using these tests, you might see a
message indicating that the device path must be offline before it can be tested.
If the ServerNet/DA Icon Action
Looks normal Go to Step 6.
Is red The initialization of the ServerNet/DA has probably failed.
Use the guided procedure to replace the ServerNet/DA.
Is yellow. Check the Subcomponent State or Service State of
the SACs on the ServerNet/DA (OSM displays these
Attributes only if there is a problem). If the state for
any of the SACs is abnormal, the cause could be:
Power-on self-test (POST) failure on one or
more SACs
■
Failure of the operational code for a SAC to
download
■
Failure of the CBB on the ServerNet/DA■
1.
See the Alarm window for additional information. The
possible SAC alarms are:
POST failed alarm■
Operation Code Download Failed alarm■
2.
Run Test Verify on the adapter for either alarm (see
Step 7).
3.
5.