FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Troubleshooting and Recovery Take detailed notes of the problem and the steps you took to attempt to resolve the problem. These notes often prove invaluable in enabling Unisys support to help you resolve local issues as well as issues with the FS6200 Server. Review MCP messages and waiting entries as well as messages in the SUMLOG. These might indicate a specific device to check. You might also need to review storage system and fabric switch logs. Be aware that if you find an external problem, such as a bad cable, and repair it, it might take some time for the device to come back on line, especially if the FS6200 Server is still running with a significant I/O load. Under certain circumstances you might also need to take action in either one of the environments or the MCP Environment to recover the device. These actions are covered in the following subsections. If there does not seem to be outboard or cable problems, consider the following situations. Problems Accessing Newly Connected I/O Devices If you are having problems accessing devices that you have just connected, such as during initial installation of the FS6200 Server or later after adding I/O devices to the system, the issue may be that the devices are not configured properly for use on the FS6200 Server. If you have migrated I/O devices from a previous system, it is possible that some device settings need to change for use by the FS6200 Server. The ClearPath Enterprise Servers Server External Disk and Tape Storage Systems Configuration Guide includes configuration information that must be followed when configuring devices for access from the FS6200 Server. In particular, this document includes required settings for EMC storage systems. You should also check FS6200 Server TIBs to see if any additional configuration requirements have been documented after publication of these manuals. Device is Not Visible in the I/O Engine Environment These procedures are for the case when Device Manager in the I/O engine environment does not show the device. If a device in the PCD is visible in Device Manager, then the MCP should be able to access it. This problem might be external to the FS6200 Server and the storage and storage connections should be reexamined for problems. If no external problems (including bad cables) are found, it is advisable to take an MCP Firmware Environment dump at this point in case you need to send problem materials to Unisys as described at the end of this section. 9–22 8222 3694–000
The topic “I/O Configuration” in Section 3 of this guide provides the mapping between physical HBA ports and information displayed by the ODT SC + command or entries displayed by Device Manager. This can be helpful in identifying which HBA ports should provide access to the device. It also describes how to disable and enable an HBA port Note: You perform the following procedure in the I/O engine environment. 1. Using Device Manager, open an HBA port that should provide access to the device and scan for hardware changes outboard of the HBA. Give this operation time to complete and see if the device is discovered. If the device is not discovered, continue with the remaining steps. While these remaining procedures are usually safe to perform during production use of the system, there is some risk that they might further destabilize the situation. If the missing device is not critical to your operation it is recommended that you defer these actions until a time when a system interruption, if necessary, causes the least impact. Also, be aware that these steps might take much longer to complete while the system is running a heavy I/O workload. 2. Use Emulex OCManager from the Operations Server to access the HBAs in the I/O engine environment. If the MCP is actively using tape devices outboard of the port, wait for these tape jobs to complete as the next step causes any active tape jobs to quit with an error. a. Use OCManager to reset the port. b. Refresh the OCManager display and check again whether the device is present outboard of the HBA port. End the OCManager program. 3. Restart Device Manager and see if the device is now visible. If not, use Device Manager again to scan for hardware changes outboard of the HBA. • If the device is now visible, skip the remainder of this section. • If the device is still not visible, then a system interruption is probably going to be required to recover the device, unless Unisys support or other resources are able to resolve the issue. 4. Use the MCP Console to halt the MCP. Be sure that OCManager and any other diagnostic utilities are not running. 5. Use Device Manager to disable and then re-enable the HBA port. Troubleshooting and Recovery Although not expected, this step might result in a message indicating that a system restart is necessary to complete the operation; ignore this message. Otherwise if the device is still not visible in Device Manager, try one last time to scan for hardware changes outboard of the HBA and see if the device becomes visible. If the preceding steps do not make the device visible in the environment, then the problem is probably external to the FS6200 Server and the storage and storage connections should be re-examined for problems. If no external problems (including bad cables) are found, restart the environment or restart the FS6200 Server. If the problem persists, contact Unisys support. 8222 3694–000 9–23
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 49 and 50:
Page 51 and 52:
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: 1. Create an unprivileged MCP userc
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?