FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Operating the Server • LCD Panel You can use the LCD panel on the front of the cell to monitor the initial phase of boot from power-off. Immediately after power-on, the LCD displays a ″System booting...″ message. This message is displayed until the hardware has finished initializing and the system BIOS starts to boot. Once the system BIOS has booted, the LCD displays the system name. • Virtual Console After the System BIOS starts booting, you can use the platform management card Virtual Console to display the messages displayed by the cell as it boots through the system BIOS and the BIOS on other hardware on the platform (for example, internal disk controller), and as s-Par boots and initializes (ISM only). To launch the Virtual Console for a particular platform, access the BMC web interface from the MCP Console of the platform. After logging in, click the Launch button on the right side of the screen to launch the virtual console • Platform Console You can access the Platform Console of the ISM from the MCP Console to view the status of the environments. Once s-Par has booted (ISM only) and it reports status of various component environments as ″Running″, start the Platform Console to monitor the status of the platform environments as they are started. • MCP Console You can access the MCP Console from the Operations Server or a remote workstation to view the state of the MCP Environment. Once the MCP Environment is loaded, use an MCP ODT to perform operations from within the MCP Environment. • MCP ODT You can access an MCP ODT from the Operations Server or a remote workstation to view the internal status of the MCP Environment and to perform operational tasks within the environment. Shutting Down the Platform The platform, including the component environments, can be gracefully or forcefully shutdown. Using either shutdown method also powers off the platform. Note: Before you shutdown the platform, halt the MCP using the MCP Console. • To shutdown the platform, access the MCP Console and from the Component View tab, right-click the System node and then click Shutdown (Graceful). • To forcefully shutdown the platform, access the MCP Console and from the Component View tab, right-click the System node and then click Shutdown (Forceful). 4–2 8222 3694–000
Powering Off the Platform Hardware You can power-off the platform hardware using either of the following methods but only use them if the methods listed under the topic “Shutting Down the Platform” earlier in this section are not available. • Press and hold the power button on the front of the platform hardware for four seconds. • Use the BMC web interface to remotely power off the platform hardware Note: This should only be done when the platform and all the platform environments have been shutdown. Restarting the Platform after a Shutdown The platform including the component environments can be restarted after either a graceful or forceful shutdown of the environments. Note: The Operations Server must be powered on, the systems management engine must be running, and the MCP Console must be accessible to perform this task. To perform a power-on after a graceful shutdown of the system, access the MCP Console from the Operations Server or a remote workstation. From the Component View tab, right-click the System node and then click Power On. Platform Services The s-Par software is used to subdivide the ISM. These subdivisions are called environments. The ISM hosts several environments, including specialty engines, that share the resources of the single hardware platform. The Platform Console provides an interface to the environments that exist in the FS6200 Server. Tasks You Can Perform from the Platform Console You can perform the following tasks from the Platform Console: • Environment tasks Environment tasks are commands you use to change the state of an environment. Examples include Run to start an environment and Shutdown to stop an environment. • Platform tasks Operating the Server Platform tasks are commands you use to control the platform. An example is changing the password of the Platform Console. Refer to the Platform Console Help for more information on environment tasks and platform tasks. 8222 3694–000 4–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 53 and 54: Using Sample BNA Initialization Fil
Page 55 and 56: Some of the procedures in MCP Imple
Page 57: Section 4 Operating the Server This
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 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?