FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Troubleshooting and Recovery • The system SUMLOG • Dell Service Tag number for each cell (can be obtained from Component View of MCP Console) • Unisys Service Tag (if available) Supply Unisys product name, style, and serial number. • Level of MCP Firmware software including any updates • MCP level including any ICs • Network Services level including any ICs • List of platform software updates that have been applied • Total system memory size and the amount allocated to MCP When submitting trouble reports for the FS6200 Server, • Issues with the Network Services firmware component should be written against the NX/Net product. • Issues that appear to be problems with other FS6200 Server firmware components or with specialty engines should be written against product FS6200 and an appropriate component choice should be made. • Issues with the MCP or other MCP software products should be submitted against the appropriate software product rather than the Server product. How to Submit Information You can submit files on tape, CD-ROM, or DVD media. To submit files on tape, copy all files from non-MCP environments to an MCP Environment disk share and then use the MCP COPY command to copy all the materials to a tape. Information on submitting UCF materials through the Internet is available from the Unisys Product Support website at http://www.support.unisys.com For information on electronically routing UCF CONTACT materials to Unisys, see the link How to send UCF Materials to Unisys over the Internet on the Unisys Product Support website. This link can be found by clicking the Support Database link in the left pane of the Product Support Web page. For materials sent through FTP, follow-up with a notification e-mail message to wcucf.coordinator@unisys.com indicating the name of the files, the UCF contact telephone number, and the name of the FTP server. 9–2 8222 3694–000
Accessing the Unisys Product Support Web Site The Unisys Product Support website for the FS6200 Server contains valuable documentation, Technical Information Bulletins (TIBs), and links to product updates. You can also, register for e-mail notification of TIBs and new documents as they become available. Perform the following steps on the Operations Server or on any system with access to the Internet to access the Unisys Product Support website: 1. From an Internet browser, access the Unisys Product Support website at www.support.unisys.com 2. Log-on with your Support Online user credentials. 3. Under the ClearPath MCP Servers category, select FS6200 from the MCP Mainframes list and click Go. The FS6200 Support Site page is displayed. Using Remote Support Remote Support is a method of connecting to remotely located systems for remote administration, real-time diagnosis, system configuration and repair, or online file transfers. Note: Remote Support applies only to systems connected to the Internet. The best reason for using Remote Support is the significant reduction in time required diagnosing a problem on a remote system. Remote Support enables a Unisys Remote Support Analyst (RSA) to see exactly what the remote client is seeing in real-time as it is occurring on the system. It also gives the remote client the ability to watch the session and interactively participate with the RSA to resolve an issue. Refer to Product Support website for more details on Remote Support. Using Call Home This subsection addresses tasks you can perform to ensure Call Home services is operational. Monitoring the Call Home Event E-mails Troubleshooting and Recovery Call Home events can be generated by the MCP, the platform management cards, and the platform firmwares. The events are converted to e-mail messages and sent to the Unisys Support Center and up to three client-designated e-mail addresses. These e-mail messages have a Subject designation of “Call Home Alert” followed by an ID number and the system serial number. They contain information in an XML format that includes items 8222 3694–000 9–3
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: Section 9 Troubleshooting and Recov
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 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?