FS6200 Server System Implementation Guide - Public Support ...

ClearPathFS6200Server 

SystemImplementationGuide 

FS6200 Server 1.0 

October 2012 8222 3694–000 

unisys

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information 

described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to 

purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the 

products described in this document are set forth in such agreement. Unisys cannot accept any financial or other 

responsibility that may be the result of your use of the information in this document or software material, including 

direct, special, or consequential damages. 

You should be very careful to ensure that the use of this information and/or software material complies with the laws, 

rules, and regulations of the jurisdictions with respect to which it is used. 

The information contained herein is subject to change without notice. Revisions may be issued to advise of such 

changes and/or additions. 

Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed at 

private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard 

commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data 

rights clauses. 

Unisys is a registered trademark of Unisys Corporation in the United States and other countries. 

All other brands and products referenced in this document are acknowledged to be the trademarks or registered 

trademarks of their respective holders.

Contents 

Section 1. Introduction 

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1 

Documentation Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2 

Section 2. System Overview 

Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1 

Platform Hardware Components . . . . . . . . . . . . . . . . . . . 2–2 

Secure Access Device . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3 

Management LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3 

Software Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3 

MCP Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4 

s-Par . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5 

Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5 

JProcessor Specialty Engine . . . . . . . . . . . . . . . . . . . . . . 2–6 

ePortal Specialty Engine . . . . . . . . . . . . . . . . . . . . . . . . . 2–7 

Systems Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7 

Operator Display Terminal (ODT) . . . . . . . . . . . . . . . . . . . 2–7 

MCP Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7 

Platform Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8 

Platform Management Card . . . . . . . . . . . . . . . . . . . . . . 2–8 

Management Card Virtual Console. . . . . . . . . . . . . . . . . . 2–8 

ePortal Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8 

Section 3. Customizing the Server Configuration 

Configuring I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1 

Configuring Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1 

Reconfiguring VSS Disks. . . . . . . . . . . . . . . . . . . . . . . . . 3–2 

Determining Correspondence between MCP Storage 

Channels and Firmware Environment Storage 

Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3 

Hot Reuse of Fibre Channel in a Channel Group is Not 

Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6 

Attaching Additional Fibre Channel Cables . . . . . . . . . . . . 3–7 

Enabling Fibre Channel Ports. . . . . . . . . . . . . . . . . . . . . . 3–7 

Disabling Fibre Channel Ports . . . . . . . . . . . . . . . . . . . . . 3–8 

8222 3694–000 iii

Contents 

Configuring the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–9 

Default Networking Configuration . . . . . . . . . . . . . . . . . 3–10 

Using Tools Associated with Network Services. . . . . . . . 3–13 

Gathering Values for Configuration. . . . . . . . . . . . . . . . . 3–14 

Supporting MCP Network Adapters . . . . . . . . . . . . . . . . 3–15 

Preparing to use Adapter Teaming and IEEE 802.1Q 

Virtual LANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16 

Preparing to Use Jumbo Frames . . . . . . . . . . . . . . . . . . 3–17 

Using the System Editor to Configure MCP 

Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–19 

Sample ADAPTERS.TXT File . . . . . . . . . . . . . . . . . . . . . 3–22 

Updating the MCP View of the Network. . . . . . . . . . . . . 3–22 

Using Sample CNS and TCP/IP Initialization Files . . . . . . 3–30 

Using Sample BNA Initialization Files . . . . . . . . . . . . . . . 3–31 

Changing the Administrator User Name and Password . . . . . . . . . . 3–31 

Changing the Default Systems Management Account Password . . . 3–32 

Configuring the MCP Environment. . . . . . . . . . . . . . . . . . . . . . . . . 3–32 

Configuring Call Home Services. . . . . . . . . . . . . . . . . . . . . . . . . . . 3–33 

Configuring the Operations Server . . . . . . . . . . . . . . . . . . . . . . . . . 3–33 

Configuring the Open Management Interface (OMI) . . . . . . . . . . . . 3–33 

Section 4. Operating the Server 

Managing Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1 

Viewing Platform Hardware Power Status . . . . . . . . . . . . 4–1 

Powering On the Platform Hardware . . . . . . . . . . . . . . . . 4–1 

Monitoring the Platform Boot Progress . . . . . . . . . . . . . . 4–1 

Shutting Down the Platform . . . . . . . . . . . . . . . . . . . . . . 4–2 

Powering Off the Platform Hardware . . . . . . . . . . . . . . . . 4–3 

Restarting the Platform after a Shutdown. . . . . . . . . . . . . 4–3 

Platform Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3 

General Environment Operational Tasks . . . . . . . . . . . . . . . . . . . . . . 4–4 

Viewing the Status of an Environment . . . . . . . . . . . . . . . 4–4 

Shutting Down an Environment . . . . . . . . . . . . . . . . . . . . 4–4 

Restarting an Environment . . . . . . . . . . . . . . . . . . . . . . . 4–4 

MCP Environment Operational Considerations . . . . . . . . . . . . . . . . . 4–4 

Controlling the MCP Environment . . . . . . . . . . . . . . . . . . 4–5 

MCP Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5 

Environment Secured Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 4–5 

MCP Firmware Environment Policy . . . . . . . . . . . . . . . . . . . . . . . . . 4–6 

Policy Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6 

Firewall Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7 

Network Authentication. . . . . . . . . . . . . . . . . . . . . . . . . 4–11 

Audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12 

iv 8222 3694–000

MCP Firmware Environment Policy Utility Scripts . . . . . . 4–12 

Enabling MCP PING Commands through the EVLAN Connection. . . 4–19 

Synchronizing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20 

Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20 

Differences from Previous MCP Systems. . . . . . . . . . . . 4–21 

Configuring MCP Networking . . . . . . . . . . . . . . . . . . . . 4–21 

Initializing Network Services . . . . . . . . . . . . . . . . . . . . . 4–21 

Verifying Network Services Installation and 

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22 

MCP Operations Interface Summary . . . . . . . . . . . . . . . 4–23 

Networking Commands and Inquiries. . . . . . . . . . . . . . . 4–25 

System Commands and Inquiries. . . . . . . . . . . . . . . . . . 4–27 

Call Home Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–27 

Using Maintenance Mode . . . . . . . . . . . . . . . . . . . . . . . 4–28 

Testing E-mail Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28 

Testing E-mail Heartbeats . . . . . . . . . . . . . . . . . . . . . . . 4–28 

I/O Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28 

I/O Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29 

Performing Dynamic PCD Updates . . . . . . . . . . . . . . . . 4–29 

Power Cycling or Disconnecting Fibre Channel I/O 

Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30 

Enabling MCP PING Commands through the Intra-Platform 

Connection for JProcessors. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30 

Section 5. Setting Up and Operating the ePortal Specialty Engine 

Contents 

Configuring ePortal Specialty Engine . . . . . . . . . . . . . . . . . . . . . . . . 5–1 

Collecting MCP Information. . . . . . . . . . . . . . . . . . . . . . . 5–1 

Creating MCP Usercodes . . . . . . . . . . . . . . . . . . . . . . . . 5–1 

Ensuring That the Necessary Disk Space Is Available . . . . 5–3 

Relocating the MCP APPLIANCES Share . . . . . . . . . . . . . 5–3 

Installing ePortal Interim Corrections (ICs) . . . . . . . . . . . . 5–3 

Configuring MCP Network Connection. . . . . . . . . . . . . . . 5–3 

Verifying the ClearPath ePortal Port That Custom 

Connect Facility (CCF) Automatically Creates . . . . . . . . 5–5 

Configuring Separate CCF Ports for Different 

Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5 

Validating the Connector Protocol-Specific Handler 

(Connector PSH) Installation and Configuration . . . . . . . 5–6 

Configuring a Named Pipe. . . . . . . . . . . . . . . . . . . . . . . . 5–7 

Configuring the MCP EMAIL Utility . . . . . . . . . . . . . . . . . 5–7 

Performing Initial Configuration Tasks in ePortal 

Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7 

Setting Up an Optional External ePortal Enterprise 

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9 

8222 3694–000 v

Contents 

ePortal Specialty Engine Operational Considerations . . . . . . . . . . . . 5–10 

Starting ePortal Manager. . . . . . . . . . . . . . . . . . . . . . . . 5–10 

ePortal Personality Module Naming . . . . . . . . . . . . . . . . 5–11 

Developing an ePortal Application . . . . . . . . . . . . . . . . . 5–11 

ePortal Specialty Engine Operational Considerations 

for a System with Two ISMs . . . . . . . . . . . . . . . . . . . 5–11 

ISM-0 ePortal to ISM-1 ePortal Failover Transition . . . . . . 5–12 

Assigning ePortal Specialty Engine ISM-0 as a Standby 

ePortal System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15 

ISM-1 ePortal to ISM-0 ePortal Failover Transition . . . . . . 5–16 

Assigning ePortal Specialty Engine ISM-1 as a Standby 

ePortal System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–18 

Restoring ePortal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–19 

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20 

Section 6. Setting Up and Operating the JProcessor Specialty Engine 

Configuring JProcessor Specialty Engine . . . . . . . . . . . . . . . . . . . . . 6–1 

JProcessor Specialty Engine Operational Considerations. . . . . . . . . . 6–1 

JProcessor Secured Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1 

Understanding the JProcessor Security Policy . . . . . . . . . . . . . . . . . 6–2 

Applying the JProcessor Security Policy for Services. . . . . 6–2 

Applying JProcessor Security Policy Settings for 

Firewall Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4 

Applying JProcessor Security Policy Settings for 

Network Authentication . . . . . . . . . . . . . . . . . . . . . . . 6–5 

Applying JProcessor Security Policy Settings for Audits . . 6–5 

Changing IP Address Scope for JProcessor 

MCPConnect Firewall Rules . . . . . . . . . . . . . . . . . . . . 6–6 

Section 7. Backing Up MCP Firmware Configuration Data 

Section 8. Updates 

Performing the System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1 

Using Interim Correction (IC) Update Files . . . . . . . . . . . . . . . . . . . . 8–1 

Accessing and Downloading Updates . . . . . . . . . . . . . . . . . . . . . . . 8–1 

Updating Firmware using the Master Installation Manager Update 

Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2 

Updating MCP Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–3 

Driver and PCI Card BIOS/Firmware Updates . . . . . . . . . . . . . . . . . . 8–3 

Updating Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–3 

Removing Network Services . . . . . . . . . . . . . . . . . . . . . . 8–4 

Reinstalling Network Services . . . . . . . . . . . . . . . . . . . . . 8–4 

vi 8222 3694–000

Updating Specialty Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4 

Updating JProcessor Firmware . . . . . . . . . . . . . . . . . . . . 8–4 

Updating JProcessor Firmware Operating Environment . . 8–4 

Installing ePortal IC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4 

Updating Environment Operating System Software . . . . . . . . . . . . . 8–6 

Section 9. Troubleshooting and Recovery 

Contents 

Submitting Trouble Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1 

Accessing the Unisys Product Support Web Site . . . . . . . . . . . . . . . 9–3 

Using Remote Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–3 

Using Call Home. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–3 

Monitoring the Call Home Event E-mails . . . . . . . . . . . . . . . . . . . . . 9–3 

Using Maintenance Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4 

Problems with Call Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4 

Restarting an Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4 

Diagnostic Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4 

Taking a Platform Environment Dump . . . . . . . . . . . . . . . 9–4 

Taking a Platform Firmware Livedump . . . . . . . . . . . . . . . 9–5 

Taking an MCP Environment Dump . . . . . . . . . . . . . . . . . 9–5 

Taking an MCP Firmware Environment Dump. . . . . . . . . . 9–5 

Transferring Diagnostic Data to Unisys Product 

Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–6 

Platform Hardware Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . . 9–6 

Operations Server Failure Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . 9–8 

s-Par Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–8 

MCP Environment Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . 9–10 

System Startup Problems . . . . . . . . . . . . . . . . . . . . . . . 9–10 

Problems Mapping to a Client Access Services Share . . . 9–12 

Fatal System Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12 

Network Services Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . . 9–12 

Initiating a Dump. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12 

JProcessor Specialty Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–16 

ePortal Specialty Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–19 

Troubleshooting Fibre Channel I/O Problems . . . . . . . . . . . . . . . . . 9–21 

Recovery Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–24 

Recovering FS6200 Server Configuration Data . . . . . . . . 9–24 

Powering Down a Cell to Replace Failed Hardware . . . . . 9–25 

Powering Up a Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–26 

Power-Cycling a Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–26 

Restarting Platform Services . . . . . . . . . . . . . . . . . . . . . 9–27 

Restarting an ISM Environment . . . . . . . . . . . . . . . . . . . 9–27 

Reinstalling the Entire Platform . . . . . . . . . . . . . . . . . . . 9–27 

8222 3694–000 vii

Contents 

Appendix A. Building Network Initialization Files 

Preconfigured CNS and TCP/IP Initialization Files . . . . . . . . . . . . . . . A–1 

CNS and TCP/IP Initialization Files . . . . . . . . . . . . . . . . . . A–1 

Guidelines for Building CNS Initialization Files . . . . . . . . . A–1 

Guidelines for Building TCP/IP Initialization Files . . . . . . . . A–2 

Preconfigured SNMP Initialization File . . . . . . . . . . . . . . . . . . . . . . . A–4 

SNMP Initialization File . . . . . . . . . . . . . . . . . . . . . . . . . . A–4 

Guidelines for Building BNA Initialization Files . . . . . . . . . . . . . . . . . A–6 

Using NAU Network Version Dump Files . . . . . . . . . . . . . . . . . . . . . A–7 

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 

viii 8222 3694–000

Figures 

2–1. FS6200 Server Hardware Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2 

8222 3694–000 ix

Figures 

x 8222 3694–000

Tables 

3–1. Physical Location of HBA Ports to entries in Device Manager or Channels 

listed by the SC+ ODT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4 

3–2. Default NP Instance Numbers for Each I/O Engine . . . . . . . . . . . . . . . . . . . . 3–10 

3–3. Default Network Processor Values for External Connections on FS6200 

Server I/O Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10 

3–4. Default IP Address Values for MCP on the FS6200 Server for each I/O 

Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–11 

3–5. Default Networking Values on the FS6200 Server IOE-1 . . . . . . . . . . . . . . . 3–11 

3–6. Default Networking Values on the FS6200 Server IOE-2 . . . . . . . . . . . . . . . 3–12 

3–7. MCP Networking Values Configuration Worksheet for FS6200 Server . . . . . . 3–23 

3–8. MCP Networking Values for FS6200 Servers IOE-1 . . . . . . . . . . . . . . . . . . . 3–23 

3–9. MCP Networking Values for FS6200 Servers IOE-2 . . . . . . . . . . . . . . . . . . . 3–27 

4–1. Unisys-Defined Firewall Rules for MCP Functions . . . . . . . . . . . . . . . . . . . . . 4–8 

4–2. Firewall Rules for JProcessor Specialty Engine Environments . . . . . . . . . . . . 4–11 

4–3. MCP Firmware Environment Policy Audit Policy Settings. . . . . . . . . . . . . . . 4–12 

6–1. Unisys-Defined JProcessor Firewall Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4 

6–2. Audit Policy Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5 

8222 3694–000 xi

Tables 

xii 8222 3694–000

Section 1 

Introduction 

About This Guide 

Audience 

When the FS6200 Server arrived at your site, your Unisys service representative 

performed the initial installation and some configuration of the system. Some system 

components have also been installed or set up at the factory. This guide explains how to 

configure and operate your FS6200 Server software, install and use optional software 

products, and customize the software configuration in the FS6200 Server. This guide also 

describes operational and maintenance tasks for your FS6200 Server. 

The audience for this document includes 

• ClearPath system administrators 

• ClearPath network administrators 

• ClearPath system operators 

• Unisys service representatives 

Media and Books 

The following media and documentation are required or referenced in this document. 

MCP Release Software and Media 

• ClearPath MCP Release Software CD-ROM 

• Interim Corrections (ICs) are available at 

http://www.support.unisys.com/ 

• Keys media 

• Supplemental Software Release 

FS6200 Server Documents 

The following documents are available from the Unisys Product Support website, at 

www.support.unisys.com 

8222 3694–000 1–1

Introduction 

• FS6200 Server System Overview 

• FS6200 Server System Planning Guide 

• ClearPath Enterprise Servers Server External Disk and Tape Storage Systems 

Configuration Guide 

• MCP Console Help 

• System Complex Definition (SCD) Editor Help 

ClearPath MCP 14.0 Documents 

The following ClearPath MCP 14.0 documents are available from the Unisys Product 

Support website. 

• ClearPath Virtual Machine for the Java 7.0 Platform on ClearPath MCP Installation 

and Administration Guide 

• ClearPath Virtual Machine for the Java 7.0 Platform on ClearPath MCP Programming 

Guide 

ClearPath ePortal Documents 

The following ClearPath ePortal documents are available from the Unisys Product Support 

website. 

• ClearPath ePortal Manager Help 

• ClearPath ePortal Business Implementation and Operations Guide 

• ClearPath ePortal Enterprise Managed Platform Implementation and Operations Guide 

Documentation Updates 

This document contains all the information that was available at the time of publication. 

Changes identified after release of this document are included in problem list entry (PLE) 

18894564. To obtain a copy of the PLE, contact your Unisys service representative or 

access the current PLE from the Unisys Product Support website: 

http://www.support.unisys.com/all/ple/18894564 

Note: If you are not logged into the Unisys Product Support website, you will be asked to 

do so. 

1–2 8222 3694–000

Section 2 

System Overview 

This section provides an overview of the FS6200 Server including 

• Hardware 

• Software 

• Systems Management 

This overview also introduces and defines terminology that is used throughout this guide. 

For a more detailed overview of the FS6200 Server, including its capabilities, supported 

system and application hardware, and the services provided to support server operation, 

refer to the ClearPath FS6200 Server System Overview. 

Hardware Overview 

This subsection provides an overview of the FS6200 Server hardware environment and its 

components. The FS6200 Server hardware environment consists of 

• Platform hardware components 

- Processor and Memory Module (PMM) 

- I/O and Specialty Engine Module (ISM) 

- Operations Server (OPS) 

• Secure Access Device 

• Management LAN 

Figure 2-1 illustrates the configuration of the FS6200 Server hardware environment. 

8222 3694–000 2–1


Figure 2–1. FS6200 Server Hardware Environment 

Platform Hardware Components 

The platform hardware components are the major hardware components of the FS6200 

Server. Most of the software, including the Unisys Secure Partitioning (s-Par ® ), MCP 

Environment, and the specialty engine environments, run on specific platform hardware 

components. 

The FS6200 Server is a highly redundant and resilient system consisting of multiple 

physical components including 

2–2 8222 3694–000

• Two Processor Memory and Modules (PMMs) 

The PMM contains E-mode memory, E-mode processors also known as Central 

Processing Modules (CPMs), and one instance of the MCP. One PMM is currently 

active. 

• Two I/O and Specialty Engine Modules (ISMs) 

The ISM is where the I/O engine, JProcessor Specialty Engine, and ePortal Specialty 

Engine reside. There are two ISMs active at all times in the FS6200 Server executing 

operations in parallel. The dual ISM configuration supports MCP continuous operation 

without a halt/load or customer application interruption. All MCP peripheral subsystem 

storage is connected to the system through the host bus adaptors in the 

ISMs. 

The I/O engine is responsible for storage I/O, networking, and encryption operations. 

s-Par resides within each ISM and subdivides the ISM so that the I/O engine is a guest 

environment within an ISM, as well as also having separate environments for each of 

the specialty engines. All of the PCIe slots in an ISM are assigned to the I/O engine. 

The I/O engine controls communication between the specialty engines and the MCP 

utilizing an s-Par virtual LAN. 

• Two Operations Servers 

The Operations Server is a cell that hosts the systems management engine, the 

environment where the MCP Firmware systems management software runs. The 

systems management engine monitors, manages, and controls the other processing 

engines on the server. One Operations Server is currently active to manage the server. 

Secure Access Device 

The secure access device controls the internal management LAN and provides security for 

a cell when accessed from the Operations Server. In addition, the secure access device 

has a WAN port that provides secure remote access to the devices on the management 

LAN. 

Management LAN 

The internal management LAN is used by an Operations Server to access the PMM and 

the ISM for systems management. Access to the management LAN is controlled by the 

secure access device. 

Software Overview 

This subsection provides an overview of FS6200 Server software. Major software 

components include: 

• MCP Environment 

• s-Par 

• Network Services 

• JProcessor Specialty Engine 


8222 3694–000 2–3


• ePortal Specialty Engine 

MCP Environment 

The MCP Environment is the core environment provided on the system where the MCP 

Operating System, MCP system software, and MCP applications run. The ClearPath MCP 

release software package is installed in this environment. 

The MCP Environment consists of multiple hardware platforms and is provided by a 

package of Unisys software called MCP Firmware. MCP Firmware provides the following 

services in support of the MCP Environment: 

• E-mode Services 

• I/O Services 

• Network Services 

• MCP Console 

E-mode Services 

I/O Services 

E-mode services represents the portion of the Unisys MCP Firmware that provides runtime 

code execution support for the MCP Operating System, MCP System Software, and 

MCP applications. These services run on the E-mode engine that is located on the PMM 

server. 

I/O services represent the portion of the MCP Firmware that supports MCP I/O to the 

following types of devices: 

• Disk and disk storage systems 

• Tape and tape libraries 

• Virtual tapes 

• Operator Display Terminals (ODTs) 

• DVD-RW drives 

I/O services are also responsible for the discovery and management of devices, and 

performing I/O operations. 

The following table lists the components of I/O services. 

Component Description 

I/O processor (IOP) Performs I/O operations on behalf of the MCP 

I/O processor Manager Starts, stops, and restarts the I/O processor 

2–4 8222 3694–000

MCP Console 

s-Par 

Component Description 

NGM I/O Service Discovers I/O devices 

NGM Disk Filter driver that controls I/O to Virtual Sector 

Size (VSS) disks 

NGM Tape Class driver that controls I/O to MCP tapes 

VSS Tab Plug In Adds a VSS disk tab in Device Manager and 

Disk Manager 

I/O processor Control Interfaces between I/O services and the 

System Editor of the MCP Console 

I/O services on the FS6200 Server also provides new I/O functionality that is not available 

on previous MCP systems. It supports Plug-and-Play enabling you to add new channels, 

taps, and disks to the MCP without a halt/load. It also supports multiple active I/Os to 

individual Virtual Sector Size (VSS) disks sometimes enabling the system to achieve higher 

I/O rates with lower numbers of disks/LUNs. This service runs on the I/O engine that is 

located on the ISM cell. 

The MCP Console is systems management software you use to perform configuration and 

operational tasks on the MCP Environment. It is contained in the MCP Firmware and runs 

as part of the MCP Environment. The MCP Console runs on the systems management 

engine that is located on the Operations Server. 

s-Par is software that provides the capability to run multiple operating environments 

concurrently—for example, multiple specialty engine operating environments. Each 

operating environment has dedicated hardware resources—processors, memory, and 

input/output—that isolate one operating environment from another and ensure that a 

failure of one specialty engine does not affect any other. 

Network Services 


Network Services provides a set of software services that make the network interfaces of 

the I/O engine available to the MCP Environment. These include 

• A local Enhanced Virtual LAN (EVLAN) network connection between the MCP 

Environment and the I/O engine. Communication across the EVLAN is through the 

TCP/IP protocol. EVLAN supports the Call Home platform service developed by 

Unisys. The EVLAN connection is not used by customer applications. 

• MCP network adapter services which enable TCP/IP and Heritage Network Services 

(BNA) network providers in the MCP Environment to establish network connections 

through NIC adapters of the underlying I/O engine. 

8222 3694–000 2–5


These services run on the I/O engine which is located on the ISM cell. 

Network Processors 

The FS6200 Server supports up to six Network Processors of type VNP per I/O engine. 

• The FS6200 Server is preconfigured with at least two NPs. 

• The first NP is reserved for the EVLAN connection and the intra-platform connections 

to the JProcessor Specialty Engines and the ePortal Specialty Engine. 

The EVLAN is an emulated network interface card providing a connection between the 

MCP Environment and the I/O engine. 

The intra-platform connections provide a connection between the MCP Environment 

and the specialty engine environments. 

• There is an additional VNP for each physical NIC in the system in the default 

configuration. The additional VNPs are assigned the adapter ports of the NICs in the 

PCI Express slots. 

This connection allows the MCP Environment to access a NIC within the I/O engine. 

The MCP network adapter supports BNA and TCP/IP transfers to and from the MCP 

Environment. 

• Each NP supports up to eight MCP network adapter connections. 

JProcessor Specialty Engine 

ISM-0 

ISM-1 

The JProcessor Specialty Engine provides Java Services to applications running in the 

MCP Environment. The JProcessor Specialty Engine is provided on the ISM. 

Each ISM consists of two JProcessor Specialty Engine environments as follows: 

• JProcessor 1 Environment 




The JProcessor Specialty Engine environments run independently and provide redundancy 

and load balancing for Java Services. 

Normal systems management of the JProcessor Specialty Engine environments is 

performed from the MCP Environment which is consistent with how JProcessor Specialty 

Engine appliances are managed on other MCP systems. 

2–6 8222 3694–000

ePortal Specialty Engine 

The ePortal Specialty Engine provides user interface modernization services for 

applications running in the MCP Environment. The ePortal Specialty Engine is provided on 

the ISM. 

Each ISM provides the ePortal Specialty Engine consisting of the following environments: 

• ePortal Manager Environment 

• ePortal Personality Module (PM) 1 Environment 




The ePortal Manager Environment is used to manage the other ePortal Personality Module 

environments. 

The FS6200 Server consists of two ISMs. The ePortal Specialty Engine running in ISM-0 is 

configured as an active ePortal and the ePortal Specialty Engine running in ISM-1 is 

configured as a standby ePortal which is used only when the ISM-0 fails or the ePortal 

Specialty Engine in ISM-0 fails. Refer to the section “ePortal Specialty Engine Operational 

Considerations for Systems with two ISMs” later in this guide for more information. 

Note: If an optional external ePortal Enterprise system is attached to the FS6200 Server, 

none of ePortal environments in the ISMs should be active. 

Systems Management 

The MCP Console is used to perform systems management tasks on the FS6200 Server. 

Shortcut icons are provided on the Operations Server desktop for the MCP Console and 

the ODT. 

Operator Display Terminal (ODT) 

MCP Console 


Normal MCP operations can be performed by accessing either of the two ODT desktop 

shortcut icons preconfigured on an Operations Server (ODT 1 or ODT 2). Double-clicking 

the icon launches Web Enabler software on the Operations Server to provide ODT-level 

access to the MCP Environment. Refer to the Web Enabler for ClearPath MCP 

Implementation Guide or more information. 

You manage the MCP Environment, including E-mode Services, I/O Services, Network 

Services, and Call Home Services using the MCP Console. The MCP Console is also used 

to start the Platform Console, BMC web interface, and ePortal Manager Browser. You 

access the MCP Console from the Operations Server or from a remote workstation. Refer 

to the MCP Console Help for more information. 

8222 3694–000 2–7


Platform Console 

You manage s-Par including platform and environment status, using the Platform Console. 

You access the Platform Console from the Operations Server. 

Platform Management Card 

You perform low-level management of server hardware components using the platform 

management card. You perform these management tasks from the Operations Server 

using the Baseboard Management Controller (BMC) Web interface. The BMC Web 

interface is the UI for the platform management card that you use to monitor the hardware 

components of the system. Each cell (OPS, ISM, and PMM) has a platform management 

card. 

Management Card Virtual Console 

Using the Virtual Console, you can display platform messages as the platform boots 

through the system BIOS and any BIOS on other hardware, and as s-Par boots and 

initializes. 

ePortal Manager 

To manage ePortal, you access the ePortal Manager website from the MCP Console. 


you access the ePortal Manager by double-clicking the ePortal Manager icon on the 

desktop of the Operations Server. 

2–8 8222 3694–000

Section 3 

Customizing the Server Configuration 

This section discusses issues you should consider for customizing the configuration of 

your FS6200 Server. You should perform these tasks after your service representative 

completes setting up the FS6200 Server. 

Configuring I/O 

This subsection provides topics you should consider when setting up your I/O 

configuration on the FS6200 Server. 

Configuring Storage 

The FS6200 Server supports Virtual Sector Size (VSS) disks on external storage. Logical 

disks are not supported on external storage. 

Storage systems with VSS disks, including active-active and active-passive disk storage 

systems, are fully supported by the FS6200 Server MCP. 

You access the OCManager installed in the systems management engine environment to 

display useful I/O subsystem information. However, you should not use it to adjust system 

settings unless directed by Unisys support. In particular, do not set persistent binding on 

the storage logical units (LUNs). 

The Fibre Channel Host Bus Adapters (HBAs) are available for your configuration. Refer to 

the Server External Disk and Tape Storage Systems Configuration Guide for details. 

There are four PCIe slots per ISM available that can be used for up to three HBAs or NICs 

in any combination. Each HBA has four Fibre Channel ports. Therefore, there are up to 24 

Fibre Channel ports which is the maximum number of ports. The Fibre Channel HBA ports 

can be used to access a disk storage system. Direct connect and fabric configurations are 

both supported. In the case of a fabric configuration, each HBA port can be given access to 

either one or two taps in the storage system. 

For a resilient storage system configuration, at least two HBA cards in separate ISMs must 

have paths that provide access to the storage system and these paths should make use of 

storage ports in at least two storage processors/directors within the storage system. In a 

fabric configuration, the best resiliency requires having those paths traverse two physically 

separate fabrics. An external halt/load unit with paths from each ISM should be configured 

for production use of the server. 

8222 3694–000 3–1


The FS6200 Server also supports up to eight active I/Os to individual VSS disks. This 

capability enables the FS6200 Server to potentially achieve improved I/O performance 

when dividing disk families into fewer members. The number of LUNs needed for 

satisfactory performance varies based on many factors, including the data access patterns 

of your applications. 

Refer to the ClearPath Enterprise Servers Server External Disk and Tape Storage Systems 

Configuration Guide for detailed storage configuration guidance that must be followed 

when configuring FS6200 Server disk and tape storage. 

You use the System Editor of the MCP Console to create a peripheral configuration 

diagram (PCD) that describes the FS6200 Server storage configuration. PCD creation is 

fully automated on the FS6200 Server. You only need to select those devices that the MCP 

is to use, optionally adjust the device numbers used to identify devices, and add 

comments about the devices. Comments placed into the PCD are visible in some of the 

MCP screen displays. 

Reconfiguring VSS Disks 

Some disks have formats other than the VSS formats supported by the MCP. For example, 

disks can have an MBR/GPT format (used by Windows and Linux) or disks can be 

unformatted. 

When adding LUNs to the FS6200 Server to be used as VSS disks, do not set persistent 

