FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Operating the Server Call Home requires initial on-site configuration before it is ready for use. Typically, the initial configuration of Call Home is performed by Unisys support personnel as part of the FS6200 Server system installation. If you need make configuration changes after installation, use the MCP Console. Refer to “Managing Call Home Services” in the MCP Console Help for more information. This subsection addresses tasks you can perform to ensure Call Home services is operational. Using Maintenance Mode When Call Home services is in Operational mode, it is fully operational and sends Call Home e-mail alerts to the Customer Support Center and the configured customer e-mail addresses. When Call Home services are in Maintenance mode, it does not send Call Home e-mail alerts to the Unisys Support Center and the configured customer e-mail addresses. Maintenance mode is intended to be used when hardware or software maintenance is to be performed on the system and you want to prevent any alerts from being sent until the maintenance is completed. Refer to the MCP Console Help for details. Testing E-mail Alerts You can send a special test e-mail alert message to Unisys Call Home Support that automatically returns an e-mail confirmation. This can be used to test the Call Home hardware and software configuration on the FS6200 Server and the communications path to and from the Unisys Support Center. Refer to the MCP Console Help for details. Testing E-mail Heartbeats You can manually send a heartbeat e-mail message to Unisys Support Center. This can be used to test the Call Home software configuration on the FS6200 Server and the communications path to and from the Unisys Support Center. Refer to the MCP Console Help for details. I/O Services Use the system command SC to obtain a general overview of your I/O configuration. The following terminology is used in the display output. • IOP • STORAGESYSTEM • CHANNEL (similar to PORT on previous MCP systems) • TAP (similar to CTL on previous MCP systems) To obtain a detailed view of your I/O configuration, use the SC+ system command. The following system commands use the new I/O terminology in displays and command input on the FS6200 Server. 4–28 8222 3694–000
I/O Time • ACQUIRE • FREE • OL • RF • SC • UR Refer to the System Commands Reference Manual for further details on the preceding commands. The FS6200 Server I/O architecture is capable of having multiple I/Os active to a disk at a time, resulting in improved throughput and I/O rates on FS6200 Server systems, especially when doing a heavy I/O load to VSS2 disks. However, this can cause I/O time reported on the FS6200 Server to be larger than on previous MCP systems because it is accumulated simultaneously for these multiple active I/Os. Larger I/O time is simply an accounting difference that occurs because some of the I/O queue is in the storage system on the FS6200 Server. Larger I/O time does not mean it takes longer to perform I/O operations. On the contrary, reductions might occur, potentially resulting in smaller elapsed times for program execution than on other MCP systems of the same performance level. As a result, you cannot meaningfully compare I/O time on the FS6200 Server to I/O time on previous MCP systems. Larger I/O time is expected (up to 8 times larger) and does not indicate a problem. What matters are statistics like overall I/O rates and the elapsed time of transactions. These increased I/O times can be seen in the ACCUMIOTIME task attribute as well as I/O times recorded in file close and end-of-task SUMLOG records. If you use the IOTIME queue attribute or the MAXIOTIME task attribute, you might need to increase the values you assign to these attributes. Performing Dynamic PCD Updates The I/O configuration of the MCP is more flexible on the FS6200 Server than on previous MCP systems. You can place new devices, not yet in the PCD, into use by the MCP without performing a halt/load operation. Perform the following steps to dynamically place devices into use: Operating the Server Note: This procedure should not be done while the MCP is executing a heavy I/O workload as some steps take longer and could possibly time out. 8222 3694–000 4–29
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 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: • Total processor utilization rep
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 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?