FS6200 Server System Implementation Guide - Public Support ...

Troubleshooting and Recovery
4. Verify that the connection to the JProcessor Specialty Engine is valid by using the
following command:
NW TCPIP PING 192.168.16.142
NW TCPIP PING 192.168.16.146
NW TCPIP PING 192.168.16.150
NW TCPIP PING 192.168.16.154
Note: You can successfully execute this command only if the JProcessor firewall
rules have been modified to allow a network PING. See ″Enabling MCP PING
Commands through the Intra-Platform Connection for JProcessors″, in section 4 of
this guide.
• A response indicating “% PACKET LOSS 0” indicates that the specialty engine is
still functioning. You should be able to connect to it using the Remote Desktop
Client from the Management Workstation where you can attempt to restart the
JProcessor Specialty Engine firmware.
• A response indicating “% PACKET LOSS 100” indicates the specialty engine is
not functioning properly or the connection failed. In either case, a specialty engine
restart is most likely required. Try to connect to the specialty engine using the
remote desktop client from the management workstation. You can initiate a
system restart if necessary.
5. From the systems management engine, launch the MCP Console, click the
Component View tab, expand ISM, expand s-Par ® , and then determine if the
JProcessor Specialty Engine in question is running (denoted by a green circle overlay).
a. Perform one of the following actions depending on the state of the JProcessor
Specialty Engine:
• If the specialty engine it is not running, right-click it and then select Restart
on the shortcut menu.
• If the specialty engine is running, right-click it and then select Launch RDP
Session on the shortcut menu to open a remote desktop session on the
specialty engine.
b. Log on using the appropriate administrator user name and password.
c. Double-click the Server Manager icon next to the Start button in the status
bar.
The Server Manager window is displayed.
d. Locate and expand the Configuration node in the console tree view.
e. Select the Services node in the console tree view.
f. Select Unisys MCP Java Monitor.
g. Right-click and select Restart on the shortcut menu.
9–18 8222 3694–000