FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

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
Gathering Diagnostic Information The JProcessor Specialty Engine firmware writes application event information to the application event log. It also maintains a MCP Java Monitor log that contains more detailed information. Perform the following steps to access the application event log from the Server Manager: 1. From the Component View tab of the MCP Console, expand ISM, expand s-Par ® , right-click the appropriate JProcessor, and then click Launch RDP Session. 2. From the task bar, open Server Manager. 3. Locate and expand the Diagnostics node in the Server Manager tree view. 4. Expand the Event Viewer node in the Server Manager tree view. 5. Expand the Applications and Services node in the Server Manager tree view. 6. Select the MCPJava event log. The MCPJava event log file contains information, warning, and error messages. 7. (Optional) Copy the MCPJava log file to an MCP share where it can be accessed by other workstations in the network. Obtaining the MCP Java Monitor Log File Perform the following steps to access the MCP Java Monitor log file from the Server Manager: 1. From the Component View tab of the MCP Console, expand the ISM and s-Par ® components, right-click the appropriate JProcessor, and then remote desktop to the JProcessor environment. 2. Browse to :\MCPJava\Logs and locate the file named JMon.JBT. This is the detailed log file of the MCP Java Monitor and might provide reasons why the firmware stopped communicating with the MCPJava support library. 3. (Optional) Copy the file to an MCP share where it can be accessed by other workstations in the network. 4. (Optional) Occasionally clear the MCPJava application event log and remove the JMon.JBT detailed log file. By default, the MCPJAVA application event log is set to 1MB of messages and reuses space as needed. The JMon.JBT file grows to 7MB before it is saved as JMonSaved.JBT and a new one started. ePortal Specialty Engine Troubleshooting and Recovery This subsection provides troubleshooting information for the ePortal Specialty Engine. 8222 3694–000 9–19
Page 1 and 2:
ClearPathFS6200Server SystemImpleme
Page 3 and 4:
Contents Section 1. Introduction Ab
Page 5 and 6:
MCP Firmware Environment Policy Uti
Page 7 and 8:
Updating Specialty Engines . . . .
Page 9 and 10:
Figures 2-1. FS6200 Server Hardware
Page 11 and 12:
Tables 3-1. Physical Location of HB
Page 13 and 14:
Section 1 Introduction About This G
Page 15 and 16:
Section 2 System Overview This sect
Page 17 and 18:
• Two Processor Memory and Module
Page 19 and 20:
MCP Console s-Par Component Descrip
Page 21 and 22:
ePortal Specialty Engine The ePorta
Page 23 and 24:
Section 3 Customizing the Server Co
Page 25 and 26:
Determining Correspondence between
Page 27 and 28:
Table 3-1. Physical Location of HBA
Page 29 and 30:
• The MCP is running. • The pat
Page 31 and 32:
e. Log on to the environment. f. Cl
Page 33 and 34:
The default IP address for the intr
Page 35 and 36:
Table 3-6. Default Networking Value
Page 37 and 38:
Changing the Network Services EVLAN
Page 39 and 40:
IEEE 802.1Q VLANs allow a single ne
Page 41 and 42:
and BIP protocols. Communications b
Page 43 and 44:
4. To modify a network processor ob
Page 45 and 46:
You must replace or modify the prec
Page 47 and 48:
Table 3-8. MCP Networking Values fo
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Using Sample BNA Initialization Fil
Page 55 and 56:
Some of the procedures in MCP Imple
Page 57 and 58:
Section 4 Operating the Server This
Page 59 and 60:
Powering Off the Platform Hardware
Page 61 and 62:
Controlling the MCP Environment Acc
Page 63 and 64:
• Domain Name System (DNS) Client
Page 65 and 66:
Table 4-1. Unisys-Defined Firewall
Page 67 and 68:
Table 4-2. Firewall Rules for JProc
Page 69 and 70:
The utility scripts enable you to m
Page 71 and 72:
Notes: Syntax Usage • Refer to th
Page 73 and 74:
Sample Commands • ChangeRulesForM
Page 75 and 76:
Note: The .\ notation before the sc
Page 77 and 78:
Differences from Previous MCP Syste
Page 79 and 80:
If you do not receive this response
Page 81 and 82:
Networking Commands and Inquiries C
Page 83 and 84:
• Total processor utilization rep
Page 85 and 86:
I/O Time • ACQUIRE • FREE • O
Page 87 and 88:
Operating the Server PING commands
Page 89 and 90:
Section 5 Setting Up and Operating
Page 91 and 92: Ensuring That the Necessary Disk Sp
Page 93 and 94: ; , REMOTEADDRESS = 000000000000 ,
Page 95 and 96: This command is optional. By defaul
Page 97 and 98: 6. Perform the following actions to
Page 99 and 100: 1. From the Component View tab, exp
Page 101 and 102: Setting Up and Operating the ePorta
Page 103 and 104: Assigning ePortal Specialty Engine
Page 105 and 106: Setting Up and Operating the ePorta
Page 107 and 108: Restoring ePortal The following act
Page 109 and 110: Section 6 Setting Up and Operating
Page 111 and 112: • Microsoft Network Client This f
Page 113 and 114: Applying JProcessor Security Policy
Page 115 and 116: Section 7 Backing Up MCP Firmware C
Page 117 and 118: Section 8 Updates This section disc
Page 119 and 120: Updating MCP Firmware MCP Firmware
Page 121 and 122: Job (USERCODE) EPORTALNOTE ACCEPT:
Page 123 and 124: 17. Go back into update settings (s
Page 125 and 126: Section 9 Troubleshooting and Recov
Page 127 and 128: Accessing the Unisys Product Suppor
Page 129 and 130: Taking a Platform Firmware Livedump
Page 131 and 132: Hardware Failure Symptoms Criticali
Page 133 and 134: Workaround Use the platform managem
Page 135 and 136: • If your TCP/IP or BNA connectio
Page 137 and 138: • Obtain a Network Services firmw
Page 139 and 140: The response to the NW NP command
Page 141: Restarting a JProcessor Specialty E
Page 145 and 146: 1. Create an unprivileged MCP userc
Page 147 and 148: The topic “I/O Configuration” i
Page 149 and 150: cd “C:\Program Files\Unisys\MCP F
Page 151 and 152: Restarting Platform Services Note:
Page 153 and 154: Appendix A Building Network Initial
Page 155 and 156: • NW TCPIP TCPIPIDENTITY NW TCPIP
Page 157 and 158: Building Network Initialization Fil
Page 159 and 160: Sample BNA Initialization File % On
Page 161 and 162: Index A accessing the Unisys Suppor
Page 163 and 164: MCP PING commands through intraplat
Page 165 and 166: MAICP4 dump data, 9-13 Maintenance
Page 167 and 168: elocating the MCP APPLIANCES share,
Page 170: © 2012 Unisys Corporation. All rig
show all

FS6200 Server System Implementation Guide - Public Support ...

Create successful ePaper yourself

Delete template?

Save as template?