FS6200 Server System Implementation Guide - Public Support ...

More documents

Recommendations

Info

Troubleshooting and Recovery If possible, use Remote Desktop to connect to the operating environment. Use the tools in the operating environment to shutdown the environment • If the previous action does not work, use the Platform Summary page in the Platform Console to shutdown (graceful stop) the environment. If after a few minutes the environment does not reach the Stopped state, use the Halt (forceful stop) command to stop the environment. • If the previous action does not work, use the platform management card to power-off or power-cycle the platform as desired. MCP Environment Failure Scenarios This subsection contains a list of problems that you might encounter during installation and configuration of the MCP Firmware. This information is used by customers and Unisys service representatives for solving system problems. System Startup Problems Some of the following conditions can cause system startup problems. Each of these is discussed in this section, along with possible causes and some corrective actions. • Network Services software Setup program does not complete • TCP/IP drive encounters connection problems • MCP Console has initialization problems • MCP does not initialize Network Services Software Setup Program Does Not Complete Review the following issues to determine why Network Services software setup does not complete: On a running system, use the MCP View from the MCP Console to verify that the Net object is in the “Running” state on the I/O engine where the Network Service firmware was installed. • If the NET status is Running, this indicates that the Network Service firmware manager is installed and is operating. In this is the case, go to the MCP Environment and query the network processor status by entering the NW NP command to ensure that the NPs are in the networking state. • If the NET object is not running or the network processors are not networking, reinstall the Network Service firmware. To verify that the network interface card (NIC) is functional, open an ODT session on the Operations Server and perform the following actions as necessary: 9–10 8222 3694–000
• If your TCP/IP or BNA connection is defined with the AUTOINIT attribute set to TRUE, issue the inquiry NW CONN . Verify that the CONNECTIONSTATUS = OPEN. • If your TCP/IP or BNA connection is defined with the AUTOINIT attribute set to FALSE, issue the establish call command NW EC BY CONNECTION to open the connection. Then, issue the inquiry NW CONN . Verify that the CONNECTIONSTATUS = OPEN. • If the connections have not opened, review the active PCD file through System Editor to ensure that the lines have been assigned the correct line numbers and the proper network processor. • If the assignments in the PCD are correct, verify the cabling and the network switches are working correctly. Finally, if all of the hardware appears to be correct, reinstall the Network Services firmware. Note: If it becomes necessary to reinstall the Network Services software, you must uninstall adapter devices before reinstalling the software. MCP Console Connection Error If the MCP Console interface starts before the NGAgent service is running, you might encounter a connection error. This error message often appears if the MCP Console interface is placed in the Startup group. If you encounter this error message, wait a few minutes and restart the MCP Console or select the Connect command from the File menu of the MCP Console. MCP Console Component View — Disconnected Components If a component on the MCP Console Component View is displayed with a blue question mark icon and a contact state of Disconnected, this indicates a problem establishing a network connection to the component. Follow these troubleshooting steps to diagnose the root cause of the problem: 1. Verify the component is running and has a working network connection. 2. Right-click on the disconnected component and select Launch. Troubleshooting and Recovery Note: The specific type of launch operation varies by component. For example, it might be to launch a Remote Desktop session or launch the BMC web interface. If the launched interface cannot connect to the component, this likely indicates the component is either not running or not properly configured on the network. 3. Verify the Systems Management account password on the component. If the component is running and active on the network, it is possible the connection is failing due to invalid credentials. This can be resolved by following the instructions in the topic “Synchronizing the System Account Password on a Component” of the MCP Console Help. 8222 3694–000 9–11
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: Workaround Use the platform managem
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?