FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Customizing the Server Configuration Setting the Local Address The MAC address for a network adapter is set through the Network Connections Control Panel applet. You cannot set the MAC address of an adapter through the local address attribute of an ADD CONNECTION GROUP command in your CNS initialization file. You can interrogate the current MAC address of an adapter using the NW CONNNECTION inquiry on the Connection Group. You must make modifications on the system where the adapter exists. From the MCP Console on the Operations Server, start a Remote Desktop session to the appropriate I/O engine and perform the following steps to override the factory assigned MAC address of an adapter. Perform the following steps in the I/O engine environment to override the factory assigned MAC address of an adapter: 1. Start Device Manager. 2. Select the adapter that you want to modify. 3. Adjust the properties of the adapter by right-clicking the adapter and selecting Properties or by selecting Status, and then clicking Properties. 4. Click Configure under the adapter name. 5. Click Advanced tab on the Properties screen. 6. Select the Locally Administered Address property. 7. Enter your desired address in the Value box. 8. Click OK. TCP Offload Settings TCP Offload Engine (TOE) options within the Advanced Adapter Settings of a NIC are incompatible with MCP use of adapters. You should turn off all TOE features on any adapters that are to be used by ClearPath MCP Networking. TOE features include IPv4 Checksum Offload, Large Send Offload, TCP Checksum Offload, and UDP Checksum Offload, among others. Preparing to use Adapter Teaming and IEEE 802.1Q Virtual LANs Network Services MCP network adapter software supports Adapter Teaming and 802.1Q Virtual LANs (VLANs). You can use Adapter Teaming to provide fault tolerance at the adapter level (ClearPath MCP Network providers TCP/IP and BNA have alternate means of providing fault tolerance as well). Note: Although Adapter Teaming can also be used to perform port aggregation, distributing network traffic across multiple adapters, this type of team offers marginal value for ClearPath MCP customers and is not recommended. System and user programs see a single virtual adapter team instead of the individual adapters that make up that team. 3–16 8222 3694–000
IEEE 802.1Q VLANs allow a single network adapter to segregate its traffic among two or more virtual LANs. Each VLAN on an adapter is represented by a separate network adapter entry within the Network Connections Control Panel applet, effectively making a single adapter appear to Network Services as more than one adapter. IEEE 802.1Q VLANs are based on the addition of a 4-byte tag to the packet header, identifying the VLAN for that packet. Adapters that are to be used in an adapter team or that are to support VLANs should be set to “Unassigned” through the Networking Configuration tool before building the team or configuring the VLANs. You must perform modifications on the system on which the adapter exists. After removing the MCP assignments for any adapters you want to modify through the System Editor, use remote desktop to the appropriate I/O engine, and modify the adapter settings for VLANs and teaming. Adapter Teaming and VLANs are configured using Intel® PROSet for Device Manager. Intel® PROSet is an extension of Device Manager. As a result of the installation of the Intel® PROSet software, additional tabs have been added to the supported Intel adapters in Device Manager You must have administrative rights to use Intel® PROSet. Refer to the Intel Network Adapters User’s Guide for additional information about creating and managing Adapter Teams and VLANs. If the FS6200 Server is a member of only one VLAN on a given adapter port, tagging is not necessary on that port. Turn tagging off at the switch port and configure the LAN Switch port to be a member of the appropriate VLAN instead. No VLAN tagging should be configured at the FS6200 Server. If the FS6200 Server is to be a member of multiple VLANs over the same adapter port, then both the LAN switch and the FS6200 Server must be configured. The switch connected to the FS6200 Server must support IEEE 802.1Q tagging. Perform the following steps to modify the adapter settings for VLANs and teaming: • At the switch, tagging should be enabled, and all VLAN ID assignments made at the specific port. Follow any other vendor-specific instructions that might exist. • At the FS6200 Server, use Intel® PROSet Device Manager to assign desired adapters to teams. • For each VLAN defined and each Adapter Team defined, a new “adapter” is created that is visible in Device Manager. • Also, the CNS and TCP/IP initialization files on the MCP must be updated to reflect the addition of the Line (NP/Line ID pair). Preparing to Use Jumbo Frames Customizing the Server Configuration Jumbo frames are large Ethernet frames used in high-performance networks (up to 9000 bytes of payload) to increase performance over long distances. Jumbo Frames improve ClearPath throughput and reduce the CPU cycles used for networking. This improvement 8222 3694–000 3–17
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: Changing the Network Services EVLAN
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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?