FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Setting Up and Operating the ePortal Specialty Engine Assigning ePortal Specialty Engine ISM-1 as a Standby ePortal <strong>System</strong> After ISM-1 or the ePortal Specialty Engine of ISM-1 is recovered from the failure while the ePortal Specialty Engine of ISM-1 was an active ePortal system and the ePortal Specialty Engine of ISM-0 took over as an active ePortal system, you must perform the following steps to assign the ePortal Specialty Engine of ISM-1 as a standby ePortal system: To avoid any confusion later in determining which is the active ePortal system, you should remove all virtual servers configuration from ISM-1 ePortal and modify the host name of ISM-1 ePortal Manager from EP1-Active to EP1-Standby by performing the following steps: 1. From the Component View tab of the MCP Console, locate the ePortal Manager for ISM-1 by clicking ePortal under ISM and s-Par ® and verify that the host name is EP1–Active (if the host name is EP0–Active, click ePortal under the other ISM and s-Par ® ). Then, launch the ISM-1 ePortal Manager website by right-clicking the ePortal and selecting Launch ePortal Browser. 2. Log on with the ePortal user account and password. Both the user and password are case-sensitive. 3. Remove all virtual server configurations from ePortal Manager website by following these steps: a. Click Virtual <strong>Server</strong>s on the list of links on the left side of the page. b. Click the virtual server name. c. Click Take Offline & Terminate Clients. d. After all members of the virtual server are in Ready/Offline state, click Manage Members. e. Select the check boxes for all PMs and then click the Remove button. f. Repeat the preceding steps for all virtual servers. Note: By removing the virtual servers, all of the PMs in the standby ePortal system will be in Ready/Unassigned state and you cannot deploy an application to the standby ePortal system 4. Click Controller in the list of links on the left side of the page. 5. Click Modify, change the name from EP1-Active to EP1-Standby, and then click OK. 6. Restart the ePortal Manager by clicking the Restart button under Operations from ePortal Manager Web site’s Controller menu. Note: Once the transition is complete, the Component View tab of the MCP Console should reflect the host name change in the ePortal under ISM and then s-Par ® , and you should be launching the new active ePortal Manager to manage the ePortal system. 5–18 8222 3694–000
Restoring ePortal The following actions occur when a standby ePortal system performs an ePortal restore operation during a transition to an active ePortal system: • Checks and installs the latest ClearPath ePortal IC Note: Keeping the IC level on the standby ePortal system up-to-date enables restoration process to skip this step and speed up the transition. • Rebuilds the database based on the latest backup generated on the previous active ePortal system • Restores virtual servers and applications Setting Up and Operating the ePortal Specialty Engine • Discovers and assigns personality modules to the virtual servers During the restoration process, a restore status page is displayed on the ePortal Management website. During the restoration, you cannot access any other section of the site since all functions are suspended until the restoration is completed. Due to browser caching, you might have to display a new browser window to see the restore status page. Also during restoration, the ePortal Controller restarts several times as required and the browser session might timeout during restart. This might require the refresh of the browser to see the latest status. Once all the steps are completed successfully, you can navigate back to the main section of the ePortal Management website. In an ideal situation, the standby ePortal system should have the same number of working PMs as the active ePortal system. If not, the restoration process allocates PMs to the virtual server based on the following rules: • Each virtual server contains at least one PM. If the virtual server number is greater than PM number, the virtual server that is online is restored first. A critical alert is raised before and after the restoration to remind you of the inadequate number of working PMs and possibly interrupted applications. • Every time a new PM is discovered, it is added to the virtual server most in need. For example, assume the ePortal system has two virtual servers: VS1 and VS2. VS1 should have two PMs and VS2 should have two. After the first round of PM allocation, both virtual servers have one PM. When the third PM is discovered, it is assigned to VS2. During the restoration, the assignment of PM names to a virtual server might change. For example, assume the active ePortal system had PM-1 and PM-2 assigned to VS1 and PM-3 and PM-4 assigned to VS2. After the restoration, VS1 might contain PM-1 and PM-3 and VS2 might contain PM2 and PM-4. Also, the dedicated IP address of the PM can be shifted amongst the PMs. Certain failure during the restoration process could put the whole ePortal system in an unstable state. For example, any failure during a rebuild of the database would make the ePortal Management website not accessible and the only way to recover from this type of failure is to reinstall the controller. Other failures are relatively minor and are recoverable. For example, if the controller failed to install the latest ClearPath ePortal IC, the IC can be installed manually after the restoration is finished. 8222 3694–000 5–19
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: Setting Up and Operating the ePorta
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 ...

Create successful ePaper yourself

Delete template?

Save as template?