FS6200 Server System Implementation Guide - Public Support ...

• If your TCP/IP or BNA connection is defined with the AUTOINIT attribute set to
TRUE, issue the inquiry NW CONN . Verify that the
CONNECTIONSTATUS = OPEN.
• If your TCP/IP or BNA connection is defined with the AUTOINIT attribute set to
FALSE, issue the establish call command NW EC BY CONNECTION
to open the connection. Then, issue the inquiry NW CONN
. Verify that the CONNECTIONSTATUS = OPEN.
• If the connections have not opened, review the active PCD file through System Editor
to ensure that the lines have been assigned the correct line numbers and the proper
network processor.
• If the assignments in the PCD are correct, verify the cabling and the network switches
are working correctly. Finally, if all of the hardware appears to be correct, reinstall the
Network Services firmware.
Note: If it becomes necessary to reinstall the Network Services software, you must
uninstall adapter devices before reinstalling the software.
MCP Console Connection Error
If the MCP Console interface starts before the NGAgent service is running, you might
encounter a connection error. This error message often appears if the MCP Console
interface is placed in the Startup group.
If you encounter this error message, wait a few minutes and restart the MCP Console or
select the Connect command from the File menu of the MCP Console.
MCP Console Component View — Disconnected Components
If a component on the MCP Console Component View is displayed with a blue question
mark icon and a contact state of Disconnected, this indicates a problem establishing a
network connection to the component.
Follow these troubleshooting steps to diagnose the root cause of the problem:
1. Verify the component is running and has a working network connection.
2. Right-click on the disconnected component and select Launch.
Troubleshooting and Recovery
Note: The specific type of launch operation varies by component. For example, it
might be to launch a Remote Desktop session or launch the BMC web interface.
If the launched interface cannot connect to the component, this likely indicates the
component is either not running or not properly configured on the network.
3. Verify the Systems Management account password on the component.
If the component is running and active on the network, it is possible the connection is
failing due to invalid credentials. This can be resolved by following the instructions in
the topic “Synchronizing the System Account Password on a Component” of the
MCP Console Help.
8222 3694–000 9–11