FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Troubleshooting and Recovery such as time and date of the event, system type, system serial number, problem text, and other specific information that can be useful to Unisys support personnel. You can monitor these e-mail messages to take necessary action on possible system problems. Using Maintenance Mode Before performing hardware or software maintenance on the FS6200 Server, you can switch Call Home from Operational Mode to Maintenance Mode. This prevents Call Home events that are generated during the maintenance period from being converted to e-mail messages and sent to the Unisys Support Center. When maintenance is complete, switch Call Home back to Operational Mode. Refer to the MCP Console Help for details on switching modes. Problems with Call Home If there is a problem (or suspected problem) with the Call Home services, MCP Firmware Environment diagnostics should be taken to gather internal diagnostic information about the specific program components that comprise the Call Home functionality. This is necessary for Unisys support to diagnose the problem. In addition a Platform Environment diagnostics might also prove useful. Refer to the MCP Console Help for information on performing these dumps. Restarting an Environment To restart an environment, access the Component View tab in the MCP Console, rightclick the component name, and then click Restart. Click Yes to restart the environment. Diagnostic Tasks This subsection discusses the various tools you can use to diagnose problems on your FS6200 Server. Taking a Platform Environment Dump The Platform Environment Dump gathers platform diagnostic information that includes a platform dump and management card logs. A Platform Environment Dump contains: • Platform Firmware Livedump • Platform management card dumps and logs: sellog Refer to “Using Diagnostics” in the MCP Console Help for more information. Note: Due to the extensive nature of this dump, it can take over 15 minutes to complete. 9–4 8222 3694–000
Taking a Platform Firmware Livedump It is recommended that you use the MCP Console to take a Platform Environment Dump (which includes the Platform Firmware Livedump). However, if this method is not available, use following steps to generate a Platform Firmware Livedump from the Platform Console: 1. Access the Platform Console from the Component View tab of the MCP Console. 2. Click the Diagnostics link under the Platform heading to the right of the screen. 3. From the Platform Diagnostics screen, click Generate Dump to generate a Platform Firmware Livedump. Note: Due to the extensive nature of this dump, it can take over 10 minutes to complete. Taking an MCP Environment Dump An MCP Environment Dump is essentially the same as a Full Memory Dump taken by the MCP. During an MCP Environment Dump, a process reads the required dump information directly without using the MCP. This process creates a dump image file that can be read by the SYSTEM/DUMPANALYZER utility. The dump image file is McpDump.zdp. Where possible, full memory dumps should be taken from the MCP system using the ??DUMP command and converted into savedumps. You can use the MDT AUTOSAVE option to automate this conversion. The MCP Environment Dump can successfully obtain a dump in case the MCP memory dump routines fail for any reason. The McpDump.zdp can be created on the problem system and transferred to a working system for analysis without utilizing the problem system for processing. An MCP Environment Dump can be taken without interrupting MCP operation. However, dumps taken while the MCP is running are sometimes unusable if too much data changes while the dump is being taken. If at all possible, instead of taking this kind of “live dump”, it is recommended that you take a dump using the MCP system command ??DUMP or take the MCP Environment Dump after halting the system. Note: The MCP Environment Dump takes over five minutes to complete. If you can use the MDT FASTDUMP feature, a system dump using the ??DUMP command can complete in seconds. Refer to the MCP Console Help for details on performing an MCP Environment Dump. Taking an MCP Firmware Environment Dump An MCP Firmware Dump contains: • Configuration info • Device Maps Troubleshooting and Recovery 8222 3694–000 9–5
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: Accessing the Unisys Product Suppor
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 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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?