binding on the LUNs as is done for IOM systems using OCManager. 

To add a LUN to the PCD for use as an MCP VSS disk: 

1. If the disk is formatted as MBR/GPT, recreate or reinitialize the LUN using the storage 

system interface. 

2. Use the System Editor of the MCP Console to edit the active Peripheral Configuration 

Diagram (PCD) and assign the disk to the MCP. 

3. Commit the PCD change by setting it as the active PCD. 

4. Acquire the disk by the MCP. 

5. Use the INIT system command to format as VSS1 or VSS2. 

6. You might need to OK a warning message if the disk is in MBR/GPT format. 

To release a VSS disk to firmware use (not expected to be a frequent action) 

1. PG PK NOLABEL. 

2. Halt the MCP. 

3. Edit the active PCD and unmark the disk so it is not assigned to the MCP. 

4. Commit the updated PCD and start the MCP. 

5. Use Disk Manager to format the disk. 

3–2 8222 3694–000

Determining Correspondence between MCP Storage Channels 

and Firmware Environment Storage Controllers 

Use the information in this subsection to determine the correspondence between the 

physical HBA cards, storage controller ports in Device Manager, and channels in the MCP 

displays and the System Editor of the MCP Console. 

In the MCP Environment 

Start an ODT session on the Operations Server and use the SC+ command to display 

detailed I/O configuration. The HBA location information for each channel is displayed as 

shown in the following example: 

