Local console does not detect console cable

 

These are solutions to problems that occur when the local console does not detect the presence of the Operations Console cable.

A status message of Connecting or Unavailable is typically present:

• Verify that the cable is properly connected.

• For the console, verify that the communications adapter on the system is properly located.

• Verify that the part numbers for the Operations Console cable is correct.

• Verify that the system is in a state such that the console can be active. For example, the console is active after a manual initial program load (IPL). After you perform the IPL, the system reference codes (SRCs) B6004031, B6004501, or B600500X (where x is a number) indicate that the system is in the proper state.

• Verify that the resources of the PC are free of address or interrupt request (IRQ) conflicts. Operations Console uses addresses in the range of 192.168.0.0 to 192.168.0.255. If you run any software that makes your PC SOCKS-enabled, check your SOCKS configuration and make sure that the entry is:

  Direct 192.168.0.0 255.255.255.0

  A SOCKS-enabled PC accesses the Internet through a firewall, such as Microsoft^® Proxy Client, Hummingbird^® SOCKS Client, or others.

 

Parent topic:

Troubleshooting configuration wizard problems

 

Related reference

Installing an Operations Console cable