Interoperability Testing
Interpreting LAN Errors
Interpreting LAN Errors
The following are possible situations you may currently find yourself in.
LAN problem corrected.
If you have made a change that corrected your LAN problem, then proceed to the OTS layer tests.
Configuration change required.
If the corrective action in the following sections require you to change a configuration parameter, then do so and rerun the LAN test.
|
| Problem persists. |
| ||
|
| If you have been unsuccessful in correcting the problem, gather the | |||
|
| information you have collected to provide to your HP support | |||
|
| representative. |
|
| |
Table | LAN Errors |
|
| ||
|
|
|
|
|
|
|
| Error |
| Reason | Action |
|
|
|
|
| |
| LAN Interface Name |
| The “interface name” is | Check the parameter | |
|
|
|
| extracted from the OTS | lanX_if_name from the |
|
|
|
| subnet configuration. If | top of the osidiag output |
|
|
|
| the device is not open, it | and verify that this |
|
|
|
| may have the wrong | interface exists using the |
|
|
|
| value configured (or no | lanscan command. |
|
|
|
| value). |
|
|
|
|
|
|
|
| open() |
|
| Opens the DLPI stream | Create device file using |
|
|
|
| device. Device file | mkdev(1M) command. |
|
|
|
| /dev/dlpi may not exist. |
|
|
|
|
|
| |
| getmsg (DL_BIND_ACK) |
| Used to set up various | If OTS is running, make | |
|
|
|
| options for LAN access. | sure OTS will not be |
|
|
|
| Possible errors: | started when the system |
|
|
|
| *Setting SSAP. Sets Link | comes up and reboot the |
|
|
|
| system to perform this | |
|
|
|
| Service Access Point. Will | |
|
|
|
| command. | |
|
|
|
| fail if it is currently in use | |
|
|
|
|
| |
|
|
|
| by another osidiag |
|
|
|
|
| process or by OTS. |
|
|
|
|
|
|
|
Chapter 1 | 37 |
