FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Troubleshooting and Recovery If you need to send problem materials for this issue and you have attempted these recovery procedures, take a second MCP Firmware Environment Dump. Include the MCP Firmware Environment dump taken at the start of this procedure, the second dump (if taken), a detailed description of the recovery actions you attempted, and MCP SUMLOGs covering the time period when access to the device was lost. Device is Visible in the I/O Engine Environment But Inaccessible from the MCP Consider the following suggestions to resolve this situation. • Review MCP messages and waiting entries as well as messages in the SUMLOG. These might indicate a specific device or path to check. Also use the RF command on the affected devices, particularly the affected taps; the command response contains error statistics that can help identify a problem. • Be aware that if there has been an outboard problem causing loss of paths that has been repaired, it might take some time for the device to come back on line, especially if the FS6200 Server is still running with a significant I/O load. If the I/O engine environment is busy rediscovering devices, the MCP might not be able to successfully access any of them until the rediscovery of devices is complete. • You might sometimes need to perform the UR command and then a UR− command on a channel, tap, or device to get it back in service. If this does not succeed, UR− should result in new system messages about device access problems that may help diagnose the problem. If the messages indicate that a recovery activity is in progress, wait a while and try the UR and UR− commands again. • If none of the preceding suggestions work and the device remains visible in the I/O engine environment but inaccessible from the MCP, problem materials should be collected at this point for potential submission to Unisys support including a detailed description of the recovery actions you attempted, an MCP memory dump, SUMLOG, and MCP Firmware Environment dump. • The next recovery steps to attempt are to halt/load the MCP, restart the I/O engine environment, or restart Platform Services. If the problem persists, contact Unisys support. Recovery Actions This subsection lists recovery action you can perform for your FS6200 Server. Recovering FS6200 Server Configuration Data You can recover FS6200 Server system configuration data, such as PCD files, by running the Restore-Item scripts. Ensure that you are logged on to the Operations Server as an administrator and then perform the following procedure. 1. To begin a PowerShell session, click the PowerShell icon on the taskbar. The PowerShell Console window is displayed. 2. Access the MCPPartition subfolder by typing 9–24 8222 3694–000
cd “C:\Program Files\Unisys\MCP Firmware\MCPPartition” Note: This input is not case-sensitive. Ensure that either double or single quotation marks surround the path name. Then, press Enter. 3. To invoke the recovery script, type .\Restore-Item Notes: • The .\ notation before the script name is important as it denotes the current path. Without this notation, PowerShell cannot locate the script file. • When running the recovery script, the parameter specifies the location from which to restore the critical files for your system. The parameter can be set to any one of the following: a CD/DVD drive, a mapped network drive, or a URL. The syntax structure for the parameter can be • a CD/DVD player or mapped network drive location. For example, z:\Backup • a URL location. For example, \\servername\sharedfolder\temp If you plan to specify a URL location for the parameter, before running the script, ensure that the URL location can be accessed with the current system credentials. Otherwise, a script failure can occur. Then, press Enter. The script prompts you for confirmation before initiating the recovery. 4. Press Y to continue the recovery. The recovery takes a few seconds to complete. At completion, the following message is displayed: files copied from Restore-Item completed successfully. 5. If you do not want to continue, press N to cancel the recovery. Powering Down a Cell to Replace Failed Hardware Use one of the following methods to power-down a cell. Troubleshooting and Recovery Note: Be sure to halt the MCP using the MCP Console before performing any of the following actions. 8222 3694–000 9–25
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 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: The topic “I/O Configuration” i
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?