FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Customizing the Server Configuration Table 3–1. Physical Location of HBA Ports to entries in Device Manager or Channels listed by the SC+ ODT Command (cont.) Physical Location Slot Port 6 0 Storage controllers Device Manager MCP Emulex LPe12004-M8, PCI Slot 6,{ Location: PCI Slot 4 (PCI bus 0, device n, function 0) 1 Storage controllers Emulex LPe12004-M8, PCI Slot 6,{ Location: PCI Slot 4 (PCI bus 0, device n, function 1) 2 Storage controllers Emulex LPe12004-M8, PCI Slot 6,{ Location: PCI Slot 4 (PCI bus 0, device n+1, function 0) 3 Storage controllers Emulex LPe12004-M8, PCI Slot 6,{ Location: PCI Slot 4 (PCI bus 0, device n+1, function 1) CHANNEL IOP 1 TYPE PCI POSITION 0,n,0 Emulex LPe12004-M8, PCI Slot 6, { CHANNEL IOP 1 TYPE PCI POSITION 0,n,1 Emulex LPe12004-M8, PCI Slot 6, { CHANNEL IOP 1 TYPE PCI POSITION 0,n+1,0 Emulex LPe12004-M8, PCI Slot 6, { CHANNEL IOP 1 TYPE PCI POSITION 0,n+1,1 Emulex LPe12004-M8, PCI Slot 6, { Hot Reuse of Fibre Channel in a Channel Group is Not Supported You cannot disconnect a Fibre Channel device from an HBA, and connect a different device to the same HBA. This action violates Unisys policy which disallows dynamic deleting of fibre devices while the MCP is running. Specifically, when these fibre devices are a part of a channel group, the MCP has a working knowledge of all paths to a device. When those paths are changed while the MCP is running, it creates confusion that can only be resolved by halting the MCP and loading the new configuration. You cannot reuse a Fibre Channel if the following conditions exists: 3–6 8222 3694–000
• The MCP is running. • The path to devices that are being added is replacing the path to devices already “owned” (usage equals MCP Use) by the running MCP. • The path being removed is part of a channel group containing multiple channels. • The path being added is not connected to the same string of devices that was removed. Attaching Additional Fibre Channel Cables The FS6200 Server installation process includes disabling all unused Fibre Channel ports because this results in faster environment startup times. If you connect additional Fibre Channel ports at a later time, you might need to enable those ports. If you permanently stop using Fibre Channel ports, you should disable them. Enabling Fibre Channel Ports To enable Fibre Channel ports: Note: Perform this procedure on each ISM with unused Fibre Channel ports. 1. Record the unused ports as follows: a. Locate the unused HBA ports on the back of the ISM. The HBA slot number is stamped near the HBA slot. b. For each unused HBA Port, record Slot Number and Port number. Note: A horizontal Quad Port HBA has Port 0 on the right and Port 3 on the left. 2. Disable the unused port(s) as follows: a. From the Operations Server, double-click the MCP Console icon. b. Click Component View. c. Expand the ISM with the unused Fibre Channel ports and then expand s-Par ® . d. Right-click I/O Engine and select Launch RDP Session. e. Log on to the environment. f. Click Start, and open the Control Panel. g. Click Hardware h. Click Device Manager. i. Expand the Storage Controllers node. Customizing the Server Configuration There will be four entries listed for each HBA which will all have the same Slot Number. j. Right-click each HBA in the list that identifies a Slot Number from the list of Ports to be disabled and then select Properties. k. Under the General tab locate the Location information which is of the form: 8222 3694–000 3–7
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: Table 3-1. Physical Location of HBA
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 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?