FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Updates The FS6200 Server Support Site page is displayed. 4. Click the desired support option under the following categories. • Fixes • Drivers and Downloads 5. Click the product IC level that you want to download. 6. Download the appropriate IC. 7. Move the IC you retrieved from the Unisys Support website to the following directory on the Operations Server. C:\Transfer 8. Follow the instructions included with the IC to install the update. Updating Firmware using the Master Installation Manager Update Script Master Installation Manager Update (MIM-Update) is a script that you run on the Operations Server to install firmware updates to your server. Updates supported by MIM- Update are distributed as update packages and posted on the Unisys Product Support website. The update package is a zip file that contains everything you need to perform the update of one or more firmware components. Step-by-step update installation instructions are also provided through either a readme file that is packaged with the update or a Unisys Technical Information Bulletin (TIB). To install a MIM-Update package: 1. Download the update zip package from the Unisys Product Support website. 2. Extract the contents of the package into C:\Unisys\Installation on the Operations Server. 3. To begin a PowerShell session, click the PowerShell icon on the taskbar of the Operations Server. 4. Enter the command .\MIM-Update.ps1. MIM-Update guides you through the process of installing the updates to all affected environments. You need Administrative privileges to install updates. MIM-Update prompts you to enter administrator credentials before attempting an update on a target environment. An attempt is made to use these credentials for all updates in the package. It is possible that these credentials might not be adequate to perform an update on a target environment. If this is the case, you are prompted again to enter different credentials. Some updates require a reboot. These reboots are automatically initiated by MIM-Update and are generally transparent to you. However, in the case of an update on the Operations Server, you must always restart MIM-Update after reboot so that it can continue the update process. 8–2 8222 3694–000
Updating MCP Firmware MCP Firmware updates are installed through the MIM-Update process. The following types of updates are available for MCP Firmware: • Service Pack (SP) An SP release is a scheduled update to the MCP Firmware. It consists of a full set of MCP Firmware files and can include fixes as well as new features. Installation of a SP package overrides any previous IC or CCU updates. • Interim Correction (IC) An IC update contains fixes for certain components in the MCP Firmware. The update package is incremental and accumulative. It does not necessarily need to be installed in all the environments on your server. It is for general distribution and applied against either the initial release of MCP Firmware or a Service Pack. • Customer Critical Update (CCU) A CCU update is an update for critical problems reported by a customer. It is not for general release but only distributed to the customers who experience a qualifying problem. CCU updates are numbered sequentially and are not accumulative. They are applied against a specific version of the MCP Firmware. Driver and PCI Card BIOS/Firmware Updates From time to time, driver and firmware updates for the various environments, such as Platform Services drivers, HBA drivers, NIC drivers and firmware or BIOS updates might be available. These updates are announced through Technical Information Bulletins (TIBs) on the Unisys Product Support website. Contact your Unisys CSE or Unisys Support to schedule an update for your system. Updating Network Services This subsection presents topics related to updating Network Services. Updates Network Service Firmware updates are installed through the MIM-Update process. Refer to section “Updating Firmware Using the Master Installation Manager Update Script” for more information on that processing. Network Services updates are included in FS6200 Server firmware update packages. Consequently, there is no need to download and install Network Services ICs independent of the firmware update process. Every Network Services update is cumulative so it can be used to update any prior Network Services installation. Note: When you install a Network Services update through the MIM-Update process, the Network Services package is automatically pushed to each I/O engine and the steps required to install Network Services on that I/O engine are performed. Follow the instructions in the Firmware Update package for the specific steps associated with updating Network Services. 8222 3694–000 8–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: Section 8 Updates This section disc
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 ...

Create successful ePaper yourself

Delete template?

Save as template?