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