FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Operating the Server 1. Connect the new devices and ensure that they have been discovered by the I/O engine environment. In some cases, such as adding new LUNs to a storage system, you must use Device Manager to scan for hardware changes outboard of each HBA that should have new devices visible to it. 2. Use the System Editor of the MCP Console and load the active PCD. The Adjust Resources dialog box is displayed that enables you add the new devices. 3. Accept the additions, changing device numbers and comments if desired, and then put the updated PCD into use on the running MCP by setting it active. The MCP displays a message about the PCD update. Added devices are initially in the MCP FREEd state and must be ACQUIREd to be used. This procedure is not restricted to newly connected devices. Older devices not yet assigned to the MCP can also be added by marking them for use by the MCP, even though they do not appear in the Adjust Resources dialog box. Devices cannot be dynamically moved (for example, swapping Fibre Channel cables between HBA ports) or removed from the PCD using this procedure. These actions require that the MCP be halted. You can dynamically FREE a device to stop the MCP from using it, but removing the device from the PCD can only be done when the MCP is halted. Power Cycling or Disconnecting Fibre Channel I/O Devices If you power down or disconnect an I/O device (such as a tape drive) and then immediately power it back on, it might become inaccessible to the I/O engine. After powering down or disconnecting an I/O device, give the I/O engine time to detect that the device was removed the Device Manager. Once that happens (or if it is not removed after two minutes), it is safe to power the device on or reconnect the device. It might then take plug and play some time to rediscover the device. If you lose access to a device due to doing one of these actions, follow the procedure outlined in the topic, “Troubleshooting Fibre Channel I/O Problems” in Section 7 of this guide to attempt to recover the device. Enabling MCP PING Commands through the Intra- Platform Connection for JProcessors Inbound Internet Control Message Protocol (ICMP) requests to the host of the JProcessor environment are blocked by default. This restriction affects PING commands, which are ICMP Echo requests. As a result, PING commands from remote computers cannot reach the JProcessor environment, not even those sent from the MCP. Refer to “Enabling MCP PING Commands through the EVLAN Connection” earlier in this section for information on how to add a firewall rule to enable inbound ICMP Echo requests. 4–30 8222 3694–000
Operating the Server PING commands are used for network target reconnaissance and can expose your environment to potential attacks. Therefore, be sure to restrict the scope of this firewall rule to appropriate intra-platform addresses only. 8222 3694–000 4–31
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 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: I/O Time • ACQUIRE • FREE • O
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?