FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Customizing the Server Configuration is achieved by reducing the number of frames an application must process. This improvement is particularly beneficial for applications that use large message sizes such as file transfers. The remote system and the connecting network equipment along the entire communications path must support jumbo frames to use this feature effectively. You can use Jumbo Frames with TCP/IP, BNA, and BNA over IP (BIP). In addition to the application message size, the performance benefits vary depending on which of these protocols you use. You must configure Jumbo Frames both within the I/O engine and within ClearPath MCP Networking. You must perform modifications on the system where the adapter exists. Perform the following steps in the I/O engine environment to configure Jumbo Frames on 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 View status of this connection, and then clicking Properties. 4. Click Configure under the adapter name. 5. Select the Advanced tab on the Properties screen. 6. Select the Jumbo Packet property. 7. Select one of the offered values. The proper value depends upon the capabilities of your network switching equipment. 8. Click OK. Within the MCP, you must set the following attributes to desired values for applicable lines (Connection Groups) and devices (Connections): • Max Input Message Size (MIMS) • Max Output Message Size (MOMS) • Max Input Message Size Limit (MIMSL) • Max Output Message Size Limit (MOMSL) The recommended frame size for Jumbo Frames is 9014, including the MAC header, but excluding the Cyclic Redundancy Check (CRC). Configure this value in the NIC driver and translate it to the following MIMS/MOMS/MIMSL/MOMSL values: • 9000 for the Connection Group • 9000 or 8996 for TCP/IP and BNA/BIP connections respectively Communications between a jumbo-capable and a jumbo-incapable end-system is generally not a problem. This follows because a common frame size is negotiated between the systems when they establish a dialog. This situation applies to TCP/IP, BNA, 3–18 8222 3694–000
and BIP protocols. Communications between a jumbo-capable and a jumbo-incapable end system is a problem for connectionless protocols such as UDP and ICMP because they are datagram-based and do not negotiate a connection. Each system transmits frames sized up to the mtu value of the system if no router is in the path. Any frames larger than 1,500 bytes are dropped if they are not supported by the receiver. The only potential issue occurs with the ICMP protocol—“pings” larger than 1,500 bytes fail. A useful technique in mixed networks is to logically segregate jumbo frame traffic from standard traffic by using IEEE 802.1Q Virtual LANs (VLANs). Using the System Editor to Configure MCP Networking If you need to modify the existing configuration of MCP networking on your FS6200 Server to match your environment, you must configure MCP networking through the System Editor of the MCP Console. Note: Any networking configuration change you make must also be reflected in the MCP initialization files. Refer to Appendix A of this guide and the TCP/IP Implementation and Operations Guide for details on modifying the MCP initialization files. You use the System Editor to perform networking firmware configuration and the configuration information is stored in the PCD file. The System Editor uses a matching algorithm to assign network processor numbers and Line IDs to the adapters that are installed in the system. These assignments are presented to the operator in the System Editor configuration tree view as the configuration default. You can modify that configuration as needed. The following features and rules apply to the use of System Editor when configuring networking. You can update the following networking characteristics: • The network processor number of the network processor node. • The Line Number of the line for a network processor node. • Movement of lines from network processor to network processor. • The EVLAN IP address on the I/O engine. • The EVLAN IP address mask on the I/O engine. • Enabling or disabling a line for MCP. • Deleting a network processor node with no lines. • Creating a new network processor node. Operational Rules Customizing the Server Configuration The following rules of operation apply to your use of the System Editor: 8222 3694–000 3–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: IEEE 802.1Q VLANs allow a single ne
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?