FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Customizing the Server Configuration • Modification of an active PCD must be done while the MCP is halted. • Network processor numbers and I/O device numbers are not allowed to overlap. • Default network processor numbers are in the range from 200-299. • The entries for the EVLAN, JProcessor Specialty Engine, and ePortal connections appear on the first designated network processor for each defined I/O engine. • The entries for the EVLAN, JProcessor Specialty Engine, and ePortal connections have defined line numbers that cannot be modified. • The remaining network processors show the connections (on NICs and virtual NICs) that are visible within the I/O engine. • Checking or unchecking of lines or network processor instances determines whether or not that adapter is bound to the MCP networking service. • Lines or network processors that are not bound to the MCP are not checked. Note: The FS6200 Server networking allows adapters to be used only as MCP network adapters exclusively or adapters assigned to the MCP Firmware I/O engine exclusively. Configuring MCP Networking Using the System Editor Perform the following steps to configure MCP networking: 1. Launch the MCP Console on the Operations Server. 2. Click the System Editor button on the toolbar of the MCP Console. 3. Perform one of the following actions to open a PCD file: • Open the active PCD file you want to edit by selecting Active from the toolbar. • Open an existing non-active PCD file you want to edit by selecting Open from the toolbar. • Click the Adjust Resources button to auto-adjust the PCD file that is open if necessary. Note: If the PCD file needs adjusting since the last time it was used, the auto-adjust window appears and does not require you to click the Auto Adjust button. • Open a new PCD file causing the launch of an auto build of a PCD by clicking the New button. The PCD file is ready to be edited. Note: For a new PCD that uses the default System Editor assignments, no further modification might be necessary. If this is the case, proceed with step 8. Otherwise, continue with step 4. 3–20 8222 3694–000
4. To modify a network processor object, locate the NP object you want to modify and perform the appropriate actions as follows: • To modify the network processor instance identifier, select the NP object and on the Properties panel and update the NP instance identifier field . • To remove the NP from being enabled by the MCP Firmware of the I/O engine, uncheck the check box for that NP. • To assign a NP to be enabled by the MCP Firmware of the I/O engine, select the check box for that NP. 5. Perform the following steps to modify the properties of an EVLAN line on a NP: a. Type the IP address in the EVLAN IP Address field for the EVLAN connection object. The IP address that initially appears is the default. If you enter a different value, it is used to modify the IPv4 address of the EVLAN adapter in the IOE. A value entered here is stored in the registry of the I/O engine and appears the next time you use System Editor to configure MCP networking. b. Type the subnet mask in the EVLAN IP Address Mask field of the EVLAN connection object. The subnet mask that initially appears is the default. If you enter a different value, it is stored in the registry of the I/O engine and appears the next time you use System Editor to configure MCP networking. 6. To modify a line object, locate the line object of the adapter you want to modify and perform the appropriate actions as follows: • To return an MCP network adapter to the control of the I/O engine, locate the line for the adapter you wish to modify and uncheck the check box for that line. • To assign a NIC or a virtual adapter as an MCP network adapter, locate the line for the adapter you want to modify and check the check box for that line. • To modify the line instance identifier, select the Line object and update the Line ID field in the Properties panel. 7. Verify the accuracy of your settings. If any changes are needed, remain in the configuration tree view and complete any necessary modifications. 8. Save the PCD by clicking the Save button. 9. If necessary, ready the PCD for operation by clicking the Set Active button. A dialog box might be displayed indicating that a reboot of the I/O engine is required. 10. Click Yes to reboot the I/O engine. Customizing the Server Configuration The networking settings are written to the registry of each affected I/O engine. If you have changed any adapter line numbers or the network processor numbers of existing MCP connections, the necessary protocol bindings of the adapters are modified. This process can take several minutes to complete. The appropriate Net icon in the MCP View tab of the MCP Console is offline during the reboot. When the I/O engine finishes rebooting, the appropriate Net icon in the MCP View tab of the MCP Console is running and the network configuration is available. Note: You might need to adjust the network initialization files to match the updated configuration. 8222 3694–000 3–21
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 BIP protocols. Communications b
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 ...

Create successful ePaper yourself

Delete template?

Save as template?