FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

System Overview Platform Console You manage s-Par including platform and environment status, using the Platform Console. You access the Platform Console from the Operations Server. Platform Management Card You perform low-level management of server hardware components using the platform management card. You perform these management tasks from the Operations Server using the Baseboard Management Controller (BMC) Web interface. The BMC Web interface is the UI for the platform management card that you use to monitor the hardware components of the system. Each cell (OPS, ISM, and PMM) has a platform management card. Management Card Virtual Console Using the Virtual Console, you can display platform messages as the platform boots through the system BIOS and any BIOS on other hardware, and as s-Par boots and initializes. ePortal Manager To manage ePortal, you access the ePortal Manager website from the MCP Console. Note: If an optional external ePortal Enterprise system is attached to the FS6200 Server, you access the ePortal Manager by double-clicking the ePortal Manager icon on the desktop of the Operations Server. 2–8 8222 3694–000
Section 3 Customizing the Server Configuration This section discusses issues you should consider for customizing the configuration of your FS6200 Server. You should perform these tasks after your service representative completes setting up the FS6200 Server. Configuring I/O This subsection provides topics you should consider when setting up your I/O configuration on the FS6200 Server. Configuring Storage The FS6200 Server supports Virtual Sector Size (VSS) disks on external storage. Logical disks are not supported on external storage. Storage systems with VSS disks, including active-active and active-passive disk storage systems, are fully supported by the FS6200 Server MCP. You access the OCManager installed in the systems management engine environment to display useful I/O subsystem information. However, you should not use it to adjust system settings unless directed by Unisys support. In particular, do not set persistent binding on the storage logical units (LUNs). The Fibre Channel Host Bus Adapters (HBAs) are available for your configuration. Refer to the Server External Disk and Tape Storage Systems Configuration Guide for details. There are four PCIe slots per ISM available that can be used for up to three HBAs or NICs in any combination. Each HBA has four Fibre Channel ports. Therefore, there are up to 24 Fibre Channel ports which is the maximum number of ports. The Fibre Channel HBA ports can be used to access a disk storage system. Direct connect and fabric configurations are both supported. In the case of a fabric configuration, each HBA port can be given access to either one or two taps in the storage system. For a resilient storage system configuration, at least two HBA cards in separate ISMs must have paths that provide access to the storage system and these paths should make use of storage ports in at least two storage processors/directors within the storage system. In a fabric configuration, the best resiliency requires having those paths traverse two physically separate fabrics. An external halt/load unit with paths from each ISM should be configured for production use of the server. 8222 3694–000 3–1
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: ePortal Specialty Engine The ePorta
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 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?