FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Customizing the Server Configuration You might be able to use your FS6200 Server as delivered without modification to the default network configuration. However, you might want to integrate your FS6200 Server into your existing network. The following topics describe the general steps required to configure Network Services to operate within your network environment. Default Networking Configuration The following text describes the default networking configuration for your system. • The default host name of the MCP server for this environment is CPMCP1. • You use the System Editor of the MCP Console to assign NP numbers and Line IDs to the network interfaces within each I/O engine according to the following rules. - The intra-platform connections for a system are located on the initial NP defined for each I/O engine. - The Line ID assignments for the intra-platform connections are pre-assigned and cannot be modified. Table 3-2 lists the default NP instance numbers for each I/O engine. Table 3–2. Default NP Instance Numbers for Each I/O Engine IOE-1 IOE-2 210 220 The NP instance and Line ID number assignments for the I/O engine for external connections are based on the adapter Slot#/Port# of the device. The following equation is used to define the expected network processor instance numbers for the I/O engine. network processor instance number = (200 + 10 x IOP number + (slot number % 10)) The default Line ID value equals the port number of the device. In this case, the following table lists the NP numbers assigned by the System Editor (assuming slot values of 1 through 10). Table 3–3. Default Network Processor Values for External Connections on FS6200 Server I/O Engines PCI Slot Number IOE-1 IOE-2 1 211 221 4 214 224 5 215 225 3–10 8222 3694–000
The default IP address for the intra-platform connections on each I/O engine are listed in the following table. There can be more than one MCP IP address for ePortal that is active at a time, whether local or remote. Note: Refer to the JProcessor Specialty Engine and ePortal Specialty Engine topics in this guide for more details. Table 3–4. Default IP Address Values for MCP on the FS6200 Server for each I/O Engine IOE Entity Name MCP IP Address IP Address Mask Line Number IOE and Specialty Engine IP Address 1 EVLAN 192.168.16.5 255.255.255.252 0 192.168.16.6 1 JProc1 192.168.16.141 255.255.255.252 1 192.168.16.142 1 JProc3 192.168.16.149 255.255.255.252 2 192.168.16.150 1 ePortal 192.168.223.250 255.255.255.0 3 2 EVLAN 192.168.16.9 255.255.255.252 0 192.168.16.10 2 JProc2 192.168.16.145 255.255.255.252 1 192.168.16.146 2 JProc4 192.168.16.153 255.255.255.252 2 192.168.16.154 2 ePortal 192.168.224.250 255.255.255.0 3 The following tables provide a summary of the standard configuration for each I/O engine. Table 3–5. Default Networking Values on the FS6200 Server IOE-1 PCI Slot Network Port NP Number Line ID IP Address Internal (management LAN) Internal (reserved) Internal (ePortal external connection) Internal (ePortal external connection) 1 (Left) Unassigned Not applicable 2 Unassigned Not applicable 3 Unassigned Unassigned, Not applicable 4 Unassigned Not applicable None EVLAN 210 0 192.168.16.5 None Internal path to JProcessor 1 Customizing the Server Configuration 210 1 192.168.16.141 8222 3694–000 3–11
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: e. Log on to the environment. f. Cl
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 ...

Create successful ePaper yourself

Delete template?

Save as template?