unisys ClearPath FS1770 System Implementation Guide FS December

Transcription

1 unisys ClearPath FS1770 System Implementation Guide FS December

2 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 and ClearPath are registered trademarks 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.

3 Contents Section 1. Introduction Documentation Updates Audience Media Section 2. Customizing the System Configuration Configuring a Management Workstation Configuring I/O I/O Services Configuring Storage Determining Correspondence Between MCP Storage Channels and Firmware Environment Storage Controllers Determining Correspondence Between MCP LUNs and Firmware Environment LUNs Determining Correspondence Between MCP Logical Disks and Firmware Environment LUNs Hot Reuse of Fibre Channel in a Channel Group is Not Supported Enabling and Disabling Fibre Channel Ports Configuring the Network Network Services Default Networking Configuration Using Tools Associated with Network Services Changing the Network Services EVLAN IP Address Supporting MCP Network Adapters Preparing to Use Adapter Teaming and IEEE 802.1Q Virtual LANs Preparing to Use Jumbo Frames Using the System Editor to Configure MCP Networking Sample ADAPTERS.TXT File Updating the MCP View of the Network Changing the Administrator User Name and Password Changing the Default Systems Management Account Password Configuring the MCP Environment Configuring Call Home Services iii

4 Contents Configuring and Using the Open Management Interface (OMI) Section 3. Operating the System Managing Power Viewing Platform Hardware Power Status Accessing the BMC Web Interface Powering On thesystem Monitoring Platform Boot Progress Shutting Down the System Powering Off Platform Hardware General Environment Operational Tasks Viewing the Status of the MCP Operating Environment Restarting or Resetting the MCP Operating Environment Operating the MCP Operating Environment MCP Firmware Environment Policy Policy Services Firewall Rules Network Authentication Audits MCP Firmware Environment Policy Utility Scripts Enabling MCP PING Commands through the EVLAN Connection Synchronizing Time Network Services Differences from Previous MCP Systems Configuring MCP Networking Initializing Network Services Verifying Network Services Installation and Configuration MCP Operations Interface Summary Networking Commands and Inquiries System Commands and Inquiries Call Home Services Using Maintenance Mode Testing Alerts Testing Heartbeats I/O Services I/O Time for VSS Disks Performing Dynamic PCD Updates Power Cycling or Disconnecting Fibre Channel I/O Devices iv

5 Contents Section 4. Backing Up MCP Firmware Configuration Data Backing Up MCP Configuration Data Backing Up a Logical Disk Section 5. Updates Using Interim Correction (IC) Update Files Accessing and Downloading Updates Updating Firmware Using the Master Installation Manager Update Script Updating MCP Firmware Driver and PCI Card BIOS/Firmware Updates Updating Network Services Removing Network Services Reinstalling Network Services Updating Environment Operating System Software Section 6. Troubleshooting and Recovery Submitting Trouble Reports Accessing the Unisys Product Support Website Using Remote Support Using Call Home Monitoring the Call Home Event Messages Using Maintenance Mode Problems with Call Home Restarting the MCP Operating Environment Diagnostic Tasks Generating an MCP Environment Dump Generating an MCP Firmware Environment Dump Transferring Diagnostic Data to Unisys Product Support Platform Hardware Failure Scenarios MCP Environment Failure Scenarios System Startup Problems Problems Mapping to a Client Access Services Share Fatal system Error Network Services Failure Scenarios Initiating a Dump Troubleshooting Fibre Channel I/O Problems Recovery Actions Restoring a Logical Disk Restoring the Halt/Load Unit Logical Disk File Recovering FS1770 System Configuration Data v

6 Contents Power-Cycling the System Reinstalling the System 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 vi

7 Tables 2 1. Physical Location of HBA Ports to Entries in Device Manager or Channels Listed by the SC+ ODT Command Default IP Address Values for MCP on the FS1770 System Default Networking Values on the FS1770 System MCP Networking Values Configuration Worksheet for FS1770 System MCP Networking Values Unisys-Defined Firewall Rules for MCP Functions MCP Firmware Environment Policy Audit Policy Settings vii

8 Tables viii

9 Section 1 Introduction This document describes the FS1770 System, its capabilities, hardware components, supported system and application software, and the services provided to support system operation. Documentation Updates Audience Media 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) To obtain a copy of the PLE, contact your service representative or access the current PLE from the product support website: Note: If you are not logged into the product support site, you will be asked to do so. The audience for this document includes: ClearPath system administrators ClearPath network administrators ClearPath system operators Unisys service representatives The following media are required when configuring your system: ClearPath MCP Release Software CD-ROM Interim Connections (ICs) are available at Keys media Supplemental Software Release

10 Introduction

11 Section 2 Customizing the System Configuration This section discusses issues you should consider for customizing the configuration of the FS1770 System. You should perform these tasks after your service representative sets up the system. Configuring a Management Workstation You perform systems management tasks for the FS1770 System either on the FS1770 System or on a management workstation. You can configure your management workstation by downloading the MCP Workstation package from the Unisys Product Support Site. This package contains the systems management software required to manage the FS1770 System. The ReadMe file for the MCP Workstation package contains the system requirements that your workstation must meet in order to be compatible with the FS1770 System. The ReadMe also provides installation instructions for the MCP Workstation package. To properly configure your management workstation, review the information and perform the procedures in this ReadMe file. To access the ReadMe file, follow these steps: 1. Go to the Unisys Product Support Site at 2. Log on to the website or register if you are a new customer. 3. Under ClearPath MCP Servers and Software, click FS1770 System from the MCP Mainframes list. The Support Site for your system appears. 4. Under Support Options, click Drivers and Downloads. The Drivers and Downloads page appears. 5. On the Hardware tab at the bottom of the page, click the Workstation link in the Operations Workstation category. The Workstation page appears. 6. Under Level Information, click the link for the latest release level of the software. The MCP Workstation package page appears. 7. Under Download Information, click the link for the ReadMe file (for example, MCPWorkstation-Readme.htm), open the file, and follow the instructions to install the workstation package

12 Customizing the System Configuration Configuring I/O This subsection provides topics to consider when setting up your I/O configuration on the FS1770 System. I/O Services 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 responsible for the discovery and management of devices, and performing I/O operations. They also support Plug-and-Play, which enables you to add new channels, taps, and disks to the MCP without a halt/load. These services run on MCP Operating Environment. Configuring Storage The FS1770 System supports both VSS and Logical disks. You can configure logical disks on internal or external storage. However, you can only configure VSS disks on the external disks. Note: External storage must be either all VSS disks or all logical disks. Each VSS disk on the FS1770 System supports up to eight active I/Os, which enables the FS1770 System 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. Each logical disk on the FS1770 System is created by the Logical Disk Manager (LDM) and is actually a file on the underlying operating system. Because this is a file in the file system, the underlying operating system takes advantage of memory caches that optimize the I/O throughout. Refer to the Disk and Tape Storage Systems Configuration Guide for detailed information and restrictions that must be followed when configuring disk and tape storage

13 Customizing the System Configuration Storage and Networking Ports The system supports the following customer options (6 cards) from the following choices: 0 3 NICs in addition to the LOM2 port for MCP use. 0 to 3 NICs, each can be either - Quad port, copper, 1 Gb NIC Intel i350 T4 (Unisys Style ES PCE) - Dual port, optical, 10 Gb NIC Intel X520 SR2 (Unisys Styles ES PCE [adapter] and ES PCE [optical transceivers] together) - Dual port, copper, 10 Gb NIC Intel X540 T2 (Unisys Style ES PCE) 0 3 HBAs, each can be either - Dual port, 8Gb FC Emulex LPe Dual port, 16 Gb FC Emulex LPe 16002B - SAS External Tape Controller 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 configurations with a resilient storage system, at least two HBA cards must have paths that provide access to the storage system. These paths should use the storage ports in at least two storage processors/directors within the storage system. To achieve the best resiliency in a fabric configuration, the paths must traverse two physically separate fabrics. Refer to the Disk and Tape Storage Systems Configuration Guide for details on available Fibre Channel HBAs for your configuration. I/O Management Tools The FS1770 System is equipped with the following user interfaces that you use to manage the I/O on the system. OCManager You access the OCManager installed in the MCP Operating 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)

