Local console does not detect cables
These are solutions to problems that occur when the local console does not detect
the presence of the Operations Console cable or remote control panel cable. A
status message of Connecting or Unavailable is usually present:
v Verify that the cables are properly connected. For more information, see Install
Operations Console cables.
v For the console, verify that the communications adapter card on the server is
properly connected.
v Verify that the part numbers for the Operations Console cable and remote
control panel cable are correct.
v Verify that the server is in a state such that the console would 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 server is in the proper state.
Note: Make sure that you power off or disconnect any display device on any
twinaxial work station controllers, with port 0 address 0 or 1, or port 1
address 0 or 1.
v 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.
v Verify that you meet all necessary networking requirements. If your local console
uses a LAN to connect to the server, be sure the network is active and properly
configured at the PC and the server.
Old network data interfering with reconfiguration of network
connectivity
If you are configuring a local console on a network and the user keeps getting an
old IP address, which may be wrong but you cannot get to it without changing the
name, you may need to edit the hosts file on the PC. You may need to edit the file
and remove the entry in question.
Note: Operations Console should be closed and restarted before attempting to
connect a new configuration. This action will remove all cached values
associated with any old configurations.
Console options not available in configuration wizard
Prior to V4R5, it was required to have a 5250 emulator installed (PC5250 or IBM
Personal Communications). Starting with V4R5 the emulator is no longer required
when only the remote control panel will be used. As a result, when the wizard gets
to the window where the user chooses what function (console or remote control
panel) the console function is disabled if the wizard code is unable to find a path
to a valid emulator. This might also indicate that the user did not allow the iSeries
Access for Windows installation to update the path (only Windows 98/Me PCs).
Either install or reinstall the emulator functions, or add the path to the emulator
manually to the system's path statement.
Chapter 6. Troubleshoot Operations Console connections
113
Need help?
Do you have a question about the E Server i Series and is the answer not in the manual?
Questions and answers