FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Troubleshooting and Recovery Hardware Failure Symptoms Criticality Response Intrusion Alarm Error message appears on LCD panel. If configured, an email alert is sent. Non-critical. Possible indication of nonapproved physical access to system. Operations Server Failure Scenarios Alarm will reset when the system is recovered. The Operations Server is the primary management interface into the system. Two Operations Servers are included with each FS6200 Server. One Operations Server is currently active to manage the server. If the Operations Server fails, contact Unisys Support so a replacement could be installed as soon as possible. s-Par Failure Scenarios The following s-Par failure scenarios might occur on your FS6200 Server. A workaround is provided for each scenario. Note: s-Par only runs in the ISM module. Platform Services Do Not Complete Initialization Symptom Workaround After powering on the ISM, Platform Services initialization does not complete. In this case, the Management Card Virtual Console shows no progress on the screen and using the “s” command has no effect. Use the BMC web interface to power cycle the server. Contact Unisys Support if this action is has no effect. Cannot Connect to the Platform Console Symptom The user receives an error message from the web browser when trying to connect to the Platform Console 9–8 8222 3694–000
Workaround Use the platform management card to verify the server is powered on. Then, use the Virtual Console to verify that the Platform Services are running. Enter s at the prompt and verify that all of the components in the s-Par line are in RUNNING state as shown below. If not running, wait for each component to reach the RUNNING state. Ultra: =RUNNING =RUNNING =RUNNING =RUNNING sPAR: =RUNNING =RUNNING =RUNNING =RUNNING =RUNNING Guests: =RUNNING =RUNNING =RUNNING =RUNNING =RUNNING =RUNNING =RUNNING Press t-troubleshooting console, s-status summary, d-diag console, ?-help Environment Stuck in Starting Mode Symptom Workaround Note: The term “environment” refers to the I/O engine or a specialty engine in the ISM. Cannot connect to the environment through Remote Desktop and the Platform Console shows that the environment is stuck in Starting mode. From the Platform Console, restart the environment (graceful stop followed by start). Wait a few seconds for the state to change to Stopping, then Starting, and finally Running. If the previous action does not work, from the Platform Console, reset the environment (forceful stop followed by start). Wait a few seconds for the state to change to Stopping, then Starting, and finally Running. Contact Unisys Support if neither of these actions have no effect. The Platform State is Stuck in Stopping Mode Symptom Workaround Troubleshooting and Recovery Note: The term “platform” refers to the I/O engine or a specialty engine in the ISM. After performing a platform Shutdown or Restart command, the platform is stuck in Stopping state for an extended period of time (that is, more than 10 minutes). The most likely cause of this problem is that one or more environments did not reach the Stopped state. This can happen if the environment is waiting for user input, is stuck or hung, or missed the stop notification from the platform. As soon as all the environments reach the Stopped state the Platform Shutdown/Restart will resume. 8222 3694–000 9–9
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: Hardware Failure Symptoms Criticali
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 and 142: Restarting a JProcessor Specialty E
Page 143 and 144: Gathering Diagnostic Information Th
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?