14 Customizing the System Configuration System Editor You use the System Editor of the MCP Console to create a peripheral configuration diagram (PCD) that describes the FS1770 System storage configuration. PCD creation is fully automated on the FS1770 System. 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. For more information on System Editor, see the MCP Console Help. 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. Note: VIRTUAL channels do not possess these attributes and are created to make the presentation of the virutal disks more in line with the physical disks. In the MCP Environment Start an ODT session on the management workstation 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 LPe15004-M8, PCI Slot 5, { 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 Firmware Environment Follow these steps: 1. On the desktop, right-click the Start button and select Device Manager. 2. Expand the Storage controllers node. 3. To locate the slot, device, and port numbers, right-click an HBA and select Properties. The Properties dialogue box appears. You can find the slot, device, and port information in the General tab. Example Location: PCISlot2 (PCI bus 11, device 0, function 0)

15 Customizing the System Configuration For a dual-port HBA in slot x, there are two entries listed with the same slot number. The two entries share the same device number, one specifies function 0 and the other function Refer to Table 2 1 for the correspondences of the physical location of the cards to the HBA entries in Device Manager and the Chanels displayed by the SC+ ODT command. Table 2 1. Physical Location of HBA Ports to Entries in Device Manager or Channels Listed by the SC+ ODT Command Physical Location Slot Port Device Manager MCP X 0 Storage controllers Emulex LPe16002B, PCI Slot X, { Location: PCI Slot X (PCI bus b, device 0, function 0) 1 Storage controllers Emulex LPe16002B, PCI Slot X, { Location: PCI Slot X (PCI bus b, device 0, function 1) CHANNEL <X> IOP 1 TYPE PCI POSITION b,0,0 Emulex LPe16002B, PCI Slot X, { CHANNEL <X> IOP 1 TYPE PCI POSITION b,0,0 Emulex LPe16002B, PCI Slot X, { Determining Correspondence Between MCP LUNs and Firmware Environment LUNs Each storage device has a SCSI address assigned in Windows that represents a real connection from the HBA to the storage device. This SCSI address comprises port, bus, target, and LUN. Bus and LUN numbers are sometimes virtualized and do not represent the actual hardware values. In the IOA system MCP, the SCSI address consists of the physical bus, target, and LUN relative to a channel (HBA port). The bus and LUN values might differ from what Windows displays. The LUN value used by the MCP matches the physical LUN value in the storage system. When presenting a physical device like a Virtual Sector Size (VSS) disk or tape in the PCD, the physical LUN, SCSI Device ID, and worldwide name (WWN) of the device are included to unambiguously identify the device and validate that multiple paths to the device are really going to the same device. Because Windows LUN numbers are logical and can change based on the order of device discovery, the mapping between actual devices, such as a VSS disk, in the MCP displays and the Device Manager or Disk Manager displays in the MCP Firmware operating environment is not fixed

16 Customizing the System Configuration To view information about the disk: 1. Right click on a VSS disk in Device Manager or Disk Manager. A VSS tab appears that presents MCP information about the disk that enables you to determine which MCP disk corresponds to this device. Note that this method is not helpful for finding the Device Manager object for an MCP disk if you have a large number of disks. 2. Search the diagnostic device tree file to find the Windows objects that correspond to an MCP disk. This file is in the C:\ProgramData\Unisys\MCP Firmware\IO\DeviceMap directory in the MCP Operating Environment. When the MCP initializes an I/O device in the PCD, the I/O Services firmware components use the information from the PCD to identify the corresponding Windows device, to open it, and to use it for subsequent I/O operations. Determining Correspondence Between MCP Logical Disks and Firmware Environment LUNs Use the information in this subsection to determine the correspondence between the logical disks declared in LDM and the MCP displays and the System Editor of the MCP Console. Each logical disk is a file on the underlying operating system. It is represented as using an.asd system file.. Note: This file is considered a system file and might be hidden in the file explorer. See the section Viewing Logical Disk Files in Backing Up a Logical Disk. Logical disks are created by the Logical Disk Manager (LDM). Once a logical disk is created by the LDM, it can then be picked up by the System Editor of the MCP Console and included in the PCD. A logical disk will be seen by the MCP as a 180 byte formatted disk. It can be RC d and supports each of the different directory formats. There is only one path to a logical disk that the MCP sees (even if there are multiple paths through EMC PowerPath on external drives). The logical disk file appears as a file on the mounted drive in the file explorer. To identify the logical disk from the MCP look under the VIRTUAL channel to see the disks: CHANNEL<number>: IOP 1 TYPE VIRTUAL Virtual Controller PK 1201 LUN 1 UNISYS UNISYS M2 [0000] C:\disk0000.asd PK 1202 LUN 2 UNISYS M2 [0000] E:\TestDisk1.asd PK 1203 LUN 3 UNISYS M2 [0000] G\TestDisk3.asd PK 1204 LUN 4 UNISYS M2 [0000] G:\TestDisk4.asd

17 Customizing the System Configuration Notice that the actual file used for the logical disk is given (for example C:\disk0000.asd). From this output, the other discernible attributes are the size of the logical disk or the first several digits of the size. After the LUN number and UNISYS you will see a value ssssssm2 [0000] where s is the relative size in MB (size specified * 1,048,576 bytes) with the last 6 digits truncated. Hot Reuse of Fibre Channel in a Channel Group is Not Supported Do not disconnect a Fibre Channel device from an HBA and connect a different device to the same HBA, as the system does not support the dynamic deletion of fibre devices while the MCP is running. When these fibre devices are a part of a channel group, the MCP has a working knowledge of all paths to a device. If 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 exist: 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. Enabling and Disabling Fibre Channel Ports During the FS1770 System installation process, all unused Fibre Channel ports are disabled to allow faster environment startup times. If you connect additional Fibre Channel ports at a later time, you must enable those ports. To enable or disable Fibre Channel ports, perform the following steps 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. Notes: For a rack-mounted system, Port 0 is on the top and Part 1 is on the bottom. For a tower configuration, Port 0 is on the left and Port 1 is on the right. 2. Disable the unused port(s) as follows: a. Right-click the Start button and select Device Manager. b. Expand the Storage Controllers node

18 Customizing the System Configuration There will be two entries listed for each dual-port HBA which will all have the same slot number. c. Right-click each HBA in the list that identifies a slot number from the list of ports to be disabled and then select Properties. d. Under the General tab, find 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 four entries listed for a quad-port HBA and two entries listed for a dual-port HBA. For quad-port HBAs, the location information is displayed as follows: PCI Slot X (PCI bus Y, device N function 0) PCI Slot X (PCI bus Y, device N function 1) Note: For dual-port HBAs, only the first two entries of the location information is displayed. e. Match the recorded information for the unused HBA ports to the location information as follows: Dual Port HBA Unused HBA Port Location Information from Properties Slot X, Port 0 PCI Slot X (PCI bus Y, device N function 0) Slot X, Port 1 PCI Slot X (PCI bus Y, device N function 1) f. 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 or Disable to disable the HBA port. Continue through the list of HBA ports to match and enable or disable the slotport pairs that you recorded earlier. Configuring the Network When you initially receive the FS1770 System, a default networking environment has been established using the following pre-configured initialization files: CLEARPATH/INIT/CNS CLEARPATH/INIT/TCPIP You can use the FS1770 System without modifying the default network configuration. However, you may want to integrate the system into your existing network. The following topics describe the general steps required to configure Network Services to operate within your network environment

19 Customizing the System Configuration Network Services Network Services encompasses a set of software services that enable the network interfaces of the MCP Operating Environment. These services include: A local Enhanced Virtual LAN (EVLAN) network connection between the MCP Environment and the MCP Operating Environment. 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 MCP Operating Environment. These services run on the MCP Operating Environment. Network Processors The FS1770 System supports up to six network processors (NPs) of type VNP. Each NP supports up to eight MCP network adapter connections. The system is preconfigured with one NP, NP 210. Additional VNP devices are created for each PCI Express network adapter that is detected when System Editor is run. The additional VNPs are assigned the adapter ports of the NICs in the PCI Express slots. The MCP network adapter supports BNA and TCP/IP transfers to and from the MCP Environment. Default Networking Configuration The following text describes the default networking configuration for your system. The default host name of the MCP system for the environment is CPMCP1. You use the System Editor of the MCP Console to assign NP numbers and Line IDs to the network interfaces within the MCP Operating Environment according to the following rules. - The intra-system connections for a system are located on the initial NP defined for the MCP Operating Environment. - The Line ID assignments for the intra-system connections are pre-assigned and cannot be modified. Default Networking Values The following tables provide default networking values. Default Intra-System NP Instance Numbers The default intra-system NP instance number for the MCP Operating Environment is

20 Customizing the System Configuration Default NP Values for External Connections The NP instance and line ID number assignments for the MCP Operating Environment for add-on network interface cards (NICs) that are used for external connections for MCP use are based on the adapter SlotX/PortX of the device. The following equation is used to define the expected network processor instance numbers for the MCP Operating Environment : NP instance number = slot number For add-on NICs, the default Line ID value equals the port number of the device. Default IP Address for Intra-System Connection Table 2 lists the default IP addresses for the intra-system connections in the FS1770 System. Table 2 2. Default IP Address Values for MCP on the FS1770 System Entity Name MCP IP Address IP Address Mask Line Number MCP Operating Environment IP Address EVLAN Default MCP Operating Environment Networking Values The following tables provide a summary of the standard configuration for the MCP Operating Environment. Table 2 3. Default Networking Values on the FS1770 System PCI Slot Network Port NP Number Line ID IP Address None EVLAN None LOM Using Tools Associated with Network Services The ClearPath network administrator installs and configures Network Services using the following tools in the MCP Console and MCP Operating Environment. In the MCP Operating Environment The NIC Configuration Manager enables you to manage settings, teaming, and virtual LAN configurations for MCP connections of add-on NICs

21 Customizing the System Configuration In the MCP Console The following tools are available in the MCP Console: System Editor MCP network diagnostics For information on other helpful tools in the MCP Console, see the MCP Console Help. In the MCP Environment The following tools are available in the MCP Environment: Simple Installation program which supports installation of the network providers and supporting utilities 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 system 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 system. Refer to Appendix A, Building Network Initialization Files, for a description of these sample initialization files. 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, you may want to change these addresses if 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 for more information. Notes: The Internet Assigned Numbers Authority (IANA) has reserved Class C addresses through 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 of the FS1770 System. See MCP Firmware Environment Policy Utility Scripts for more information. Call Home functionality might also be affected. Refer to the appropriate Call Home documentation for more information

22 Customizing the System Configuration 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 highperformance technologies, the actual data transfer rate might be less than the potential maximum for that network technology. For example, a 10 Gb Ethernet MCP network adapter allows the MCP system to participate on a 10 Gb Ethernet backbone, but the MCP does not transfer data at the maximum 10 Gb Ethernet transfer rate. Network Services supports up to eight MCP network adapter connections per NP where a connection is an Ethernet port, IP over InfiniBand adapter, 802.1Q Virtual LAN (VLAN) connection, or adapter team. In essence, the ClearPath Network Services view of an adapter is the same as that of the MCP Operating Environment 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 configure the network adapter for MCP uset. 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 six network processors per MCP Operating Environment on the FS1770 System. 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. Configuring MCP Network Adapter Settings Network adapter settings are configured through the NIC Configuration Manager a tool that gathers adapter information and enables you to change such NIC settings as TCP offload capabilities, adapter team management, and VLAN management. You access the NIC Configuration Manager from the FS1770 System desktop. Setting the Local Address To override the factory-assigned MAC address of a network adapter on the FS1770 System, set the MAC address through the NW ADD CONNECTIONGROUP command in the CNS initialization file. Note: You must set the local address through the ADD CONNECTIONGROUP command, as you cannot modify the MAC address on an existing CONNECTIONGROUP

23 Customizing the System Configuration Disabling TCP Offload Settings TCP Offload Engine (TOE) options within the advanced adapter settings of a NIC are incompatible with MCP use of adapters. Turn off all TOE features on any adapters that are to be used by ClearPath MCP networking, including such features as: IPv4 Checksum Offload Large Send Offload TCP Checksum Offload UDP Checksum Offload Preparing to Use Adapter Teaming and IEEE 802.1Q Virtual LANs You use the NIC Configuration Manager to create adapter teams and virtual LANs (VLANs). For instructions on using this tool, see the NIC Configuration Manager help, available from the interface under HELP MENU. Before creating adapter teams or VLANs, review the following information to ensure that the adapter teams and VLANs are configured properly. Overview Network Services MCP network adapter software supports adapter teaming and 802.1Q VLANs. Adapter Teaming When you create an adapter team, the system and user programs see a single virtual adapter team instead of the individual adapters that make up the team. 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). Notes: Although adapter teaming can also be used to distribute network traffic across multiple adapters on the same FS1770 System, this type of team is not recommended as it offers marginal value for ClearPath MCP customers. Teaming of IP over InfiniBand adapters is not supported at this time. IEEE 802.1Q VLANs IEEE 802.1Q VLANs enable 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

24 Customizing the System Configuration If the FS1770 System 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. If the FS1770 System is to be a member of multiple VLANs over the same adapter port, then both the LAN switch and the FS1770 System must be configured. The switch connected to the FS1770 System must support IEEE 802.1Q tagging. Modifying Adapter Settings for VLANS and Teaming Perform the following steps to modify the adapter settings for VLANs and teaming: 1. 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. 2. On the FS1770 System, use the NIC Configuration Manager to build adapter teams and configure VLANs. You must have administrative privileges to use the NIC Configuration Manager. For more information on using this tool, see the NIC Configuration Manager help, available from the interface under HELP MENU. Note: Before creating adapter teams or VLANs, you must use the System Editor to remove all MCP assignments from the adapters that you want to modify and save the changes. For more information on using the System Editor, see Using the System Editor to Configure MCP Networking. 3. For each VLAN defined and each adapter team defined, a new adapter is created. Use the System Editor to assign the new adapters to NPs and line IDs on the MCP. For more information on using the System Editor, see Using the System Editor to Configure MCP Networking. 4. Update the CNS and TCP/IP initialization files on the MCP to reflect the changes to the line availability (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 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 within ClearPath MCP Networking. You must perform modifications on the system where the adapter exists

25 Customizing the System Configuration Configuring Jumbo Frames Perform the following steps to configure jumbo frames on an adapter: 1. Start the NIC Configuration Manager. 2. Right-click the adapter that you want to modify, and click Settings Select the *JumboPacket property. 4. Select one of the values in the drop-down menu. The proper value depends upon the capabilities of your network switching equipment. 5. Click Apply, and then click OK. 6. 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 connections respectively Notes: Communications between a jumbo-capable and a jumbo-incapable end-system is generally not a problem, as a common frame size is negotiated between the systems when they establish a dialog. This situation applies to TCP/IP, BNA, and BIP protocols. Communications between a jumbo-capable and a jumbo-incapable end system is a problem for protocols without connections, such as UDP and ICMP, as 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. 7. From an ODT, restart the MCP Networking services that you updated as follows: a. Enter the following commands to shut down the services that you updated: NW TCPIP - NW CNS - NW BNA - b. Enter the following commands to restart the services: NW TCPIP + <TCP/IP initialization file name> NW CNS + <CNS initialization file name> NW BNA + <BNA initialization file name>

26 Customizing the System Configuration Using the System Editor to Configure MCP Networking If you need to modify the existing configuration of MCP networking on your FS1770 System 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, Building Network Initialization Files, 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. 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. You can update the following networking characteristics using the System Editor: 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. The EVLAN IP address mask. Enabling or disabling a line for MCP. Deleting a network processor node with no lines. Creating a new network processor node. Operational Rules for the System Editor The following rules of operation apply to your use of the System Editor: 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. System Editor does not assign values to I/O devices within the range of 200 to 299 by default. This range is reserved for network processors. The entry for the EVLAN connection appears on the first designated network processor. The entry for the EVLAN connection has a defined line number that cannot be modified. LAN on Motherboard (LOM) 2 connection is assigned to the first designated Network Processor, Line 2 by default

27 Customizing the System Configuration The remaining network processors show the connections (on NICs and virtual NICs) that are visible. Checking or unchecking of lines or network processor instances determines whether or not that adapter is bound to the MCP networking service. Do not check lines or network processors that are not to be used by the MCP. Note: The FS1770 System networking allows adapters to be used exclusively as MCP network adapters. Configuring MCP Networking Using the System Editor Perform the following steps to configure MCP networking: 1. Launch the MCP Console. 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: Note: Before editing an active PCD file, halt the MCP. 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, skip to step 8. Otherwise, continue with step To modify a network processor object, locate the NP object you want to modify and perform the following actions, as appropriate: To modify the network processor instance identifier, select the NP object and update the NP Number field on the Properties panel. To remove the NP from the MCP Environment, clear the check boxes for all of the line numbers of that NP. To assign a line number to be used with an NP in the MCP Environment, select the check box for the line number of that NP

28 Customizing the System Configuration 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 MCP Operating Environment. A value entered here is stored in the registry of the MCP Operating Environment 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 MCP Operating Environment 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 MCP Operating Environment, 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 MCP Operating Environment is required. 10. Click Yes to reboot the MCP Operating Environment. The networking settings are written to the registry of the affected MCP Operating Environment. 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 MCP Operating Environment 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. For more detailed information on System Editor for network configuration, refer to the MCP Console Help

29 Customizing the System Configuration Sample ADAPTERS.TXT File The MCP Networking configuration utility generates an ADAPTERS.TXT file. 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 ADAPTERS.TXT file adapter entry adheres to the following format: <adapter display name> (<adapter component name>)assigned to NP <network processor identifier> LineID <line identifier>pci Slot <PCI slot/port identifier> The file sample contents for a NIC adapter in slot 1 and slot 5 follow. Adapter Assignments Thursday October 30, :48:07 PM MCP Timezone Hostname: EVLAN IP address: / Ethernet (EVLAN) Assigned to NP 210, LineID 0, PCI Slot NIC2 (Intel(R) Gigabit 2P I350-t LOM #2) Assigned to NP 210, LineID 2, PCI Slot 0/2 SLOT 1 Port 1 (Intel(R) Ethernet Server Adapter I350-T4) Assigned to NP 211, LineID 1, PCI Slot 1/1 SLOT 1 Port 2 (Intel(R) Ethernet Server Adapter I350-T4 #2) Assigned to NP 211, LineID 2, PCI Slot 1/2 SLOT 1 Port 3 (Intel(R) Ethernet Server Adapter I350-T4 #3) Assigned to NP 211, LineID 3, PCI Slot 1/3 Assigned to NP 211, LineID 4, PCI Slot 1/4 SLOT 1 Port 4 (Intel(R) Ethernet Server Adapter I350-T4 #4 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. For more information on these preconfigured values, refer to Appendix A, Building Network Initialization Files. 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 the FS1770 System. 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

30 Customizing the System Configuration Table 2 4. MCP Networking Values Configuration Worksheet for FS1770 System MCP Environment Preconfigured Value New Value Host Name TCP/IP Domain Name CPMCP1 CPMCP1.CUSTOMER.COM Table 2 5. MCP Networking Values MCP Environment Preconfigured Value New Value NP number NP 210 Must match the value entered in the Networking Configuration portion of System Editor. MCP Adapter #0 EVLAN IP Address Do not change. Note: Unisys recommends that you do not change the IP address and subnet mask for the EVLAN adapter unless 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. Subnet Mask Do not change. LAN Local Address (line 0) 08000B Note: Line 0 is reserved for the EVLAN adapter. If you change the LAN Local Address for the MCP EVLAN adapter, do not use 08000B as the address. The EVLAN adapter in the MCP Operating Environment already uses this address. Line-ID

31 Customizing the System Configuration Table 2 5. MCP Networking Values (cont.) MCP Environment Preconfigured Value New Value NP number NP 210 Must match the value entered in the Networking Configuration portion of the System Editor. MCP Adapter #1 IP Address Subnet Mask LAN Local Address (line 1) *Default Line-ID 2 Notes: Because each of the MCP EVLAN adapters resides on a separate virtual LAN, the same LAN Local Address can be used for each adapter. 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) Changing the Administrator User Name and Password The user name, called Administrator, is the built-in administrator account for the MCP Operating Environment on the FS1770 System. It is one of the most targeted account names by malicious programs and hackers. As a security precaution, rename this account to another less common name. During the initial installation of the FS1770 System 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 FS1770 System Overview and Planning Guide for various environments. If this change has not been made, make the change. Unisys recommends that you set a password policy to change the password from time to time. Changing the Password Follow these steps to change the Administrator account password: 1. Right-click the Start button and select Control Panel. 2. In View by box, click Category

32 Customizing the System Configuration 3. Under User Accounts, click Change Account Type. 4. Select the Administrator account. 5. Click Change the password. 6. Type the current password in the Current password box. 7. Type the new password in the New password box and retype it in the Confirm new password box. 8. (Optional) Type a hint in the Type a password hint box. 9. Click Change password, and close the Change Password window. Changing the Account Name Follow these steps to change the Administrator account user name: 1. From the task bar, start Server Manager. 2. Open the Tools menu and select Local Security Policy. 3. Open Security Settings and select Local Policies. 4. Under Local Policies, select Security Options. 5. Under Security Options, open Accounts: Rename administrator account. 6. Enter a new name for the administrator account, and click Apply and OK. 7. Close the Local Security Policy and Server Manager windows. 8. Log off the system and log back on using the new administrator account name and password. Changing the Default Systems Management Account Password Systems management software needs to communicate with software running throughout the system. This communication is protected through the use of an internal user account, UIS_SysMgmt. The 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. 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

33 Customizing the System Configuration 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 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 FS1770 System 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. Some of the procedures in the MCP Implementation Guide can be completed by Unisys support when the system is initially installed. Configuring Call Home Services Call Home provides automatic alert messages when hardware and softwarerelated events occur on the FS1770 System that requires attention. Call Home alerts are automatically sent to Unisys Support with a copy sent to up to three 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 FS1770 System 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

34 Customizing the System Configuration Configuring and Using the Open Management Interface (OMI) The FS1770 System offers an open-standards-based management interface through which you can manage the system. The OMI is configured automatically during the MCP Firmware installation and includes a preconfigured user account in the MCP Operating Environment. The account name is OMIUser and the default password is 4Forward@Status. The OMIUser account is disabled by default. If you wish to use OMI management, you must first enable the OMIUser account. Once you enable the account, you can change the password according to your data center security policies. Unisys provides an OMI SDK that contains information on the OMI capabilities as well as customizable samples of PowerShell scripts demonstrating various management tasks, including but not limited to: System Power On System Power Off Diagnostics Collection Halting/Loading MCP Monitoring MCP State You can find OMI information for the style and release level of your system on the Unisys Product Support website at

35 Section 3 Operating the System This section discusses issues you should consider in the operation of your FS1770 System. Managing Power This subsection discusses considerations for managing power on your FS1770 System. Viewing Platform Hardware Power Status You can view the power status of the platform hardware using one of the following methods. From the MCP Console, within the Component View tab, you can see the power status. View the front panel of the platform hardware. The LED is lit with a green light and the LCD light is lit with a blue light. Access the BMC web interface. After logging in, click the Power tab. View the power status that is displayed on the screen. Use a PowerShell script. See Configuring and Using the Open Management Interface (OMI) for more information. Accessing the BMC Web Interface You can access the BMC web interface using one of the following methods. From the MCP Console 1. Click the Component View tab. The MCP Platform node appears if you have a connection to the system. 2. Right-click on the MCP Platform and select Launch BMC Web Interface. 3. If the system node shows disconnected, right click the System node and select Power On. The Baseboard Management Card Connect pop-up appears. 4. If the BMC IP Address is not filled in, enter the BMC IP address and click OK

36 Operating the System Internet Explorer appears and displays the BMC log-in screen. From Internet Explorer 1. Enter the BMC IP address and press Enter. 2. If a screen appears stating, There is a problem with this website s security certificate, click Continue to this website (not recommended). 3. After the BMC log-in screen appears, enter your credentials. Powering On thesystem Powering on the system uses the same process as powering on the platform hardware. You can power-on the platform using one of the following methods. Press the power button Use the BMC web interface to remotely power on the platform hardware. Use a PowerShell script. See Configuring and Using the Open Management Interface (OMI) for more information. As the platform boots, you can monitor its progress using the methods described in Monitoring Platform Boot Progress. Monitoring Platform Boot Progress You can use the following methods to monitor the progress of the platform boot progress: LCD Panel You can use the LCD panel 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 boots, the LCD displays the system name. Virtual Console After the System BIOS starts booting, you can use the platform management card Virtual Console to view the messages as it boots through the system BIOS and the BIOS on other hardware on the platform (for example, internal disk controller). To launch the Virtual Console for the platform, access the BMC web interface as described in the Accessing the BMC Web Interface subsection 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. PowerShell script See Configuring and Using the Open Management Interface (OMI) for more information

37 Operating the System Shutting Down the System You can shut down the system gracefully or forcefully. Using one of the following shutdown method also powers off the platform. Note: Before you shut down the system, halt the MCP using the MCP Console. If you plan to perform maintenance on the system while it was down, set the system to Call Home maintenance mode. Graceful Shutdown To gracefully shut down the system: 1. Access the MCP Console and from the Component View tab. 2. Right-click either the System node or the MCP Platform node. 3. Click Shutdown (Graceful). Forceful Shutdown To forcefully shut down the system: 1. Access the MCP Console and from the Component View tab. 2. Right-click either the System node or the MCP Platform node. 3. Click Shutdown (Forceful). You can also use a PowerShell script to shut down the system. See Configuring and Using the Open Management Interface (OMI) for more information. Powering Off Platform Hardware You can power-off the platform hardware using either of the following methods but only use them if the methods listed under Shutting Down the System 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. See Accessing the BMC Web Interface for more information. Note: This should only be done when the platform has been shutdown. General Environment Operational Tasks The following tasks can be performed on the environment

38 Operating the System Viewing the Status of the MCP Operating Environment Access the Platform Console through the BMC web interface to view the status. You can also view the MCP Operating Environment from the Component View of the MCP Console. Restarting or Resetting the MCP Operating Environment Restarting the MCP Operating Environment is the same as performing a graceful shutdown followed by a power on action. Resetting the MCP Operating Enviornment is the same as performing a forceful shutdown followed by a power on action. Note: Before you restart or reset the MCP Operating Environment, perform the following actions: Halt the MCP using the MCP Console. If Call Home is configured, set the system to Call Home Maintenance Mode to prevent Call Home events from being generated for your scheduled restart operation. To restart or reset the environment, right-click the environment in the Component View of the MCP Console, and select Restart or Reset. Operating the MCP Operating Environment You monitor and control the state of the MCP Operating Environment from the MCP Console either on the FS1770 System or on a management workstation. For more details, refer to Managing the MCP Environment in the MCP Console Help. To perform operational commands within the MCP Environment, access an MCP ODT either from the FS1770 System or a management workstation. 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 system as follows: Unnecessary services are disabled based on the functionality defined for the MCP Operating Environment. Firewall rules are created or modified to enable only necessary connections for the MCP Operating Environment. Settings for LAN Manager and IPv6 are selected to support functionality required by the MCP Operating Environment. The audit policy is defined

39 Operating the System Policy Services The MCP Firmware Environment Policy enables services to support the following features and options. Some other services that support system roles and features, but are not mentioned in the following list, are disabled: Microsoft Network Client Domain Name System (DNS) Client Remote Desktop SNMP Local Application Installation 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 systems 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 enable the following outbound connections: 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: By default, ping commands from remote computers cannot reach the host of an environment, not even those sent from the MCP. If you need to enable pings, refer to Enabling MCP PING Commands through the EVLAN Connection for more information. Domain Name System (DNS) Client This feature is only supported by the DNS Client service. 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

40 Operating the System Remote Desktop This feature is supported by three services: Remote Desktop Services, Remote Desktop Configuration, and Remote Desktop Services UserMode Port Redirector. SNMP The SNMP service is enabled only on the MCP Operating Environment to allow the use of SNMP traps by the MCP Firmware. The following firewall rules 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 the Windows Installer service. 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. Firewall Rules 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 3 1. Table 3 1. Unisys-Defined Firewall Rules for MCP Functions Unisys ODT (TCP-In) Firewall Rule Name Unisys Call Home n (TCP-In), where n is the instance number Unisys Windows Remote Management (HTTPS-In) Description This rule enables inbound connections on TCP ports for remote WebEnabler ODT connections. Each port corresponds to an ODT unit. This rule enables inbound connections on TCP port for Call Home messages across the EVLAN This rule enables secured Remote Management over TCP port

41 Operating the System Network Authentication The LAN Manager authentication level is set to Send NTLMv2 response only - Refuse LM & NTLM. Notes: If necessary, you can change this setting on the MCP Operating Environment by running the SetLMCompatibility.ps1 script. The MCP Environment is preconfigured with NTLMv2 authentication enabled. If you decide to disable NTLMv2 authentication in the MCP Environment, refer to the Client Access Services Authentication Changes topic 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. Audits 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. To support the potentially large amount of auditing events, Security Event Log size is set to 2 GB. You can modify the auditing policy and the Security Event Log size according to your corporate policy and specific usage characteristics. The MCP Firmware Environment Policy settings are listed in Table 3 2. Table 3 2. MCP Firmware Environment Policy Audit Policy Settings Event Name Security Log Records account logon account management directory service access logon/logoff object access policy change privilege use process tracking system events Success, Failure Success Success Success, Failure Success Success Not audited Success Success, Failure (except the Filtering Platform Connection and Other Object Access Events subcategories)

42 Operating the System MCP Firmware Environment Policy Utility Scripts The FS1770 System is equipped with utility scripts that you use to manage the MCP Firmware Environment Policy. Written with PowerShell, these utility scripts enable you to make certain firewall adjustments and to restore the environment to a previous state. The scripts are stored in the C:\Program Files\Unisys\Security folder on the MCP Operating Environment. Note: 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. The utility scripts include: UnisysHarden_Rollback.ps1 Use this script for restoring to a previous environment. UnisysHarden.ps1 If you performed a rollback to an unhardened state, use this script to re-harden the system. SetLMCompatibility.ps1 Use this script to change the LAN Manager authentication level. The following text further describes the purpose and syntax of each script. Note: Do not download and execute scripts from unknown sources. Doing so might put your system at security risks. 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, use the UnisysHarden_Rollback.ps1. Once you complete your troubleshooting tasks, ensure that you reapply the most recent policy using the UnisysHarden.ps1 script. 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. 2. To begin a PowerShell session, right-click the PowerShell icon on the taskbar and click Run as administrator. 3. On the User Account Control prompt, click Yes. The PowerShell Console window appears. 4. Access the Security subfolder by typing the following command: cd "C:\Program Files\Unisys\Security" Note: The preceding command input is not case-sensitive. Ensure that either double or single quotation marks surround the path name

43 Operating the System Then, press Enter. 5. At the PowerShell prompt, type.\unisysharden_rollback.ps1 Note: The.\ notation before the script name denotes the current path. Without this notation, PowerShell cannot locate the script file. Then, press Enter. A dialog box appears listing 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. 6. Select the folder containing the data to which you want to return. 7. Click the Roll Back button to roll back the policy. If the selected folder contains any saved scheduled tasks, these tasks are restored. If the selected folder does not contain any saved scheduled tasks, a warning appears and the script rolls back the other items. A message appears when the roll back action completes successfully. You can find a log of the actions of the script at C:\ProgramData\Unisys\Installation\Hardening_Rollback.txt. UnisysHarden.ps1 Script To execute the UnisysHarden.ps1 script, perform the following steps on the MCP Operating Environment: 1. To begin a PowerShell session, right-click the PowerShell icon on the taskbar and click Run as administrator. The PowerShell Console window is displayed. 2. Navigate to the Security subfolder. You can find a log of the actions of the script at C:\ProgramData\Unisys\Installation\Hardening_Rollback.txt. 3. At the PowerShell prompt, run the UnisysHarden.ps1 script using the following syntax:.\unisysharden.ps1 Note: The.\ notation before the script name denotes the current path. Without this notation, PowerShell cannot locate the script file. The script runs and returns to the Windows PowerShell prompt when finished. SetLMCompatibility.ps1 Script By default, the LAN Manager authentication level of the system is set to Send NTLMv2 response only - Refuse LM & NTLM. If this causes a problem with the operation of the system, you can run the SetLMCompatibility.ps1 script to set a lower authentication level

44 Operating the System To execute the SetLMCompatibility.ps1 script, perform the following steps on the MCP Operating Environment: 1. Log on with the Administrator account. 2. To begin a PowerShell session, right-click the PowerShell icon on the taskbar and click Run as administrator. 3. On the User Account Control prompt, click Yes. The PowerShell Console window appears. 4. Navigate to the Security subfolder. You can find a log of the actions of the script at C:\ProgramData\Unisys\Installation\Hardening_Rollback.txt. 5. At the PowerShell prompt, type.\setlmcompatibility.ps1 Note: The.\ notation before the script name denotes the current path. Without this notation, PowerShell cannot locate the script file. Then, press Enter. The system displays the current LAN Manager authentication level and offers a choice of six compatibility levels, ranging from 0 to Choose the authentication level that you want to use. The script makes the appropriate modifications to the system. 7. Reboot the system for the changes to take effect. You can find a log of the actions of the script at C:\ProgramData\Unisys\Installation\Hardening_Log.txt. Enabling MCP PING Commands through the EVLAN Connection Notes: Perform the following procedure only if you suspect connection problems between the MCP and I/O subsystem. If you implement this firewall rule to debug the system, delete or disable the rule when you finish the debugging process. Failure to do so would reduce the security of the system. 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 MCP Operating Environment, create a customized firewall rule to allow PING commands through the EVLAN connection, as follows:

45 Operating the System 1. Log on to the MCP Operating 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, For the Remote IP addresses, select These IP addresses, click Add, and type the MCP host EVLAN IP address, Click Next. 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

46 Operating the System Synchronizing Time Time synchronization for the FS1770 System is MCP-centric. Time zone and daylight saving time (DST) settings should never be directly assigned in the MCP Operating Environment. Time changes should be always be performed from the MCP Environment (for example, using the Time Reset system command, TR <time>). After the initial load of the MCP, you set the correct time on the MCP Environment. The MCP Operating Environment automatically synchronizes with the time you set for the MCP Environment. Whenever the time between the MCP Operating Environment and MCP Environment differs by more than ten seconds, the MCP Operating Environment time is updated to match the MCP Environment time. Note: Once the MCP Operating Environment has synchronized its time settings with the MCP Environment, some time and time zone related displays in the MCP Operating Environment may look incorrect. For example,in the Date and Time applet, the time zone of the MCP Operating Environment will be displayed as (UTC-12:00) International Date Line West. When you click the time and date display on the taskbar, the message: Your current time zone is not recognized. Please select a valid time zone using the link below appears. These settings and messages are expected and no attempt should be made to modify them or any other time or time zone settings from the MCP Operating Environment. Network Services This subsection provides the following operating information for VNP network processors in the FS1770 System: 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 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 System Commands and Inquiries 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 the FS1770 System. Information about installation is discussed in

47 Operating the System Section 5, Updates. Information about configuration is covered in Section 2, Customizing the System Configuration. 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 more information. Network Services diagnostic information is automatically zipped and placed into the dumps directory on the MCP Platform. Additional information about Network Services diagnostics is included in Section 6, Troubleshooting and Recovery. Configuring MCP Networking MCP networking configuration is performed by Unisys before you receive your FS1770 System. 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 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 + <CNS initialization file name> c. Enter the following command to initiate the latest version of TCP/IP: NW TCPIP + <TCP/IP initialization file name> d. If necessary, enter the following command to initiate the latest version of BNA (Heritage Network Services): NW BNA + <BNA initialization file name> 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

48 Operating the System Notes: The PING operation must be performed from the MCP Operating Environment. Refer to Table 2 3 for default IP address and Line ID values for the MCP Operating Environment. 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 from a command prompt on the MCP Operating Environment and verify that you receive a response. 2. Verify that the FS1770 System responds. For example Pinging with 32 bytes of data: Reply from : bytes=32 time=10ms TTL=62 If the system does not respond, continue with the following procedure If the PING Command Is Unsuccessful. If the PING Command Is Unsuccessful Notes: 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. 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 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:

49 Operating the System IPADDRESS / NP-DEVICE 210, LINEID 0, PHYSICAL ADDRESS HEX 08000B AUTOCONFIGURATION FALSE, DUPLICATEADDRESSDETECTIONTRANSMITS 0, VISIBLE -, If the IP address is different but the NP-DEVICE and LINEID match, there might be a mismatch in the IP address of the MCP Environment and the EVLAN adapter definition in the MCP Operating Environment. Refer to Table 2 3 for comparison with default IP address and Line ID values. If the Physical Address is all zeroes ( ), 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 2 2. If the IP address is correct and the Physical Address is correct, check the configuration of the EVLAN adapter in the MCP Operating Environment. 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 Ethernet 2: Connection-specific DNS Suffix. : Description : Unisys Network Services EVLAN TCP Adapter Physical Address : B DHCP Enabled : No Autoconfiguration Enabled.... : Yes IPv4 Address : (Preferred) Subnet Mask : Default Gateway : NetBIOS over Tcpip : Enabled The IP address should be the MCP Operating Environment address for the EVLAN adapter from Table 2 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 System Editor. 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. Attributes for EVLAN and MCP Network Adapters Use the following attributes for configuring network connections for EVLAN and MCP network adapters through a VNP:

50 Operating the System 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 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 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 CNS Initialization file 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 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 = , 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 = )

51 Operating the System Networking Commands and Inquiries CNS CLEAR NP <device number> 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 <connection/connection group name> 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 <device number> [<family name> LOCAL [To NP] REBOOT] Use this command to request a dump of data of the network processors (NPs) in a FS1770 System. 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_<timestamp> is placed in a separate folder on the MCP Operating Environment 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 may not be readily accessible for collection by the operator. Refer to Section 6, Troubleshooting and Recovery, for more information. All VNP devices are dumped when the Dump NP command is issued for any one of the VNPs in the FS1770 System, regardless of the NP number. Local Dump 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

52 Operating the System Reboot Dump 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 Usage Do not specify <family name> in the command syntax. The data is dumped to the device. ESTABLISHCALL BY CONN <connection/connection group name> Use this command to prepare the specified connection or connection group to initiate an outgoing call. Example NW EC BY CONN CG_ICP_2111 NP 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 NW NP NW NP 211 UTILIZATION Use this inquiry to view the percentage of processor capacity and memory being used (processor utilization and memory utilization)

53 Operating the System For Network Services devices, the reported information is the: Total processor utilization reported by the MCP Operating Environment. Amount of physical memory in use within the MCP Operating Environment. 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 FS1770 System should report nearly identical processor utilization and memory utilization. Example NW UTIL System Commands and Inquiries The following system commands do not apply to FS1770 System Network Processors. OL CTL <device number> OL PORT <port number> READY NP <device #> SAVE NP <device #> UR PORT <port number> UR CTL <control number of NP> UR NP<device number> The following system commands do not apply to FS1770 System Network Processors. However, an alternate command is available that provides similar functionality. CLEAR NP <device number> Refer to the CNS CLEAR NP <device number> system command for similar functionality. OL NP <device number> 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 alert messages when hardware and softwarerelated events occur on the FS1770 System that requires attention. Call Home alerts are automatically sent to Unisys Support with a copy sent to up to three addresses that you designate. Unisys Support responds accordingly with the appropriate action

54 Operating the System 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 FS1770 System 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. This subsection addresses tasks you can perform to ensure Call Home services is operational. Using Maintenance Mode When Call Home services are in Operational mode, Call Home is fully operational and sends alerts to the Support Center and the configured customer addresses. When Call Home services are in Maintenance mode, Call Home does not send alerts to the Unisys Support Center and the configured customer 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 Alerts You can manually send an alert message to the Unisys Support Center. This can be used to test the Call Home alert configuration on the FS1770 System and the communications path to and from the Unisys Support Center. Refer to the MCP Console Help for details. Testing Heartbeats You can manually send a heartbeat message to the Unisys Support Center. This can be used to test the Call Home software configuration on the FS1770 System 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 SERVICE <Service Type> (possible Service Types: CNS, TCPIP, BNA, CRYPTO, SCAGENT) 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

55 Operating the System With the exception of SERVICE, the following system commands use the new I/O terminology in displays and command input on the FS1770 System: ACQUIRE FREE OL RF SC UR While the SC- and SC+ commands display SERVICE Types, they are not valid targets for the above commands like ACQUIRE/FREE. Service Types like CNS use a special feature (Service Units) of the IOP Firmware. Service Units allow custom firmware components (called Service Providers) to be used by MCP host software components (called Service Consumers) to offload and support a number of special I/O services like CNS, TCP, and CRYPTO. Refer to the System Commands Reference Manual for more information on these commands.: I/O Time for VSS Disks The FS1770 System 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 the system, especially when doing a heavy I/O load to VSS2 disks. However, this can cause I/O time reported on the FS1770 System 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 FS1770 System. 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 FS1770 System 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 such statistics as 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 MCP Operating Environment is more flexible on the FS1770 System 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:

56 Operating the System 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. 1. Connect the new devices and ensure that they have been discovered by the MCP Operating Environment. In some cases, such as adding new LUNs to a storage system, you must force a scan for the hardware changes outboard of each HBA that should have new devices visible to it. This can be accomplished in Device Manager by running Scan for Hardware Changes or from the System Editor of the MCP Console in the View tab and using Rescan. 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 MCP Operating Environment. After powering down or disconnecting an I/O device, give the MCP Operating Environment 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 while completing one of these actions, follow the procedure outlined in Troubleshooting Fibre Channel I/O Problems to attempt to recover the device

57 Section 4 Backing Up MCP Firmware Configuration Data This section provides information on backing up and recovering your system configuration data. You might want to perform a backup at a time when all MCP configuration has been completed and the system is fully operational or afterwards when significant alterations have been made to the initial MCP configuration. You can use this backup to restore the system in the unlikely event of a problem in which the information has been lost and requires the reinstallation of the operating environment. You can back up the critical configuration data to removable or external media. A 32 GB USB thumb drive is shipped with the system to help you maintain backup copies of critical configuration data. In addition to using this USB device as backup media when running the Backup from the Tools menu of the MCP Console, it may also be used to back up the halt/load unit logical disk file. Backing Up MCP Configuration Data Perform the following backup procedure from the MCP Console when you have completed your initial system configuration: Notes: Repeat the backup process each time you modify your system configuration. You must perform this procedure from the MCP Console running directly on the FS1770 System. You cannot back up the configuration from an MCP Console running on a management workstation. 1. From the Tools menu, click Backup Configuration. The Browse for Folder dialog appears. 2. Select a destination folder or create a new folder for the backup files. 3. Click OK to initiate the backup. A subfolder called NGMbackup automatically appears in the folder that you selected or created. 4. When prompted, if creating a new folder, enter Y to confirm the folder creation. If the

58 Backing Up MCP Firmware Configuration Data folder already existed, confirm that the script should delete all existing files in the destination folder. If old files are not deleted, the script overwrites files that have the same name. After a few seconds, a message confirms that the backup was successful. 5. Press any key to complete the backup. For more information on performing a backup from the Tools menu in the MCP console, refer to the MCP Console Help. Backing Up a Logical Disk MCP Logial Disk technology uses the native Windows NT File System (NTFS) as the base file system and creates pseudo MCP volumes that actually exist as large files under NTFS. These files have a file extension of.asd and are found at the root level of an NTFS partition. For example: D:\disk0001.asd or D:\diskxxx.asd. Unisys recommends backing up MCP data on MCP disks using tools provided in the MCP Environment. However, if the MCP Environment is not available, the MCP halt/load disk image may be backed up manually from the MCP Operating Environment. Note: Following a backup of the MCP halt/load disk image, the data in the image immediately becomes out of date when the MCP continues to run using the halt/load logical disk. This fact must be taken into consideration when later relying on the back up image to restore the halt/load disk image. Viewing Logical Disk Files Because logical disk files have the SYSTEM and HIDDEN file attributes, they might not appear in a standard folder listing from the command prompt or in the Windows Explorer. To see the.asd files, follow this procedure: 1. Open Windows Explorer. 2. Go to the View menu item and click Options. The Folder Options dialog box appears. 3. In the Folder Options dialog box, click the View tab. 4. Under the Advanced settings option: a. Select the Show hidden files, folders, and drives setting option. b. Clear the Hide protected operating system files (Recommended) setting option. 5. Click OK

59 Backing Up MCP Firmware Configuration Data 6. To hide the files again after the backup, under the Advanced settings options from Step 4: a. Clear the Show hidden files, folders, and drives setting option. b. Select the Hide protected operating system files (Recommended) setting option. Performing a Logical Disk Backup If your halt/load unit is on a logical disk, for example on the internal logical disk, complete the following procedure to back up the halt/load unit. 1. From the MCP Console, halt the MCP. 2. Open System Editor, then open the active PCD file and left-click on the pack designated as the Primary Halt/Load Unit. 3. Under the Properties pane of the halt/load unit, record the logical disk File name, including the path assigned to the disk (for example: Logical Disk). 4. Open Windows Explorer and navigate to the location containing the.asd file. 5. Copy and Paste the.asd file to the backup media. Note: You can also copy and compress the.asd file to conserve space on the backup media. However, you cannot operate the system with a compressed halt/load disk image. For more information on performing a backup from the Tools menu in the MCP Console, refer to the MCP Console Help

60 Backing Up MCP Firmware Configuration Data

61 Section 5 Updates This section discusses how to update the various components of your FS1770 System. Using Interim Correction (IC) Update Files Interim Correction (IC) update files for your FS1770 System 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 - MCP Platform components - Other third-party updates Accessing and Downloading Updates Perform the following steps on any virus-protected 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 FS Series category, select FS1770 System from the MCP Mainframes list. The FS1770 System Support Site page is displayed

62 Updates 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 C:\Transfer directory. 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 to install firmware updates to your system. 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, follow these steps: 1. Download the update zip package from the Unisys Product Support website. 2. Extract the contents of the package into C:\Unisys\Installation. 3. To begin a PowerShell session, click the PowerShell icon. 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. Some updates require a reboot. These reboots are automatically initiated by MIM-Update. MIM-Update will automatically restart after you log on again after a MIM-Update installed reboot. Updating MCP Firmware MCP Firmware updates are installed through the MIM-Update process. The following types of updates are available for MCP Firmware:

63 Updates 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 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 MCP Operating Environment, 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. Network Service Firmware updates are installed through the MIM-Update process. Refer to Updating Firmware Using the Master Installation Manager Update Script for more information on that processing. MCP Firmware updates are included in FS1770 System Network Services update packages. Consequently, there is no need to download and install MCP Firmware ICs independent of the Network Services update process. Every Network Services update is cumulative so it can be used to update any prior Network Services installation. Removing Network Services Normally, Network Services runs automatically when your FS1770 System 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 uninstallation of Network Service firmware

64 Updates Reinstalling Network Services Network Services can be reinstalled without any special considerations. The steps are the same those listed in Updating Network Services. Updating Environment Operating System Software Unisys does not restrict the customer from installing third party applications into the FS1770 System. However, if support is requested from Unisys for a problem, Unisys may require that the third party software be removed and the problem reproduced. Unisys disclaims any and all responsibility and liability (and, by changing firmware you agree that Unisys is not responsible or liable) for any changes to the Unisys firmware other than changes made by or on behalf of Unisys

65 Section 6 Troubleshooting and Recovery This section contains a list of problems that you might encounter during installation, configuration, and use of the MCP Environment and Network Services software. This section also provides details for recovering your FS1770 System 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 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 FS1770 System, 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 then Start to collect dumps. The system SUMLOG Service Tag number for the 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

66 Troubleshooting and Recovery 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 FS1770 System, Issues with the Network Services firmware component should be written against the NX/Net product. Issues that appear to be problems with other FS1770 System firmware components should be written against the FS1770 System 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 thefs1770 System 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 the MCP Operating Environment 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 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 to [email protected] indicating the name of the files, the UCF contact telephone number, and the name of the FTP system. Accessing the Unisys Product Support Website The Unisys Product Support website for the FS1770 System contains valuable documentation, Technical Information Bulletins (TIBs), and links to product updates. You can also register for notification of TIBs and new documents as they become available. Perform the following steps 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 FS Series category, select FS1770 from the MCP Mainframes list

67 Troubleshooting and Recovery The FS1770Support 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. Remote Support significantly reduces the time required to diagnose a problem on a remote system and 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 interact 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 Messages Call Home events can be generated by the MCP, MCP Firmware, and the platform management cards. The events are converted to messages that are sent to the Unisys Support Center and up to three client-designated addresses. These messages have a Subject of Call Home Alert, followed by an ID number and the system serial number. They contain information in an XML format that includes items 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 messages to take necessary action on possible system problems. Using Maintenance Mode Before performing hardware or software maintenance on the FS1770 System, 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 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

68 Troubleshooting and Recovery 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, Platform Environment diagnostics might also prove useful. Refer to the MCP Console Help for information on performing these dumps. Restarting the MCP Operating Environment To restart the MCP Operating Environment, access the Component View tab in the MCP Console, right-click the MCP Operating Environment 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 the FS1770 System. Generating 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

69 Troubleshooting and Recovery Refer to the MCP Console Help for details on performing an MCP Environment Dump. Generating an MCP Firmware Environment Dump An MCP Firmware Dump contains: Configuration info Device Maps Diagnostic files Dumps PCD Info Trace files ASE Dump Event logs BIOS and BMC settings for the BMC system component Refer to the MCP Console Help for details on performing an MCP Firmware Environment Dump. Transferring Diagnostic Data to Unisys Product Support Perform the following steps from the active MCP Platform to transfer diagnostic data to Unisys support: 1. Open an Internet Explorer browser window to and sign in with your Primus account. 2. Select the appropriate product. 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

70 Troubleshooting and Recovery Hardware Failure Symptoms Criticality Response Internal Disk Drive Error message appears on LCD panel. LED on disk drive turns amber, indicating the failed drive. Non-critical if only one drive has failed. Multi-drive failures might lead to data loss. Contact Unisys Support. Memory DIMM Error message appears on LCD panel. Usually non-critical. Redundancy and error correction can correct all but the most severe errors. Contact Unisys Support. Power Supply LED on rear power supply turns amber, indicating a fault. Error message appears on LCD panel. Non-critical if only one power supply has failed. Contact Unisys Support. Cooling Fan Error message appears on LCD panel. Non-critical if only one fan has failed. Contact Unisys Support. Motherboard System failure. Audible alarm may sound. Non-critical for HA configurations; critical otherwise. Contact Unisys Support. HBA Error message may appear on LCD panel. HBA may show error LED s. Non-critical in redundant I/O configurations. Potentially critical in other configurations. Contact Unisys Support. NIC Error message might appear on LCD panel. NIC may show error LEDs. Non-critical in redundant network configurations. Potentially critical in other configurations. Contact Unisys Support. Platform management card Error message might appear on LCD panel. Unable to perform remote management. Usually non-critical. Contact Unisys Support. Battery Error message appears on LCD panel. Non-critical. Loss of AC power to system may cause loss of Real-Time Clock and CMOS settings, requiring a reconfiguration. Contact Unisys Support

71 Troubleshooting and Recovery Hardware Failure Symptoms Criticality Response Intrusion Alarm Error message appears on LCD panel. If configured, an alert is sent. Non-critical. Possible indication of nonapproved physical access to system. Alarm will reset when the system is recovered. 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 environment 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, follow the directions in the Network Readme document included with the Network Services firmware MIM-Update package to reinstall the Network Services firmware. To verify that the network interface card (NIC) is functional, open an ODT session and perform the following actions as necessary:

72 Troubleshooting and Recovery If your TCP/IP or BNA connection is defined with the AUTOINIT attribute set to TRUE, issue the inquiry NW CONN <connection name>. 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 <connection name> to open the connection. Then, issue the inquiry NW CONN <connection name>. 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. 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 System 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 You are most likely to notice that the MCP Operating Environment suffered a fatal system error when a popup message appears 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 messages

73 Troubleshooting and Recovery If a fatal system error (also known as a Blue Screen or STOP error) occurs on one of your FS1770 System operating environments, follow these steps: 1. Using the MCP Console, generate a diagnostic dump with the MCP Environment and Platform Environment dump options. 2. Transfer the materials to a Unisys service representative for analysis. For more information, see Transferring Diagnostic Data from the MCP Environment to Unisys Product Support. 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 FS1770 System. 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 <NP number> 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 collected by the MCP Console. 2. To collect the captured information, use the previously-described option for initiating a dump from the MCP Console. The MCP Console will create an additional network services firmware dump, but both dumps are included in the captured dump data. For more information, see the DUMP NP command in Section 3, Operating the System

74 Troubleshooting and Recovery Location of the Dump Data When the dump is obtained through the MCP Console, the firmware dump data is available on the FS1770 System at the location specified on the Diagnostics tab of the MCP Console. Within this file is a zip file with diagnostic information. 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 MCP Operating Environment 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 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 During CNS initialization file processing, the following error message displays in response to an ADD CONNECTIONGROUP command for a Network Services MCP Network adapter: Possible Corrective Action 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. Hardware Not Present

75 Troubleshooting and Recovery The response to the NW NP <np number> command indicates that there are no NPs defined. The response to the NW NP <np number> command indicates that the network processor remains in a discovered state. The response to the NW NP <np number> command indicates that the network processor remains in an unavailable state. The response to the NW NP <NP #> command for a Network Services device indicates that the device is NASCENT. 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. 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. 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 MCP Operating Environment might be necessary if either case is not true. Check for a pop-up window on the environment system 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 for 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 is necessary to restart Network Services. Also, check for a pop-up 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 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

76 Troubleshooting and Recovery 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, the following error message displays in response to an ADD CONNECTIONGROUP command for a Network Services MCP Network adapter: Invalid Attribute Value 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 <IP address> from MCP to the MCP Operating Environment through EVLAN does not work. During CNS initialization following initialization file processing, network connection remains in a state of pending open. During CNS initialization following initialization file processing, network connection will not open. Optical network adapter will not connect to 1 Gb Ethernet switch. Cables using molded connectors or boots for the connectors that are wider than the RJ45 (8P8C) connector itself should not be used on the FS1770 System. Earlier ClearPath systems might have included or recommended cables with inappropriate connectors. These cables cannot be carried forward to the FS1770 System. 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 MCP Operating Environment. 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 FS1770 System. See Enabling MCP PING Commands through the EVLAN Connection for more information. Verify that the network processor and line identifiers are identical for the ADD CONNECTIONGROUP command of the CNS initialization file and the configuration output of the System Editor. Verify that the network processor and line identifiers are identical for the ADD CONNECTIONGROUP command of the CNS initialization file and the configuration output of the System Editor utility. The network adapter is capable of automatically detecting 1 Gb and 10 Gb 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

77 Troubleshooting and Recovery 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 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 FS1770 System 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. 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 FS1770 System. 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 FS1770 System is still running with a significant I/O load. Under certain circumstances you might also need to take action in 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 FS1770 System 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 FS1770 System. 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 FS1770 System. The Disk and Tape Storage Systems Configuration Guide includes configuration information that must be followed when configuring devices for access from the FS1770 System. In particular, this document includes required settings for EMC storage systems. You should also check FS1770 System TIBs to see if any additional configuration requirements have been documented after publication of these manuals

78 Troubleshooting and Recovery Device is Not Visible in the Environment These procedures are for the case when Device Manager 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 FS1770 System 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. Configuring I/O 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: 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, Unisys recommends 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 on the FS1770 System to access the HBAs. 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

79 Troubleshooting and Recovery If the preceding steps do not make the device visible in the environment, then the problem is probably external to the FS1770 System and the storage and storage connections should be re-examined for problems. If no external problems (including bad cables) are found, restart the FS1770 System. If the problem persists, contact Unisys support. If you need to send problem materials for this issue and you have attempted these recovery procedures, take a second MCP Environment Dump. Include the MCPEnvironment 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 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 FS1770 System is still running with a significant I/O load. If the 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 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 or restart Platform Services. If the problem persists, contact Unisys support. Recovery Actions This subsection lists recovery actions you can perform for your FS1770 System

80 Troubleshooting and Recovery Restoring a Logical Disk If your halt/load unit is on the internal logical disk, perform the following procedures to restore the disk. Note: To make hidden logical disk files visible, perform the steps described in Backing Up a Logical Disk. Restoring the Halt/Load Unit Logical Disk File If your Halt/Load unit is a logical disk, you can restore a copy of the logical disk file that you previously backed up. To restore the Halt/Load disk image from a backup copy, perform the following procedure: 1. From the MCP Console, halt the MCP. 2. Open Windows Explorer. 3. Copy and paste the.asd file from the backup media to the location specified identified in Step 3 from Backing Up a Logical Disk. Note: If the logical disk file is compressed, you must uncompress the file. Do not attempt to operate the system with a compressed Halt/Load disk image. 4. the security attributes that the system modified make the logical disk unusable until the correct security is applied to the file. To secure the logical disk file: a. From the MCP Console, open Logical Disk Manager. b. From the list of logical disks, select the logical disk file. A red icon appears in front of the disk name to indicate invalid security. c. From the toolbar, click the Apply Security button. 5. Run the Restore process from the MCP Console as described in Recovering FS1770 System Configuration Data using the data backup saved with the Halt/Load logical disk file. Recovering FS1770 System Configuration Data You can recover FS1770 System configuration data, such as PCD files, by running the Restore-Item scripts. The recommended method for restoring the critical configuration data is to copy the information from external media, such as the supplied USB drive. Perform the following procedure from the MCP Console: 1. From the Tools menu, click Restore Configuration. The Browse for Folder dialog appears. 2. Select the NGMbackup folder and click OK to initiate the restore function. After a few seconds, a message confirms that the restore was successful. 3. Press any key to complete the restore

81 Troubleshooting and Recovery For more information, refer to the MCP Console Help. Power-Cycling the System Note: Halt the MCP using the MCP Console before performing the following steps. To power-cycle the FS1770 System, perform one of the following procedures: From the desktop 1. Pull down the Settings icon by placing the mouse in the upper right corner of the screen for the icons to appear. 2. Select Power. 3. Select Restart. From the Component View tab of the MCP Console, right-click the MCP Operating Environment and click Restart or Reset. If the previous method is not available, follow these steps to use the BMC web interface to power-cycle the system: 1. From the Component View tab of the MCP Console, right-click the MCP Platform component and then click Launch BMC Web Interface. 2. If you see a Certificate error screen, click Continue to this Website. 3. Log on with default usercode Administrator and password Administer4Me. 4. Select Power/Thermal under Overview/Server on the left-hand side. 5. Select either Reset System or Power Cycle System. 6. Click Apply. Press and hold the power button on the front of the system for five seconds. Note: Use this method as a last resort. Reinstalling the System Reinstalling the platform hardware and software should only be performed by Unisys support personnel. Contact Unisys Support if you need to reinstall the platform hardware and software

82 Troubleshooting and Recovery

83 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 FS1770 System 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 Guidelines for Building CNS Initialization Files or Guidelines for building TCP/IP Initialization Files. If you want to create BNA (also known as Heritage Network Services) initialization files, refer to Guidelines for Building BNA Initialization Files. Preconfigured CNS and TCP/IP Initialization Files The following subsections describe the CNS and TCP/IP sample initialization files for the FS1770 System. CNS and TCP/IP Initialization Files The following CNS initialization files define the commands preconfigured for the FS1770 System: INIT/SAMPLE/CLEARPATH/ENTRY/CPMCP1/CNS INIT/SAMPLE/CLEARPATH/ENTRY/CPMCP1/TCPIP Guidelines for Building CNS Initialization Files Use the following general guidelines when building a CNS initialization file. The examples in this subsection are taken from the following file on the NETSYSTEM release media: *INIT/SAMPLE/CLEARPATH/ENTRY/CPMCP1/CNS A connection group is required for each network interface. The first network interface for an MCP Operating Environment has an EVLAN Connection Group and up 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 A 1

84 Building Network Initialization Files NW AUTHORIZE statements are included as follows. Adjust for your own environment. NW AUTHORIZE *DEFAULT NW AUTHORIZE ADMINISTRATOR AT CPMCP1 = NETWORKCONTROL;% = 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 example: NW ADD CONNECTIONGROUP CG_ICP_2100% % Connection Group Information % ( TYPE = LAN%, ICPDEVICEID = 210%, LINEMODULEID = 1%, LINEID = 0%, SPEED = %, LOCALADDRESS = *DEFAULT%, MAXINPUTMESSAGESIZELIMIT = 4352%, MAXOUTPUTMESSAGESIZELIMIT = 4352%, MAXINPUTMESSAGESIZE = 4352%, MAXOUTPUTMESSAGESIZE = 4352% )% ;% NW ADD CONNECTIONGROUP CG_ICP_2102% % Connection Group Information % ( TYPE = LAN%, ICPDEVICEID = 210%, LINEMODULEID = 1%, LINEID = 1%, SPEED = %, LOCALADDRESS = *DEFAULT%, ADAPTERTYPE = GIGABIT%, MAXINPUTMESSAGESIZELIMIT = 1500%, MAXOUTPUTMESSAGESIZELIMIT = 1500%, MAXINPUTMESSAGESIZE = 1500%, MAXOUTPUTMESSAGESIZE = 1500% )% ;% Note: The MIMS, MOMS, MIMSL, and MOMSL values are required for an EVLAN connection. The recommended value is Guidelines for building TCP/IP Initialization Files Use the following general guidelines when 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/ENTRY/CPMCP1/TCPIP Note that the following statements are included in the initialization file: NW TCPIP TCPIPIDENTITY NW TCPIP TCPIPIDENTITY ADD NP 210 LINE /24 VISIBLE +;% A

85 Building Network Initialization Files 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 ;% % % 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 = %, CLASS = CLASS_1%, MAXINPUTMESSAGESIZELIMIT = 4352%, MAXOUTPUTMESSAGESIZELIMIT = 4352%, MAXINPUTMESSAGESIZE = 4352%, MAXOUTPUTMESSAGESIZE = 4352% )% ;% 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 A 3

86 Building Network Initialization Files Preconfigured SNMP Initialization File The SNMP initialization file (INIT/SAMPLE/SNMPAGENT/INITFILE) provides the preconfigured SNMP configuration commands for identifying required information for an SNMP Management station. 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" ReadOnly; % A

87 Building Network Initialization Files % 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. %NW SNMP COMMUNITY ADD % % "community" xxx.xxx.xxx.xxx ReadWrite;% % % The next command adds SP1. %NW SNMP COMMUNITY ADD % % "community" xxx.xxx.xxx.xxx ReadWrite;% % % Add the external Management Server if it exists. %NW SNMP COMMUNITY ADD % % "community" xxx.xxx.xxx.xxx ReadWrite;% % % 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 %NW SNMP TRAPCOMMUNITY ADD % % "public" xxx.xxx.xxx.xxx;% % % Add SP1 Trapcommunity %NW SNMP TRAPCOMMUNITY ADD % % "public" xxx.xxx.xxx.xxx;% % % Add the external Management Server trapcommunity if it exists. %NW SNMP TRAPCOMMUNITY ADD % % "public" xxx.xxx.xxx.xxx;% % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % 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 SysContact = "ClearPath Administrator" % A 5

88 Building Network Initialization Files,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 "CNS Object Manager" = 10% ;% NW SNMP SET % 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 Class of Service 2. To specify this class of service, simply add the following attribute to each required connection: CLASS = CLASS_2 A

89 Building Network Initialization Files 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_2102% 2102_BNAHOST1_1% % Connection Information ( NETWORKLAYERENTITY = ROUTER%, REMOTEADDRESS = 08000B000834), % <--- See shaded comment 2102_BNAHOST2_1% % Connection Information ( NETWORKLAYERENTITY = ROUTER%, REMOTEADDRESS = 08000B000C1C); % <--- See shaded comment %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % END INITIALIZATION % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% NW ENDINITIALIZATION;% Note that in this file: You must set the LOCALIDENTITY. You must add component connections to your connection groups for each remote host you are communicating with by using the NW ADD CONNECTION statement. Do not add component connections to an EVLAN connection group. EVLAN can only be used for TCP/IP. The NETWORKLAYEDIDENTITY value is always ROUTER for BNA. The REMOTEADDRESS value must match the LOCALADDRESS of the connection on the remote host. The last statement in BNA initialization files in NW END INITIALIZATION. Using NAU Network Version Dump Files If you use the Network Administrative Utility (NAU) to configure the MCP system, you can load the appropriate sample NAU network version disk dump file for editing or review. These files are listed in the following table. For the FS1770 System, load the VNPSINGLEIOP sample NAU network version disk dump file. Note: The NAU Network Version Dump files are not available for the FS1770 System. Use the VNP version dumps as a starting point instead. 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 A 7

90 Building Network Initialization Files For additional information about loading an NAU network version disk dump file, refer to the Network Administrative Utility Operations Guide. A

91 Index A accessing the Unisys Support Product website, 6 2 accessing updates, 5 1 Adapter teaming, modifying adapter settings, 2 14 Adapter teaming preparing to use, 2 13 ADAPTERS.TXT file, sample, 2 19 ADAPTERTYPE attribute, for defining EVLANs and MCP network adapters, 3 16 Administrator password, changing, 2 21 user name, changing, 2 21 Network Services troubleshooting tips, 6 10 attributes EVLAN, 3 15 Jumbo Frames, 2 15 MCP network adapters, 3 15 audit settings MCP Firmware Environment Policy, 3 7 UnisysHarden.ps1 script, 3 9 UnisysHarden_Rollback.ps1 script, 3 8 C Call Home configuration, 2 23 diagnostic tasks, 6 3 alerts, testing, heartbeats, testing, 3 20 Maintenance mode, 3 20 monitoring event s, 6 3 problems with, 6 4 services, 3 19 using Maintenance mode, 6 3 CANDE editor, 2 11 changing Administrator password, 2 21 Administrator user name, 2 21 IP address for Network Services, 2 11 changing the default systems management account password, 2 22 CLEAR NP command, 3 17 CNP dump data, 6 10 CNS initialization file, 2 11 preconfigured, 2 19 commands, networking, 3 17 configuration Call Home services, 2 23 MCP Environment, 2 23 MCP Networking, 3 13 Networking, 2 8, 3 13 recovering FS1770 System data, 6 16 System Editor, 2 11, 2 14, 2 16 Configuring Ethernet Jumbo Frames, 2 15 connection error, MCP Console, 6 8 CONNECTION inquiry, 3 17 D default Networking configuration, 2 9 default systems management account password, changing, 2 22 diagnostic tasks, 6 4 accessing the Unisys Product Support website, 6 2 Call Home, 6 3 Call Home Maintenance mode, 6 3 MCP Environment Dump, 6 4 MCP Firmware Environment Dump, 6 5 monitoring Call Home event s, 6 3 problems with Call Home, 6 4 Remote Support, 6 3 transferring diagnostic data to Unisys Product Support, 6 5 disabling Fibre Channel ports, 2 7 disconnecting Fibre Channel I/O devices, 3 22 downloading updates, 5 1 driver updates, 5 1, 5 3 dump files, NAU network version, using, A 7 DUMP NP command, Index 1

92 Index dumps initiating, 6 9 MCP Environment Dump, 6 4 MCP Firmware Environment Dump, 6 5 dynamic PCD updates, 3 21 E alerts, testing in Call Home, 3 20 heartbeats, testing in Call Home, 3 20 enabling Fibre Channel ports, 2 7 MCP PING commands through EVLAN connection, 3 5, 3 10, 6 12 environment MCP, configuring, 2 23 shutting down, 3 4 status, viewing, 3 4 transferring diagnostic data, 6 5 viewing status, 3 4 ESTABLISHCALL command, 3 18 Ethernet jumbo frames configuring, 2 15 Ethernet Jumbo Frames, preparing to use, 2 14 event s, monitoring, 6 3 EVLAN attributes, 3 15 connection, enabling PING commands, 3 5, 3 10, 6 12 connections, 2 11 IP Address, changing, 2 11 verifying Network Services installation, 3 13 F failure scenarios Network Services, 6 9 MCP Environment, 6 7 platform hardware, 6 5 Fast Ethernet port aggregation, preparing to use, 2 13 fatal system error, 6 8 Fibre Channel I/O problems, troubleshooting, 6 13 ports, 2 7 disabling, 2 7 enabling, 2 7 firewall rules MCP Firmware Environment Policy, 3 6 MCP Firmware Environment Policy settings, 3 6 firmware updates using MIM-Update script, 5 2, 5 3 fixes, updates, 5 1 FS1770 System configuration data, recovering, 6 16 initialization files, A 1 preconfigured initialization files, 2 19 H hardware platform monitoring boot progress, 3 2 powering off, 3 3 powering on, 3 2 viewing power status, 3 1 I IC update files, 5 1 IEEE 802.1Q VLANS preparing to use, 2 13 initialization files, 2 8, 2 11 described, A 1 FS1770 System, 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, 3 13 initiating a dump, 6 9 inquiries, networking, 3 17 Interim Correction (IC) update files, 5 1 I/O services, 3 20 disabling Fibre Channel ports, 2 7 disconnecting Fibre Channel I/O devices, 3 22 enabling Fibre Channel ports, 2 7 I/O time, 3 21 performing dynamic PCD updates, 3 21 power cycling Fibre Channel I/O devices, 3 22 I/O time, 3 21 Index

93 Index IP address changing for Network Services EVLAN path, 2 11 IP address values MCP Operating Environment default, 2 10 J Jumbo Frames attributes, 2 15 Networking configuration, 2 14 preparing to use, 2 14 L LCD panel, 3 2 LINEID attribute, for defining MCP network adapters, 3 16 LocalAddress attribute, for defining VLANs and MCP network adapters, 3 16 local dump, 3 17 local MAC address, setting, 2 12 M MAC address, setting, 2 12 MAICP4 dump data, 6 10 Maintenance mode, 3 20 diagnostic task, 6 3 Management Card Virtual Console, 3 2 mapping to a Client Access Services share, problems, 6 8 Master Installation Manager Update Script, 5 2, 5 3 MCP Console, 2 11 connection error, 6 8 MCP Environment, 2 11 configuration, 2 23 failure scenarios, 6 7 MCP Firmware Environment Policy, 3 4 operating, 3 4 MCP Environment Dump generating, 6 4 MCP Firmware Environment Dump generating, 6 5 MCP Firmware Environment Policy, 3 4 audit settings, 3 7 irewall rules, 3 6 network authentication settings, 3 7 services, 3 5 utility scripts, 2 11, 3 8 SetLMCompatibility.ps1, 3 9 UnisysHarden.ps1, 3 9 UnisysHarden_Rollback.ps1, 3 8 MCP Firmware, updating, 5 2 MCP network adapter, 2 12 attributes, 3 15 MCP Networking configuring, 3 13 values, 2 20 values for MCP Operating Environment -2, 2 20 MCP PING commands enabling through EVLAN connection, 3 5, 3 10, 6 12 MIM-Update script updating firmware, 5 2, 5 3 Modifying adapter settings for VLANs and teaming, 2 14 monitoring Call Home event s, 6 3 platform boot progress, 3 2 N Network Administrative Utility (NAU), 2 11 network authentication settings MCP Firmware Environment Policy, 3 7 Network Processor default values EVLAN and intra-system connections on MCP Operating Environment, 2 9 Network Processors (VNPs), 2 9 Network Services, 2 9 differences from previous MCP systems, 3 12 EVLAN attributes, 3 15 failure scenarios, 6 9 initializing, 3 13 initiating a dump, 6 9 operations, 3 12 operations interface summary, 3 15 reinstalling, 5 4 removing, 5 3 support for MCP network adapters, 2 12 tools, 2 10 troubleshooting, 6 9 updating, 5 3, 5 4 verifying EVLAN installation, 3 13 verifying installation, 3 13 network version dump files, using, A Index 3

94 Index networking commands CNS CLEAR NP, 3 17 CONNECTION inquiry, 3 17 DUMP NP, 3 17 ESTABLISHCALL BY CONN, 3 18 NP, 3 18 UTILIZATION inquiry, 3 18 Networking configuration, 2 8, 3 13 adapter teaming, 2 13 default, 2 9 initialization files, 2 8 Jumbo Frames, 2 14 MCP Networking values, 2 20 MCP Networking values IOE-2, 2 20 sample ADAPTERS.TXT file, 2 19 setting local MAC address, 2 12 System Editor, 2 11, 2 14, 2 16 Networking values MCP, 2 20 MCP IOE-2, 2 20 MCP Operating Environment -1 default, 2 10 NP inquiry, 3 18 O offload settings, TCP, 2 13 Open Management Interface (OMI) installing and configuring, 2 24, 3 1, 3 2, 3 3 P password of Administrator, changing, 2 21 PCD updates, 3 21 PCI card BIOS/firmware updates, 5 3 performing dynamic PCD updates, 3 21 PING command verifying EVLAN path, 3 14 PING commands, enabling for MCP, 3 5, 3 10, 6 12 platform boot progress, monitoring, 3 2 platform hardware failure scenarios, 6 5 monitoring boot progress, 3 2 power status, 3 1 powering off, 3 3 powering on, 3 2 policy services MCP Firmware Environment Policy, 3 5 power control, 3 1 monitoring the platform boot progress, 3 2 powering off platform hardware, 3 3 powering on platform hardware, 3 2 shutting down system, 3 3 viewing platform hardware status, 3 1 power cycling cell, 6 17 Fibre Channel I/O devices, 3 22 powering off platform hardware, 3 3 powering on platform hardware, 3 2 preparing to use Ethernet Jumbo Frames, 2 14 IEEE 802.1Q VLANS, 2 13 problems Call Home, 6 4 mapping to a Client Access Services share, 6 8 Product Support website, accessing, 6 2 R reboot dump, 3 18 recovering FS1770 System configuration data, 6 16 recovery actions, 6 15 power-cycling a cell, 6 17 recovering FS1770 System configuration data, 6 16 reinstalling the entire system, 6 17 reinstalling entire system, 6 17 Network Services, 5 4 Remote Support, 6 3 removing Network Services, 5 3 restarting an environment, 6 4 S sample ADAPTERS.TXT File, 2 19 scripts UnisysHarden.ps1, 3 9 UnisysHarden_Rollback.ps1, 3 8 SetLMCompatibility.ps1 script, 3 9 setting local MAC address, 2 12 shutting down an environment, 3 4 system, 3 3 SNMP initialization files, A 4 Index

95 Index status viewing environment, 3 4 viewing platform hardware power, 3 1 support for MCP network adapters, 2 12 synchronizing time, 3 12 system shutting down, 3 3 system commands and inquiries, 3 12, 3 19 system error, 6 8 systems management account password, changing, 2 22 Systems Management Environment tools for Network Services, 2 10 T TCP offload settings, 2 13 TCP/IP connections, 2 11 initialization file, 2 11, A 1 initialization file, guidelines for building, A 2 preconfigured initialization file, 2 19 testing alerts, 3 20 testing heartbeats, 3 20 time synchronization, 3 12 tips, troubleshooting for Network Services, 6 10 tools associated with Network Services, 2 10 transferring diagnostic data to Unisys Product Support, 6 5 trouble report, submitting, 6 1 troubleshooting accessing the Unisys Support Product website, 6 2 diagnostic tasks, 6 4 Fibre Channel I/O problems, 6 13 MCP Environment Dump, 6 4 MCP Environment failure, 6 7 MCP Firmware Environment Dump, 6 5 monitoring Call Home event s, 6 3 Network Services, 6 9 platform hardware failure, 6 5 problems with Call Home, 6 4 recovery actions, 6 16 tips, Network Services, 6 10 transferring diagnostic data to Unisys Product Support, 6 5 using Call Home, 6 3 using Call Home Maintenance mode, 6 3 using Remote Support, 6 3 U Unisys Product Support, transferring diagnostic data to, 6 5 updates accessing and downloading, 5 1 driver, 5 3 dynamic PCD, 3 21 MCP Firmware, 5 2 Network Services, 5 3, 5 4 PCI card BIO/firmware, 5 3 using Interim Correction (IC) update files, 5 1 updating firmware using MIM-Update script, 5 2, 5 3 User Communication Form (UCF), submitting, 6 1 user name Administrator, changing, 2 21 utility scripts MCP Firmware Environment Policy, 2 11, 3 8 SetLMCompatibility.ps1, 3 9 UnisysHarden.ps1, 3 9 UnisysHarden_Rollback.ps1, 3 8 UTILIZATION inquiry, 3 18 V viewing environment status, 3 4 platform hardware power status, 3 1 Virtual LANs modifying adapter settings, 2 14 virtual LANs, IEEE 802.1Q, Index 5

96 Index Index

97 .

98 2014 Unisys Corporation. All rights reserved. * *