FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Setting Up and Operating the JProcessor Specialty Engine In addition to the audit settings, the audit security template—SCWAudit.inf—is included in the Policy. This template helps detect tampering or attempted tampering of the operating system. Write access by any user to any executable or configuration files in the directory structure, and changes to the state or configuration of Windows services are recorded in the security log. Security Event Log size in the JProcessor environment is kept at the default size of 20MB. You can modify the auditing policy and the event log size according to your corporate policy and specific usage characteristics. Changing IP Address Scope for JProcessor MCPConnect Firewall Rules There are four firewall rules created to open all TCP ports for the intra-platform connections on JProcessor 1, JProcessor 2, JProcessor 3, and JProcessor 4. They are named “JProcessor MCPConnect1 (TCP-In),” “JProcessor MCPConnect2 (TCP-In),” “JProcessor MCPConnect3 (TCP-In),” and “JProcessor MCPConnect4 (TCP-In)”, respectively. In the firewall rules, IP address scope is defined to use the preconfigured values in Table 6–1, as follows: • For JProcessor MCPConnect1 (TCP-In), 192.168.16.141 and 192.168.16.142 • For JProcessor MCPConnect2 (TCP-In), 192.168.16.145 and 192.168.16.146 • For JProcessor MCPConnect3 (TCP-In), 192.168.16.149 and 192.168.16.150 • For JProcessor MCPConnect4 (TCP-In), 192.168.16.153 and 192.168.16.154 If you changed the intra-platform IP addresses from these preconfigured values, perform the following steps to adjust the IP address scope in these firewall rules. Otherwise, connections between the MCP and your JProcessor through the intra-platform connection will be blocked. 1. From the desktop of the JProcessor environment, start the Server Manager by clicking the Server Manager icon on the taskbar. The Server Manager icon is the first icon to the right of the Start button. 2. From the left pane of the Server Manager window, expand the Configuration node. 3. Expand the Windows Firewall with Advanced Security node under Configuration and then select Inbound Rules. 4. In the pane under the heading Inbound Rules, JProcessor MCPConnect1 (TCP-In), JProcessor MCPConnect2 (TCP-In), JProcessor MCPConnect3 (TCP-In),and JProcessor MCPConnect4 (TCP-In) are displayed. 5. To change either rule, double-click on the rule name. The Properties dialog box for that rule displays. 6. Select the Scope tab and then you can change the IP addresses as needed. The Local IP address on the Scope page refers to the IP address of the JProcessor environment and the Remote IP address refers to the MCP IP address. 7. When you are done, click OK. 6–6 8222 3694–000
Section 7 Backing Up MCP Firmware Configuration Data This section provides information on backing up and recovering your system configuration data. When to Back Up When you modify the system configuration, perform a backup on the Operations Server to save the changes. The recommended method for backing up the critical configuration data is to back up the information to external media, such as a DVD or disk drive. Note: Backing up MCP data, including customer data and configuration information, should be performed using tools and solutions available in the MCP Environment. It is not covered in this document. Refer to the ClearPath Enterprise Servers Server External Disk and Tape Storage Systems Configuration Guide for information. Performing the System Backup Perform the following backup procedure from the Operations Server when you have completed your initial system configuration. Also, repeat the backup process each time you modify your system configuration. 1. To begin a PowerShell session, click the PowerShell icon on the taskbar of the Operations Server. The PowerShell Console window is displayed. 2. Access the MCPPartition subfolder by typing cd “C:\Program Files\Unisys\MCP Firmware\MCPPartition” Note: This input is not case-sensitive. Ensure that either double or single quotation marks surround the path name. Then, press Enter. 3. To invoke the backup script, type .\Backup-Item 8222 3694–000 7–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 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: Applying JProcessor Security Policy
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?