CHANNEL IOP 1 TYPE PCI POSITION 0,1,0 Emulex LPe12004-M8, PCI Slot 4, { 

The three numbers (0,1,0) that follow POSITION correspond to bus, device, and function 

in that order. The slot number is listed after the description of the HBA. 

In the I/O Engine Environment 

1. Connect to the I/O engine environment through the MCP Console. 

2. In Device Manager (accessed through Server Manager), right-click Device 

Manager, point to View and then click View Devices by Connection. 

3. In the right pane, expand ACPI x64-based PC, Microsoft ACPI-Compliant 

System, and then PCI Bus. 

The HBAs are listed and the slot in which an HBA is installed is indicated. 

To locate the slot, device, and port numbers right-click an HBA and then select 

Properties. The General tab in the Properties dialog box indicates the slot, 

device, and port. 

Example 

Location: PCI Slot 4 (PCI bus 0, device 1, function 0) 


For a Quad Port HBA in slot x, there are four entries listed with the same slot number. 

There are two pair of entries each of which share the same device number. For each 

pair that shares the same device number, one specifies function 0 and the other 

function 1. The pair with the smaller device number represents port 0 (function 0) and 

port 1 (function 1) of the HBA. The pair with the larger device number (typically one 

greater than the smaller), represents port 2 (function 0) and port 3 (function 1) of the 

HBA. 

4. Refer to Table 3-1 for the correspondences of the physical location of the cards to the 

HBA entries in Device Manager and the Channels displayed by the SC+ ODT 

command. 

8222 3694–000 3–3


Table 3–1. Physical Location of HBA Ports to entries in Device Manager 

or Channels listed by the SC+ ODT Command 

Physical Location 

Slot Port 

4 0 Storage controllers 

Device Manager MCP 

Emulex 

LPe12004-M8, PCI 

Slot 4,{ 

Location: PCI Slot 4 

(PCI bus 0, device k, 

function 0) 

1 Storage controllers 

Emulex 


Slot 4,{ 


(PCI bus 0, device k, 

function 1) 


Emulex 


Slot 4,{ 


(PCI bus 0, device 

k+1, function 0) 


Emulex 


Slot 4,{ 



k+1, function 1) 

CHANNEL IOP 1 

TYPE PCI POSITION 

0,k,0 

Emulex 


Slot 4, { 

CHANNEL IOP 1 


0,k,1 

Emulex 


Slot 4, { 

CHANNEL IOP 1 


0,k+1,0 

Emulex 


Slot 4, { 

CHANNEL IOP 1 


0,k+1,1 

Emulex 


Slot 4, { 

3–4 8222 3694–000


or Channels listed by the SC+ ODT Command (cont.) 


Slot Port 



Emulex 


Slot 5,{ 


(PCI bus 0, device m, 

function 0) 


Emulex 


Slot 5,{ 


(PCI bus 0, device m, 

function 1) 


Emulex 


Slot 5,{ 



m+1, function 0) 



Emulex 


Slot 5,{ 



m+1, function 1) 

CHANNEL IOP 1 


0,m,0 

Emulex 


Slot 5, { 

CHANNEL IOP 1 


0,m,1 

Emulex 


Slot 5, { 

CHANNEL IOP 1 


0,m+1,0 

Emulex 


Slot 5, { 

CHANNEL IOP 1 


0,m+1,1 

Emulex 


Slot 5, { 

8222 3694–000 3–5



or Channels listed by the SC+ ODT Command (cont.) 


Slot Port 



Emulex 


Slot 6,{ 


(PCI bus 0, device n, 

function 0) 


Emulex 


Slot 6,{ 


(PCI bus 0, device n, 

function 1) 


Emulex 


Slot 6,{ 



n+1, function 0) 


Emulex 


Slot 6,{ 



n+1, function 1) 

CHANNEL IOP 1 


0,n,0 

Emulex 


Slot 6, { 

CHANNEL IOP 1 


0,n,1 

Emulex 


Slot 6, { 

CHANNEL IOP 1 


0,n+1,0 

Emulex 


Slot 6, { 

CHANNEL IOP 1 


0,n+1,1 

Emulex 


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. 


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


PCI Slot X (PCI bus Y, device N function Z) 

For the HBA in Slot X there will be 4 entries listed with Location information as 

follows: 

PCI Slot X (PCI bus Y, device N function 0) 


PCI Slot X (PCI bus Y, device N+1 function 0) 


l. Match the recorded information for the unused HBA Ports to the location 

information as follows: 

Unused HBA Port Location Information from 

Properties 

Slot X, Port 0 PCI Slot X (PCI bus Y, device N function 0) 


Slot X, Port 2 PCI Slot X (PCI bus Y, device N+1 function 

0) 


1) 

m. If the device and function number in the Location information matches one of the 

unused HBA Ports recorded earlier, click the Driver tab, and then click Enable to 

enable the HBA Port. 

Continue through the list of HBA ports to match and enable the slot-port pairs that 

you recorded earlier. 

Disabling Fibre Channel Ports 

To disable 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 the 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. 

3–8 8222 3694–000

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. 

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: 

PCI Slot X (PCI bus Y, device N function Z) 

For the HBA in Slot X there will be 4 entries listed with Location information as 

follows: 





l. Match the recorded information for the unused HBA Ports to the location 

information as follows: 

Unused HBA Port Location Information from 

Properties 




0) 


1) 

m. If the device and function number in the Location information matches one of the 

unused HBA Ports recorded earlier, click the Driver tab, and then click Disable 

to disable the HBA Port. 

Continue through the list of HBA ports to match and disable the slot-port pairs that 

you recorded earlier. 

Configuring the Network 

When you initially receive your ClearPath MCP FS6200 Server, a default networking 

environment has been established using the following pre-configured initialization files: 

CLEARPATH/INIT/CNS 

CLEARPATH/INIT/TCPIP 


8222 3694–000 3–9


You might be able to use your FS6200 Server as delivered without modification to the 

default network configuration. However, you might want to integrate your FS6200 Server 

into your existing network. The following topics describe the general steps required to 

configure Network Services to operate within your network environment. 

Default Networking Configuration 

The following text describes the default networking configuration for your system. 

• The default host name of the MCP server for this environment is CPMCP1. 

• You use the System Editor of the MCP Console to assign NP numbers and Line IDs to 

the network interfaces within each I/O engine according to the following rules. 

- The intra-platform connections for a system are located on the initial NP defined 

for each I/O engine. 

- The Line ID assignments for the intra-platform connections are pre-assigned and 

cannot be modified. 

Table 3-2 lists the default NP instance numbers for each I/O engine. 

Table 3–2. Default NP Instance Numbers for Each I/O Engine 

IOE-1 IOE-2 

210 220 

The NP instance and Line ID number assignments for the I/O engine for external 

connections are based on the adapter Slot#/Port# of the device. 

The following equation is used to define the expected network processor instance 

numbers for the I/O engine. 

network processor instance number = (200 + 10 x IOP number + (slot number % 10)) 

The default Line ID value equals the port number of the device. In this case, the following 

table lists the NP numbers assigned by the System Editor (assuming slot values of 1 

through 10). 

Table 3–3. Default Network Processor Values for External Connections on 

FS6200 Server I/O Engines 

PCI Slot Number IOE-1 IOE-2 

1 211 221 

4 214 224 

5 215 225 

3–10 8222 3694–000

The default IP address for the intra-platform connections on each I/O engine are listed in 

the following table. There can be more than one MCP IP address for ePortal that is active 

at a time, whether local or remote. 

Note: Refer to the JProcessor Specialty Engine and ePortal Specialty Engine topics in 

this guide for more details. 

Table 3–4. Default IP Address Values for MCP on the FS6200 Server for 

each I/O Engine 

IOE 

Entity 

Name MCP IP Address IP Address Mask 

Line 

Number 

IOE and Specialty 

Engine IP Address 

1 EVLAN 192.168.16.5 255.255.255.252 0 192.168.16.6 

1 JProc1 192.168.16.141 255.255.255.252 1 192.168.16.142 

1 JProc3 192.168.16.149 255.255.255.252 2 192.168.16.150 

1 ePortal 192.168.223.250 255.255.255.0 3 

2 EVLAN 192.168.16.9 255.255.255.252 0 192.168.16.10 

2 JProc2 192.168.16.145 255.255.255.252 1 192.168.16.146 

2 JProc4 192.168.16.153 255.255.255.252 2 192.168.16.154 

2 ePortal 192.168.224.250 255.255.255.0 3 

The following tables provide a summary of the standard configuration for each I/O engine. 

Table 3–5. Default Networking Values on the FS6200 Server IOE-1 

PCI Slot Network Port NP Number Line ID IP Address 

Internal 

(management 

LAN) 

Internal 

(reserved) 

Internal (ePortal 

external 

connection) 


external 

connection) 

1 (Left) Unassigned Not applicable 

2 Unassigned Not applicable 

3 Unassigned Unassigned, Not 

applicable 


None EVLAN 210 0 192.168.16.5 

None Internal path to 

JProcessor 1 


210 1 192.168.16.141 

8222 3694–000 3–11


Table 3–5. Default Networking Values on the FS6200 Server IOE-1 (cont.) 



JProcessor 3 


ePortal 

210 2 192.168.16.149 

210 3 192.168.223.250 

1 First (Left) 211 1 192.168.237.50 

1 Second 211 2 192.168.237.51 

1 Third (Copper 

Only) 

1 Fourth (Right, 

Copper) 

211 3 192.168.237.52 

211 4 192.168.237.53 

4 First (Right) 214 1 192.168.237.54 

4 Second 214 2 192.168.237.55 


only) 

4 Fourth (Left, 

Copper) 

And/Or 

214 3 192.168.237.56 

214 4 192.168.237.57 

5 First (Right) 215 1 192.168.237.58 

5 Second 215 2 192.168.237.59 


only) 


Copper) 

215 3 192.168.237.60 

215 4 192.168.237.61 

Table 3–6. Default Networking Values on the FS6200 Server IOE-2 


Internal 

(management 

LAN) 

Internal 

(reserved) 


external 

connection) 

1 (Left) Unassigned Not applicable 


3 Unassigned Unassigned, Not 

applicable 

3–12 8222 3694–000

Table 3–6. Default Networking Values on the FS6200 Server IOE-2 (cont.) 



external 

connection) 


None EVLAN 220 0 192.168.16.9 


JProcessor 2 


JProcessor 4 


ePortal 

220 1 192.168.16.145 

220 2 192.168.16.153 

220 3 192.168.224.250 

1 First (Left) 221 1 192.168.237.62 

1 Second 221 2 192.168.237.63 


Only) 

1 Fourth (Right, 

Copper) 

221 3 192.168.237.64 

221 4 192.168.237.65 

4 First (Right) 224 1 192.168.237.66 

4 Second 224 2 192.168.237.67 


only) 


Copper) 

And/Or 

224 3 192.168.237.68 

224 4 192.168.237.69 

5 First (Top) 225 1 192.168.237.70 

5 Second 225 2 192.168.237.71 


only) 

5 Fourth (Bottom, 

Copper) 

Using Tools Associated with Network Services 


225 3 192.168.237.72 

225 4 192.168.237.73 

Several tools are used in the installation and operation of Network Services. The ClearPath 

network administrator installs and configures Network Services using the following tools 

in the systems management engine, MCP Console, and the MCP Environment. 

8222 3694–000 3–13


In the Systems Management Engine 

The following tools are used in the systems management engine: 

• The installation package for installing the FS6200 Server system complex through the 

Master Installation Manager (MIM-Based) utility. 

• The Network Services Setup program (used for updates) 

In the MCP Console 

The following tools are used in the MCP Console: 

• The System Editor 

• Network Services diagnostics 

• Selective diagnostics types 

• Mechanisms for initiating the diagnostic handling 

• Diagnostics displays that identify diagnostics type, provide a summary, and show 

status of each requested component diagnostic 

MCP Environment 

The following tools are used in the MCP Environment: 

• The Simple Installation program which supports installation of the network providers 

and supporting utilities 

• The Network Administrative Utility (NAU) or a file editing program such as CANDE. 

Generally, you use only one of these methods to configure TCP/IP and EVLAN 

connections. 

- Use the NAU to create new (or edit existing) CNS, TCP/IP, and BNA (optional) 

initialization files for this ClearPath server complex. These files define all TCP/IP, 

Network Services EVLAN, and Network Services MCP network adapter 

connections. Most often, you use NAU in installations that include Heritage 

Network Services (BNA) since it can ensure that the BNA initialization files are 

consistent on all of the ClearPath MCP hosts in your network. 

- Use an editor such as CANDE to make necessary modifications to sample CNS 

and TCP/IP initialization files that are provided with the ClearPath server. Refer to 

Appendix A “Building Network Initialization Files” of this guide for a description of 

these sample initialization files. 

Gathering Values for Configuration 

This topic discusses gathering networking values if you decide changes are necessary to 

your networking configuration. 

3–14 8222 3694–000

Changing the Network Services EVLAN IP Address 

Unisys recommends that you do not change the IP Address and Subnet Mask for Network 

Services (EVLAN path). However, one reason to change these addresses is because you 

already have nodes in your network using the same subnet. In this case, choose a 

different private set of IP addresses that do not conflict with the subnets in your network. 

Modify the EVLAN IP address and mask through the system editor. Refer to ″Using the 

System Editor to Configure MCP Networking″ later in this section for more information. 

Notes: 

• The Internet Assigned Numbers Authority (IANA) has reserved Class C addresses 

192.168.0.0 through 192.168.255.255 for use within private networks (see RFC 1918). 

• Changing the IP addresses of the EVLAN path is likely to require updates to the 

firewall rules within the I/O engine of the FS6200 Server. See the topic “Environment 

Secured Configuration” in Section 4 of this guide. Call Home functionality might also 

be affected. Refer to the appropriate Call Home documentation for more information. 

Supporting MCP Network Adapters 


MCP network adapters provide MCP access to qualified NICs, operating at speeds ranging 

from 10 megabits per second to 10 gigabits per second. Although the MCP network 

adapter software service allows connection to networks comprised of high-performance 

technologies, the actual data transfer rate might be less than the potential maximum for 

that network technology. For example, a 10Gb Ethernet MCP network adapter allows the 

MCP server to participate on a 10Gb Ethernet backbone, but the MCP does not transfer 

data at the maximum 10Gb Ethernet transfer rate. 

The FS6200 Server includes all necessary licenses required for MCP network adapter 

connections through TCP/IP. 

Network Services supports up to eight MCP network adapter connections per Network 

Processor – where a connection is an Ethernet port, an 802.1Q Virtual LAN (VLAN) 

connection, or an Adapter Team. In essence, the ClearPath Network Services view of an 

adapter is the same as that of the I/O engine view of the adapter. If it shows up as an entity 

to be managed within the Network Connections list of the Network and Sharing center 

within Control Panel, then you can make an MCP network adapter out of it. This is 

accomplished through the MCP Networking entities listed by the System Editor and using 

one of the MCP network adapter connections for a network processor. 

Network Services supports up to 6 network processors per I/O engine on ClearPath 

FS6200 Server systems. Both TCP/IP and Heritage Network Services (BNA) are supported 

to and from the MCP Environment through MCP network adapter connections. The use of 

Heritage Network Services might require the purchase of additional MCP software 

licenses beyond the base Integrated Operating Environment package. 

8222 3694–000 3–15


Setting the Local Address 

The MAC address for a network adapter is set through the Network Connections Control 

Panel applet. You cannot set the MAC address of an adapter through the local address 

attribute of an ADD CONNECTION GROUP command in your CNS initialization file. You 

can interrogate the current MAC address of an adapter using the NW CONNNECTION 

inquiry on the Connection Group. You must make modifications on the system where the 

adapter exists. From the MCP Console on the Operations Server, start a Remote Desktop 

session to the appropriate I/O engine and perform the following steps to override the 

factory assigned MAC address of an adapter. 

Perform the following steps in the I/O engine environment to override the factory assigned 

MAC address of an adapter: 

1. Start Device Manager. 

2. Select the adapter that you want to modify. 

3. Adjust the properties of the adapter by right-clicking the adapter and selecting 

Properties or by selecting Status, and then clicking Properties. 

4. Click Configure under the adapter name. 

5. Click Advanced tab on the Properties screen. 

6. Select the Locally Administered Address property. 

7. Enter your desired address in the Value box. 

8. Click OK. 

TCP Offload Settings 

TCP Offload Engine (TOE) options within the Advanced Adapter Settings of a NIC are 

incompatible with MCP use of adapters. You should turn off all TOE features on any 

adapters that are to be used by ClearPath MCP Networking. TOE features include IPv4 

Checksum Offload, Large Send Offload, TCP Checksum Offload, and UDP Checksum 

Offload, among others. 

Preparing to use Adapter Teaming and IEEE 802.1Q Virtual LANs 

Network Services MCP network adapter software supports Adapter Teaming and 802.1Q 

Virtual LANs (VLANs). 

You can use Adapter Teaming to provide fault tolerance at the adapter level (ClearPath 

MCP Network providers TCP/IP and BNA have alternate means of providing fault tolerance 

as well). 

Note: Although Adapter Teaming can also be used to perform port aggregation, 

distributing network traffic across multiple adapters, this type of team offers marginal 

value for ClearPath MCP customers and is not recommended. 

System and user programs see a single virtual adapter team instead of the individual 

adapters that make up that team. 

3–16 8222 3694–000

IEEE 802.1Q VLANs allow a single network adapter to segregate its traffic among two or 

more virtual LANs. Each VLAN on an adapter is represented by a separate network adapter 

entry within the Network Connections Control Panel applet, effectively making a single 

adapter appear to Network Services as more than one adapter. IEEE 802.1Q VLANs are 

based on the addition of a 4-byte tag to the packet header, identifying the VLAN for that 

packet. 

Adapters that are to be used in an adapter team or that are to support VLANs should be set 

to “Unassigned” through the Networking Configuration tool before building the team or 

configuring the VLANs. 

You must perform modifications on the system on which the adapter exists. After 

removing the MCP assignments for any adapters you want to modify through the System 

Editor, use remote desktop to the appropriate I/O engine, and modify the adapter settings 

for VLANs and teaming. 

Adapter Teaming and VLANs are configured using Intel® PROSet for Device Manager. 

Intel® PROSet is an extension of Device Manager. As a result of the installation of the 

Intel® PROSet software, additional tabs have been added to the supported Intel adapters 

in Device Manager 

You must have administrative rights to use Intel® PROSet. Refer to the Intel Network 

Adapters User’s Guide for additional information about creating and managing Adapter 

Teams and VLANs. 

If the FS6200 Server is a member of only one VLAN on a given adapter port, tagging is not 

necessary on that port. Turn tagging off at the switch port and configure the LAN Switch 

port to be a member of the appropriate VLAN instead. No VLAN tagging should be 

configured at the FS6200 Server. 

If the FS6200 Server is to be a member of multiple VLANs over the same adapter port, 

then both the LAN switch and the FS6200 Server must be configured. The switch 

connected to the FS6200 Server must support IEEE 802.1Q tagging. 

Perform the following steps to modify the adapter settings for VLANs and teaming: 

• At the switch, tagging should be enabled, and all VLAN ID assignments made at the 

specific port. Follow any other vendor-specific instructions that might exist. 

• At the FS6200 Server, use Intel® PROSet Device Manager to assign desired adapters 

to teams. 

• For each VLAN defined and each Adapter Team defined, a new “adapter” is created 

that is visible in Device Manager. 

• Also, the CNS and TCP/IP initialization files on the MCP must be updated to reflect the 

addition of the Line (NP/Line ID pair). 

Preparing to Use Jumbo Frames 


Jumbo frames are large Ethernet frames used in high-performance networks (up to 9000 

bytes of payload) to increase performance over long distances. Jumbo Frames improve 

ClearPath throughput and reduce the CPU cycles used for networking. This improvement 

8222 3694–000 3–17


is achieved by reducing the number of frames an application must process. This 

improvement is particularly beneficial for applications that use large message sizes such 

as file transfers. The remote system and the connecting network equipment along the 

entire communications path must support jumbo frames to use this feature effectively. 

You can use Jumbo Frames with TCP/IP, BNA, and BNA over IP (BIP). In addition to the 

application message size, the performance benefits vary depending on which of these 

protocols you use. 

You must configure Jumbo Frames both within the I/O engine and within ClearPath MCP 

Networking. You must perform modifications on the system where the adapter exists. 

Perform the following steps in the I/O engine environment to configure Jumbo Frames on 

an adapter: 

1. Start Device Manager. 

2. Select the adapter that you want to modify. 

3. Adjust the properties of the adapter by right-clicking the adapter and selecting 

Properties or by selecting View status of this connection, and then clicking 

Properties. 

4. Click Configure under the adapter name. 

5. Select the Advanced tab on the Properties screen. 

6. Select the Jumbo Packet property. 

7. Select one of the offered values. The proper value depends upon the capabilities of 

your network switching equipment. 

8. Click OK. 

Within the MCP, you must set the following attributes to desired values for applicable lines 

(Connection Groups) and devices (Connections): 

• Max Input Message Size (MIMS) 

• Max Output Message Size (MOMS) 

• Max Input Message Size Limit (MIMSL) 

• Max Output Message Size Limit (MOMSL) 

The recommended frame size for Jumbo Frames is 9014, including the MAC header, but 

excluding the Cyclic Redundancy Check (CRC). Configure this value in the NIC driver and 

translate it to the following MIMS/MOMS/MIMSL/MOMSL values: 

• 9000 for the Connection Group 

• 9000 or 8996 for TCP/IP and BNA/BIP connections respectively 

Communications between a jumbo-capable and a jumbo-incapable end-system is 

generally not a problem. This follows because a common frame size is negotiated 

between the systems when they establish a dialog. This situation applies to TCP/IP, BNA, 

3–18 8222 3694–000

and BIP protocols. Communications between a jumbo-capable and a jumbo-incapable end 

system is a problem for connectionless protocols such as UDP and ICMP because they 

are datagram-based and do not negotiate a connection. 

Each system transmits frames sized up to the mtu value of the system if no router is in the 

path. Any frames larger than 1,500 bytes are dropped if they are not supported by the 

receiver. The only potential issue occurs with the ICMP protocol—“pings” larger than 

1,500 bytes fail. 

A useful technique in mixed networks is to logically segregate jumbo frame traffic from 

standard traffic by using IEEE 802.1Q Virtual LANs (VLANs). 

Using the System Editor to Configure MCP Networking 

If you need to modify the existing configuration of MCP networking on your FS6200 

Server to match your environment, you must configure MCP networking through the 

System Editor of the MCP Console. 

Note: Any networking configuration change you make must also be reflected in the MCP 

initialization files. Refer to Appendix A of this guide and the TCP/IP Implementation and 

Operations Guide for details on modifying the MCP initialization files. 

You use the System Editor to perform networking firmware configuration and the 

configuration information is stored in the PCD file. 

The System Editor uses a matching algorithm to assign network processor numbers and 

Line IDs to the adapters that are installed in the system. These assignments are presented 

to the operator in the System Editor configuration tree view as the configuration default. 

You can modify that configuration as needed. 

The following features and rules apply to the use of System Editor when configuring 

networking. 

You can update the following networking characteristics: 

• The network processor number of the network processor node. 

• The Line Number of the line for a network processor node. 

• Movement of lines from network processor to network processor. 

• The EVLAN IP address on the I/O engine. 

• The EVLAN IP address mask on the I/O engine. 

• Enabling or disabling a line for MCP. 

• Deleting a network processor node with no lines. 

• Creating a new network processor node. 

Operational Rules 


The following rules of operation apply to your use of the System Editor: 

8222 3694–000 3–19


• Modification of an active PCD must be done while the MCP is halted. 

• Network processor numbers and I/O device numbers are not allowed to overlap. 

• Default network processor numbers are in the range from 200-299. 

• The entries for the EVLAN, JProcessor Specialty Engine, and ePortal connections 

appear on the first designated network processor for each defined I/O engine. 

• The entries for the EVLAN, JProcessor Specialty Engine, and ePortal connections have 

defined line numbers that cannot be modified. 

• The remaining network processors show the connections (on NICs and virtual NICs) 

that are visible within the I/O engine. 

• Checking or unchecking of lines or network processor instances determines whether 

or not that adapter is bound to the MCP networking service. 

• Lines or network processors that are not bound to the MCP are not checked. 

Note: The FS6200 Server networking allows adapters to be used only as MCP network 

adapters exclusively or adapters assigned to the MCP Firmware I/O engine exclusively. 

Configuring MCP Networking Using the System Editor 

Perform the following steps to configure MCP networking: 

1. Launch the MCP Console on the Operations Server. 

2. Click the System Editor button on the toolbar of the MCP Console. 

3. Perform one of the following actions to open a PCD file: 

• Open the active PCD file you want to edit by selecting Active from the toolbar. 

• Open an existing non-active PCD file you want to edit by selecting Open from the 

toolbar. 

• Click the Adjust Resources button to auto-adjust the PCD file that is open if 

necessary. 

Note: If the PCD file needs adjusting since the last time it was used, the 

auto-adjust window appears and does not require you to click the Auto Adjust 

button. 

• Open a new PCD file causing the launch of an auto build of a PCD by clicking the 

New button. 

The PCD file is ready to be edited. 

Note: For a new PCD that uses the default System Editor assignments, no further 

modification might be necessary. If this is the case, proceed with step 8. Otherwise, 

continue with step 4. 

3–20 8222 3694–000

4. To modify a network processor object, locate the NP object you want to modify and 

perform the appropriate actions as follows: 

• To modify the network processor instance identifier, select the NP object and on 

the Properties panel and update the NP instance identifier field . 

• To remove the NP from being enabled by the MCP Firmware of the I/O engine, 

uncheck the check box for that NP. 

• To assign a NP to be enabled by the MCP Firmware of the I/O engine, select the 

check box for that NP. 

5. Perform the following steps to modify the properties of an EVLAN line on a NP: 

a. Type the IP address in the EVLAN IP Address field for the EVLAN connection 

object. 

The IP address that initially appears is the default. If you enter a different value, it 

is used to modify the IPv4 address of the EVLAN adapter in the IOE. A value 

entered here is stored in the registry of the I/O engine and appears the next time 

you use System Editor to configure MCP networking. 

b. Type the subnet mask in the EVLAN IP Address Mask field of the EVLAN 

connection object. The subnet mask that initially appears is the default. If you 

enter a different value, it is stored in the registry of the I/O engine and appears the 

next time you use System Editor to configure MCP networking. 

6. To modify a line object, locate the line object of the adapter you want to modify and 

perform the appropriate actions as follows: 

• To return an MCP network adapter to the control of the I/O engine, locate the line 

for the adapter you wish to modify and uncheck the check box for that line. 

• To assign a NIC or a virtual adapter as an MCP network adapter, locate the line for 

the adapter you want to modify and check the check box for that line. 

• To modify the line instance identifier, select the Line object and update the Line 

ID field in the Properties panel. 

7. Verify the accuracy of your settings. If any changes are needed, remain in the 

configuration tree view and complete any necessary modifications. 

8. Save the PCD by clicking the Save button. 

9. If necessary, ready the PCD for operation by clicking the Set Active button. 

A dialog box might be displayed indicating that a reboot of the I/O engine is required. 

10. Click Yes to reboot the I/O engine. 


The networking settings are written to the registry of each affected I/O engine. If you 

have changed any adapter line numbers or the network processor numbers of existing 

MCP connections, the necessary protocol bindings of the adapters are modified. This 

process can take several minutes to complete. The appropriate Net icon in the MCP 

View tab of the MCP Console is offline during the reboot. 

When the I/O engine finishes rebooting, the appropriate Net icon in the MCP View 

tab of the MCP Console is running and the network configuration is available. 

Note: You might need to adjust the network initialization files to match the updated 

configuration. 

8222 3694–000 3–21


For more detailed information on System Editor for network configuration, refer to the 

MCP Console Help. 

Sample ADAPTERS.TXT File 

The MCP Networking configuration utility generates an ADAPTERS.TXT file on each I/O 

engine. This file is incorporated into any Networking Dump that the user captures. The file 

gives a summary of the installation, including a list of network adapter choices. 

The format of the ADAPTERS.TXT file adapter entry is the following. 

()Assigned to NP LineID PCI Slot 

The file sample contents for a NIC adapter in slot1 and slot 5 follow. 

Adapter Assignments 

Wednesday March 28, 2012 11:51:32 AM Eastern Standard Time 

Hostname: Hostname: CPMCP1 

EVLAN IP address: 192.168.16.6/255.255.255.252 

(EVLAN) 

Assigned to NP 210, LineID 0, PCI Slot 

Local Area Connection 4 (Java Processor 1) 


Local Area Connection 10 (Java Processor 3) 


Local Area Connection 7 (ePortal) 


Local Area Connection 13 (Intel(R) Ethernet Server Adapter I350-T4 #4) 

Assigned to NP 211, LineID 4, PCI Slot 1/4 

Local Area Connection 2 (Intel(R) Ethernet Server Adapter I350-T4) 








Local Area Connection 15 (Intel(R) Ethernet Server Adapter I350-T4 - VLAN : LAN186) 




Local Area Connection 17 (Intel(R) Ethernet Server Adapter I350-T4 #3 - VLAN : LAN183) 


Updating the MCP View of the Network 

When you receive a ClearPath system, it has preconfigured CNS and TCP/IP initialization 

files. These initialization files establish TCP/IP communications between the components 

of a ClearPath system on a private LAN. 

3–22 8222 3694–000

You must replace or modify the preconfigured initialization files if you want to bring your 

ClearPath system into an existing TCP/IP network. To connect to an existing TCP/IP 

network, you need to get IP addresses for the addressable ClearPath components and 

define them to the public network. 

The following tables lists preconfigured values for the MCP Environment in FS6200 

Servers. Use the values in this table as many times as needed if you are defining more 

lines per network processor or if you are configuring an additional network processor. The 

table also provides space to enter the new values you intend to use. Preconfigured values 

are defined in the CNS and TCP/IP initialization files provided with your server (described in 

Appendix A). 

Table 3–7. MCP Networking Values Configuration Worksheet for FS6200 

Server 

MCP Environment Preconfigured Value New Value 

Host Name CPMCP1 

TCP/IP Domain Name CPMCP1.CUSTOMER.COM 

Table 3–8. MCP Networking Values for FS6200 Servers IOE-1 


NP number NP 210 Must match the value entered 

in the Networking 

Configuration portion of 

System Editor. 

MCP Adapter #0 EVLAN 

IP Address 192.168.16.5 Do not change (note 1) 

Subnet Mask 255.255.255.252 Do not change (note 1) 

LAN Local Address (line 0) 08000B002100 (note 2) 

MCP Adapter #1 Internal connection to 

JProcessor 1 

IP Address 192.168.16.141 

Subnet Mask 255.255.255.252 (/30) 

LAN Local Address (line 1) *Default 

Line-ID 1 


JProcessor 3 

IP Address 192.168.16.149 

Subnet Mask 255.255.255.252 (/30) 


8222 3694–000 3–23


Table 3–8. MCP Networking Values for FS6200 Servers IOE-1 (cont.) 



Line-ID 2 

MCP Adapter #3 Internal connection to ePortal 

IP Address 192.168.223.250 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 3 





MCP Adapter #1 

IP Address 192.168.237.50 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 1 


IP Address 192.168.237.51 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 2 


IP Address 192.168.237.52 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 3 


IP Address 192.168.237.53 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 4 

3–24 8222 3694–000








IP Address 192.168.237.54 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 1 


IP Address 192.168.237.55 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 2 


IP Address 192.168.237.56 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 3 


IP Address 192.168.237.57 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 4 



This NP can be used in place 

of or in conjunction with NP 

214. 

8222 3694–000 3–25









IP Address 192.168.237.58 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 1 


IP Address 192.168.237.59 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 2 


IP Address 192.168.237.60 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 3 


IP Address 192.168.237.61 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 4 



214. 

The IP Addresses from NP 

214 could be used here if NP 

214 is not enabled. 

3–26 8222 3694–000

Table 3–9. MCP Networking Values for FS6200 Servers IOE-2 






MCP Adapter #0 EVLAN 

IP Address 192.168.16.9 Do not change (note 1) 

Subnet Mask 255.255.255.252 Do not change (note 1) 

LAN Local Address (line 0) 08000B002100 (note 2) 


JProcessor 2 

IP Address 192.168.16.145 

Subnet Mask 255.255.255.252 (/30) 


Line-ID 1 


JProcessor 4 

IP Address 192.168.16.153 

Subnet Mask 255.255.255.252 (/30) 


Line-ID 2 

MCP Adapter #3 Internal connection to ePortal 

IP Address 192.168.224.250 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 3 



Configuration portion of the 



IP Address 192.168.237.62 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 1 


8222 3694–000 3–27





IP Address 192.168.237.63 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 2 


IP Address 192.168.237.64 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 3 


IP Address 192.168.237.65 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 4 






IP Address 192.168.237.66 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 1 


IP Address 192.168.237.67 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 2 




225. 

3–28 8222 3694–000



IP Address 192.168.237.68 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 3 


IP Address 192.168.237.69 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 4 






IP Address 192.168.237.70 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 1 


IP Address 192.168.237.71 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 2 


IP Address 192.168.237.72 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 3 




224. 

The IP Addresses from NP 

224 could be used here if NP 

224 not enabled. 

8222 3694–000 3–29





IP Address 192.168.237.73 

Subnet Mask 255.255.255.0 (/24) 


Line-ID 4 

Notes: 

1. Unisys recommends that you do not change the IP Address and Subnet Mask for the 

EVLAN adapter. However, one reason to change these addresses is because you 

already have nodes in your network using the same subnet. In this case, choose an IP 

address that is reserved by IANA and does not conflict with the subnets in your 

network. 

2. Line 0 is reserved for the EVLAN adapter. If you change the LAN Local Address for the 

MCP EVLAN adapter, do not use 08000B062259 as the address. The EVLAN adapter 

in the I/O engine already uses this address. 

3. Because each of the MCP EVLAN adapters resides on a separate virtual LAN, the 

same LAN Local Address can be used for each adapter. 

4. Network Services supports the configuration of up to eight MCP network adapters per 

network processor. If you are defining an MCP network adapter, you need to supply 

the following values to the NAU: 

• Line ID 

• LAN Local Address (physical or MAC address of the adapter) 

Using Sample CNS and TCP/IP Initialization Files 

Appendix A of this guide describes a set of initialization files that are shipped with each 

FS6200 Server. These CNS and TCP/IP initialization files contain default values necessary 

to configure an isolated TCP/IP network without public internet access. 

The sample initialization files are 

• INIT/SAMPLE/CLEARPATH/VNP/DUALIOP/CPMCP1/CNS 

• INIT/SAMPLE/CLEARPATH/VNP/DUALIOP/CPMCP1/TCPIP 

You can use these initialization files without alteration if you do not need to connect to an 

external network. Otherwise, edit the appropriate CNS and TCP/IP initialization files as 

necessary for your configuration. The file descriptions in Appendix A contain remarks to 

assist in this editing process. 

3–30 8222 3694–000

Using Sample BNA Initialization Files 

Appendix A of this guide describes a BNA initialization file that might be appropriate for 

your FS6200 Server. This file defines BNA connections on a single MCP Adapter. 

Changing the Administrator User Name and 

Password 

The user name, called Administrator, is the built-in administrator account for the 

Operations Server and all of the environments (I/O engine, E-mode engine, JProcessor 

Specialty Engine, and so on) on your FS6200 Server. It is one of the most targeted account 

names by malicious programs and hackers. As a security precaution, you should rename 

this account to another less common name. 

During the initial installation of the FS6200 Server at your site, the user name 

Administrator and the associated password are changed from the default factory settings 

to credentials that you specified in the FS6200 Server System Planning Guide for various 

environments. If this change has not been done, make the change. Unisys recommends 

that you set a password policy to change the password from time to time. 

Note: For all ePortal environments, the user name Administrator is removed during the 

ePortal installation; ePortal manages the user accounts itself. Therefore, the following 

procedure should not be performed for any ePortal environment. 

Perform the following steps to change the Administrator account user name and 

password in each environment: 

1. Click Start and select Control Panel. 

2. Click Add or remove user accounts under User Accounts and Family 

Safety. 

3. Click the Administrator account icon. 

4. Click Change the account name. 

5. Type the new name in the New account name box and then click Change Name. 

You return to the Make changes to Administrator’s account window. 

6. Click Change the password. 

7. Type the current password in the Current password box. 

8. Type the new password in the New password box and retype it in the Confirm 

new password box. 

9. (Optional) Type a hint in the Type a password hint box. 

10. Click Change password. 


11. Log off the system and log back on using the new Administrator account name and 

password. 

8222 3694–000 3–31


Changing the Default Systems Management 

Account Password 

Systems management software running on the Operations Server needs to communicate 

with software running in the other supporting environments. This communication is 

protected through the use of an internal user account, UIS_SysMgmt. Your system comes 

initially configured with a default password for this account. 

Note: It is strongly recommended you perform the following instructions to update the 

password to a value unique to your system. 

To change the UIS_SysMgmt account password, perform the following steps: 

1. On the Operations Server, open the MCP Console. 

2. From the Configure menu, select System Account. 

3. Verify that there are no errors communicating with any environments in the system. 

Do not change the password until any errors are resolved. 

4. If there are no errors reported, select Change Password to update the account 

password. 

Refer to “Managing the System Account” in the MCP Console Help for additional 

information. 

Note: When changing the UIS_SysMgmt account password, you do not specify a 

password directly, but instead specify a “seed key” which is used to generate a secure 

password. You can choose any value for the seed key as you desire. It is recommended 

that you choose something you can remember in case you need to reset the password on 

a component in the future. You can use the MCP Console to change the seed key to a new 

value at any time. 

Configuring the MCP Environment 

You might want to consider some additional configuration settings and installation 

procedures that are beyond the scope of this manual when you initially configure the 

FS6200 Server MCP Environment. 

The MCP Implementation Guide contains many procedures that are useful for initially 

setting up any MCP system. Not all of the procedures in the guide are necessary for the 

FS6200 Server because the MCP Environment is preconfigured with many of the 

recommended settings. Refer to Section 5 “Setting up Your MCP Partition” of the MCP 

Implementation Guide for topics related to 

• Migrating settings from a previous MCP system to a new halt/load disk on your new 

system. 

• Migrating the halt/load disk itself from your old system into use on your new system. 

• Integrating your MCP Environment with Microsoft Networks. 

3–32 8222 3694–000

Some of the procedures in MCP Implementation Guide can be completed by Unisys 

support for you when your system is initially installed. 

Configuring Call Home Services 

Call Home provides automatic e-mail alert messages when hardware and software-related 

events occur on the FS6200 Server that requires attention. Call Home e-mail alerts are 

automatically sent to Unisys Support with a copy sent to up to three e-mail addresses that 

you designate. Unisys Support responds accordingly with the appropriate action. 

Call Home requires initial on-site configuration before it is ready for use. Typically, the initial 

configuration of Call Home is performed by Unisys support personnel as part of the 

FS6200 Server installation. If you need to make configuration changes after installation, 

use the MCP Console. Refer to “Managing Call Home Services” in the MCP Console Help 

for more information. 

Configuring the Operations Server 

The Operations Server is the primary method of accessing the FS6200 Server and enables 

you to manage the MCP Environment, specialty engines, and Network Services. Two 

Operations Servers are delivered with your FS6200 Server. One Operations Server is 

currently active. 

Configuring the Open Management Interface (OMI) 

Your FS6200 Server is capable of being managed by open standards-based management 

tools. The Open Management Interface (OMI) is provided with your system and requires 

manual configuration. You can find information about OMI on the Unisys Product Support 

website at the following address: 



At the website, locate your system type, click Drivers and Downloads, and then select 

the OMI installation package. 

8222 3694–000 3–33


3–34 8222 3694–000

Section 4 

Operating the Server 

This section discusses issues you should consider in the operation of your FS6200 Server. 

Managing Power 

This subsection discusses considerations for managing power on your FS6200 Server. 

Viewing Platform Hardware Power Status 

You can view the power status of the platform hardware using either of the following 

methods. 

• From the MCP Console, within the Component View tab, you can see the power 

status of each cell. 

• To check a specific component, view the front panel of the desired cell. The LED is lit 

with a green light and the LCD light is lit with a blue light. 

• Access the BMC web interface from the MCP Console and click the Power tab. View 

the power status that is displayed on the screen. 

Powering On the Platform Hardware 

You can power-on a specific platform using either of the following methods. 

• Press the power button on the front of the desired cell. 

• Use the BMC web interface to remotely power on the cell. 

Note: It might be desirable to access and monitor the platform as it boots to gauge 

progress and know when it nearing initialization complete and is ready for use. Refer to 

“Monitoring the Platform Boot Progress” later in this section for more details. 

Monitoring the Platform Boot Progress 

You can use the following methods to monitor the progress of a specific platform boot 

progress: 

8222 3694–000 4–1


• LCD Panel 

You can use the LCD panel on the front of the cell to monitor the initial phase of boot 

from power-off. Immediately after power-on, the LCD displays a ″System booting...″ 

message. This message is displayed until the hardware has finished initializing and the 

system BIOS starts to boot. Once the system BIOS has booted, the LCD displays the 

system name. 

• Virtual Console 

After the System BIOS starts booting, you can use the platform management card 

Virtual Console to display the messages displayed by the cell as it boots through the 

system BIOS and the BIOS on other hardware on the platform (for example, internal 

disk controller), and as s-Par boots and initializes (ISM only). 

To launch the Virtual Console for a particular platform, access the BMC web interface 

from the MCP Console of the platform. After logging in, click the Launch button on 

the right side of the screen to launch the virtual console 

• Platform Console 

You can access the Platform Console of the ISM from the MCP Console to view the 

status of the environments. 

Once s-Par has booted (ISM only) and it reports status of various component 

environments as ″Running″, start the Platform Console to monitor the status of the 

platform environments as they are started. 

• MCP Console 

You can access the MCP Console from the Operations Server or a remote workstation 

to view the state of the MCP Environment. Once the MCP Environment is loaded, use 

an MCP ODT to perform operations from within the MCP Environment. 

• MCP ODT 

You can access an MCP ODT from the Operations Server or a remote workstation to 

view the internal status of the MCP Environment and to perform operational tasks 

within the environment. 

Shutting Down the Platform 

The platform, including the component environments, can be gracefully or forcefully 

shutdown. Using either shutdown method also powers off the platform. 

Note: Before you shutdown the platform, halt the MCP using the MCP Console. 

• To shutdown the platform, access the MCP Console and from the Component 

View tab, right-click the System node and then click Shutdown (Graceful). 

• To forcefully shutdown the platform, access the MCP Console and from the 

Component View tab, right-click the System node and then click Shutdown 

(Forceful). 

4–2 8222 3694–000

Powering Off the Platform Hardware 

You can power-off the platform hardware using either of the following methods but only 

use them if the methods listed under the topic “Shutting Down the Platform” earlier in 

this section are not available. 

• Press and hold the power button on the front of the platform hardware for four 

seconds. 

• Use the BMC web interface to remotely power off the platform hardware 

Note: This should only be done when the platform and all the platform environments 

have been shutdown. 

Restarting the Platform after a Shutdown 

The platform including the component environments can be restarted after either a 

graceful or forceful shutdown of the environments. 

Note: The Operations Server must be powered on, the systems management engine 

must be running, and the MCP Console must be accessible to perform this task. 

To perform a power-on after a graceful shutdown of the system, access the MCP Console 

from the Operations Server or a remote workstation. From the Component View tab, 

right-click the System node and then click Power On. 

Platform Services 

The s-Par software is used to subdivide the ISM. These subdivisions are called 

environments. The ISM hosts several environments, including specialty engines, that 

share the resources of the single hardware platform. 

The Platform Console provides an interface to the environments that exist in the FS6200 

Server. 

Tasks You Can Perform from the Platform Console 

You can perform the following tasks from the Platform Console: 

• Environment tasks 

Environment tasks are commands you use to change the state of an environment. 

Examples include Run to start an environment and Shutdown to stop an environment. 

• Platform tasks 


Platform tasks are commands you use to control the platform. An example is changing 

the password of the Platform Console. 

Refer to the Platform Console Help for more information on environment tasks and 

platform tasks. 

8222 3694–000 4–3


General Environment Operational Tasks 

The following tasks can be performed on any environment. 

Viewing the Status of an Environment 

Access the Platform Console from the Operations Server to view the status of s-Par 

environments on the ISM. You can also view all of the environments, including the 

Operations Server, from the Component View of the MCP Console. 

Shutting Down an Environment 

A platform environment can be gracefully or forcefully shut down. 

Note: Before you shutdown an environment, halt the MCP using the MCP Console. 

• To perform a graceful shutdown of an environment, access the Platform Console from 

the MCP Console and issue a ″Shutdown″ command on an environment. 

• To perform a forceful shutdown of an environment, access the Platform Console from 

the MCP Console and issue a ″Halt″ command on an environment. 

Restarting an Environment 

A platform environment can be restarted after either a graceful or forceful shutdown. 

Note: Before you shutdown and restart an environment, halt the MCP using the MCP 

Console. 

• To shutdown of an environment followed by a restart, access the Platform Console 

from the MCP Console and issue a Restart command on an environment. 

• To forcefully shutdown of an environment followed by a restart, access the Platform 

Console from the MCP Console and issue a Reset command on an environment. 

Note: These actions can also be performed from the Component View tab of the MCP 

Console. 

MCP Environment Operational Considerations 

The MCP Environment is preinstalled and configured at the factory. This subsection 

describes some of the operational conditions for your system and provides information for 

making supported modifications to the configuration and saving your changes. 

4–4 8222 3694–000

Controlling the MCP Environment 

Access the MCP Console from the Operations Server or remote workstation to monitor 

and control the state of the MCP Environment. For more detail, refer to “Managing the 

MCP Environment” in the MCP Console Help. 

MCP Operations 

Access an MCP ODT from the Operations Server or remote workstation to perform 

operational commands within the MCP Environment. 

Environment Secured Configuration 

The FS6200 Server is configured to ensure the security and reliability for the MCP 

Environment. The features of this secured configuration include 

• Disabled front-accessible USB ports 

Disabling the ports prevents exposure to malicious software from portable USB 

devices. 

Note: If you decide to enable the front access USB ports, contact a Unisys service 

representative to change the BIOS settings to enable these ports. 

• A network configuration that uses the Unisys secure access device 

The hardware firewall protects the public LAN from accessing the MCP Environment. 

Note: Refer to the FS6200 Server System Planning Guide for more information. 

• Only the following predetermined set of software is supported in the environments. 

Supported Software Notes 

Unisys MCP Firmware 

Unisys MCP Network Services (I/O engine 

only) 

WebEnabler for ClearPath MCP 

(NXWebStation) (systems management 

engine only) 

Driver and OCManager for Emulex Fibre 

Channel Host Bus Adapters (I/O engine only) 

Driver and tools for Intel NIC Adapters 

Unisys MCP Cryptography Services (I/O 

engine only) 

• A pre-defined Security Configuration Wizard (SCW) policy 


Software is required and preinstalled. 

Software is optional and installed by the 

customer. 

This policy further reduces attacks on the environments. Refer to “MCP Firmware 

Environment Policy” later in this section for more information. 

8222 3694–000 4–5


MCP Firmware Environment Policy 

Unisys determined the minimum functional requirements of standard environments and 

created a policy that implements the needed configuration. This policy is referred to as the 

“MCP Firmware Environment Policy” in this guide and it protects the environment from 

possible attacks from external applications. 

The MCP Firmware Environment Policy modifies the server as follows: 

• Unnecessary services are disabled based on the functionality defined for the systems 

management engine, E-mode engine, and I/O engines. 

• Firewall rules are created or modified to enable only necessary connections for the 

MCP Environment. 

• Settings for LAN Manager and IPv6 are selected to support functionality required by 

the MCP Environment. 

• The audit policy is defined. 

Policy Services 

The MCP Firmware Environment Policy enables services to support the following features 

and options. Some other services that support server roles and features, but are not 

mentioned in the following list, are disabled. 

• Microsoft Network Client 

This feature is supported by two services: Workstation and TCP/IP NetBIOS Helper. 

Microsoft Network Client enables users to share files, print, and log on to the network 

by creating and maintaining network connections to remote servers using the SMB 

protocol, and by providing support for the NetBIOS over TCP/IP (NetBT) service and 

NetBIOS name resolution for clients on the network. 

A set of firewall rules for file and printer sharing are enabled to enable the following 

outbound connections: 

- Ping requests for both IPv4 and IPv6 

- NetBIOS Datagram transmission and reception (UDP 138) 

- NetBIOS name resolution (UDP 137) 

- NetBIOS Session Service connections (TCP 139) 

- SMB transmission and reception (TCP 445) 

Consequently, from the environments, you can ping a remote computer or map a drive 

to a share on a remote computer. 

Note: Inbound Internet Control Message Protocol (ICMP) requests to the host of an 

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 host of an environment, not even those sent from the MCP. Refer to 

“Enabling MCP Ping Commands through the EVLAN Connection” later in this section 

for information on how to add a firewall rule to enable inbound ICMP requests. 

4–6 8222 3694–000

• Domain Name System (DNS) Client 

This feature is supported by a single service: DNS Client. 

DNS Client registers the Windows host name of an environment and enables you to 

use computer names, in addition to IP addresses, when accessing other computers in 

the network. 

A firewall rule is predefined to open UDP port 53 for outbound DNS requests. 

• Remote Desktop 

This feature is supported by three services: Remote Desktop Services, Remote 

Desktop Configuration, and Remote Desktop Services UserMode Port Redirector. 

Included in the MCP Firmware Environment Policy is a predefined Remote Desktop 

firewall rule for inbound connections. This rule opens TCP port 3389. However, the 

scope of the Remote Desktop firewall rule has been modified to restrict inbound 

remote connections, allowing connections only from the following range of IP 

addresses on the management LAN: 

192.168.222.20 through 192.168.222.59 

If these addresses do not match your network configuration, use the 

ChangeRulesForMCP.ps1 script to modify the Remote Desktop rule. For more 

information on how to run this script, refer to “Using the ChangeRulesForMCP.ps1 

Script” later in this section. 

• SNMP 

Firewall Rules 

The SNMP service is enabled only on the systems management engine to allow the 

use of SNMP traps by the MCP Firmware. There following firewall rules that are 

associated with this service and are configured in support of this service: 

- SNMP Service (UDP In) – This firewall rule is disabled. 

- SNMP Trap Service (UDP In) – This firewall rule is enabled. 

• Local Application Installation 

This option is supported by one service: Windows Installer. 


Installer enables you to install supported applications on an environment. This service 

also enables you to remove or modify applications. 

Note: Do not use Installer to install unsupported applications on an environment. 

Doing so can jeopardize the stability and security of the system. 

In addition to the default core networking rules and the predefined firewall rules that are 

associated with a previously discussed feature, Unisys created additional firewall rules 

that support specific MCP functions. These rules are described in Table 4-1. 

8222 3694–000 4–7


Table 4–1. Unisys-Defined Firewall Rules for MCP Functions 

Firewall Rule Name Description 

Unisys ODT (TCP-In) This rule enables inbound connections on TCP 

ports 3001-3016 for remote WebEnabler ODT 

connections. Each port corresponds to an ODT 

unit. This rule further restricts the scope of 

remote computers to the address range of 

192.168.222.20 through 192.168.222.59. 

If these addresses do not match your network 

configuration, use the 

ChangeRulesForMCP.ps1 script to modify the 

firewall rule. For more information on how to 

run this script, refer to “Using the 

ChangeRulesForMCP.ps1 Script” later in this 

section. 

Note: This rule is only configured on I/O 

engines. 

Unisys CallHome (TCP-In) This rule enables inbound connections on TCP 

port 13001 for Call Home messages across the 

EVLAN (between 192.168.16.5 and 

192.168.16.6). 







section. 


engines. 

4–8 8222 3694–000

Table 4–1. Unisys-Defined Firewall Rules for MCP Functions (cont.) 



Unisys Configure HBA (TCP-In) This rule is only configured on I/O engines. It 

enables inbound connections on TCP port 

23333 to allow the HBA configuration utility to 

function. This rule restricts the range of remote 

computers to the address range 

192.168.222.58-192.168.222.59. 







section. 


engines. 

Unisys IOE Infiniband Configure (ICMPV4-In) This rule is created only on I/O engines. It 

enables pings from the E-mode engine to the 

I/O engine. This functionality is needed by the 

utility that configures the Infiniband adapters. 

This rule restricts the range of IP addresses 

from which the ping can originate to the 

following: 

192.168.54.1 

192.168.55.1 

192.168.56.1 

192.168.57.1 

192.168.58.1 

192.168.59.1 

192.168.60.1 

192.168.61.1 


engines. 

8222 3694–000 4–9


Table 4–1. Unisys-Defined Firewall Rules for MCP Functions (cont.) 


Unisys EME Infiniband Configure (ICMPV4-In) This rule is created only on the E-mode engine. 

It enables pings from the I/O engine to the 

E-mode engine. This functionality is needed by 

the utility that configures the Infiniband 

adapters. This rule restricts the range of IP 

addresses from which the ping can originate to 

the following: 

192.168.54.2 

192.168.55.2 

192.168.56.2 

192.168.57.2 

192.168.58.2 

192.168.59.2 

192.168.60.2 

192.168.61.2 

Unisys Windows Remote Management 

(HTTPS-In) 

Note: This rule is only configured on the 

E-mode engine. 

This rule is created only on the systems 

management engine. It enables secured 

Remote Management over TCP port 5986. 

This rule restricts the range of IP addresses 

from which the communications can originate 

to 192.168.222.20 – 192.168.222.59. If these 

addresses do not match your network 






section. 

Note: This rule is only configured on the 

systems management engine. 

The firewall rules in Table 4–2 apply only to the JProcessor Specialty Engine environments: 

4–10 8222 3694–000

Table 4–2. Firewall Rules for JProcessor Specialty Engine Environments 


JProcessor VLAN Ping (ICMPv4-In) This rule allows the MCP to ping the 

JProcessor Specialty Engine environment 

through the VLAN connection. This rule 

restricts the IP addresses within the 

JProcessor Specialty Engine environment to 

the following addresses: 

JProcessor ICMP Timestamp Request 

(ICMPv4-In) 

192.168.16.142 

192.168.16.146 

192.168.16.150 

192.168.16.154 

This rule also restricts the IP addresses from 

which the ping can originate to the following: 

192.168.16.141 

192.168.16.145 

192.168.16.149 

192.168.16.153 

This rule will block ICMPv4 timestamp 

requests. This rule applies to all local IP 

addresses and all remote IP addresses. 

JProcessor MCPConnect1 (TCP-In) This rule opens all TCP ports (1024 – 65525) for 

communications from JProcessor1 and the 

MCP. It restricts the communication to the 

JProcessor1 IP address 192.168.16.142 

originating from IP address 192.168.16.141 





originating from IP address 192.168.16.145. 











Network Authentication 


The following policy settings have been defined for environments to communicate with 

other computers: 

8222 3694–000 4–11


Audits 

• LAN Manager Authentication Level is set to “Send LM and NTLM — use NTLMv2 

session security if negotiated.” 

Notes: 

• To change this setting if necessary on the JProcessor Specialty Engine, I/O engine, 

E-mode engine, or systems management engine, use the Local Security Policy 

option available in Administrative Tools in Control Panel. 

• The MCP Environment is preconfigured with NTLMv2 authentication enabled. If you 

decide to disable NTLMv2 authentication in the MCP Environment, consult the topic 

“Client Access Services Authentication Changes” in the Migration Guide for Local 

Security Policy changes that are required in an environment to restore the ability to 

authenticate using MCP Client Access Services. 

Auditing is the process that tracks user activities and records selected types of events in 

the Windows security log. An audit policy defines the type of event information that 

should be collected. The MCP Firmware Environment Policy settings are listed in Table 

4-3. 

Table 4–3. MCP Firmware Environment Policy Audit Policy Settings 

Event Name Security Log Records 

account logon Success, Failure 

account management Success 

directory service access Success 

logon/logoff Success, Failure 

object access Success 

policy change Success 

privilege use Not audited 

process tracking Success 

system events Success, Failure (except the ″Filtering Platform 

Connection″ and ″Other Object Access 

Events″ subcategories) 

To support the potentially large amount of auditing events, Security Event Log size has 

been increased to 2GB. You can modify the auditing policy and the Security Event Log size 

according to your corporate policy and specific usage characteristics. 

MCP Firmware Environment Policy Utility Scripts 

Two utility scripts are provided to manage the MCP Firmware Environment Policy. The 

scripts are written with PowerShell. 

4–12 8222 3694–000

The utility scripts enable you to make certain firewall adjustments, and to restore the 

environment to a previous state in case of problems. Do not modify the content of these 

scripts or attempt to use a script for something other than its intended purpose. Changed 

or altered scripts are not supported 

For normal operations, use the following script to view and analyze the policy and adjust 

the firewall rules: 

• ChangeRulesForMCP.ps1 

For restoring a pervious environment, use the following script: 

• UnisysHarden_Rollback.ps1 

For re-hardening the system if you performed a rollback to an unhardened state, use the 

following script: 

• UnisysHarden.ps1 

These scripts can be found under the following folder on the System Management engine, 

E-mode engine, and I/O engine: 

C:\Unisys\Installation\Firmware\Common\Security 

The usage and syntax of each script utility is described in the following text. 

Note: Do not download and execute scripts from unknown sources. Doing so might put 

your server at security risks. 

Using the ChangeRulesForMCP.ps1 Script 

If you change the IP addresses in your MCP Environment, use the 

ChangeRulesForMCP.ps1 script to change the IP addresses in the following firewall rules: 

• Unisys Call Home (TCP-In) 

• Unisys ODT (TCP-In) 

• Remote Desktop (TCP-In) 

• FTP Server (FTP Traffic-In) 

• FTP Server Passive (FTP Passive Traffic-In) 

• DFS Management (DCOM-In) 

• DFS Management (WMI-In) 

• Unisys Windows Remote Management (HTTPS-In) 

• Windows Remote Management (HTTP-In) 

• Unisys NGAgent (TCP-In) 

• Unisys Configure HBA (TCP-In) 


8222 3694–000 4–13


The Unisys Call Home (TCP-In), Unisys ODT (TCP-In), and Unisys Configure HBA (TCP-In) 

rules exist only on the I/O engine environment. The Remote Desktop (TCP-In) rule exists 

on the I/O engine, E-mode engine, systems management engine, and JProcessor 

Specialty Engine environments. 

In the default firewall rules, the IP address scopes are defined as follows: 

• Call Home connection 

remote = 192.168.16.5 

local = 192.168.16.6 

• Unisys Configure HBA (TCP-In) 

remote = 192.168.222.58 – 192.168.222.59 

local = any 

• ODT connections 

remote = 192.168.222.20 – 192.168.222.59 

local = any 

• Remote Desktop Protocol (RDP) connections 

remote = 192.168.222.20 – 192.168.222.59 

local = any 

• Diagnostic file transfers through FTP 

remote = 192.168.222.11 – 92.168.222.16 

192.168.222.190 – 192.168.222.191 

192.168.222.241 – 192.168.222.248 

local = 192.168.222.58 – 192.168.222.59 

To execute the ChangeRulesForMCP.ps1 script, perform the following steps on each 

environment that is affected: 

1. Log on with the Administrator account. 

2. To begin a PowerShell session, right-click the PowerShell icon on the taskbar and then 

click Run as administrator. 

3. In the User Account Control prompt, click Yes. 

The PowerShell Console window is displayed. 

4. Access the Security subfolder by typing the following command: 

cd ″C:\Unisys\Installation\Firmware\Common\Security″ 

Note: This command input is not case-sensitive. Ensure that either double or single 

quotation marks surround the path name. 

Then press Enter. 

5. At the prompt, type 

.\ChangeRulesForMCP 

4–14 8222 3694–000

Notes: 

Syntax Usage 

• Refer to the information in “Syntax Usage” to replace the parameter in 

this command. 

• The .\ notation before the script name denotes the current path. Without this 

notation, PowerShell cannot locate the script file. 

Use the following syntax when modifying the IP addresses in the firewall rules: 

ChangeRulesForMCP type IP [action] 

Note: Input is not case-sensitive. 

• type 

• IP 

This required parameter determines the rule that is being modified. It can be set to 

ODTRDP, CALLHOME, HBA, or DIAG. 

- Use ODTRDP to modify the rules for both WebEnabler ODT and Remote Desktop 

connections. 

Note: To reduce the number of options required to modify firewall rules when 

non-default IP addresses are configured, the ODTRDP rule will automatically 

modify additional firewall rules that use the same remote addresses as the ODT 

and RDP firewall rules. The same remote IP addresses will also be applied to each 

of the following rules: 

o Unisys NGAgent (TCP-In) 

o Windows Remote Management (HTTP-In) 

o Unisys Windows Remote Management (HTTPS-In) 

o DFS Management (DCOM-In) 

o DFS Management (WMI-In) 

- Use CALLHOME to modify the rule for the Call Home connection. 

- Use HBA to modify the rule for HBA configuration. 

- Use DAIG to modify the rule for diagnostic file transfer. 


Note: This type is valid only on the systems management engine and is used to 

modify the FTP Server (FTP Traffic-In) and FTP Server Passive (FTP Passive 

Traffic-In) rules. While the syntax is the same as the ODTRDP type, the point of 

reference for the Remote IP addresses and Local IP addresses is different. For 

this type, the Remote IP range that is specified refers to the address ranges of the 

non-systems management engine cells and the Local IP refers to the systems 

management engine cell. The Local IP address is automatically determined by the 

script and it uses the supplied IP parameter to represent the Remote IP ranges. 

This implies that if you are changing the MLAN subnet, the MLAN IP of the 

Systems Management Engine should be changed before running the 

ChangeRulesForMCP script with the DIAG type. 

8222 3694–000 4–15


This required parameter provides the actual address data for the rule. 

For a type ODTRDP, HBA, or DIAG rule, the parameter provides one or more remote 

addresses. You can specify any combination of a single IP address, an IP address 

range, or both. To specify an IP address range, use a dash (–) between the starting and 

ending IP addresses. To specify multiple addresses, use a forward slash (/) between IP 

addresses or between IP address ranges. Do not include spaces in the IP address 

syntax. 

For a type CALLHOME rule, you must specify a pair of IP addresses separated by a 

hash sign (#). The first IP address is the EVLAN address for the host (which is treated 

as the local address in the rule). The IP address after the hash sign is the EVLAN 

address for the MCP host (which is treated as the remote address in the rule). Ensure 

these IP addresses match the addresses specified during the ClearPath Network 

Services configuration. 

Note: The IP addresses shown in the following table demonstrate syntax structure, 

and do not specify actual IP addresses to be used. When running the script, use IP 

addresses that are appropriate in your environment. 

Sample Syntax for the IP Parameter Explanation 

ODTRDP, HBA, or DIAG Rule 

10.10.100.60 Single IP address 

10.10.100.1 – 10.10.100.50 Range of IP addresses 

10.10.100.60/10.10.100.1 – 10.10.100.50 Single IP address, followed by a range of IP 

addresses 

CALLHOME Rule 

192.168.10.6#192.168.10.5 EVLAN IP address for the host, followed by the 

hash sign (#) sign, and then EVLAN IP address 

for the MCP host 

• action 

The action parameter is optional and applies only when the type parameter is 

ODTRDP, HBA, or DIAG . It is not needed if the type parameter is set to CALLHOME. 

Only one value can be specified for the action parameter. Specify keep to add the IP 

parameter data to the remote IP addresses already in the rule. 

If keep is not specified as the action parameter, then the existing remote IP 

addresses in the rule are replaced with the value specified for the IP parameter. 

4–16 8222 3694–000

Sample Commands 

• ChangeRulesForMCP ODTRDP 10.10.100.1/192.168.100.10-192.168.100.15 

This command changes the Unisys ODT (TCP-In) and Remote Desktop (TCP-In) 

firewall rules to enable connections from IP address 10.10.100.1 and the IP address 

range of 192.168.100.10 through 192.168.100.15, in addition to the remote IP 

addresses that are already defined in those rules. 

On any cell other than the I/O engine, only the Remote Desktop (TCP-In) rule is 

affected; the Unisys ODT (TCP-In) rule does not exist on the E-mode engine, systems 

management engine, or JProcessor Specialty Engine cells. 

As stated in the preceding Syntax subsection, the Remote IP addresses in the Unisys 

NGAgent (TCP-In), Windows Remote Management (HTTP-In), Unisys Windows 

Remote Management (HTTPS-In), DFS Management (DCOM-In), and DFS 

Management (WMI-In) rules will also be updated. 

• ChangeRulesForMCP ODTRDP 10.10.100.1 

This command changes the Unisys ODT (TCP-In) and Remote Desktop (TCP-In) 

firewall rules to enable connections from IP address 10.10.100.1 only. The existing 

Remote IP addresses in the rules are deleted because an action parameter is not 

specified in the syntax. 

• ChangeRulesForMCP CALLHOME 192.168.1.2#192.168.1.1 

This command affects the Unisys Call Home (TCP-In) rule. The local IP address (host) 

is changed to 192.168.1.2, and the remote IP address (I/O engine) is changed to 

192.168.1.1. 

• ChangeRulesForMCP HBA 10.10.100.1/192.168.100.10-192.168.100.15 keep 

This command causes the Unisys Configure HBA(TCP-In) to allow connections from IP 

addresses 10.10.100.1 and 192.168.100.10-192.168.100.15, as well as the Remote IP 

addresses that are already defined in the rule. 

• ChangeRulesForMCP DIAG 192.168.222.11-192.168.222.19/192.168.100.10- 

192.168.100.15 keep 

This command causes the FTP Server (FTP Traffic-In) and FTP Server Passive (FTP 

Passive Traffic-In) rules to allow connections from IP address ranges 192.168.222.11- 

192.168.222.19 and 192.168.100.10-192.168.100.15, as well as the Remote IP 

addresses that are already configured in those rules. The Local IP address is updated 

with the current IP address of the systems management engine. 

UnisysHarden_Rollback.ps1 Script 


It is not recommended that you permanently roll back the most recently applied MCP 

Firmware Environment Policy. However, you might need to temporarily roll back this 

security policy to isolate problems. For those instances, the UnisysHarden_Rollback.ps1 

script is provided. 

Ensure that you reapply the policy using the Rollback.ps1 script after you complete your 

troubleshooting tasks. 

8222 3694–000 4–17


Perform the following steps to initiate the temporary rollback of the MCP Firmware 

Environment Policy on a specific environment: 

1. Log on with the Administrator account. 



3. In the User Account Control prompt, click Yes. 


4. Access the Security subfolder by typing the following command: 

cd ″C:\Unisys\Installation\Firmware\Common\Security″ 

Note: The preceding command input is not case-sensitive. Ensure that either double 

or single quotation marks surround the path name. 

Then, press Enter. 

5. At the PowerShell prompt, type 

.\UnisysHarden_Rollback 

Note: The .\ notation before the script name denotes the current path. Without this 



A dialog box is displayed. 

A list box on the dialog box shows the numbered folders that contain rollback data 

from previous applications of the MCP Firmware Environment Policy. The numbers 

are encoded dates and times, and the explanation of the selected one appears to the 

right. Select the folder containing the data to which you want to return. 

6. Click the Roll Back button to roll back the policy. 

A message is displayed when the roll back action completes successfully. You can find 

a log of the actions of the script actions at 

C:\ProgramData\Unisys\Installation\Hardening_Rollback.txt. 

UnisysHarden.ps1 Script 

To execute the UnisysHarden.ps1 script, perform the following steps on each systems 

management engine, I/O engine, E-mode engine, and JProcessor environment: 




2. Navigate to the following Security subfolder. 

C:\Unisys\Installation\Firmware\Common\Security 

3. At the PowerShell prompt, type 

Run the UnisysHarden.ps1 script using the following syntax: 

.\UnisysHarden.ps1 

4–18 8222 3694–000

Note: The .\ notation before the script name denotes the current path. Without this 


The script runs and returns to the Windows PowerShell prompt when finished. 

Enabling MCP PING Commands through the EVLAN 

Connection 

Inbound Internet Control Message Protocol (ICMP) requests to the host of an 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 host of 

an environment, not even those sent from the MCP host. 

To enable PING commands from the MCP to the I/O engine, create a customized firewall 

rule to allow PING commands through the EVLAN connection, as follows: 

1. Log on to the I/O engine environment using an account with Administrator privileges. 

2. Start the Server Manager by clicking the Server Manager icon on the taskbar. 

The Server Manager window is displayed. 

3. On the left pane, expand the Configuration node, and then expand the Firewall 

with Advanced Security node. 

4. Right-click Inbound Rules and select New Rule. 

The New Inbound Rule wizard starts and the Rule Type screen is displayed. 

5. Select Custom and click Next. 

The Program screen is displayed. 

6. Select All Programs and click Next. 

The Protocol and Ports screen is displayed. 

7. Select ICMPv4 from the Protocol type list. 

The Customize option under Internet Control Message Protocol (ICMP) 

settings becomes available. 

8. Click Customize. 

The Customize ICMP Settings dialog box is displayed. 

9. Select Specific ICMP types and Echo Request, and then click OK to save the 

setting and exit the dialog box. 

10. On the Protocol and Ports screen, click Next. 

The Scope screen is displayed. 

11. For the Local IP addresses, select These IP addresses, click Add, and type the 

host EVLAN IP address, 192.168.16.6. 

12. For the Remote IP addresses, select These IP addresses, click Add, and type the 

MCP host EVLAN IP address, 192.168.16.5. 

13. Click Next. 


8222 3694–000 4–19


The Action screen is displayed. 

14. Select Allow the connection and click Next. 

The Profile screen is displayed. 

15. Click Next. 

The Name screen is displayed. 

16. Type a unique and descriptive name for this firewall rule, for example, “MCPPartition 

Ping (ICMPv4-In).” 

Typing a description for this rule is also recommended for example, “Allow inbound 

Ping request over the EVLAN.” 

17. Click Finish to implement your changes and exit the wizard, or click Back to make 

any changes on previous screens. 

Synchronizing Time 

Time synchronization for the system components that make up the MCP Environment is 

MCP-centric. Time zone and DST settings should never be assigned from the system 

component environments. Time changes for the MCP Environment should be always be 

performed from the MCP Environment (for example, TR ). After the initial load of 

the MCP, the correct time zone and time should be set through the MCP Environment. The 

time zone and time of the system components is automatically synchronized with the 

MCP time. Whenever the time for a system component differs from the MCP 

Environment time by more than ten seconds, the system component time is assigned the 

MCP time. 

Note: After initially setting the MCP time, you should halt the MCP through the MCP 

Console and restart the Operations Server. Once the Operations Server restarts, you can 

load the MCP and all time assignments will be correct. 


This subsection provides the following operating information for VNP network processors 

in the FS6200 Server: 

• Differences from previous MCP systems 

• Configuring MCP Networking 

• Initializing Network Services 

• Verifying Network Services installation and configuration 

• Attributes for EVLAN and MCP Network Adapters 

• Networking commands and inquiries 

• System commands and inquiries 

4–20 8222 3694–000

Differences from Previous MCP Systems 

The VNP Network Processor is managed exclusively using Networking commands and 

inquiries. The commands that are used to manage VNP NPs are not new commands, but 

many users are unfamiliar with them. 

Refer to “Networking Commands and Inquiries” later in this section for details about 

which commands and inquires apply to VNPs and which no longer apply. 

The installation and configuration tasks are separated into two different activities for 

Network Services on FS6200 Servers. Information about installation is discussed in 

Section 8, “Updates.” Information about configuration is covered in Section 3, 

“Customizing the Server Configuration” of this guide. You can perform all Networking 

configuration tasks for Network Services using the Networking Configuration features 

available through the MCP Console. Refer to the MCP Console Help for further 

information. 

Network Services diagnostic information is automatically zipped and placed into the 

dumps directory on the Operations Server for FS6200 Servers. Additional information 

about Network Services diagnostics is included in the Section 9, “Troubleshooting and 

Recovery” of this guide. 

Configuring MCP Networking 

MCP networking configuration is performed by Unisys at the factory before you receive 

your FS6200 Server. However, if you need to make any changes to the networking 

settings to match your environment, you must configure MCP networking through the 

MCP Console. Refer to “Configuring the Network” in Section 3 of this guide and to 

“Configuring MCP Networking” in the MCP Console Help for more information. 

Initializing Network Services 

Perform the following steps using an ODT to initialize Network Services: 

1. From the ODT, initialize the network providers (TCP/IP and BNA, if applicable): 

a. Enter the following commands to take down the current network provider 

versions: 

NW TCPIP - 

NW CNS - 

NW BNA - 

b. Enter the following command to initiate the latest version of CNS: 

NW CNS + 

c. Enter the following command to initiate the latest version of TCP/IP: 

NW TCPIP + 


d. If necessary, enter the following command to initiate the latest version of BNA 

(Heritage Network Services): 

8222 3694–000 4–21


NW BNA + 

2. Issue the following command to list the NPs and their state: 

NW NP 

The expected response should include status similar to the following for each 

configured NP: 

NP 210 NETWORKING VNP, 

Verifying Network Services Installation and Configuration 

Perform the following tests to verify that Network Services is correctly installed. 

Note: The PING operation must be performed from each I/O engine environment. Refer 

to Table 3–4 for default IP address and Line ID values for each I/O engine. 

If the EVLAN IP address was modified during MCP networking configuration, that IP 

address is required for the remainder of this subsection in order for this process to 

complete as expected. 

1. Enter PING 192.168.16.5 from a command prompt on the I/O engine environment 

and verify that you receive a response. 

2. Verify that the FS6200 Server responds. For example 

Pinging 192.168.16.5 with 32 bytes of data: 

Reply from 192.168.16.5: bytes=32 time=10ms TTL=62 

If the server does not respond, continue with the following procedure “If the PING 

Command Is Unsuccessful.” 

If the PING Command Is Unsuccessful 

Note: If the PING command in the preceding subsection was unsuccessful, continue 

with this subsection. All of the assumptions from the preceding subsection apply to this 

one, including the Note. However, if the PING command was successful, no further action 

is required. 

The EVLAN path is not working if a PING command gets the response ″Request timed 

out″ for all four attempts. Verify that MCP Networking is running with the following 

command from an MCP ODT session: 

NW TCPIP STATUS 

The response should be similar to: 

TCPIP IS CURRENTLY NETWORKING(IPV4-ONLY), 

RIP IS CURRENTLY ENABLED/RUNNING, 

TCPIP SECURITY IS CURRENTLY RUNNING, 

SSL IS CURRENTLY TERMINATED, 

IPSEC IS CURRENTLY DISABLED/NOT RUNNING 

4–22 8222 3694–000

If you do not receive this response, check the state of CNS and TCP/IP on the MCP. If 

TCPIP reports that it is currently “Networking,” query the TCPIP IDENTITY of the MCP 

using the following command: 

NW TCPIP IDENTITY 

The first identity in the response should be similar to: 

IPADDRESS 192.168.16.5 / 255.255.255.252 

NP-DEVICE 210, LINEID 0, 

PHYSICAL ADDRESS HEX 08000B002100 

AUTOCONFIGURATION FALSE, 

DUPLICATEADDRESSDETECTIONTRANSMITS 0, 

VISIBLE - , 

If the IP address is different but the NP-DEVICE and LINEID match, then there might be a 

mismatch in the IP address of the MCP Environment and the EVLAN adapter definition in 

the I/O engine. Refer to Table 3–4 for comparison with default IP address and Line ID 

values. 

If the Physical Address is all zeroes (000000000000), the TCPIP connection is closed. 

Determine the reason that the TCP/IP connection is closed using the NW CONN 

command on the Connection Group and the Component Connection associated with the 

appropriate NP based upon Table 3-3. 

If the IP address is correct and the Physical Address is correct, check the configuration of 

the EVLAN adapter in the I/O engine. Issue the command IPCONFIG −ALL from the same 

command prompt you used to enter the PING command. You should see an adapter in the 

resulting list that appears similar to the following: 

Ethernet adapter Local Area Connection 29: 

Connection-specific DNS Suffix . : 

Description . . . . . . . . . . . : Unisys Network Services EVLAN Adapter 

Physical Address. . . . . . . . . : 08-00-0B-06-22-59 

DHCP Enabled. . . . . . . . . . . : No 

Autoconfiguration Enabled . . . . : Yes 

IPv4 Address. . . . . . . . . . . : 192.168.16.6(Preferred) 

Subnet Mask . . . . . . . . . . . : 255.255.255.252 

Default Gateway . . . . . . . . . : 

NetBIOS over Tcpip. . . . . . . . : Enabled 

The IP address should be the IOE address for the EVLAN adapter from Table 3-3, or an 

alternate value assigned by the client within the same subnet as the MCP IP address for 

that line. If it is not, re-configure the IP Address of the EVLAN using the MCP Console 


If the addresses are correct but the PING command still does not work, contact your 

Unisys representative for further assistance. 

MCP Operations Interface Summary 


This topic summarizes the data types, EVLAN and MCP network adapter attributes, and 

MCP commands related to Network Services and ClearPath MCP networking operations. 

8222 3694–000 4–23


Attributes for EVLAN and MCP Network Adapters 

Use the following attributes for configuring network connections for EVLAN and MCP 

network adapters through a VNP. 

• ADAPTERTYPE (ADT) 

This attribute indicates whether the adapter is an EVLAN line or an Ethernet line. 

Values include: 

- EVLAN (the default) 

MIMS/MOMS/MIMSL/MOMSL is set to 4352. Line 0 on the first defined NP must 

be set to EVLAN and must be configured for TCP/IP. 

- ETHERNET, FASTETHERNET or GIGABIT 

• LINEID 

SPEED for the Connection Group reflects the maximum speed of the adapter. 

MIMS/MOMS/MIMSL/MOMSL default to 1496. Unisys recommends modifying 

this value to 1500 or your selection of Jumbo frame size on your Connection 

Group and on the TCPIP Component Connection. 

Network Services uses this attribute to map a LAN connection group to the adapter 

that was selected through the Networking configuration tool. 

The LINEID specified in the I/O engine environment must match the Line ID assigned 

to the adapter in the MCP Console System Editor. 

• Local Address (LA) 

This attribute indicates the local address associated with a particular EVLAN or MCP 

network adapter. 

For EVLAN, LA is a configured 12-character hexadecimal value (there is no physical 

address). 

For MCP network adapters, LA is the physical (MAC) address of the adapter or the 

value assigned through the device driver for the NIC (12 hexadecimal characters). 

For MCP network adapters, a LA value of *DEFAULT or 000000000000 causes the 

software to detect the MAC address of the NIC or the value assigned through the 

device driver. Automatic address detection also occurs if no LA value is specified. 

Command Examples 

Definition of an EVLAN: 

NW ADD CONNGRP CG_ICP_2100 (TYPE = LAN, ICPDEVICEID = 210, 

LINEMODULEID = 1, LINEID = 0, LOCALADDRESS = 08000B002100, 

SPEED = 100000000, MAXINPUTMESSAGESIZELIMIT = 4352, 

MAXOUTPUTMESSAGESIZELIMIT = 4352, MAXINPUTMESSAGESIZE = 4352, 

MAXOUTPUTMESSAGESIZE = 4352) 

Definition of a MCP network adapter (allowing software to detect the MAC address): 

NW ADD CONNGRP CG_ICP_2111 (TYPE = LAN, ADT = GIGABIT, 

ICPDEVICEID = 211, LINEMODULEID = 1, LINEID = 1, 

LOCALADDRESS = *DEFAULT, SPEED = 1000000000) 

4–24 8222 3694–000

Networking Commands and Inquiries 

CNS CLEAR NP 

Use this command to shutdown a specified network processor and all connections that 

are currently attached to it. If the NP is still available following completion of the shutdown 

operation, the NP is reloaded and reinitialized. The host is informed of affected 

connections during the NP reload phase. 

Example 

NW CNS CL NP 211 

CONNECTION 

Use this inquiry to determine the connection status of a connection or connection group. 

Examples 

NW CONN CG_ICP_2100 

NW CONN CG_ICP_2121 

DUMP NP [ | LOCAL [To NP] | 

REBOOT] 

Local Dump 

Use this command to request a dump of data of the network processors (NPs) in a FS6200 


Local dump is the default option for the VNP device type, which can also be obtained 

without using a dump option. 

When the dump is obtained through the NW DUMP command, the firmware dump data 

with the naming convention NetworkDumps_ is placed in a separate folder 

on the I/O engine where the NP is located. The networking dump file is a zip file named 

NetworkDumps.zip, which is located within that dump folder. 

The dump file located on the I/O engine is not readily accessible for collection by the 

operator. Refer to Section 9, “Troubleshooting and Recovery” for more information. 

The Dump NP command initiates action at an I/O processor level. All VNP devices are 

dumped when the Dump NP command is issued for any one of the VNPs in the FS6200 

Server, regardless of the NP number. 

• The data is collected without impacting the operation of the device. The NP remains 

operational during the dump. 

• The data is stored locally on the device. 


8222 3694–000 4–25


Reboot Dump 

Usage 

The Reboot command is interpreted as a LOCAL dump request for VNP devices. No 

reboot is performed. 

Network Processor Default Dump Type Dump Options 

VNP Local Local 

Example 

NW DUMP NP 210 

Do not specify in the command syntax. The data is dumped to the device. 

ESTABLISHCALL BY CONN 

NP 

Use this command to prepare the specified connection or connection group to initiate an 

outgoing call. 

Example 

NW EC BY CONN CG_ICP_2111 

Use this inquiry to find the device numbers of the network processors on your system or 

to see detailed information for a particular network processor. This command also returns 

the state of the NP device. 

An example of an NP Device state is NASCENT. NASCENT indicates the host operating 

system has been asked to initialize the NP. If the device number is zero and the state is 

NASCENT then the greeting with the NP has not yet taken place. 

For information on other states that might be displayed, see the NP Inquiry command in 

the Networking Commands and Inquiries Help. 

Examples 

UTILIZATION 

NW NP 

NW NP 211 

Use this inquiry to view the percentage of processor capacity and memory being used 

(processor utilization and memory utilization). 

For Network Services devices, the reported information is the: 

4–26 8222 3694–000

• Total processor utilization reported by the I/O engine. 

• Amount of physical memory in use within the I/O engine. Note that this is physical 

memory, not total memory, since it does not include virtual memory. 

Since the reported information is based upon platform values, all of the NPs defined on a 

FS6200 Server should report nearly identical processor utilization and memory utilization. 

Example 

NW UTIL 

System Commands and Inquiries 

The following system commands do not apply to FS6200 Server Network Processors. 

• OL CTL 

• OL PORT 

• READY NP 

• SAVE NP 

• UR PORT 

• UR CTL 

• UR NP 

The following system commands do not apply to FS6200 Server Network Processors. 

However, an alternate command is available that provides similar functionality. 

• CLEAR NP 

Refer to the CNS CLEAR NP system command for similar 

functionality. 

• OL NP 

Refer to the Networking command NP for similar functionality. 

• PER NP 

Refer to the Networking command NP for similar functionality. 

Call Home Services 


Call Home provides automatic e-mail alert messages when hardware and software-related 

events occur on the FS6200 Server that requires attention. Call Home e-mail alerts are 

automatically sent to Unisys Support with a copy sent to up to three e-mail addresses that 

you designate. Unisys Support responds accordingly with the appropriate action. 

8222 3694–000 4–27


Call Home requires initial on-site configuration before it is ready for use. Typically, the initial 

configuration of Call Home is performed by Unisys support personnel as part of the 

FS6200 Server system installation. If you need make configuration changes after 

installation, use the MCP Console. Refer to “Managing Call Home Services” in the MCP 

Console Help for more information. 

This subsection addresses tasks you can perform to ensure Call Home services is 

operational. 

Using Maintenance Mode 

When Call Home services is in Operational mode, it is fully operational and sends Call 

Home e-mail alerts to the Customer Support Center and the configured customer e-mail 

addresses. When Call Home services are in Maintenance mode, it does not send Call 

Home e-mail alerts to the Unisys Support Center and the configured customer e-mail 

addresses. Maintenance mode is intended to be used when hardware or software 

maintenance is to be performed on the system and you want to prevent any alerts from 

being sent until the maintenance is completed. Refer to the MCP Console Help for details. 

Testing E-mail Alerts 

You can send a special test e-mail alert message to Unisys Call Home Support that 

automatically returns an e-mail confirmation. This can be used to test the Call Home 

hardware and software configuration on the FS6200 Server and the communications path 

to and from the Unisys Support Center. Refer to the MCP Console Help for details. 

Testing E-mail Heartbeats 

You can manually send a heartbeat e-mail message to Unisys Support Center. This can be 

used to test the Call Home software configuration on the FS6200 Server and the 

communications path to and from the Unisys Support Center. Refer to the MCP Console 

Help for details. 

I/O Services 

Use the system command SC to obtain a general overview of your I/O configuration. The 

following terminology is used in the display output. 

• IOP 

• STORAGESYSTEM 

• CHANNEL (similar to PORT on previous MCP systems) 

• TAP (similar to CTL on previous MCP systems) 

To obtain a detailed view of your I/O configuration, use the SC+ system command. 

The following system commands use the new I/O terminology in displays and command 

input on the FS6200 Server. 

4–28 8222 3694–000

I/O Time 

• ACQUIRE 

• FREE 

• OL 

• RF 

• SC 

• UR 

Refer to the System Commands Reference Manual for further details on the preceding 

commands. 

The FS6200 Server I/O architecture is capable of having multiple I/Os active to a disk at a 

time, resulting in improved throughput and I/O rates on FS6200 Server systems, especially 

when doing a heavy I/O load to VSS2 disks. However, this can cause I/O time reported on 

the FS6200 Server to be larger than on previous MCP systems because it is accumulated 

simultaneously for these multiple active I/Os. Larger I/O time is simply an accounting 

difference that occurs because some of the I/O queue is in the storage system on the 

FS6200 Server. 

Larger I/O time does not mean it takes longer to perform I/O operations. On the contrary, 

reductions might occur, potentially resulting in smaller elapsed times for program 

execution than on other MCP systems of the same performance level. 

As a result, you cannot meaningfully compare I/O time on the FS6200 Server to I/O time 

on previous MCP systems. Larger I/O time is expected (up to 8 times larger) and does not 

indicate a problem. What matters are statistics like overall I/O rates and the elapsed time 

of transactions. These increased I/O times can be seen in the ACCUMIOTIME task 

attribute as well as I/O times recorded in file close and end-of-task SUMLOG records. 

If you use the IOTIME queue attribute or the MAXIOTIME task attribute, you might need 

to increase the values you assign to these attributes. 

Performing Dynamic PCD Updates 

The I/O configuration of the MCP is more flexible on the FS6200 Server than on previous 

MCP systems. You can place new devices, not yet in the PCD, into use by the MCP 

without performing a halt/load operation. 

Perform the following steps to dynamically place devices into use: 


Note: This procedure should not be done while the MCP is executing a heavy I/O 

workload as some steps take longer and could possibly time out. 

8222 3694–000 4–29


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


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


4–32 8222 3694–000

Section 5 

Setting Up and Operating the ePortal 

Specialty Engine 

This section describes the steps to make the ePortal Specialty Engine operational. 

Note: The configuration considerations in this section only apply if you have a product 

license for ClearPath ePortal. 

Configuring ePortal Specialty Engine 

This subsection discusses configuration tasks for the ePortal Specialty Engine. 


follow the instruction in subsection “Setting Up an Optional External ePortal Enterprise 

System” in this section to verify that internal ePortal Specialty Engines are disabled and to 

setup the external ePortal Enterprise system. 

The following subsections describe the necessary steps to make the FS6200 Server 

ePortal-ready. 

Collecting MCP Information 

Before you install and configure MCP software, collect the following information. 

Required Information Value 

Privileged usercode for the MCP software 

Interim Correction (IC) installation 

Password for the privileged usercode 

Creating MCP Usercodes 

For the ePortal Specialty Engine to access the MCP Environment, you must create a 

special MCP usercode with the GROUPCODE attribute EPORTALCONTROLLER or 

EPORTALSTUDIO. Only MCP usercodes with the GROUPCODE attribute value 

EPORTALCONTROLLER or EPORTALSTUDIO can access the preconfigured 

APPLIANCES share of the MCP. The following topics describe how to create MCP 

usercodes. 

8222 3694–000 5–1

Setting Up and Operating the ePortal Specialty Engine 

Creating a Usercode with the GROUPCODE Attribute 

EPORTALCONTROLLER 

For a FS6200 Server, a special unprivileged usercode, called EPORTAL, with the 

GROUPCODE attribute of EPORTALCONTROLLER is preconfigured in the system. The 

EPORTALCONTROLLER attribute provides full access to the APPLIANCES share. 

ePortal Manager uses this usercode to obtain information about the configuration, 

application, and software updates from the MCP Environment. 

You should change the password of this usercode in both MCP Environment and ePortal 

environment when you setup the system for the first time. For the ePortal environment, 

you can change the MCP usercode/password by selecting the backend server name from 

the Back-End Servers page of the ePortal Manager website. 

In case this special usercode was removed from the MCP Environment, you can recreate 

this usercode by performing the step in the following example procedure. 

Client Access Services limits the length of this password to 14 characters. 

Example 

To create a usercode called EPORTAL with the GROUPCODE attribute 

EPORTALCONTROLLER, do the following on the Operations Server using the ODT in 

CANDE: 

1. Type and transmit Run *SYSTEM/MAKEUSER. 

2. Type and transmit $SET LIST IGNORE. 

3. Type and transmit +USER EPORTAL; . 

4. Type and transmit USER EPORTAL MINPW=1 MAXPW=1; . 

5. Type and transmit USER EPORTAL PASSWORD=″″;. 

6. Type and transmit USER EPORTAL GROUPCODE=EPORTALCONTROLLER;. 

7. Type and transmit Bye; . 

Creating a Usercode with the GROUPCODE Attribute 

EPORTALSTUDIO 

Portal Developer requires a usercode with the GROUPCODE attribute or 

SUPPLEMENTARYGRPS attribute EPORTALSTUDIO. This usercode enables an ePortal 

application developer to stage applications to the MCP server APPLIANCES share. 

To create this usercode, do one of the following: 

• If the application developer usercode is not already using a GROUPCODE attribute, 

add EPORTALSTUDIO to the GROUPCODE attribute in the USERDATAFILE. 

• If the application developer usercode is already using a GROUPCODE attribute, add 

EPORTALSTUDIO to the SUPPLEMENTARYGRPS attribute in the USERDATAFILE. 

5–2 8222 3694–000

Ensuring That the Necessary Disk Space Is Available 

ePortal requires the following MCP disk space: 

• In the APPLIANCES share: 1GB 

• The Client Access Services software automatically creates this share. 

• The ePortal installation software creates permanent directories and moves the ePortal 

run-time environment files to this share. ePortal Manager uses this share to obtain 

configuration, application, and software updates from the MCP system. 

Note: To relocate the MCP APPLIANCES share, see “Relocating the MCP 

APPLIANCES Share.” 

• In the INSTALLS share: 60 MB 

• The ePortal Developer plug-in requires disk space in this share. 

Relocating the MCP APPLIANCES Share 

The MCP APPLIANCES share contains the ePortal run-time environment files. The default 

family for this share is the Client Access Services family (NXSFAMILY). If you want this 

share in another family, use the Administration Center to specify that family in the 

APPLIANCES family definition. 

The APPLIANCES share is created in a permanent directory space. Do not move this share 

outside a permanent directory space. The first node of a permanent directory space 

always starts with *DIR. 

Installing ePortal Interim Corrections (ICs) 

To install the ePortal IC, follow the instructions in ″Installing the ePortal Interim Correction 

(IC)” in Section 8 of this guide. 

Configuring MCP Network Connection 


ePortal Specialty Engine uses a private internal network connection to communicate with 

the MCP environment. By default, ISM-0 ePortal is configured to use 192.168.223.250 as 

its MCP backend server connection and ISM-1 ePortal is configured to use 

192.168.224.250 as the MCP backend server connection. 

The following lists the default recommended TCPIP configuration setting in the MCP. 

• NP210 Line 3: 192.168.223.250 (ISM-0 ePortal) 

• NP220 Line 3: 192.168.224.250 (ISM-1 ePortal) 

The following lists an example of the network configuration files for MCP. 

8222 3694–000 5–3


CNS Initialization File 

The following example shows the addition of a new connection group for NP210 Line 3 for 

ISM-0: 

NW ADD CONNECTIONGROUP CG_ICP_2103 

( TYPE = LAN 

,ICPDEVICEID = 210 

,LINEMODULEID = 1 

,LINEID = 3 

,LOCALADDRESS = *DEFAULT 

, ADAPTERTYPE = GIGABIT 

); 

The following example shows a second connection group for NP220 Line 3 which must be 

configured for ISM-1: 

NW ADD CONNECTIONGROUP CG_ICP_2203 

( TYPE = LAN, ICPDEVICEID = 220 

, LINEMODULEID = 1 

, LINEID = 3 

, LOCALADDRESS = *DEFAULT 

, ADAPTERTYPE = GIGABIT 

); 

TCPIP Initialization File 

The following example shows the addition of a connection and IP address for NP210 Line 

3: 

NW TCPIP TCPIPIDENTITY ADD NP 210 LINE 3 

192.168.223.250/255.255.255.0 

VISIBLE – 

; 

NW ADD CONNECTION TO CG_ICP_2103 

2103_TCPIP_2103 

% Connection Information 

( NETWORKLAYERENTITY = IP 

, REMOTEADDRESS = 000000000000 

, CLASS = ETHIP 

) 

; 

The following example shows the second connection and IP address for NP220 Line 3 

which must be configured for ISM-1: 

NW TCPIP TCPIPIDENTITY ADD NP 220 LINE 3 

192.168.224.250/255.255.255.0 

VISIBLE – 

; 

NW ADD CONNECTION TO CG_ICP_2203 

2203_TCPIP_2203 


( NETWORKLAYERENTITY = IP 

5–4 8222 3694–000

; 

, REMOTEADDRESS = 000000000000 

, CLASS = ETHIP 

) 

Verifying the ClearPath ePortal Port That Custom Connect 

Facility (CCF) Automatically Creates 

An MCP T27 data source project accesses an MCP application by using a CCF port to 

connect to an MCP server. 

CCF software installation automatically configures the following for ClearPath ePortal: 

• Port 37654 

• Related services 


Configuring Separate CCF Ports for Different Applications 

In the CCF configuration file, you might need to configure separate ports for different 

applications if your application requires different CCF settings. 

The following examples of sections in the CCF configuration file show the default CCF 

setting for ePortal: 

[TCPIPPCM] section: 

ADD PORT EPORTALPORT37654 

CHECKINTERVAL = 5, 

FRAMING = STANDARD, 

MINOFFER = 9, 

MAXOFFER = 9, 

MAXOUTPUT = 4000, 

SERVICE = EPORTALTERMINAL, 

SOCKET = 37654, 

STATIONNAME = EPORTAL/#, 

TRANSPORT = TCPIP; 

ENABLE PORT EPORTALPORT37654; % enabled by default 

[TERMPCM] section; 

ADD SERVICE EPORTALTERMINAL 

ACVT = LSCANDE, 

CHARSET = ASCII, 

CCHAR = ?, 

DEFAULTVT = LSCANDE, 

LINEWIDTH = 80, 

LOGOFF DISCONNECT = FALSE, 

LOGONREQUIRED = TRUE, 

MYUSE = IO, 

MAXINPUT = 1920, 

MAXOUTPUT = 2200, 

PAGELENGTH = 24, 

SCROLLING = FALSE, 

SCREEN = TRUE, 

SERVICE = EPORTALCUCI; 

ENABLE SERVICE EPORTALTERMINAL; 

8222 3694–000 5–5


[CUCIPCM] section; 

ADD SERVICE EPORTALCUCI 

DYNAMIC = TRUE, 

STATIONNAME = EPORTAL/#; 

ENABLE SERVICE EPORTALCUCI; 

Validating the Connector Protocol-Specific Handler (Connector 

PSH) Installation and Configuration 

An MCP COBOL data source project accesses an MCP application by using the Connector 

protocol-specific handler (Connector PSH) to connect to an MCP server system. 

Connector PSH is installed with Transaction Server software. By default, MCP COBOL 

data source projects use port 7952. 

To verify that Connector PSH is installed and configured on the MCP Environment, enter 

the following command at the ODT or from a MARC window: 

NA CONNPSH CONFIGURE 

A response similar to the following indicates that the Connector PSH is installed and 

enabled: 

PSH Configuration: Current endpoint: 7952 

Offers: 3 

Auto logon: Enabled 

Clear text passwords: Enabled 

Close wait timeout: 60 seconds 

Dynamic stations: Enabled 

Blocked timeout: 10 minutes 

Dialog check interval: 5 minutes 

Target connections: 0 

Maximum connections: 65535 

If Connector PSH is installed but disabled, enter the following command at the ODT or 

from a MARC window to start Connector PSH: 

NA CONNPSH+ 

If Connector PSH is not installed, see the Transaction Server for ClearPath MCP 

Operations Guide for installation instructions. 

You need to modify the Connector PSH configuration using one of the following 

commands to enable it to work correctly with the ePortal MCP COBOL data source 

project: 

• NA CONNPSH CONFIGURE CLEARTEXTPW+ 

This command is required if ePortal MCP COBOL data source project uses 

Connect_basic option. 

• NA CONNPSH CONFIGURE AUTOLOGON+ 

This command is required if ePortal MCP COBOL data source project uses 

Connect_autologon option. 

• NA CONNPSH CONFIGURE OFFERS = 

5–6 8222 3694–000

This command is optional. By default, it is set to 3. You might need to increase it to 

higher number if ePortal clients receive a port open error messags similar to the 

following: 

NW RESET SENT DUE TO PACKET RESEND LIMIT EXCEEDED / 

NW LOCAL IP ADDRESS = 192.168.223.250, LOCAL PORT = 7952) 

Configuring a Named Pipe 

ePortal includes a utility program, named SYSTEM/EPORTAL/NAMEDPIPE, that runs on 

the MCP Environment. This program uses the named pipe EPORTALPIPE to communicate 

with the ClearPath ePortal controller in order to support E-mail Notification. If the 

EPORTALPIPE named pipe is not already defined in the Client Access Services 

configuration file, define the named pipe with the attributes in the following example: 

SHARE EPORTALPIPE 

(TYPE = PIPE 

,COMMENT = ″CLEARPATH EPORTAL NAMED PIPE INTERFACE″ 

,ACCESS = ALL 

,APPNAME = ″*SYSTEM/EPORTAL/NAMEDPIPE ON DISK″ 

,APPORTINTNAME = ″EPORTALPORT″ 

,PORTMAXRECSIZE = 15000 

); 

In the preceding example, the family name of the APPNAME attribute is DISK. You might 

need to modify this family name to point to the correct family on your MCP system. 

Configuring the MCP EMAIL Utility 


The Portal Alert Notifications feature requires the MCP EMAIL utility to send an e-mail 

notification when an error occurs. The MCP EMAIL utility is a part of the MCP release, but 

is not configured by default. 

You need to set up the MCP EMAIL utility on the MCP and configure the Alert Notifications 

feature on the ePortal Specialty Engine. To configure Alert Notifications, specify the e-mail 

addresses to which ePortal sends the notifications. For instructions on how to configure 

the MCP EMAIL utility, see the System Software Utilities Operations Reference Manual. 

Performing Initial Configuration Tasks in ePortal Manager 

To complete configuration of the ePortal Specialty Engine, perform the following from the 

Component View tab of the MCP Console: 

Note: The FS6200 Server has two I/O and Specialty Engine Modules. This procedure 

must be performed for both the active and standby ePortal Specialty Engine running in 

ISM-0 and ISM-1. 

8222 3694–000 5–7


1. Perform the following actions to start ePortal Manager. 

a. From the Component View tab, expand the components ISM and s-Par ® , 

right-click ePortal and then select Launch ePortal Browser. 

b. In the log-on dialog box, type portaladmin for the user, kodiak for the 

password, and click OK. 

ePortal Manager starts and the home page is displayed. 

Note: If you cannot access the ePortal Manager website, see “Cannot Access 

the ePortal Manager Web Site” in Section 7 of this guide. 

2. Perform the following actions to set the correct time zone: 

a. On the Management menu on the left side of the page, click Controller. 

b. At the bottom of the controller page, under Configuration, click Set Local 

Date and Time 

c. Set the time zone. 

d. Click Apply. 

3. Perform the following actions to view the readme file: 

a. On the Management menu on the left side of the page, click About. 

b. At the bottom of the dialog box, click View README. 

c. Close the About dialog box. 

4. Perform the following actions to configure the back-end server (MCP) name. 

a. On the Management menu on the left side of the page, click Back-End 

Servers. 

b. On the Back-End Server Definitions page, select the default primary back-end 

server name CPMCP1. 

c. Click Modify. 

d. In the Name box, type the MCP server name and click OK. 

5. Perform the following actions to configure the usercode and password of the MCP 

system for accessing the APPLIANCES share. 

a. On the Management menu on the left side of the page, click Back-End 

Servers. 

b. On the Back-End Server Definitions page, click the primary back-end server 

name. 

c. Under Configuration, click Change Usercode and Password. 

d. In the User Code box, type the usercode that you created for ePortal in the 

primary back-end server (MCP system). This user code has to be set with the 

EPORTALCONTROLLER GROUPCODE attribute. 

e. In the Password and Confirm Password boxes, type the password. 

f. Click Apply. 

5–8 8222 3694–000

6. Perform the following actions to change the password for accessing the ePortal 

Manager. 


b. At the bottom of the controller page, under Configuration, click Change 

Password. 

c. In the Old Password box, type kodiak. 

d. In the New Password and Confirm Password boxes, type the new 

password. 

e. Click Apply. 

7. Perform the following actions to verify that all ePortal Personality Module 

environments are in the proper state. 

a. On the Management menu on the left side of the page, click Personality 

Modules. 

b. Verify that all of 4 Personality Modules are in Ready/Unassigned state. 

Note: If you see any ePortal Personality Modules not in Ready/Unassigned state, 

refer to Section 7, “Troubleshooting and Recovery” of this guide for more 

information. 

8. Perform the following actions to synchronize to the latest ePortal system software. 


b. Under Configuration, click Manage System Software. 

c. Under Operations, click on Synchronize System Software. 

d. Click Yes when asked to confirm. 


Note: Wait several minutes, navigate back to Manage System Software page, 

and verify that “All software is synchronized on this controller.” 

9. Perform the following actions to backup the current configuration: 

a. On the Management menu, on the left side of the page, click Controller. 

b. Under Configuration, click Backup Configuration. 

c. Under Operations, click Backup Current Configuration. 

d. Enter the backup parameters and click Backup. 

10. In the upper-right corner, click Log Off, and then click Yes to exit ePortal Manager. 

Setting Up an Optional External ePortal Enterprise System 

When an optional external ePortal Enterprise system is attached to the FS6200 Server, 

none of the internal ePortal Specialty Engines within the ISMs should be running. 

Perform the following steps to verify that the internal ePortal Specialty Engines are 

disabled before setting up the ePortal Enterprise system. 

8222 3694–000 5–9


Note: If the internal ePortal Specialty Engines are not disabled, the external ePortal 

Enterprise System would not function correctly. 

1. From the Platform Console, verify that the initial state of all ePortal environments is 

set to the Inactive. Setting the ePortal environments to Inactive state, ensures that 

none of the ePortal environments are running in the ISM. 

2. From the MCP Console, verify that ePortal is not visible from the ISM component 

and the s-Par ® node in the Component View tab. 

3. From the MCP network configuration files, verify that the default internal ePortal 

network connections used by the internal ePortal Specialty Engines are not defined in 

the CNS and TCPIP initialization files. By default, NP 210/Line 3 (192.168.223.250) and 

NP 220/Line 3 (192.168.224.250) are defined in the default TCPIP initialization file. 

Refer to the “Preparing the MCP for ClearPath ePortal” in the ClearPath ePortal Enterprise 

Managed Platform Implementation and Operations Guide for instructions on making the 

FS6200 Server ePortal-ready. 

When setting up the ePortal Enterprise system, use the following information as additional 

guidelines: 

• Two external NIC ports on the FS6200 Server are required to connect the external 

ePortal Enterprise system. It is recommended that the primary ePortal connection be 

configured as 192.168.223.250 and the redundant connection as 192.168.223.249 in 

the MCP network. 

The FS6200 Server has two ISMs and the redundant connection 192.168.223.249 

should be configured on a different ISM than the ISM that contains the primary 

connection 192.168.223.250. For example, the primary connection 192.168.223.250 

can be defined in the ISM-0 and the redundant connection 192.168.223.249 can be 

defined in the ISM-1. This ensures that if ISM-0 fails, the IP address 192.168.223.250 

is moved to the redundant connection in ISM-1 transparently and both 

192.168.223.249 and 192.168.223.250 go through the ISM-1 connection. 

• Both the primary and redundant management port (Port 21) of the ePortal Enterprise 

system internal switches should be connected to the secure access device of the 


ePortal Specialty Engine Operational Considerations 

This subsection discusses operational considerations for the ePortal Specialty Engine. 


refer to the ClearPath ePortal Enterprise Managed Platform Implementation and 

Operations Guide for operational instructions. 

Starting ePortal Manager 

Perform the following steps from the MCP Console to start ePortal Manager. 

5–10 8222 3694–000

1. From the Component View tab, expand the components ISM and s-Par ® , right 

click ePortal, and then select Launch ePortal Browser. 

2. In the logon dialog box, type the usercode and password for ePortal Manager and click 

OK. 

Notes: 

The ePortal Manager website is launched and the home page is displayed. 

• If you cannot access the ePortal Manager website, see “Cannot Access the ePortal 

Manager Web Site” in Section 7 of this guide. 

• The FS6200 Server has two I/O and Specialty Engine Modules, you can find out which 

is the active ePortal system by checking the Host Name property when you click the 

ePortal. The Host Name property of the active ePortal system has –Active as a suffix. 

The Host Name property of the stanby ePortal system has –Standby as a suffix. 

ePortal Personality Module Naming 

It is possible that the ePortal PM name in ePortal Manager website might not correspond 

to the ePortal PM Environment name in Platform Console. For example, if the ePortal 

Manager website lists the PM-1 as Partition Number 3 in the Personality Modules detail 

page, the corresponding ePortal PM Environment name in the Platform Console is ePortal 

PM 3 Environment. Therefore, if you need to restart the PM-1 from the Platform Console, 

you must restart the ePortal PM 3 Environment from the Platform Console. 

Developing an ePortal Application 


Refer to the “Developing a ClearPath ePortal Business Application” section of the 

ClearPath ePortal Business Implementation and Operations Guide for instructions on 

developing an ePortal application. 

ePortal Specialty Engine Operational Considerations for a 

System with Two ISMs 

This subsection discusses operational considerations for the ePortal Specialty Engine for a 

system configured with two I/O and Specialty Engine Modules (ISMs). 

When a system is configured with two ISMs, an independent ePortal system is running in 

each ISM. However, only one ePortal system is considered as an active ePortal system. 

The second ePortal system is considered as a standby ePortal system. 

Note: Only the active ePortal system should be connected to the front-end public 

network. Connecting both active and standby ePortal Specialty Engines to the public 

network at a same time causes problems accessing the ePortal applications and would 

cause unpredictable results. 

As a result, only virtual servers running on the active ePortal system can service the 

ePortal application requests from ePortal clients. 

8222 3694–000 5–11


By default, the ISM-0 ePortal Specialty Engine is configured as the active ePortal system 

and the ISM-1 ePortal Specialty Engine is configured as the standby ePortal system which 

is used during a failover only when ISM-0 fails or the ePortal Specialty Engine of ISM-0 

fails. 

The active and standby ePortal system can be determined by checking the Name field of 

the controller from the ePortal Manager website. The active ePortal system should have 

the -Active suffix (for example, EP0-Active or EP1-Active) in the Controller Name 

field and the standby ePortal system should have the -Standby suffix (for example, 

EP0-Standby or EP1-Standby) in the Controller Name field. 

You can also determine the active ePortal system from the Component View tab of the 

MCP Console by checking the Host Name property when you select ePortal under the 

components ISM and s-Par ® . As mentioned previously, the active ePortal system has the 

suffix -Active as a suffix in the Host Name field. 

The ePortal Manager is configured with the following default setting: 

• ISM-0 ePortal Manager is configured to use IP address 192.168.222.190 and the 

name EP0-Active. The MCP backend server IP address is set to 

192.168.223.250. 

• ISM-1 ePortal Manager is configured to use IP address 192.168.222.191 and the 

name EP1-Standby. The MCP backend server IP address is set to 

192.168.224.250. 

Whenever configuration changes (for example, deploying a new application, modifying 

virtual server or personality module, modifying controller or back-end server configuration, 

and so on) are made on the active ePortal system, you must create a new backup. During 

the failover, the standby ePortal system uses the latest backup on the active ePortal 

system to restore the ePortal configuration. If the backup is not up to the date on the 

active ePortal system, you lose any changes since the last backup when a failover occurs 

from the active ePortal system to the standby ePortal system. 

ePortal generates the following warning alert on the Management website if the 

configuration is changed. Also, a new backup should be generated: 

Need to generate a new backup 

In addition, the MCP back-end server usercode and password must be configured the 

same on both the active and standby ePortal systems for a successful failover 

ISM-0 ePortal to ISM-1 ePortal Failover Transition 

In the event of an ISM-0 failure or ePortal Specialty Engine of ISM-0 failure while the 

ePortal Specialty Engine of ISM-0 is an active ePortal system, perform the following steps 

to recover the ePortal environment into the ePortal Specialty Engine of ISM-1: 

5–12 8222 3694–000


1. Move both ePortal public LAN network cables from ISM-0 to ISM-1. 

Refer to the following figure for the LAN port locations. 

2. Copy the latest ePortal backup files from ePortal IP segment 223 of ISM-0 to ePortal 

IP segment 224 of ISM-1 by performing the following actions from a workstation 

that has access to the APPLIANCES share on the MCP system: 

a. Map a drive to the APPLIANCES directory share on the MCP system using an 

MCP usercode with the EPORTALCONTROLLER GROUPCODE attribute. 

b. Check the APPLIANCES share for a folder named Backups\223 and 

Backups\224. 

c. If there is no folder named Backups\224 in the APPLIANCES share, create a 

new folder under the Backups folder in the APPLIANCES share and name it 

224. 

d. Copy the latest backup files from the Backups\223 folder to the 

Backups\224 folder of the APPLIANCES share. 

The backup files are in the format of Backup_-.zip and 

Backup_-.xml. 

Note: You need to copy both .zip and .xml files. 

8222 3694–000 5–13


3. Modify the host name of the ePortal Manager of ISM-1 from EP1-Standby to 

EP1-Active by performing the following steps: 

a. From the Component View tab of the MCP Console, locate the ePortal 

Manager for ISM-1 by clicking ePortal under ISM and s-Par ® and verify that the 

host name is EP1–Standby (if the host name is EP0–Active, click ePortal 

under the other ISM and s-Par ® ). Then, launch the ISM-1 ePortal Manager 

website by right-clicking the ePortal and selecting Launch ePortal Browser. 

b. Log on with the ePortal user account and password. Both the user and password 

are case-sensitive. 

c. Click Controller in the list of links on the left side of the page. 

d. Click Modify, change the name from EP1-Standby to EP1-Active, and then 

click OK. 

e. Restart the ePortal Manager by clicking the Restart button under Operations 

from ePortal Manager Web site’s Controller menu. 

4. After the ePortal Manager of ISM-1 restarts, restore the latest ePortal backup into the 

ePortal Specialty Engine of ISM-1 by performing the following steps: 


Manager for ISM-1 by clicking ePortal under ISM and s-Par ® and verifying that 

the host name is EP1–Active (if the host name is EP0–Active, click ePortal 





c. Click on Controller in the list of links on the left side of the page. 

d. Under Configuration, click Backup Configuration. 

You should see the latest backup file you copied from the ePortal of ISM-0. 

e. Click Restore a System Backup and follow the wizard to restore the latest 

ePortal configuration. 

Note: Refer to the section “Restoring ePortal” later in this guide for more 

information on the restore operation. 

5. After the ePortal restoration successfully completes, verify that the ePortal 

configuration is good and you can access the deployed applications. 

6. Perform the backup operation from the ePortal Manager. 

7. The ePortal Specialty Engine of ISM-1 is now the active ePortal system. 

8. Perform the steps described in the topic “Assigning ePortal Specialty Engine ISM-0 as 

a Standby ePortal System” later in this guide. 

Note: In case of an ISM-0 failure or ePortal Specialty Engine of ISM-0 failure while the 

ePortal Specialty Engine of ISM-0 is a standby ePortal system, contact Unisys support to 

recover from the failed component. 

5–14 8222 3694–000

Assigning ePortal Specialty Engine ISM-0 as a Standby ePortal 

System 

After ISM-0 or the ePortal Specialty Engine of ISM-0 is recovered from the failure while the 

ePortal Specialty Engine of ISM-0 was an active ePortal system and the ePortal Specialty 

Engine of ISM-1 took over as an active ePortal system, you must perform the following 

steps to assign the ePortal Specialty Engine of ISM-0 as a standby ePortal system. 

To avoid any confusion later in determining which is the active ePortal system, you should 

remove all virtual servers configuration from ISM-0 ePortal and modify the host name of 

ISM-0 ePortal Manager from EP0-Active to EP0-Standby by performing the following 

steps: 

1. From the Component View tab of the MCP Console, locate the ePortal Manager for 

ISM-0 by clicking ePortal under ISM and s-Par ® , and verify that the host name is 

EP0–Active (if the host name is EP1–Active, click ePortal under the other ISM 

and s-Par ® ). Then, launch the ISM-0 ePortal Manager website by right-clicking the 

ePortal and selecting Launch ePortal Browser. 

2. Log on with the ePortal user account and password. Both the user and password are 

case-sensitive. 

3. Remove all virtual server configurations from ePortal Manager website by following 

these steps: 

a. Click Virtual Servers on the list of links on the left side of the page. 

b. Click the virtual server name. 


c. Click Take Offline & Terminate Clients. 

d. After all members of the virtual server are in Ready/Offline state, click Manage 

Members. 

e. Select the check boxes for all PMs and then click the Remove button. 

f. Repeat the preceding steps for all virtual servers. 

Note: By removing the virtual servers, all of the PMs in the standby ePortal system 

will be in Ready/Unassigned state and you cannot deploy an application to the standby 

ePortal system 

4. Click Controller in the list of links on the left side of the page. 

5. Click Modify, change the name from EP0-Active to EP0-Standby, and then click 

OK. 

6. Restart the ePortal Manager by clicking the Restart button under Operations from 

ePortal Manager Web site’s Controller menu. 

Note: Once the transition is complete, the Component View tab of the MCP Console 

should reflect the host name change in the ePortal under the components ISM and s-Par ® 

and you should be launching the new active ePortal Manager to manage the ePortal 

system. 

8222 3694–000 5–15


ISM-1 ePortal to ISM-0 ePortal Failover Transition 

In the event of an ISM-1 failure or ePortal Specialty Engine of ISM-1 failure while the 

ePortal Specialty Engine of ISM-1 is an active ePortal system, perform the following steps 

to recover the ePortal environment into the ePortal Specialty Engine of ISM-0: 

1. Move both ePortal public LAN network cables from ISM-1 to ISM-0. 

Refer to the following figure for the LAN port locations. 

2. Copy the latest ePortal backup files from ePortal IP segment 224 of ISM-1 to ePortal 

IP segment 223 of ISM-0 by performing the following actions from a workstation 

that has access to the APPLIANCES share on the MCP system: 

a. Map a drive to the APPLIANCES directory share on the MCP system using an 

MCP usercode with the EPORTALCONTROLLER GROUPCODE attribute. 

b. Check the APPLIANCES share for a folder named Backups\223 and 

Backups\224. 

c. If there is no folder named Backups\223 in the APPLIANCES share, create a 

new folder under the Backups folder in the APPLIANCES share and name it 

223. 

d. Copy the latest backup files from the Backups\224 folder to the 

Backups\223 folder of APPLIANCES share. 

The backup files are in the format of Backup_-.zip and 

Backup_-.xml. 

Note: You need to copy both .zip and .xml files. 

5–16 8222 3694–000


3. Modify the host name of the ePortal Manager of ISM-0 from EP0-Standby to 

EP0-Active by performing the following steps: 



host name is EP0–Standby (if the host name is EP1–Active, click ePortal 





c. Click Controller in the list of links on the left side of the page. 

d. Click Modify, change the name from EP0-Standby to EP0-Active, and then 

click OK. 

e. Restart the ePortal Manager by clicking the Restart button under Operations 

from ePortal Manager Web site’s Controller menu. 

4. After the ePortal Manager of ISM-0 restarts, restore the latest ePortal backup into the 

ePortal Specialty Engine of ISM-0 by performing the following steps: 



host name is EP0–Active (if the host name is EP1–Active, click ePortal under 

the other ISM and s-Par ® ). Then, launch the ISM-0 ePortal Manager website by 

right-clicking the ePortal and selecting Launch ePortal Browser. 



c. Click on Controller in the list of links on the left side of the page. 

d. Under Configuration, click Backup Configuration. 

You should see the latest backup file you copied from the ePortal of ISM-1. 

e. Click Restore a System Backup and follow the wizard to restore the latest 

ePortal configuration. 

Note: Refer to the section “Restoring ePortal” later in this guide for more 

information on the restore operation. 

5. After the ePortal restoration successfully completes, verify that the ePortal 

configuration is good and you can access the deployed applications. 

6. Perform the backup operation from the ePortal Manager. 

7. The ePortal Specialty Engine of ISM-0 is now the active ePortal system. 

8. Perform the steps described in the following subsection “Assigning ePortal Specialty 

Engine ISM-1 as a Standby ePortal System.” 

Note: In case of an ISM-1 failure or ePortal Specialty Engine of ISM-1 failure while the 

ePortal Specialty Engine of ISM-1 is a standby ePortal system, contact Unisys support to 

recover from the failed component. 

8222 3694–000 5–17


Assigning ePortal Specialty Engine ISM-1 as a Standby ePortal 

System 

After ISM-1 or the ePortal Specialty Engine of ISM-1 is recovered from the failure while the 

ePortal Specialty Engine of ISM-1 was an active ePortal system and the ePortal Specialty 

Engine of ISM-0 took over as an active ePortal system, you must perform the following 

steps to assign the ePortal Specialty Engine of ISM-1 as a standby ePortal system: 

To avoid any confusion later in determining which is the active ePortal system, you should 

remove all virtual servers configuration from ISM-1 ePortal and modify the host name of 

ISM-1 ePortal Manager from EP1-Active to EP1-Standby by performing the following 

steps: 

1. From the Component View tab of the MCP Console, locate the ePortal Manager for 

ISM-1 by clicking ePortal under ISM and s-Par ® and verify that the host name is 

EP1–Active (if the host name is EP0–Active, click ePortal under the other ISM 

and s-Par ® ). Then, launch the ISM-1 ePortal Manager website by right-clicking the 

ePortal and selecting Launch ePortal Browser. 

2. Log on with the ePortal user account and password. Both the user and password are 

case-sensitive. 

3. Remove all virtual server configurations from ePortal Manager website by following 

these steps: 

a. Click Virtual Servers on the list of links on the left side of the page. 

b. Click the virtual server name. 

c. Click Take Offline & Terminate Clients. 

d. After all members of the virtual server are in Ready/Offline state, click Manage 

Members. 

e. Select the check boxes for all PMs and then click the Remove button. 

f. Repeat the preceding steps for all virtual servers. 

Note: By removing the virtual servers, all of the PMs in the standby ePortal system 

will be in Ready/Unassigned state and you cannot deploy an application to the standby 


4. Click Controller in the list of links on the left side of the page. 

5. Click Modify, change the name from EP1-Active to EP1-Standby, and then click 

OK. 

6. Restart the ePortal Manager by clicking the Restart button under Operations from 

ePortal Manager Web site’s Controller menu. 

Note: Once the transition is complete, the Component View tab of the MCP Console 

should reflect the host name change in the ePortal under ISM and then s-Par ® , and you 

should be launching the new active ePortal Manager to manage the ePortal system. 

5–18 8222 3694–000

Restoring ePortal 

The following actions occur when a standby ePortal system performs an ePortal restore 

operation during a transition to an active ePortal system: 

• Checks and installs the latest ClearPath ePortal IC 

Note: Keeping the IC level on the standby ePortal system up-to-date enables 

restoration process to skip this step and speed up the transition. 

• Rebuilds the database based on the latest backup generated on the previous active 


• Restores virtual servers and applications 


• Discovers and assigns personality modules to the virtual servers 

During the restoration process, a restore status page is displayed on the ePortal 

Management website. During the restoration, you cannot access any other section of the 

site since all functions are suspended until the restoration is completed. Due to browser 

caching, you might have to display a new browser window to see the restore status page. 

Also during restoration, the ePortal Controller restarts several times as required and the 

browser session might timeout during restart. This might require the refresh of the 

browser to see the latest status. Once all the steps are completed successfully, you can 

navigate back to the main section of the ePortal Management website. 

In an ideal situation, the standby ePortal system should have the same number of working 

PMs as the active ePortal system. If not, the restoration process allocates PMs to the 

virtual server based on the following rules: 

• Each virtual server contains at least one PM. If the virtual server number is greater 

than PM number, the virtual server that is online is restored first. A critical alert is 

raised before and after the restoration to remind you of the inadequate number of 

working PMs and possibly interrupted applications. 

• Every time a new PM is discovered, it is added to the virtual server most in need. For 

example, assume the ePortal system has two virtual servers: VS1 and VS2. VS1 

should have two PMs and VS2 should have two. After the first round of PM allocation, 

both virtual servers have one PM. When the third PM is discovered, it is assigned to 

VS2. 

During the restoration, the assignment of PM names to a virtual server might change. For 

example, assume the active ePortal system had PM-1 and PM-2 assigned to VS1 and 

PM-3 and PM-4 assigned to VS2. After the restoration, VS1 might contain PM-1 and PM-3 

and VS2 might contain PM2 and PM-4. Also, the dedicated IP address of the PM can be 

shifted amongst the PMs. 

Certain failure during the restoration process could put the whole ePortal system in an 

unstable state. For example, any failure during a rebuild of the database would make the 

ePortal Management website not accessible and the only way to recover from this type of 

failure is to reinstall the controller. Other failures are relatively minor and are recoverable. 

For example, if the controller failed to install the latest ClearPath ePortal IC, the IC can be 

installed manually after the restoration is finished. 

8222 3694–000 5–19


Troubleshooting 

During the restoration process certain failures might occur, some of which are 

recoverable. The following table lists actions you can take against certain symptoms. 

Symptom Action Expected Result 

Once restore started, the 

Management website did not 

navigate to the restore status 

page. 

Restore status page stuck on 

one step for an unusually long 

time. 

Refresh the browser or close 

the current browser and open 

a new browser window. Then, 

type the URL of the default 

controller. 

The restore status page 

should appear. 

Refresh the browser. The status page should 

update and eventually finish. 

If the browser is stuck at one 

step, there might be a serious 

problem. Consider re-imaging 

the controller. 

5–20 8222 3694–000

Section 6 

Setting Up and Operating the 


This section describes the steps to make the JProcessor Specialty Engine operational. 

Configuring JProcessor Specialty Engine 

Refer to the ClearPath Virtual Machine for the Java 7.0 Platform on ClearPath MCP 

Installation and Administration Guide for information related to JProcessor Specialty 

Engine configuration. 

JProcessor Specialty Engine Operational 

Considerations 

Note: The operational considerations in this subsection only apply if you have obtained a 

JProcessor license. 

If you purchased the JProcessor license, a Unisys service representative installed and 

configured the JProcessor Specialty Engine for use. If you do not have a JProcessor 

license, the service representative configured the MCP to be Java-ready. 

JProcessor Secured Configuration 

The JProcessor Specialty Engine is configured in a similar manner as the other 

environments with respect to security and reliability. The features of the JProcessor 

secured configuration include 

• No removable media access in the JProcessor environments 

Having no removable media access completely prevents malicious software getting 

into the system through portable USB devices or CD/DVD media. 

• The secure access device isolates the networking on the JProcessor environment 

from directly accessing the public LAN. 

Note: Refer to the System Planning Guide for more information. 

• Only the following predetermined set of software is supported in the JProcessor 

environment. 

8222 3694–000 6–1

Setting Up and Operating the JProcessor Specialty Engine 

Supported Software Notes 

Unisys MCPJava JVM Software is required and preinstalled. 

Unisys XlateEBCDIC 

Unisys JVM Software is separately licensed and installed 

by the customer. 

• A pre-defined Security Configuration Wizard (SCW) policy 

This policy further reduces the attacks on the JProcessor environment. Refer to 

“Understanding the JProcessor Security Policy” later in this section for more 

information. 

Understanding the JProcessor Security Policy 

Unisys has determined the minimum functional requirements of a standalone JProcessor 

environment and created an SCW policy that implements the needed configuration. This 

SCW policy is referred to as the “JProcessor Security Policy” in this guide. 

The JProcessor Security Policy is available as an XML file with the file name 

JProcessorPolicy.xml. This XML file is applied to the system at the factory. You can find 

this file in the folder below: 

C:\Program Files\Unisys\JPPartition 

The JProcessor Security Policy modifies settings in the JProcessor environment in the 

area of services, firewall rules, connections to the other computers, and security auditing 

in a similar manner as the MCP Firmware Environment Policy does for the environments. 

Details are provided in the following subsections. 

Applying the JProcessor Security Policy for Services 

The JProcessor Security Policy enables the following features and options. Other services 

that support server roles and features, but are not mentioned in the following list, are 

disabled. 

6–2 8222 3694–000

• Microsoft Network Client 

This feature is supported by two services: Workstation and TCP/IP NetBIOS Helper. 

Microsoft Network Client enables users to share files, print, and log on to the network 

by creating and maintaining network connections to remote servers using the SMB 

protocol, and by providing support for the NetBIOS over TCP/IP (NetBT) service and 

NetBIOS name resolution for clients on the network. 

A set of firewall rules for file and printer sharing are enabled to enable the following 

outbound connections: 

- Ping requests for both IPv4 and IPv6 

- NetBIOS Datagram transmission and reception (UDP 138) 

- NetBIOS name resolution (UDP 137) 

- NetBIOS Session Service connections (TCP 139) 

- SMB transmission and reception (TCP 445) 

Consequently, from the JProcessor environment, you can ping a remote computer or 

map a drive to a share on a remote computer. 

Note: 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 Windows host of the JProcessor environment, not even 

those sent from the MCP. Refer to “Enabling MCP Ping Commands through the 

Intra-Platform Connection For JProcessors” in Section 4 of this guide for information 

on how to add a firewall rule to enable inbound ICMP requests. 

• Domain Name System (DNS) Client 

This feature is supported by a single service: DNS Client. 

DNS Client registers the host name of the JProcessor environment and enables you to 

use computer names, in addition to IP addresses, when accessing other computers in 

the network. 

A firewall rule is predefined to open UDP port 53 for outbound DNS requests. 

• Remote Desktop 


This feature is supported by three services: Remote Desktop Services, Remote 

Desktop Configuration, and Remote Desktop Services UserMode Port Redirector. 

You can make a Remote Desktop connection from your Operations Server to the host 

of the JProcessor environment and vice versa. 

To connect to a remote computer from the JProcessor environment, click Start, click 

All Programs, click Accessories, and then click Remote Desktop 

Connection. 

Included in the JProcessor Security Policy is a predefined Remote Desktop firewall 

rule for inbound connections. This rule opens TCP port 3389, which enables remote 

connection. However, the scope of the Remote Desktop firewall rule has been 

modified to restrict inbound remote connections, allowing connections only from the 

following IP addresses on the management LAN: 

8222 3694–000 6–3


192.168.222.20 

192.168.222.50-192.168.222.59 

• Local Application Installation 

This option is supported by one service: Windows Installer. 

Windows Installer enables you to install supported applications on the JProcessor 

environment. This service also enables you to remove or modify applications. 

Note: Do not use Windows Installer to install unsupported applications on the 

JProcessor environment. Doing so can jeopardize the stability and security of the 

system. 

Applying JProcessor Security Policy Settings for Firewall Rules 

In addition to the default core networking rules and the predefined firewall rules that are 

associated with a previously discussed feature or option, Unisys created additional firewall 

rules that support specific JProcessor functions as listed in the following table. These 

rules all have JProcessor as the prefix in their names. 

Table 6–1. Unisys-Defined JProcessor Firewall Rules 


JProcessor MCPConnect1 (TCP-In) This rule opens all TCP ports for the internal 

intra-platform connection between the MCP 

and JProcessor 1 using IP addresses 

192.168.16.141 and 192.168.16.142. 




192.168.16.145 and 192.168.16.146. 




192.168.16.149 and 192.168.16.150. 




192.168.16.153 and 192.168.16.154. 

Note: If the IP addresses in the above firewall rules do not match your internal intraplatform 

configuration, follow the instructions in the topic “Changing IP Address Scope for 

JProcessor MCPConnect Firewall Rules” to modify them. 

6–4 8222 3694–000

Applying JProcessor Security Policy Settings for Network 

Authentication 

The following policy settings have been defined for JProcessor environment to 

communicate with other computers: 

• LAN Manager Authentication Level is set to “Send LM and NTLM — use NTLMv2 

session security if negotiated.” 

Notes: 


- To access this setting, use the Local Security Policy option available in 

Administrative Tools in Control Panel. 

- The MCP Environment is preconfigured with NTLMv2 authentication enabled. If 

you decide to disable NTLMv2 authentication in the MCP Environment, consult 

the topic “Client Access Services Authentication Changes” in the Migration Guide 

for Local Security Policy changes that are required in the JProcessor Operating 

Environment to restore the ability to authenticate using MCP Client Access 

Services. 

• SMB Packet Signing is disabled due to potential performance degradation. 

Note: Access this setting from Local Policies, and under Security Options, access 

Microsoft Network Server: Digitally sign communications (always). 

Applying JProcessor Security Policy Settings for Audits 

Auditing is the process that tracks user activities and records selected types of events in 

the Security Event Log. An audit policy defines the type of event information that should 

be collected. The JProcessor Security Policy Audit settings are listed in Table 6-2. 

Table 6–2. Audit Policy Settings 

Event Name Security Log Records 

account logon events Success, Failure 

account management Success 

directory service access Success 

logon events Success, Failure 

object access Not audited 

policy change Success 

privilege use Not audited 

process tracking Success 

system events Success, Failure 

8222 3694–000 6–5


In addition to the audit settings, the audit security template—SCWAudit.inf—is included in 

the Policy. This template helps detect tampering or attempted tampering of the operating 

system. Write access by any user to any executable or configuration files in the directory 

structure, and changes to the state or configuration of Windows services are recorded in 

the security log. 

Security Event Log size in the JProcessor environment is kept at the default size of 20MB. 

You can modify the auditing policy and the event log size according to your corporate policy 

and specific usage characteristics. 

Changing IP Address Scope for JProcessor MCPConnect Firewall 

Rules 

There are four firewall rules created to open all TCP ports for the intra-platform 

connections on JProcessor 1, JProcessor 2, JProcessor 3, and JProcessor 4. They are 

named “JProcessor MCPConnect1 (TCP-In),” “JProcessor MCPConnect2 (TCP-In),” 

“JProcessor MCPConnect3 (TCP-In),” and “JProcessor MCPConnect4 (TCP-In)”, 

respectively. In the firewall rules, IP address scope is defined to use the preconfigured 

values in Table 6–1, as follows: 

• For JProcessor MCPConnect1 (TCP-In), 192.168.16.141 and 192.168.16.142 




If you changed the intra-platform IP addresses from these preconfigured values, perform 

the following steps to adjust the IP address scope in these firewall rules. Otherwise, 

connections between the MCP and your JProcessor through the intra-platform connection 

will be blocked. 

1. From the desktop of the JProcessor environment, start the Server Manager by clicking 

the Server Manager icon on the taskbar. The Server Manager icon is the first icon to 

the right of the Start button. 

2. From the left pane of the Server Manager window, expand the Configuration node. 

3. Expand the Windows Firewall with Advanced Security node under 

Configuration and then select Inbound Rules. 

4. In the pane under the heading Inbound Rules, JProcessor MCPConnect1 (TCP-In), 

JProcessor MCPConnect2 (TCP-In), JProcessor MCPConnect3 (TCP-In),and 

JProcessor MCPConnect4 (TCP-In) are displayed. 

5. To change either rule, double-click on the rule name. 

The Properties dialog box for that rule displays. 

6. Select the Scope tab and then you can change the IP addresses as needed. 

The Local IP address on the Scope page refers to the IP address of the JProcessor 

environment and the Remote IP address refers to the MCP IP address. 

7. When you are done, click OK. 

6–6 8222 3694–000

Section 7 

Backing Up MCP Firmware 

Configuration Data 

This section provides information on backing up and recovering your system configuration 

data. 

When to Back Up 

When you modify the system configuration, perform a backup on the Operations Server to 

save the changes. The recommended method for backing up the critical configuration data 

is to back up the information to external media, such as a DVD or disk drive. 

Note: Backing up MCP data, including customer data and configuration information, 

should be performed using tools and solutions available in the MCP Environment. It is not 

covered in this document. Refer to the ClearPath Enterprise Servers Server External Disk 

and Tape Storage Systems Configuration Guide for information. 

Performing the System Backup 

Perform the following backup procedure from the Operations Server when you have 

completed your initial system configuration. Also, repeat the backup process each time 

you modify your system configuration. 

1. To begin a PowerShell session, click the PowerShell icon on the taskbar of the 

Operations Server. 


2. Access the MCPPartition subfolder by typing 

cd “C:\Program Files\Unisys\MCP Firmware\MCPPartition” 

Note: This input is not case-sensitive. Ensure that either double or single quotation 

marks surround the path name. 


3. To invoke the backup script, type 

.\Backup-Item 

8222 3694–000 7–1

Backing Up MCP Firmware Configuration Data 

Notes: 

• The .\ notation before the script name denotes the current path. Without this 


• When running the backup script, the parameter specifies a 

folder to store the critical files for your system. The parameter can be set to any 

one of the following: a CD/DVD drive, a mapped network drive, or a URL. The 

syntax structure for the parameter can be 

• a CD/DVD drive or a mapped network drive location. For example, 

z:\Backup 

• a URL location. For example, 

\\servername\sharedfolder\temp 

If you specify a URL location for the parameter, before 

running the script, ensure that the URL location can be accessed with the 

current system credentials. Otherwise, a script failure can occur. 


The script prompts you for confirmation before creating a folder for the destination 

path if none previously exists. 

4. Press Y to continue the backup, and continue to the next step. 

If you do not want to continue, press N to cancel the backup process. 

The backup takes a few seconds complete. Upon completion, the following 

message is displayed: 

Section 8 

Updates 

This section discusses how to update the various components of your FS6200 Server. 

Using Interim Correction (IC) Update Files 

Interim Correction (IC) update files for your FS6200 Server are available on the Unisys 

Product Support website. These IC update files include fixes for the following support 

options: 

• Fixes 

- MCP 

- Microsoft 

• Downloads and Drivers 

- MCP Firmware 

- Drivers 

- Platform firmware 

- Platform BIOS 

- Platform management card firmware 

- Secure access device firmware 

- Operations Server components 

- Other third-party updates 

Accessing and Downloading Updates 

Perform the following steps on the FS6200 Server Operations Server or on any virusprotected 

system with access to the Internet to download the IC update files from the 

Unisys Product Support website: 

1. From an Internet browser, access the Unisys Product Support website at 


2. Log-on with your Support Online user credentials. 

3. Under the ClearPath MCP Servers category, select FS6200 from the MCP 

Mainframes list and click Go. 

8222 3694–000 8–1

Updates 

The FS6200 Server Support Site page is displayed. 

4. Click the desired support option under the following categories. 

• Fixes 

• Drivers and Downloads 

5. Click the product IC level that you want to download. 

6. Download the appropriate IC. 

7. Move the IC you retrieved from the Unisys Support website to the following directory 

on the Operations Server. 

C:\Transfer 

8. Follow the instructions included with the IC to install the update. 

Updating Firmware using the Master Installation 

Manager Update Script 

Master Installation Manager Update (MIM-Update) is a script that you run on the 

Operations Server to install firmware updates to your server. Updates supported by MIM- 

Update are distributed as update packages and posted on the Unisys Product Support 

website. The update package is a zip file that contains everything you need to perform the 

update of one or more firmware components. Step-by-step update installation 

instructions are also provided through either a readme file that is packaged with the 

update or a Unisys Technical Information Bulletin (TIB). 

To install a MIM-Update package: 

1. Download the update zip package from the Unisys Product Support website. 

2. Extract the contents of the package into C:\Unisys\Installation on the Operations 


3. To begin a PowerShell session, click the PowerShell icon on the taskbar of the 

Operations Server. 

4. Enter the command .\MIM-Update.ps1. 

MIM-Update guides you through the process of installing the updates to all affected 

environments. 

You need Administrative privileges to install updates. MIM-Update prompts you to enter 

administrator credentials before attempting an update on a target environment. An 

attempt is made to use these credentials for all updates in the package. It is possible that 

these credentials might not be adequate to perform an update on a target environment. If 

this is the case, you are prompted again to enter different credentials. 

Some updates require a reboot. These reboots are automatically initiated by MIM-Update 

and are generally transparent to you. However, in the case of an update on the Operations 

Server, you must always restart MIM-Update after reboot so that it can continue the 

update process. 

8–2 8222 3694–000

Updating MCP Firmware 

MCP Firmware updates are installed through the MIM-Update process. The following 

types of updates are available for MCP Firmware: 

• Service Pack (SP) 

An SP release is a scheduled update to the MCP Firmware. It consists of a full set of 

MCP Firmware files and can include fixes as well as new features. Installation of a SP 

package overrides any previous IC or CCU updates. 

• Interim Correction (IC) 

An IC update contains fixes for certain components in the MCP Firmware. The update 

package is incremental and accumulative. It does not necessarily need to be installed 

in all the environments on your server. It is for general distribution and applied against 

either the initial release of MCP Firmware or a Service Pack. 

• Customer Critical Update (CCU) 

A CCU update is an update for critical problems reported by a customer. It is not for 

general release but only distributed to the customers who experience a qualifying 

problem. CCU updates are numbered sequentially and are not accumulative. They are 

applied against a specific version of the MCP Firmware. 

Driver and PCI Card BIOS/Firmware Updates 

From time to time, driver and firmware updates for the various environments, such as 

Platform Services drivers, HBA drivers, NIC drivers and firmware or BIOS updates might 

be available. These updates are announced through Technical Information Bulletins (TIBs) 

on the Unisys Product Support website. Contact your Unisys CSE or Unisys Support to 

schedule an update for your system. 

Updating Network Services 

This subsection presents topics related to updating Network Services. 

Updates 

Network Service Firmware updates are installed through the MIM-Update process. Refer 

to section “Updating Firmware Using the Master Installation Manager Update Script” for 

more information on that processing. 

Network Services updates are included in FS6200 Server firmware update packages. 

Consequently, there is no need to download and install Network Services ICs independent 

of the firmware update process. Every Network Services update is cumulative so it can be 

used to update any prior Network Services installation. 

Note: When you install a Network Services update through the MIM-Update process, 

the Network Services package is automatically pushed to each I/O engine and the steps 

required to install Network Services on that I/O engine are performed. Follow the 

instructions in the Firmware Update package for the specific steps associated with 

updating Network Services. 

8222 3694–000 8–3

Updates 

Removing Network Services 

Normally, Network Services runs automatically when your FS6200 Server is running. 

However, you might occasionally want to remove it from the system. 

Network Service Firmware removal can be accomplished through the MIM-Update utility. 

There is a ReadMe file with the package that details the steps necessary to accomplish a 

successful uninstall of Network Service firmware. 

Reinstalling Network Services 

Network Services can be reinstalled without any special considerations. The steps are the 

same those listed in the topic ″Updating Network Services″ presented earlier in this 

section. 

Updating Specialty Engines 

This subsection presents topics related to updating the JProcessor Specialty Engine and 

the ePortal Specialty Engine. 

Updating JProcessor Firmware 

Refer to the Java Installation and Administration Guide for details on performing updates 

to the JProcessor Specialty Engine firmware. 

Updating JProcessor Firmware Operating Environment 

Refer to the Java Installation and Administration Guide for details on performing updates 

to the JProcessor Specialty Engine Firmware Operating Environment. 

Security updates are not needed unless desired by the customer. 

Installing ePortal IC 

Perform the following steps to install the ClearPath ePortal IC: 

1. Use the privileged usercode to log on to the MCP. 

You obtained this usercode when you collected MCP information. 

2. Download the latest ClearPath ePortal IC software from the Unisys Product Support 

website. 

3. If ClearPath ePortal license keys are not installed on the MCP system, use the IK 

MERGE command to merge the ePortal license keys into the SYSTEM/KEYSFILE. 

4. Install the IC software on the MCP Environment. 

5. Check whether following waiting entry is displayed on the ODT: 

8–4 8222 3694–000

Job (USERCODE) EPORTALNOTE 

ACCEPT: Client Access Services share APPLIANCES is not found, 

installation is not completed. 

The preceding entry means that one of the following is true: 

• The Client Access Services Administration Center management server is not 

running. 

• The APPLIANCES share is not configured in the Client Access Services 

configuration. 

6. If you see the waiting entry in the preceding step, do the following: 

a. Make sure that both of the following tasks are running: 

Client Access Services (*SYSTEM/NXSERVICES/SERVER) 

Client Access Services Administration Center management server 

(*SYSTEM/NXSERVICES/ADMINCENTER) 

To start the Client Access Services Administration Center management server, 

enter the following at the ODT or from a MARC window: 

RUN *OBJECT/NXSERVICES (″ADMINCENTER″) 

b. Reinstall the ClearPath ePortal IC. 

7. After Simple Install is completed successfully, you must upgrade the ePortal 

Controller and virtual servers by performing the remaining steps. 

Note: The FS6200 Server has two I/O and Specialty Engine Modules. The remaining 

steps must be performed for both the active and standby ePortal Specialty Engine 

running in ISM-0 and ISM-1. 

8. Update system software of the ePortal controller from the ePortal Manager Website 

as follows: 

a. Click Controller/Manage System Software. 

b. If the available version number is higher than the current version number, click 

Synchronize System Software to start the update. 

The controller might become unavailable during the synchronization process, at 

which time ClearPath ePortal Manager is unreachable. It is recommended that you 

close the ClearPath ePortal Manager after issuing this command and reconnect 

after a few minutes because the ClearPath ePortal Manager itself may be 

updated. 

9. After Controller software is updated, check the current version number by clicking 

Controller/ Manage System Software. It should be same as the available 

version number. 

10. Upgrade all of your virtual servers to the new version performing the following actions 

for each of the virtual servers in your ePortal system: 

a. Click Virtual Server and click one of the virtual server names. 

Updates 

b. Click Manage System Software and if the available version number is higher 

than the current version number, click Synchronize System Software to start 

the update. 

8222 3694–000 8–5

Updates 

c. Check the Health Monitoring page and wait for all PM members of the virtual 

server come back online. 

Note: ClearPath ePortal installation requires the APPLIANCES share on the MCP 

system. The ClearPath ePortal installation performs the following operations: 

• Links to the Client Access Services Administration Center management server 

(ADMINCENTER library) 

• Determines whether the APPLIANCES share is defined in the Client Access Services 

configuration file 

• Creates permanent directories in this share and moves the ClearPath ePortal files to 

these directories 

Updating Environment Operating System Software 

Because your FS6200 Server Management LAN has been restricted to have limited 

exposure to general network attacks, the need to update the supporting environment 

operating sSystem is diminished. If you (according to your organization’s update policy) 

need to update these environments, you can do so. However, you must agree to release 

Unisys from any claims of liability. 

Perform the following steps from the Operations Server to update the FS6200 Server with 

the latest operating system updates: 

1. Launch the MCP Console and click the Halt toolbar button to halt the MCP 

Environment. 

2. Select the MCP menu, point to Maintenance, and then click Shut Down MCP 

Control. 

3. From the Operations Server, click Start and then click Control Panel. 

4. Click Network and Internet. 

5. Click Network and Sharing Center. 

6. Click Local Area Connection for the Management LAN. 

7. Click Properties. 

8. Click Internet Protocol Version 4(TCP/IPv4) and then click Properties. 

9. Type the DNS Server addresses that are used on your intranet LAN. 

10. Click OK until you return to the desktop. 

11. From the Start menu, click Control Panel. 

12. Click on System and Security. 

13. Click Windows Update. 

14. Click Change Settings on the left hand side. 

15. Change the Update setting to Download updates but let me choose 

whether to install them and then click OK to start the download. 

16. Once the download has completed install all the Important updates. 

8–6 8222 3694–000

17. Go back into update settings (steps 11 through 15), change the Update setting to 

Never check for updates, and then reboot the environment. 

18. From the MCP Console, select the Component View tab, expand ISM, expand 

s-Par ® , right-click the E-mode component, and then click Launch RDP Session. 

19. Repeat steps 3 through 17. 

20. From the MCP Console, select the Component View tab, expand ISM, expand 

s-Par ® , right-click the I/O Engine component, and then click Launch RDP 

Session. 

Note: This step must be performed for both I/O engines. 

21. Repeat steps 3 through 17. 

Updates 

22. On the Operations Server, launch the MCP Console and click the Load toolbar button 

to load the MCP Environment. 

8222 3694–000 8–7

Updates 

8–8 8222 3694–000

Section 9 

Troubleshooting and Recovery 

This section contains a list of problems that you might encounter during installation, 

configuration, and use of the 

• MCP Environment 

• JProcessor Specialty Engine 

• ePortal Specialty Engine 

• Network Services software 

• I/O Services 

This section also provides details for recovering your FS6200 Server configuration data. 

This information is used by customers and Unisys service representatives for solving 

system problems. 

Note: If you have an Electronic Service Request (ESR) agreement, your Customer 

Support Center (CSC) is automatically notified of certain types of system problems. In 

these cases, a CSC representative will contact you. You should also report problems to 

Unisys whether or not you expect the support center to contact you. If you have an ESR 

agreement, your ESR support is included in the purchase of the system for the first year. 

Most clients continue this support after the first year. 

See “Submitting Trouble Reports” later in this section for details on how to submit 

information and which information to include. 

Submitting Trouble Reports 

If you need to submit a Unisys Communication Form (UCF) trouble report or CONTACT 

against the FS6200 Server, be sure to provide the following information. 

• A complete description of the issue being reported 

Provide as much detail as possible including the exact time of the problem, any recent 

changes to the system, and so on. 

• If the problem is reproducible, provide the steps to reproduce. 

• Collect all available dumps 

From the MCP Console Diagnostics tab, click Select and take dumps. 

8222 3694–000 9–1


• The system SUMLOG 

• Dell Service Tag number for each cell (can be obtained from Component View of MCP 

Console) 

• Unisys Service Tag (if available) 

Supply Unisys product name, style, and serial number. 

• Level of MCP Firmware software including any updates 

• MCP level including any ICs 

• Network Services level including any ICs 

• List of platform software updates that have been applied 

• Total system memory size and the amount allocated to MCP 

When submitting trouble reports for the FS6200 Server, 

• Issues with the Network Services firmware component should be written against the 

NX/Net product. 

• Issues that appear to be problems with other FS6200 Server firmware components or 

with specialty engines should be written against product FS6200 and an appropriate 

component choice should be made. 

• Issues with the MCP or other MCP software products should be submitted against 

the appropriate software product rather than the Server product. 

How to Submit Information 

You can submit files on tape, CD-ROM, or DVD media. 

To submit files on tape, copy all files from non-MCP environments to an MCP Environment 

disk share and then use the MCP COPY command to copy all the materials to a tape. 

Information on submitting UCF materials through the Internet is available from the Unisys 

Product Support website at 

http://www.support.unisys.com 

For information on electronically routing UCF CONTACT materials to Unisys, see the link 

How to send UCF Materials to Unisys over the Internet on the Unisys Product 

Support website. This link can be found by clicking the Support Database link in the left 

pane of the Product Support Web page. 

For materials sent through FTP, follow-up with a notification e-mail message to 

wcucf.coordinator@unisys.com indicating the name of the files, the UCF contact 

telephone number, and the name of the FTP server. 

9–2 8222 3694–000

Accessing the Unisys Product Support Web Site 

The Unisys Product Support website for the FS6200 Server contains valuable 

documentation, Technical Information Bulletins (TIBs), and links to product updates. You 

can also, register for e-mail notification of TIBs and new documents as they become 

available. 

Perform the following steps on the Operations Server or on any system with access to the 

Internet to access the Unisys Product Support website: 

1. From an Internet browser, access the Unisys Product Support website at 


2. Log-on with your Support Online user credentials. 

3. Under the ClearPath MCP Servers category, select FS6200 from the MCP 

Mainframes list and click Go. 

The FS6200 Support Site page is displayed. 

Using Remote Support 

Remote Support is a method of connecting to remotely located systems for remote 

administration, real-time diagnosis, system configuration and repair, or online file transfers. 

Note: Remote Support applies only to systems connected to the Internet. 

The best reason for using Remote Support is the significant reduction in time required 

diagnosing a problem on a remote system. Remote Support enables a Unisys Remote 

Support Analyst (RSA) to see exactly what the remote client is seeing in real-time as it is 

occurring on the system. It also gives the remote client the ability to watch the session 

and interactively participate with the RSA to resolve an issue. 

Refer to Product Support website for more details on Remote Support. 

Using Call Home 

This subsection addresses tasks you can perform to ensure Call Home services is 

operational. 

Monitoring the Call Home Event E-mails 


Call Home events can be generated by the MCP, the platform management cards, and the 

platform firmwares. The events are converted to e-mail messages and sent to the Unisys 

Support Center and up to three client-designated e-mail addresses. These e-mail 

messages have a Subject designation of “Call Home Alert” followed by an ID number and 

the system serial number. They contain information in an XML format that includes items 

8222 3694–000 9–3


such as time and date of the event, system type, system serial number, problem text, and 

other specific information that can be useful to Unisys support personnel. You can monitor 

these e-mail messages to take necessary action on possible system problems. 

Using Maintenance Mode 

Before performing hardware or software maintenance on the FS6200 Server, you can 

switch Call Home from Operational Mode to Maintenance Mode. This prevents Call Home 

events that are generated during the maintenance period from being converted to e-mail 

messages and sent to the Unisys Support Center. When maintenance is complete, switch 

Call Home back to Operational Mode. Refer to the MCP Console Help for details on 

switching modes. 

Problems with Call Home 

If there is a problem (or suspected problem) with the Call Home services, MCP Firmware 

Environment diagnostics should be taken to gather internal diagnostic information about 

the specific program components that comprise the Call Home functionality. This is 

necessary for Unisys support to diagnose the problem. In addition a Platform Environment 

diagnostics might also prove useful. Refer to the MCP Console Help for information on 

performing these dumps. 

Restarting an Environment 

To restart an environment, access the Component View tab in the MCP Console, rightclick 

the component name, and then click Restart. Click Yes to restart the environment. 

Diagnostic Tasks 

This subsection discusses the various tools you can use to diagnose problems on your 


Taking a Platform Environment Dump 

The Platform Environment Dump gathers platform diagnostic information that includes a 

platform dump and management card logs. 

A Platform Environment Dump contains: 

• Platform Firmware Livedump 

• Platform management card dumps and logs: sellog 

Refer to “Using Diagnostics” in the MCP Console Help for more information. 

Note: Due to the extensive nature of this dump, it can take over 15 minutes to complete. 

9–4 8222 3694–000

Taking a Platform Firmware Livedump 

It is recommended that you use the MCP Console to take a Platform Environment Dump 

(which includes the Platform Firmware Livedump). However, if this method is not 

available, use following steps to generate a Platform Firmware Livedump from the 

Platform Console: 

1. Access the Platform Console from the Component View tab of the MCP Console. 

2. Click the Diagnostics link under the Platform heading to the right of the screen. 

3. From the Platform Diagnostics screen, click Generate Dump to generate a Platform 

Firmware Livedump. 

Note: Due to the extensive nature of this dump, it can take over 10 minutes to complete. 

Taking an MCP Environment Dump 

An MCP Environment Dump is essentially the same as a Full Memory Dump taken by the 

MCP. During an MCP Environment Dump, a process reads the required dump information 

directly without using the MCP. This process creates a dump image file that can be read by 

the SYSTEM/DUMPANALYZER utility. The dump image file is McpDump.zdp. 

Where possible, full memory dumps should be taken from the MCP system using the 

??DUMP command and converted into savedumps. You can use the MDT AUTOSAVE 

option to automate this conversion. 

The MCP Environment Dump can successfully obtain a dump in case the MCP memory 

dump routines fail for any reason. 

The McpDump.zdp can be created on the problem system and transferred to a working 

system for analysis without utilizing the problem system for processing. 

An MCP Environment Dump can be taken without interrupting MCP operation. However, 

dumps taken while the MCP is running are sometimes unusable if too much data changes 

while the dump is being taken. If at all possible, instead of taking this kind of “live dump”, 

it is recommended that you take a dump using the MCP system command ??DUMP or 

take the MCP Environment Dump after halting the system. 

Note: The MCP Environment Dump takes over five minutes to complete. If you can use 

the MDT FASTDUMP feature, a system dump using the ??DUMP command can complete 

in seconds. 

Refer to the MCP Console Help for details on performing an MCP Environment Dump. 

Taking an MCP Firmware Environment Dump 

An MCP Firmware Dump contains: 

• Configuration info 

• Device Maps 


8222 3694–000 9–5


• Diagnostic files 

• Dumps 

• PCD Info 

• Trace files 

• ASE Dump 

• Event logs 

Refer to the MCP Console Help for details on performing a MCP Firmware Environment 

Dump. 

Transferring Diagnostic Data to Unisys Product Support 

Perform the following steps from the Operations Server to transfer diagnostic data to 

Unisys support: 

1. Open an Internet Explorer browser window to www.support.unisys.com and sign 

in with your Primus account. 

2. Select the appropriate product and click Go. 

3. Go to Support Database link and click Submit a UCF document directly to 

Engineering. 

4. Fill out the information in the UCF. 

5. In the Materials section, select the Uploading files to Product Support from 

desktop using FTP Client Applet check box or Supporting Materials via 

another process or tool (i.e. FTPing to another server) check box. 

6. Click Submit Entry. 

7. Follow instructions on uploading material via FTP. 

Platform Hardware Failure Scenarios 

There might come a time when your system becomes unresponsive and it appears that it 

might be the result of a hardware failure. If you are running Call Home, it is likely that 

Unisys Support has already been notified and will be contacting you or visiting you to help. 

In your FS6200 Server configuration (depending on the circumstances), the system might 

already have failed over to the hot standby. 

In any event, it might be useful for you to do a basic diagnosis of the problem. If you 

contact Unisys Support, it is helpful to relay any error codes or symptoms to them to assist 

them in helping you 

The following table lists some possible hardware failure scenarios and their implications. 

9–6 8222 3694–000

Hardware Failure Symptoms Criticality Response 

Internal Disk Drive Error message 

appears on LCD 

panel. LED on disk 

drive turns amber, 

indicating the failed 

drive. 

Memory DIMM Error message 

appears on LCD panel 

Power Supply LED on rear power 

supply turns amber, 

indicating a fault. 

Error message 


panel. 

Cooling Fan Error message 


Motherboard System failure. 

Audible alarm may 

sound. 

HBA Error message may 

appear on LCD panel. 

HBA may show error 

LED’s. 

NIC Error message might 


NIC may show error 

LEDs. 

Platform 

management card 

Error message might 


Unable to perform 

remote management 

Battery Error message 



Non-critical if only 

one drive has failed. 

Multi-drive failures 

might lead to data 

loss. 

Usually non-critical. 

Redundancy and 

error correction can 

correct all but the 

most severe errors. 


one power supply has 

failed 


one fan has failed 

Non-critical for HA 

configurations; critical 

otherwise. 

Non-critical in 

redundant I/O 

configurations. 

Potentially critical in 

other configurations. 

Non-critical in 

redundant network 

configurations. 

Potentially critical in 

other configurations. 

Contact Unisys 

Support 













Usually non-critical Contact Unisys 


Non-critical. Loss of 

AC power to system 

may cause loss of 

Real-Time Clock and 

CMOS settings, 

requiring a 

reconfiguration. 



8222 3694–000 9–7


Hardware Failure Symptoms Criticality Response 

Intrusion Alarm Error message 


panel. If configured, 

an email alert is sent. 

Non-critical. Possible 

indication of nonapproved 

physical 

access to system. 

Operations Server Failure Scenarios 

Alarm will reset when 

the system is 

recovered. 

The Operations Server is the primary management interface into the system. Two 

Operations Servers are included with each FS6200 Server. One Operations Server is 

currently active to manage the server. If the Operations Server fails, contact Unisys 

Support so a replacement could be installed as soon as possible. 

s-Par Failure Scenarios 

The following s-Par failure scenarios might occur on your FS6200 Server. A workaround is 

provided for each scenario. 

Note: s-Par only runs in the ISM module. 

Platform Services Do Not Complete Initialization 

Symptom 

Workaround 

After powering on the ISM, Platform Services initialization does not complete. In this case, 

the Management Card Virtual Console shows no progress on the screen and using the “s” 

command has no effect. 

Use the BMC web interface to power cycle the server. Contact Unisys Support if this 

action is has no effect. 

Cannot Connect to the Platform Console 

Symptom 

The user receives an error message from the web browser when trying to connect to the 

Platform Console 

9–8 8222 3694–000

Workaround 

Use the platform management card to verify the server is powered on. Then, use the 

Virtual Console to verify that the Platform Services are running. Enter s at the prompt and 

verify that all of the components in the s-Par line are in RUNNING state as shown below. If 

not running, wait for each component to reach the RUNNING state. 

Ultra: =RUNNING =RUNNING =RUNNING =RUNNING 

sPAR: =RUNNING =RUNNING =RUNNING =RUNNING =RUNNING 

Guests: =RUNNING =RUNNING =RUNNING =RUNNING =RUNNING =RUNNING =RUNNING 

Press t-troubleshooting console, s-status summary, d-diag console, ?-help 

Environment Stuck in Starting Mode 

Symptom 

Workaround 

Note: The term “environment” refers to the I/O engine or a specialty engine in the ISM. 

Cannot connect to the environment through Remote Desktop and the Platform Console 

shows that the environment is stuck in Starting mode. 

From the Platform Console, restart the environment (graceful stop followed by start). Wait 

a few seconds for the state to change to Stopping, then Starting, and finally Running. 

If the previous action does not work, from the Platform Console, reset the environment 

(forceful stop followed by start). Wait a few seconds for the state to change to Stopping, 

then Starting, and finally Running. 

Contact Unisys Support if neither of these actions have no effect. 

The Platform State is Stuck in Stopping Mode 

Symptom 

Workaround 


Note: The term “platform” refers to the I/O engine or a specialty engine in the ISM. 

After performing a platform Shutdown or Restart command, the platform is stuck in 

Stopping state for an extended period of time (that is, more than 10 minutes). 

The most likely cause of this problem is that one or more environments did not reach the 

Stopped state. This can happen if the environment is waiting for user input, is stuck or 

hung, or missed the stop notification from the platform. As soon as all the environments 

reach the Stopped state the Platform Shutdown/Restart will resume. 

8222 3694–000 9–9


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. 


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


Problems Mapping to a Client Access Services Share 

If you are unable to map to a Client Access Services share in the MCP Environment, first 

verify that you can PING the MCP Environment by IP address and by MCP Server Name. If 

either of these actions fails, follow the troubleshooting suggestions for TCP/IP networking 

issues and fix those capabilities first. If you are still unable to access Client Access 

Services after getting PING working, consult the following resources: 

• The topics “Using Client Server Applications” and “Integrating Your Server with 

Microsoft Networks” in the MCP Implementation Guide 

• Client Access Server Administration Guide 

• Client Access Server User Guide 

Fatal System Error 

If a fatal system error (also known as a Blue Screen or STOP error) occurs on one of your 

FS6200 Server operating environments, submit the following materials to Unisys support. 

• \Windows\Memory.dmp 

• The matching MiniDump from \Windows\Minidump 

• From the MCP Console, take a diagnostic dump with the MCP Environment and 

Platform Environment dump options. 

Follow the steps outlined in “Transferring Diagnostic Data from the MCP Environment to 

Unisys Product Support” earlier in this section to transfer the materials to Unisys for 

analysis. 

You are most likely to notice that the MCP Firmware Operating Environment suffered a 

fatal system error when a popup message appeared within a Remote Desktop session to 

the operating environment. The popup message notifies you that the system recovered 

from a serious problem. You also might be notified of a fatal system error if you monitor 

Call Home event e-mail messages. 

Network Services Failure Scenarios 

The subsection discusses how to submit a networking trouble report and how to perform 

dumps related to Network Services. 

Initiating a Dump 

There are two options available to initiate a dump of networking information on a FS6200 


9–12 8222 3694–000

• Obtain a Network Services firmware dump from the MCP Console: 

1. Click Select from the Diagnostics tab. 

The Select Diagnostics dialog box appears. 

2. Ensure that the Network Services check box is selected. 

3. Click Start. 

The Diagnostics tab of the MCP Console displays the status of the system 

diagnostics and component diagnostics. The diagnostic operation is finished when 

the Overall status in the Summary panel displays Completed. 

4. Submit the entire system diagnostic package file along with your UCF to Unisys 

support. 

• Obtain a network services firmware dump from the MCP environment: 

1. Issue the command NW DUMP NP from an authorized user 

within the MCP Environment. 

This command captures a snapshot dump of all of the NPs that share an I/O 

processor with the NP specified in the command. This command differs from 

issuing the request through the MCP Console because it does not cause the 

information that is captured to be transferred to the Operations Server. 

2. To transfer the captured information to the Operations Server, use the first option 

for initiating a dump. It captures an additional dump, but both dumps are included 

in the captured dump data. For more information, see the DUMP NP command in 

Section 4, “Operational Considerations” of this guide. 

Location of the Dump Data 

When the dump is obtained through the MCP Console, the firmware dump data is 

available on the Operations Server at the location specified on the Diagnostics tab of the 

MCP Console. Within this file is a zip file with diagnostic information for each I/O engine. 

That file, if the Network dump option was selected when the dump was requested, 

contains the zip file with the Network Services firmware dump information. 

When the dump is obtained through the NW DUMP command, the time stamped 

firmware dump data with the name reported in the system sumlog is placed in a separate 

file on the I/O engine where the NP is located. 

The timestamp is formatted as YYYYMMDD_hh.mm.ss. YYYY is the four-digit year, MM is 

the two-digit month, DD is the two-digit day, hh is the two-digit hour, mm is the two-digit 

minute, and ss is the two-digit second of the timestamp at the creation of the dump. 

The Network Services Dump zip files contain the following items from each NP on the 

system: 

• Trace file information 

• Probe file information 

• Setup log file 

• Configuration Utility log file 


8222 3694–000 9–13


• Event logs 

• NSManager log file 

You must provide the dump files when submitting a Network Services software trouble 

report. 

Troubleshooting Tips 

You might find it useful to save your current Adapters.Txt file in case you want to refer to it 

on a subsequent installation. If so, you can find the Adapters.Txt file in the 

ProgramData\Unisys\Networking\Log directory. 

Problem Possible Corrective Action 

During CNS initialization file processing on the 

MCP server, the following error message 

displays in response to an ADD 

CONNECTIONGROUP command for a 

Network Services MCP Network adapter: 

Hardware Not Present 

The response to the NW NP 

command indicates that there are no NPs 

defined. 


command indicates that the network 

processor remains in a discovered state. 


command indicates that the network 

processor remains in an unavailable state. 

Verify that the ICPDEVICEID and LineID in the 

CNS initialization files matches the Line ID for 

that NP as defined in the System Editor of the 

MCP Console. 

Verify that the network processor and line 

identifiers are defined in the ADD 

CONNECTIONGROUP command of the CNS 

initialization file match definitions in the active 

PCD file defined through the System Editor of 

the MCP Console. 


identifiers are defined in the ADD 


initialization file match definitions in the active 

PCD file defined through the System Editor of 

the MCP Console. 

Verify that the System Editor of the MCP 

Console has been run and the proper 

information provided for the network 

processors line identifiers for every network 

processor and that the Network Service 

Firmware is running by running the Task 

Manager applet and locating the NSManager 

process. 

A reboot of the I/O engine might be necessary 

if either case is not true. 

9–14 8222 3694–000

The response to the NW NP command 

for a Network Services device indicates that 

the device is NASCENT. 

Some Ethernet Cable connectors are too wide 

to allow use of all four ports in Quad port NIC 

You cannot establish connections to network 

drives in the MCP Environment over a MCP 

network adapters path. 

During CNS initialization file processing on the 

MCP server, the following error message 

displays in response to an ADD 

CONNECTIONGROUP command for a 

Network Services MCP Network adapter: 

Invalid Attribute Value 


Check for a popup window on the I/O engine 

server for the Service Control Manager 

indicating that ″At least one service or driver 

failed during system startup. Use Event Viewer 

to examine the event log for details″. In this 

case, the event log would be the system event 

log. 

Look for log entries for the Service Control 

Manager of the appropriate date and time and 

examine them. If the description indicates that 

any of the Network Services or drivers failed to 

start or load then a reboot of the operating 

environment server is necessary to restart 

Network Services. 

Also, check for a popup window indicating that 

an application error has occurred and an 

application error log is being generated. If this 

window indicates that any of the Network 

Services is at fault then a reboot of the 

operating environment server is necessary to 

restart Network Services. 

In some rare cases, a Network Services 

uninstall and reinstall might be necessary to 

resolve the problem of one of the services or 

drivers not starting properly. 

Cables using molded connectors or boots for 

the connectors that are wider than the RJ45 

(8P8C) connector itself should not be used on 

the FS6200 Server. Earlier ClearPath systems 

might have included or recommended cables 

with inappropriate connectors. These cables 

cannot be carried forward to the FS6200 


Verify that the NET object of the MCP View in 

the MCP Console is listed and running. 

Try using a PING command to the IP address of 

the MCP network adapter from a device on the 

same subnet. 

Verify that the value specified as the local 

address (in the initialization file ADD 

CONNECTIONGROUP command) matches 

the MAC address of the adapter NIC in the I/O 

engine. 

8222 3694–000 9–15


The IP address for Network Services EVLAN is 

not correct (as shown in the configuration 

summary of the Adapters.txt file generated by 

Network Services Setup). 

NW TCPIP PING from MCP to 

the I/O engine through EVLAN does not work. 

During CNS initialization following initialization 

file processing on the MCP server, network 

connection remains in a state of pending open. 

During CNS initialization following initialization 

file processing on the MCP server, network 

connection will not open. 

Optical network adapter will not connect to 

1Gb Ethernet switch. 


Examine the IP address for Network Services 

EVLAN through the Control Panel for the 

correct value. Note that changes to Network 

Services parameters through the Control Panel 

are not reflected in the Adapters.txt file. To 

keep this file up to date, use the System Editor. 

This is not allowed by the default configuration 

of the FS6200 Server. See “Enabling MCP 

PING Commands through the EVLAN 

Connection” in Section 4 of this guide. 


identifiers are identical for the ADD 


initialization file and the configuration output of 

the System Editor. 


identifiers are identical for the ADD 


initialization file and the configuration output of 

the System Editor utility. 

The network adapter is capable of 

automatically detecting 1Gb and 10Gb 

Ethernet, and selecting the correct speed. This 

does not work with all switches. 

Go to the Advanced Adapter properties within 

the Network and Sharing Center and manually 

set the speed to 1Gb. 

This subsection provides troubleshooting information for the JProcessor Specialty Engine. 

Setting Up a Server Pool 

When setting up your JProcessor Specialty Engines, it is recommended that you setup a 

server pool as shown in one of the following examples. 

NA JAVA SERVER POOL=1, 2 

or 

NA JAVA SERVER POOL=1 

When you assign JProcessor Specialty Engines to a pool, the MCPJava support library 

notifies you when the connection to the specialty engine firmware is lost. Refer to the 

MCPJava Installation and Administration Guide for more information on the server pool. 

9–16 8222 3694–000

Restarting a JProcessor Specialty Engine 

Periodically, the JProcessor Specialty Engine firmware sends a heartbeat message to the 

MCPJava support library. When the MCPJava support library does not receive the 

heartbeat message, it reports that the JProcessor Specialty Engine is not responding by 

initiating a waiting RSVP task named JAVASUPPORT/SERVER/n/NOT/RESPONDING. This 

task displays the following message at the ODT. 

Java Monitor is not responding for Java server n, 

check the Java server or AX to terminate this task and wait for an AX or DS 

In the preceding message, the variable n is the number of the JProcessor Specialty 

Engine. 

Use the NA JAVA SERVER command to determine if the server state as “Unavailable”. 

Perform the following steps to restart a JProcessor Specialty Engine: 

Note: The command examples in this procedure assume you have set up your 

JProcessor Specialty Engines in a server pool. 

1. Check the TCPIP connection to the JProcessor Specialty Engine using the following 

commands: 

• JProcessor Specialty Engine 1 

NW CONN 2101_TCPIP_2101 







The response should indicate the CONNECTIONSTATUS = OPEN. 

2. If the connection status is not OPEN, establish the connection using the following 

commands: 

NW ESTABLISHCALL BY CONN 2101_TCPIP_2101 

NW EC BY CONN 2201_TCPIP_2201 

NW ESTABLISHCALL BY CONN 2102_TCPIP_2102 

NW EC BY CONN 2202_TCPIP_2202 

3. If necessary, clear the connection using the following command: 

NW CLEARCALL 2101_TCPIP_2101 

NW CC 2201_TCPIP_2201 

NW CLEARCALL 2102_TCPIP_2102 

NW CC 2202_TCPIP_2202 


8222 3694–000 9–17


4. Verify that the connection to the JProcessor Specialty Engine is valid by using the 

following command: 

NW TCPIP PING 192.168.16.142 

NW TCPIP PING 192.168.16.146 

NW TCPIP PING 192.168.16.150 

NW TCPIP PING 192.168.16.154 

Note: You can successfully execute this command only if the JProcessor firewall 

rules have been modified to allow a network PING. See ″Enabling MCP PING 

Commands through the Intra-Platform Connection for JProcessors″, in section 4 of 

this guide. 

• A response indicating “% PACKET LOSS 0” indicates that the specialty engine is 

still functioning. You should be able to connect to it using the Remote Desktop 

Client from the Management Workstation where you can attempt to restart the 

JProcessor Specialty Engine firmware. 

• A response indicating “% PACKET LOSS 100” indicates the specialty engine is 

not functioning properly or the connection failed. In either case, a specialty engine 

restart is most likely required. Try to connect to the specialty engine using the 

remote desktop client from the management workstation. You can initiate a 

system restart if necessary. 

5. From the systems management engine, launch the MCP Console, click the 

Component View tab, expand ISM, expand s-Par ® , and then determine if the 

JProcessor Specialty Engine in question is running (denoted by a green circle overlay). 

a. Perform one of the following actions depending on the state of the JProcessor 

Specialty Engine: 

• If the specialty engine it is not running, right-click it and then select Restart 

on the shortcut menu. 

• If the specialty engine is running, right-click it and then select Launch RDP 

Session on the shortcut menu to open a remote desktop session on the 

specialty engine. 

b. Log on using the appropriate administrator user name and password. 

c. Double-click the Server Manager icon next to the Start button in the status 

bar. 

The Server Manager window is displayed. 

d. Locate and expand the Configuration node in the console tree view. 

e. Select the Services node in the console tree view. 

f. Select Unisys MCP Java Monitor. 

g. Right-click and select Restart on the shortcut menu. 

9–18 8222 3694–000

Gathering Diagnostic Information 

The JProcessor Specialty Engine firmware writes application event information to the 

application event log. It also maintains a MCP Java Monitor log that contains more detailed 

information. 

Perform the following steps to access the application event log from the Server Manager: 

1. From the Component View tab of the MCP Console, expand ISM, expand s-Par ® , 

right-click the appropriate JProcessor, and then click Launch RDP Session. 

2. From the task bar, open Server Manager. 

3. Locate and expand the Diagnostics node in the Server Manager tree view. 

4. Expand the Event Viewer node in the Server Manager tree view. 

5. Expand the Applications and Services node in the Server Manager tree view. 

6. Select the MCPJava event log. 

The MCPJava event log file contains information, warning, and error messages. 

7. (Optional) Copy the MCPJava log file to an MCP share where it can be accessed by 

other workstations in the network. 

Obtaining the MCP Java Monitor Log File 

Perform the following steps to access the MCP Java Monitor log file from the Server 

Manager: 

1. From the Component View tab of the MCP Console, expand the ISM and s-Par ® 

components, right-click the appropriate JProcessor, and then remote desktop to the 

JProcessor environment. 

2. Browse to :\MCPJava\Logs and locate the file named JMon.JBT. 

This is the detailed log file of the MCP Java Monitor and might provide reasons why 

the firmware stopped communicating with the MCPJava support library. 

3. (Optional) Copy the file to an MCP share where it can be accessed by other 

workstations in the network. 

4. (Optional) Occasionally clear the MCPJava application event log and remove the 

JMon.JBT detailed log file. 

By default, the MCPJAVA application event log is set to 1MB of messages and reuses 

space as needed. The JMon.JBT file grows to 7MB before it is saved as JMonSaved.JBT 

and a new one started. 



This subsection provides troubleshooting information for the ePortal Specialty Engine. 

8222 3694–000 9–19


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. 


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


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. 


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


If you need to send problem materials for this issue and you have attempted these 

recovery procedures, take a second MCP Firmware Environment Dump. Include the MCP 

Firmware Environment dump taken at the start of this procedure, the second dump (if 

taken), a detailed description of the recovery actions you attempted, and MCP SUMLOGs 

covering the time period when access to the device was lost. 

Device is Visible in the I/O Engine Environment But Inaccessible from 

the MCP 

Consider the following suggestions to resolve this situation. 

• Review MCP messages and waiting entries as well as messages in the SUMLOG. 

These might indicate a specific device or path to check. Also use the RF command on 

the affected devices, particularly the affected taps; the command response contains 

error statistics that can help identify a problem. 

• Be aware that if there has been an outboard problem causing loss of paths that has 

been repaired, 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. If the I/O engine 

environment is busy rediscovering devices, the MCP might not be able to successfully 

access any of them until the rediscovery of devices is complete. 

• You might sometimes need to perform the UR command and then a UR− command on 

a channel, tap, or device to get it back in service. If this does not succeed, UR− should 

result in new system messages about device access problems that may help 

diagnose the problem. If the messages indicate that a recovery activity is in progress, 

wait a while and try the UR and UR− commands again. 

• If none of the preceding suggestions work and the device remains visible in the I/O 

engine environment but inaccessible from the MCP, problem materials should be 

collected at this point for potential submission to Unisys support including a detailed 

description of the recovery actions you attempted, an MCP memory dump, SUMLOG, 

and MCP Firmware Environment dump. 

• The next recovery steps to attempt are to halt/load the MCP, restart the I/O engine 

environment, or restart Platform Services. If the problem persists, contact Unisys 

support. 

Recovery Actions 

This subsection lists recovery action you can perform for your FS6200 Server. 

Recovering FS6200 Server Configuration Data 

You can recover FS6200 Server system configuration data, such as PCD files, by running 

the Restore-Item scripts. Ensure that you are logged on to the Operations Server as an 

administrator and then perform the following procedure. 

1. To begin a PowerShell session, click the PowerShell icon on the taskbar. 


2. Access the MCPPartition subfolder by typing 

9–24 8222 3694–000

cd “C:\Program Files\Unisys\MCP Firmware\MCPPartition” 

Note: This input is not case-sensitive. Ensure that either double or single quotation 

marks surround the path name. 


3. To invoke the recovery script, type 

.\Restore-Item 

Notes: 

• The .\ notation before the script name is important as it denotes the current path. 

Without this notation, PowerShell cannot locate the script file. 

• When running the recovery script, the parameter specifies the 

location from which to restore the critical files for your system. The parameter can 

be set to any one of the following: a CD/DVD drive, a mapped network drive, or a 

URL. 

The syntax structure for the parameter can be 

• a CD/DVD player or mapped network drive location. For example, 

z:\Backup 

• a URL location. For example, 

\\servername\sharedfolder\temp 

If you plan to specify a URL location for the parameter, before 

running the script, ensure that the URL location can be accessed with the 

current system credentials. Otherwise, a script failure can occur. 


The script prompts you for confirmation before initiating the recovery. 

4. Press Y to continue the recovery. 

The recovery takes a few seconds to complete. At completion, the following 

message is displayed: 

files copied from 

Restore-Item completed successfully. 

5. If you do not want to continue, press N to cancel the recovery. 

Powering Down a Cell to Replace Failed Hardware 

Use one of the following methods to power-down a cell. 


Note: Be sure to halt the MCP using the MCP Console before performing any of the 

following actions. 

8222 3694–000 9–25


• Press and hold the Power button on the front of the cell for five seconds. 

• Use the BMC web interface. 

1. From the Component View tab of the MCP Console, right-click the appropriate 

component (PMM, ISM, OPS) and then click BMC Web Interface. 

2. If you see a Certificate error screen, click Continue to this Website. 

3. Log on (default usercode/password: Administrator/Administer4Me) 

4. Select Power on the left-hand side. 

5. Select either Power Off System or Graceful Shutdown. 

6. Click Apply. 

• From the Component View tab of the MCP Console, right-click the appropriate 

component and then click either Shutdown (Graceful) or Shutdown (Forceful). 

Powering Up a Cell 

Use one of the following methods to power-up a cell. 

• Press the Power button on the front of the cell. 

• Use the BMC web interface. 




3. Logon (default usercode/password: Administrator/Administer4Me) 


5. Select Power On System. 


Power-Cycling a Cell 

Perform the following steps using the BMC web interface to power-cycle a cell: 

Note: Be sure to halt the MCP using the MCP Console before performing the following 

steps. 




3. Logon (default usercode/password: Administrator/Administer4Me) 


5. Select either Reset System or Power Cycle System. 


9–26 8222 3694–000

Restarting Platform Services 

Note: Be sure to halt the MCP using the MCP Console before restarting Platform 

Services. 

You can restart the ISM cell from the Component View tab of the MCP Console or from the 

Platform Console when the platform is in the Running state. Restarting the platform 

means bringing the platform to the Stopped state and back to the Running state in a 

controlled manner. 

Refer to “Using Platform Commands” in the Platform Console Help for more details. 

Restarting an ISM Environment 

Note: Be sure to halt the MCP using the MCP Console before restarting an ISM 

environment. 

You can restart an ISM environment from the Component View tab of the MCP Console or 

from the Platform Console when an environment is in the Running state. Restarting an 

environment means bringing a running environment to the Stopped state and then back to 

the Running state in a controlled manner. 

Refer to “Using Environment Commands” in the Platform Console Help for more details. 

Reinstalling the Entire Platform 


Reinstalling the entire platform should only be performed by Unisys support personnel. 

Contact Unisys Support if you need to reinstall the entire platform. 

8222 3694–000 9–27


9–28 8222 3694–000

Appendix A 

Building Network Initialization Files 

This appendix provides guidelines for building CNS, TCP/IP, and BNA network initialization 

files and also includes a preconfigured SNMP initialization file. You can find sample CNS 

and TCP/IP initialization files for the FS6200 Server on the Network System Software 

NETSYSTEM release media. 

The standard set of initialization files is included in the samples: 

In addition, a preconfigured SNMP agent initialization file is included on the NETSYSTEM 

release media. 

If you want to create your own CNS or TCP/IP initialization files, refer to the sample files on 

the NETSYSTEM release media and to the “Guidelines for Building CNS Initialization 

Files” or “Guidelines for Building TCP/IP Initialization Files” topics later in this appendix. If 

you want to create BNA (also known as Heritage Network Services) initialization files, refer 

to “Guidelines for Building BNA Initialization Files” later in this appendix. 

Preconfigured CNS and TCP/IP Initialization Files 

The following subsections describe the CNS and TCP/IP sample initialization files for all 

ClearPath Series model groups. 

CNS and TCP/IP Initialization Files 

These CNS initialization files define the commands preconfigured for ClearPath FS6200 

Servers: 

• INIT/SAMPLE/CLEARPATH/VNP/DUALIOP/CPMCP1/CNS 

• INIT/SAMPLE/CLEARPATH/VNP/DUALIOP/CPMCP1/TCPIP 

Guidelines for Building CNS Initialization Files 

This subsection provides general guidelines for building a CNS initialization file. The 

examples in this subsection are taken from the following file on the NETSYSTEM release 

media: 

INIT/SAMPLE/CLEARPATH/VNP/DUALIOP/CPMCP1/CNS 

• A connection group is required for each network interface 

• The first network interface for an I/E Engine has an EVLAN Connection Group and up 

8222 3694–000 A–1


to 8 MCP network adapter connection groups. The remaining 5 network interfaces 

have up to 8 MCP network adapter connection groups without an EVLAN connection 

group. 

• NW AUTHORIZE statements are included as follows. Adjust for your own 

environment: 

NW AUTHORIZE *DEFAULT = NETWORKCONTROL;% 

NW AUTHORIZE ADMINISTRATOR AT CPMCP1 = SECURITY;% 

• The NW CONNECTION GROUP statements you may need to change are 

ICPDEVICEID, LINEID, and LOCALADDRESS. The LOCALADDRESS is allowed to 

default for Network Services devices by using *DEFAULT as shown in the following: 

NW ADD CONNECTIONGROUP CG_ICP_2100% 

% Connection Group Information % 

( TYPE = LAN% 

, ICPDEVICEID = 210% 

, LINEMODULEID = 1% 

, LINEID = 0% 

, SPEED = 1000000000% 

, LOCALADDRESS = *DEFAULT% 

, MAXINPUTMESSAGESIZELIMIT = 4352% 

, MAXOUTPUTMESSAGESIZELIMIT = 4352% 

, MAXINPUTMESSAGESIZE = 4352% 

, MAXOUTPUTMESSAGESIZE = 4352% 

)% 

;% 

NW ADD CONNECTIONGROUP CG_ICP_2111% 

% Connection Group Information % 

( TYPE = LAN% 

, ICPDEVICEID = 211% 

, LINEMODULEID = 1% 

, LINEID = 1% 

, SPEED = 1000000000% 

, LOCALADDRESS = *DEFAULT% 

, ADAPTERTYPE = GIGABIT% 





)% 

;% 

Note: The MIMS, MOMS, MIMSL, and MOMSL values are required for an EVLAN 

connection. The recommended value is 4352. 

Guidelines for Building TCP/IP Initialization Files 

This subsection provides general guidelines for building a TCP/IP initialization file. The 

examples in this subsection are taken from the following file on the NETSYSTEM release 

media: 

INIT/SAMPLE/CLEARPATH/VNP/DUALIOP/CPMCP1 

Note that the following statements are included in the initialization file: 

A–2 8222 3694–000

• NW TCPIP TCPIPIDENTITY 

NW TCPIP TCPIPIDENTITY ADD NP 210 LINE 1 192.168.16.141/30 VISIBLE -;% 

There must be one TCPIPIDENTITY statement for each network interface. Each 

combination of NP and LINE in a NW TCPIP TCPIPIDENTITY statement must have a 

corresponding NW ADD CONNECTION statement. 

• NW TCPIP HOSTNAME 

NW TCPIP TCPIPHOSTNAME CPMCP1.CUSTOMER.COM;% 

% % 

Note that you have to set the TCPIPHOSTNAME. Include your fully qualified domain name 

in this statement. By default, all ClearPath initialization file samples name the host 

CPMCP1.CUSTOMER.COM. 

• NW TCPIP OPTION 

NW TCPIP OPTION - USERFCMTU;% 

% % 

Note that by default, USERFCMTU is reset to improve performance. 

• NW TCPIP ROUTE ADD 

% NW TCPIP ROUTE ADD DEFAULT 192.168.237.250 1;% 

% % 

Note that you need to uncomment and change this value to match the value of the router 

on your network segment. 

• NW ADD CONNECTION TO 

NW ADD CONNECTION TO CG_ICP_2100% 

2100_TCPIP_2100% 

% Connection Information % 

( NETWORKLAYERENTITY = IP% 

, REMOTEADDRESS = 000000000000% 

, CLASS = CLASS_1% 





)% 

;% 

This statement adds a connection to a connection group defined in a CNS initialization file. 

The entries that must be unique for each connection are: 

CONNECTION GROUP NAME 

CONNECTION NAME 

Note the following for the CLASS statement: 


• CLASS_1 is for an EVLAN connection; ETHIP is for Ethernet connections. 

• MIMS, MOMS, MIMSL, and MOMSL are required for an EVLAN connection. The 

recommended value is 4352. 

8222 3694–000 A–3


Preconfigured SNMP Initialization File 

The following SNMP initialization file provides the preconfigured SNMP configuration 

commands for identifying required information for an SNMP Management station. 

INIT/SAMPLE/SNMPAGENT/INITFILE 

Notes: 

• The ADAPTERNAME attribute cannot be used to map MCP Network adapters to the 

MCP; mapping is provided by the LINEID attribute. The ADAPTERNAME attribute is 

still accepted but will be ignored. ADAPTERNAME will be de-implemented in a future 

release. 

• There is no need to specify SPEED attribute values for LAN MCP Network adapters. 

Connection Services forces SPEED=*DEF which causes the MCP Network adapter 

hardware to return an actual speed value when the connection group is opened. 

SNMP Initialization File 

This SNMP initialization file (INIT/SAMPLE/SNMPAGENT/INITFILE) provides the 

preconfigured SNMP configuration commands for identifying required information for an 

SNMP Management station. 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

%%%%%%%%%% MCP SNMP Sample Init File %%%%%%%%%% 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

%%%%% %%%%% 

%%%%% This file is not a configured SNMP initfile. It is meant to %%%%% 

%%%%% be used as a guide for building a configured SNMP initfile. %%%%% 

%%%%% The xxx.xxx.xxx.xxx IP addresses must be changed to valid %%%%% 

%%%%% IP addresses; if those commands are used, they must be %%%%% 

%%%%% uncommented. The community values listed as ″community″ %%%%% 

%%%%% must be changed to values that cannot be easily guessed; %%%%% 

%%%%% this must be done to provide increased security from %%%%% 

%%%%% malicious attacks. (Do not remove the quotes; they are %%%%% 

%%%%% required for processing the command.) The ReadOnly community %%%%% 

%%%%% string CPMCP1 must also be changed. %%%%% 

%%%%% The first section contains the read-only COMMUNITY SET and %%%%% 

%%%%% examples of read-write COMMUNITY and TRAPCOMMUNITY commands %%%%% 

%%%%% usable on all MCP platforms; the second section contains %%%%% 

%%%%% examples of the COMMUNITY/TRAPCOMMUNITY SET commands with %%%%% 

%%%%% Server Sentinel explicit comments for Server Sentinel %%%%% 

%%%%% knowledgable users. The third section contains the SETs %%%%% 

%%%%% for System variables and the object managers. Commands %%%%% 

%%%%% which are not commented out should be included in the %%%%% 

%%%%% SNMP initfile (the only exception being the read-only SET %%%%% 

%%%%% in environments that want to tightly control read-only %%%%% 

%%%%% access.) %%%%% 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

% The first command allows read-only access from all IP addresses. 

%NW SNMP COMMUNITY ADD ″CPMCP1″ 0.0.0.0 ReadOnly; 

A–4 8222 3694–000


% 

% The next command sets read-write access from a particular IP address 

% Update the community value and the IP address; copy the command 

% to give read-write access to multiple IP addresses/community strings. 

%NW SNMP COMMUNITY ADD % 

% ″community″ xxx.xxx.xxx.xxx ReadWrite;% 

% 

% The next command identifies a destination for traps from this system. 

% Update the IP address to a valid IP address destination; copy the 

% command to add more destinations. 

%NW SNMP TRAPCOMMUNITY ADD % 

% ″public″ xxx.xxx.xxx.xxx;% 

% 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

% Server Sentinel 

% The next command adds SP0. 



% 

% The next command adds SP1. 



% 

% Add the external Management Server if it exists. 



% 

% Define a SNMP TRAPCOMMUNITY for each Service processor and the 

% external management server if it exists. As sites may/may not use the 

% default IP addresses for SP0 and SP1, the IP address must be updated; 

% the command must be uncommented to use. The community value does not 

% need to be updated unless the ″public″ community value has not been 

% defined on the system. 

% 

% Add SP0 Trapcommunity 



% 

% Add SP1 Trapcommunity 



% 

% Add the external Management Server trapcommunity if it exists. 



% 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

% The next command sets the SysContact, SysName, and SysLocation 

% objects. Change the values in parentheses to meaningful values. 

% (Do not remove the parentheses; they are needed for processing the 

% command.) 

NW SNMP SET 

8222 3694–000 A–5


SysContact = ″ClearPath Administrator″ % 

,SysName = ″ClearPath System″ % 

,SysLocation = ″ClearPath Location″ 

; 

% 

% 

% The next command identifies the Host Resources Object Manager to 

% the SNMP Agent. 

NW SNMP SET % 

agentAPIPRowStatus ″Host Resources MIB Object Manager″ = 4% 

,agentAPIPCodefile ″Host Resources MIB Object Manager″ = 

″RUN *SYSTEM/SNMPOBJMGR/HOSTMIB″% 

,agentAPIPAdminStatus ″Host Resources MIB Object Manager″ = 1% 

,agentAPIPRspTimer 

;% 

″Host Resources MIB Object Manager″ = 5% 

% 

% The next command identifies the MCP Resource Object Manager to the 

% SNMP Agent. 

NW SNMP SET % 

agentAPIPRowStatus ″MCP Resource Object Manager″ = 4% 

,agentAPIPCodefile ″MCP Resource Object Manager″ = 

″RUN *SYSTEM/SNMPOBJMGR/MCP″% 

,agentAPIPAdminStatus ″MCP Resource Object Manager″ = 1% 

,agentAPIPRspTimer 

;% 

″MCP Resource Object Manager″ = 5% 

% 

% The next two commands set the agent response timer to a value higher 

% than the default of 3 seconds. (The response timers for the object 

% managers above are also set higher than the default. Setting the 

% response timer to a higher value is recommended for MCP platforms 

% with high processor demand.) Note that the CNS Object Manager and 

% the System/Assistant Object Manager can only have the response timer 

% timer set; these are libraries and the other objects normally set in 

% the initfile for object managers cannot be set for libraries. 

NW SNMP SET % 

agentAPIPRspTimer 

;% 

NW SNMP SET % 

″CNS Object Manager″ = 10% 

agentAPIPRspTimer 

;% 

″System/Assistant Object Manager″ = 10% 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

Guidelines for Building BNA Initialization Files 

This subsection provides general guidelines for building a BNA initialization file. It shows 

sample BNA configuration commands required to identify the MCP Ethernet Adapter. This 

adapter provides connections to a pair of BNA hosts (BNAHOST1 and BNAHOST2. For 

BNA based operations, Network Services now supports 802.2 Class of Service 2. To 

specify this class of service, simply add the following attribute to each required 

connection: 

CLASS = CLASS_2 

A–6 8222 3694–000

Sample BNA Initialization File 

% On the following lines, REMOTEADDRESS values are sample 

% addresses. The actual hardware-specific addresses of the 

% remote host must be used. 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

% Local Identity % 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 

NW LOCALIDENTITY CPMCP1(1,1,1,1)% 

NW ADD CONNECTION TO CG_ICP_2101% 

2101_BNAHOST1_1% 


( NETWORKLAYERENTITY = ROUTER% 

, REMOTEADDRESS = 08000B000834), %


Note: You can define a router (gateway) IP address for your router on the NAU TCP/IP 

DEFAULT ROUTE LIST screen. For additional information, refer to the TCP/IP 

Implementation and Operations Guide. 

If you are loading the file for editing, load it to a version name that is different than the 

samples. This will prevent your version disk dump file from being overwritten if you update 

your NAU release. 

For additional information about loading an NAU network version disk dump file, refer to 

the Network Administrative Utility Operations Guide. 

A–8 8222 3694–000

Index 

A 

accessing the Unisys Support Product 

website, 9–3 

accessing updates, 8–1 

ADAPTERS.TXT file, sample, 3–22 

ADAPTERTYPE attribute, for defining 

EVLANs and MCP network adapters, 

4–24 

diagnostic tasks 

Call Home, 9–3 

problems with Call Home, 9–4 

Administrator 

password, changing, 3–31 

user name, changing, 3–31 


troubleshooting, 9–19 

event e-mails, monitoring, 9–3 

fatal system error, 9–12 

initiating a dump, 9–12 



MCP APPLIANCES share, relocating, 5–3 

MCP Environment Dump 

taking, 9–5 


failure scenarios, 9–12 

troubleshooting tips, 9–14 

Platform Environment Dump 

taking, 9–4 

Platform Firmware Livedump 

taking, 9–5 

platform hardware 


APPLIANCES share, relocating, 5–3 

application 

configuring a separate CCF port for, 5–5 

developing an ePortal, 5–11 

recovery actions 

power-cycling a cell, 9–26 

setting up a server pool, JProcessor 

Specialty Engine, 9–16 

specialty engine 

JProcessor, 9–16 

system error, 9–12 

transferring diagnostic data to Unisys 

Product Support, 9–6 

trouble report, submitting, 9–1 

attaching additional Fibre Channel cables, 

3–7 

attributes 

EVLAN, 4–24 

Jumbo Frames, 3–18 

MCP network adapters, 4–24 

audit settings 

JProcessor Security Policy, 6–5 

MCP Firmware Environment Policy, 4–12 

UnisysHarden.ps1 script, 4–18 

UnisysHarden_Rollback.ps1 script, 4–17 

User Communication Form (UCF), 

submitting, 9–1 

B 

BMC Web interface, 2–8 

BNA initialization file, 3–31 

books and media, 1–1 

C 

Call Home 

configuration, 3–33 

diagnostic tasks, 9–3 

e-mail alerts, testing, 4–28 

e-mail heartbeats, testing, 4–28 

Maintenance mode, 4–28 

monitoring event e-mails, 9–3 

problems with, 9–4 

services, 4–27 

using Maintenance mode, 9–4 

CANDE editor, 3–14 

CCF ports for different applications, 

configuring separate, 5–5 

ChangeRulesForMCP.ps1 script, 4–13 

changing 

Administrator password, 3–31 

Administrator user name, 3–31 

8222 3694–000 Index–1

Index 

IP address for Network Services, 3–15 

IP address scope for JProcessor 

MCPConnect firewall rules, 6–6 

changing the default systems management 

account password, 3–32 

CLEAR NP command, 4–25 

ClearPath ePortal documents, 1–2 

ClearPath MCP 14.0 documents, 1–2 

CNP dump data, 9–13 

CNS initialization file, 3–14, 3–30 

preconfigured, 3–22 

collecting information 

for the MCP, 5–1 

commands, networking, 4–25 

configuration 

recovering FS6200 Server data, 9–24 

Call Home services, 3–33 

ePortal Specialty Engine, 5–1 

tasks in ePortal Manager, 5–7 

JProcessor Specialty Engine, 6–1 

MCP EMAIL utility, 5–7 

MCP Environment, 3–32 

MCP Networking, 4–21 

named pipe, 5–7 

Networking, 3–9 

Operations Server, 3–33 

separate CCF ports for different 

applications, 5–5 

System Editor, 3–19 

validating Connector protocol-specific 

handler (Connector PSH), 5–6 

connection error, MCP Console, 9–11 

CONNECTION inquiry, 4–25 

Connector protocol-specific handler 

(Connector PSH) installation and 

configuration, verifying, 5–6 

controlling the MCP Environment, 4–5 

correspondence between MCP storage 

channels and firmware environment 

storage controllers, 3–3 

creating MCP usercodes, 5–1 

GROUPCODE attribute, 5–2 

EPORTALCONTROLLER, 5–2 

EPORTALSTUDIO, 5–2 

Custom Connect Facility (CCF) port, verifying 

creation for ePortal Business, 5–5 

D 

default Networking configuration, 3–10 

default systems management account 

password, changing, 3–32 

developing an ePortal application, 5–11 


accessing the Unisys Product Support 


monitoring Call Home event e-mails, 9–3 

Platform Environment Dump, 9–4 

Platform Firmware Livedump, 9–5 

Call Home Maintenance mode, 9–4 

MCP Environment Dump, 9–5 

MCP Firmware Environment Dump, 9–5 

Remote Support, 9–3 



disabling Fibre Channel ports, 3–8 

disconnected components in MCP Console, 

9–11 

disconnecting Fibre Channel I/O devices, 

4–30 

disk management, VSS, 3–2 

disk space on the MCP server, 5–3 

documentation updates, 1–2 

documents 

ClearPath ePortal, 1–2 

ClearPath MCP 14.0, 1–2 

FS6200 Server, 1–1 

downloading updates, 8–1 

driver updates, 8–1, 8–3 

dual ISM system, ePortal Specialty Engine, 

5–11 

dump files, NAU network version, using, A–7 

DUMP NP command, 4–25 

dumps 


initiating, 9–12 




dynamic PCD updates, 4–29 

E 

e-mail 

alerts, testing in Call Home, 4–28 

heartbeats, testing in Call Home, 4–28 

enabling 

Fibre Channel ports, 3–7 

MCP PING commands through EVLAN 

connection, 4–19 

Index–2 8222 3694–000

MCP PING commands through intraplatform 

connection, 4–30 

environment 

transferring diagnostic data, 9–6 

MCP, configuring, 3–32 

restarting, 4–4 

secured configuration, 4–5 

shutting down, 4–4 

status, viewing, 4–4 

viewing status, 4–4 

ePortal Manager, 2–7, 2–8 

initial configuration tasks, 5–7 

ePortal Personality Module, 2–7 



initial tasks in ePortal Manager, 5–7 

ePortal personality module name conflicts, 

5–11 

for dual ISM system, 5–11 

operating, 5–1 

operational considerations, 5–10 

overview, 2–7 

restoring, 5–19 

setting up, 5–1 


gathering diagnostic information, 9–21 



EPORTALCONTROLLER value for the 

GROUPCODE attribute, creating a 

usercode with, 5–2 

EPORTALSTUDIO value for the 

GROUPCODE attribute, creating a 

usercode with, 5–2 

ESTABLISHCALL command, 4–26 

Ethernet Jumbo Frames, preparing to use, 

3–18 

EVLAN 

attributes, 4–24 

connection, enabling PING commands, 

4–19 

connections, 3–14 

IP Address, changing, 3–15 

verifying Network Services installation, 

4–22 

F 

failure scenarios 

Network Services, 9–12 

platform hardware, 9–6 


Operations Server, 9–8 

s-Par, 9–8 

Fast Ethernet 

port aggregation, preparing to use, 3–17 

Fibre Channel 

cables, attaching additional, 3–7 

I/O problems, troubleshooting, 9–21 

ports, 3–8 

disabling, 3–8 

enabling, 3–7 

firewall rules 


JProcessor Security Policy settings, 6–4 


MCP Firmware Environment Policy 

settings, 4–7 

MCPConnect, 6–6 

firmware environment storage controllers, 

3–3 

firmware updates 

using MIM-Update script, 8–2 

fixes, updates, 8–1 

fixing disconnected components in MCP 

Console, 9–11 

FS6200 Server 

configuration data, recovering, 9–24 

documents, 1–1 

initialization files, A–1 

preconfigured initialization files, 3–22 

G 

gathering diagnostic information, ePortal 


gathering diagnostic information, JProcessor 


GROUPCODE attribute, creating a usercode 

with 

EPORTALCONTROLLER attribute, 5–2 

EPORTALSTUDIO attribute, 5–2 

H 

hardware overview, 2–1 

hardware platform 

monitoring boot progress, 4–1 

powering off, 4–3 

powering on, 4–1 



Index 

8222 3694–000 Index–3

Index 

viewing power status, 4–1 

I 

IC 

ePortal Business, installing, 5–3, 8–4 

update files, 8–1 

IEEE 802.1Q VLANS 

preparing to use, 3–17 

information, collecting 

for the MCP, 5–1 

initial configuration tasks in ePortal Manager, 

5–7 

initialization files, 3–9, 3–14 , 3–30 

described, A–1 

FS6200 Server, A–1 

guidelines for building CNS files, A–1 

guidelines for building TCP/IP files, A–2 

required information for SNMP 

Management station, A–4 

SNMP, A–4 

initializing Network Servicese, 4–21 

inquiries, networking, 4–25 

installation 

ePortal Business Interim Correction (IC), 

5–3, 8–4 

validating Connector protocol-specific 

handler (Connector PSH), 5–6 

Interim Correction (IC) 

ePortal Business, installing, 5–3, 8–4 

ePortal Business Interim Correction (IC), 

installing, 5–3 

update files, 8–1 

intra-platform 

connection, enabling PING commands, 

4–30 

I/O services, 4–28 

attaching additional Fibre Channel cables, 

3–7 

disabling Fibre Channel ports, 3–8 

disconnecting Fibre Channel I/O devices, 

4–30 

enabling Fibre Channel ports, 3–7 

I/O time, 4–29 

MCP storage channels and firmware 

environment storage controllers, 

3–3 

performing dynamic PCD updates, 4–29 

power cycling Fibre Channel I/O devices, 

4–30 

VSS disks, reconfiguring, 3–2 

I/O time, 4–29 

IP address 

changing for Network Services EVLAN 

path, 3–15 

IP address values 

IOE default, 3–11 

J 

Java Monitor Log File, obtaining, 9–19 

JProcessor Firmware Operating 

Environment, updating, 8–4 


audit settings, 6–5 

firewall rules, 6–4 

network authentication settings, 6–5 



changing IP address for MCPConnect 

firewall rules, 6–6 


firmware, updating, 8–4 





gathering diagnostic information, 9–19 

obtaining the MCP Java Monitor log 

file, 9–19 


setting up a server pool, 9–16 

Jumbo Frames 


Networking configuration, 3–18 

preparing to use, 3–18 

L 

LCD panel, 4–2 

LINEID attribute, for defining MCP network 

adapters, 4–24 

LocalAddress attribute, for defining VLANs 

and MCP network adapters, 4–24 

local dump, 4–25 

local MAC address, setting, 3–16 

log file, MCP Java Monitor, 9–19 

M 

MAC address, setting, 3–16 

Index–4 8222 3694–000

MAICP4 

dump data, 9–13 

Maintenance mode, 4–28 

diagnostic task, 9–4 

Management Card Virtual Console, 2–8, 4–2 

management LAN, overview, 2–3 

mapping to a Client Access Services share, 

problems, 9–12 

Master Installation Manager Update Script, 

8–2 

MCP Console, 2–5, 2–7 , 3–14 , 4–2 

connection error, 9–11 

MCP EMAIL utility, configuring, 5–7 

MCP Environment, 2–4, 3–14 


controlling, 4–5 



MCP operations, 4–5 



MCP Firmware Environment Dump 

taking, 9–5 


audit settings, 4–12 

irewall rules, 4–7 

network authentication settings, 4–11 


utility scripts, 4–12 

ChangeRulesForMCP.ps1, 4–13 

UnisysHarden.ps1, 4–18 

UnisysHarden_Rollback.ps1, 4–17 

MCP Firmware, updating, 8–3 

MCP information, collecting, 5–1 

MCP Java Monitor log file, obtaining, 9–19 

MCP network adapter, 3–15 


MCP Networking 

configuring, 4–21 

values, 3–23 

values for IOE-1, 3–23 

values for IOE-2, 3–27 

MCP ODT, 4–2 

MCP operations, 4–5 

MCP PING commands 

enabling through EVLAN connection, 4–19 

enabling through intra-platform 

connection, JProcessors, 4–30 

MCP server disk space, 5–3 

MCP storage channels, 3–3 

MCP usercodes, creating, 5–1 

MCPConnect firewall rules, 6–6 

MCPJava log file, 9–19 

MCPJava Monitor log file, 9–19 

media and books, 1–1 

MIM-Update script 

updating firmware, 8–2 

monitoring 

Call Home event e-mails, 9–3 

platform boot progress, 4–1 

Index 

N 

named pipe, configuring, 5–7 

Network Administrative Utility (NAU), 3–14 

network authentication settings 



Network Processor default values 

external connections on IOEs, 3–10 

Network Processor instance numbers 

EVLAN and intra-platform connections on 

IOEs, 3–10 

Network Processors (VNPs), 2–6 


differences from previous MCP systems, 

4–21 

EVLAN attributes, 4–24 

initializing, 4–21 

initiating a dump, 9–12 

operations, 4–20 

operations interface summary, 4–23 

reinstalling, 8–4 

removing, 8–4 

support for MCP network adapters, 3–15 

tools, 3–13 


updating, 8–3 

verifying EVLAN installation, 4–22 

verifying installation, 4–22 

network version dump files, using, A–7 

networking commands 

CNS CLEAR NP, 4–25 

CONNECTION inquiry, 4–25 

DUMP NP, 4–25 

ESTABLISHCALL BY CONN, 4–26 

NP, 4–26 

UTILIZATION inquiry, 4–26 

Networking configuration, 3–9 

adapter teaming, 3–17 

CNS initialization file, 3–30 

default, 3–10 

8222 3694–000 Index–5

Index 

initialization files, 3–9 

Jumbo Frames, 3–18 

MCP Networking values, 3–23 

MCP Networking values IOE-1, 3–23 

MCP Networking values IOE-2, 3–27 

sample ADAPTERS.TXT file, 3–22 

setting local MAC address, 3–16 

System Editor, 3–19 

TCP/IP initialization file, 3–30 

Networking values 

IOE-1 default, 3–11 

IOE-2 default, 3–12 

MCP, 3–23 

MCP IOE-1, 3–23 

MCP IOE-2, 3–27 

NP inquiry, 4–26 

O 

obtaining MCP Java Monitor log file, 9–19 

offload settings, TCP, 3–16 

Open Management Interface (OMI) 

installing and configuring, 3–33 

operating 


Operations Servcer 


Operations Server 


Operator Display Terminal (ODT), 2–7 

P 

password of Administrator, changing, 3–31 

PCD updates, 4–29 

PCI card BIOS/firmware updates, 8–3 

performing dynamic PCD updates, 4–29 

PING command 

verifying EVLAN path, 4–22 

PING commands, enabling 

for JProcessors, 4–30 

for MCP, 4–19 

platform boot progress, monitoring, 4–1 

Platform Console, 2–8, 4–2 , 4–3 

platform hardware 

components, 2–2 

monitoring boot progress, 4–1 

power status, 4–1 

powering off, 4–3 

powering on, 4–1 



platform management card, 2–8 

Platform Services, 4–3 

policy services 


port 

Custom Connect Facility (CCF), 5–5 

power control, 4–1 

monitoring the platform boot progress, 

4–1 

powering off platform hardware, 4–3 

powering on platform hardware, 4–1 

restarting platform hardware, 4–3 

shutting down platform hardware, 4–2 

viewing platform hardware status, 4–1 

power cycling 

cell, 9–26 

Fibre Channel I/O devices, 4–30 

powering down cell to replace failed 

hardware, 9–25 

powering off platform hardware, 4–3 

powering on platform hardware, 4–1 

powering up cell, 9–26 

preparing to use 

Ethernet Jumbo Frames, 3–18 

IEEE 802.1Q VLANS, 3–17 

problems 

mapping to a Client Access Services 

share, 9–12 

Call Home, 9–4 

Product Support website, accessing, 9–3 

R 

reboot dump, 4–26 

reconfiguring 

VSS disks, 3–2 

recovering FS6200 Server configuration data, 

9–24 

recovery actions, 9–24 

powering down cell to replace failed 

hardware, 9–25 

powering up cell, 9–26 

recovering FS6200 Server configuration 

data, 9–24 

reinstalling the entire platform, 9–27 

restarting an ISM environment, 9–27 

restarting the ISM, 9–27 

reinstalling 

entire platform, 9–27 


Index–6 8222 3694–000

elocating the MCP APPLIANCES share, 5–3 

Remote Support, 9–3 

removing Network Services, 8–4 

restarting 

environment, 4–4 

ISM, 9–27 

ISM environment, 9–27 



restarting an environment, 9–4 

restoring ePortal Specialty Engine, 5–19 

S 

sample ADAPTERS.TXT File, 3–22 

scripts 



secure access device, overview, 2–3 

secured configuration 


of environments, 4–5 

Security Policy 

JProcessor, 6–2 

JProcessor firewall rules, 6–4 

JProcessor services, 6–2 

separate CCF ports for different applications, 

configuring, 5–5 

services 


setting local MAC address, 3–16 

setting up 


shutting down 

an environment, 4–4 


SNMP 

initialization files, A–4 

software 





space on an MCP server disk, 5–3 

s-Par 


specialty engine 

ePortal, 2–7, 5–10 , 9–19 

JProcessor, 2–6, 6–1 

status 

viewing environment, 4–4 

Index 

viewing platform hardware power, 4–1 

support for MCP network adapters, 3–15 

synchronizing time, 4–20 

system commands and inquiries, 4–27 

system overview, 2–1 

systems management account password, 

changing, 3–32 

systems management, 2–7 

ePortal Manager, 2–8 

Management Card Virtual Console, 2–8 

MCP Console, 2–7 

ODT, 2–7 

patform management card, 2–8 

Platform Console, 2–8 

platform management card, 2–8 

systems management engine 

tools for Network Services, 3–14 

T 

TCP offload settings, 3–16 

TCP/IP 

connections, 3–14 

initialization file, 3–14, 3–30 , A–1 

initialization file, guidelines for building, 

A–2 

preconfigured initialization file, 3–22 

testing e-mail alerts, 4–28 

testing e-mail heartbeats, 4–28 

time synchronization, 4–20 

tips, troubleshooting for Network Services, 

9–14 

tools associated with Network Services, 

3–13 

troubleshooting 

accessing the Unisys Support Product 


monitoring Call Home event e-mails, 9–3 

obtaining MCP Java Monitor log file, 






ePortal Specialty Engine, 5–20, 9–19 

Fibre Channel I/O problems, 9–21 

gatering diagnostic information, ePortal 


gatering diagnostic information, 



8222 3694–000 Index–7

Index 


MCP Environment failure, 9–10 



Operations Server failure, 9–8 


platform hardware failure, 9–6 

problems with Call Home, 9–4 

recovery actions, 9–24 

restarting JProcessor Specialty Engine, 

9–17 

setting up a server pool, JProcessor 


s-Par, 9–8 

tips, Network Services, 9–14 

using Call Home, 9–3 

using Call Home Maintenance mode, 9–4 

using Remote Support, 9–3 

U 

Unisys Product Support, transferring 

diagnostic data to, 9–6 

updates 

accessing and downloading, 8–1 

documentation, 1–2 

driver, 8–3 

dynamic PCD, 4–29 

JProcessor Firmware Operating 

Environment, 8–4 

JProcessor Specialty Engine firmware, 

8–4 

MCP Firmware, 8–3 


PCI card BIO/firmware, 8–3 

using Interim Correction (IC) update files, 

8–1 

updating firmware 

using MIM-Update script, 8–2 

user name 

Administrator, changing, 3–31 

usercode, creating MCP, 5–1 

utility scripts 

ChangeRulesForMCPw.ps1, 4–13 




UTILIZATION inquiry, 4–26 

V 

validating installation and configuration 

Connector protocol-specific handler 

(Connector PSH), 5–6 

ePortal Business port created by Custom 

Connect Facility (CCF), 5–5 

values for configuration, 3–14 

viewing 

environment status, 4–4 

platform hardware power status, 4–1 

virtual LANs, IEEE 802.1Q, 3–17 

VSS disk, reconfiguring, 3–2 

Index–8 8222 3694–000

© 2012 Unisys Corporation. 

All rights reserved. 

*82223694-000* 

8222 3694–000

FS6200 Server System Implementation Guide - Public Support ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?