FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Troubleshooting and Recovery Problems Mapping to a Client Access Services Share If you are unable to map to a Client Access Services share in the MCP Environment, first verify that you can PING the MCP Environment by IP address and by MCP Server Name. If either of these actions fails, follow the troubleshooting suggestions for TCP/IP networking issues and fix those capabilities first. If you are still unable to access Client Access Services after getting PING working, consult the following resources: • The topics “Using Client Server Applications” and “Integrating Your Server with Microsoft Networks” in the MCP Implementation Guide • Client Access Server Administration Guide • Client Access Server User Guide Fatal System Error If a fatal system error (also known as a Blue Screen or STOP error) occurs on one of your FS6200 Server operating environments, submit the following materials to Unisys support. • \Windows\Memory.dmp • The matching MiniDump from \Windows\Minidump • From the MCP Console, take a diagnostic dump with the MCP Environment and Platform Environment dump options. Follow the steps outlined in “Transferring Diagnostic Data from the MCP Environment to Unisys Product Support” earlier in this section to transfer the materials to Unisys for analysis. You are most likely to notice that the MCP Firmware Operating Environment suffered a fatal system error when a popup message appeared within a Remote Desktop session to the operating environment. The popup message notifies you that the system recovered from a serious problem. You also might be notified of a fatal system error if you monitor Call Home event e-mail messages. Network Services Failure Scenarios The subsection discusses how to submit a networking trouble report and how to perform dumps related to Network Services. Initiating a Dump There are two options available to initiate a dump of networking information on a FS6200 Server. 9–12 8222 3694–000
• Obtain a Network Services firmware dump from the MCP Console: 1. Click Select from the Diagnostics tab. The Select Diagnostics dialog box appears. 2. Ensure that the Network Services check box is selected. 3. Click Start. The Diagnostics tab of the MCP Console displays the status of the system diagnostics and component diagnostics. The diagnostic operation is finished when the Overall status in the Summary panel displays Completed. 4. Submit the entire system diagnostic package file along with your UCF to Unisys support. • Obtain a network services firmware dump from the MCP environment: 1. Issue the command NW DUMP NP from an authorized user within the MCP Environment. This command captures a snapshot dump of all of the NPs that share an I/O processor with the NP specified in the command. This command differs from issuing the request through the MCP Console because it does not cause the information that is captured to be transferred to the Operations Server. 2. To transfer the captured information to the Operations Server, use the first option for initiating a dump. It captures an additional dump, but both dumps are included in the captured dump data. For more information, see the DUMP NP command in Section 4, “Operational Considerations” of this guide. Location of the Dump Data When the dump is obtained through the MCP Console, the firmware dump data is available on the Operations Server at the location specified on the Diagnostics tab of the MCP Console. Within this file is a zip file with diagnostic information for each I/O engine. That file, if the Network dump option was selected when the dump was requested, contains the zip file with the Network Services firmware dump information. When the dump is obtained through the NW DUMP command, the time stamped firmware dump data with the name reported in the system sumlog is placed in a separate file on the I/O engine where the NP is located. The timestamp is formatted as YYYYMMDD_hh.mm.ss. YYYY is the four-digit year, MM is the two-digit month, DD is the two-digit day, hh is the two-digit hour, mm is the two-digit minute, and ss is the two-digit second of the timestamp at the creation of the dump. The Network Services Dump zip files contain the following items from each NP on the system: • Trace file information • Probe file information • Setup log file • Configuration Utility log file Troubleshooting and Recovery 8222 3694–000 9–13
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: • If your TCP/IP or BNA connectio
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?