FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Troubleshooting and Recovery Only FS6200 Server-specific ePortal troubleshooting problems are listed here. To see the general ePortal troubleshooting problems, refer to the ClearPath ePortal Business Implementation and Operations Guide . Cannot Access the ePortal Manager Website • Check the management LAN network cable connection • Check the Manager website IP address • Verify that you can communicate with the ePortal Manager environment by using the PING command: ping Personality Modules not in Ready/Unassigned state If a personality module state remains in either “Booting” or “Not Responding for some time, the controller is not able to communicate with a personality module. In this case, first restart the ePortal Manager environment from the Platform Console first to see if the problem goes away. If the problem persists after restarting the ePortal Manager environment, restart the affected ePortal PM environment from the Platform Console. To find out the correct ePortal PM environment name, display the detailed PM page of the affected PM by clicking the affected PM name from the ePortal Manager website, then use the Partition Number field to identify the correct ePortal PM environment name. For example, if the Partition Number field is 3, then you need to restart the ePortal PM 3 Environment from the Platform Console. Recovering ePortal Environment Failure If any of the ePortal environments fail, contact Unisys support to recover the failed environment. If the failed environment is the ePortal Manager environment, restore from the latest ePortal system backup after the ePortal Manager environment is recovered. “NXSERVICES: Attached EPO IP address = 192.168.223.254” Message Appears Once a Minute in MCP Console When ePortal Manager starts, ePortal Manager maps to the APPLIANCES share of the MCP using the MCP usercode and password configured in the ePortal Manager environment to determine the ePortal licensing and other ePortal configuration information. If ePortal Manager cannot map to the APPLIANCES share, this message is displayed. To avoid this problem, perform the following steps for the active ePortal System: 9–20 8222 3694–000
1. Create an unprivileged MCP usercode with the GROUPCODE attribute of EPORTALCONTROLLER. Refer to the topic “Creating a Usercode with the GROUPCODE Attribute EPORTALCONTROLLER” in Section 5 of this guide under subsection “Configuring ePortal Specialty Engine.” 2. From the MCP Console, start the ePortal Manager. Refer to “Starting ePortal Manager” in Section 5 of this guide for details. 3. From the ePortal Manager website, click Back-End Servers, the primary back-end server name, Change Usercode/Password, and then enter the correct MCP usercode and password. 4. Click Apply to update the MCP usercode and password information in ePortal Manager environment. For a FS6200 Server, you have to repeat the above steps for the standby ePortal system. Gathering Diagnostic Information Perform the following steps to collect ePortal diagnostics information: 1. Start ePortal Manager. 2. From the Management menu on the left side of the page, click Controller. The Controller page is displayed. 3. Under the Operations section, click Gather Diagnostics. The Gather Diagnostics Information page is displayed. 4. Click Generate Diagnostic File. Troubleshooting and Recovery ePortal Manager gathers diagnostics from the controller and every personality module that responds, and then creates a compressed zip file. When the gather diagnostics operation completes, the zip file appears in the Diagnostics Files list. 5. To download the diagnostics zip file, click the link for the file in the Size column and then save the file to your Service Processor hard drive. Troubleshooting Fibre Channel I/O Problems This subsection contains procedures for resolving certain types of I/O problems. Additional information on resolving I/O configuration problems can be found in the ClearPath Enterprise Servers External Disk and Tape Storage Systems Configuration Guide . If the MCP is unable to access certain I/O devices or use certain I/O paths, there are a number of actions you can take to diagnose and attempt to correct the problem. These issues are frequently external to the FS6200 Server and the Fibre Channel switches and storage systems should be checked for problems. While these actions are intended for customer use, you can also contact Unisys support for assistance. 8222 3694–000 9–21
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: Gathering Diagnostic Information Th
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?