HPE NonStop Cluster I/O Protocols(CIP) Configuration and ManagementManual

Part Number: 541613-027Published: June 2016Edition: L15.02, J06.05, and H06.16 and subsequent L-series, J-series, and H-series RVUs

© Copyright 2008, 2016 Hewlett Packard Enterprise Development LP

The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and servicesare set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constitutingan additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensedto the U.S. Government under vendor's standard commercial license.

Export of the information contained in this publication may require authorization from the U.S. Department of Commerce.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is notresponsible for information outside the Hewlett Packard Enterprise website.

Acknowledgments

Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries.

Microsoft® and Windows® are trademarks of the Microsoft group of companies.

Intel®, Pentium®, and Celeron® are trademarks of Intel Corporation in the U.S. and other countries.

Java and Oracle are registered trademarks of Adobe Systems Incorporated.

Motif, OSF/1, UNIX, X/Open, and the "X" device are registered trademarks, and IT DialTone and The Open Group are trademarks of The OpenGroup in the U.S. and other countries.

Open Software Foundation, OSF, the OSF logo, OSF/1, OSF/Motif, and Motif are trademarks of the Open Software Foundation, Inc. OSF MAKESNO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED HEREIN, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. OSF shall not be liable for errors containedherein or for incidental consequential damages in connection with the furnishing, performance, or use of this material.

© 1990, 1991, 1992, 1993 Open Software Foundation, Inc. The OSF documentation and the OSF software to which it relates are derived in partfrom materials supplied by the following:© 1987, 1988, 1989 Carnegie-Mellon University. © 1989, 1990, 1991 Digital Equipment Corporation. ©1985, 1988, 1989, 1990 Encore Computer Corporation. © 1988 Free Software Foundation, Inc. © 1987, 1988, 1989, 1990, 1991 Hewlett-PackardCompany. © 1985, 1987, 1988, 1989, 1990, 1991, 1992 International Business Machines Corporation. © 1988, 1989 Massachusetts Institute ofTechnology. © 1988, 1989, 1990 Mentat Inc. © 1988 Microsoft Corporation. © 1987, 1988, 1989, 1990, 1991, 1992 SecureWare, Inc. © 1990,1991 Siemens Nixdorf Informationssysteme AG. © 1986, 1989, 1996, 1997 Sun Microsystems, Inc. © 1989, 1990, 1991 Transarc Corporation.OSFsoftware and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University ofCalifornia. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch,Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. © 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents ofthe University of California.

ContentsAbout This Document...........................................................................................13

Supported Release Version Updates (RVUs).....................................................................................13Intended Audience..............................................................................................................................13New and Changed Information...........................................................................................................13

New and Changed Information in the 541613–027 Edition...........................................................13New and Changed Information in the 541613-026R Edition.........................................................13New and Changed Information in the 541613-026 Edition............................................................13New and Changed Information in the 541613-025 Edition............................................................14New and Changed Information in the 541613-024 Edition............................................................17

Notation Conventions.........................................................................................................................17General Syntax Notation...............................................................................................................17Notation for Messages...................................................................................................................19

Related Information............................................................................................................................20Related Documents.......................................................................................................................20Linux Man Page Documentation and Help....................................................................................20Glossary........................................................................................................................................21

Publishing History...............................................................................................................................211 Overview............................................................................................................22

Internet Protocol Version 6 (IPv6) Compliance...................................................................................22CIP Hardware Overview.....................................................................................................................22CIP NonStop Host System Software Overview..................................................................................23

NonStop Host System Management.............................................................................................23CIP CLIM Software Overview.............................................................................................................24

CLIM Management........................................................................................................................24Persistence....................................................................................................................................26

The CIP Subsystem for Internet Protocols (IP CIP)............................................................................26IP Protocols...................................................................................................................................27Telco Protocols..............................................................................................................................27Multiple CLIMs per Provider..........................................................................................................27Multiple Providers per CLIM..........................................................................................................28Using Multiple Providers................................................................................................................29Using Multiple SWAN Paths in a Single Provider..........................................................................29Using Multiple Listeners with Round Robin Sockets.....................................................................29Routing in the CIP Subsystem.......................................................................................................29Failover in the CIP Subsystem......................................................................................................31Internet Protocol Security (IPSec).................................................................................................45Name Resolution...........................................................................................................................47SNMP Support...............................................................................................................................47IP CLIM..........................................................................................................................................48CIP iptables/ip6tables Support (climiptables)................................................................................48IB CLIM..........................................................................................................................................49

The CIP Subsystem for Storage I/O and the Storage Subsystem......................................................49Storage CLIM................................................................................................................................50

Subsystem ID and Product Numbers.................................................................................................50Capacity and Resource Use...............................................................................................................51

Restrictions....................................................................................................................................512 Quick Start.........................................................................................................53

Default Processes and Naming Conventions.....................................................................................53Change the CLIM Passwords.............................................................................................................54Configure and Start CIP......................................................................................................................55Configure the Eth1 Through Eth5 Interfaces (IP CLIM Only).............................................................56

Contents 3

Configure CLIM-To-CLIM Failover (IP and Telco CLIMs Only)...........................................................56Check Network Applications (IP CLIMs Only)....................................................................................58

3 CIP Configuration and Management.................................................................59Using Linux Commands and Custom CIP Commands.......................................................................59Entering CIP Commands....................................................................................................................61

Errors.............................................................................................................................................62Enabling root Access for Non-Super Users........................................................................................62Configuring CIP..................................................................................................................................63

On the NonStop Host System.......................................................................................................63On the CLIM..................................................................................................................................71

Policy Based Routing..........................................................................................................................72Troubleshooting Routing...............................................................................................................76

Displaying the CIP Configuration........................................................................................................77On the NonStop Host System.......................................................................................................77On the CLIM..................................................................................................................................77

Displaying Man Pages for CIP Commands........................................................................................85Monitoring CIP....................................................................................................................................85

On the NonStop Host System.......................................................................................................86On the CLIM..................................................................................................................................86

Configuring Bonded Interface Failover (IP CIP).................................................................................86Configuring CLIM-to-CLIM Failover (IP CIP)......................................................................................87Replicating the Configurations from One CLIM to Another CLIM.......................................................90

Using the CLIMCMD /IN/ run-option..............................................................................................91Starting and Restarting CIP................................................................................................................91

Starting CIP on the NonStop Host System....................................................................................91Starting CIP on the CLIM...............................................................................................................92Starting the IP Applications (IP CIP Only).....................................................................................93Restarting CIP on the NonStop Host System................................................................................93Restarting CIP on the CLIM...........................................................................................................93

Controlling Interface States (IP CIP)...................................................................................................94Activating an Interface...................................................................................................................94Deactivating an Interface...............................................................................................................95

Configuring IPSec (IP CIP).................................................................................................................95Installing X.509 Certificates...........................................................................................................95Setting Up Links to the Certificate Revocation List (CRL) and to the Certificate Authority (CA)....96Configuring Pre-Shared Keys........................................................................................................96Configuring Security Policies.........................................................................................................97Configuring Security Associations.................................................................................................97Configuring Remote Information...................................................................................................98Controlling the Virtual Private Network (VPN)...............................................................................98Using IPSec...................................................................................................................................98

Configuring Transport of Authentication Events from CLIM...............................................................99Checking the Status of the Collector $ZCLA ................................................................................99Starting the Collector.....................................................................................................................99Adding the Collector....................................................................................................................100Viewing the Events in the Collector $ZCLA.................................................................................100Retrieving the Events from the $ZCLA by an Application...........................................................100Deleting the Collector..................................................................................................................100

Configuring CIP iptables/ip6tables (IP CIP)......................................................................................100Configuring climiptables..............................................................................................................101Configuring iptables/ip6tables.....................................................................................................101

Configuring Stream Control Transmission Protocol (SCTP) (IP and Telco CIP)..............................104Round-Robin Filtering.......................................................................................................................104Logging Messages............................................................................................................................104

4 Contents

Configuring IPv6 (IP CIP).................................................................................................................104Running Applications in Multiple Environments (IP CIP)..................................................................105Managing the Configuration Preservation........................................................................................105

Managing the Configuration Database on the NonStop Host System........................................105Managing Persistence on the NonStop Host System.................................................................106Managing the CLIM Configuration Preservation.........................................................................106

Planning for Coexistence With Conventional TCP/IP (IP CIP Only).................................................108Stopping CIP.....................................................................................................................................108

Preparing to Stop the CIP Subsystem.........................................................................................108Stopping CIP...............................................................................................................................110

Monitoring the Network (IP CIP).......................................................................................................111Testing Access to Internet Network Hosts by Using the Ping Command (IP CIP)...........................111

Displaying a Datagram’s Route to a Network Host by Using Traceroute....................................111Event Management System (EMS) Messages............................................................................112

Troubleshooting Tools and Tips........................................................................................................112CLIMCMD clim Command...........................................................................................................112Event Logging..............................................................................................................................113Detecting Duplicate IP Addresses...............................................................................................114Displaying Link Speed.................................................................................................................114Verifying the lunmgr Configuration of Two Storage CLIMs..........................................................115Tip: Finding an Available UDP Port (IP CIP Only).......................................................................118CLIM and Host Incompatibility.....................................................................................................118Troubleshooting Network Applications Using Tcpdump..............................................................118Mapping CLIM Name...................................................................................................................121

Setting Up Multiple Providers per CLIM............................................................................................122Enabling the MULTIPROV Attribute............................................................................................122Disabling the MULTIPROV Attribute............................................................................................122

Changing Providers, Adding and Starting a CLIM (IP and Telco Only)............................................123CLIMs with MULTIPROV OFF.....................................................................................................123CLIMs with MULTIPROV ON.......................................................................................................124

4 Upgrading CIP.................................................................................................126Performing an Online Upgrade of the CIP Subsystem on the NonStop Host...................................126

Replace CIPMON (Only).............................................................................................................126Replace CIPMAN (Only)..............................................................................................................127Replace CIPMAN and CIPMON Simultaneously........................................................................127Replace CIPSAM.........................................................................................................................128

Upgrading CLIM Software and Firmware.........................................................................................128Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic.................129

Upgrading CLIM Software with the System Running..................................................................130Upgrading CLIM Firmware with the System Running.................................................................144Upgrading Multiple CLIMs in Parallel..........................................................................................155Upgrading Multiple CLIMs of Different Types..............................................................................160

Upgrading CLIM Software or Firmware While the System is Down ................................................160Overview of Optimized CLIM Software and Firmware Update Procedure..................................161Prepare CLIMs for Down System Firmware Update...................................................................161Halt the Processors.....................................................................................................................161Update CLIM Software on a Down System.................................................................................161Update CLIM Firmware on a Down System................................................................................162Load the System..........................................................................................................................162Apply CLIM Hotfix Software Patches..........................................................................................162

Falling Back to Conventional TCP/IP or NonStop TCP/IPv6............................................................163Falling Back to Conventional TCP/IP or NonStop TCP/IPv6.......................................................163

Falling Back to Previous RVUs that Support the Multiple Providers per CLIM Feature...................163Falling Back to a Previous CLIM Version..........................................................................................163

Contents 5

5 LUN Manager for Storage CLIM......................................................................164Lunmgr Commands..........................................................................................................................164

Approve Command......................................................................................................................164Binaryfind Command...................................................................................................................164Clear Command..........................................................................................................................164Delete Command.........................................................................................................................164Enclosures Command.................................................................................................................165Find Command............................................................................................................................165Help Command............................................................................................................................165led Command..............................................................................................................................166Print Command............................................................................................................................166Renumber Command..................................................................................................................166Scan Command...........................................................................................................................166Startover Command....................................................................................................................166Unblock Command......................................................................................................................166Update Command.......................................................................................................................166WWNs Command........................................................................................................................167

6 IP CIP Migration, Compatibility and Operational Differences..........................168Summary of High-Level Differences Between Previous TCP/IP Subsystems and CIP....................168Operational Differences Between Previous TCP/IP Subsystems and CIP.......................................169

SLSA Subsystem.........................................................................................................................176Network Partitioning Differences.................................................................................................176Routing Differences.....................................................................................................................177Failover Differences (Fault Tolerance).........................................................................................177Differences That Affect Planning for CLIMs Instead of G4SAs...................................................177IPv6 Differences..........................................................................................................................178Fault Tolerant Sockets.................................................................................................................178Remote Sockets..........................................................................................................................178New Error Codes when Using IPSec..........................................................................................178Avoiding Interfaces With Link Pulse Down..................................................................................178Error on Sockets When CIPSAM Process Aborts.......................................................................180Connecting to Non-Loopback Address after Binding to Loopback..............................................180CIPSAM Commands...................................................................................................................180Configuring SWAN Adapters on a CLIM.....................................................................................181

Application Programming Differences Between NonStop TCP/IPv6 and CIP..................................182Suppressing Compatibility Errors................................................................................................182Bind to INADDR_ANY and a Specific Address on the Same Interface.......................................182Changing Destination of a Connected UDP Socket....................................................................183Multicast Bind and Set or Join on Separate Interfaces...............................................................183Multicast Loopback......................................................................................................................183Receiving Broadcasts on Specific Addresses.............................................................................183Error after UDP Send to Unreachable Port.................................................................................184Conversion of Limited Broadcast to Subnet-Directed Broadcast................................................184Binding to a Recently Used Address and Port............................................................................184Round-Robin Socket Support Considerations.............................................................................184Socket IOCTL Differences...........................................................................................................184Socket Options............................................................................................................................185

TCP/IP Attributes in CIP...................................................................................................................188NonStop TCP/IPv6 Attributes and Their CIP Equivalents...........................................................188Attribute Default Values and Ranges...........................................................................................193NonStop TCP/IPv6 Attributes Not Supported..............................................................................195

How to Migrate From NonStop TCP/IP or NonStop TCP/IPv6 to CIP..............................................197Migrate the Environment.............................................................................................................197

6 Contents

7 Storage CLIM Migration, Compatibility and Operational Differences..............1988 Collecting Data for CLIM Issues......................................................................200

Create CLIM Debug Information.......................................................................................................200CLIM Log Files..................................................................................................................................200Collecting CLIM Log Files using CLIMDBUG...................................................................................200

OSM Event Viewer Log for CIP Event 5231................................................................................202Copying CLIM Debug Information to NonStop.................................................................................203Collecting iLO and IML Logs.............................................................................................................204Collecting lunmgr Information...........................................................................................................206Collecting EMS Logs........................................................................................................................206Collecting SCF Information...............................................................................................................206Collecting Network Information.........................................................................................................207Collecting SSH Information...............................................................................................................207Collecting IB Network Status............................................................................................................207

9 Dump to ME Unit (L-Series Only)....................................................................20810 Telco CIP Migration, Compatibility and Operational Differences...................20911 SCF Reference for CIP..................................................................................210

SCF for Cluster I/O Protocols...........................................................................................................210SCF Commands for CIPMAN Compared to SCF Commands for CIPSAM.....................................210Object Types.....................................................................................................................................211

CIPMAN PROCESS Object.........................................................................................................212CIPSAM Object...........................................................................................................................213MON Object.................................................................................................................................213CLIM Object.................................................................................................................................213PROVIDER Object......................................................................................................................213ROUTE Object.............................................................................................................................214SUBNET Object...........................................................................................................................214

Naming Convention Summary..........................................................................................................214Wildcard Support..............................................................................................................................215Abbreviations....................................................................................................................................215Summary States...............................................................................................................................216Sensitive and Nonsensitive Commands...........................................................................................217SCF HELP Facility............................................................................................................................217LISTDEV CIP and LISTDEV TCPIP.................................................................................................218CIPMAN SCF Commands................................................................................................................218

ABORT Commands.....................................................................................................................218ADD Commands..........................................................................................................................220ALTER Command........................................................................................................................226DELETE Commands...................................................................................................................228INFO Commands.........................................................................................................................229LISTOPENS Commands.............................................................................................................239NAMES Commands....................................................................................................................244PRIMARY Command...................................................................................................................247START Commands......................................................................................................................247STATS Commands......................................................................................................................248STATUS Commands...................................................................................................................253STOP Commands.......................................................................................................................275SWITCH CLIM.............................................................................................................................277TRACE Commands.....................................................................................................................278VERSION Commands.................................................................................................................283

CIPSAM SCF Commands................................................................................................................285ABORT Command, CIPSAM.......................................................................................................285INFO Commands, CIPSAM.........................................................................................................285

Contents 7

NAMES SUBNET, CIPSAM.........................................................................................................290PRIMARY Command, CIPSAM...................................................................................................290STATUS Command, CIPSAM.....................................................................................................291STOP Command, CIPSAM.........................................................................................................291TRACE Command, CIPSAM.......................................................................................................292VERSION Command, CIPSAM...................................................................................................293

12 CLIMCMD and CLIMCMD climconfig Commands (Man Pages)...................29413 Support and other resources.........................................................................295

Accessing Hewlett Packard Enterprise Support...............................................................................295Accessing updates............................................................................................................................295Websites...........................................................................................................................................296Customer self repair.........................................................................................................................296Remote support................................................................................................................................296Documentation feedback..................................................................................................................296

1 Standalone Commands (Man Pages).............................................................297clim(1)...............................................................................................................................................298climstatus(1).....................................................................................................................................300ifstart(1).............................................................................................................................................302ifstop(1).............................................................................................................................................303prov(1p)............................................................................................................................................304psclim(1)...........................................................................................................................................306

2 Climconfig (Man Pages)..................................................................................307climconfig(1).....................................................................................................................................308climconfig.all(1).................................................................................................................................309climconfig.arp(1)...............................................................................................................................310climconfig.bondmode(1)...................................................................................................................312climconfig.climiptables(1)..................................................................................................................314climconfig.failover(1).........................................................................................................................316climconfig.hostname(1).....................................................................................................................319climconfig.hosts(1)............................................................................................................................320climconfig.interface(1).......................................................................................................................323climconfig.ip(1)..................................................................................................................................330climconfig.ip6tables(1)......................................................................................................................333climconfig.iptables(1)........................................................................................................................345climconfig.prov(1).............................................................................................................................356climconfig.psk(1)...............................................................................................................................358climconfig.remote(1).........................................................................................................................360climconfig.resolver(1)........................................................................................................................365climconfig.route(1)............................................................................................................................370climconfig.sa(1).................................................................................................................................376climconfig.slaveinterface(1)..............................................................................................................382climconfig.snmp(1)............................................................................................................................385climconfig.sp(1).................................................................................................................................387climconfig.sysctl(1)...........................................................................................................................392climconfig.tunnel(1)...........................................................................................................................394climconfig.vpn(1)...............................................................................................................................397

A SCF Error Messages.......................................................................................399B Fault Codes.....................................................................................................417Index...................................................................................................................435

8 Contents

Figures1 Distribution of Functionality in the CIP Subsystem......................................................................272 Multiple CLIMs per Provider, Example Configuration..................................................................283 Multiple Providers per CLIM, Example Configuration.................................................................294 Intra-CLIM Interface Failover.......................................................................................................325 CLIM-to-CLIM Failover, Single Interface.....................................................................................346 Full CLIM Failover.......................................................................................................................357 Bound Socket Problem Configuration Without Policy Based Routing.........................................738 Bound Socket Problem Configuration With Policy Based Routing..............................................749 Server Socket Problem Configuration Without Policy Based Routing........................................7510 Server Socket Problem Configuration With Policy Based Routing.............................................7611 Configuration State......................................................................................................................8912 Configuration State......................................................................................................................9013 Two Interfaces Connected To The Same Subnet......................................................................17914 Two CLIMs Connected to the Same Subnet.............................................................................18015 CIP SCF Object Hierarchy........................................................................................................212

Tables1 Interface Resource Failover Behavior.........................................................................................362 Interface Type for Failover Behavior...........................................................................................383 Interface Locations of NICs on CLIM Models..............................................................................394 CLIM-to-CLIM Failover................................................................................................................405 CIP Process Naming Conventions..............................................................................................536 Sample Safe Linux Commands...................................................................................................597 Custom CIP Commands..............................................................................................................618 Sample CLIM upgrade form, all types.......................................................................................1319 Sample populated Storage CLIM upgrade form........................................................................13410 Sample populated IP CLIM upgrade form.................................................................................13711 Sample populated Telco CLIM upgrade form............................................................................13912 Firmware Update Time Estimates and Calculation Form..........................................................14813 Sample populated Storage CLIM group upgrade form.............................................................15614 Sample populated IP CLIM group upgrade form.......................................................................15815 Sample populated Telco CLIM group upgrade form..................................................................15916 Sample populated IP CLIM group upgrade form.......................................................................16017 High-Level Differences Between Conventional TCP/IP, Parallel Library TCP/IP, NonStop

TCP/IPv6, and CIP....................................................................................................................16818 Subsystem Task Comparison....................................................................................................16919 Differences in Socket Options Defaults.....................................................................................18720 TCP/IP Attribute Default Values and Ranges............................................................................19421 TCP/IP Attributes, CIP Equivalents, and their CIP Default Values and Ranges.......................19422 IOAM and CLIM Based Operations Comparison......................................................................19823 CLIM Based Operations Information.........................................................................................19924 IOAM and Telco CLIM Based Operations Comparison.............................................................20925 Commands and Object Types for CIPMAN...............................................................................21126 Commands and Object Types for CIPSAM...............................................................................21127 Object Naming Convention Summary and Reserved Names ..................................................21428 Command and Object Type Abbreviations................................................................................21629 Object Summary States ...........................................................................................................21630 Object State Descriptions..........................................................................................................21631 Sensitive and Nonsensitive SCF Commands...........................................................................217

Examples1 Configure Failover for the CLIMs................................................................................................572 Climstatus Command ServerNet Status Information, IP and Telco CLIM...................................783 Climstatus Command ServerNet Status Information, Storage CLIM..........................................794 Climstatus Command NonStop X Status Information.................................................................795 Climstatus Command Ethernet LAN Status (IP and Telco CLIM)...............................................796 Climstatus Command Ethernet LAN Status (IP and Telco CLIM), NonStop X............................807 Climstatus Command IP Routing Table Information (IP and Telco CLIM) (J06.10/H06.21 and

later RVUs)..................................................................................................................................818 Climstatus Command IP Routing Table Information (IP and Telco CLIM) (RVUs prior to

J06.10/H06.21.............................................................................................................................829 Climstatus Command Hard Disk Space Usage..........................................................................8310 Climstatus Command Failover Configuration (IP CIP)................................................................8311 Climstatus Command IPSec Configuration (IP and Telco CLIM)................................................8312 Climstatus Command SNMP Information....................................................................................8413 Climstatus Command CLIM Configuration..................................................................................8414 psclim Command.........................................................................................................................8515 CLIM-to-CLIM Failover (IP CIP)..................................................................................................8716 Inbound FTP Traffic...................................................................................................................10217 Allow Inbound SNMP TRAPS...................................................................................................10318 Ethtool Link Speed Display.......................................................................................................11519 Using tcpdump..........................................................................................................................11920 Enabling MULTIPROV...............................................................................................................12221 Disabling MULTIPROV..............................................................................................................12322 Changing Providers...................................................................................................................12323 Changing Providers or Adding New Providers..........................................................................12424 Collect Debug Data From Single CLIM.....................................................................................20125 Collect Debug Data From Multiple CLIMs.................................................................................20226 Using Help to Obtain Information About an Error......................................................................21727 ABORT CLIM.............................................................................................................................21828 ABORT MON.............................................................................................................................21929 ABORT PROCESS...................................................................................................................22030 ABORT PROVIDER..................................................................................................................22031 ADD IP CLIM.............................................................................................................................22232 ADD IP CLIM, NonStop X.........................................................................................................22233 ADD Storage CLIM....................................................................................................................22234 ADD Storage CLIM, NonStop X................................................................................................22235 ADD PROVIDER.......................................................................................................................22436 ADD ROUTE.............................................................................................................................22637 ALTER CLIM With MULTIPROV ON.........................................................................................22638 ALTER PROVIDER...................................................................................................................22739 DELETE CLIM...........................................................................................................................22840 DELETE PROVIDER.................................................................................................................22841 DELETE ROUTE.......................................................................................................................22942 INFO CLIM, Summary, NonStop NS16000 Series Server........................................................23043 INFO CLIM, Summary, NonStop BladeSystem.........................................................................23044 INFO CLIM With Summary Display, NonStop X........................................................................23045 INFO CLIM, Detailed, IP CLIM, NonStop BladeSystem............................................................23146 INFO CLIM, Detailed, IP CLIM, NonStop X...............................................................................23247 INFO CLIM Detailed, Telco CLIM, OPEN MODE, NonStop BladeSystem................................23348 INFO CLIM Detailed, Storage, NonStop BladeSystem.............................................................23449 INFO CLIM Detailed, Storage, NonStop X................................................................................23450 INFO CLIM With OBEYFORM Display, NonStop BladeSystem................................................234

51 INFO CLIM With OBEYFORM Display, NonStop X..................................................................23452 INFO PROCESS Summary.......................................................................................................23553 INFO PROVIDER Summary Display.........................................................................................23554 INFO PROVIDER With Detailed Display...................................................................................23555 INFO PROVIDER (Maintenance) Detailed................................................................................23756 INFO PROVIDER (Maintenance) With OBEYFORM................................................................23757 INFO PROVIDER (IPDATA) With OBEYFORM........................................................................23858 INFO PROVIDER (ZTCO) With OBEYFORM...........................................................................23859 INFO ROUTE Summary............................................................................................................23960 INFO ROUTE With OBEYFORM..............................................................................................23961 LISTOPENS MON Summary....................................................................................................23962 LISTOPENS MON Detailed.......................................................................................................24063 LISTOPENS PROVIDER Summary..........................................................................................24264 LISTOPENS PROVIDER Detailed............................................................................................24365 NAMES $ZZCIP........................................................................................................................24566 NAMES CLIM............................................................................................................................24567 NAMES MON............................................................................................................................24668 NAMES PROCESS...................................................................................................................24669 NAMES PROVIDER..................................................................................................................24670 NAMES ROUTE........................................................................................................................24771 PRIMARY PROCESS...............................................................................................................24772 START CLIM.............................................................................................................................24873 START PROCESS....................................................................................................................24874 START PROVIDER...................................................................................................................24875 STATS CLIM..............................................................................................................................24976 STATS MON..............................................................................................................................25177 STATUS CLIM Summary, BladeSystem....................................................................................25478 STATUS CLIM Summary, NonStop X........................................................................................25479 STATUS CLIM Detailed.............................................................................................................25580 STATUS CLIM Detailed, NonStop X.........................................................................................26081 STATUS CLIM Summary, NonStop X Systems.........................................................................26582 STATUS CLIM, Starting, BladeSystem.....................................................................................26583 STATUS CLIM, Detailed, Storage CLIM, BladeSystem............................................................26684 STATUS CLIM, Detailed, Storage CLIM, NonStop X................................................................26785 STATUS CLIM, Detailed, T0971 VPROC..................................................................................26886 STATUS MON Summary...........................................................................................................26987 STATUS MON Detailed.............................................................................................................26988 STATUS PROCESS Summary..................................................................................................27089 STATUS PROCESS Detailed....................................................................................................27090 STATUS PROVIDER Summary.................................................................................................27091 STATUS PROVIDER Detail.......................................................................................................27192 STATUS Maintenance PROVIDER Detail.................................................................................27493 STATUS PROVIDER Route......................................................................................................27494 STOP CLIM...............................................................................................................................27595 STOP MON...............................................................................................................................27696 STOP PROCESS......................................................................................................................27697 STOP PROVIDER.....................................................................................................................27798 SWITCH CLIM...........................................................................................................................27899 SWITCH CLIM RESTORE........................................................................................................278100 TRACE CLIM.............................................................................................................................280101 TRACE MON.............................................................................................................................281102 TRACE PROCESS....................................................................................................................282103 TRACE PROVIDER..................................................................................................................283104 VERSION CLIM Summary, IP...................................................................................................283105 VERSION CLIM Detailed, IP.....................................................................................................283

106 VERSION MON Summary........................................................................................................284107 VERSION MON Detailed...........................................................................................................284108 VERSION PROCESS................................................................................................................285109 ABORT PROCESS...................................................................................................................285110 INFO PROCESS (CIPSAM) Summary......................................................................................286111 INFO PROCESS (CIPSAM) Detailed........................................................................................286112 INFO SUBNET (CIPSAM).........................................................................................................289113 INFO SUBNET Detailed............................................................................................................289114 NAMES SUBNET (CIPSAM).....................................................................................................290115 PRIMARY PROCESS (CIPSAM)..............................................................................................291116 STATUS SUBNET (CIPSAM)....................................................................................................291117 STOP PROCESS (CIPSAM).....................................................................................................292118 TRACE PROCESS (CIPSAM)..................................................................................................293119 VERSION PROCESS................................................................................................................293

About This DocumentThis manual provides overview information about the HPE NonStop Cluster I/O Protocols (CIP)subsystem as well as procedures for configuring, managing, and migrating to CIP.

Supported Release Version Updates (RVUs)This manual supports L15.02 and subsequent L-series RVUs, J06.05 and subsequent J-seriesRVUs, and H06.16 and subsequent H-series RVUs until otherwise indicated in a replacementpublication.

Intended AudienceThis manual is intended for network and storage administrators who need procedures for installingand managing the CIP subsystem on an HPE Integrity NonStop system; system planners andother decision makers can also use this manual to study the CIP product and the migrationrequirements for using CIP.

New and Changed InformationNew and Changed Information in the 541613–027 Edition

• Removed note from the “CIP Hardware Overview” (page 22) section, “IB CLIMS are notsupported by NonStop Systems.”

• Added section “InfiniBand Access Control List (IBACL)” (page 25).

• Added section “Enabling root Access for Non-Super Users” (page 62). Throughout themanual, updated statements about operations than can be executed by members of thesuper group that now can be executed by members of the SafeguardSECURITY-CLIM-ADMIN group.

• Updated note in “Managing the CLIM Configuration Preservation” (page 106) section.

• Added section “Apply CLIM Hotfix Software Patches” (page 162).

• Updated table in section “Collecting CLIM Log Files using CLIMDBUG” (page 200)

• Added information to “STATUS CLIM, Detailed, T0971 VPROC” (page 268).

• Added detailed information on Open CLIMs to “Failover in the CIP Subsystem” (page 31)

• Updated “STATUS CLIM” (page 253) with new flag and status.

• Added these commands to “Climconfig (Man Pages)” (page 307), for CLIM DNS resolution:

climconfig.hosts◦◦ climconfig.resolver

• Updated climconfig.failover with -autofo option “Climconfig (Man Pages)” (page 307), forCLIM failover.

New and Changed Information in the 541613-026R Edition• Updated Hewlett Packard Enterprise references.

New and Changed Information in the 541613-026 Edition• Update the “OSM” (page 26) section.

• In section “CLIM Bonded Interfaces” (page 38), remove G6 CLIM-specific paragraph.

Supported Release Version Updates (RVUs) 13

• Update the “Restarting CIP on the NonStop Host System” (page 93) section.

• In section “Configuring Stream Control Transmission Protocol (SCTP) (IP and Telco CIP)”(page 104), add command to set SCTP protocol.

• Update the “CLIM and Host Incompatibility” (page 118) section.

• Update the “Upgrading CLIM Software and Firmware” (page 128) section.

• Update the “Updating CLIM Software Using the OSM Low-Level Link (H- and J-Series RVUs)”(page 140) section.

• Update the “Updating Individual CLIM Software Using the CLIM Management Tool ” (page 142)section.

• Update the “Preparing to Update CLIM Firmware with the System Running” (page 144) section.

• Update the “Prepare CLIMs for Down System Firmware Update” (page 161) section.

• Update the “Update CLIM Software on a Down System” (page 161) section.

• In table “TCP/IP Attribute Default Values and Ranges” (page 194), change TCPSENDSPACEand TCPRECVSPACE default and maximum values from 61400 to 61440.

• In table “TCP/IP Attributes, CIP Equivalents, and their CIP Default Values and Ranges”(page 194), change MAX-PRIV-PORT (built-in) maximum value from 1048576 to 1023.

• Update the “Collecting iLO and IML Logs” (page 204) section.

• In “Fault Codes” (page 417), update the Recovery section for Fault Code 1011.

• In “Fault Codes” (page 417), update the Recovery section for Fault Code 1020.

New and Changed Information in the 541613-025 Edition• Made these changes throughout the manual:

Changed all occurrences of “Storage CIP” to “Storage CLIM.”◦◦ Changed IP address examples to more appropriate values.

◦ To eliminate redundancy across manuals, referred to planning guides for specific systemsfor descriptions and examples of supported CLIM models and for naming conventions.

◦ Added references to the L15.02 RVU and the NonStop X system.

◦ Indicated that IB CLIMs are not supported on NonStop X systems, but added explanatorytext about InfiniBand usage in the “Collecting IB Network Status” (page 207) section.

• In Chapter 1, updated these subsections:

Made general updates to overview information.◦◦ Under “CIP Hardware Overview” (page 22), removed references to Carrier Grade (CG)

because there is no software difference between CLIM and CLIM CG (the only differenceis hardware).

◦ Added note to “Using Multiple SWAN Paths in a Single Provider” (page 29) that SWANis not supported on systems running L15.02 and later.

◦ Under CIP CLIM Software Overview, added the new subsection, “Maintenance EntityUnit (MEU) Subsystem” (page 25).

◦ Added information to “CLIM Bonded Interfaces” (page 38).

◦ Indicated that one cause of processor failure could be interconnect failure between allprocessors and the CLIM. See “CLIM-to-CLIM Failover” (page 40).

14

◦ Under “IP CLIM” (page 48) and “IB CLIM” (page 49), eliminated redundant specificinformation and diagrams; referred to the appropriate planning guides.

◦ Under “The CIP Subsystem for Storage I/O and the Storage Subsystem” (page 49),referred to planning guides for Storage CIP hardware descriptions, illustrations, andsupported models.

◦ Under “Subsystem ID and Product Numbers” (page 50), added components and theirproduct numbers.

◦ Under “Capacity and Resource Use” (page 51), indicated the capacities of componentsused with CIP.

• In Chapter 3, updated these subsections:

Added a note to “Update CLIM Software on a Down System” (page 161) aboutprerequisites for using this section.

◦

◦ In a note under “Upgrading CLIM Firmware with the System Running” (page 144),indicated firmware should be updated using this method only if it is flagged as downrevision by OSM.

◦ Under “Displaying CLIM Status Information With climstatus” (page 77) and “MonitoringCLIM Devices and Network Interfaces” (page 86), changed the -s option for statusinformation.

◦ Under “NonStop X Status” (page 79), added new subsection and example to provideNonStop X status information.

◦ Updated “Climstatus Command Ethernet LAN Status (IP and Telco CLIM), NonStop X”(page 80) to show output for LAN Interfaces status on NonStop X systems for CLIMswith the MultiProv feature enabled.

◦ Updated and corrected the procedural steps under “Starting CIP on the NonStop HostSystem” (page 91).

◦ Indicated “Running Applications in Multiple Environments (IP CIP)” (page 105) and“Planning for Coexistence With Conventional TCP/IP (IP CIP Only)” (page 108) applyonly to H-series and J-series RVUs.

◦ Under “Avoiding Interfaces With Link Pulse Down” (page 178), added L15.02 to supportedRVU information.

◦ Enhanced the procedure for “Stopping CIP” (page 110).

• In Chapters 1, 3 and 4, updated OSM information for these sections:

In Chapter 1, included OSM information in the new section, “Maintenance Entity Unit(MEU) Subsystem” (page 25).

◦

◦ In Chapter 1, changed information under “OSM” (page 26).

◦ In Chapter 3, updated these sections with OSM changes:“Restarting CIP on the NonStop Host System” (page 93)–

– “Stopping CIP” (page 108)

New and Changed Information 15

– “CLIM and Host Incompatibility” (page 118)

– “Troubleshooting Network Applications Using Tcpdump” (page 118)

◦ In Chapter 4, updated these sections with OSM changes:– Added two L-series firmware components to “Firmware Update Time Estimates

and Calculation Form” (page 148)– “Upgrading CIP” (page 126)

– “Replace CIPMAN and CIPMON Simultaneously” (page 127)

– “Upgrading CLIM Software and Firmware” (page 128)

– “Upgrading CLIM Software with the System Running” (page 130)

– “Upgrading CLIM Firmware with the System Running” (page 144)

– “Identifying the Target Software” (page 131)

– Added a new section, “Updating Individual CLIM Software Using the CLIMManagement Tool ” (page 142) and added links to it in various sections on specificCLIMs.

– “Upgrading CLIM Software or Firmware While the System is Down ” (page 160)

– “Prepare CLIMs for Down System Firmware Update” (page 161)

– “Update CLIM Software on a Down System” (page 161)

– “Update CLIM Firmware on a Down System” (page 162)

– “Load the System” (page 162)

• In Chapter 5, made these changes:

Changed all occurrences of “Storage CIP” to “Storage CLIM.”◦◦ Expanded on the description of the “Delete Command” (page 164).

◦ Under “Example of lunmgr Enclosures Command” (page 165), made minor edits.

◦ Under “Example of lunmgr Find Command” (page 165), added data to the table.

◦ Under “Renumber Command” (page 166), made minor edits.

◦ Changed the information for “Considerations for the Update Command” (page 167).

◦ Clarified information throughout the chapter.

• In Chapter 7, made these changes:

Changed all occurrences of “Storage CIP” to “Storage CLIM.”◦◦ Deleted out-of-date information about introducing the CLIM systems.

◦ Deleted commands that are seldom used.

◦ In “IOAM and CLIM Based Operations Comparison” (page 198), changed “Add a storagecommunication device” to “Add a CLIM.”

◦ In “CLIM Based Operations Information” (page 199), removed the Carrier Grade IP CLIM.

• Throughout the manual, indicated that IB CLIMs are not supported on NonStop X systems.In Chapter 8 under “Collecting IB Network Status” (page 207), indicated that although NonStop

16

X systems do not use InfiniBand networks for external connectivity, they do use InfiniBandnetworks for internal connectivity.

• Added a new chapter, “Dump to ME Unit (L-Series Only)”.

• In Chapter 10, updated SCF commands to support NonStop X systems and made generalchanges:

◦ Indicated throughout that the LOCATION and CONNPTS attributes are used in J- andH-series only.

◦ Under ADD commands, added information for “ADD CLIM Command Syntax for NonStopX Systems” (page 221).

◦ Under “ADD IP CLIM” (page 222) and “ADD Storage CLIM” (page 222), made additionsand changes for NonStop X systems.

◦ Under “INFO CLIM” (page 229), made additions and changes to command displays(examples) and field definitions.

◦ Under “STATS CLIM” (page 249),

◦ Under “STATUS Commands” (page 253), made additions and changes to commanddisplays (examples) and field definitions.

• In Appendix A, SCF Error Messages, changed the Recovery information for CIP 00013(zcip-err-location-incompatible) to include NonStop X systems.

• In Appendix B, Fault Codes, updated fault code Origin “CIP Manager” Fault Code 1011 andadded new fault code Origin "CIP Manager" Fault Code 1020.

• Under climstatus(1), changed the -s option for status information.

• Under psclim(1), added information on MEUs including an example.

New and Changed Information in the 541613-024 Edition• In Chapter 1, updated “Using Multiple SWAN Paths in a Single Provider” with details about

configuration under “Using Multiple Providers” (page 29).• In Chapter 3, corrected syntax in “Adding the Collector” under “Configuring Transport of

Authentication Events from CLIM” (page 99).• In Chapter 3, updated “climbkup and climrstrConsiderations” (page 107) with additional

information.• In Chapter 4, updated “Estimating Time for CLIM Firmware Updates” (page 148) and

“Performing CLIM Firmware Updates with the System Running” (page 150) to clarify steps.

Notation ConventionsGeneral Syntax Notation

This list summarizes the notation conventions for syntax presentation in this manual.UPPERCASE LETTERS

Uppercase letters indicate keywords and reserved words. Type these items exactly as shown.Items not enclosed in brackets are required. For example:MAXATTACH

Italic LettersItalic letters, regardless of font, indicate variable items that you supply. Items not enclosedin brackets are required. For example:

Notation Conventions 17

file-name

Bold TextBold text in an example indicates user input typed at the terminal. For example:

ENTER RUN CODE

?123CODE RECEIVED: 123.00

The user must press the Return key after typing the input.[ ] Brackets

Brackets enclose optional syntax items. For example:

TERM [\system-name.]$terminal-name

INT[ERRUPTS]

A group of items enclosed in brackets is a list from which you can choose one item or none.The items in the list can be arranged either vertically, with aligned brackets on each side ofthe list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. Forexample:

FC [ num ][ -num][ text]

K [ X | D ] address

{ } BracesA group of items enclosed in braces is a list from which you are required to choose one item.The items in the list can be arranged either vertically, with aligned braces on each side of thelist, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example:

LISTOPENS PROCESS { $appl-mgr-name }{ $process-name }

ALLOWSU { ON | OFF }

| Vertical LineA vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces.For example:

INSPECT { OFF | ON | SAVEABEND }

… EllipsisAn ellipsis immediately following a pair of brackets or braces indicates that you can repeatthe enclosed sequence of syntax items any number of times. For example:

M address [ , new-value ]…

- ] {0|1|2|3|4|5|6|7|8|9}…

An ellipsis immediately following a single syntax item indicates that you can repeat that syntaxitem any number of times. For example:

"s-char…"

PunctuationParentheses, commas, semicolons, and other symbols not previously described must betyped as shown. For example:

18

error := NEXTFILENAME ( file-name ) ;

LISTOPENS SU $process-name.#su-name

Quotation marks around a symbol such as a bracket or brace indicate the symbol is a requiredcharacter that you must type as shown. For example:

"[" repetition-constant-list "]"

Item SpacingSpaces shown between items are required unless one of the items is a punctuation symbolsuch as a parenthesis or a comma. For example:

CALL STEPMOM ( process-id ) ;

If there is no space between two items, spaces are not permitted. In this example, no spacesare permitted between the period and any other items:

$process-name.#su-name

Line SpacingIf the syntax of a command is too long to fit on a single line, each continuation line is indentedthree spaces and is separated from the preceding line by a blank line. This spacingdistinguishes items in a continuation line from items in a vertical list of selections. For example:

ALTER [ / OUT file-spec / ] LINE

[ , attribute-spec ]…

Notation for MessagesThis list summarizes the notation conventions for the presentation of displayed messages in thismanual.Bold Text

Bold text in an example indicates user input typed at the terminal. For example:

ENTER RUN CODE

?123CODE RECEIVED: 123.00

The user must press the Enter key after typing the input.Nonitalic Text

Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactlyas shown. For example:Backup Up.

Italic TextItalic text indicates variable items whose values are displayed or returned. For example:

p-register

process-name

[ ] BracketsBrackets enclose items that are sometimes, but not always, displayed. For example:

Event number = number [ Subject = first-subject-value ]

Notation Conventions 19

A group of items enclosed in brackets is a list of all possible items that can be displayed, ofwhich one or none might actually be displayed. The items in the list can be arranged eithervertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair ofbrackets and separated by vertical lines. For example:

proc-name trapped [ in SQL | in SQL file system ]

{ } BracesA group of items enclosed in braces is a list of all possible items that can be displayed, ofwhich one is actually displayed. The items in the list can be arranged either vertically, withaligned braces on each side of the list, or horizontally, enclosed in a pair of braces andseparated by vertical lines. For example:

obj-type obj-name state changed to state, caused by{ Object | Operator | Service }

process-name State changed from old-objstate to objstate{ Operator Request. }{ Unknown. }

| Vertical LineA vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces.For example:

Transfer status: { OK | Failed }

% Percent SignA percent sign precedes a number that is not in decimal notation. The % notation precedesan octal number. The %B notation precedes a binary number. The %H notation precedes ahexadecimal number. For example:

%005400

%B101111

%H2F

P=%p-register E=%e-register

Related InformationProcedures that apply to the CIP subsystem but which are documented in other Hewlett PackardEnterprise manuals are not duplicated here. This subsection provides a guide to those proceduresand other related documentation.

Related Documents

CIP Subsystem OperationsIn addition to this manual, to operate the CIP subsystem, you may need to refer to the SCFReference Manual for the Kernel Subsystem for information about managing persistence forgeneric processes. The CIPMAN, CIPMON and CIPSAM processes are added and managedthrough the Kernel subsystem. If you are managing the storage subsystem, also refer to the SCFReference Manual for the Storage Subsystem.

Linux Man Page Documentation and HelpYou can get information about networking and IP protocol configuration from man pages andhelp residing on your CLIM. Use the CLIMCMD man command from the NonStop host system,followed by the feature for which you are seeking information. For example, N1002532 is the

20

host name of one of the CLIMs. (See “Displaying Man Pages for CIP Commands” (page 85) forthe complete syntax):TACL> CLIMCMD n1002532 man climconfig

Press Enter before the output display starts. After all the output has been displayed, press theq (quit) key to return to the TACL prompt.This example displays information about the Linux free command:TACL> climcmd n1002581 man free

To obtain information about the climconfig utility itself, enter:TACL> CLIMCMD n1002532 climconfig -help

This command displays the climconfig syntax, including the version number and the supportedclimconfig commands.Alternatively, you can append the man command with the | more option. For example:TACL> CLIMCMD dl385p man climconfig ~| more

GlossaryThe terms used in this manual are defined in the common Glossary. The Glossary is locatedunder G in the NonStop Technical Library.

Publishing History

Publication DateProduct VersionPart Number

June 2016H01541613-027

November 2015H01541613-026R

September 2015H01541613-026

February 2015H01541613-025

March 2014H01541613-024

Publishing History 21

1 OverviewCluster I/O Protocols (CIP) is a subsystem that manages and configures I/O and networkingprotocols on the CLuster I/O Modules (CLIMs) in a NonStop system. CIP is supported on systemsrunning L15.02 and later L-series RVUs, J06.04 and later J-series RVUs, and H06.16 and laterH-series RVUs (H-series is only supported on NS16000).

CAUTION: The CIP subsystem includes a front-end device running the Linux operating system.Do not use any Linux command that is not documented in this manual as a supported command.Using unsupported Linux commands can cause failure of the CIP subsystem.

This chapter provides an overview of the CIP subsystem including:

• “CIP Hardware Overview” (page 22)

• “CIP NonStop Host System Software Overview” (page 23)

• “CIP CLIM Software Overview” (page 24)

• “The CIP Subsystem for Internet Protocols (IP CIP)” (page 26)

• “The CIP Subsystem for Storage I/O and the Storage Subsystem” (page 49)

• “Subsystem ID and Product Numbers” (page 50)

• “Capacity and Resource Use” (page 51)

Internet Protocol Version 6 (IPv6) ComplianceThe CLIM complies with Internet Protocol version 6 (IPv6), an Internet Layer protocol forpacket-switched networks, and has passed official certification of IPv6 readiness.

CIP Hardware OverviewThe CLuster I/O Module (CLIM) provides the hardware interface for the CIP subsystem. Thereare several CLIM models. For a detailed description of supported hardware as well as whetheryour system requires a NonStop system console that supports DHCP and TFTP, see the planningguide for your system.The CLIM can be configured for:• IP protocols (IP CLIM)

IP CLIMs are configured with a Mode attribute of IP

• Storage protocols (Storage CLIM)Storage CLIMs are configured with a Mode attribute of STORAGE

• Telco protocols (Telco CLIM)Telco CLIMs are configured with a Mode attribute of OPEN

• IB protocols (IB CLIM)IB CLIMs are configured with a Mode attribute of OPEN

22 Overview

The IP and Telco (OPEN mode) CLIMs are configured similarly and provide similar services.Notable differences are that the Telco CLIM provides additional services provided by HPEOpenCall software for telecommunications. For information about the OpenCall product, see theGuide to Operations and Maintenance for HPE OpenCall Intelligent Network Server and theInstallation Guide For HPE OpenCall Intelligent Network Server.IB CLIMs (OPEN mode) provide InfiniBand connectivity to a customer-supplied IB switch usinga customer-supplied cable as part of the Low Latency Solution.

NOTE: To find out if your system supports Telco or IB CLIMs, see the planning guide for yoursystem.

CIP NonStop Host System Software OverviewCIP provides an integrated manageability solution from the NonStop host system to manage theLinux capabilities of the CLIM. CIP uses SCF for its command line interface and OSM, EMS, andthe NonStop I/O Essentials plug-in to HPE Systems Insight Manager (SIM) for configuration,control, and management of the NonStop connection to the CLIM, of TCP/IP, IPSec, and of LUNson the CLIM. CIP on the host also converts CLIM syslog and evlog events to EMS events.

NonStop Host System ManagementThe Subsystem Control Facility (SCF) is the management tool for the NonStop host systemobjects. The objects in the NonStop host system allow monitoring of subsystem status andstatistics and provide a TCP/IP process to serve as a transport-service provider for NonStop hostsystem socket applications.For information about SCF, see Chapter 11 (page 210).

Configuration PersistencePersistence in the NonStop host system is provided through the system configuration databaseand the persistence manager, which store and start the CIPMAN, CIPMON, CIPSAM (IP CIPonly) SCF objects ($ZZKRN.#ZZCIP, $ZZKRN.#cipsam_name and $ZZKRN.#CIPMON).

Maintenance ProviderTwo SCF Provider objects (see “PROVIDER Object” (page 213)) are configured by default on twoIP or Telco CLIMs (one each) to provide OSM connectivity from the NonStop host system to thededicated service LAN and to support dedicated-service LAN traffic. These maintenance Providers(MPs) connect through a logical interface (eth0:0).The TYPE attribute for the maintenance Provider is MAINTENANCE.

NOTE: The physical interface eth0 connects each CLIM to the dedicated service LAN. OnlyIP and Telco CLIMs can have the logical interface eth0:0 and the associated maintenanceProviders.

NOTE: In this manual, unless stated explicitly otherwise, “Provider” refers to an IPDATAProvider.

Maintenance Provider Restrictions

• There is no failover support for the maintenance Provider. However, Hewlett PackardEnterprise recommends configuring two maintenance Providers running on different CLIMswith different IP addresses. OSM can then switch to a different maintenance Provider if oneof them fails.

• The maintenance Provider supports only IPv4 addresses.

CIP NonStop Host System Software Overview 23

• The maintenance Provider does not support the IP loopback address (127.0.0.1), 127.*.*.*,class D, or class E IP addresses.

• There is a limit of one maintenance Provider interface and one maintenance Provider IPaddress for each CLIM.

CLIM Object Name and HostnameThe CLIM object name on the NonStop system must be the same as the host name on the CLIMitself for the CLIM to be brought to the STARTED state. You assign the name. Host names onCLIMs on different systems can be the same as long as the combination of the system nameand the host name on the CLIM are unique across the dedicated service LAN. For example, ifyou have two systems named \A and \B, you can have a CLIM with a host name of CLIM1 oneach system, since the combination of system name and CLIM name are unique.Neither the CLIM object name nor the host name on the CLIM can be changed while the CLIMobject is in the STARTED state. The CLIM object is configured by using SCF. The host nameon the CLIM is configured by using the climconfig tool.

CIP CLIM Software OverviewThe CLIM runs the Linux operating system offering many of the open source networking featuresand providing an intelligent device for storage applications. The CIP software on the CLIM usesLinux tools to configure and control TCP/IP and IPSec, SNMP agents for health monitoring, HPEIntegrated Lights Out (iLO) Management for low-level diagnostics, and the syslog and evlogevent mechanism for event reporting.When using CIP, you do not need to use Linux commands directly on the CLIM and in fact veryfew Linux commands are supported. Instead, use the CLIMCMD command line interface fromthe TACL prompt on the NonStop host system. The CLIMCMD CLI provides persistence andfailover for the configuration and also offers only Linux commands that are safe to execute onthe CLIM.

CLIM ManagementA combination of OSM, the CLIMCMD tool, I/O Essentials, and an integrated Lights OutManagement (iLO) interface are the management tools for the CLIM.

CLIMCMD ToolThe CLIMCMD tool provides a pass-through for commands issued from the NonStop host systemto the CLIM. This mechanism uses a Secure Shell (SSH) server accepting SSH requests fromthe NonStop host system.The CLIMCMD tool with the climconfig command is used to configure networking attributes,SNMP (for both IP and storage) and the LUN manager on the CLIM. The CLIMCMD tool is alsoused for other commands. See Chapter 3 (page 59) for a complete list of CLIMCMD utilities.You run the CLIMCMD tool on the NonStop host system from the TACL prompt.

NOTE: The default behavior of CLIMCMD is to not display the SSH Client banner. Effectivewith the J06.15 RVU, the SSH Client banner can be displayed in the output of CLIMCMD bysetting the TACL parameter SUPPRESSCLIENTBANNER to ‘N’ before executing CLIMCMD.To revert to the default behavior, explicitly set the TACL param SUPPRESSCLIENTBANNER toany value other than ‘N’. For example:

> $SYSTEM SYSTEM 25> climcmd N1002531 psclimPID RSS %MEM %CPU TIME START STAT CMD4829 1024 0.0 0.0 00:00:27 Oct 12 Sl /usr/local/bin/climmon --time 304974 1180 0.0 0.0 00:00:31 Oct 12 Sl confsync4975 23604 0.6 0.0 00:01:39 Oct 12 Sl cipssrv --number 04976 94008 2.3 0.5 00:44:18 Oct 12 Sl climagt --number 1

24 Overview

Termination Info: 0

> #SET #PARAM SUPPRESSCLIENTBANNER N> $SYSTEM SYSTEM 25> climcmd N1002531 psclimSSH client version T9999H06_14Jun2012_comForte_SSH_0092PID RSS %MEM %CPU TIME START STAT CMD829 1024 0.0 0.0 00:00:27 Oct 12 Sl /usr/local/bin/climmon --time 304974 1180 0.0 0.0 00:00:31 Oct 12 Sl confsync4975 23604 0.6 0.0 00:01:39 Oct 12 Sl cipssrv --number 04976 94008 2.3 0.5 00:44:18 Oct 12 Sl climagt --number 1Termination Info: 0

> #SET #PARAM SUPPRESSCLIENTBANNER Y> $SYSTEM SYSTEM 25> climcmd N1002531 psclimPID RSS %MEM %CPU TIME START STAT CMD4829 1024 0.0 0.0 00:00:27 Oct 12 Sl /usr/local/bin/climmon --time 304974 1180 0.0 0.0 00:00:31 Oct 12 Sl confsync4975 23604 0.6 0.0 00:01:39 Oct 12 Sl cipssrv --number 04976 94008 2.3 0.5 00:44:18 Oct 12 Sl climagt --number 1Termination Info: 0

Maintenance Entity Unit (MEU) SubsystemThe Maintenance Entity Unit (MEU) subsystem performs maintenance functions for NonStop X.The MEU runs on a Storage CLIM that has connectivity to both NonStop InfiniBand SAN andthe maintenance LAN (or dedicated service LAN) that provides down system support throughconsole-based OSM tools such as the System Startup Tool, System Configuration Tool, andCLIM Management Tool.The MEU is implemented as a software process running on the CLIM and is designed to coexistwith other CLIM functions.The MEU is automatically installed via the NonStop X CLIM DVD and activated on the first pairof Storage CLIMs included in each system (named SCLIM000 and SCLIM001 by default).NonStop X systems comprise two MEUs to achieve the maximum Reliability and Scalability(RAS) benefits. Each MEU will provide the following functionality:

• NonStop X System/Subnet Configuration

• NonStop X Maintenance Interfaces

• CLCI/CNSL bridge from NSK to a LAN-based terminal emulator (e.g., MR-Win6530)

• InfiniBand Subnet Manager (SM) server launch for the NonStop X system

• DHCP Server launch for the InfiniBand SAN

• CLIM Receive DumpFor most situations the two MEUs in a NonStop system will run independently of each other.There are some cases, however, where the peer MEUs will need to communicate to each othervia the NonStop InfiniBand SAN.For more information about configuring MEUs, refer to the OSM System Configuration Tool onlinehelp.

InfiniBand Access Control List (IBACL)The purpose of the IBACL process is to help prevent external servers using NSADI that areconnected to the same InfiniBand fabric(s) as the CLIM from interfering with CLIM operations.The IBACL instances running on the CLIMs housing the MEU have the additional responsibilityof preventing third-party InfiniBand Subnet Managers from disrupting the operation of the InfiniBandfabric(s) used by the NSK CPUs and the CLIMs.

CIP CLIM Software Overview 25

Integrated Lights Out (iLO)iLO is supported on the CLIM and is used for operator tasks such as remotely powering up ordown the CLIM and diagnostics. For more information about iLO features, refer to the HewlettPackard Enterprise website http://www.hpe.com/info/iLO. For instructions for invoking the iLOmanagement screen, see “Change the CLIM Passwords” (page 54).

OSMOSM provides the following support for managing and servicing CLIMs:

• CLIM configuration – For L-series, initial CLIM configuration is done through the SystemConfiguration Tool. For H- and J-series, use the OSM Low-Level Link.

• CLIM software and firmware updates – For L-series CLIM software and down system firmwareupdates, use the CLIM Management Tool. For H- and J-series, with the requisite OSMversion T0682H02^ADP or later, use the CLIM management Tool. For H- and J-series, theOSM Low-Level Link can also be used to update CLIM software. For all threads, the OSMService Connection can be used to update individual CLIM firmware while the system isrunning.

• Monitoring and servicing CLIMs – For monitoring the status of CLIMs, use the OSM ServiceConnection. The OSM Service Connection can also be used as an alternative to SCF foractions such as starting, stopping, adding, and deleting CLIM objects.

Additional information can be found in the relevant sections of this book, the CLuster I/O Module(CLIM) Installation and Configuration Guide for your RVU, the online help available within OSMapplications and tools, and in the OSM Configuration Guide.

HPE NonStop I/O EssentialsNonStop I/O Essentials is a plug-in to the Systems Insight Manager (SIM). HPE SIM is aninfrastructure management tool for Hewlett Packard Enterprise systems that runs on the systemconsole. The NonStop I/O Essentials plug-in provides a graphical user interface alternative tothe command line interfaces of the CLIMCMD tool and SCF.For more information about using NonStop I/O Essentials, see the NonStop I/O EssentialsInstallation and Quick Start Guide.

PersistencePersistence in the CLIM is provided by configuration files stored on the CLIM hard drive. Changesmade by using the CLIMCMD climconfig command line interface (CLI) to the protocol attributesare stored and are persistent. For example:> CLIMCMD n1002532 climconfig sysctl -update net.ipv4.tcp_keepalive_intvl 25

This command sets the time interval between the retransmissions of unacknowledged keepalivepackets to 25 seconds and the change is preserved across CLIM reboots.The persistent CLIM configuration is backed up by the CLIM backup utility and, in the event ofa CLIM failure or CLIM hard drive failure, can be restored onto the replacement CLIM by usingthe CLIM restore utility. See“Managing the Configuration Preservation” (page 105) for moreinformation about these utilities.

The CIP Subsystem for Internet Protocols (IP CIP)The Cluster I/O Protocols (CIP) subsystem provides an IP facility for the NonStop system thatleverages current, open-source networking features and takes advantage of the NonStop systemarchitecture for application scalability. The Cluster I/O Protocols (CIP) subsystem also providesTelco connectivity with management facilities and Telco applications on the NonStop host andTelco protocols on the CLIM. The CIP subsystem resides partly on the NonStop host systemand partly on the CLIM.

26 Overview

In the CIP subsystem, IP functionality is distributed between the NonStop system and the CLIM.Figure 1: Distribution of Functionality in the CIP Subsystem shows this distribution of functionality.

Figure 1 Distribution of Functionality in the CIP Subsystem

CIP includes a NonStop host system subsystem that provides:

• An application programmatic interface (API)

• Transport service providers

• A Subsystem Control Facility (SCF) interface for monitoring the subsystem and for configuringhost-to-CLIM relationships

NOTE: There are some migration considerations when porting applications from conventionaland Parallel Library TCP/IP and NonStop TCP/IPv6 to CIP. See Chapter 6 (page 168).

CIP provides a socket access method (SAM) process on the NonStop system for applicationsto use as a transport service provider.Monitoring and management of the CIP subsystem on the NonStop system is provided by SCFand by the CLIMCMD CLI. See Chapter 11 (page 210), for more information.You use the CLIMCMD climconfig tool to add, modify, delete, and display information in thenetwork, IPSec, and Failover configuration files. For more information about the climconfig tool,see “Climconfig (Man Pages)” (page 307).

IP ProtocolsIP CIP supports these protocols:

• Transmission Control Protocol/Internet Protocol (TCP/IP) (including IPv6 and IPv4)

• User Datagram Protocol (UDP)

• Stream Control Transmission Protocol (SCTP)

• IP Security (IPSec)

Telco ProtocolsTelco CIP supports the Message Transfer Part Level 3 User Adaptation layer (M3UA) protocol.

Multiple CLIMs per ProviderMultiple IP and Telco CLIMs can be configured in the same IPDATA Provider. This featureprovides scalability for applications that need high bandwidth. Unless the MULTIPROV attributeis set for multiple providers, as described under “Multiple Providers per CLIM”, a CLIM can onlybelong to one IPDATA Provider, but a maintenance provider can also be configured to use it.

The CIP Subsystem for Internet Protocols (IP CIP) 27

Figure 2 Multiple CLIMs per Provider, Example Configuration

Multiple Providers per CLIMFor the H06.25/J06.14/L15.02 RVUs and later, a CLIM can be associated with multiple dataproviders simultaneously. You can enable or disable this Multiple Providers per CLIM functionalityon a per-CLIM basis by setting a new MULTIPROV attribute of each CLIM object. See “ADDCLIM” (page 220), “ALTER CLIM” (page 226), and climconfig.prov(1).

NOTE: Detailed displays of command output in this manual are updated to show support forMultiple Providers per CLIM.

28 Overview

Figure 3 Multiple Providers per CLIM, Example Configuration

Using Multiple ProvidersYou can use multiple providers to customize network configurations to an application's needs,while isolating that application's configuration from other applications in other providers. Toassociate a CLIM and all of its interfaces with multiple providers, set the MULTIPROV attributeof the CLIM object to ON using the ADD CLIM or ALTER CLIM command. See “ADD PROVIDER”(page 223) and “ADD CLIM” (page 220).

Using Multiple SWAN Paths in a Single ProviderCIP supports configuring path A and path B in a SWAN configuration to run in the same Provideronly on a single CLIM. If you use two CLIMs in a SWAN configuration, you must use differentProviders.

NOTE: SWAN is not supported on systems running L15.02 and later.

Using Multiple Listeners with Round Robin SocketsNonStop TCP/IPv6 had a limitation of one listening process per processor per port. CIP doesnot have this limitation. There can be many listening processes per processor per port. The onlylimitation is the amount of memory available to create sockets.

Routing in the CIP SubsystemIn a Provider comprising multiple CLIMs, a socket that is bound to a specific local IP addressother than a loopback address (IPv4 127.0.0.1 or IPv6 ::1) is associated with a CLIM containingthat address. An outgoing connection or packet for these kinds of sockets is sent through thatCLIM.However, sockets not yet bound, bound to INADDR_ANY, or bound to a loopback address mightbe used to listen for incoming connections or packets on addresses that exist in all the CLIMsof a Provider and so are associated with all of the CLIMs. If the socket is used for an outgoingconnection or for sending a packet, the host must choose one of the CLIMs to send it. This

The CIP Subsystem for Internet Protocols (IP CIP) 29

process uses the destination address and is similar to IP routing, but is used only to select aCLIM within a Provider.With either type of binding, the sending CLIM then performs its own IP routing to select aninterface and the first hop in the external network.Network routes are configured on the CLIMs. You specify static routes by using CLIMCMDclimconfig commands. Dynamic routes are created by the system as the result of various protocolevents. CIP keeps separate routing tables for IPv4 and IPv6 destinations. Default routes have aprefix or subnet-mask length of zero and indicate where to send packets or connections whenno other routes match the destination address. Default routes can be static or dynamic. A CLIMthat does not have a default route cannot route to arbitrary destinations.If a CLIM is configured to join multiple providers, an independent set of routes is maintained foreach of the providers. When sending packets, only routes for the provider that was used to sendthe packet are used.Each CLIM uploads a copy of the statically-configured entries, entries added for each local IPaddress, and the dynamic default entries in its routing tables to the NonStop host system foreach interface as it reports that the interface is up. Each CLIM continues updating the host aschanges are made to its tables. The host merges the routing tables from all the CLIMs in aProvider into one IPv4 and one IPv6 table for the Provider. When the host needs to use adestination address to decide which CLIM gets an outgoing connection or packet, it consults thecorresponding table. If it finds that more than one CLIM could be used, it uses round-robinselection to help balance the load among them. Once the connection or packet gets to the CLIM,the CLIM uses its own tables to decide on an interface and first-hop destination.In many environments, nearly all CLIMs have default routes defined and most traffic uses theseroutes, so simple round-robin selection may not be adequate. The ROUTE object on the NonStophost system allows additional control of default route use. Each ROUTE object indicates a CLIMto use for a default route and a PRIORITY for its use. The PRIORITY is a number from 1 to 100where higher numbers indicate higher priority. The CLIM is considered only if it actually has adefault route defined in its routing table for the desired address family. When a default route isneeded, the CLIM with the highest priority is selected. If more than one CLIM has the highestpriority, round-robin selection is used. If no ROUTEs have an available CLIM, any CLIM with adefault route defined is used. If no CLIMs have a default route, the packet cannot be routed.Every CLIM contains a loopback interface (lo) and the loopback addresses for the configuredIP address families (IPv4 127.0.0.1 and/or IPv6 ::1). When a NonStop host system applicationconnects or sends to a loopback address or to a local address, the connection or data is sent toa CLIM and is looped back to the host using the loopback interface. If the sending socket is boundto a specific local IP address other than a loopback address, then the CLIM containing thataddress is chosen. If the socket is not bound or is bound to INADDR_ANY, the CLIM containingthe destination address is used. If the destination is a loopback address, any CLIM can be chosen.

NOTE: If a socket is bound to a specific local address and connects or sends to a local addresson a different CLIM, the data is passed from one CLIM to the other over the external network.Even though the addresses are both local in the Provider, a path through the external networkis required. Sockets bound to a loopback address are replicated in all the CLIMs of the Providerlike sockets bound to INADDR_ANY. If the socket is later used to listen for incoming connectionsor packets, it can get them at that address no matter to which CLIM they are directed.

The NonStop host system performs these steps to select a CLIM for an outgoing connection orpacket in Providers with multiple CLIMs:1. If the socket has bound to a specific local IP address other than a loopback address (127.0.0.1

or ::1), use the CLIM containing that address.2. If the destination address is a loopback address, make a round-robin selection of any CLIM.3. If the destination address is a local address in one of the CLIMs, use that CLIM.

30 Overview

4. If the destination address matches one or more network-route entries that are not defaultroutes, make a round-robin selection of one of the CLIMs containing the entries with thesame longest matching prefix or subnet-mask length.

5. Make a round-robin selection of any available CLIM that has a default network-route entry.When selecting a CLIM containing a default route, only the available CLIM(s) with the highestROUTE PRIORITY attribute value are considered. If there is more than one with the samehighest value, one is round-robin selected from that group. CLIMs with no ROUTE objectare considered to have the lowest priority, and if those are all that are available, one of themis round-robin selected.

6. If no available CLIMs have a default network-route entry, then no route can be found. Returnan error to the application.

Failover in the CIP SubsystemCIP failover allows the resources associated with a failing interface to be switched to anotherinterface so they remain available to the external network with minimal impact on socketapplications.Upon failure of one or more Ethernet interfaces or an entire CLIM, CIP can ensure the availabilityof the interface resources such as IP addresses, sockets, connections, routes, and tunnels byeither sharing those resources among multiple physical interfaces on the same CLIM or migratingthem to another interface on a different CLIM. While most resources can be migrated duringfailover, some are lost if migration to a different CLIM is required. This section defines resourcesand describes their treatment in failover situations.There are two types of failover in CIP: failover from one interface to another in the same CLIM,and failover from one CLIM to another.

Intra-CLIM Failover – OverviewIntra-CLIM failover occurs when a link to the external network has failed, but the CLIM is stilloperational. It is configured and handled completely within the CLIM by using bonded interfaces.The NonStop operating system does not need to take any action. All interface resources areswitched without disruption.Bonded interfaces share interface resources among multiple physical interfaces. They can beconfigured to be similar to NonStop TCP/IPv6 failover with the SHAREDIP option except thatthe interfaces must be in the same CLIM and are not limited to just two interfaces. Bondedinterfaces do not support a mode similar to the NonStop TCP/IPv6 NONSHAREDIP option inwhich each interface has a different IP address until failover.Figure 4: Intra-CLIM Interface Failover (page 32) illustrates intra-CLIM failover. The figure usesshaded rectangles to show CLIM interfaces, ovals for the resources using those interfaces, andlines for the physical interfaces associated with them. Bonded interface bond1 is defined in theCLIM to consist of the two slave physical interfaces: eth1 and eth2. If either slave interface goesdown, the other takes its traffic with no disruption. The NonStop OS tracks the bonded interface,not the slave interfaces, so no changes are made in the NonStop OS tables or resource locationswhen this occurs.

The CIP Subsystem for Internet Protocols (IP CIP) 31

Figure 4 Intra-CLIM Interface Failover

CLIM-to-CLIM Failover – OverviewCLIM-to-CLIM failover is invoked when a CLIM fails, a non-slave physical interface or bondedinterface fails, or an SCF SWITCH command is issued. Physical interfaces fail when their driverindicates a physical fault or link pulse remains down. Bonded interfaces fail when all their slaveinterfaces fail. During failover, most interface resources are switched to their configured backupinterfaces in other CLIMs, but since much of the connection state was saved inside the originalCLIM, TCP and SCTP connections are lost and applications are given ECONNRESET errors.Failure of an entire CLIM is treated as failure of all the interfaces on that CLIM and each interfaceis failed over to its configured failover destination individually.Interface resources are configured or created for each physical or bonded interface, called thehome interface, for those resources. These are listed in “Interface Names and Resources”(page 36). A separate failover interface can also be configured for each interface. The failoverinterface must be in the same broadcast domain as the home interface, its CLIM must be in thesame Provider, and if it uses failover, it must use this home interface as its failover interface. Itneed not be the same type of interface, physical or bonding, but the IP configuration shouldmatch to avoid unexpected changes in protocol behavior when failover occurs. Like interfaceconfiguration, failover configuration is specified on the CLIMs.If an interface or CLIM fails, its home interface resources are migrated to the failover interface(s)and become visiting resources. If the interface or CLIM becomes available again, its resourcesare not automatically moved back as this might disrupt TCP and SCTP connections. An SCFSWITCH command must be used to manually restore resources to their home interface. If thefailover interface or CLIM fails, an attempt is made to automatically restore the visiting resourcesback to their home interface.Failover interfaces must be configured in pairs, where each interface specifies either the otheras its failover interface or no failover. To spread the load on other CLIMs when a CLIM fails, each

32 Overview

of the interfaces in a CLIM can be paired with interfaces in different CLIMs under the sameProvider.For the H06.21/J06.10/L15.02 and later RVUs, CLIM-to-CLIM failover is supported for all typesof CLIMs, and Telco CLIMs do not require a unique Provider.Failover is not supported for the Maintenance Provider interface, only the data LAN interfaces.Multiple maintenance Providers can be configured on different CLIMs if fault-tolerance is desiredbut fault handling must be done explicitly by the applications in that case.Figure 5: CLIM-to-CLIM Failover, Single Interface (page 34) and Figure 6: Full CLIM Failover(page 35) both show CLIM-to-CLIM failover. Figure 5: CLIM-to-CLIM Failover, Single Interface(page 34) shows what happens when a single interface fails or loses network connectivity, butthe CLIM is still operational. The clim1.eth4 interface is paired with clim2.eth1 for failover. Whenclim1.eth4 fails, its resources are moved to clim2.eth1 and the NonStop OS updates its tablesso references to clim1.eth4 are directed to clim2.eth1.Third-party software not provided as part of the standard CLIM DVD can be loaded onto OpenCLIMs. The standard CLIM-to-CLIM failover model described above can interfere with theoperation of third-party software. For that reason, the CLIM supports a model of failover that isdirected by the third-party software, rather than by the standard CLIM software. There is an"autofo" option to the climconfig failover command to enable this functionality. See theclimconfig.failover man page for details.

The CIP Subsystem for Internet Protocols (IP CIP) 33

Figure 5 CLIM-to-CLIM Failover, Single Interface

Figure 6: Full CLIM Failover shows what happens when an entire CLIM fails. In the figure, CLIM2has failed and the resources for all its interfaces have moved to interfaces in other CLIMs. TheNonStop OS has updated its tables to refer to their new locations.

34 Overview

Figure 6 Full CLIM Failover

Failover Behavior in DetailThis section describes CIP failover in more detail, including:• “Interface Names and Resources”

• “CLIM Interface Types” (page 37)

• “CLIM Bonded Interfaces” (page 38)

• “CLIM-to-CLIM Failover” (page 40)

• “Fail Back (Restore Behavior)” (page 41)

The CIP Subsystem for Internet Protocols (IP CIP) 35

• “Failover Failure” (page 41)

• “CLIM Startup Behavior” (page 41)

Interface Names and ResourcesOn the NonStop system, interfaces are given a unique name within a Provider by pre-pendingthe CLIM home interface name with the CLIM name and a period (.). For instance: n1002531.eth4or n1012542.bond0.Physical and bonded interfaces are tied to physical ports and so cannot move in a literal sense.However, many of the resources associated with an interface can be moved from one interfaceto another, which is how failover works. The resources are given the name of their home interface,so one can say that n1002531.eth2 is currently located at n1012542.eth4, meaning that theresources configured or created for interface n1002531.eth2 have been moved to n1012542.eth4.The NonStop OS contains an interface table that gives the current location of each interfacename.On the CLIM, each interface can contain resources from either none, one, or two interface names.The normal state is to contain only the home resources. If CLIM resources have failed over, theCLIM has no resources and the interface is down. If the failover interface has failed, the homeCLIM contains both the home resources and the visiting resources from the failover interface.Visiting resources cannot be present unless the home resources are also present.Table 1: Interface Resource Failover Behavior summarizes the interface resources, how theyare created, and how they are migrated during failover. Bonded interfaces share many of theirresources among multiple physical interfaces, making intra-CLIM failover a matter of just lettingthe others take over the load. CLIM-to-CLIM failover requires actual migration of resources to anew location.

Table 1 Interface Resource Failover Behavior

CLIM-to-CLIM FailoverIntra-CLIM FailoverCreated byResource

Not migratedShared, migrated, or notmigrated depending onbonding mode

Hardware parameterMAC address

MigratedSharedConfigurationStatic IPv4 addresses

MigratedSharedConfigurationStatic IPv6 addresses

MigratedSharedProtocolLink-local andautoconfigured IPv6addresses

MigratedSharedApplicationsJoined-group multicast IPaddresses

MigratedSharedProtocolSolicited-node multicast IPaddresses

MigratedSharedApplicationsUDP sockets

MigratedSharedApplicationsTCP listening sockets

MigratedSharedConfigurationStatic routes

Not migrated, re-created asneeded

SharedProtocolsDynamic routes

Not migrated, must beconfigured the same on thefailover CLIM

SharedConfigurationStatic ARP entries

Not migrated, re-created asneeded

SharedProtocolDynamic ARP entries

36 Overview

Table 1 Interface Resource Failover Behavior (continued)

CLIM-to-CLIM FailoverIntra-CLIM FailoverCreated byResource

Not migrated, client canreestablish the connections

SharedApplicationsTCP connections

Not migrated, client canreestablish the connections

SharedApplicationsSCTP connections

Migrated when interfacecontaining the local addressis migrated

SharedConfigurationStatic IPv6-over-IPv4Tunnels

Not migrated, must beconfigured the same on thefailover CLIM

SharedConfigurationIPSec PSKs

Not migrated, renegotiatedby new endpoints

SharedNegotiationIPSec SAs

Not migrated, must beconfigured the same on thefailover CLIM

SharedConfigurationIPSec SPs

Not migrated, must beconfigured the same on thefailover CLIM

SharedConfigurationIPSec remotes

Not migrated, must beconfigured the same on thefailover CLIM

SharedConfigurationIPSec X.509 certificates

CLIM Interface TypesTable 2: Interface Type for Failover Behavior lists the various interface types supported by theCLIM and how they are supported by failover.

The CIP Subsystem for Internet Protocols (IP CIP) 37

Table 2 Interface Type for Failover Behavior

FailoverCharacteristicsInterface Type

Exists in every CLIM so failover is not needed.Cannot be configured for failover, but does

Loopback • Reflects output back to its input

• Named lo have an entry in the NonStop OS interfacetable.

Can be configured for CLIM-to-CLIM failover.The backup interface can be a physical orbonded interface.

Physical (non-slave) • Corresponds to a physical Ethernetinterface connected to a user network

• Reports link pulse from the physicalinterface

• Named by the CLIM kernel: eth1, eth2,…

Not supported and cannot be configured ondata LAN interfaces.

Logical • Adds an IP address to a physical interface

• Named by appending a colon (:) andnumber to the physical interface name:eth2:1

Can be configured for CLIM-to-CLIM failover.If all its slave interfaces fail, the interface

Bonding • Combines two or more physical interfacesfor fault tolerance

resources of the bonded interface are• Each physical interface is called a slave

interfacemigrated. The backup interface can be aphysical or bonded interface.

• Reports link pulse down only if down onall slave interfaces

• Named by the user, must be either :bond0 or bond1 (only two bondedinterfaces allowed on each CLIM)

Cannot be configured for failover and doesnot have an entry in the NonStop OS interfacetable.

• A physical interface that is combined intoa bonded interface

Slave

Follows the physical or bonded interfaceassociated with its local address. Cannot be

Static IPv6-over-IPv4Tunnel

• Encapsulates IPv6 packets inside IPv4packets.

individually configured for failover, but does• Named by the user, typically: TUN0,

TUN1, TUN2, …have an entry in the NonStop OS interfacetable.

Cannot be configured for failover and doesnot have an entry in the NonStopoperating-system interface table.

Maintenance Interface • Corresponds to a physical Ethernetinterface eth0 connected to the dedicatedservice LAN

• Used for CLIM access to the dedicatedservice LAN

• Named by the CLIM kernel as eth0. (Asingle wire from the eth0 interface to thededicated service LAN is used for botheth0 and eth0:0.)

Cannot be configured for failover and doesnot have an entry in the NonStop OS interface

Maintenance ProviderInterface

• Configured for maintenance Provider

• Used for NonStop OS access to thededicated service LAN

table for a data Provider. Does have an entryin the NonStop OS interface table for themaintenance Provider.• Associated with maintenance interface

eth0

• Added at startup, named eth0:0

CLIM Bonded InterfacesCIP supports failover of Ethernet interfaces within the same CLIM using the CLIM bonding driver.The bonding driver groups multiple physical interfaces, called slave interfaces, into a single

38 Overview

bonded interface. The bonding driver transparently handles failure of a slave interface by switchingtraffic to the others. The number of bonded interfaces and the number of slaves in each is limitedonly by the number of data LAN interfaces on the CLIM. Typically, the bonded interface takesup the MAC address of its first slave.A bonded interface can be configured to use one of several policies for fault tolerance andbandwidth aggregation. CIP supports all current policy modes as long as their prerequisites aremet. See “climconfig.bondmode Description” (page 312) for descriptions of the bonding modes.Interface resources are configured and created for the bonded interface, not the individual slaveinterfaces. CLIM-to-CLIM failover can switch a bonded interface to a configured failover interfaceby command or if the bonded interface indicates a failure. This occurs only if all its slaves havefailed.As of J06.10 and H06.21, the DL380 G6 CLIM is available, which has2 embedded NICs, one foreth0 and eth1 and the other for eth2 and eth3. It also has one external PCI NIC for eth4 andeth5. This allows you to create 2 bonded interfaces that are spread across two NICs, for exampleeth1 and eth4 as bond0, and eth2 and eth5 as bond 1. In this configuration losing one NIC willnot result in losing an entire bond.When configuring slaves in a bonded interface, it is recommended that the slaves be spreadacross separate Network Interface Cards (NICs) so that the failure of a network interface cardwill not result in the failure of both slaves. Configuring multiple slaves on the same NIC will stillallow redundancy from link or switch failures.Table 3: Interface Locations of NICs on CLIM Models shows the location of each interface onNICs for the different CLIM hardware models.

Table 3 Interface Locations of NICs on CLIM Models

NIC 3NIC 2NIC 1CLIM Model

eth4, eth5 (1Gb/s copper)eth2, eth3 (1Gb/s copper)eth1 (1Gb/s copper)H/J series G6 Copper

eth4, eth5 (1Gb/s fiber)eth2, eth3 (1Gb/s copper)eth1 (1Gb/s copper)H/J series G6 Fiber

ib0, ib1 (InfiniBand)eth2, eth3 (1Gb/s copper)eth1 (1Gb/s copper)H/J series G6 IB

N/Aeth4, eth5 (1Gb/s copper)eth1, eth2, eth3 (1Gb/scopper)

H/J series Gen8 Copper

N/Aeth4, eth5 (1Gb/s optical)eth1, eth2, eth3 (1Gb/scopper)

H/J series Gen8 Optical

eth5 (1Gb/s copper)eth3, eth4 (10Gb/s copper)eth1, eth2 (10Gb/s copper)NonStop X Gen8 Copper

eth5 (1Gb/s copper)eth3, eth4 (10Gb/s optical)eth1, eth2 (10Gb/s optical)NonStop X Gen8 Optical

N/Aeth4, eth5 (1Gb/s copper)eth1, eth2, eth3 (1Gb/scopper)

NonStop Entry-class Gen8

N/Aeth4, eth5 (1Gb/s copper)eth1, eth2, eth3 (1Gb/scopper)

J series Gen9 Copper

N/Aeth4, eth5 (1Gb/s copper)eth1, eth2, eth3 (1Gb/scopper)

J series Gen9 Optical

eth5 (1Gb/s copper)eth3, eth4 (10Gb/s copper)eth1, eth2 (10Gb/s copper)NonStop X Gen9 Copper

eth5 (1Gb/s copper)eth3, eth4 (10Gb/s copper)eth1, eth2 (10Gb/s copper)NonStop X Gen9 Optical

N/Aeth4, eth5 (1Gb/s copper)eth1, eth2, eth3 (1Gb/scopper)

NonStop X Entry-classGen9

The CIP Subsystem for Internet Protocols (IP CIP) 39

CLIM-to-CLIM FailoverCIP supports failover of individual interfaces from one CLIM to interfaces on other CLIMs underthe same Provider. Failover of an entire CLIM is treated as failover of all its interfaces. Table 4:CLIM-to-CLIM Failover describes the various scenarios of failure and resulting failover action:

Table 4 CLIM-to-CLIM Failover

Resulting Failover ActionProbable CausesFailure Definition

Initiate failover of all interfaces on theCLIM

Failure in all processors to receiveheartbeat from CLIM for more than aheartbeat time

• Interconnect failure between allprocessors and the CLIM

• CLIM panic halt or hang

• CLIM reboot

• CLIM CLIMCMD clim stopcommand

• CLIM software problem

Initiate interface failover.• NIC hardware failureFailure indication on data LANinterface or on all interfaces in abonded interface

No failover actionLoss of link pulse on data LANinterface or on all interfaces in a

• Transient condition

• Recoverable failure in bondedinterface

bonded interface for less than linkpulse time

• Cable briefly disconnected

• Cable permanently disconnected

• Switch or network down

Initiate interface failoverLoss of link pulse on data LANinterface or on all interfaces in a

• Cable permanently disconnected

• Switch or network downbonded interface for more than linkpulse time

No failover, but interface resourcesusing the interface becomeunavailable.

• CLIMCMD ifstop commandCLIM-initiated interface down on adata LAN interface

No action.Failure indication, loss of link pulse,or CLIM-initiated interface down onmaintenance interface

• NIC hardware failure

• Cable disconnected

• Switch or network down

• CLIMCMD ifstop command

Initiate CLIM or interface failover asdirected.

• SCF SWITCH CLIM commandOperator initiated failover

No failover, but the CLIM object goesto the STOPPED state. Interface

• SCF ABORT CLIM or STOP CLIMcommand

NonStop OS-initiated CLIM stop

resources still on the CLIM becomeunavailable. Those resources that havealready failed over to other CLIMsremain active unless the INTFALLoption is given.

Heartbeat time enforces sending a heartbeat signal from each CLIM to indicate it is runningproperly. Failover is triggered only when all NonStop system processors have lost contact withthe CLIM. Link pulse time keeps failover from triggering because of a transient link pulse problem.It is a fixed value less than two seconds.All changes in the CLIM interface status are reported as EMS messages even if they do not resultin failover.

40 Overview

Each individual interface can be configured with its own failover interface, including the CLIMand interface names. Failover interfaces are configured in pairs, so both interfaces of the pairspecify either the other as their failover interface or no failover. It is not necessary that all interfacesin a CLIM have their failover interfaces on the same CLIM. It is also acceptable for a failoverinterface to be a bonded interface or a physical interface regardless of the home-interfacetype.Table 1: Interface Resource Failover Behavior (page 36) summarizes how CLIM-to-CLIMfailover migrates each type of interface resource from the failed interface to the failover interface.“Interface Resource Migration” (page 42) describes migration of each of these resources in moredetail. A two-way periodic heartbeat timeout is used on both the NonStop host system and CLIMto detect failure of a CLIM, the host, or the fabric connection between them (ServerNet orInfiniBand). If a CLIM can no longer communicate with any processor in the NonStop host system,it removes all the IP addresses from its data LAN ports. If the NonStop host system is truly down,a down-state is conveyed to the external network. If the NonStop host system is actually still up,it allows the host to migrate the IP addresses to another CLIM. If no NonStop host systemprocessor can communicate with a CLIM, the host initiates a CLIM-to-CLIM failover of all theinterfaces on the CLIM. The resources for each interface are migrated to its configured failoverinterface. Each interface can have its own failover destination and hence a CLIM failover couldresult in failover of interfaces to multiple CLIMs. Each interface migrates separately from theothers. Hence, a problem migrating one interface does not affect the others.

Fail Back (Restore Behavior)Fail back or restore is only supported by a manual method and initiated from the host only byusing a SWITCH CLIM command. Fail back of interfaces also follows the “check-break-make”principle and the actual sequence is similar to a failover sequence. See “Failover in the CIPSubsystem” (page 31) for an overview of the CIP failover sequence.

Failover FailureWhen a CLIM-to-CLIM failover operation is started, the host tries to migrate the resources to thefailover interface and to the home interface alternately, separated by 10 seconds. If the resourcesare successfully brought up on one of the interfaces, failover is complete. If the resources cannotbe brought up on either interface within 10 seconds, the failover has failed. Sockets using theinterface are marked to return an error to the application on the next or current socket call andjoined multicast groups are removed from the interface resources. The remaining resources,such as IP addresses, become unavailable both to applications and to the external network.If the resources end up on the same interface where they started, which might happen if thefailed interface comes back up quickly, it is still a failover operation and resources normally notpreserved across a CLIM-to-CLIM failover are lost.After a failover failure, the host continues to try to migrate the remaining resources alternatelyto the home or failover interfaces until it either succeeds or an SCF STOP or ABORT CLIMcommand for the home CLIM is issued. When either the home or failover interface comes backup, the resources migrate to that interface and become available again automatically.

CLIM Startup BehaviorIf a CLIM crashes, it can lead to a failover, where all its interfaces are migrated to the failoverCLIM(s). If the failed CLIM subsequently boots up and brings all its interfaces to the UP statealong with the respective IP addresses, it could lead to a duplicate IP address conflict.To avoid such scenarios, the CLIM boots in this manner:• All the Data LAN interfaces are disabled (DOWN state) on startup. However, all interfaces

are initiated (drivers for such Ethernet cards loaded) and the bonding configuration is done.• No IP addresses are assigned on any of the Data LAN interfaces. No tunnel configurations

are enabled/started.

The CIP Subsystem for Internet Protocols (IP CIP) 41

• Only the Maintenance interfaces and maintenance Provider interfaces are enabled (UPstate) and have their IP addresses assigned.

• When an SCF START CLIM command is given on the host and the CLIM object goes to theSTARTED state, the host starts the home interface resources on the new CLIM if they donot already exist on other CLIMs.

Interface Resource MigrationThis section gives more details about how interface resources are treated during CLIM-to-CLIMfailover.

MAC AddressesMAC addresses are associated with hardware and are not migrated. IPv6 addresses derivedfrom the home interface’s MAC address are migrated.

SocketsHow socket failover is performed depends on the socket state.

• No migration needed. Sockets not yet bound, bound to INADDR_ANY, or bound to aloopback or multicast address and have not done a TCP or SCTP connect might be usedto listen for incoming connections or packets on addresses that exist in all the CLIMs of aProvider, so they are replicated in all the CLIMs. Since the socket exists in all the CLIMs ofthe Provider, the one in the failing CLIM can be allowed to go away without migration sincecopies exist in the other CLIMs.

• Socket migrated. When a socket binds to a local address other than INADDR_ANY or aloopback address, the copies in the CLIMs other than the one containing the local addressare removed, so the socket exists in only one CLIM. On failover, a new socket bound to thesame IP address is re-created in the failover CLIM. Any state-changing operations done onthe socket since the bind (such as listen or setsockopt) are repeated in the failover CLIM.

• Socket lost. When a socket has a TCP or SCTP connection, it is also removed on all butone CLIM if this was not already been done by a previous bind. Sockets associated withTCP and SCTP connections do not survive a failure. Each such socket is marked to returnan error to the NonStop application on its next or current socket call.For TCP sockets, the failover CLIM attempts to reset the connection. This reset is not issuedfor SCTP sockets.

A UDP connect by itself does not affect failover handling. UDP sockets always fall into the Nomigration needed or the Socket migrated categories. For UDP sockets that have joineda multicast group, the IP multicast addresses are moved to the failover CLIM. During migrationof UDP sockets, a transient loss of data may occur.

IP AddressesAll IP addresses associated with an interface are migrated during failover. Before an addresscan be added to the failover CLIM, it must be removed from the home CLIM. When the failoveraddresses are all removed from the network, the failover CLIM adds them to the failover interfaceand tells the host to update its interface tables.

IPv4 AddressesStatic IPv4 addresses are part of the configuration files copied to the failover CLIM from the homeCLIM and are migrated by adding them to the destination interface.Duplicate IP address checking is not done for IPv4 addresses. The failover and home interfacesare tried alternately until one succeeds or the CLIM object is stopped. If it has not completedafter a certain time, the failover operation is declared a failure and all sockets are marked toreturn an error on the current or next socket call.

42 Overview

IPv6 AddressesStatic IPv6 addresses are also part of the configuration files copied to the failover CLIM from thehome CLIM and are migrated by adding the failover addresses to the destination interface. Thelink-local IPv6 address is derived from the MAC address of the home interface and is migratedby adding it to the destination interface.Auto configured IPv6 addresses are derived from the MAC address of the home interface andprefixes advertised by routers in the external network. Since both interfaces of a failover pairmust be in the same broadcast domain, it is assumed they have the same prefixes. They areadded to the destination interface by using the prefixes in the auto-configured addresses of thehome resources for the destination interface. As the prefixes change or expire, the same changesare made to the failed over auto-configuration addresses.IPv6 automatically performs duplicate IP address checking. Duplicate addresses remain assignedto the interface, but marked as tentative. If an address is still marked tentative after a certaintime, all the addresses are removed and the alternate interface is tried until one succeeds or theCLIM object is stopped.

Multicast AddressesIPv4 and IPv6 multicast addresses are added by applications when they join multicast groupsby means of the setsockopt() call. The NonStop host system code saves these addresses alongwith their associated interfaces as it passes them to the CLIM. If the interface requires failover,the same multicast groups are joined on the failover interface. Duplicate-address checking is notneeded.A solicited-node multicast address exists for each unicast address and is failed over with theunicast address.

RoutesStatic routes configured for an interface are migrated during failover. They are copied to thefailover CLIM from the home CLIM as part of the interface configuration and are added when thefailover logical interface is started.Dynamic routes were created as the result of information received from routers in the externalnetwork and are not failed over. The failover CLIM has or obtains similar information when itstarts taking over the workload of the failed interface.

TCP and SCTP ConnectionsTCP and SCTP connections are not migrated during CLIM-to-CLIM failover. An ECONNRESETerror is returned to the local application instead. For TCP connections, the failover CLIM attemptsto reset the connections that were using the failed interface so the remote application can bequickly informed that the connection is gone. SCTP connections are not reset.Clients are expected to handle error recovery by attempting to re-establish connections on a newsocket.

IPv6-over-IPv4 TunnelsStatic IPv6-over-IPv4 tunnel interfaces configured with a local address are migrated during failoverof that address. Their configuration is copied to the failover CLIM from the home CLIM as partof the interface configuration and the interface is added when other failover resources are added.

IPSec ConfigurationIPSec parameters are not migrated during failover. It is expected that the IPSec configurationon the home and failover CLIMs is identical for addresses that can fail over between them. IPSecSAs that were negotiated between the CLIM containing the failed interface and the remoteendpoint cannot be failed over. They must be renegotiated with the failover CLIM. The remoteendpoint sees an unexpected request for renegotiation, which it must allow.

The CIP Subsystem for Internet Protocols (IP CIP) 43

Failover ConfigurationFailover is configured on the CLIMs using the climconfig tool. See “Climconfig (Man Pages)”(page 307) for command syntax.

CLIM Interface ConfigurationInterfaces are configured on their home CLIM using the climconfig tool. Loopback, physical, andIPv6-over-IPv4 tunnel interfaces can be configured. Intra-CLIM failover is configured by creatinga bonded interface and adding slave interfaces to it. Logical interfaces cannot be configured.Static routes and ARP entries can be associated with interfaces.The interface configurations are kept in standard CLIM files on the home CLIM and are copiedto a mirror file sub-tree on their failover CLIMs. Subsequent configuration changes trigger a copyof the configuration again.

Failover ConfigurationA non-slave physical or bonded interface can have a failover interface name associated with it.If it does not, its interface resources do not fail over if the interface fails, loses link pulse, or theCLIM fails. If it does, the failover interface name specifies the CLIM and interface to use forfailover. The failover CLIM must be different from the one on which the interface is configured;the failover interface must be a non-slave physical or bonded interface on the failover CLIM. Ifan interface and its failover interface both use failover, they must be configured to use each other.Even if an interface is not configured for failover, that interface can be used as a failover interfaceby only one other interface. The interfaces configured on a CLIM can specify failover interfaceson differing CLIMs.Both IPv4 and IPv6 addresses, if configured, are failed over. IPv4 resources include IPv4addresses, sockets, and routes. IPv6 resources are IPv6 addresses, sockets, routes, and tunnels.IPv6-over-IPv4 tunnel interfaces are not directly configured for failover; rather, they follow theinterface containing their configured local address. The interface name configured on the homeCLIM is used on the failover CLIM; therefore, tunnel interface names must not be the same onthe home and failover CLIMs.

Interface Status ControlThe CLIMCMD utilities ifstart and ifstop are provided to bring interfaces up and down, respectively.They coordinate with the CLIM software and host to start and stop the proper interface resources.Failover is suppressed when an interface is brought down using ifstop.The INTFALL option of the SCF ABORT CLIM command brings down all home interfaces on thespecified CLIM even if they have failed over to other CLIMs. Otherwise, failed-over interfacesare not affected by ABORT CLIM. The INTFALL option can be used on CLIMs that have alreadybeen aborted to bring down just the failed-over interfaces.

IPSec ConfigurationIPSec is configured on the CLIM using the climconfig command tool (see “Climconfig (ManPages)” (page 307)). The IPSec configuration is not failed over and must be identical on the homeand failover CLIMs for addresses that can fail over between them.

44 Overview

Configuration ChangesWhen a configuration change is made using the climconfig command tool that affects failover,such as changing interfaces, IP addresses, routes, or failover-interface names, the failoverconfiguration becomes invalid and failover does not occur until:• The failover configuration is propagated to all CLIMs containing failover interfaces. This is

done automatically as long as the failover CLIMs are available on the dedicated serviceLAN.

• The home CLIM object is in the STARTED state, at least briefly, so the host can retrieveinformation about the configuration change.

When an interface has failed over, changes made to its configuration do not take effect until theinterface is restored to its home interface.

Invalid Failover ConfigurationSome invalid failover configurations cannot be detected until the affected CLIM objects becomeSTARTED. These invalid configurations include:• Failover interface does not exist or is not allowed, such as a slave or tunnel interface

• Home and failover interfaces do not form a pair

• A configuration change has been made and the CLIM has not copied the new configurationfiles to the failover CLIM

• A configuration change has been made and the home CLIM object never became STARTED

• A CLIM interface is specified that is configured on the system, but is not under the sameProvider.

When an invalid failover configuration is detected, an EMS message is issued and failover doesnot occur either manually or automatically. When the condition is repaired, another EMS messageindicates that failover is now possible.

Internet Protocol Security (IPSec)For background information about IPSec, see the NonStop Networking Overview Manual.The CLIM has IPSec functionality enabled by default. The climconfig command tool allowsconfiguration of the IPSec security policies, security associations and dynamic internet keyexchange (IKE) functionality using racoon.IPSec security associations (SAs) can either be configured to be manually added to the securityassociation database (SAD), with fixed predetermined secret keys, or can be configured to beautomatically negotiated with the remote node.Since manually added SAs pose a security risk over a period of time, Hewlett Packard Enterprisediscourages this practice, and recommends configuration of automatically negotiated SAs instead.CLIM runs a daemon process called racoon, which establishes automatically keyed IPSec securityassociations and supports authentication using pre-shared keys or X.509 security certificates.Whenever an application sends network data, the CLIM kernel checks whether there are securitypolicies in the security policy database (SPD) matching with the source and destination IPaddresses. If a security policy is found, and there is no security association corresponding to thissecurity policy, the kernel triggers the racoon daemon to establish the security association.To accomplish this, racoon queries "remote" and automatic SA objects configured by climconfigto determine the parameters for the Internet Key Exchange (IKE).The climconfig remote objects tell racoon how to authenticate the remote peer and whatparameters to use for the security assocations for IKE phase 1. The climconfig automatic SAobjects tell racoon the SAs that need to be established with IKE phase 2, and added to the SADfor further communication over the IPSec connection.

The CIP Subsystem for Internet Protocols (IP CIP) 45

The application data is then transferred over the newly created IPSec connection.

IPSec Related FilesThis section details the set of configuration files related to IPSec (setkey and racoon).If the automatic SA establishment is preferred, either the mechanism of configuring the pre-sharedsecret key or providing X.509 security certificates can be used for Internet key exchange (IKE).

IPSec Configuration FilesFiles containing configuration details reside on the CLIM. The IPSec configuration commandsare used to edit the contents of these files. The IPSec configuration files are:

CAUTION: The IPSec configuration files must not be edited directly. Use the climconfigcommands to change them.

NOTE: For CLIMs with MULTIPROV ON, a separate copy of each one of the files listed hereis maintained for each provider.

In CIP, Modify by usingthe...DescriptionFile

“climconfig.psk Description”(page 358)

Pre-shared secret key forracoon IKE phase 1

psk.txt

These are generated by theuse of tools which generate

Security certificates to beused instead of pre-shared

/etc/racoon/certs/security-certificates

a certificate signing request.key for the key exchangesSee “Security Certificates –during the racoon phase-1

IKE establishment Public and Private KeyCertificates” (page 47) and“Installing X.509 Certificates”(page 95)

“climconfig.remoteDescription” (page 343) and

Racoon configuration,containing configured

racoon.conf

“climconfig.sa Description”"remote" and "automatic SA"(page 354)“climconfig.saconfigurations to directDescription” (page 376)andclimconfig.remote(1)

racoon on the parameters forIKE negotiations.

“climconfig.sp Description”(page 364) and

IPSec Security Policies (SPs)and manually configured

ipsec-tools.conf

“climconfig.sa Description"Security Associations(manual SAs). (page 354)“climconfig.sa

Description” (page 376)and“climconfig.sp Description”(page 387)

psk.txt– pre-shared secret key for racoon IKE phase 1The pre-shared secret keys are contained in the file psk.txt. This file consists of the IPaddresses or fully qualified domain names (FQDNs) of the remote machines with thecorresponding secret key.A sample psk.txt file is:# IPv4/IPv6 Adresses192.168.2.100 simple psk5.0.0.1 0xe10bd52b0529b54aac97db63462850f3# USER_FQDNjoe@doe.net This is a psk for an email address# FQDN

46 Overview

The secret key is a hexadecimal number or text. Any text or any hexadecimal number can bespecified as the pre-shared key.

Security Certificates – Public and Private Key CertificatesInstead of the pre-shared key mechanism, you can also use security certificates for the keyexchanges during the racoon phase-1 IKE (Internet key exchange) establishment. The securitycertificates are X.509 generated public and private keys. These files are placed under the directory/etc/racoon/certs/. These security files are generated by the use of tools which generate acertificate signing request and are certified by the root certificate authorities like Verisign orThawte with the use of these tools. The generation of the certificates is not done by the IPSecconfiguration tools. For procedures for using CIP IPSec, see “Using IPSec” (page 98).

Commands for Controlling Virtual Private NetworksThe set of commands that allow you to activate and deactivate VPN connections are:

saspvpn

Xstart

Xstatus

XXstop

See “Climconfig (Man Pages)” (page 307) for the command syntax and options for thesecommands.

Name ResolutionName resolution for NonStop host system applications is processed by the NonStop operatingsystem socket library either by using the HOSTS and IPNODES files or by using the DomainName System (DNS). You configure the Guardian environment to use the HOSTS file (whichinvokes IPNODES, if necessary) by specifying a DEFINE for =TCPIP^HOST^FILE.When the DEFINE for =TCPIP^HOST^FILE is not set, the NonStop host system uses DNS. Thename server accessed is defined in the $SYSTEM.ZTCPIP.RESCONF file.The Open System Services (OSS) environment inherits these Guardian-environment definesand also uses the RESCONF files.For information about using the resolver in applications, see the TCP/IP Programming Manualor theOpen System Services Library Calls Reference Manual for OSS socket-library applications.For information about the use of defines and name-resolution files in the OSS environment, seethe Open System Services Management and Operations Guide.

SNMP SupportSNMP support is provided on the NonStop system with CIP, similar to the SNMP support onNonStop systems without CIP, with a few exceptions mentioned below. Using SNMP on theNonStop host system, you can integrate your SNMP-based management application to manageand monitor the NonStop system. In addition, SNMP support is provided on the CLIMs, but onlywithin the dedicated service LAN. This support is used by Hewlett Packard Enterprise managementapplications, such as OSM, to monitor the CLIMs.

SNMP on the NonStop Host SystemThe NonStop SNMP support in CIP is similar to SNMP support in the NonStop TCP/IP andTCP/IPv6 environments. For the CIP subsystem, the SNMP agent, EMS Trap Subagent, NonStopNET/MASTER Trap subagent, Host Resources subagent and TRAP Multiplexer subagent andManager are supported. However, the TCP/IP subagent (TCPIPSA) and Ethernet subagent

The CIP Subsystem for Internet Protocols (IP CIP) 47

(ETHSA) are not supported for CIP subsystem. For configuring the supported SNMP componentson NonStop refer to SNMP Configuration and Management Manual.

CLIM SNMP SupportSNMPv1 support is provided on the CLIM, but only on the dedicated service LAN. It provides anextensible agent for responding to SNMP queries for management information. CIP supportsconfiguring the SNMP agent (snmpd) on the CLIM using the climconfig interface. The SNMPagent supports many existing networking, storage, and server MIBs that are qualified for DebianTE. These are used by the NonStop management applications, such as OSM, to monitor theCLIMs.

NOTE: SNMP trapdests must be configured on each CLIM for it to be able to send the SNMPtraps to the NonStop host.

When the eth0 is configured/modified by the user using config ip -add eth0 ip-addressor climconfig interface -modify eth0 ip-address, the climconfig tool updates the/etc/defaults/snmpd configuration file with the new listening address as the dedicatedservice LAN IP.The SNMP agent on the CLIM has public as trap community string. Public is the defaultcommunity string to be used when sending traps. The SNMP agent on the CLIM has publicfor read-only and read-write as community names. These are the read-only and read-writecommunities that are used to access the agent.

CLIM SNMP AgentsCLIM SNMP agents monitor CLIM hardware, presence of disk enclosures and devices, statusand environmental status.The OSM server issues SNMP calls to obtain the information and status. The OSM server alsocreates an SNMPTMUX process to listen to traps generated by CLIM SNMP agents.

IP CLIMSee the planning guide for your system for hardware descriptions and illustrations of the supportedCLIM models.

NOTE: The CLIM is intended only for the NonStop host system I/O functionality described inthis manual. Hewlett Packard Enterprise does not support any other use of the CLIM. Any otheruse of the CLIM, including installation of any unauthorized software, voids the warranty. Inparticular, do not attempt to install customer code or any customer-originated Linux utilities withinthe CLIM.

CIP iptables/ip6tables Support (climiptables)For CLIMs with MULTIPROV ON, each provider has its own iptables/ip6tables configuration,which can be independently manipulated and disabled or enabled.The CIP implementation of iptables/ip6tables only supports the INPUT chain of the ‘filter’ table.In addition, CIP does not directly support invoking the Linux iptables/ip6tables through CLIMCMD.Rather, CIP wraps these commands with similar iptables/ip6tables commands in climconfig.These wrappers allow the CIP software to preserve similar iptables syntax while allowing CIPsoftware to:1. Use iptables/ip6tables internally. CIP software filters out iptables/ip6tables commands that

are in conflict with CIP internal rules. The CIP rules are used during failover and to controlthe dedicated service LAN IP traffic.

2. Provide automatic configuration persistence. The CIP software persists the iptables/ip6tablesconfiguration across CLIM boots and HPE CLIM software restarts.

48 Overview

3. Provide configuration backup and restore. CIP software has a provision for allowing customersto backup and restore the configuration of a CLIM, including the iptables/ip6tablesconfiguration.

4. Ensure that the exposed iptables/ip6tables functionality is conforming to the ways the CLIMis used in the CIP environment. This involves removing the support for some functionality,mostly related to router functionality which is not supported by the CLIM.

CIP iptables/ip6tables depends on Linux iptables/ip6tables. Functionality changes in subsequentversions of Linux iptables/ip6tables may affect the functionality of CIP iptables/ip6tables.The following assumptions relate to CIP iptables/ip6tables support:

• You must not execute the Linux native iptables/ip6tables commands directly.

• You should not edit any configuration files on the CLIM.

• You should invoke the climconfig commands provided for iptables/ip6tables support on theCLIM, either through CLIMCMD or Nonstop I/O Essentials to configure and controliptables/ip6tables.

• Automatic failover of iptables/ip6tables rules is not supported. Similar to IPSec rules, youhave to pre-configure the failover CLIM’s iptables/ip6tables rules in anticipation of a failover.You can compare the configuration of the home CLIM and failover CLIM by comparing the–obeyform output of climiptables from each CLIM and ensuring any iptables/ip6tables ruleson the home CLIM exist on the failover CLIM in anticipation of a failover.

The only Linux built-in chain that is supported is the INPUT chain of the ‘filter’ tables. However,you cannot manage it directly. Instead, use the CIP built-in chain CIP_INPUT as a target forcommands that are intended for the Linux INPUT chain.The climiptables facility is disabled by default. Before using the facility it must be enabled using“climconfig climiptables –enable”.The climiptables are initialized during CLIM start up. At that time, the CIP built-in chainsCIP_INPUT and CIP_INPUT_p are created and the iptables and ip6tables configurations are setin place.The CIP_INPUT_p chain is used internally for simulating policy setting on the CIP_INPUT chainand should not be modified directly by the users.

IB CLIMFor more information about the IB CLIM, refer to the NonStop BladeSystem Planning Guide orthe NonStop NS16000 Series Planning Guide. The IB CLIM is not supported on L-series RVUs.

The CIP Subsystem for Storage I/O and the Storage SubsystemTo find out of your system supports Storage CLIMs, see the planning guide for your system.Storage CLIM provides the NonStop host system storage subsystem an industry-standard server(the CLIM).Storage CLIM uses mostly the same CLIM hardware as IP CIP with some additional storagespecific hardware such as storage-controller adapters and disk storage.Storage CLIM interfaces with the NonStop host system storage subsystem with theseconsiderations:

• Storage CLIM requires a CLIM object to be configured within the CIP subsystem before aCLIM can be accessed by the storage subsystem. The storage subsystem cannot use aCLIM object that is configured for IP. A CLIM object that is in use by the storage subsystemcannot be removed from the CIP subsystem.

• Some management and status information provided by the CIP subsystem is essential formanagement of CLIMs by OSM and I/O Essentials. The CLIM object must be in the STARTED

The CIP Subsystem for Storage I/O and the Storage Subsystem 49

state within the CIP subsystem in order for the CIP subsystem to provide some of thisinformation (mostly through the STATUS CLIM command).

• CLIM hardware event reporting is provided using a common mechanism for both IP andStorage CLIM. Syslog and evlog events generated in the CLIM are sent to EMS and I/OEssentials. The CLIM object must be in the STARTED state within the CIP subsystem forthis event reporting functionality to work.

The CIP subsystem allows you to configure and monitor the CLIM as a storage I/O device. Toconfigure storage features, such as disk paths, use the SCF interface for the storage subsystem.See the SCF Reference Manual for the Storage Subsystem. Storage CLIM commands include:

• Adding a CLIM

• Deleting a CLIM

• Monitoring events from a CLIM

• Obtaining information and various statistics about the CLIM

Storage CLIMFor storage I/O, the CLIM supports Serial Attached SCSI (SAS) and fibre channel connections.In addition to the features of the basic CLIM, the Storage CLIM can be configured with:

• Host Bus Adapters (HBAs) that contain a serial attached SCSI (SAS) interface

• HBAs that contain fibre channel portsFor Storage CLIM hardware descriptions, illustrations, and supported models, refer to the planningguide for your system.

Subsystem ID and Product NumbersThe CIP subsystem ID on the NonStop host system is ZCIP (number 259). CIP includes thesesoftware components on the NonStop host system and CLIM.

CLIM DVDProduct NumberComponent

T0690Manager process

XT0691CIP CLIM software

XT0692CIP Linux OS

T0693Socket access method

T0694Monitor processes, Library

T0695Subsystem Control Facility (SCF)product module

T0696Trace facility

T0715kIT-API software

XT0830Storage CLIM software

T0834CLIMCMD

T0853CLIM DVD installation software

XT0867NonStop Volume Level Encryption(NSVLE)

T0891CLIM DVD source (distributedseparately)

XT0932Maintenance Entity Unit (MEU)

XT0998OSM CLIM-based Components

50 Overview

For descriptions of the manager, monitor, and socket access method processes, as well as thetrace facility and SCF, see Chapter 11 (page 210).The CLIM software is pre-installed on new CLIMs.

Capacity and Resource UseComponents used with CIP have the following capacity:

This varies by system type. Refer to the planning guidefor your system for the maximum number of CLIMs.

Max number of CLIMs in a system

Refer to the planning guide for your system for the numberof embedded ports and NICs on the CLIM.

User Ethernet interfaces

128K (131,072)Max number of sockets on a NonStop host systemprocessor

64K (65,536)Max number of sockets on a CLIM

Can support a maximum of 4 SAS or FC ports.Serial attached SCSI (SAS) Host bus adapters (HBAs)and Fibre Channel (FC) HBAs (Storage CLIM)

1024 for NonStop X, 512 for previous systems. Eachprimary, backup, mirror and mirror backup path is countedin this maximum.

Max number of LUNs for each CLIM, including SAS disks,ESS and tapes:

RestrictionsThese restrictions apply to the CLIM:• The eth0 interface and the eth0:0 interface, if configured, are restricted to dedicated service

LAN use and do not accept data traffic. For data traffic, use the eth1, eth2, eth3, eth4, andeth5 interfaces.

• You must use IPv4 for the dedicated service LAN IP addresses for the CLIM.

• NOTE: Effective with J06.14/H06.25 and later RVUs, the following restriction has beenremoved.

For CLIMs on RVUs prior to J06.14/H06.25, the default subnet of the dedicated service LANis 192.168.*.*/16; therefore, the data interfaces eth1 - eth5 and bond0 - bond1 cannot haveIP addresses in the 192.168.*.*/16 range. In addition, eth1 - eth5 cannot communicate withhosts having an address in the 192.168.*.*/16 range when the address is already assignedto the dedicated service LAN.

Example of eth1 - eth5 or bond0 - bond1 Address RestrictionWhen eth1 has an address in the 192.168.*.*/16 range, the dedicated LAN must not havean address in the 192.168.*.*/16 range.

Example of Destination Restriction via GatewayWhen eth1 has an address of 10.10.10.10/16 and tries to communicate with a remote hostwhich has an address in the 192.168.*.*/16 range, the dedicated LAN must not have anaddress in the 192.168.*.*/16 range.

Capacity and Resource Use 51

To avoid the restriction, change the dedicated service LAN addresses or change theaddresses of the conflicting subnet to use a different private subnet. Any address is valid,but these private addresses are recommended:

10.255.255.255 (10/8 prefix)-10.0.0.0

172.31.255.155 (172.16/12 prefix)-172.16.0.0

192.168.255.255 (192.168/16 prefix)-192.168.0.0

See Chapter 6 (page 168) for a complete list of compatibility and migration considerations for IPCIP.

52 Overview

2 Quick StartThe installation of the CLIM is a service procedure; therefore, some basic configuration taskshave been performed.

• Two CLIMs are connected to the NonStop host system.

• Management facilities OSM and SCF are installed and configured on the NonStop hostsystem.

• CIP subsystem components are installed on the NonStop host system.

• CIP subsystem components are installed and configured on the CLIM.

• NonStop system and CLIMs are powered up.

• CLIM interface to the dedicated service LAN is configured.

A CLIM has been added for the dedicated service LAN.◦◦ Two maintenance Providers are configured for the dedicated service LAN. (These serve

the NonStop host system and all the CLIMs.)

• The CIPMAN and CIPMON processes have been configured and started.If your service provider has not already done so, change the default passwords on your CLIMsto secure your environment. The iLO and eth0 interfaces have passwords.

CAUTION: Best Practice: You should always back up the configuration files after changingany configuration information. For information on how to perform a backup, see “Managing theCLIM Configuration Preservation” (page 106).

Default Processes and Naming ConventionsThe CLIM comes with the software pre-installed. To upgrade the software, see “Performing anOnline Upgrade of the CIP Subsystem on the NonStop Host” (page 126).For CLIM and attached storage devices’ naming conventions, refer to the planning guide for yoursystem.CIP processes have the default naming conventions shown in Table 5: CIP Process NamingConventions:

Table 5 CIP Process Naming Conventions

DescriptionExampleNaming ConventionResource Type

First maintenance CIPSAM process forthe system

$ZTCP0$ZTCPnumberMaintenance CIPSAMprocess

First maintenance Provider for the system,associated with CIPSAM process $ZTCP0

ZTCP0$ZZCIP.ZTCPnumberMaintenance Provider

Second maintenance CIPSAM process forthe system

$ZTCP1$ZTCPnumberMaintenance CIPSAMprocess

Second maintenance Provider for thesystem, associated with CIPSAM process$ZTCP1

ZTCP1$ZZCIP.ZTCPnumberMaintenance Provider

First IPDATA CIPSAM process for thesystem

$ZTC0$ZTCnumberIPDATA CIPSAM process

First IPDATA Provider for the systemZTC0$ZZCIP.ZTCnumberIPDATA Provider

Default Processes and Naming Conventions 53

Table 5 CIP Process Naming Conventions (continued)

DescriptionExampleNaming ConventionResource Type

Second maintenance TELSERV processfor the system, associated with CIPSAMprocess $ZTCP1

$ZTNP1$ZTNPnumberMaintenance TELSERVprocess

First non-maintenance TELSERV processfor the system, associated with CIPSAMprocess $ZTC0

$ZTN0$ZTNnumberNon-maintenanceTELSERV process

Second maintenance LISTNER processfor the system, associated with CIPSAMprocess $ZTCP1

$ZPRP1$ZPRPnumberMaintenance LISTNERprocess

First non-maintenance Listner process forthe system, associated with CIPSAMprocess $ZTC0

$LSN0$LSNnumber or $LSnnnNon-maintenance LISTNERprocess

CAUTION: Do not change the names of the $ZTCP0 and $ZTCP1 processes, as doing socould lead to internal errors.

Change the CLIM PasswordsIf your service provider has not already done so, change the passwords on the maintenanceinterface and the iLO interfaces of your CLIMs.1. Change the password on the iLO interface of a CLIM (the default user name and password

for the iLO are: Admin and hpnonstop):1. In the OSM Service Connection, right click on the CLIM and select Actions.2. In the next screen, in the Available Actions drop-down window, select Invoke

iLO and click Perform Action.

3. In the iLO interface, select the Administration tab.

54 Quick Start

4. Select the Admin local user.5. Click View/Modify.6. Change the password.7. Click Save User Information.8. Keep track of your CLIM iLO password.

2. Change the password of the maintenance interface (eth0):• From the NonStop host system, enter the CLIMCMD command for password:

> CLIMCMD {clim-name | ip-address | dns} passwd

It will ask for a password twice. For example:$SYSTEM STARTUP 3> CLIMCMD n1002531 passwdcomForte SSH client version T9999H06_11Feb2008_comForte_SSH_0078Enter new UNIX password: hpnonstopRetype new UNIX password: hpnonstoppasswd: password updated successfullyTermination Info: 0

3. Change the iLO and maintenance interface passwords for each CLIM.The user name and password for the eth0:0 maintenance provider are the standard NonStophost system ones, for example, super.super, and so on. Follow standard procedures for settingup NonStop host system user names and passwords.

Configure and Start CIP1. Enter SCF.2. Check the CIP processes on the NonStop system.

> STATUS PROCESS $ZZKRN.ZZCIP

NONSTOP KERNEL — Status PROCESS \BLITUG.$ZZKRN.$ZZCIP

Symbolic Name Name State Sub Primary Backup OwnerPID PID ID

ZZCIP $ZZCIP STARTED 0 ,317 None 255,255ZZCIP> STATUS PROCESS $ZZKRN.CIPMONNONSTOP KERNEL — Status PROCESS \BLITUG.$ZZKRN.$CIPMON

Symbolic Name Name State Sub Primary Backup OwnerPID PID ID

CIPMON $ZCM00 STARTED 0 ,320 None 255,255CIPMON $ZCM01 STARTED 1 ,301 None 255,255CIPMON $ZCM02 STARTED 2 ,292 None 255,255CIPMON $ZCM03 STOPPED None None

NOTE: The CIPMAN, CIPMON and (for IP CIP) CIPSAM processes are pre-configured.If you need to add these processes to the persistence manager in the Kernel subsystem,see “Starting and Restarting CIP” (page 91).

3. Get the information on existing CLIMs from the NonStop host system.• Determine the names of the CLIMs:

> Info CLIM $ZZCIP.*CIP Info CLIM

Name Mode Location ConnPts Provider MultiProvN1002541 IP (100 ,2 ,5 ,4 ,1 ) 2 ZTC0 ONN1002551 IP (100 ,2 ,5 ,5, 1 ) 2 ZTC0 OFFN1002581 IP (100 ,2 ,5 ,8 ,1 ) 1 ZSAM1 OFFS1002553 STORAGE (100 ,2 ,5 ,5 ,3 ) 2 -- --

In this example, the user-defined Provider names (defined by the TPNAME attribute)for applications to use IP CIP are ZTC0 and ZSAM1.

Configure and Start CIP 55

Configure the Eth1 Through Eth5 Interfaces (IP CLIM Only)These interfaces, for customer data communication, are configured by using the TACL climconfigfacility. The TACL prompt ‘>’ is shown at the start of each command for clarity.

NOTE: You must name physical interfaces eth1, eth2, eth3, eth4 and eth5 and bonded interfacesbond0 or bond1.

These procedures assume you have two CLIMs, each configured with physical interfaces eth1and eth2 and bonded interface bond0. This example shows how to change eth1 and eth2 onone CLIM into a bonded interface and how to configure physical interface eth5 on both CLIMs.The example uses the CLIM IP address and the CLIM host name to show different ways ofqualifying the CLIM.

NOTE: In some commands, the CLIM IP address rather than the CLIM name is used in theCLIMCMD command to demonstrate this option.The CLIM IP address used in this example, 192.168.37.31, belongs to the CLIM dedicated serviceLAN interface, eth0 of the first CLIM. The second CLIM is identified by its name N1002531.

1. Create the physical interface eth5 on both CLIMs:> CLIMCMD 192.168.37.31 climconfig interface -add eth5> CLIMCMD 192.168.37.31 climconfig ip -add eth5-ipaddress 172.17.188.195 -netmask 255.255.255.0> CLIMCMD N1002531 climconfig interface -add eth5> CLIMCMD N1002531 climconfig ip -add eth5-ipaddress 172.17.100.50 -netmask 255.255.255.0

2. Change the physical interfaces eth1 and eth2 to bonded interface bond1 on one of theCLIMs:> CLIMCMD 192.168.37.31 ifstop eth1> CLIMCMD 192.168.37.31 ifstop eth2> CLIMCMD 192.168.37.31 climconfig interface -delete eth1> CLIMCMD 192.168.37.31 climconfig interface -delete eth2> CLIMCMD 192.168.37.31 climconfig interface -add bond1 -jumbo on> CLIMCMD 192.168.37.31 climconfig ip -add bond1-ipaddress 172.17.188.195 -netmask 255.255.255.0> CLIMCMD 192.168.37.31 climconfig slaveinterface-configure bond1 -add eth1> CLIMCMD 192.168.37.31 climconfig slaveinterface-configure bond1 -add eth2> CLIMCMD 192.168.37.31 climconfig route -add bond1-net -target 172.17.188.0 -netmask 255.255.255.0-gateway 172.17.188.1

NOTE: You do not need to start the interfaces. They start automatically.

3. Add a default static route to the bond1 interfaces on each CLIM:> CLIMCMD N1002532 climconfig route –add bond1 -default -gateway 172.17.188.1> CLIMCMD N1002531 climconfig route -add bond1 -default -gateway 172.17.188.1

Configure CLIM-To-CLIM Failover (IP and Telco CLIMs Only)To configure failover, the two CLIMs must belong to the same Provider. In the example in“Configure and Start CIP” (page 55), the CLIMs are in different Providers: ZTC00 and ZTC01.The CLIMs must be reconfigured to be in the same Provider for failover. To reconfigure the CLIM,delete one of the CLIMs and then re-add it to the same Providers as shown in Example 1:Configure Failover for the CLIMs.

56 Quick Start

Example 1 Configure Failover for the CLIMs

1. Stop the CLIM that is using ZTC00 by using the SCF ABORT command:> ABORT CLIM N1002532

2. Collect the current configuration by entering this SCF command and recording the display:> INFO CLIM N1002532, OBEY

3. Delete the CLIM:> DELETE CLIM N1002532CIP E00015 CLIM $ZZCIP.N1002532 is associated with an existingMaintenance Provider object.

4. Find the associated Maintenance Provider:> INFO CLIM N1002532, detail

CIP Detailed info CLIM \MYSYS.$ZZCIP.N1002532

Mode........................... IPConfigured Location............ Group 100 , Module 2 , Slot 5 , Port 3 , Fiber 2ConnPts........................ 1X1 Location.................... Group 100 , Module 2 , Slot 5 , Port 3 , Fiber 2Y1 Location.................... Group 100 , Module 3 , Slot 7 , Port 3 , Fiber 2SvNet ID 1..................... 192.168.37.82

Network CLIM Information:MultiProv....................... OFFProvider........................ ZTC00Index........................... 0

Maintenance Providers Configured:ZTCP1........................... 192.168.37.99

NOTE: The Fiber field is displayed only for systems that support it.

5. Abort the maintenance Provider:> ABORT PROVIDER ZTCP1, forced

6. Delete the maintenance Provider.a. Record the current configuration:

> INFO PROVIDER ZTCP1, obeyADD PROVIDER $ZZCIP.ZTCP1 , &

TPNAME $ZTCP1 , &HOSTNAME "osmlany" , &HOSTID 0.0.0.0 , &TCP-LISTEN-QUE-MIN 128 , &TYPE MAINTENANCE , &CLIM N1002532IPADDRESS 192.168.36.11

b. Delete the Provider:> DELETE PROVIDER ztcP1

7. Delete the CLIM:> DELETE CLIM N1002532

8. Add the CLIM using the required data Provider:> ADD CLIM N1002532, mode ip, connpt 1, location (100,2,5,3,2), provider ztc01

9. Add a maintenance Provider using recorded attributes:> ADD PROVIDER ztcp1, type maint, clim n1002532,ip 192.168.36.11, hostname "osmlany"

10. Start the CLIM:> START CLIM n1002532

Configure CLIM-To-CLIM Failover (IP and Telco CLIMs Only) 57

11. Start the maintenance Provider:> START PROVIDER ztcp1

12. Check the configuration:> INFO CLIM *CIP Info CLIM

Name Mode Location ConnPts Provider MultiProvN1002532 IP (100 ,2 ,5 ,3 ,2) 1 ZTC01 OFFN1002531 IP (100 ,2 ,5 ,3 ,1) 1 ZTC01 OFF

Configure two-way failover for the bond1 and eth4 interfaces from source N1002532 to targetN1002531:> CLIMCMD N1002532 climconfig failover –add bond1 -dest N1002531.bond1> CLIMCMD N1002532 climconfig failover –add eth4 -dest N1002531.eth4> CLIMCMD N1002531 climconfig failover –add bond1 -dest N1002532.bond1> CLIMCMD N1002531 climconfig failover –add eth4 -dest N1002532.eth4

Check Network Applications (IP CLIMs Only)Check the LISTNER and TELSERV processes.From the SCF prompt, issue the LISTOPENS MON commands:> LISTOPENS MON $ZZCIP.*

This command displays all the processes that are using the CIP subsystem, including the LISTNERand TELSERV processes.

58 Quick Start

3 CIP Configuration and ManagementThis chapter explains the tasks involved in configuring, running, and managing the CIP subsystemon the NonStop host system and on the CLIM. Tasks that are only relevant for IP CIP, StorageCLIM or Telco CIP are identified throughout the text. For information about the LUN manager,see Chapter 5 (page 164). The tasks covered in this chapter are:

CAUTION: Best Practice: You should always back up the configuration files after changingany configuration information. For information on how to perform a backup, see“Managing theConfiguration Preservation” (page 105).

Using Linux Commands and Custom CIP CommandsTable 6: Sample Safe Linux Commands provides examples of Linux commands Hewlett PackardEnterprise considers safe to use with the CIP subsystem. For instructions on obtaining manpages and help for Linux commands, see “Linux Man Page Documentation and Help” (page 20).

CAUTION: The CIP subsystem includes a front-end device running the Linux operating system.It is safe to use Linux commands for simple operations, such as copying a file, searching a string,or collecting logs.Table 6: Sample Safe Linux Commands shows examples of Linux commandsthat are safe to use. Do not use any destructive Linux command on the CLIM. Using destructiveLinux commands can cause failure of the CIP subsystem.

NOTE: This table contains a number of network-sensitive commands that need to have aprovider specified when invoked on a CLIM with MULTIPROV ON. Those commands are flaggedwith an X in the second column and are also listed under prov(1p).

Table 6 Sample Safe Linux Commands

Task Description LocationSpecifyProviderLinux Command

Displays the Internet-to-Ethernet address translation tables used by theaddress resolution protocol. See the arp man page for more information.

Xarp -a

Concatenates files and prints on the standard output. See the cat manpage for more information.

cat

Changes current directory. Use the help cd command for moreinformation.

cd

Prints or sets the system date and time. See the date man page for moreinformation.

date

Prints or controls the kernel ring buffer. See the dmesg man page for moreinformation.

dmesg

Displays ethernet card settings for the given interface. See the ethtoolman page for more information.

Xethtoolinterface-name

Displays amount of free and used memory in the system. See the freeman page for more information.

free

Print lines matching a pattern. See the grepman page for more information.grep

HPE ProLiant Integrated Management Logging (IML) utility. See the hplogman page for more information.

Xhplog

Since hplog is not a network-sensitive command and its agents executeonly in %MAINT provider, hplog must always be executed in the ‘%MAINT’provider.

Using Linux Commands and Custom CIP Commands 59

Table 6 Sample Safe Linux Commands (continued)

Task Description LocationSpecifyProviderLinux Command

Displays status of currently active interfaces. See ifconfig man page formore information.

Xifconfig

Displays status for the given interface. See the ifconfig man page formore information.

Xifconfiginterface-name

Displays status of all interfaces, even those that are down. See theifconfig man page for more information.(other forms of this command are not supported)

Xifconfig -a

Displays all the IP addresses for each of the network interfaces. See theip man page for more information.

Xip addr show

Displays contents of routing tables. See the ip man page for moreinformation.

Xip route show

Lists all the network interfaces. See the ip man page for more information.(Other forms of the ip command are not supported. Use the man 8 ipcommand to obtain the man page for the Linux ip command instead of theman ipcommand.)

Xip link show

Filter for paging through text, one screen at a time. But, it allows backwardmovement in the file as well as forward movement. See the lessman pagefor more information.

less

Lists directory contents. See the ls man page for more information.ls

An interface to the on-line reference manuals. See the man man page formore information.

man

Displays the negotiated link speed and link status of each ethernet interface.Not supported. Use the ethtool command.

Xmii-tool

Creates directory/directories, if they do not exist. See the mkdir man pagefor more information.

mkdir

Filter for paging through text one screenful at a time. See the more manpage for more information.

more

Prints network connections, routing tables, masquerade connections,interface statistics and multicast memberships. See the netstatman pagefor more information.

Xnetstat

Sends ICMP ECHO_REQUEST to network hosts. See the pingman pagefor more information.

Xping

Sends ICMP6 ECHO_REQUEST to network host. See the ping6 manpage for more information.

Xping6

Changes passwords for user accounts. See the passwdman page for moreinformation.

passwd

Prints full filename of current working directory. See the pwd man page formore information.

pwd

Removes files or directories. See the rm man page for more information.rm

Removes empty directories. See the rmdirman page for more information.rmdir

Dumps traffic on a network. See the tcpdump man page for moreinformation.

Xtcpdump

Reads from standard input and writes to standard output and files. See thetee man page for more information.

tee

60 CIP Configuration and Management

Table 6 Sample Safe Linux Commands (continued)

Task Description LocationSpecifyProviderLinux Command

Displays Linux tasks. See the top man page for more information.top -b

Changes file timestamps. See the touch man page for more information.touch

Prints the route that packets take to the network host. See the tracerouteman page for more information.

Xtraceroute

Traces path to a network host. See the traceroute6 man page for moreinformation.

Xtraceroute6

Reports virtual memory statistics. See the vmstat man page for moreinformation.

vmstat

Prints newline, word, and byte counts for each file. See the wc man pagefor more information.

wc

Shows who is logged on. See the who man page for more information.who

Table 7: Custom CIP Commands lists the custom CIP commands.

Table 7 Custom CIP Commands

Task Description LocationCIP Command

“Climconfig (Man Pages)” (page 307)climconfig

“Troubleshooting Tools and Tips” (page 112)clim

“Displaying CLIM Status Information With climstatus” (page 77) and“Monitoring CLIM Devicesand Network Interfaces” (page 86)

climstatus

“Linux Command Logging with cmd Command Wrapper” (page 114) (L15.02/J06.10/H06.21 andlater RVUs only)

cmd

“Controlling Interface States (IP CIP)” (page 94)ifstart

“Deactivating an Interface” (page 95)ifstop

Chapter 5: LUN Manager for Storage CLIM (page 164)lunmgr

“Displaying System Information” (page 85) and “Monitoring CLIM Processes” (page 86)psclim

Enter Linux and CIP commands with the tools described under “Entering CIP Commands”For an explanation of how to view man pages, see“Linux Man Page Documentation and Help”(page 20).

Entering CIP CommandsThe primary methods of entering commands for the CIP subsystem (see Table 6: Sample SafeLinux Commands (page 59) and Table 7: Custom CIP Commands (page 61)) are the commandline interface tools: Subsystem Command Facility (SCF) and CLIMCMD. Occasionally, you alsomust enter TACL commands. For example, for IP CIP, to established soft links for IPSec, youcreate and run a TACL macro (see “Setting Up Links to the Certificate Revocation List (CRL)and to the Certificate Authority (CA)” (page 96)).Certain configuration and management tasks are performed by commands that are executed onthe CLIM. A TACL command line tool, CLIMCMD, is provided that enables you to enter thosecommands on the NonStop host system; the commands are then run on the CLIM.To enter a CLIM command using CLIMCMD, enter the command name and any associatedarguments. The CLIMCMD... CLIMCONFIG portion of the command is not case sensitive butthe parameters are case sensitive. The syntax is:

Entering CIP Commands 61

CLIMCMD {clim-name | IP-address | host-name} [-provider prov-name][command [arguments]]

If clim-name is specified, the command line interface uses the SCF INFO CLIM CLIM-NAME,DETAIL display to get the dedicated service LAN IP address corresponding to that CLIM. If theIP address is specified, the command line interface uses SSH to run remote commands onthe CLIM.For a MULTIPROV ON CLIM, -provider specifies the provider in which the command should beexecuted.If you omit command[arguments] from the CLIMCMD command, a list of supported Linuxcommands for the specified CLIM is displayed.CLIMCMD requires the presence of the dedicated service LAN Providers ZTCP0 and ZTCP1and the secure shell processes ZSSP0 and ZSSP1.One of the CLIMCMD commands is climconfig. The climconfig command takes many argumentsand supplies most of the configuration interface to the CLIM. climconfig never requires the-provider option to CLIMCMD. Refer to “Using Linux Commands and Custom CIP Commands”(page 59) for a list of commands that must have the provider specified. Also see “Climconfig(Man Pages)” (page 307) for syntax descriptions of these commands. Other CLIMCMD commandsare documented in this chapter.The CLIMCMD command line interface has these assumptions:• The dedicated service LAN (eth0) is operational.

• The CLIM has been properly installed and configured, with a secure relationship establishedbetween the CLIM and the NonStop console.

Errors• climname is an invalid CLIM name

• Maintenance Interface IP Address is not known

• Neither (ZSSP0,ZTCP0) nor (ZSSP1,ZTCP1) pair of processes exist

• Connection could not be established to the clim climname

Enabling root Access for Non-Super UsersIn RVUs prior to J06.20, only NonStop users in the super group can perform CLIM configurationand management operations. With the L16.05/J06.20 RVU, NonStop Centric CLIM Management(T0834) command line tools have been enhanced to allow non-super group users to performthose actions, provided they are member of the Safeguard SECURITY-CLIM-ADMIN group.The super group members continue to have all privileges as earlier, to perform all the CLIMconfiguration and management operations.To use this feature, the administrator must perform the following steps:1. Add the Safeguard file-sharing group SECURITY-CLIM-ADMIN with the reserved group

number as 65537. The members of this group are permitted by CLIM Management tools tosuccessfully perform actions, which were otherwise restricted only for SUPER group users.

2. Add NonStop user(s) as members to the SECURITY-CLIM-ADMIN group.3. Log on as SUPER.SUPER NonStop user and execute SSOCLIM as follows:

TACL> SSOCLIM * root <password>

SSOCLIM uses the Comforte SSH implementation to communicate with the CLIMs, so eitherthe $ZSSP0 or $ZSSP1 process must be running for SSOCLIM to function.

62 CIP Configuration and Management

NOTE: NOTE: This step puts the key files that store private keys used for authentication withthe CLIM’s "root" user under Safeguard protection. An Access Control List (ACL) entry is addedfor the SECURITY-CLIM-ADMIN group on these key files.Members can be added to the SECURITY-CLIM-ADMIN group at any later point in time todelegate CLIM Management permission to additional users. Similarly, members can also beremoved from the group to revoke their permission.To enable root access for the members of the SECURITY-CLIM-ADMIN group, CIP softwareadds ACLs on certain key/configuration files that reside under the $SYSTEM.ZSERVICEsubvolume. To view the ACLs, execute the following command:TACL> SAFECOM info diskfile $SYSTEM.ZSERVICE.*, warnings off

Therefore, Hewlett Packard Enterprise recommends that the system administrators set up restof the ACLs such that they do not interfere with these ACLs which are added by the CIP software.Hewlett Packard Enterprise does not recommend the usage of the file sharing groupSECURITY-CLIM-ADMIN group for any other purpose.

Configuring CIPTo use CIP, you must configure components on the NonStop host system and the CLIM. It doesn’tmatter which set of components you configure first.This subsection covers configuring CIP:

• “On the NonStop Host System” (page 63)

• “On the CLIM” (page 71)

On the NonStop Host SystemConfigure CIP components on the NonStop host system by using SCF. First add CIP processesto the system configuration database by issuing SCF commands to the NonStop Kernel subsystem.Then define the CIP management objects by issuing SCF commands to the CIP subsystem.For more details about SCF commands you use with CIP, see Chapter 11 (page 210).Configuration tasks explained in this subsection include:

• “Configuring CIP Processes for Persistence” (page 63)

• “Other CIP Management Objects” (page 64)

• “Setting the Host Names (IP and Telco CIP Only)” (page 65)

• “Customize the NETWORKS File” (page 68)

Configuring CIP Processes for PersistenceThree types of CIP processes run on the NonStop host system:

• CIPMAN. The CIPMAN process is the main management component on the NonStop hostsystem side of the CIP subsystem. The CIPMAN object is the root of all other CIPconfiguration objects on the NonStop host system side and is used to configure, control,and query the components of CIP on its local system. One CIPMAN process pair runs oneach NonStop host system. You can run the CIPMAN process pair only in processors 0 and1 (the location of $System.)

• CIPMON. The CIPMON process is a monitor process (MON object). It is responsible forCLIM connection management and for stack operations other than data transfer, for example

Configuring CIP 63

socket migration and OSS shared sockets. You configure one CIPMON process perprocessor, for a maximum of 16 CIPMON processes per NonStop host system.

• CIPSAM (for IP CIP only). The CIPSAM process pair is a transport provider: it provides theSocket Interface TCP^PROCESS^NAME. You configure as many CIPSAM process pairsas you need to serve applications on the local system.

To ensure the availability of your CIP subsystem, CIPMAN, CIPSAM (IP CIP only), and CIPMONare configured as in the Kernel subsystem. These processes are pre-configured in manufacturing.See Chapter 2 (page 53) for a list of pre-configured processes.The SCF commands directed to the Kernel subsystem add the CIPMAN, CIPSAM and CIPMONprocesses to the NonStop system configuration database. For information about the attributesshown in these configuration examples, see theSCFReferenceManual for the Kernel Subsystem.The CIPMAN, CIPSAM, and CIPMON processes are system-managed processes (managed bythe $ZPM persistence manager). By adding CIPMAN (#ZZCIP) with a nonzero AUTORESTARTattribute and a STARTMODE attribute set to SYSTEM, makes these processes persistent, sowhenever the processes stop, $ZPM restarts them. See “Starting CIP on the NonStop HostSystem” (page 91) for examples of the SCF commands for adding these processes to the Kernelsubsystem.

Other CIP Management ObjectsIn addition to the CIPMAN, CIPSAM and CIPMON processes, these CIP management objectsare also required.

• CLIM. The CLIM object on the NonStop host system represents the NonStop host systeminterface to a CLIM; it does not really represent the CLIM device itself. The CLIM itself startsoperating as soon as it boots the CLIM software, but the NonStop host system gains accessto the CLIM by starting the CLIM object.

• PROVIDER (for IP CIP only). The PROVIDER object represents a transport service providerand directs socket requests to a specific CLIM. Each provider must have a correspondingCIPSAM process whose name is used by applications to select the transport service provider.It is best to make the provider name the same as the CIPSAM name. If you do not, then youmust specify a TPNAME attribute in the ADD PROVIDER command and that attribute mustmatch the CIPSAM name.

To define these objects:1. For IP CIP only, add a PROVIDER object by using the SCF ADD PROVIDER command:

> ADD PROVIDER $ZZCIP.ZTC02

The Provider name must match the CIPSAM process. You can either name the Provider tomatch the CIPSAM process (for example, $ZZCIP.ZTC02, where $ZTC02 is a CIPSAMprocess name) or use the TPNAME attribute (for example, $ZZCIP.SAM1 , TPNAME ZTC02,where $ZTC02 is CIPSAM process name).

NOTE: If you want more than one provider for this CLIM, see “Setting Up Multiple Providersper CLIM” (page 122) and “Changing Providers, Adding and Starting a CLIM (IP and TelcoOnly)” (page 123).

2. Add a connection to a CLIM by using the SCF ADD CLIM command:

NOTE: This step is usually done by your service provider but if you delete a CLIM forsome reason, you need to re-add it to make it operational again.

> ADD CLIM $ZZCIP.N1002532, LOCATION (100,2,5,3,2) , PROVIDER ZTC02

This step does not affect the CLIM itself; rather, this command adds a CLIM SCF object tothe CIP subsystem on the NonStop host system. Alternatively, you can use the Configure

64 CIP Configuration and Management

CLIM action in the OSM Service Collection to add the connection to the CLIM. Addsubsequent CLIMs to the subsystem by using the OSM:1. In OSM, right-click on the CLIMs object and select Actions.2. Select the Configure CLIM action and click Perform action3. Read the confirmation text and then click OK.4. Enter the desired CLIM parameters and click OK.

3. For IP CIP, ADD a CIPSAM process to go with your new provider.> ADD PROCESS $ZZKRN.#CIPSAM, AUTORESTART 10, PRIMARYCPU 1,&BACKUPCPU 2, NAME $ZTC02, PROGRAM $SYSTEM.SYSTEM.CIPSAM, &HOMETERM $ZHOME, STARTMODE SYSTEM, STOPMODE SYSMSG, &STARTUPMSG "<BCKP-CPU>"

4. The CIPSAM process starts automatically. For IP CIP, to start the provider, issue the SCFSTART PROVIDER command. For example:> START PROVIDER $ZZCIP.ZTC02

5. To start the SCF CLIM object, issue the SCF START CLIM command. For example:> START CLIM $ZZCIP.N1002532

Other Tasks (IP and Telco CIP Only)

Setting the Host Names (IP and Telco CIP Only)Name resolution for CIP is a function of the socket library on the NonStop host system. To providefor this function, customize the following files and parameters:

NOTE: These files are in $SYSTEM.ZTCPIP on the NonStop host system.For information about managing these files during a SUT installation, see the applicable softwareinstallation and upgrade guide associated with your CIP RVU.

• The HOSTS file

• The TCPIP^HOST^FILE DEFINE

• The IPNODES file

• The TCPIP^RESOLVER^ORDER PARAM

• The RESCONF file

• The NETWORKS fileHosts within an IP network communicate through their IP addresses. However, IP addresses arenot easy to remember. As a result, it is common practice to assign host names to IP addresses;commands can then refer to a host by name.The component that provides the translation between a host name and an IP address is calleda Domain Name Resolver (DNR). To resolve names, the DNR uses either a Domain Name Server(DNS) or a HOSTS file; configure the DNR to use one or the other.Using the Domain Name Server is the preferred way of resolving names on the network. If aname server is not available, use a HOSTS or IPNODES file.

Configure the HOSTS File (IP CIP Only)The HOSTS file is a simple edit type file that contains an entry for each remote host known toyour system. Specify each remote host's IP address, host name, and alias.Each entry in the HOSTS file has this format:IP_address host_name [alias...]

Configuring CIP 65

The IP_address is a 32-bit numeric value expressed in dotted decimal form. The IP_addressmust begin in the first column of an entry in your edit file. The host_name and aliases arealphanumeric and separated by at least one space. For example:# HOSTS file127.0.0.1 me loop geoff mark cyclone

128.1.1.1 CB21 cb21 6

128.1.2.1 CB22 cb22

Notice the first entry beginning with 127.0.0.1 has several aliases. This indicates user can useany of these aliases to communicate with the destination host that has the IP address 127.0.0.1.The IP address 127.0.0.1 is a TCP/IP convention that refers to “this” host or loopback.Specifying an alias for a host is optional, and a host can have more than one alias; however, thealiases must be separated by spaces and be on the same line. The other entries (beginning with128.1.1.1) each have two host names: one in uppercase and one in lowercase. Neither the hostname nor the alias is case sensitive.You can add comments to the HOSTS file by preceding the comment with a pound sign (#). Youcan add comments as separate lines of the file or after the IP address and host entry. Includecomments like the line name or hardware address that can be used for reference.The site update tape (SUT) comes with a sample HOSTS file called SMPLHOST, which is installedinto $SYSTEM.ZTCPIP. Modify this file for your environment.

Configure the TCPIP^HOST^FILE DEFINEThe default behavior of the Domain Name Resolver (DNR) is to use the Domain Name System(DNS) (and the RESCONF file), rather than the HOSTS file. If you want the DNR to use theHOSTS file, you must set the TCPIP^HOST^FILE environment variable, using a TACL ADDDEFINE command. For example:ADD DEFINE =TCPIP^HOST^FILE, FILE $SYSTEM.ZTCPIP.HOSTS

You also must set the TCPIP^HOST^FILE parameter at each terminal that uses the IP network.Then, when you invoke a TCP/IP application, the DNR uses the appropriate HOSTS file to resolvereferences to host names. For convenience, include an ADD DEFINE command as an entry inthe TACLCSTM file, so that the command is executed automatically every time you log onto theNonStop system.

Configure the IPNODES FileThe IPNODES file contains information regarding the known IPv6 (and IPv4) nodes on thenetwork. If you are using INET6 communications and want to use a name resolution file, youmust create $SYSTEM.ZTCPIP.IPNODES to support local definitions of IPv4 and IPv6 addresses.(For DUAL mode, you can either use HOSTS for IPv4 addresses and IPNODES for IPv6addresses, or you can put your IPv4 addresses in IPNODES.)The format of the IPNODES file is the same as for the HOSTS file. For example:#

# ipnodes - local database associating names of nodes with IP

# addresses. IP addresses can be either an IPv4 or an IPv6 address.

# The ipnodes file can be used with, or instead of, the HOSTS file.

#

2::56:a00:20ff:fe7b:b667 foo # John Smith

192.168.182.52 grand-poohbah bobafet-xx

66 CIP Configuration and Management

0:0:0:ffff:0d:1:44:3 bar-mapped

0:0:0:0:d:1:44:3 bar-compatible

1080:0:0:0:8:800:200c:417a some-addr

1080:0:0:0:8:0:0:0 compress-this

Items are separated by any number of blanks or tab characters, or both. The pound sign (#)indicates the beginning of a comment; characters up to the end of the line are not interpreted byroutines that search the file. Network addresses, both IPv4 and IPv6, are converted to binaryformat by using the inet_pton() routine from the NonStop OS sockets library. Node names cancontain any printable character other than a field delimiter, new line, or comment character.The getaddrinfo() routines as defined in RFC 2553 (Basic Socket Interface Extensions for IPv6),support the use of the $SYSTEM.ZTCPIP.IPNODES file. and getnameinfo()There is no sample IPNODES file on the SUT; you must create this file yourself if you want touse it.

Add the TCPIP^NODE^FILE DEFINEIf you want to use an IPNODES file that is located someplace other than the default location($SYSTEM.ZTCPIP.IPNODES), set the TCPIP^NODE^FILE environment variable, by using theTACL ADD DEFINE command:ADD DEFINE =TCPIP^NODE^FILE, FILE $SYSTEM.ZTCPIP.IPNODES

Also, for the resolver to use IPNODES in stead of DNS, you must set the TCPIP^NODE^FILEDEFINE.

Add the TCPIP^RESOLVER^ORDER PARAMYou can override system defines for the HOSTS file by using the TCPIP^RESOLVER^ORDERPARAM. The syntax is:PARAM TCPIP^RESOLVER^ORDER value

value indicates the file that the socket library should query. Valid values are:DNSONLY

Query only the DNS.HOSTFILEONLY

Search only the HOSTS file.DNS-HOSTFILE

Query the DNS and if the host name is not found, search the HOSTS file.HOSTFILE-DNS

Search the HOSTS file and if the host name is not found, query the DNS.This PARAM takes precedence over the HOSTS DEFINE. The PARAM name and value are notcase-sensitive.If there are no DEFINEs or PARAMs in effect for the process, the socket library consults DNSfirst. If it doesn’t find the address there, it consults the IPNODES file.

Configure the RESCONF FileThe DNR resolves domain names to IP addresses using either DNS or a HOSTS file to providethe translation. If you did not set the TCP^HOST^FILE or TCP^NODE^FILE parameter, the DNRassumes it must use DNS. To determine which DNS to use, the DNR interrogates the RESCONFfile. Therefore, you must configure the RESCONF file when using DNS.The RESCONF file specifies the name of the domain in which the host is running and the IPaddresses of DNS servers to consult. The following example lists three DNS IP addresses(nameserver 127.1, nameserver 50.0.0.23, and nameserver 50.0.0.36):

Configuring CIP 67

domain HP.COMnameserver 127.1nameserver 50.0.0.23nameserver 50.0.0.36

The first server address is the primary server. If that server is unavailable, the resolver contactsthe second server. If the second is unavailable, the resolver tries to contact the third server.Notice that the first server address is 127.1; this is the address you would use if the currentNonStop host had a server available.The site update tape (SUT) comes with a sample RESCONF file that is installed into$SYSTEM.ZTCPIP. The name of this file is SMPLRESC. Modify this file for your environment.

Add the TCPIP^RESOLVER^NAME DEFINETo override the default RESCONF file, use the environment variable TCPIP^RESOLVER^NAME.This variable provides flexibility in selecting the RESCONF file accessed for name resolution.The default RESCONF file is located on $SYSTEM.ZTCPIP. To select a different RESCONFfile, use a TACL ADD DEFINE command like:ADD DEFINE =tcpip^resolver^name, FILE $data.user.resconf

Customize the NETWORKS FileThe NETWORKS file lists the names, numbers, and aliases of networks known to the currenthost. This file converts an Internet network address to a symbolic name.Applications use this file when they call a getnetbyaddr() or a getnetbyname() function. TheNETWORKS file included with the CIP software is a prototype; you should customize this file.Each entry of the NETWORKS file has this format:network_name network_number [alias...]

Where network_name is an alphanumeric name, network_number is the assigned networknumber, and alias is an alphanumeric name.The alias is optional for each network, and each network can have more than one alias. Thealiases for each network must be on the same entry line and separated by spaces.

Sample NETWORKS File: SMPLNETWThe site update tape (SUT) comes with a sample NETWORKS filethat is installed into$SYSTEM.ZTCPIP. The name of this file is SMPLNETW and the contents are shown in thedisplay:## Network configuration file#loopback 127xxx-ether 192.9.200 xxxether ethernet localnettdm-oldether 125 tdmoldether## Internet networks# Internet networks#arpanet 10 arpaucb-ether 46 ucbether

Modify this file for your environment.

68 CIP Configuration and Management

Customizing the Protocols, Services, and Programs (IP and Telco CIP Only)Applications that use CIP rely on several other configuration files on the host:

• The PROTOCOL file, to identify all available protocols (TCP, UDP, and so on)

• The SERVICES file, to identify all available port-level services (FTP, SMTP, and so on)

• The PORTCONF file, to list the ports monitored by the LISTNER and to identify, for eachport, the program the LISTNER invokes to service requests

PROTOCOL FileThe PROTOCOLfile contains the names of the protocols currently supported by the CIP software,as well as some not currently supported. Applications use the PROTOCOL file to get protocolnames and Internet protocol numbers. When an application calls the functions getprotobynameor getprotobynumber, the PROTOCOL file provides this information. You do not need to alterthis file.Each entry has this format:protocol_name protocol_number PROTOCOL_NAME

Where protocol_name is the protocol name in lowercase, protocol_number is the well-knownInternet protocol number and PROTOCOL_NAME is the protocol name in uppercase. (Becausethe functions getprotobyname and getprotobynumber are case sensitive, both uppercaseand lowercase representations of the protocol names are included in the PROTOCOL file.)

Sample PROTOCOL File: SMPLPROTThe site update tape (SUT) comes with a sample PROTOCOL file that is installed into$SYSTEM.ZTCPIP. The name of this file is SMPLPROT and the contents are shown in thedisplay:## @(#)protocols 1.1 Tandem## Internet (IP) protocols# This file is never consulted when the yellow pages are running#ip 0 IP # internet protocol, pseudo protocol numbericmp 1 ICMP # internet control message protocolggp 3 GGP # gateway-gateway protocoltcp 6 TCP # transmission control protocolpup 12 PUP # PARC universal packet protocoludp 17 UDP # user datagram protocolipv6 41 IP # internet protocol for v6icmpv6 58 ICMP # internet control message protocol for v6

Precede comment lines with a pound sign (#).

NOTE: You must add an entry for SCTP to use that protocol. To use SCTP, add this line:sctp 132 SCTP # stream control transmission protocol

SERVICES FileThe SERVICES file contains the Internet port level services that are available with the CIPsoftware. Applications use the SERVICES file to get the service port numbers and service names.When the application calls the getservbyname(), getservbynumber(), or getaddrinfo() function,CIP uses the SERVICES file to provide that information.Each entry specifies a service name, the port number through which that service is accessed,and the corresponding protocol that supports that service. You can use an alias to identify theservice.

Configuring CIP 69

Sample SERVICES File: SMPLSERVThe site update tape (SUT) comes with a sample SERVICES file that is installed into$SYSTEM.ZTCPIP. The name of this file is SMPLSERV and the contents are shown in thedisplay:## @(#)services 1.16 90/01/03 SMI## Network services, Internet style# This file is never consulted when the NIS are running#tcpmux 1/tcp # rfc-1078echo 7/tcpecho 7/udpdiscard 9/tcp sink nulldiscard 9/udp sink nullsystat 11/tcp usersdaytime 13/tcpdaytime 13/udpnetstat 15/tcpchargen 19/tcp ttytst sourcechargen 19/udp ttytst sourceftp-data 20/tcpftp 21/tcptelnet 23/tcpsmtp 25/tcp mailtime 37/tcp timservertime 37/udp timservername 42/udp nameserverwhois 43/tcp nicname # usually to sri-nicdomain 53/udpdomain 53/tcphostnames 101/tcp hostname # usually to sri-nicsunrpc 111/udpsunrpc 111/tcppiccolo 2787/udp piccolo # Cornerstone Softwarepiccolo 2787/tcp piccolo # Cornerstone Software## Host specific functions#tftp 69/udprje 77/tcpfinger 79/tcplink 87/tcp ttylinksupdup 95/tcpiso-tsap 102/tcpx400 103/tcp # ISO Mailx400-snd 104/tcpcsnet-ns 105/tcppop2 109/tcp # Post Officeuucp-path 117/tcpnntp 119/tcp usenet # Network News Transferntp 123/tcp # Network Time ProtocolNeWS 144/tcp news # Window System## UNIX specific services## these are NOT officially assigned#exec 512/tcplogin 513/tcpshell 514/tcp cmd # no passwords usedprinter 515/tcp spooler # line printer spoolercourier 530/tcp rpc # experimental

70 CIP Configuration and Management

uucp 540/tcp uucpd # uucp daemonbiff 512/udp comsatwho 513/udp whodsyslog 514/udptalk 517/udproute 520/udp router routednew-rwho 550/udp new-who # experimentalrmonitor 560/udp rmonitord # experimentalmonitor 561/udp # experimentalpcserver 600/tcp # ECD Integrated PC boardsrvringreslock 1524/tcp

You may need to edit the SERVICES file for the DSM/SCM Planner Interface to work. For moreinformation, see the applicable software installation and upgrade guide associated with your CIPRVU.

PORTCONF FileThe PORTCONF file specifies the ports that the LISTNER process listens to and the correspondingserver program it invokes when the request comes in.Here is an example of the PORTCONF file:#

ftp $system.ztcpip.ftpserv

finger $system.ztcpip.fingserv

7 $system.ztcpip.echoserv

Sample PORTCONF File: SMPLPORTThe site update tape, SUT, comes with a sample PORTCONF file that is installed into$SYSTEM.ZTCPIP. The name of this file is SMPLPORT and the contents are:## This file tells the listner program which ports to# listen to, and what programs to run# Telnet is directly, and does not use the listner's# services.# To run the listner use:# $system.ztcpip.listner / name.../ [config-file-name]# where config-file-name is this file.#ftp $system.ztcpip.ftpservfinger $system.ztcpip.fingserv7 $system.ztcpip.echoserv

You may need to edit the PORTCONF file for the DSM/SCM Planner Interface to work. For moreinformation, see the applicable software installation and upgrade guide associated with your CIPRVU.For more information about the PORTCONF file, see the TCP/IP Applications and Utilities UserGuide.

On the CLIMConfiguring the CLIM involves a variety of tasks:

• “Setting the Host Name” (page 72)

• “Defining Networking Interfaces (IP CLIM Only)” (page 72)

• “Mapping IP Addresses to Ethernet Addresses (ARP) (IP CLIM Only)” (page 72)

Configuring CIP 71

Setting the Host NameThe CLIM host name identifies the CLIM in various banners and prompts.s1002532

To change the host name, use the CLIMCMD {clim-name | ip-address } climconfig command.See climconfig.hostname(1).

NOTE: The CLIM hostname must match the SCF CLIM object name. If the CLIM hostnameand SCF CLIM object name do not match, the CLIM does not go to the STARTED state.

Defining Networking Interfaces (IP CLIM Only)The CLIMCMD climconfig interface command sets the protocols, IP addresses, and otherparameters for the interface. Using this command, you can add an interface, delete an interface,view and modify attributes of existing interfaces. See climconfig.interface(1).You may configure the interfaces eth1, eth2, eth3, eth4, and eth5 for data communications. Eth0and eth0:0 are pre-configured.)

Mapping IP Addresses to Ethernet Addresses (ARP) (IP CLIM Only)ARP maps IP addresses to hardware MAC addresses. The CLIM usually builds the ARP cacheautomatically as it discovers the MAC addresses of other entities, but you can also add, delete,and view ARP cache entries by using the “climconfig.arp Description” (page 310).

Policy Based RoutingNOTE: Policy based routing applies to all providers for CLIMs with the MULTIPROV ON option.

For J06.04 to J06.09 and H06.16 to H06.20 RVUs, you cannot associate an application with aspecific interface on a CLIM by binding to the IP address configured on that interface. For theseRVUs, if you need to restrict access of an application to an interface, you can use one interfaceor set of interfaces on a CLIM by just adding a subset of the possible physical interfaces (forexample, eth1 and eth2).As of L15.02 and later L-series RVUs, J06.10 and later J-series RVUs and H06.21 and laterH-series RVUs, you can use policy based routing to ensure that the interface with the IP addressbound to a socket will be used by that socket for outgoing network traffic, or that an interfacewith an IP address in the source address of the network packet is used for routing the packet.This feature is enabled by default, but you can disable it.Use the CLIMCMD {clim-name | ip-address} clim command to enable or disable policyrouting. The default is on. See “CLIMCMD clim Command” (page 112) for syntax.Figure 7: Bound Socket Problem Configuration Without Policy Based Routing (page 73) andFigure 9: Server Socket Problem Configuration Without Policy Based Routing (page 75) showconfigurations that may encounter routing problems. Figure 8: Bound Socket ProblemConfiguration With Policy Based Routing (page 74) and Figure 10: Server Socket ProblemConfiguration With Policy Based Routing (page 76) show the same configurations with policyrouting enabled, which alleviates the routing problems.Figure 7: Bound Socket Problem Configuration Without Policy Based Routing shows a boundsocket configuration with these characteristics:• There are two interfaces on the same IP subnet (A.0).

• A.0/24 is the subnet route added automatically when the IP address A.11 was configuredon the CLIM.

• eth3 is activated first (non-deterministic).

• The subnet route on eth3 is used for all outgoing connections to the network.

72 CIP Configuration and Management

• The socket is bound to the A.11, IP address on eth1.

• The source address used in the packet is the one that is bound by the socket.Problem: A packet is sent out on the eth3 interface with a source address from the eth1 interface.

Figure 7 Bound Socket Problem Configuration Without Policy Based Routing

With policy based routing enabled and no configuration change, the packet is sent out on theeth1 interface with a source address from the correct interface, eth1, as shown in Figure 8: BoundSocket Problem Configuration With Policy Based Routing:

Policy Based Routing 73

Figure 8 Bound Socket Problem Configuration With Policy Based Routing

Figure 9 (page 75) shows a server socket configuration with these characteristics:• There are two interfaces on the same IP subnet (A.0)

• A.0/24 is the subnet route added automatically when the IP address A.11 was configuredon the CLIM.

• eth3 is activated first (non-deterministic)

• The server is listening on the eth1 IP address

• Incoming requests come through the eth1 interface

• Outgoing requests go through the eth3 interfaceProblem: The response is sent on a different interface than the one the request came in on.

74 CIP Configuration and Management

Figure 9 Server Socket Problem Configuration Without Policy Based Routing

With policy based routing enabled and no configuration change, the response is sent on thesame interface that the request came in on, as shown in Figure 10 (page 76):

Policy Based Routing 75

Figure 10 Server Socket Problem Configuration With Policy Based Routing

This CLIMCMD {clim-name | ip-address} climstatus -or report shows the additionaltables created by policy routing:$SYSTEM.SABUN 22> climcmd n1002571 climstatus -orSSH client version T9999H06_21Jun2010_comForte_SSH_088-------------------------------------------------------------------------------------IPv4 routing tableTABLE main:10.11.12.0/24 dev eth5 proto kernel scope link src 10.11.12.109172.17.213.0/24 dev eth5 proto kernel scope link src 172.17.213.112192.168.0.0/16 dev eth0 proto kernel scope link src 192.168.37.71default via 172.17.213.1 dev eth5

TABLE ETH0:192.168.0.0/16 dev eth0

TABLE ETH5:10.11.12.0/24 dev eth5172.17.213.0/24 dev eth5default via 172.17.213.1 dev eth5

The original entries are listed under “TABLE MAIN”. Additional tables are listed as “TABLE ETH5”,and so on.

Troubleshooting RoutingIf you upgrade to RVU L15.02/J06.10/H06.21 and find that routing behavior has changed, disablepolicy based routing. It is enabled by default. See “Policy Based Routing” (page 72) for detailsand “CLIMCMD clim Command” (page 112) for syntax details.

76 CIP Configuration and Management

Displaying the CIP ConfigurationThis section describes how to display information on the NonStop host system and on the CLIM.

On the NonStop Host SystemTo display the configurations of CIP objects on the NonStop host system, use the SCF INFOcommand and specify the name of the object. For example:

• The INFO CLIM command indicates whether the specified CLIM is present.

• The INFO PROCESS command displays the process ID of the CIPMAN and CIPSAM (IPCIP only) processes.

• The INFO PROVIDER command (for IP CIP only) displays, for the specified provider, thename of the transport provider (CIPSAM) process, the name of the associated CLIM (if thedetail option is specified in the INFO PROVIDER command), and the configured host name(for example, the Expand node name).

• The STATUS CLIM command displays a variety of information about the CLIM.

• The LISTDEV CIP command displays the CIP monitor and manager processes. See“LISTDEV CIP and LISTDEV TCPIP” (page 218)

• The LISTDEV TCPIP (for IP CIP only) command displays the TCP/IP processes, includingthe CIPSAM processes. See “LISTDEV CIP and LISTDEV TCPIP” (page 218).

This is not a complete list of display commands. For more information about all commands, seeChapter 11 (page 210), “Climconfig (Man Pages)” (page 307) and the various tasks described inthis chapter.

See...For Information About the...

“INFO CLIM” (page 229)INFO CLIM command

“INFO PROCESS” (page 234) and “INFO Commands, CIPSAM” (page 285)INFO PROCESS command

“INFO PROVIDER” (page 235)INFO PROVIDER command

“STATUS CLIM” (page 253)STATUS CLIM command

“LISTDEV CIP and LISTDEV TCPIP” (page 218)LISTDEV TCPIP and LISTDEV CIP

On the CLIMUse the CLIMCMD command line interface from the TACL prompt on the NonStop host systemto display configuration information.

• To display the current setting of a TCP/IP protocol parameter, use the climconfig sysctl infocommand, specifying the all parameter. See “Climconfig (Man Pages)” (page 307) for details.

• To display the routing table, you can use the Linux netstat -r command.

NOTE: For better performance, always use the –n option.

• To display the ARP cache, use the CLIMCMD arp command with no arguments. See thearp(8) man page for details.

NOTE: netstat and arp are network-sensitive commands, requiring that the -provider optionbe specified to CLIMCMD if the MULTIPROV option is ON.

Displaying CLIM Status Information With climstatusThe climstatus script displays status information for CLIM objects and devices, including theServerNet, the Ethernet LAN, the kernel IP routing table, and hard disk drives.

Displaying the CIP Configuration 77

Invoke climstatus either from the command line by using the CLIMCMD command from TACLor (partially) from I/O Essentials. (I/O Essentials allows you to show Routing Table Information,which is equivalent to climstatus -o r). Some of this information can also be obtained fromthe SCF STATUS CLIM command. The syntax is:CLIMCMD {clim-name | IP-address} climstatus [-o option]

option is any of these:

Displays information about...Option

For all CLIM types, this displays the CLIM mode, CLIM state, CLIM software start time, CLIM hostname,and CLIM software versions. For H- and J-series CLIMs, this also displays CLIM location and CLIM

s

fabric status. CLIM fabric status is not shown by this option on NonStop X CLIMs; that informationis available on NonStop X using the SCF STATUS CLIM command, as shown under Example 78:STATUS CLIM Summary, NonStop X.

Status of the local area network. The display includes, for each interface, the interface name, type,status, link status, and IP addresses (IPv4 and IPv6). LAN information is split into sections, one forthe data interfaces (loopback, eth2, eth3, eth4, eth5), and one for the maintenance interfaces (eth0).

l

Kernel IPv4 and IPv6 routing tables. The display for IPv4 includes the interface name, destination IPaddress, the gateway address and network mask. The display for IPv6 includes the interface name,destination IP address, and next hop.

r

File system disk space utilization. The display includes, for each configured disk, its name, type, size,space used, space available, percentage in use, and mount point.

h

IPSec configuration.i

Failover configuration.f

SNMP configuration.m

climprep config information.c

climiptables config information.t

Invoking the tool without options displays information about all components. Options allow youto specify the components for which to display status.

ServerNet StatusThis command provides ServerNet status information:

Example 2 Climstatus Command ServerNet Status Information, IP and Telco CLIM

\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD n1002532 climstatus -o s

CLIM Configuration & Status:Mode..................... IPState.................... STARTEDConnPts.................. 2X1 Location.............. Group 100, Module 2, Slot 5, Port 3, Fiber 2Y1 Location.............. Group 100, Module 3, Slot 7, Port 3, Fiber 1X2 Location.............. Group 100, Module 2, Slot 5, Port 4, Fiber 2Y2 Location.............. Group 100, Module 3, Slot 7, Port 4, Fiber 2X1 Connection Status..... UPY1 Connection Status..... UPX2 Connection Status..... UPY2 Connection Status..... UPLast Restart Time........ Wed Oct 17 03:21:26 2007CIP/Linux Hostname....... CLIM1Network SW Version....... T0691H01_01MAY2008_AAA_CLIMStorage SW Version....... T0691H01_01MAY2008_AAA_CLIMCIP SW Version........... T0853h01_01AUG2008_23JUL2008_AAA

Telco SW Version........... T08718INS_17FEB2011_18JAN2011_XYZ29West SW Version...........T01234IBX_17FEB2011_18JAN2011_XYZ

78 CIP Configuration and Management

Number of Socket Servers. 1CIP/Linux Version:Linux version 2.6.18-5-telco-amd64 (Debian 2.6.18.dfsg.1-14~hpde1.8)(brian.haley@hp.com) (gcc version 4.1.2 20061115 (prerelease)(Debian 4.1.1-21)) #1 SMP PREEMPT Fri Sep 28 20:50:40 UTC 2007

Example 3 Climstatus Command ServerNet Status Information, Storage CLIM

\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD s1002531 climstatus -o s

CLIM Configuration & Status:Mode..................... STORAGEState.................... STARTEDConnPts.................. 2X1 Location.............. Group 100, Module 2, Slot 5, Port 3, Fiber 1Y1 Location.............. Group 100, Module 3, Slot 7, Port 3, Fiber 1X2 Location.............. Group 100, Module 2, Slot 5, Port 3, Fiber 2Y2 Location.............. Group 100, Module 3, Slot 7, Port 3, Fiber 2X1 Connection Status..... UPY1 Connection Status..... UPX2 Connection Status..... UPY2 Connection Status..... UPLast Restart Time........ Fri Apr 25 15:04:37 2008CIP/Linux Hostname....... S1002531Network SW Version....... T0691H01_01MAY2008_AAA_CLIMStorage SW Version....... T0830H01_01MAY2007_22APR2008_CIP SW Version........... T0853H01_01MAY2008_23APR2008_Number of Socket Servers. 1CIP/Linux Version:Linux version 2.6.18-6-clim-amd64 (Debian 2.6.18.dfsg.1-18hpdeetch1hpde1.3)( brian.haley@hp.com) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21))#1 SMP PREEMPTMon Mar 31 19:17:50 UTC 2008

NonStop X StatusThis command provides NonStop X status information:

Example 4 Climstatus Command NonStop X Status Information

\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD NCLIM000 climstatus -o s

CLIM Configuration & Status:Mode..................... IPState.................... STARTEDLast Restart Time........ Fri Dec 5 07:56:20 2014CLIM Hostname............ NCLIM005Network SW Version....... T0691L02_01FEB2015_BAB_CLIM_Z11Storage SW Version....... T0830L02_18FEB2015_20NOV2014_BAB

CIP SW Version........... T0853L02_01FEB2015_04DEC2014_BAB

Number of Socket Servers. 1CIP/Linux Version:Linux 3.2.30-clim-58.3-amd64 #1 SMP Wed Oct 8 21:54:40 UTC 2014

Ethernet LAN StatusThis display shows Ethernet LAN status information for an IP CLIM. Notice the separate displaysfor the data interfaces and the dedicated service LAN (also called maintenance LAN):

Example 5 Climstatus Command Ethernet LAN Status (IP and Telco CLIM)

For CLIM(s) with the MultiProv feature enabled, the following is the output for LAN Interfacesstatus.

Displaying the CIP Configuration 79

\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD n1002532 climstatus -o l

MultiProv: ON

Maintenance LAN Status & IP Addresses:Name Status LkP Master / IP Family & Addresslo UP -- IPv4: 127.0.0.1eth0 UP UP IPv4: 192.168.37.32

Maintenance Provider Interface Status & IP Addresses:Name Status LkP Master / IP Family & Addresslo UP -- IPv4: 127.0.0.1eth0:0 UP UP IPv4: 192.168.36.11

Data Provider ZTC0 Interface Status & IP Addresses:Name Status LkP Master / IP Family & Addresslo UP -- IPv4: 127.0.0.1

IPv6: ::1eth1 UP UP

IPv4: 172.17.190.101IPv6: 3ffe:1200:0190:0002:0215:60ff:fe04:24deIPv6: 3ffe:1200:0190:0001:0215:60ff:fe04:24deIPv6: fe80:0000:0000:0000:0215:60ff:fe04:24de

eth2 UP UP IPv4: 172.17.190.102IPv6: 3ffe:1200:0190:0002:0215:60ff:fe04:24dfIPv6: 3ffe:1200:0190:0001:0215:60ff:fe04:24dfIPv6: fe80:0000:0000:0000:0215:60ff:fe04:24df

Data Provider ZTC1 Interface Status & IP Addresses:Name Status LkP Master / IP Family & Addresslo UP -- IPv4: 127.0.0.1

IPv6: ::1eth3 UP UP IPv4: 172.17.190.103

IPv6: 3ffe:1200:0190:0002:0215:60ff:fe04:257eIPv6: 3ffe:1200:0190:0001:0215:60ff:fe04:257eIPv6: fe80:0000:0000:0000:0215:60ff:fe04:257e

Unconfigured Interfaces:Name Status LkPeth4 DOWN --eth5 DOWN --bond0 DOWN --

Example 6 Climstatus Command Ethernet LAN Status (IP and Telco CLIM), NonStop X

For CLIM(s) with the MultiProv feature enabled, the following is the output for LAN Interfacesstatus on NonStop X systems.\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD NCLIM000 climstatus -o l

MultiProv: ON

Maintenance LAN Status & IP Addresses:Name Status LkP Line-Speed Master / IP Family & Addresslo UP -- - - IPv4: 127.0.0.1

IPv6: ::1eth0 UP UP 100Mb/s IPv4: 192.168.37.32

IPv6: fe80::2e76:8aff:fe5a:c4d3

Maintenance Provider Interface Status & IP Addresses:Name Status LkP Line-Speed Master / IP Family & Addresslo UP -- - - IPv4: 127.0.0.1

IPv6: ::1eth0:0 UP UP 100Mb/s IPv4: 192.168.36.10

IPv6: fe80::2c76:8aff:fe5a:c4d3

Data Provider ZTC5 Interface Status & IP Addresses:Name Status LkP Line-Speed Master / IP Family & Addresseth5 UP DOWN Unknown IPv4: 10.5.5.5

IPv6: fe80::9e8e:99ff:fe4b:fe5ceth1 UP UP 10000Mb/s IPv4: 10.1.5.1

IPv6: fe80::f292:1cff:fe0c:e3c8eth2 UP UP 10000Mb/s IPv4:10.2.5.2

IPv6:fe80::f292:1cff:fe0c:e3cceth3 UP UP 10000Mb/s IPv4:10.3.5.3

IPv6:fe80::da9d:67ff:fe20:6168eth4 UP UP 10000Mb/s IPv4:10.4.5.4

80 CIP Configuration and Management

IPv6:fe80::da9d:67ff:fe20:616clo UP -- - IPv4:127.0.0.1

IPv4:127.0.2.2IPv6:::1

Unconfigured Interfaces:Name Status LkPbond0 DOWN ----bond1 DOWN ----

IP Tables StatusFor examples of iptables/ip6tables information, see Example 16: Inbound FTP Traffic (page 102)and Example 17: Allow Inbound SNMP TRAPS (page 103) under Configuring CIP iptables/ip6tables(IP CIP) (page 100).

Kernel Routing Table InformationExample 7: Climstatus Command IP Routing Table Information (IP and Telco CLIM)(J06.10/H06.21 and later RVUs) shows the kernel routing table on an IP CLIM forL15.02/J06.10/H06.21 and later RVUs. IPv4 and IPv6 routing information is displayed separately.Example 8: Climstatus Command IP Routing Table Information (IP and Telco CLIM) (RVUs priorto J06.10/H06.21 shows the kernel routing table on an IP CLIM for RVUs prior to J06.10/H06.21.

Example 7 Climstatus Command IP Routing Table Information (IP and Telco CLIM)(J06.10/H06.21 and later RVUs)

For CLIM(s) with the MultiProv feature enabled, the following is the output for Kernel IP Routingtable.$SYSTEM.SABUN 22> CLIMCMD n1002571 climstatus -o rMaintenance LAN IPv4 Routing tableTABLE main:192.168.37.0/16 dev eth0 proto kernel scope linksrc 192.168.37.71default via 192.168.172.1 dev eth0

Maintenance LAN IPv6 Routing tableTABLE main:fe80::/64 dev eth0 proto kernel metric 256 mtu 1500advmss 1440 hoplimit 4294967295

Maintenance Provider IPv4 Routing tableTABLE main:192.168.36.0/22 dev eth0 proto kernel scope linksrc 192.168.36.10

Maintenance Provider IPv6 Routing tableTABLE main:fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440hoplimit 4294967295ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1440hoplimit 4294967295

Data Provider ZTC0 IPv4 Routing tableTABLE main:10.1.1.1 dev eth2 scope host metric 510.1.1.0/24 dev eth2 proto kernel scope linksrc 1.1.1.1410.1.1.0/24 dev eth1 proto kernel scope linksrc 1.1.1.1510.1.1.0/24 dev eth3 proto kernel scope linksrc 1.1.1.13

TABLE ETH1:

Displaying the CIP Configuration 81

10.1.1.0/24 dev eth1

TABLE ETH2:10.1.1.1 dev eth2 scope host metric 510.1.1.0/24 dev eth2

TABLE ETH3:10.1.1.0/24 dev eth3

Data Provider ZTC0 IPv6 Routing tableTABLE main:fe80::/64 dev eth2 proto kernel metric 256 mtu 1500advmss 1440 hoplimit 4294967295fe80::/64 dev eth1 proto kernel metric 256 mtu 1500advmss 1440 hoplimit 4294967295fe80::/64 dev eth3 proto kernel metric 256 mtu 1500advmss 1440 hoplimit 4294967295

TABLE ETH1:fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1440hoplimit 4294967295

TABLE ETH2:fe80::/64 dev eth2 metric 256 mtu 1500 advmss 1440hoplimit 4294967295

TABLE ETH3:fe80::/64 dev eth3 metric 256 mtu 1500 advmss 1440hoplimit 4294967295

The original entries are listed under “TABLE MAIN”. Additional tables are listed as “TABLE ETH5”,and so on.

Example 8 Climstatus Command IP Routing Table Information (IP and Telco CLIM) (RVUsprior to J06.10/H06.21

\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD n1002532 climstatus -o rKernel IP routing table:Destination Gateway Genmask Ifacelocalnet * 255.255.255.0 eth0172.17.214.0 * 255.255.255.0 eth1172.17.0.0 172.17.214.1 255.255.0.0 eth1224.0.0.0 * 240.0.0.0 eth1224.0.0.0 * 240.0.0.0 eth0..............................................................................................................................................

Kernel IPv6 routing table:Destination Next_Hop

Flags Metric Ref Use Iface::1/128 ::

U 0 13 2 lo::1.2.3.4/128 ::

U 0 0 2 lo::3.4.5.6/128 ::

U 0 0 2 lo::4.3.2.1/128 ::

U 0 0 2 lo::16.107.192.195/128 ::

U 0 0 2 lo::127.0.0.1/128 ::

U 0 0 2 lo::172.17.190.2/128 ::

U 0 0 2 lo::172.17.190.5/128 ::

U 0 0 2 lo::172.17.214.50/128 ::

82 CIP Configuration and Management

U 0 0 2 lo3ffe:1200:aaaa:bbbb::/128 ::

U 0 0 2 lo

Hard Disk Space UsageThis display shows information pertaining to hard disk space usage.

Example 9 Climstatus Command Hard Disk Space Usage

\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD n1002532 climstatus -o hn1002532:~#climstatus -o h

Filesystem Disk Space UsageFilesystem Type Size Used Avail Use% Mounted/dev/sda2 ext3 32G 11G 20G 36% /tmpfs tmpfs 2.0G 64K 2.0G 1% /dev/shmtmpfs tmpfs 10M 9.8M 224K 98% /dev

Failover ConfigurationThis display shows failover configuration.

Example 10 Climstatus Command Failover Configuration (IP CIP)

\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD n1002531 climstatus -o f

Interface Failover Configuration:Source DestinationN1002531.eth1 N1002533.eth1N1002531.eth2 N1002533.eth3

IPSec ConfigurationThis display shows IPSec configuration.

Example 11 Climstatus Command IPSec Configuration (IP and Telco CLIM)

For CLIM(s) with the MultiProv feature enabled, the following is the output for IPSec configuration.\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD n1002531 climstatus -o i

Data Provider ZTC0 Security Policies---------------------------------------------------10.3.3.2[any] 10.1.1.2[any] any

in ipsecesp/transport//requirecreated: Feb 8 14:54:57 2007 lastused:lifetime: 0(s) validtime: 0(s)spid=8 seq=2 pid=369refcnt=1

10.1.1.2[any] 10.3.3.2[any] anyout ipsecesp/transport//requirecreated: Feb 8 14:54:57 2007 lastused:lifetime: 0(s) validtime: 0(s)spid=1 seq=1 pid=369refcnt=1

10.3.3.2[any] 10.1.1.2[any] anyfwd ipsecesp/transport//requirecreated: Feb 8 14:54:57 2007 lastused:lifetime: 0(s) validtime: 0(s)spid=18 seq=0 pid=369refcnt=1

Displaying the CIP Configuration 83

---------------------------------------------------

Data Provider ZTC0 Security Associations---------------------------------------------------10.1.1.2 10.3.3.2esp mode=tunnel spi=104020735(0x06333aff) reqid=0(0x00000000)E: 3des-cbc 89bc2167 67e907db 36194b58 163d37f4 966907d8c6dc4febA: hmac-md5 77902409 4ddf1ea3 7522e4b8 fb202793seq=0x00000000 replay=4 flags=0x00000000 state=maturecreated: Feb 8 15:19:02 2007 current: Feb 8 15:19:20 2007diff: 18(s) hard: 28800(s) soft: 23040(s)last: hard: 0(s) soft: 0(s)current: 0(bytes) hard: 0(bytes) soft: 0(bytes)allocated: 0 hard: 0 soft: 0sadb_seq=7 pid=863 refcnt=0

10.3.3.2 10.1.1.2esp mode=tunnel spi=67944745(0x040cc129) reqid=0(0x00000000)E: 3des-cbc ae9637c0 4093cc5e 457f248d a35518e2 3fe45e53a1304a03A: hmac-md5 883dd135 b494dff9 99bf9796 fe7b0165seq=0x00000000 replay=4 flags=0x00000000 state=maturecreated: Feb 8 15:19:02 2007 current: Feb 8 15:19:20 2007diff: 18(s) hard: 28800(s) soft: 23040(s)last: hard: 0(s) soft: 0(s)current: 0(bytes) hard: 0(bytes) soft: 0(bytes)allocated: 0 hard: 0 soft: 0sadb_seq=3 pid=863 refcnt=0

SNMP InformationThis display shows SNMP information.

Example 12 Climstatus Command SNMP Information

\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD n1002581 climconfig snmp -infocomForte SSH client version T9999H06_11Feb2008_comForte_SSH_0078Trap Receiver IP Address 192.168.36.10

192.168.36.11SNMP Agent State STARTEDSNMP Agent Listening IP Address 192.168.37.81Termination Info: 0

CLIM Configuration InformationThis display shows CLIM configuration information.

Example 13 Climstatus Command CLIM Configuration

\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD s1002581 climstatus -o c

CLIMPREP Configuration:VERSION 1CONNECTED_GMS 100.2.3.3.0SYS_NAME MYSYSSNET_SPEED 2NETWORK_CLIM 1DISK_CLIM 0NUM_SNET_CONN 2SWITCH_TYPE 1PCI_SLOTS 1.2C,2.1F,3.DC,4.1F,5.VO

84 CIP Configuration and Management

Displaying System InformationUse the psclim tool to display system information about CLIM processes. The psclim commandshows the process PID, memory used, percentage memory, percentage CPU time, accumulatedCPU time, start time, run status, and start command.For field descriptions, see the ps(1) man page.This command displays information about CLIM processes on s1002532:

Example 14 psclim Command

\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD s1002532 psclimPID RSS %MEM %CPU TIME START STAT CMD1640 1616 0.0 0.0 00:00:00 Sep 25 S /usr/local/bin/climmon1698 7312 0.1 0.0 00:00:00 Sep 25 S confsync1644 7360 0.1 0.0 00:00:00 Sep 25 S cipssrv --number 01690 7316 0.1 0.0 00:00:00 Sep 25 S climagt --number 1

Displaying Man Pages for CIP CommandsThe CLIM man commands provide online documentation for the CLIM side of CIP. The manpages include entries for the clim(1), climstatus(1), ifstart(1), ifstop(1), prov(1p), psclim(1), andclimconfig(1) commands and the CLIM configuration files. See Chapter 12: “CLIMCMD andCLIMCMD climconfig Commands (Man Pages)” for documentation on CIP man pages.Most Linux commands have man pages. You can access Linux man pages by using the CLIMCMDcommand. The man commands have this syntax:CLIMCMD {clim-name |IP-address} man [section] command

sectionman pages are grouped into sections of related commands. By default, all sections aresearched for documentation on a command.To disambiguate documentation for commands with the same name, you can optionallyspecify the section to indicate which command is intended. For example, the linux command"ip" is grouped into section 8, while the ip object of climconfig is documented in section 1.Specifying the section to the man command allows these two different man pages to beaccessed:CLIMCMD N1002531 man 1 ipCLIMCMD N1020531 man 8 ip

commandIs the CLIM or Linux command for which you want information. For example, the commandCLIMCMD n1002531 man man displays a description of the Linux man command. If youwant to see a man page for a climconfig command, enter climconfig.subcommand-name,for example, CLIMCMD n1002531 man climconfig.failover.

You can obtain help by using the SCF help command. See “SCF HELP Facility” (page 217).

Monitoring CIPBecause CIP resides on both the NonStop host system and the CLIM, monitoring it requires useof the Subsystem Control Facility (SCF) and the CLIMCMD CLI.

Displaying Man Pages for CIP Commands 85

On the NonStop Host System

Monitoring CIP ProcessesTo monitor the CIP processes on the NonStop host system, you use the SCF commands:

• STATS CLIM, to display protocol statistics for individual processes on the CLIM

• STATS MON, to display statistics pertaining to the interaction of CIP processes on theNonStop host system with applications using the socket interface

For more information about these commands, see Chapter 11 (page 210).

Monitoring the Interface to the CLIMTo monitor the interaction between CIP processes on the NonStop host system and individualCLIMs, you use the SCF commands:

• STATUS MON, to display the status of the interaction of CIP processes on the NonStophost system with individual CLIMs, for example, fabric status.

• STATUS CLIM, to discover whether a given CLIM is present and, if so, whether it is startedor stopped and whether it is currently being traced. The detail option also displays informationabout the physical connection of the CLIM to the NonStop host system.

For more information about these commands, see Chapter 11 (page 210).

On the CLIMSCF commands on the NonStop host system can show only a limited amount of informationabout the operation of the CLIM and its TCP/IP protocol stack. More information is availableusing commands that run on the CLIM itself.

Monitoring CLIM ProcessesYou use the CLIM psclim script to monitor CLIM-specific processes.This script is derived from the Linux ps command and reports information such as the processID, memory and CPU utilization, start time, and run status of specific processes on the CLIM.For detailed information, see “Displaying System Information” (page 85).

Monitoring CLIM Devices and Network InterfacesYou use the CLIM climstatus script to monitor CLIM-specific resources. You can invoke the scriptwithout options to monitor a wide range of CLIM devices or specify options to find out the statusof a particular resource:

• The s option provides information about NonStop systems.

• The l option provides information about the Local Area Network (Ethernet).

• The r option provides information about the Kernel IP routing table.

• The h option provides information about Linux file-system disks and disk space.See “Displaying CLIM Status Information With climstatus” (page 77) for the syntax of thiscommand.

Configuring Bonded Interface Failover (IP CIP)To set up interface-to-interface failover, use these CLIMCMD {clim-name | ip-address}climconfig commands:

86 CIP Configuration and Management

1. Use interface to add a bonded interface.2. Use ip to add an IP address to the bonded interface.3. Use slaveinterface to configure the bonded interface with multiple slave interfaces.

With multiple physical interfaces configured for each bonding interface, when one physicalinterface has a problem, the traffic will be switched to another interface.Use the -primary option to designate a primary interface to be used for the bonded interfacewhen using bond mode 1. This interface will be used as the active interface for the bondwhenever it is available. See the “climconfig.slaveinterface Description” (page 382) command.Also see Example 15: CLIM-to-CLIM Failover (IP CIP) (page 87) for an example of configuringa primary interface for the bonded interface.

Configuring CLIM-to-CLIM Failover (IP CIP)To set up CLIM-to-CLIM failover, use the CLIMCMD {clim-name | ip-address} climconfigfailover command to add a destination interface on a different CLIM.For examples of these commands, see “Configure the Eth1 Through Eth5 Interfaces (IP CLIMOnly)” (page 56) and “Configure CLIM-To-CLIM Failover (IP and Telco CLIMs Only)” (page 56).For the full syntax of these commands, see “Climconfig (Man Pages)” (page 307).For faster failover, on the router, do not set the Retrans Timer field of the router advertisements,or set it less than or equal to 1000ms.

CAUTION: If the Retrans Timer field of the router advertisements is set to greater than 1000ms,failover may not work.

Example 15 CLIM-to-CLIM Failover (IP CIP)

This example is for CLIMs with MULTIPROV OFF. See “Setting Up Multiple Providers per CLIM”(page 122) for a discussion of configuring CLIMs with MULTIPROV ON.1. Find already configured CLIM interfaces.

> CLIMCMD c1002581 climconfig interface –info allcomForte SSH client version T999H06_20Mar2008_comForte_SSH_079Interface : loInterface Type : Loopback Interface

Interface : eth0Interface Type : Physical InterfaceMTU Size : 1500IP Address : 192.168.37.81

Netmask : 255.255.0.0Auto Negotiation Details :- Status : on

Line Speed : Not ApplicableDuplex : Not Applicable

Software MAC Address : Unspecified

Interface : eth1Interface Type : Physical InterfaceMTU Size : 1500IP Address : 10.1.1.2

Netmask : 255.255.252.0ROUTE Details :- Route Type : Default Route

Destination Address : 0.0.0.0Netmask : 0.0.0.0Gateway Address : 10.1.1.1Metric : 0Minimum RTO : UnspecifiedInitCWND : Unspecified

Configuring CLIM-to-CLIM Failover (IP CIP) 87

Auto Negotiation Details :- Status : on

Line Speed : Not ApplicableDuplex : Not Applicable

Software MAC Address : Unspecified

Interface : eth0:0Interface Type : Logical InterfaceIP Address : 192.168.36.10

Netmask : 255.255.252.0

Interface : ib1Interface Type : Physical InterfaceMTU Size : 2044IP Address : 10.2.1.2

Netmask : 255.255.252.0ROUTE Details :- Route Type : Default Route

Destination Address : 0.0.0.0Netmask : 0.0.0.0Gateway Address : 10.2.1.1Metric : 0Minimum RTO : UnspecifiedInitCWND : Unspecified

Interface : ib0Interface Type : Physical InterfaceMTU Size : 2044IP Address : 10.3.1.2

Netmask : 255.255.252.0

2. Delete CLIM interfaces> CLIMCMD c1002581 ifstop eth2 –forcecomForte SSH client version T9999H06_20Mar2008_comForte_SSH_0079Interface is stopped.Termination info: 0\BLITUG.$SYSTEM.SABUN 15> CLIMCMD c1002581 climconfig interface –delete eth2comForte SSH client version T9999H06_20Mar2008_comForte_SSH_0079Deleted the Interface.Termination info: 0

3. Check that all data interfaces are deleted.> CLIMCMD C1002582 climconfig interface –info allcomForte SSH client version T9999H06_20Mar2008_comForte_SSH_0079Interface : loInterface Type : Loopback Interface

Interface : eth0Interface Type : Physical InterfaceJumbo Frame : NOIP Address : 192.168.37.82

Netmask : 255.255.0.0ROUTE Details :– Route Type : Default Route

Destination Address : 0.0.0.0Netmask : 0.0.0.0Gateway Address : 0.0.0.0Metric : 0

Interface : eth0:0Interface Type : Logical InterfaceJumbo Frame : NOIP Address : 192.168.36.11

Netmask : 255.255.0.0

Termination Info: 0

88 CIP Configuration and Management

4. Set up bond mode C1002581 and C1002582 on LAN A:> CLIMCMD c1002582 climconfig bondmode –info> CLIMCMD c1002582 climconfig bondmode –modify 1> CLIMCMD c1002581 climconfig bondmode –info> CLIMCMD c1002581 climconfig bondmode –modify 1

5. Bond the interface of C1002582 on LAN A with eth5 as primary.> CLIMCMD c1002582 climconfig interface –add bond0> CLIMCMD c1002582 climconfig slaveinterface –configure bond0 –add eth4> CLIMCMD c1002852 climconfig slaveinterface -configure bond0 -add eth5 -primary eth5> CLIMCMD c1002582 climconfig ip –add bond0 –ipaddress 10.1.100.11 –netmask 255.0.0.0

6. Bond the interface of C1002581 on LAN A with eth4 as primary.> CLIMCMD c1002581 climconfig interface –add bond0> CLIMCMD c1002581 climconfig slaveinterface –configure bond0 –add eth5> CLIMCMD c1002581 climconfig slaveinterface -configure bond0 -add eth4 -primary eth4> CLIMCMD c1002581 climconfig ip –add bond0 –ipaddress 10.1.100.12 –netmask 255.0.0.0

7. Configure failover on C1002582:> CLIMCMD C1002582 climconfig failover –add bond0 –dest C1002581.bond0comForte SSH client version T9999H06_20Mar2008_comForte_SSH_0079Added the Failover ConfigurationTermination Info: 0

> CLIMCMD C1002582 climconfig failover –info C1002582 –interface bond0comForte SSH client version T9999H06_20Mar2008_comForte_SSH_0079SOURCE DESTINATIONC1002581.bond0 C1002582.bond0Termination Info: 0

Figure 11: Configuration State shows the configuration state at this point:

Figure 11 Configuration State

8. Configure failover on C1002581:> CLIMCMD C1002581 climconfig failover –add bond0 –dest C1002582.bond0c

9. Configure LAN B.

Configuring CLIM-to-CLIM Failover (IP CIP) 89

> CLIMCMD c1002581 climconfig ip -add bond0 -ipaddress 10.13.100.21 netmask 255.0.0.0> CLIMCMD c1002581 climconfig ip -add bond1 -ipaddress 10.14.100.22 -netmask 255.0.0.0

10. Configure LAN C> CLIMCMD C1002582 climconfig interface –add eth2> CLIMCMD C1002582 climconfig ip –add eth2 –ipaddress 10.25.100.31 –netmask 255.0.0.0> CLIMCMD C1002582 climconfig ip –add eth2 –ipaddress 10.26.100.32 –netmask 255.0.0.0

Figure 12: Configuration State shows the state of the configuration at this point:

Figure 12 Configuration State

Replicating the Configurations from One CLIM to Another CLIMTo replicate any portion or the entire configuration from one CLIM to another CLIM, use the INand OUT run options of CLIMCMD, described here:1. Use this command:

CLIMCMD /OUT file-name/ {clim-name|IP address} climconfig command-args –obeyform

to obtain the desired configuration information from the CLIM to file-name. For example,to place the configurations from C1002581 into the file ‘config,’ enter:CLIMCMD /OUT config/ C1002581 climconfig interface –info all –obeyform

2. Edit file-name for any changes in the configuration value.3. Stop the destination CLIM.4. Use this command:

CLIMCMD /IN file-name/ {clim-name|IP address}

to replicate the configuration on the destination CLIM. For example, to replicate theconfiguration from C1002581 on C1002582, enter:CLIMCMD /IN config/ C1002582

5. Start the CLIM.6. For a Storage CLIM, you must run the lunmgr -a command for each enclosure so that

they will be numbered correctly.

90 CIP Configuration and Management

For the full syntax of the climconfig commands, refer to “Climconfig (Man Pages)” (page 307).

Using the CLIMCMD /IN/ run-optionYou can create a file manually with the set of commands to be executed on a CLIM and specifythe /IN/ run-option of CLIMCMD. It is mandatory that the user-created file have the command‘exit’ added at the end.1. Create a file ‘config’ with the list of commands followed by an ‘exit’. End-Of-Line characters

in a command that spans multiple lines must be escaped using the ‘\’ character, as shownin the second command, below.climconfig interface -add eth5climconfig ip -add eth5 -ipaddress \

172.18.7.5 -netmask 255.255.255.0exit

2. Pass this file to the /IN/ run-option:CLIMCMD /IN config/ C1002581

Linux C1002581 2.6.32-clim-18-amd64#1 SMP Tue Jul 19 18:36:07 UTC 2011 x86_64

The programs included with the Debian GNU/Linux system are free software;the exact distribution terms for each program are described in theindividual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extentpermitted by applicable law.Last login: Thu Jan 5 00:44:32 2012 from 192.168.36.11

C1002581:~# climconfig interface -add eth5Added the Interface.

C1002581:~# climconfig ip -add eth5 -ipaddress \> 172.18.7.5 -netmask 255.255.255.0Added the IP.

C1002581:~# exitlogout

Termination Info: 0

Starting and Restarting CIPUpon installation, the CLIM software is configured to start automatically when power is appliedto the CLIM device. On the NonStop host system side, first start CIP and then the applicationsthat will use the subsystem.For examples of the commands needed to start the CIP subsystem, see Chapter 2 (page 53).The commands shown are issued to the Kernel subsystem and they start the CIPMAN, CIPSAM(IP CIP only) and CIPMON generic processes for the first time or after they have been stoppedby an SCF ABORT command to the Kernel subsystem. Because CIPMAN, CIPSAM and CIPMONare configured as persistent processes, the persistence manager restarts them whenever thesystem is reloaded or whenever an SCF STOP or ABORT command is issued to the CIPsubsystem rather than to the Kernel subsystem.

Starting CIP on the NonStop Host SystemThe CIP manager, monitor, and socket access method (SAM) (IP CIP only) processes arepersistent and are restarted by the persistence manager unless you set the AUTORESTARTparameter to 0 (zero) and the STARTMODE parameter to MANUAL in SCF ADD command to theKernel subsystem. See “Managing Persistence on the NonStop Host System” (page 106) for moreinformation about managing persistence. The commands used for a typical configuration of theCIPMAN, CIPSAM (IP CIP only), and CIPMON processes are:

Starting and Restarting CIP 91

1. On the NonStop host system, add the CIPMAN process to the system configuration databaseby using SCF to the Kernel subsystem:> ADD PROCESS $ZZKRN.#ZZCIP, AUTORESTART 10, PRIMARYCPU 0, &BACKUPCPU 1, NAME $ZZCIP, PROGRAM $SYSTEM.SYSTEM.CIPMAN, &HOMETERM $ZHOME, STARTMODE SYSTEM, STOPMODE SYSMSG, &STARTUPMSG “<BCKP-CPU>”

2. Add the CIPMON process to the system configuration database by using SCF to the kernelsubsystem:> ADD PROCESS $ZZKRN.#CIPMON, CPU ALL, NAME $ZCMnn, &HOMETERM $ZHOME, AUTORESTART 10, &PROGRAM $SYSTEM.SYSTEM.CIPMON, &STARTMODE SYSTEM, STOPMODE SYSMSG

3. For IP CIP, add the CIPSAM process (IP CIP only) to the system configuration database byusing SCF to the Kernel subsystem:> ADD PROCESS $ZZKRN.#CIPSAM, AUTORESTART 10, PRIMARYCPU 0,&BACKUPCPU 1, NAME $ZTC02, PROGRAM $SYSTEM.SYSTEM.CIPSAM, &HOMETERM $ZHOME, STARTMODE SYSTEM, STOPMODE SYSMSG, &STARTUPMSG "<BCKP-CPU>"

4. Start all processes.> START PROCESS $ZZKRN.#ZZCIP> START PROCESS $ZZKRN.#CIPMON> START PROCESS $ZZKRN.#CIPSAM

5. Add a Provider object.> ADD PROVIDER $ZZCIP.ZTC02

6. Add a CLIM object.On H/J series:> ADD CLIM $ZZCIP.N1002532,LOCATION (100,2,5,3,2),PROVIDER ZTC02

On L-series:> ADD CLIM $ZZCIP.NCLIM001,PROVIDER ZTC02

7. Start the CLIM and Provider objects.On H/J series:> START CLIM $ZZCIP.N1002532

> START PROVIDER $ZZCIP.ZTC02

On L-series:> START CLIM $ZZCIP.NCLIM001

> START PROVIDER $ZZCIP.ZTC02

You can also start and stop the CIP subsystem by using the SCF START and STOP commandsto the CIP subsystem ($ZZCIP). However, if $ZZCIP is a persistent process, it restartsautomatically. See “START PROCESS” (page 248) and “STOP PROCESS” (page 276).

Starting CIP on the CLIMThe CLIM itself starts automatically. Under certain circumstances, you may need to issue theifstart command. See “Controlling Interface States (IP CIP)” (page 94).The SCF CLIM object does not start automatically, however. Start the CLIM by using the STARTCLIM command. For example:> START CLIM $ZZCIP.N1002532

92 CIP Configuration and Management

Starting the IP Applications (IP CIP Only)LISTNER and TELSERV come preconfigured on your system. However, if you need to startthem, follow these procedures.1. Delete and add a DEFINE and PARAM for CIPSAM processes to be used as the transport

service providers for LISTNER and TELSERV.From the SCF prompt, issue these commands:> DELETE DEFINE =TCPIP^PROCESS^NAME> ADD DEFINE =TCPIP^PROCESS^NAME, CLASS MAP, FILE $ZTC0> DELETE PARAM TCPIP^PROCESS^NAME> PARAM TCPIP^PROCESS^NAME $ZTC0> PARAM ZTNT^TRANSPORT^PROCESS^NAME $ZTC0

2. Start LISTNER:> RUN $SYSTEM.SYSnn.LISTNER /TERM $ZHOME, OUT $ZHOME, NAME $LSN0,CPU 0, NOWAIT, PRI 160/1 LOG_GOTCONN

3. Start TELSERV:> RUN $SYSTEM.SYSnn.TELSERV /TERM $ZHOME, OUT $ZHOME, NAME $ZTN0,CPU 1, NOWAIT, PRI 170/ -BACKUPCPU 0

Restarting CIP on the NonStop Host SystemTo restart the NonStop host system side of the CIP subsystem, you can stop and restart all theobjects subordinate to CIPMAN. This is like a reboot of the subsystem; all active connectionsare stopped.If you are not running an alternative TCP/IP subsystem, CLCI sessions for viewing error messagesare available through the OSM Low-Level Link (H- and J-series) or the OSM System StartupTool (L-series). (CLCI has limited functionality, but provides a primitive terminal emulation whenno other TCP/IP subsystem is available.)These comForte MR-Win6530 Terminal Emulator CLCI TACL sessions are launched automaticallywhen you perform a system load. To launch manually:

• In the OSM Low-Level Link, from the File menu select Start Terminal Emulator→ForStartup TACL.

• In the OSM System Startup Tool, from the Operations menu on the main screen select StartTerminal Emulator→For Startup TACL.

1. Stop the subordinate objects by using the SCF command:> ABORT PROCESS $ZZCIP, SUB ONLY, FORCED

2. Restart the subordinate objects by using the SCF command:> START PROCESS $ZZCIP, SUB ONLY

When you perform a system load in the System Startup Tool (via the Start System action),comForte MR-Win6530 Terminal Emulator sessions for both Startup TACL and Event Streamsare launched automatically.When loading an individual processor (via the Load action in the Processor Status window),those sessions are not automatically launched, but can be launched from the Operations menuon the main screen of the System Startup Tool:Start Terminal Emulator> For Startup TACL> For Event Streams

Restarting CIP on the CLIMTo restart the CLIM, issue these CLIMCMD commands:

Starting and Restarting CIP 93

> CLIMCMD {clim-name | ip-address} clim abort> CLIMCMD {clim-name | ip-address} clim start

You can also reboot a CLIM using the Reboot action in the OSM Service Connection.For information about using the clim command, see “Troubleshooting Tools and Tips” (page 112).

Controlling Interface States (IP CIP)To bring an interface up or down, use the ifstart and ifstop CLIMCMD commands. Use thesecommands under these circumstances:

• If you want to delete an interface once the CLIM is started; for example, if you want to changephysical interfaces to bonded interfaces. (You need to bring the interface down before doingso.)

• If you want to delete the only remaining slave of a bond. (You need to use ifstop on the bondand then delete that slave.)

• If you want to perform maintenance of the CLIM interfaces. (For example, when changingthe cables of an interface, you can do so without bringing down the entire CLIM. First issuean ifstop command. This notifies the host that the interface is being intentionally broughtdown for maintenance by the operator. The host does not take any action (such as failover)for that interface. After you are done with the maintenance, issue an ifstart on the interfaceto activate it for use.

NOTE: Sockets are not affected by ifstop but some socket operations that require theinterface state to be up may receive an error. For example, a connect may receive anunreachable error.

Activating an InterfaceUse the ifstart command to activate an interface if you stopped using the ifstop command. Forall data interfaces (eth1 – ethn, ib0–ibn, bonding and tunnel interfaces), this command informsthe NonStop host system to start using the specified interface. You execute the ifstart commandon the CLIM by using the CLIMCMD tool as described under “Entering CIP Commands” (page 61).Only use the ifstart command to restart the interface after using ifstop command.The ifstart command syntax is:CLIMCMD {clim-name | IP-address} ifstart interface

interfaceSpecifies the network interface name to be used by the NonStop host system for all interfacefunctionality. The interface name can be specified as a physical or bonded interface name,for example, eth1 or bond0 or ib0, or a tunnel interface (for example, MYTUN).

Errors

• The interface interface name is not configured.

• This command is not supported for the interface eth0.

• This command is not supported for the interface lo.

• This command is not supported for the interface eth0:0.

• slave interface is not configured for this bonded interface.

• climagt process is not executing.

• Interface is already in started state.

94 CIP Configuration and Management

Deactivating an InterfaceUse the ifstop command to deactivate an interface. ifstop brings down the physical, bonding, andtunnel interfaces. All the IP addresses and routes associated with a network interface aredeactivated, including the IP addresses migrated to the failover CLIM.You execute the ifstop command on the CLIM by using the CLIMCMD tool as described in“Entering CIP Commands” (page 61).For all data interfaces (eth1 - ethn, ib0–ibn, bonding, and tunnel interfaces), the ifstop commandbrings down the interface. The interface is brought down by the NonStop host system. Issuingifstop on an interface does not trigger a failover.If there is a tunnel associated with the specified interface, and if the tunnel interface is UP, CIPdoes not allow the interface to be stopped. The tunnel interface must be stopped before its parentinterface can be stopped. The ifstop command syntax is:CLIMCMD {clim-name |IP-address} ifstop interface [-force]

interfaceSpecifies the network interface to be brought down. The interface name can be a physicalor bonded interface name, for example, eth1, bond0, ib0 or a tunnel interface name (forexample, MYTUN).

-forceWhen used without –force option, ifstop prompts for confirmation before stopping the interface.If the –force option is used, ifstop stops the interface without prompting for the confirmation.

Errors

• The interface interface name is not configured.

• This command is not supported for the interface eth0.

• This command is not supported for the interface lo.

• This command is not supported for the interface eth0:0.

• climagt process is not executing.

• Interface is in already in stopped state.

• The interface interface has a tunnel interface associated with it. The tunnel interfaceshould be stopped prior to stopping the specified interface.

Configuring IPSec (IP CIP)Internet protocol security (IPSec) provides application-transparent encryption services for IPnetwork traffic. You can set up IPSec on an IP-address-to-IP-address basis, and optionally on aUDP or TCP port, but you cannot establish IPSec on a per interface basis.

NOTE: In CIP, limited SCTP security is provided.

IPSec is configured on the CLIM using the climconfig command tool. See “Climconfig (ManPages)” (page 307) for detailed syntax of the IPSec configuration commands.The IPSec configuration is not failed over and must be identical on the home and failover CLIMsfor addresses that can fail over between them.

Installing X.509 CertificatesObtain certificates from a certificate authority (CA) and install them on the NonStop console byfollowing the instructions from your CA. Move the certificates, the private key files, and thecertificate revocation lists, which are stored in PEM format, to the /etc/racoon/certs directoryon the CLIM.

Configuring IPSec (IP CIP) 95

NOTE: While there are independent IPSec configurations for each provider, they all look forcertificates from this common directory (/etc/racoon/certs).

If the certificate of the peer is to be checked against a certificate authority, the certificate of theCA also has to be stored in this directory. For OpenSSL to find the certificate it has to be linkedusing the hashed name:ln -s CAfile.pem 'openssl x509 -noout -hash < CAfile.pem'.0

If the certificate additionally is to be checked against a certificate revocation file (CRL) the CRLmust be stored in the same directory (/etc/racoon/certs) using a similar linked hashedname:ln -s CRLfile.pem 'openssl x509 -noout -hash < CAfile.pem'.r0

Once the certificates are on the console, transfer them to the CLIM by using secure FTP fromthe PuTTY application. You can find the PuTTY SFTP application (psftp.exe) on the console inC:\Documents and Settings\Administrator\Desktop\putty\psftp.exe. From theDOS comand prompt, run psftp.exe as follows:psftp root@clim eth0 ip-address

NOTE: Use PuTTY only for transferring files between the CLIM and the console, not for CLIMcommands.

At the psftp prompt use the lcd command to go to the NonStop console folder where the certsare located and the cd command to change directories to /etc/racoon/certs. Then use theput command to transfer the files.

Setting Up Links to the Certificate Revocation List (CRL) and to the CertificateAuthority (CA)

To set up links to the certificate revocation list (CRL) use this command (which executes usingopen SSL):1. Create a TACL macro file called clinks (for example) with these lines (substituting real

values for the parameters):?tacl macroCLIMCMD %1% ln -s /etc/racoon/certs/%2% /etc/racoon/certs/`opensslx509 -noout -hash < /etc/racoon/certs/%2%`.0CLIMCMD %1% ln -s /etc/racoon/certs/%3% /etc/racoon/certs/`opensslx509 -noout -hash < /etc/racoon/certs/%2%`.r0

Where:• %1% is the CLIM name

• %2% is the CA certificate file name

• %3% is the CRL file nameFor example:TACL> clinks DL385C cacert.pem crl2.pem

Configuring Pre-Shared KeysPre-shared keys are used by the racoon daemon to establish automatically keyed IPSec securityassociations. Use the climconfig psk commands to configure pre-shared keys. These commandsalter the contents of the /etc/racoon/psk.txt file.

96 CIP Configuration and Management

NOTE: There are independent pre-shared key configurations for each provider when theMULTIPROV option is ON for a particular CLIM and the -prov argument must be specified toselect the desired provider's configuration.

DescriptionClimconfigCommand

Add pre-shared key informationpsk –add

Delete pre-shared key informationpsk –delete

Display pre-shared keys configuredpsk –info

Configuring Security PoliciesSpecific security requirements are defined at each node by a list of policies that form the node'ssecurity policy database (SPD). The protection provided to each incoming or outgoing traffic flowis verified or decided by consulting the SPD. You use the following climconfig commands toconfigure the SPD. These commands alter the contents of the /etc/ipsec-tools.conf file.SP objects added by climconfig are, by default, not immediately added to the active SPDmaintained by the kernel, unless the -load parameter is specified.The climconfig sp -start command allows all configured SPs to be simultaneously addedto the SPD, allowing you to configure security policies carefully and then activate them as agroup. CLIMs that are rebooted automatically load all configured SPs into the SPD.The climconfig sp -stop command removes all configured SP objects from the kernel'sSPD, but keeps them configured.

NOTE: There are independent security policy configurations for each provider when theMULTIPROV option is ON for a particular CLIM, and the -prov argument must be specified toselect the desired provider's configuration.

DescriptionClimconfigCommand

Add security policy configurationsp –add

Delete security policy configurationsp –delete

Display security policies configuredsp –info

Loads all configured security policies into the SPDsp –start

Empties the SPD, deactivating all configured security policiessp –stop

Configuring Security AssociationsSecurity associations are used by the authentication header (AH) and encapsulating securitypayload (ESP) to agree upon the security algorithms, transforms, and parameters shared by thesender and the receiver of a protected traffic flow. Use the climconfig sa command to configurethe security associations.SA objects can either be configured as automatic SAs (the default), or as manual SAs (specifiedwith the -manual argument). Manual SAs are, by default, not immediately added to the activeSAD maintained by the kernel, unless the -load parameter is specified. Automatic SAs alterthe configuration of racoon, but racoon is not informed immediately of the change unless the-restart argument is specified. Automatic SAs do not result in SAs being added to the SADuntil racoon successfully completes an IKE negotiation, as directed by the automatic SAconfiguration.

Configuring IPSec (IP CIP) 97

NOTE: There are independent security associations for each provider when the MULTIPROVoption is ON for a particular CLIM, and the -prov argument must be specified to select thedesired provider's configuration.

DescriptionClimconfigCommand

Add security association to configuration filesa –add

Delete security association from configuration filesa –delete

Display security associations configuredsa –info

Configuring Remote InformationThe climconfig remote command alters racoon configuration to add or delete instructions for IKEPhase 1 with remote peers, specifying how to authenticate the peer and what security parametersto use for Phase 1 SAs. Like automatic SAs, racoon is not immediately informed when remoteconfigurations are added, unless the "-restart" parameter is specified to restart racoon with thenew configuration.The remote command alters or gets information about the contents of the /etc/racoon/racoon.conffile.

NOTE: There are independent remote entries for each provider when the MULTIPROV optionis ON for a particular CLIM.

DescriptionClimconfigCommand

Add remote entry into racoon.conf configuration fileremote –add

Delete proposals for remote IP address from racoon.conf configuration fileremote –delete

Display proposals and other configurations for the remote IP address from the racoon.confconfiguration file

remote –info

Controlling the Virtual Private Network (VPN)You activate and deactivate the virtual private network (VPN) connections by using the followingcommands:

DescriptionCommand

Load configured security policies into the security policy databasesp –start

Display status of virtual private network (VPN) connectionvpn –status

Unload security policies from security policy databasesp –stop

Unload security associations from security association databasesa –stop

Using IPSecTasks for configuring and managing IPSec are:

• Configuring, controlling, and monitoring manual IPSec connections

• Configuring, controlling, and monitoring automatic IPSec connections by using pre-sharedkey or X.509 security certificates

• Configuring all IPSec related attributes such as SP, SA, remote, and psk on a set of CLIMs

98 CIP Configuration and Management

• Adding a static route on the IPSec-enabled CLIM so the host routing decisions favor NonStophost system application traffic to be forwarded to this CLIM

• Restarting the racoon daemon if you add a new SA or remote attribute using the -restartoption. (Restart of racoon causes all active SAs in the kernel's SAD to be flushed (whetherthese were automatically established by racoon, or were manually added SAs by climconfig).This results in disruption of existing application data traffic over the established IPSecconnections.)

• If a SP is modified (delete followed by add), a new IPSec connection is re-establishedHere is a sample script for using CLIMCMD on a CLIM with MULTIPROV OFF on the NonStophost system to issue IPSec climconfig commands to do sp, remote and sa with X.509 securitycertificates:CLIMCMD N1002581 climconfig sp -add

-s 1.2.3.6 -d 1.2.3.4 -u any -dir in -policy ipsec-protocol esp -mode transport -level require -load

CLIMCMD N1002581 climconfig sp -add-s 1.2.3.4 -d 1.2.3.6 -u any -dir out -policy ipsec-protocol esp -mode transport -level require -load

CLIMCMD N1002581 climconfig remote -add-ip 1.2.3.6 -M base -idtype asn1dn-pubcert host1_cert.pem-privkey host1_key.pem -E 3des -H md5 -A rsasig-D modp768 -restart

CLIMCMD N1002581 climconfig sa -add-s 1.2.3.4 -d 1.2.3.6 -u any -P modp1024 -E aes-A hmac_md5 -C deflate -restart

Configuring Transport of Authentication Events from CLIMThe CLIM Authentication Transport feature transports the authentication events from the CLIMto the NonStop Host System. These authentication events record various security-related activitieson the CLIM. For example, events are generated by the SSHD process running on the CLIMwhen a remote user attempts to log on to the CLIM. After the generation of these events on theCLIM, the events are transported to the NonStop Host System. At the NonStop Host System,these authentication events received from the CLIM are formatted and logged as EMS event5239, zcip-evt-clim-auth-event under a new EMS collector $ZCLA.The EMS collector $ZCLA is automatically configured on the NonStop Host system as a persistentprocess and is managed by the SCF KERNEL subsystem manager.

Checking the Status of the Collector $ZCLAIssue this command to check the status of the $ZCLA collector:$SYSTEM SYSTEM 2> scf status process $zzkrn.zclaSCF - T9082H01 - (23JUN11) (02MAY11) - 05/02/2013 11:56:35 System \VIHAR(C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P.

NONSTOP KERNEL - Status PROCESS \VIHAR.$ZZKRN.#ZCLA

Symbolic Name Name State Sub Primary Backup OwnerPID PID ID

ZCLA $ZCLA STARTED 0,383 1,380 255,255

Total Errors = 0 Total Warnings = 0

Starting the CollectorIssue this command to start the collector if the collector is in STOPPED state:$SYSTEM SYSTEM 7> scf start process $zzkrn.zclaSCF - T9082H01 - (23JUN11) (02MAY11) - 05/03/2013 14:58:09 System \VIHAR

Configuring Transport of Authentication Events from CLIM 99

(C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P.KERNEL W00030 Process \VIHAR.$ZCLA started successfully.

Adding the CollectorIssue this command to add the collector with its default settings if the collector was not alreadyadded:ADD PROCESS $ZZKRN.ZCLA , &

AUTORESTART 5 , &BACKUPCPU 1 , &DEFAULTVOL $SYSTEM.ZAUDIT , &HOMETERM $ZHOME , &NAME $ZCLA , &PRIMARYCPU 0 , &PRIORITY 150 , &PROGRAM $SYSTEM.SYSTEM.EMSACOLL , &STARTMODE SYSTEM , &STARTUPMSG "LOGSUBVOL $SYSTEM.ZAUDIT, SECURITY &NUNU, LOGPREFIX C, BACKUP <BCKP—CPU>, EXT 512"

Refer to the SCF Reference Manual for the Kernel Subsystem for details on parameters, theirvalues and the commands to change the values of these default parameters.

Viewing the Events in the Collector $ZCLAYou can view the authentication events by using EMSDIST for the collector $ZCLA. Issue thiscommand:TACL> #SET #INFORMAT TACLTACL> EMSDIST COLLECTOR $ZCLA, TYPE P, TEXTOUT [#MYTERM]

Retrieving the Events from the $ZCLA by an ApplicationThis feature will allow security audit applications running on NonStop to access these logs andinclude them in the audit reports. The application can retrieve these events from the collector$ZCLA. Please refer to the EMSManual for details on procedures to be used to retrieve the EMSmessages from the alternative collector.

Deleting the CollectorThe logging of authentication events is an optional service. If you are not interested inauthentication events and do not want to have the collector $ZCLA running and creating the EMSlogfiles, the $ZCLA collector can be aborted and deleted. This stops logging of authenticationevents to the collector $ZCLA. To abort and delete the $ZCLA collector, use the followingcommands:$SYSTEM SYSTEM 3> scf abort process $zzkrn.zclaSCF - T9082H01 - (23JUN11) (02MAY11) - 07/08/2013 20:24:47 System \VIHAR(C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P.KERNEL W00028 Process \VIHAR.$ZCLA aborted successfully.

$SYSTEM SYSTEM 4> scf delete process $zzkrn.zclaSCF - T9082H01 - (23JUN11) (02MAY11) - 07/08/2013 20:24:57 System \VIHAR(C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P.

Configuring CIP iptables/ip6tables (IP CIP)To configure CIP iptables and ip6tables, use the CLIMCMD {clim-name | ip-address}climconfig {climiptables|iptables|ip6tables} commands.The CLIMCMD {clim-name | ip-address} climconfig climiptables commandenables and disables the configured functionalities for iptables and ip6tables, and also displaysthe state and configurations of the iptables and ip6tables.

100 CIP Configuration and Management

Before using climiptables you must enable the facility.See : “Climconfig (Man Pages)” (page 307) for detailed syntax of the configuration commands.The CLIMCMD {clim-name | ip-address} climconfig {iptables|ip6tables}commands are used to configure the iptables and ip6tables configuration rules. Later in thissection are two examples of how one would use the climiptables facility: “Inbound FTP Traffic”(page 102) and “Allow Inbound SNMP TRAPS” (page 103).

NOTE: The CIP iptables and ip6tables configurations are not failed over. You must pre-setthe failover CLIM’s iptables and ip6tables configuration in anticipation of a failover. You cancompare the configuration of the home CLIM and failover CLIM by comparing the –obeyformoutput of climiptables from each CLIM and ensuring any iptables/ip6tables rules on the homeCLIM exist on the failover CLIM in anticipation of a failover.

Configuring climiptablesThe command syntax for climconfig climiptables isclimconfig climiptables [-prov prov-name] {-enable | -disable[-force] | -status | -info [-obeyform] | -h | -help | --help }

DescriptionClimconfig Command

Enable the iptables and ip6tables functionalityclimiptables -enable

Disable the iptables and ip6tables functionalityclimiptables -disable [-force]

Display the state of the climiptablesclimiptables -status

Display the state of the climiptables and the iptables and ip6tablesconfigurations

climiptables -info

Generate obeyform lines for the current iptables and ip6tables configurationsclimiptables -info -obeyform

Configuring iptables/ip6tablesThe command syntax for climconfig iptables isclimconfig iptables [HP options] arguments [-force]

The command syntax for climconfig ip6tables isclimconfig ip6tables [HP options] arguments [-prov prov-name] [-force]

The two options that can be used with iptables/ip6tables are -prov prov-name and -force. Eachprovider has its own iptables and ip6tables configurations, and the -prov option to specify theprovider is mandatory on CLIMs that have the MULTIPROV ON option enabled. –force, usedwith a sensitive command, causes the command to bypass user confirmation.Climconfig iptables and climconfig ip6tables configure CIP iptables and ip6tables with the sameLinux iptables and ip6tables commands and options with some limitations:

• Only INPUT chain of the ‘filter’ table is supported.

• The Linux INPUT chain is accessed indirectly via the CIP built-in chain CIP_INPUT chain.Direct access to the Linux INPUT chain is not permitted except for the ‘-L’ command.

• The functionality of the configured iptables and ip6tables rules are controlled by the state ofclimiptables. iptables and ip6tables can be configured while climiptables is disabled. Theconfigured iptables and ip6tables rules take no effect until climiptables is enabled.

“Inbound FTP Traffic” (page 102) allows all inbound FTP traffic on all but eth2 and allows inboundtelnet traffic only on eth2.

Configuring CIP iptables/ip6tables (IP CIP) 101

Example 16 Inbound FTP Traffic

climcmd N1002581 climconfig iptables -N ftpclimcmd N1002581 climconfig iptables -A ftp -i eth2 -j REJECTclimcmd N1002581 climconfig iptables -A CIP_INPUT -p tcp --dport 20:21 -j ftp

climcmd N1002581 climconfig iptables -N telnetchainclimcmd N1002581 climconfig iptables -A telnetchain ! -i eth2 -j REJECTclimcmd N1002581 climconfig iptables -A CIP_INPUT -p tcp --dport 23 -j telnetchain

Following is the output for these commands:\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD N1002581 climstatus -o tclimiptables Enabled: Yes

----------------------------------------------------------------------IPTABLES Configuration:Chain INPUT (policy ACCEPT 11 packets, 889 bytes)pkts bytes target prot opt in out source destination7636 1970K ACCEPT all -- any any N1002581 anywhere656K 228M ACCEPT all -- eth0 any anywhere anywhere204 13045 CIP_INPUT all -- any any anywhere anywhere146 9781 CIP_INPUT_p all -- any any anywhere anywhere

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 1166 packets, 220K bytes)pkts bytes target prot opt in out source destination

Chain CIP_INPUT (1 references)pkts bytes target prot opt in out source destination18 972 ftp tcp -- any any anywhere anywhere

tcp dpts:ftp-data:ftp4 224 telnet tcp -- any any anywhere anywhere

tcp dpt:telnet

Chain CIP_INPUT_p (1 references)pkts bytes target prot opt in out source destination

Chain ftp (1 references)pkts bytes target prot opt in out source destination

2 120 REJECT all -- eth2 any anywhere anywherereject-with icmp-port-unreachable

Chain telnet (1 references)pkts bytes target prot opt in out source destination

1 60 REJECT all -- !eth2 any anywhere anywherereject-with icmp-port-unreachable

IP6TABLES Configuration:Chain INPUT (policy ACCEPT 0 packets, 0 bytes)pkts bytes target prot opt in out source destination21175 2062K ACCEPT all eth0 any anywhere anywhere

0 0 CIP_INPUT all any any anywhere anywhere0 0 CIP_INPUT_p all any any anywhere anywhere

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 169 packets, 12844 bytes)pkts bytes target prot opt in out source destination

Chain CIP_INPUT (1 references)pkts bytes target prot opt in out source destination

Chain CIP_INPUT_p (1 references)

102 CIP Configuration and Management

pkts bytes target prot opt in out source destination----------------------------------------------------------------------

Termination Info: 0

“Allow Inbound SNMP TRAPS” (page 103) allows inbound SNMP TRAPS (port 162) from IPaddress 10.100.100.56 only.

Example 17 Allow Inbound SNMP TRAPS

This exampleclimcmd N1002581 climconfig iptables -N snmptrapclimcmd N1002581 climconfig iptables -A snmptrap ! -s 10.100.100.56 -j REJECTclimcmd N1002581 climconfig iptables -A CIP_INPUT -p tcp --dport 162 -j snmptrapclimcmd N1002581 climconfig iptables -A CIP_INPUT -p udp --dport 162 -j snmptrap

Following is the output for these commands:\MYSYS.$SYSTEM.STARTUP 3> CLIMCMD N1002581 climstatus -o tclimiptables Enabled: Yes

----------------------------------------------------------------------IPTABLES Configuration:Chain INPUT (policy ACCEPT 1 packets, 64 bytes)pkts bytes target prot opt in out source destination5652 1325K ACCEPT all -- any any N1002581 anywhere586K 228M ACCEPT all -- eth0 any anywhere anywhere14 725 CIP_INPUT all -- any any anywhere anywhere3 144 CIP_INPUT_p all -- any any anywhere anywhere

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 821 packets, 165K bytes)pkts bytes target prot opt in out source destination

Chain CIP_INPUT (1 references)pkts bytes target prot opt in out source destination10 528 snmptrap tcp -- any any anywhere anywhere tcp dpt:snmp-trap2 117 snmptrap udp -- any any anywhere anywhere udp dpt:snmp-trap

Chain CIP_INPUT_p (1 references)pkts bytes target prot opt in out source destination

Chain snmptrap (2 references)pkts bytes target prot opt in out source destination11 581 REJECT all -- any any !10.100.100.56 anywhere

reject-with icmp-port-unreachable

IP6TABLES Configuration:Chain INPUT (policy ACCEPT 0 packets, 0 bytes)pkts bytes target prot opt in out source destination16466 1599K ACCEPT all eth0 any anywhere anywhere

0 0 CIP_INPUT all any any anywhere anywhere0 0 CIP_INPUT_p all any any anywhere anywhere

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 6 packets, 456 bytes)pkts bytes target prot opt in out source destination

Chain CIP_INPUT (1 references)pkts bytes target prot opt in out source destination

Chain CIP_INPUT_p (1 references)pkts bytes target prot opt in out source destination----------------------------------------------------------------------

Termination Info: 0

Configuring CIP iptables/ip6tables (IP CIP) 103

Configuring Stream Control Transmission Protocol (SCTP) (IP and TelcoCIP)

CIP only supports one-to-one SCTP associations. To use SCTP, select IPPROTO_SCTP as theprotocol from your application, as follows:sd = socket(AF_INET, SOCK_STREAM, IPPROTO_SCTP);

Also ensure the PROTOCOL file contains an entry for SCTP. See the TCP/IP ProgrammingManual for more information about setting the socket option to use SCTP. See “PROTOCOLFile” (page 69) in this manual for procedures for adding SCTP to the PROTOCOL file.Additional SCTP support is available on the Telco CLIM. Please see OpenCall INS documentationfor more information.

Round-Robin FilteringFor background information about round-robin filtering, see the NonStop TCP/IPv6 Configurationand Management Manual.To use the round-robin feature you must explicitly configure it; the default configuration is fornon-round-robin. If you are using Providers, you must also define the appropriate transport-serviceprovider (CIPSAM process) in the same TACL session in which you define the filter key soincoming connections are distributed among application instances within the same Provider. Forapplication servers in a Provider environment to use the round-robin filtering feature, they mustshare both the round-robin filter-key DEFINE and the transport-service provider DEFINE.Enable round-robin filtering in CIP the same way you enable it in NonStop TCP/IPv6. Set theDEFINE to enable round-robin filtering on your server processes by using this ADD DEFINEcommand at the TACL prompt:ADD DEFINE =PTCPIP^FILTER^KEY, CLASS MAP, FILE file-name

You can limit the shared ports by adding one or both of these DEFINEs:ADD DEFINE =PTCPIP^FILTER^TCP^PORTS, FILE Pstartport.PendportADD DEFINE =PTCPIP^FILTER^UDP^PORTS, FILE Pstartport.Pendport

The startport and endport variables are integers specifying the allowable port range. The=PTCPIP^FILTER^TCP^PORTS key limits the shared TCP ports to the range defined instartportand endport. The =PTCPIP^FILTER^UDP^PORTS key limits the shared UDP portsto the range defined in startport and endport. Ports outside those ranges are not shared.You must always specify the =PTCPIP^FILTER^KEY DEFINE to enable round-robin filtering. Ifyou want to limit TCP and UDP ports, add the appropriate DEFINE after the=PTCPIP^FILTER^KEY DEFINE.In CIP, unlike in NonStop TCP/IPv6, you can have multiple application listeners in each processor.

NOTE: The round-robin feature is used only for listening (server) sockets and not client sockets.

Logging MessagesThe CLIM software logs error and some informational messages to /var/log/syslog as do thekernel and most other applications. Messages from the CLIM software always include thecomponent name. The messages are forwarded to the Event Management System (EMS) onthe NonStop host system.

Configuring IPv6 (IP CIP)This section provides an example of configuring IPv6.1. Configure IPv6 for the eth4 interfaces on each CLIM:

104 CIP Configuration and Management

> CLIMCMD n1002532 climconfig ip -add eth4-ipaddress 2001:0db8:0:0:0:0:1428:57ab -netmask 64

This interface is installed in network 2001:0db8:0:0/64.> CLIMCMD n1002531 climconfig ip -add eth4

-ipaddress 2001:0db8:0:0:0:0:1428:57ac -netmask 64

This interface is also in network 2001:0db8:0:0/64.2. Add a default IPv6 static route to the eth4 interfaces on each CLIM.

> CLIMCMD n1002532 route –add eth4 -default –gateway 2001:0db8:0:0:0:0:0:1> CLIMCMD n1002531 route –add eth4 -default –gateway 2001:0db8:0:0:0:0:0:1

Running Applications in Multiple Environments (IP CIP)NOTE: This section applies only to H-series and J-series RVUs.

You may run applications in the conventional TCP/IP, NonStop TCP/IPv6 and CIP environments.If you are using ATM or token-ring adapters your applications must use conventional TCP/IP. Ifyou are using Ethernet adapters, you can run your application in all environments.Conventional TCP/IP and NonStop TCP/IPv6 environments cannot share the same LIF but theycan share an Ethernet 4 ServerNet adapter (E4SA) or Gigabit Ethernet 4-port ServerNet adapter(G4SA) as those adapters have multiple LIFs. However, a Fast Ethernet ServerNet adapter(FESA) and a Gigabit Ethernet ServerNet adapter (GESA) have only one LIF, so they can onlysupport one environment. Only CIP can run on a CLIM.

Managing the Configuration PreservationThe system configuration database (CONFIG) is part of the NonStop Kernel subsystem. Theconventional TCP/IP subsystem (NonStop TCP/IP) does not participate in the system configurationdatabase, but NonStop TCP/IPv6 and CIP do (although their configuration databases are notcompatible). When you configure CIP for the first time, the SCF objects are added to the systemconfiguration database and any alterations to those objects also update the configuration of thoseobjects in the system configuration database. The system configuration database stores yoursubsystem configuration and can be accessed at any time to restore the subsystem to its lastconfiguration.The CIPMAN, when started, starts any subordinate objects that are stored in the systemconfiguration database.

Managing the Configuration Database on the NonStop Host SystemSave your configuration database before configuring CIP for the first time and record the nameand date of the saved database. This saved configuration database can be used if higher RVUsof CIP are incompatible with the CIP records residing in the system configuration database. If anew RVU of CIP is incompatible with the data stored in the configuration database, you canrestore the saved configuration database and reconfigure CIP. This SCF command saves thecurrent configuration database file in a new file located at $SYSTEM.ZYSCONF.CONF0104:> SAVE CONFIGURATI0N 01.04

The SCF SAVE command is documented in the SCFReferenceManual for J-Series and H-SeriesRVUs.

CAUTION: The configuration database stores all SCF commands that you issue to modifyyour CIP environment. If you use startup scripts to start your CIP subsystem, you should compareyour configuration database to those startup files to ensure that the startup files reflect theseadditional modifications to the environment. For more detailed procedures and specific migrationconsiderations, see Chapter 6: IP CIP Migration, Compatibility and Operational Differences.

Running Applications in Multiple Environments (IP CIP) 105

Managing Persistence on the NonStop Host SystemYou can add a generic process to the system configuration database and define that genericprocess in such a way that the persistence manager restarts the generic process whenever thegeneric process abends, is stopped through TACL, or the system is reloaded. To define thegeneric process this way, set the STARTMODE to SYSTEM.If you add the CIPMAN, CIPMON, or CIPSAM (IP CIP only) process as a generic processconfigured in this way, these processes start automatically upon system reload and subsequentlyrestores their stored and subordinate objects. Alternatively, when you add the CIPMAN, CIPMON,or CIPSAM process as a generic process to the system configuration database, you can chooseto configure it using STARTMODE MANUAL; this method requires that you start $ZZKRN.#ZZCIPmanually by using an SCF START command to the NonStop Kernel subsystem.The persistence manager restarts persistent generic processes whenever they are stopped bythe TACL STOP command (if the generic process is configured with STARTMODE SYSTEM) inaddition to starting those generic processes when the system is reloaded. Hence, if CIPMAN,CIPMON, or CIPSAM is a generic, persistent process (AUTORESTART > 0), any time you issuea TACL STOP command to the CIP subsystem, CIPMAN, CIPMON, or CIPSAM gets restartedby the persistence manager. To avoid this behavior and stop a persistent, generic, CIPMAN,CIPMON, or CIPSAM process, issue the ABORT command to the NonStop Kernel subsystemas in this example:> ABORT PROCESS $ZZKRN.#ZZCIP> ABORT PROCESS $ZZKRN.#CIPMON> ABORT PROCESS $ZZKRN.#CIPSAM

For more information about generic processes and the persistence manager, see the SCFReference Manual for the Kernel Subsystem.

Managing the CLIM Configuration PreservationHewlett Packard Enterprise recommends that you store CLIM configurations any time you changethem. Two TACL scripts are provided for this practice: one for backing up and one for restoringthe CLIM configuration.

NOTE: These operations can be executed only by a user who is either a member of the supergroup or a member of the Safeguard SECURITY-CLIM-ADMIN group. Unauthorized invocationsresult in a warning condition.

climbkup and climrstr Command Synopsis{climbkup | climrstr} {clim-name | ip-address | hostname}[file-name | volume | volume.subvolume | subvolume.filename | volume.subvolume.filename]

clim-nameIs the name of the CLIM to be backed up or restored.

ip-addressIs the IP address of the CLIM to be backed up or restored.

hostnameIs the hostname of the CLIM to be backed up or restored, without the subsystem qualifier.For example: C1002531.

file-nameIs the name of the file on the NonStop system in which the backup configuration is stored. Iffile-name is not specified, the default file name is BACKUPGZ.

subvolumeIs the name of the subvolume on the NonStop host system in which the backup configurationis stored. If the command specifies a CLIM name, the default subvolume is clim-name. Ifthe command specifies an IP address, the default subvolume is the current subvolume.

106 CIP Configuration and Management

volumeIs the name of the volume on the NonStop host system in which the backup configuration isstored. If the command specifies a subvolume and no volume, the default volume is $SYSTEM.If the command does not specify a volume or subvolume, the default location iscurrent-volume.subvolume.

climbkup and climrstr Considerations

• A CLIM configured with J06.17 RVU or later can be restored with a backup file taken fromany RVU from J06.08 to the RVU with which the CLIM is configured. For example, if theCLIM is configured with J06.17 RVU, any backup file taken from the RVUs J06.08 to J06.17can be used to restore on this CLIM.This is not true for a CLIM configured with pre-J06.17 RVUs. In that case, a backup fileshould be used only to restore on CLIMs that use the same RVU version as the backup file.For example, if the backup file was taken from the J06.09 RVU, it can only be used to restoreon a J06.09 CLIM. It may not be used to restore on a J06.10 CLIM.

• CLIMRSTR is not designed to be run on a CLIM that is in the STARTED state. Additionally,CLIMRSTR requires a reboot to be done after the restore. If a failover occurs during a restoreoperation such that the CLIM being restored takes over the other CLIM, the failoverinformation and network configuration of the CLIM that fails may not be correct on the failoverCLIM. Hewlett Packard Enterprise recommends using CLIMRSTR this way:1. Abort or stop the CLIM.2. Perform the restore operation.3. Start the CLIM.

ExamplesTo create a backup copy of the CLIM configuration on the $SYSTEM volume of the NonStophost system, use the CLIMBKUP clim-name TACL script. This command stores the configurationfiles of CLIM n1002531 in $SYSTEM.n1002531:tacl> CLIMBKUP n1002531

To restore your CLIM configuration files, use the CLIMRSTR clim-name TACL script. Forexample:tacl> CLIMRSTR n1002531

This command copies the configuration information that was saved during the backup operationon the NonStop host system from the $SYSTEM disk to the CLIM. Before invoking this command,the CLIM should be stopped or aborted. Upon completion of this command, the CLIM must berebooted to load the new configuration.The following table shows examples of behavior for the CLIMBKUP command and indicatesdifferences in behavior between different releases:

Behavior and File Backup Locationsfor Previous RVUs

Backup File and Location (L15.02,J06.06, H06.17 and later RVUs)

Example Command

Same$system.n1002531.backupgzCLIMBKUP N1002531

$current-vol.file-name.backupgz$system.n1002531.file-nameCLIMBKUP N1002531 file-name

UNSUPPORTED$system.subvolume.file-nameCLIMBKUP N1002531subvol.file-name

UNSUPPORTED$volume.n1002531.backupgzCLIMBKUP N1002531 $volume

Same$volume.subvolume.backupgzCLIMBKUP N1002531$volume.subvolume

Managing the Configuration Preservation 107

Behavior and File Backup Locationsfor Previous RVUs

Backup File and Location (L15.02,J06.06, H06.17 and later RVUs)

Example Command

UNSUPPORTED$volume.subvolume.fileCLIMBKUP N1002531$volume.subvolume.file-name

UNSUPPORTED$current-vol.current-subvol.backupgzCLIMBKUP 192.0.2.1

$current-vol.file-name.backupgz$system.current-subvol.file-nameCLIMBKUP 192.0.2.1 file-name

UNSUPPORTED$system.subvolume.file-nameCLIMBKUP 192.0.2.1subvolume.file-name

UNSUPPORTED$volume.current-subvol.backupgzCLIMBKUP 192.0.2.1 $volume

Same$volume.subvolume.backupgzCLIMBKUP 192.0.2.1$volume.subvolume

UNSUPPORTED$volume.subvolume.file-nameCLIMBKUP 192.0.2.1$volume.subvolume.file-name

Planning for Coexistence With Conventional TCP/IP (IP CIP Only)NOTE: This section applies only to H-series and J-series RVUs.

For the same application processes, one socket can be associated with the conventional NonStopTCP/IP subsystem, another with the NonStop TCP/IPv6 subsystem and another with the CIPsubsystem by programmatically changing the transport-service provider process.

NOTE: Parallel Library TCP/IP cannot coexist with CIP.

Stopping CIP

CAUTION: If you are not running an alternative TCP/IP subsystem, connect to CLCI asdescribed in “Restarting CIP on the NonStop Host System” (page 93).

To stop the CIP subsystem follow these procedures:

• “Preparing to Stop the CIP Subsystem”

• “Stopping CIP” (page 110)

Preparing to Stop the CIP Subsystem

Task Summary1. Ensure that you do not stop the TCP/IP process running your terminal.2. Check for applications using CIP.

Tasks: Preparing to Stop the CIP Subsystem1. Ensure that you do not stop the TCP/IP process that is running your home terminal.

a. Enter WHO at the TACL prompt:> WHO\HOME.$SYSTEM.SYSTEM 2> WHOHome terminal: $ZTNP1.#PTYPRABTACL process: \HOME.$Z34APrimary CPU: 2 (NSR-G)Default Segment File: $SYSTEM.#0000382Pages allocated: 24 Pages Maximum: 1024Bytes Used: 32820 (1%) Bytes Maximum: 2097152

Current volume: $SYSTEM.SYSTEMSaved volume: $SYSTEM.SYSTEM

108 CIP Configuration and Management

Userid: 255,255 Username: SUPER.SUPER Security: "AAAA"Logon name: SUPER.SUPER

The TELSERV process, $ZTNP1, is listed next to the HOME TERMINAL field. Makenote of the TELSERV process.

b. Check all TCP/IP processes to find the one that has your TELSERV process listed asan opener. This is the process that you do not want to shut down.> SCF> LISTDEV TCPIP

LDev Name PPID BPID Type RSize Pri Program204 $ZTC0 1,302 0,322 (48,0 ) 32000 200 \HOME.$SYSTEM.SYS07.TCPIP298 $TCPS3 3,278 (48,0 ) 57344 201 \HOME.$SYSTEM.SYS07.CIPSAM305 $TCPS1 1,341 (48,0 ) 57344 201 \HOME.$SYSTEM.SYS07.CIPSAM332 $ZTC01 0,301 1,389 (48,0 ) 57344 201 \HOME.$SYSTEM.SYS07.CIPSAM

c. Make a note of the CIPSAM processes (in this example, $TCPS3, $TCPS1, $ZTC01)so that you can shut them down in your shutdown procedures (see “Stopping CIP”(page 108).

d. Issue a LISTOPENS PROCESS $process-name on each process listed in the displayfor LISTDEV TCPIP until you find the process that is running the TACL prompt of yourhome terminal.The listing shows all the processes depending on $ZTC0:> LISTOPENS PROCESS $ZTC0Openers PPID BPID PLFN BLFN Protocol Lport$ZPRP1 1,304 4 0 TCP echo$ZPRP1 1,304 5 0 TCP finger$ZPRP1 1,304 6 0 TCP ftp$ZTN1 1,305 3 0 TCP telnet$ZTSM 0,307 22 0 TCP 980$ZCVP1 0,324 1 0 UDP 548$ZPMP1 1,266 2 0 UDP 111$ZPMP1 1,266 3 0 TCP 111$ZTNP1 1,305 4 0 TCP telnet$ZNET 0,21 2 0 #ZSPI *

In the Openers column, $ZTNP1 is an opener of the $ZTC0 process. In this example,$ZTNP1 is the TELSERV process running our home terminal so you must make sureyou do not shut it down. If the process running your home terminal is a CIPSAM process,use TELNET to connect to another TCP/IP process (conventional TCP/IP or NonStopTCP/IPv6) if one is available. If you are not running an alternative TCP/IP subsystem,connect to CLCI as described in “Restarting CIP on the NonStop Host System” (page 93).

2. Determine if any applications are using the CIPMONs and make a note of the applicationnames. Enter this command at the SCF prompt (a sample display follows this command):The listing shows all the processes depending on the CIP subsystem:> LISTOPENS MON $ZZCIP.*CIP Listopens MON \HOME.$ZZCIP.#ZPTM0

Openers PPID BPID PLFN BLFN Protocol Lport$ZPT0 0,295 5 0 TCP echo$ZPT0 0,295 6 0 TCP finger$ZPT0 0,295 7 0 TCP ftp$ZTN0 0,277 3 0 TCP telnet$ZTN0 0,277 5 0 TCP telnet$ZTN0 0,277 10 0 TCP telnet$ZTN0 0,277 7 0 TCP telnet$ZTN0 0,277 4 0 TCP telnet$ZTN0 0,277 8 0 TCP telnet$ZTN0 0,277 9 0 TCP telnet$ZTN0 0,277 6 0 TCP telnet$ZTN0 0,277 12 0 TCP telnet$Z07S 0,331 1 0 TCP ftp

Stopping CIP 109

In the above display, you would record all the opener processes: $ZPT0, $ZTN0, $ZTF0,$Z0KW, $Z0KX, $ZTN0, and $Z07S to be stopped.

Stopping CIPYou must stop the CIP subsystem from a conventional TCP/IP or NonStop TCP/IPv6 environmentor by using CLCI.Perform the tasks in “Preparing to Stop the CIP Subsystem” (page 108) before following theseprocedures.

Task Summary1. Stop all openers of the CIPMONs.2. Stop the CLIM.3. Stop the CIPSAM processes.4. Stop the PROVIDER objects.5. Stop the CIPMON processes.6. Stop the CIPMAN process.

110 CIP Configuration and Management

TasksEach of the following steps provides an example of the required command syntax. You may needto modify the exact command(s) you enter depending on your system configuration.1. Stop all openers of the CIPMONs.

NOTE: The LISTNER and TELSERV do not support the SCF ABORT command so youmust use the TACL STOP command to stop those processes.

Enter these commands at the TACL prompt:> STOP PROCESS $ZTN0> STOP PROCESS $LSN0

2. Stop the CLIMs by entering these SCF commands:> ABORT CLIM $ZZCIP.CLIM1, FORCED> ABORT CLIM $ZZCIP.CLIM2, FORCED

3. Stop the CIPSAM processes by entering these SCF commands:> ABORT PROCESS $ZZKRN.#ZTC0> ABORT PROCESS $ZZKRN.#ZTC1> ABORT PROCESS $ZZKRN.#ZTCP0> ABORT PROCESS $ZZKRN.#ZTCP1

4. Stop the PROVIDER objects by entering these SCF commands:> ABORT PROVIDER $ZZCIP.ZTC1, FORCED> ABORT PROVIDER $ZZCIP.ZTC0, FORCED> ABORT PROVIDER $ZZCIP.ZTCP0, FORCED> ABORT PROVIDER $ZZCIP.$ZTCP1, FORCED

5. Stop the CIPMON processes:> ABORT PROCESS $ZZKRN.#CIPMON

6. Stop the CIPMAN process:> ABORT PROCESS $ZZKRN.#ZZCIP

Monitoring the Network (IP CIP)To monitor your network, use these management tools:

• ping command

• Tracer utility

• Event Management System (EMS) Messages

NOTE: Before using the ping and tracer utilities, set the transport provider name to theappropriate CIPSAM process by using the ADD DEFINE TCPIP^PROCESS^NAME command.

Testing Access to Internet Network Hosts by Using the Ping Command(IP CIP)

The ping command accepts an IPv4 address, IPv6 address, or node name on the command line.For information about using the PING command, see the TCP/IP Applications and Utilities UserGuide.

Displaying a Datagram’s Route to a Network Host by Using TracerouteThe CLIMCMD {clim-name | ip-address} traceroute command displays the path taken by IPpackets on route to a network host. Use the CLIMCMD traceroute command to determine anyproblems that these packets might encounter. From each gateway system along the path, theCLIMCMD traceroute command tries to elicit an ICMP TIME_EXCEEDED message. From the

Monitoring the Network (IP CIP) 111

destination remote host, the CLIMCMD traceroute tries to elicit an ICMP_PORT_UNREACHABLEmessage.> CLIMCMD {clim-name | ip-address} traceroute

For more information see the traceroute man page by entering:> CLIMCMD {clim-name | ip-address} man traceroute

For more information on tracing, see “TRACE Commands” (page 278).

NOTE: Since traceroute is a network-sensitive command, the provider option be specified toCLIMCMD if the MULTIPROV option is ON. If the MULTIPROV attribute is set to ON, see theConsiderations section under prov(1p).

Event Management System (EMS) MessagesCIP generates event messages that are documented in the Operator Messages Manual.

NOTE: Messages with number 5227 are Linux messages: they have no immediate effect butmay indicate a problem on the CLIM. These are most likely informational events but may be usedby your service provider.Linux events are also sent to EMS.

Troubleshooting Tools and TipsSeveral tools are available to you for troubleshooting the CIP environment.

• SCF STATUS, DETAIL command for information about all or failing CIP objects

• SCF INFO, DETAIL command for information about all or failing CIP objects

• SCF LISTOPENS, DETAIL command for information about MON and PROV (IP CIP only)

• Linux tcpdump command to collect network tracing info.You also can use the CLIMCMD {clim-name | ip-address} clim command to abort, rebootand start the CLIM as well as to collect information. The CLIMCMD clim command isautomatically invoked when a CLIM stops because of issues in software. A snapshot file thatcaptures the CLIM debug files is created when a CLIM has failed due to a software or hardwareproblem or when a CLIM is aborted by the operator by using the CLIMCMD clim abortcommand. The snapshot is created as/home/debuginfo/clim-date-time.tgz. (date-timeis computed and replaced automatically). The snapshot includes the network configuration files,core files of the CLIM software components, and network configuration in the kernel. Thisautomatically created snapshot is available as of the J06.04 and H06.16 RVUs.However, in the following scenarios, the CLIM snapshot file is not created automatically:

• Configuration issues

• Failover issues

• Any issue that does not result in an intended or unintended stop of the CLIM or CLIM softwareIn these scenarios, create the CLIM snapshot manually by using the CLIMCMD command climwith the onlinedebug parameter on the problematic CLIM. The onlinedebug parametermanually generates and archives the snapshot file /home/debuginfo/clim-date-time.tgz.The onlinedebug parameter is available as of J06.05 and H06.16.Hewlett Packard Enterprise recommends sending this snapshot to your support provider foranalysis during troubleshooting.

CLIMCMD clim CommandCLIMCMD {clim-name | clim-ip-address} clim [abort | clearlog | reboot| start | onlinedebug | enable-policy-routing | disable-policy-routing | info ]

112 CIP Configuration and Management

abortAbort and dump all CLIM processes.

clearlogAllows a CLIM that has stopped trying to restart itself after reaching a retry threshold to beresumed. Should be followed by 'clim start'.

rebootReboots the CLIM, after taking a system memory dump.

startStarts the CLIM software. The CLIMMON, CONFSYNC, CLIMAGT, and CIPSSRV processesare started. Before starting the processes, CLIM related information is packaged into acompressed tar file for debugging purpose.

onlinedebugPackages clim-related information into a compressed tar file for debugging purposes.

enable-policy-routingEnables policy based routing, which ensures that the interface with the IP address bound bya socket will be used by that socket for outgoing network traffic, or that an interface with anIP address in the source address of the network packet is used for routing the packet.The default is enable-policy-routing.

disable-policy-routingDisables policy routing on the next CLIM reboot.

infoProvides clim configuration information. This command displays the current value/status ofconfigurable clim parameters.

clim Command ExamplesIf you need to reboot the CLIM, issue the CLIMCMD clim command with the clearlog and rebootoptions:> CLIMCMD n1002532 clim clearlog> CLIMCMD n1002532 clim reboot

Here is an example of using onlinedebug:> CLIMCMD n1002532 clim onlinedebug

Here is an example of checking policy routing settings:> CLIMCMD n1002581 clim infoSSH client version T9999H06_21Jun2010_comForte_SSH_0088policyRouting: EnabledTermination Info: 0

Event LoggingThe CIP subsystem generates NonStop host system reporting of CLIM issues. The report maybe in the form of error codes for cancelled commands or Event Management System (EMS)messages issued in the NonStop host system. See theOperator MessagesManual for informationabout events reported through the Event Management System (EMS).Use the CLIMCMD climstatus command to show the current CLIM state and to obtain statusinformation. See “Displaying System Information” (page 85), climstatus(1)

Troubleshooting Tools and Tips 113

NOTE: For pre-J06.08 and H06.19 RVUs, the time zone on the CLIM is GMT.For L15.02 and later L-series RVUs, J06.08 and later J-series RVUs, and H06.19 and laterH-series RVUs, the time on the CLIM is synchronized with the time on the NonStop host. Forthese RVUs, CLIMs run with the local time of the NonStop host.

During a failure, some information is automatically dumped, zipped and stored in the/home/debuginfo directory. Procedures for managing these files (copying, transferring, anddeleting) are similar to managing files collected by using tcpdump.

Linux Command Logging with cmd Command WrapperCertain native Linux commands issued via CLIMCMD, whether destructive or not, need to belogged into the system log. cmd is the command wrapper used for executing supported Linuxcommands on the CLIM and logs them into the system log. The user-entered command is loggedin its entirety to the system log, along with its arguments and information on the NonStop userwho issued the command. The result of the command, along with the CLIM user information, iswritten to the system log.

NOTE: This feature is supported for L15.02 and later L-series RVUs, J06.10 and later J-seriesRVUs, and H06.21 and later H-series RVUs only.

The syntax is:CLIMCMD {clim–name | ip-address } cmd command-name [arg1 arg2...argn]

command-nameSpecifies the Linux command to be executed.

arg1Specifies arguments for the command.

arg2Specifies arguments for the command.

This example shows the execution of a rm command using the command wrapper, and thecorresponding text logged into syslog:TACL> CLIMCMD C1002781 cmd rm file1NonStop User: SUPER.OPER CLIM User: root Command Succeeded: rm file1

Detecting Duplicate IP AddressesAs of RVU L15.02/J06.10/H06.21, CIP detects duplicate IPv4 addresses and MAC addressesin a subnet. When a duplicate IP or MAC Address is detected, EMS Event 5230 will be created.One of these alarms will be created:• Duplicate CLIM IP Address: A duplicate IP address has been detected within the same

network and a potential loss of network connectivity for sockets using that source IP addressmay occur. This alarm must be manually deleted.

• Duplicate CLIM MAC Address: A duplicate MAC address has been detected within the samenetwork and a potential loss of network connectivity through the interface with that MACaddress may occur. This alarm must be manually deleted.

Displaying Link SpeedUse ethtool to display the speed of a link. The syntax is:ethtool interface-name

where interface-name is eth1, eth2, etc. Example 18: Ethtool Link Speed Display shows thedisplay:

114 CIP Configuration and Management

Example 18 Ethtool Link Speed Display

ethtool eth1

Settings for eth1:Supported ports: [ TP ]Supported link modes: 10baseT/Half 10baseT/Full

100baseT/Half 100baseT/Full1000baseT/Full

Supports auto-negotiation: YesAdvertised link modes: 10baseT/Half 10baseT/Full

100baseT/Half 100baseT/Full1000baseT/Full

Advertised auto-negotiation: YesSpeed: 1000Mb/s <==== current SpeedDuplex: Full <--- current duplex modePort: Twisted PairPHYAD: 1Transceiver: internalAuto-negotiation: onSupports Wake-on: gWake-on: gLink detected: yes

Verifying the lunmgr Configuration of Two Storage CLIMsTo provide fault tolerance, two storage CLIMs must always be connected to the same enclosure.Each storage CLIM identifies the enclosures connected to it and assigns a base LUN to eachenclosure. This LUN must match between the two CLIMs. If they point to different enclosures onthe two CLIMs, neither path to the disks can be started. This can occur when one storage CLIMin a pair is replaced or a new enclosure is added or removed.To detect LUN configuration problems, use the CLIMSCMP tool. The syntax is:CLIMSCMP [/out out-file | /outv var-name] clim-name-1 clim-name-2

out out-fileDirects the display text to the file out-file.

outv var-nameDirects the display text to the variable var-name.

clim-name-1Specifies the name of the first storage CLIM to be compared.

clim-name-2Specifies the name of the second storage CLIM to be compared.

CLIMSCMP ConsiderationsCLMSCMP must be run by a user who is either a member of the Super group or a member ofthe Safeguard SECURITY-CLIM-ADMIN group.CLIMSCMP displays its completion status with a message completion code. Successful terminationresults in a completion code equal to zero. Error conditions are reported with a completion codegreater than zero; warning conditions are reported with a completion code less than zero, asfollows:

DescriptionCompletionCode

ESS LUN is connected through two different FC ports-6

Tape enclosure is configured but not connected to the CLIM-5

Troubleshooting Tools and Tips 115

DescriptionCompletionCode

Disk enclosure is configured on both the CLIMs, but is disconnected from one of the CLIMs-4

Disk enclosure is configured but not connected to the CLIM-3

Certain enclosures were found to be single ported-2

Success0

Syntax Error1

At least one of the specified CLIMs does not exist in the CIP subsystem2

At least one of the specified CLIMs is not of type STORAGE3

SSH connection could not be established to at least one of the specified CLIMs4

lunmgr –e command did not execute successfully on at least one of the specified CLIMs5

A mismatch was found while comparing the enclosure information of the two CLIMs6

CLIMSCMP is invoked by a user who is neither a member of the super group nor a member of theSafeguard SECURITY-CLIM-ADMIN group.

7

Disk enclosure is connected to both the CLIMs, but not configured on one of the CLIMs8

CLIMSCMP ExamplesBelow are examples of various configurations and the messages that CLIMSCMP returns.

• All enclosures are correctly configured and connected on both the CLIMs:TACL> CLIMSCMP S1002581 S1002582

The enclosure configurations of ‘S1002581’ and ‘S1002582’ CLIMs match.

Termination Info: 0

• Enclosures are configured and connected to both the CLIMs but there is a mismatch in theattribute values:TACL> CLIMSCMP S1002581 S1002582

Error: Mismatch in enclosure configurations of two CLIMs

lun type stable address serial # revisionS1002581: 200 1 enclosure 500143800045e880 SGA802004A 2.18S1002582: 200 1 enclosure 5001438000464500 SGA802004H 2.18

Termination Info: 6

• Disk enclosure is configured but not connected to the CLIM:TACL> CLIMSCMP S1002581 S1002582Warning: Enclosure disconnected from the CLIM 'N1002581'

lun type stable address serial # revision

S1002581: 200 1 enclosure 500143800045e880 --- ---

Termination Info: -3

• Disk enclosure is connected to both the CLIMs, but not configured on one of the CLIMs:TACL> CLIMSCMP S1002581 S1002582

Error: Enclosure configured on the CLIM ‘S1002581’ but not on the CLIM ‘S1002582’

lun type stable address serial # revisionS1002581: 200 1 enclosure 500143800045e880 SGA802004A 2.18

Termination Info: 8

116 CIP Configuration and Management

• Disk enclosure is configured on both the CLIMs, but is disconnected from one of the CLIMs:TACL> CLIMSCMP S1002581 S1002582

Warning: Enclosure disconnected from the CLIM 'S1002533'

lun type stable address serial # revisionS1002581: 300 1 enclosure 500143800046f780 SGA8040070 2.28S1002582: 300 1 enclosure 500143800046f780 ------- ------Termination Info: -4

• Tape enclosure is configured but not connected to the CLIM:TACL> CLIMSCMP S1002581 S1002582

Warning: Enclosure disconnected from the CLIM 'S1002581'

lun type stable address serial # revisionS1002582: 1 3 tape HP M8505 #HU10837WNA ------ ------

Termination Info: -5

• All enclosures are correctly configured and connected on both CLIMs. However, certainenclosures were found to be single ported:TACL> CLIMSCMP S1002581 S1002582

Warning: Following enclosures are single ported

lun type stable address serial # revisionS1002581: 200 1 enclosure 500143800045e880 SGA802004A 2.18

300 1 enclosure 500143800045e880 SGA802004A 2.18

S1002582: 400 1 enclosure 5001438000464500 SGA802004H 2.18500 1 enclosure 5001438000464500 SGA802004H 2.18

Termination Info: -2

• All the disk enclosures are correctly configured and connected on both the CLIMs. However,certain enclosures have ESS LUNs connected through two different FibreChannel ports:TACL> CLIMSCMP S1002551 S1002553

Warning: ESS LUN is connected through two different FC portslun type stable address serial # revision

S1002551: 1000 2 port 50060e8004289406 10388 5009S1002553: 1000 2 port 50060e8004289413 10388 5009

Warning: ESS LUN is connected through two different FC portslun type stable address serial # revision

S1002551: 1500 2 port 50060e8004289406 10388 5009S1002553: 2000 2 port 50060e8004289413 10388 5009

Termination Info: 0

CLIMSCMP MessagesError messages:

• Error: Only members of the SUPER group and Safeguard 'SECURITY-CLIM-ADMIN' groupcan execute 'CLIMSCMP'.

• Error: No value specified for the 'run-option' run-option.

• Error: Unsupported run-option 'run-option' specified.

• Error: 'clim-name' is not a configured CLIM.

• Error: 'clim-name-1' and 'clim-name-2' are not configured CLIMs.

• Error: SSH connection could not be established to the CLIM 'clim-name'.

Troubleshooting Tools and Tips 117

• Error: SSH connection could not be established to the CLIMs 'clim-name-1' and'clim-name-2'.

• Error: No CLIMs specified for the comparison of enclosures.

• Error: Only two CLIMs can be specified for the comparison of enclosures.

• Error: 'clim-name' is not a storage CLIM.

• Error: 'clim-name-1' and 'clim-name-2' are not storage CLIMs.

• Error: Could not successfully execute 'lunmgr -e' on the CLIM 'clim-name'.

• Error: Could not successfully execute 'lunmgr -e' on the CLIMs 'clim-name-1' and'clim-name-2'

Warning messages:

• Warning: Following enclosures are single ported.

Tip: Finding an Available UDP Port (IP CIP Only)Use the LISTOPENS MON command to display UDP ports in use. See the Expand Configurationand Management Manual for examples of finding available UDP ports.

CLIM and Host IncompatibilityIf the CLIM stays in the STARTING state, the CLIM software might be incompatible with the host.In this case, event 5228 is generated. To fix this, upgrade or downgrade the CLIM software tomatch the host RVU version. See Chapter 4 (page 126) for the CLIM upgrade procedure. Seethe applicable software installation and upgrade guide associated with your host system RVUfor procedures for downgrading the CLIM, or contact your service provider to perform thedowngrade.If the CLIM is in the STARTED state, you can determine the CLIM software version by using theOSM Service Connection or by entering:> SCF VERSION CLIM $ZZCIP.clim-name

You can also use the OSM Low-Level Link for H- and J-series.If the CLIM is not in the STARTED state, you can use the CLIM Management Tool or theCLIMCMD command with the Linux cat subcommand by entering:> climcmd clim-name cat /etc/vproc

NOTE: For H- and J-series, if not using OSM version T0682H02^ADP or later, you could usethe OSM Low-Level Link as an alternative to the CLIMCMD.

On L-series RVUs, whether or not the CLIM is in the STARTED state, you can use the CLIMManagement Tool to log onto the individual CLIM to display the current version.Multiple RVUs of a CLIM are allowed on a system as long as all CLIMs have CLIM RVUs thatare compatible with the host RVU.

Troubleshooting Network Applications Using TcpdumpTo trace and collect network traffic, you can use the Linux tcpdump command.

118 CIP Configuration and Management

NOTE: Since tcpdump is a network-sensitive command, the provider option be specified toCLIMCMD if the MULTIPROV option is ON. If the MULTIPROV attribute is set to ON, see theConsiderations section under prov(1p).

NOTE: In pre-J06.09/H06.20 RVUs, tcpdump can show large IP packets even when the jumboframe feature is not enabled on the CLIM interface. This can occur because Ethernet ports onthe IP and Telco CLIM were configured with TCP Segmentation Offloading (TSO) in hardware.TSO enables the network stack to buffer a large stream of data (much larger than the supportedMTU of the medium) to the NIC. The NIC hardware segments it into MSS-sized packets withproper sequence numbers. Because the packet-capture engine used by tcpdump operates abovethe interface layer, the packet-capture engine captures the packet prior to the NIC-hardwaresegmentation. This behavior results in packets captured by tcpdump showing a larger packetsize than the supported MTU. Packets passively captured on the wire (using a mirrored port onthe switch) would show the correct packet size.

Running tcpdump can impact system performance. These suggestions can reduce this impact:1. Run tcpdump with -n to avoid name resolution.2. Save the traces to a file with -w. This option causes the raw packets to be saved instead of

being parsed and printed in real time.3. Do not run tcpdump with -i any.4. Limit the capture size to the minimum when possible. Specifying -s 1500 can increase the

performance impact.

Running tcpdumpHere are steps for collecting traces by using tcpdump:1. Create a trace directory on the CLIM2. Identify all the TCP/IP attributes required to focus on only the data to be traced.

• Use the -n flag to avoid reverse look up of IP addresses

• See the tcpdump man page for details.3. Capture the trace data and save to the trace file in bin format.

NOTE: You must be logged on as a super group user to run tcpdump. Best practice is tostore the trace file somewhere under the /home directory on the CLIM.

4. Move the collected trace file to the NonStop host or the NonStop console.5. Remove the trace file and trace directory from the CLIM.6. Decode the trace file.

Example 19 Using tcpdump

1. Create a trace directory on the CLIM.Use climcmd clim-name mkdir tracedir

> == Create a temporary directory on the CLIM>>climcmd n1002582 mkdir /home/mylogcomForte SSH client version T999H06_14Oct2008_comForte_SSH_0081Termination Info: 0> == List the directory and files>> climcmd N1002582 ls -lrt /home/mylogcomForte SSH client version T999H06_14Oct2008_comForte_SSH_0081total 0

2. Capture the data.

Troubleshooting Tools and Tips 119

a. For CLIMs with MULTIPROV OFF:Use climcmd clim-name man tcpdump for information.

Press the break key on Mr-Win6530 to stop the tracing.> == run tcpdump (must be super group user) and save> == the output goes to a binary file, that can be> == decoded by other tools or tcpdump itself> == Look for traffic from/to host 192.0.2.1> climcmd N1002582 tcpdump -n -i any -w /home/mylog/telnet-data-to-10 host 192.0.2.1

comForte SSH client version T999H06_14Oct2008_comForte_SSH_0081

tcpdump: WARNING: Promiscuous mode not supported on the "any" devicetcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes

***CLIMCMD: Script terminated at user request>> == Stop tracing by the <break> key

b. For CLIMs with MULTIPROV ON:Use climcmd clim-name man tcpdump for information.

Press the break key on Mr-Win6530 to stop the tracing.> == run tcpdump (must be super group user) and save> == the output goes to a binary file, that can be> == decoded by other tools or tcpdump itself> == Look for traffic from/to host 192.0.2.1> climcmd N1002582 –provider ZTC0 tcpdump -n -i any -w /home/mylog/telnet-data-to-10 host 192.0.2.1

comForte SSH client version T999H06_14Oct2008_comForte_SSH_0081

tcpdump: WARNING: Promiscuous mode not supported on the "any" devicetcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes

***CLIMCMD: Script terminated at user request>> == Stop tracing by the <break> key

3. Decode the trace file.Use climcmd clim-name ls —lrt tracedir to list the trace file.Use climcmd clim-name tcpdump -r tracefile to decode the file.> == Check the trace output file>> climcmd N1002582 ls -lrt /home/mylogcomForte SSH client version T999H06_14Oct2008_comForte_SSH_0081

total 124-rw-r--r-- 1 root root 122880 2009-01-29 01:01 telnet-data-to-10Termination Info: 0>> == Decode the tracefule using tcpdump -r>> climcmd N1002582 tcpdump -r /home/mylog/telnet*comForte SSH client version T999H06_14Oct2008_comForte_SSH_0081reading from file /home/mylog/telnet-data-to-10, link-type LINUX_SSL (Linux cooked)00:48:50:339967 IP N1002582.ssh > 192.0.2.1.44632: P 1:197(196) ack 0 win 3499 <nop,nop,timestamp 135991971 86225567>

4. Copy the trace file to the NonStop host.

NOTE: This SFTP syntax can be used for L15.02/J06.06/H06.17 and later RVUs only.

Use sftp -S $zssp0 user@ip-address:trace-dir/trace-file target-file> == Move the file from the CLIM to the host>> sftp -S $zssp0 user@192.0.2.1:/home/mylog/lnet-data-to-10 tcpd10comForte SSH client version T999H06_14Oct2008_comForte_SSH_0081Connecting to 192.0.2.1...Fetching /home/mylog/telnet-data-to-10 to tcpd10

120 CIP Configuration and Management

----------------- -------- --- ------ ------Filename BytesNow % Bytes/s Remaining----------------- -------- --- ------ ------/home/mylog/telnet-data-to-10 0 0% 0.0KB --:------------------- -------- --- ------ ------Filename BytesNow % Bytes/s TimeSpent----------------- -------- --- ------ ------/home/mylog/telnet-data-to-10 192KB 106% 0.0KB 00:00>> fileinfo tcpd10

$MYSYS.MYSUBCODE EOF LAST MODIFIED OWNER RWEP PExt SExt

TCPD10 0 196608 29JAN2009 0:21 255,255 NUNU 14 112>

For L15.02/J06.10/H06.21 and later RVUs only, you can use the CLSFTP script. The syntaxis:CLSFTP {clim-name | clim-ip-address} [sftp commands]

For example:> CLSFTP n1002532 get file2

In interactive mode:TACL> CLSFTP n1002532CLSFTP - T0834 - version 1.2, 29-SEP-2009

Run sftp in interactive mode.using $ZSSP0...

comForte SFTP client version T9999H06_18Dec2009_comF ...Connecting to 192.168.199.242 via SSH2 process $ZSSP0 ...sftp> get file1sftp> exit

5. Delete the trace file.Use climcmd clim-name rm /trace-dir/trace-file

Then use climcmd clim-name rmdir /trace-dir

> == Delete the file on the CLIM>> climcmd N1002582 rm /home/mylog/telnet-data-to-10comForte SSH client version T999H06_14Oct2008_comForte_SSH_0081Termination Info: 0> climcmd N1002582 ls -lrt /home/mylogcomForte SSH client version T999H06_14Oct2008_comForte_SSH_0081total 0Termination Info: 0> == Delete the directory used for tcpdump>> climcmd N1002582 rmdir /home/mylogcomForte SSH client version T999H06_14Oct2008_comForte_SSH_0081Temination Info: 0

Mapping CLIM NameLog files are collected to the location specified when performing the action “Set Location for CLIMLog Collection” on the CLIMs object in the OSM Service Connection. The default location is$system.zservice. The clim-name is mapped to a two character ID as shown:$system.zservice.zclimid file shows the CLIM nameto ID mapping – in the listing below N1002582 is mapped to 04.\BLADQA3.$SYSTEM.ZSERVICE 25> fup copy zclimid#ZCLIMID: Maps CLIM name to unique two character IDN1002571 01N1002573 02N1002581 03N1002582 04N1002583 05

Troubleshooting Tools and Tips 121

S1002531 06S1002533 078 RECORDS TRANSFERRED

Files named ‘ZCL04*’ belong to CLIM debug files from CLIM N1002582.There will be two sets of files, one set with ‘D’ (for data) in thefilename which contains the PAK-file with the CLIM log/crash files,and the other set with ‘L’ in the filename which contains the logof the user/OSM action of transferring the data from the CLIM file.Both of these files, with the timestamp that is relevant to the probleminstance must be collected for analyzing a CLIM problem.\BLADQA3.$SYSTEM.ZSERVICE 26> fileinfo zcl04*

$SYSTEM.ZSERVICE

CODE EOF LAST MODIFIED OWNER RWEP PExt SExtZCL04D01 1729 21759572 18MAY2011 11:29 255,255 CCCC 84 84ZCL04L01 101 28600 18MAY2011 11:29 255,255 CCCC 14 14ZCL04L02 101 2048 19MAY2011 14:35 255,255 CCCC 14 14\BLADQA3.$SYSTEM.ZSERVICE 27>

For more details, see “Collecting Data for CLIM Issues” (page 200).

Setting Up Multiple Providers per CLIMEffective with the H06.25/J06.14 RVU, a CLIM can be associated with multiple data providers ifthe MULTIPROV attribute of the CLIM object is set to ON (enabled). The default is OFF (disabled),which configures the CLIM to use pre-Multiple Providers per CLIM behavior and use the soleprovider specified by the PROVIDER attribute of the CLIM object.Each CLIM contains configuration information indicating whether the Multiple Providers per CLIMfunctionality is enabled or disabled.When you enable the Multiple Providers per CLIM functionality, you associate a data providerwith one or more data interfaces, which can be changed by using the climconfig command. Seeclimconfig.prov(1) for a description on how to add, delete, and obtain information on a provider.See also these SCF commands and their guidelines for more information: “ADD CLIM” (page 220)and “ALTER CLIM” (page 226). All the CLIMCMD commands and the SCF commands are describedunder “CLIMCMD and CLIMCMD climconfig Commands (Man Pages)” (page 294) and “SCFReference for CIP” (page 210).

Enabling the MULTIPROV AttributeTo enable MULTIPROV for an existing CLIM object, follow these steps:

Example 20 Enabling MULTIPROV

1. To turn the MULTIPROV feature on:> SCF ALTER CLIM $ZZCIP.clim-name, MULTIPROV ON

2. To verify that the MULTIPROV feature is on:> CLIMCMD clim-name climstatus -o l

3. To add new providers:> CLIMCMD clim-name climconfig prov -add prov-name

NOTE: An SCF PROVIDER object must also exist or be added.

Disabling the MULTIPROV AttributeTo disable MULTIPROV for an existing CLIM object, follow these steps:

122 CIP Configuration and Management

Example 21 Disabling MULTIPROV

1. Issue this command for each CLIM to display a list of providers for that CLIM:> CLIMCMD clim-name climconfig prov -info all

2. Delete the unneeded providers and the objects using each of these providers.a. Issue these commands to delete the objects used by the providers:

> CLIMCMD clim-name ifstop interface-name> CLIMCMD clim-name climconfig interface —delete interface-name

b. Issue this command to delete the providers:> CLIMCMD clim-name climconfig prov —delete prov-name

NOTE: When you delete a provider, you'll receive a message stating: Deleting theProvider prov-namewill delete the IPSec configurations and IPtables rules associatedwith it. Continue? (yes/[no])?

3. Verify that each unneeded provider is deleted and check the status of each CLIM:> CLIMCMD clim-name climconfig prov —info all> CLIMCMD clim-name climstatus —o l

4. Turn the MULTIPROV feature OFF:> SCF ALTER CLIM $ZZCIP.clim-name, MULTIPROV OFF, PROVIDER prov-name

NOTE: For this command to be successful, network resources on the CLIM must onlybelong to the provider associated with the CLIM object.

5. Recheck the status of each CLIM to verify that the CLIM's status has been changed toMULTIPROV OFF.> CLIMCMD clim-name climstatus —o l

Changing Providers, Adding and Starting a CLIM (IP and Telco Only)CLIMs that are configured with the MULTIPROV feature OFF can participate in only a singleIPDATA provider, as described under “CLIMs with MULTIPROV OFF” (page 123).CLIMs that are configured with the MULTIPROV feature ON can have any unassigned resourcesassigned to new providers without affecting any existing provider configuration, as describedunder “CLIMs with MULTIPROV ON” (page 124).Two maintenance Providers on two IP or Telco CLIMs are configured by default for the system(see“Maintenance Provider” (page 23) for more information). If you need to add maintenanceProviders for the system, use these SCF commands:> ADD PROVIDER $ZZCIP.ZTCP0, TYPE MAINTENANCE, CLIM clim-name1, IPADDRESS ip-addr1> ADD PROVIDER $ZZCIP.ZTCP1, TYPE MAINTENANCE, CLIM clim-name2, IPADDRESS ip-addr2

CLIMs with MULTIPROV OFFTo change the provider to which a CLIM with MULTIPROV OFF belongs, you stop, alter, andstart it.

Example 22 Changing Providers

1. Stop the CLIM by using the SCF ABORT CLIM command:> ABORT CLIM $ZZCIP.clim-name, FORCE

2. Change the CLIM's provider by using the SCF ALTER command:> ALTER CLIM $ZZCIP.clim-name, PROVIDER prov-name

3. Start the CLIM by using the SCF START command:

Changing Providers, Adding and Starting a CLIM (IP and Telco Only) 123

> START CLIM $ZZCIP.clim-name> START PROVIDER $ZZCIP.prov-name

CLIMs with MULTIPROV ONTo change the providers that a CLIM provides services to, you discover the current usage of theCLIM, free any resources that might be in use by pre-existing providers, and configure the newprovider.

Example 23 Changing Providers or Adding New Providers

1. Determine what providers exist on the CLIM:> CLIMCMD clim-name climconfig prov -info all

2. Determine what interfaces are configured on the CLIM:> SCF STATUS CLIM $ZZCIP.clim-name, DETAIL

3. Delete any interfaces that are no longer needed:

CAUTION: Deleting interfaces will also delete IP addresses and routes.

> CLIMCMD clim-name ifstop interface-name

> CLIMCMD clim-name climconfig interface -delete interface-name

4. Delete any unused providers on the CLIM:

CAUTION: Deleting providers will also delete iptables rules and ipsec objects. Objectsinclude sp, sa, psk, remote, iptables and ip6tables.

> CLIMCMD clim-name climconfig prov -delete prov-name

5. Add new providers, as necessary:> SCF ADD PROCESS $ZZKRN.process-name, PROGRAM CIPSAM, NAME $process-name> SCF ADD PROVIDER $ZZCIP.prov-name, TPNAME process-name> SCF START PROCESS $ZZKRN.process-name> SCF START PROVIDER $ZZCIP.prov-name

For more options on adding the provider, see ALTER CLIM Guidelines (page 226).6. Register the provider on the CLIM:

> CLIMCMD clim-name climconfig prov -add prov-name

7. Configure unused interfaces in the new provider:> CLIMCMD clim-name climconfig interface -add interface-name -prov prov-name

8. Configure the objects for the new provider.> CLIMCMD clim-name climconfig ip -add interface-name-ipaddress ip-address netmask 255.255.255.0

Refer to the climconfig prov command and the other commands for objects, such as sp, sa,psk, remote, iptables and ip6tables, under “Climconfig (Man Pages)” (page 307).

9. Delete any unused providers on the NonStop system by issuing the following SCF commands:a. Verify that the provider is unused:

> SCF INFO PROVIDER $ZZCIP.prov-name, DETAIL

b. Delete the unused providers:> SCF STOP PROVIDER $ZZCIP.prov-name> SCF ABORT PROCESS $ZZKRN.process-name> SCF DELETE PROCESS $ZZKRN.process-name> SCF DELETE PROVIDER $ZZCIP.prov-name

124 CIP Configuration and Management

For detailed information on how to use these commands, refer to “SCF Reference for CIP”(page 210) and “CLIMCMD and CLIMCMD climconfig Commands (Man Pages)” (page 294).

Changing Providers, Adding and Starting a CLIM (IP and Telco Only) 125

4 Upgrading CIPThis chapter provides procedures for online upgrading of CIP on the host and both online anddown system methods for upgrading CLIM software and firmware (see “Upgrading CLIM Softwareand Firmware” (page 128)). This chapter also provides information on falling back to previousTCP/IP subsystems and provides a pointer to information on falling back to previous CLIMversions if needed.Each procedure stands alone. If you are performing an RVU upgrade, you are likely to need toupgrade CIP on the NonStop host and on the CLIM; however, you also can upgrade CLIMsoftware independently. If you have to update CIP on NonStop and the CLIM using an onlineprocedure, the CLIM must be done first.Updating CLIM firmware is independent of CLIM software upgrades. Falling back to a previousCLIM version, independently from an RVU fallback, should rarely be required.

Performing an Online Upgrade of the CIP Subsystem on the NonStopHost

For Telco applications, Hewlett Packard Enterprise recommends that you:1. Move traffic from the node.2. Stop the DPA and HLR application processes on the node.3. Shut down the INS node before performing an online CIP upgrade.4. Start the INS node, DPA, and HLR applications.5. Move traffic back to the node, starting with one link or linkset, and test traffic before moving

all the traffic back.For information about INS, see the CMS documents Guide to Operations and Maintenance forHPE OpenCall Intelligent Network Serve and the Installation Guide For HPE OpenCall IntelligentNetwork Server.

NOTE: You cannot perform an online upgrade of the CIP subsystem to J06.08/H06.19 or laterRVUs from an RVU previous to that. A system load is required for these upgrades.

Replace CIPMON (Only)TCP/IP socket connections are lost during this procedure. Storage paths are unaffected by thisprocedure.For each processor:1. Rename the existing CIPMON and library files by using the TACL commands:

> RENAME $SYSTEM.SYSnn.CIPMON, $SYSTEM.SYSnn.CIPMONx> RENAME $SYSTEM.SYSnn.ZCIPDLL, $SYSTEM.SYSnn.ZCIPDLLx> RENAME $SYSTEM.SYSnn.ZCIPMDLL, $SYSTEM.SYSnn.ZCIPMDLx

2. Install the new CIPMON as $SYSTEM.SYSnn.CIPMON.3. Install the new CIP library as $SYSTM.SYSnn.ZCIPDLL.4. Install the new Measure interface to CIP as $SYSTM.SYSnn.ZCIPMDLL.5. Stop the measure subsystem.6. Abort the CIPMON processes one processor at a time by using the SCF command:

CAUTION: IP CLIM connectivity is temporarily lost, which can affect this operation. Forexample, if you are connected through $ZTC0 and stop the CIPMON process in the processorwhere $ZTC0 is running, you lose connectivity. Options are to reconnect through $ZTC1after this operation or connect through $ZTC1 and perform this operation on the processorwhere $ZTC0 is running then, once the CIPMON is running in that processor, connect through$ZTC0 and perform the operation on the processor running $ZTC1.

126 Upgrading CIP

> ABORT MON $ZZCIP.ZCMprocessor-numberOpen connections still exist, okay to continue? Y

7. The CIPMON processes are restarted automatically. Check to make sure each one is upbefore doing the next one.

8. Restart the measure subsystem.

Replace CIPMAN (Only)TCP/IP socket connections are not lost during this procedure. Storage paths are also unaffectedby this procedure.1. Rename the existing CIPMAN file by using the TACL command:

> RENAME $SYSTEM.SYSnn.CIPMAN, $SYSTEM.SYSnn.CIPMANx

2. Install the new CIPMAN as $SYSTEM.SYSnn.CIPMAN.3. Stop the CIPMAN process by using the SCF command:

> ABORT PROCESS $ZZKRN.#ZZCIP

4. Restart the CIPMAN process by using the SCF command:> START PROCESS $ZZKRN.#ZZCIP

Replace CIPMAN and CIPMON SimultaneouslyThis procedure is required if there is a requisite between the new CIPMAN (T0690) and CIPMON(T0694) called out in the respective softdocs.

CAUTION: TCP/IP socket connections are lost during this procedure. Storage paths areunaffected by this procedure.

1. Rename the existing CIPMON and library files by using the TACL commands:> RENAME $SYSTEM.SYSnn.CIPMON, $SYSTEM.SYSnn.CIPMONx

> RENAME $SYSTEM.SYSnn.ZCIPDLL, $SYSTEM.SYSnn.ZCIPDLLx> RENAME $SYSTEM.SYSnn.ZCIPMDLL, $SYSTEM.SYSnn.ZCIPMDLx

2. Rename the existing CIPMAN file by using the TACL command:> RENAME $SYSTEM.SYSnn.CIPMAN, $SYSTEM.SYSnn.CIPMANx

3. Install the new CIPMON as $SYSTEM.SYSnn.CIPMON.4. Install the new CIP library as $SYSTM.SYSnn.ZCIPDLL.5. Install the new Measure interface to CIP as $SYSTM.SYSnn.ZCIPMDLL.6. Install the new CIPMAN as $SYSTEM.SYSnn.CIPMAN.7. Stop the Measure subsystem.8. Abort the CIPMON processes on all CPUs (see CAUTION below):

> ABORT PROCESS $ZZKRN.CIPMON

9. Wait for the CIPMON processes to stop (approximately 15 to 30 seconds):file $SYSTEM.SYSnn.CIPMONx is no longer Open.

10. Stop the CIPMAN process by using the SCF command:> ABORT PROCESS $ZZKRN.#ZZCIP

11. Restart the CIPMAN process by using the SCF command:> START PROCESS $ZZKRN.#ZZCIP

12. Restart the CIPMON processes by using the SCF command:

Performing an Online Upgrade of the CIP Subsystem on the NonStop Host 127

> START PROCESS $ZZKRN.CIPMON

13. Restart the Measure subsystem.

CAUTION: You must connect to CLCI as described in “Restarting CIP on the NonStop HostSystem” (page 93).

Replace CIPSAMTCP/IP socket connections are lost during this procedure. Storage paths are unaffected by thisprocedure.For CIPSAM processes configured under the Persistence Manager, use the SCF ABORT andSTART PROCESS commands to the Kernel subsystem, for example: > ABORT PROCESS$ZZKRN.name and > START PROCESS $ZZKRN.name.1. Rename the existing CIPSAM file by using the TACL command:

> RENAME $SYSTEM.SYSnn.CIPSAM, $SYSTEM.SYSnn.CIPSAMx

2. Install the new CIPSAM as $SYSTEM.SYSnn.CIPSAM.3. List all CIPSAM and other TCP/IP processes by using the SCF LISTDEV command.4. If the OSM maintenance processes are configured on CLIMs, stop them by using the SCF

Abort command on the maintenance Providers. For example:> ABORT PROCESS $ZTCP0> ABORT PROCESS $ZTCP1

5. Check to ensure the maintenance processes are stopped by using the SCF LISTDEVcommand. If the processes do not appear in the display, they are stopped. For example:> LISTDEV TCPIP

6. Start the OSM maintenance processes by using the SCF START command to the Kernelsubsystem. For example:> START PROCESS $ZZKRN.ZTCP0> START PROCESS $ZZKRN.ZTCP1

7. Stop and restart the remaining CIPSAM processes by :1. Using the SCF ABORT command to the Kernel ($ZZKRN) or to the CIP subsystem

($ZZCIP).2. Checking that the CIPSAM processes are stopped by using the SCF LISTDEV command.3. Restarting the CIPSAM processes by using the SCF START command to the Kernel

or CIP subsystem.

Upgrading CLIM Software and FirmwareThe CLIM Management Tool, available on NonStop System Console Installer DVD Update 23and later, replaces the Down System CLIM Firmware Update Tool in OSM Console Tools T0634H06 ABJ and later. The CLIM Management Tool makes it possible to update CLIM software andthe firmware for all CLIM components in a single action, while the NonStop system is not running.Because the updates run on multiple CLIMs at the same time, the process is much more efficient.Thus, this method is prescribed during planned system down time, such as during RVU upgrades.

• For L-series, the CLIM Management Tool is required to perform CLIM software updates (upor down system) and down system CLIM firmware updates, as neither the OSM Low-LevelLink nor the Down System CLIM Firmware Update Tool is supported.

• For H- and J-series, the CLIM Management Tool can be used as described above providedOSM version T0682H02^ADP or later is used. If not, it can be used for down system CLIMfirmware updates, just as the Down System CLIM Firmware Update Tool it replaced, but notfor updating CLIM software. The OSM Low-Level Link must be used for CLIM software

128 Upgrading CIP

updates. The Down System CLIM Firmware Update Tool is still supported for H- and J-series,if the CLIM Management Tool is not installed.

As a result of these options, this chapter contains separate procedures for:

• “Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic”(page 129)

• “Upgrading CLIM Software or Firmware While the System is Down ” (page 160)

CAUTION: Before attempting the procedures in this section:• Ensure that the NonStop console has at least 2 GB memory (4 GB is recommended), before

upgrading your CLIMs.• Be sure that the CLIM software is compatible with the host RVU you are currently running.

For more information, see “CLIM and Host Incompatibility” (page 118).• Fix all alarms and bad attribute values in the OSM Service Connection before upgrading

CLIMs.• “Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic”

(page 129) requires careful planning (as described in this section) and execution to ensurethe storage and networking resources that support your environment are protected.

• “Upgrading CLIM Software or Firmware While the System is Down ” (page 160) involveshaving the requisite software and advance preparation (as described in this section) beforebring the system down.

• For H- or J-series, ensure the version of OSM Low-Level Link has been updated to therequisite version as specified in the T0853 softdoc.

Upgrading CLIM Software and Firmware While Maintaining Network orStorage Traffic

This section describes the procedures for upgrading CLIM software and firmware when you arenot planning to bring the system down. It consists of two parts:

• “Upgrading CLIM Software with the System Running” (page 130)

• “Upgrading CLIM Firmware with the System Running” (page 144)If you plan to bring down the system, as needed during an RVU upgrade, see “Upgrading CLIMSoftware or Firmware While the System is Down ” (page 160) for a faster, more efficient process.

TIP: If you are updating a system with SPRs, without a SUT update, and if you need to performCLIM software updates, you can do updates in this order and perform only one reboot:1. Apply the SPRs.2. Update firmware using OSM Service Connection Multi-Resource Actions dialog box (see

“Upgrading CLIM Firmware with the System Running” (page 144)) but do not reboot theCLIMs.

3. Update CLIM software (see “Updating CLIM Software Using the OSM Low-Level Link (H-and J-Series RVUs)” (page 140)) including the reboot of the CLIM.

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 129

Upgrading CLIM Software with the System RunningYou can perform CLIM software updates either one CLIM at a time or multiple CLIMs in parallel.If you are comfortable performing more than one CLIM upgrade at a time, additional considerationsfor group updates are provided in:

• “Upgrading Multiple CLIMs in Parallel” (page 155)

• “Upgrading Multiple CLIMs of Different Types” (page 160)

NOTE:• Performing multiple CLIM updates in parallel is optional and helps in reducing the total time

for upgrading all the CLIMs.• CLIM software updates (excluding reboot) take about 10-15 minutes.

The steps for upgrading are:1. “Enabling the FTP Port on the Console” (page 130)2. “Backing up the CLIM Configuration Files” (page 130)3. “Installing the new CLIM Software on the System Console” (page 130)4. “Identifying the Target Software” (page 131)5. “Creating a CLIM Upgrade Form” (page 131)6. Depending on your configuration, performing one or more of:

• “Upgrading Storage CLIMs” (page 132)

• “Upgrading IP and IB CLIMs” (page 136)

• “Upgrading Telco CLIMs” (page 138)

Enabling the FTP Port on the ConsoleBefore upgrading the CLIM software, enable the FTP port on the console. The way you performthis step depends on whether or not a firewall package is configured on the console. If a firewallpackage is not configured, use the standard Windows method to enable this port. If a firewallpackage is configured, see the system console operations personnel.

Backing up the CLIM Configuration FilesBefore upgrading the CLIM software, save your configuration files onto the NonStop host byusing the Backup Tool described in “Managing the CLIM Configuration Preservation” (page 106).The Backup Tool archives configuration files, log files, and trace files.

Installing the new CLIM Software on the System ConsoleFor the Telco CLIM, if you have an INS software upgrade DVD, follow the same instructions forthat DVD.

NOTE: The Telco CLIM may require both a CLIM software upgrade and INS software upgrade.The INS software upgrade does not include CLIM software upgrade.

CLIM software is delivered on a DVD or, for L15.02, J06.08 and H06.19 and later RVUs, as adownloadable file from Scout for NonStop Servers. You must load the software from the CLIMDVD Installation Software or from NonStop Scout onto the system console, then install it fromthe system console onto the CLIM.For the CLIM DVD:1. Insert the CLIM DVD into the CD/DVD drive on the system console.2. In Windows, click the CD/DVD drive symbol.

130 Upgrading CIP

3. Click the setup icon, then follow the prompts to load the CLIM software on the systemconsole.

Scout for NonStop Servers:1. Follow the download procedures provided in Scout for installing a self-extracting SPR (.exe)

on T0853.

NOTE: Downloading the file takes approximately 15 minutes. The process does not providea status of the operation during this time. Please wait until it completes.

2. Click the setup icon, then follow the prompts to load the CLIM software on the systemconsole.

NOTE: The download from Scout of T0853 provides all necessary components.

Identifying the Target Software1. List the existing software versions for all CLIMs by using the SCF VERSION CLIM $ZZCIP.*

command.2. List the available software version for the CLIM available on the NonStop console. For an

example of using OSM to determine the CLIM software versions on the console, see“Updating CLIM Software Using the OSM Low-Level Link (H- and J-Series RVUs)” (page 140)or “Updating Individual CLIM Software Using the CLIM Management Tool ” (page 142).

3. Make note of the software versions to install on the CLIMs from the console or, if furtherupdates are needed, from Scout for NonStop Servers.

Creating a CLIM Upgrade FormPrepare a form to keep track of your CLIMs. Table 8: Sample CLIM upgrade form, all types showsan example:

Table 8 Sample CLIM upgrade form, all types

Normaloperationsresumed?

CLIMrestarted?

Upgradedone?

Switchandabortdone?

B/upCLIMstarted?B/up CLIM name

Storagepath

RunningMaintProv?If yes,

TypeCLIM namewhichone?

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 131

Table 8 Sample CLIM upgrade form, all types (continued)

Normaloperationsresumed?

CLIMrestarted?

Upgradedone?

Switchandabortdone?

B/upCLIMstarted?B/up CLIM name

Storagepath

RunningMaintProv?If yes,whichone?TypeCLIM name

Upgrading Storage CLIMs

1. Prepare the Storage CLIM for Upgrade (skip if the host system is not running)a. List the CLIMs.

> SCF INFO CLIM $ZZCIP.*Name Mode Location ConnPts ProviderN1002541 IP (100 ,2 ,5 ,4 ,1 ) 1 CSAM2N1002542 IP (100 ,2 ,5 ,4 ,2 ) 1 ZTC0N1002581 IP (100 ,2 ,5 ,8 ,1 ) 1 ZTC0N1002582 IP (100 ,2 ,5 ,8 ,2 ) 1 CSAM2N1012581 IP (101 ,2 ,5 ,8 ,1 ) 1 CSAM5N1012582 IP (101 ,2 ,5 ,8 ,2 ) 1 CSAM5O1002571 OPEN (100 ,2 ,5 ,7 ,1 ) 1 CSAM3O1002572 OPEN (100 ,2 ,5 ,7 ,2 ) 1 CSAM4S1002531 STORAGE (100 ,2 ,5 ,3 ,1 ) 2 --S1002533 STORAGE (100 ,2 ,5 ,3 ,3 ) 2 --

There are two Storage CLIMs configured in this example (S1002531 and S1002533).b. Ensure all the Storage CLIMs are in the STARTED state by issuing the SCF STATUS CLIM

command to the CIP subsystem.> STATUS CLIM $ZZCIP.S*CIP Status CLIM

Name Present State TraceS1002531 Yes STARTED OFFS1002533 Yes STARTED OFF

c. Determine which Storage CLIMs are configured to provide dual paths to a set of disks byissuing the SCF STATUS CLIM command to the storage subsystem.> STATUS CLIM $ZZSTO.S1002531 , DETAILSTORAGE - Detailed Status CLIM \MYSYS.$ZZSTO.#S1002531

Configured Devices:Name State Substate Primary PID Backup PID$SYSTEM-P *STARTED 0,257 1,257$DATA00-P *STARTED 0,327 1,310$DATA01-P *STARTED 0,326 1,313$OSS-P *STARTED 0,323 1,319$DATA03-P *STARTED 0,325 1,315$KMSF1-P *STARTED 0,324 1,317$DATA00-MB STARTED 0,327 1,310$DATA01-MB STARTED 0,326 1,313

132 Upgrading CIP

$OSS-MB STARTED 0,323 1,319$DATA03-MB STARTED 0,325 1,315

> STATUS CLIM $ZZSTO.S1002533 , DETAILSTORAGE - Detailed Status CLIM \MYSYS.$ZZSTO.#S1002533

Configured Devices:Name State Substate Primary PID Backup PID$SYSTEM-B STARTED 0,257 1,257$DATA00-B STARTED 0,327 1,310$DATA01-B STARTED 0,326 1,313$OSS-B STARTED 0,323 1,319$DATA03-B STARTED 0,325 1,315$KMSF1-B STARTED 0,324 1,317$DATA00-M *STARTED 0,327 1,310$DATA01-M *STARTED 0,326 1,313$OSS-M *STARTED 0,323 1,319$DATA03-M *STARTED 0,325 1,315

These commands show that CLIMs S1002531 and S1002533 provide dual paths to thesame disks.

NOTE: The STATUS CLIM $ZZSTO.clim-name shows the status of the disk pathsbelonging to this CLIM and shows the active path (denoted by the asterisk (*) in the Statefield).

d. Switch the disk paths by using the SCF SWITCH CLIM command to the Storage subsystem($ZZSTO).> SWITCH CLIM $ZZSTO.S1002531 , AWAY

e. Ensure the switch worked by issuing the STATUS CLIM command to the storage subsystem.> STATUS CLIM $ZZSTO.S1002531 , DETAILSTORAGE - Detailed Status CLIM \MYSYS.$ZZSTO.#S1002531

Configured Devices:Name State Substate Primary PID Backup PID$SYSTEM-P STARTED 0,257 1,257$DATA00-P STARTED 0,327 1,310$DATA01-P STARTED 0,326 1,313$OSS-P STARTED 0,323 1,319$DATA03-P STARTED 0,325 1,315$KMSF1-P STARTED 0,324 1,317$DATA00-MB STARTED 0,327 1,310$DATA01-MB STARTED 0,326 1,313$OSS-MB STARTED 0,323 1,319$DATA03-MB STARTED 0,325 1,315

S1002531 has disk paths that have no asterisk (*) next to STARTED in the State field,which means the paths configured on this CLIM are not active.> STATUS CLIM $ZZSTO.S1002533 , DETAILSTORAGE - Detailed Status CLIM \MYSYS.$ZZSTO.#S1002533

Configured Devices:Name State Substate Primary PID Backup PID$SYSTEM-B *STARTED 0,257 1,257$DATA00-B *STARTED 0,327 1,310$DATA01-B *STARTED 0,326 1,313$OSS-B *STARTED 0,323 1,319$DATA03-B *STARTED 0,325 1,315$KMSF1-B *STARTED 0,324 1,317$DATA00-M *STARTED 0,327 1,310$DATA01-M *STARTED 0,326 1,313$OSS-M *STARTED 0,323 1,319$DATA03-M *STARTED 0,325 1,315

The backup disk paths are active on S1002533. Since all the disks still have active pathsprovided by CLIM S1002533, you can abort CLIM S1002531.

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 133

f. Abort CIP for the Storage CLIM by issuing the SCF ABORT CLIM command to the CIPsubsystem.> ABORT CLIM $ZZCIP.S1002531

g. Ensure the CLIM is STOPPED by issuing the SCF STATUS CLIM command to the CIPsubsystem.> STATUS CLIM $ZZCIP.S1002531CIP Status CLIM

Name Present State TraceS1002531 Yes STOPPED OFF

h. Update the form as shown in Table 9: Sample populated Storage CLIM upgrade form

Table 9 Sample populated Storage CLIM upgrade form

Normaloperationsresumed?

CLIMrestarted?

Upgradedone?

Switchandabortdone ?

B/upCLIMstarted?B/up CLIM name

Storagepath

RunningMaintProv?If

TypeCLIM name

yes,whichone?

YYS1002533PStS1002531

MB

YS1002531BStS1002533

M

i. Continue with “2. Upgrade the Storage CLIM” (page 134).

2. Upgrade the Storage CLIMa. Perform the software upgrade as described in “Updating CLIM Software Using the OSM

Low-Level Link (H- and J-Series RVUs)” (page 140) or “Updating Individual CLIM SoftwareUsing the CLIM Management Tool ” (page 142).

b. Return to this procedure and continue with “3. Resume Storage CLIM Normal Operations(skip if the host system is not running)” (page 134).

3. Resume Storage CLIM Normal Operations (skip if the host system is not running)a. Check that the upgraded CLIM is operational.

> STATUS CLIM $ZZCIP.*CIP Status CLIM

Name Present State TraceN1002541 Yes STARTED OFFN1002542 Yes STARTED OFFN1002581 Yes STARTED OFFN1002582 Yes STARTED OFFN1012581 Yes STARTED OFFN1012582 Yes STARTED OFFO1002571 Yes STARTED OFFO1002572 Yes STARTED OFFS1002531 Yes STARTED OFFS1002532 Yes STARTED OFF

b. Start CIP for the Storage CLIM if it is STOPPED.c. Check that the disk paths configured in the Storage CLIM are started by issuing the STATUS

CLIM command to the storage subsystem.

134 Upgrading CIP

> STATUS CLIM $ZZSTO.S1002531 , DETAILSTORAGE - Detailed Status CLIM \MYSYS.$ZZSTO.#S1002531

Configured Devices:Name State Substate Primary PID Backup PID$SYSTEM-P STARTED 0,257 1,257$DATA00-P STARTED 0,327 1,310$DATA01-P STARTED 0,326 1,313$OSS-P STARTED 0,323 1,319$DATA03-P STARTED 0,325 1,315$KMSF1-P STARTED 0,324 1,317$DATA00-MB STOPPED 0,327 1,310$DATA01-MB STARTED 0,326 1,313$OSS-MB STARTED 0,323 1,319$DATA03-MB STARTED 0,325 1,315

d. Start any stopped disk paths of the Storage CLIM by issuing the SCF RESET DISK andSTART DISK commands to the storage subsystem. For example:> RESET DISK $DATA00-MB> START DISK $DATA00-MBSTORAGE W01001 To START the disk, SCF must revive the information on

\MYSYS.$DATA00-MB. This operation might IMPACT systemperformance, especially users of $DATA00-MB.

Do you want to start a disk revive on \MYSSY.$DATA00-MB (Y/[N])Y

Enter Y and press Enter at the prompt.

e. Check the disk status again by issuing the SCF STATUS CLIM command to the storagesubsystem.> STATUS CLIM $ZZSTO.S1002531 , DETAILSTORAGE - Detailed Status CLIM \MYSYS.$ZZSTO.#S1002531

Configured Devices:Name State Substate Primary PID Backup PID$SYSTEM-P STARTED 0,257 1,257$DATA00-P STARTED 0,327 1,310$DATA01-P STARTED 0,326 1,313$OSS-P STARTED 0,323 1,319$DATA03-P STARTED 0,325 1,315$KMSF1-P STARTED 0,324 1,317$DATA00-MB STARTED 0,327 1,310$DATA01-MB STARTED 0,326 1,313$OSS-MB STARTED 0,323 1,319$DATA03-MB STARTED 0,325 1,315

f. Switch the disk paths for the Storage CLIM back to the default by using the SCF SWITCHCLIM command to the storage subsystem.> SWITCH CLIM $ZZSTO.S1002531 , DEFAULT

g. Ensure the switch worked and make sure there is at least one active path on the restartedCLIM as indicated by an asterisk (*) next to STARTED in the State field. Use the SCFSTATUS CLIM command to the storage subsystem.> STATUS CLIM $ZZSTO.S1002531 , DETAILSTORAGE - Detailed Status CLIM \MYSYS.$ZZSTO.#S1002531

Configured Devices:Name State Substate Primary PID Backup PID$SYSTEM-P *STARTED 0,257 1,257$DATA00-P *STARTED 0,327 1,310$DATA01-P *STARTED 0,326 1,313$OSS-P *STARTED 0,323 1,319$DATA03-P *STARTED 0,325 1,315$KMSF1-P *STARTED 0,324 1,317$DATA00-MB STARTED 0,327 1,310$DATA01-MB STARTED 0,326 1,313$OSS-MB STARTED 0,323 1,319$DATA03-MB STARTED 0,325 1,315

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 135

> STATUS CLIM $ZZSTO.S1002533 , DETAILSTORAGE - Detailed Status CLIM \MYSYS.$ZZSTO.#S1002533

Configured Devices:Name State Substate Primary PID Backup PID$SYSTEM-B STARTED 0,257 1,257$DATA00-B STARTED 0,327 1,310$DATA01-B STARTED 0,326 1,313$OSS-B STARTED 0,323 1,319$DATA03-B STARTED 0,325 1,315$KMSF1-B STARTED 0,324 1,317$DATA00-M *STARTED 0,327 1,310$DATA01-M *STARTED 0,326 1,313$OSS-M *STARTED 0,323 1,319$DATA03-M *STARTED 0,325 1,315

h. Update the form.i. Wait for about 15 minutes to make sure the system returns to normal operating condition

before updating the backup CLIM.You have now completed the procedure for upgrading a Storage CLIM. Continue upgradeoperations until all Storage CLIMs are upgraded.

Upgrading IP and IB CLIMs

CAUTION: During this procedure, the IP CLIM loses connectivity.

1. Prepare IP and IB CLIMs for Upgrade (skip if the host system is not running)This example shows the preparation step for a failover-configured CLIM. If you are performingthis step on a non-failover-configured CLIM or on a CLIM that is part of a multi-line-path Expandconfiguration, start with the Abort CLIM step.a. List the CLIMs.

> SCF> INFO CLIM $ZZCIP.*Name Mode Location ConnPts ProviderN1002541 IP (100 ,2 ,5 ,4 ,1 ) 1 CSAM2N1002542 IP (100 ,2 ,5 ,4 ,2 ) 1 ZTC0N1002581 IP (100 ,2 ,5 ,8 ,1 ) 1 ZTC0N1002582 IP (100 ,2 ,5 ,8 ,2 ) 1 CSAM2N1012581 IP (101 ,2 ,5 ,8 ,1 ) 1 CSAM5N1012582 IP (101 ,2 ,5 ,8 ,2 ) 1 CSAM5O1002571 OPEN (100 ,2 ,5 ,7 ,1 ) 1 CSAM3O1002572 OPEN (100 ,2 ,5 ,7 ,2 ) 1 CSAM4S1002531 STORAGE (100 ,2 ,5 ,3 ,1 ) 2 --S1002533 STORAGE (100 ,2 ,5 ,3 ,3 ) 2 --

According to the info display there are six IP CLIMs (N1002541, N1002542, N1002581,N1002582, N1012581, N1012582) and two IB CLIMs (O1002571 AND O1002572).

b. Determine which IP or IB CLIMs are configured as failover pairs and ensure the primary andbackup interfaces are up and their link pulses are up.> STATUS PROVIDER $ZZCIP.* , DETAILExcerpt from PROVIDER CSAM2F Home Sts LkP Failover/(Assoc) Sts LkP Current FovrN1002582.bond0 UP UP N1002541.bond0 UP UP N1002582.bond0 HomeN1002582.bond1 UP UP N1002541.eth1 UP UP N1002582.bond1 HomeN1002582.eth3 UP UP N1002541.eth3 UP UP N1002582.eth3 Home

T N1002541.tun624 UP UP (N1002541.eth2) -- -- N1002541.tun624 --N1002541.bond0 UP UP N1002582.BOND0 UP UP N1002541.bond0 HomeN1002541.eth3 UP UP N1002582.eth3 UP UP N1002541.eth3 HomeN1002541.eth2 UP UP -- -- N1002541.eth2 --N1002541.eth1 UP UP -- -- N1002541.eth1 --

This extract shows that N1002541 and N1002582 are configured as a failover pair in ProviderCSAM2, that all failover interfaces have status UP and link pulse UP, and the interfaces arerunning on their home CLIM.

136 Upgrading CIP

NOTE: If the interfaces are not running on their home CLIMs, perform an SCF SWITCHCLIM, RESTORE command to the CIP subsystem and check again.

c. For a failover-configured CLIM, perform a manual failover.1. Switch the CLIM activity to the backup CLIM.

> SWITCH CLIM $ZZCIP.N1002582 , FAILOVEROpen connections still exist, okay to continue? Y

NOTE: TCP and SCTP connections are lost during a failover.

2. Ensure the switch worked.> STATUS PROVIDER $ZZCIP.CSAM2 , DETAILExcerpt from PROVIDER CSAM2F Home Sts LkP Failover/(Assoc) Sts LkP Current FovrN1002582.bond0 UP UP N1002541.bond0 UP UP N1002541.bond0 BkOPN1002582.bond1 UP UP N1002541.eth1 UP UP N1002541.bond1 BkOPN1002582.eth3 UP UP N1002541.eth3 UP UP N1002541.eth3 BkOP

T N1002541.tun624 UP UP (N1002541.eth2) -- -- N1002541.tun624 --N1002541.bond0 UP UP N1002582.bond0 UP UP N1002541.bond0 HomeN1002541.eth3 UP UP N1002582.eth3 UP UP N1002541.eth3 HomeN1002541.eth2 UP UP -- -- N1002541.eth2 --N1002541.eth1 UP UP -- -- N1002541.eth1 --O1002571.ib0 UP UP -- -- O1002571.ib0 --

d. Abort the CLIM.> ABORT CLIM $ZZCIP.N1002582Open connections still exist, okay to continue? Y

Ensure that the CLIM you are about to upgrade is stopped.> SCF STATUS CLIM $ZZCIP.N1002582CIP Status CLIM

Name Present State TraceN1002582 Yes STOPPED OFF

e. Update the form as shown in Table 10: Sample populated IP CLIM upgrade form:

Table 10 Sample populated IP CLIM upgrade form

Normaloperationsresumed?

CLIMrestarted?

Upgradedone?

Switchandabortdone ?

B/upCLIMstarted?B/up CLIM name

Storagepath

RunningMaintProv?If

TypeCLIM name

yes,whichone?

NN1002582IPN1002541

YYN1002541$ZTCP1IPN1002582

YN1002572OPENN1002571

f. Continue with “2. Upgrade the IP or IB CLIMs” (page 137).

2. Upgrade the IP or IB CLIMsa. Perform the software upgrade as described in “Updating CLIM Software Using the OSM

Low-Level Link (H- and J-Series RVUs)” (page 140) or “Updating Individual CLIM SoftwareUsing the CLIM Management Tool ” (page 142).

b. Return to this procedure and continue with “3. Resume IP CLIM Normal Operations (skip ifthe host system is not running)” (page 137).

3. Resume IP CLIM Normal Operations (skip if the host system is not running)a. Start the IP or IB CLIM that you upgraded.

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 137

> START CLIM $ZZCIP.N1002582

b. Check the status of the upgraded IP or IB CLIM.> STATUS CLIM $ZZCIP.N1002582CIP Status CLIM

Name Present State TraceN1002582 Yes STARTED OFF

c. Switch the IP failover CLIMs back.> SWITCH CLIM $ZZCIP.N1002582 , RESTOREOpen connections still exist, okay to continue? Y

d. Ensure the default failover activity is restored.> STATUS PROVIDER $ZZCIP.CSAM2 , DETAILExcerptF Home Sts LkP Failover/(Assoc) Sts LkP Current FovrN1002582.bond0 UP UP N1002541.bond0 UP UP N1002582.bond0 HomeN1002582.bond1 UP UP N1002541.eth1 UP UP N1002582.bond1 HomeN1002582.eth3 UP UP N1002541.eth3 UP UP N1002582.eth3 Home

T N1002541.tun624 UP UP (N1002541.eth2) -- -- N1002541.tun624 --N1002541.bond0 UP UP N1002582.bond0 UP UP N1002541.bond0 HomeN1002541.eth3 UP UP N1002582.eth3 UP UP N1002541.eth3 HomeN1002541.eth2 UP UP -- -- N1002541.eth2 --N1002541.eth1 UP UP -- -- N1002541.eth1 --

N1002582.bond0, N1002582.bond1 and N1002582.eth3 have a status of UP, show Homein the Fovr field and show themselves as the current interfaces in the Current field. Theyhave been restored to the default.

You have now completed the procedure for upgrading an IP CLIM. Continue upgrade operationsuntil all IP CLIMs are upgraded.

Upgrading Telco CLIMs

CAUTION: During this procedure, the Telco CLIM loses connectivity.

For Telco CLIMs, redundancy is configured at the application level. Multiple links using differentCLIMs are configured to each destination and traffic is load balanced across all active links tothat destination. There is no failover for Telco CLIMs, just a redistribution of load across thelink-set going to a common destination.

CAUTION: Determine the configuration for all links on all the Telco CLIMs. Make sure that allthe links on the CLIM being upgraded have a companion link to the same destination on anotherCLIM and that all those links are displaying a healthy status before performing the upgrade.

1. Prepare the Telco CLIM for Upgrade (skip if the host system is not running)a. List the CLIMs:

> SCF> INFO CLIM $ZZCIP.*Name Mode Location ConnPts ProviderN1002541 IP (100 ,2 ,5 ,4 ,1 ) 1 CSAM2N1002542 IP (100 ,2 ,5 ,4 ,2 ) 1 ZTC0N1002581 IP (100 ,2 ,5 ,8 ,1 ) 1 ZTC0N1002582 IP (100 ,2 ,5 ,8 ,2 ) 1 CSAM2N1012581 IP (101 ,2 ,5 ,8 ,1 ) 1 CSAM5N1012582 IP (101 ,2 ,5 ,8 ,2 ) 1 CSAM5O1002571 OPEN (100 ,2 ,5 ,7 ,1 ) 1 CSAM3O1002572 OPEN (100 ,2 ,5 ,7 ,2 ) 1 CSAM4S1002531 STORAGE (100 ,2 ,5 ,3 ,1 ) 2 --S1002533 STORAGE (100 ,2 ,5 ,3 ,3 ) 2 --

138 Upgrading CIP

There are two Telco CLIMs (O1002571 and O1002572), configured in Providers CSAM3and CSAM4.

b. Examine the linkset configuration by generating a configuration report with the OpenCallINS Command Control and Monitoring Interface (CCMI). The Guide to Operations andMaintenance for HPEOpenCall Intelligent Network Serve describes the Configuration Reportgenerated from the System Home Page (used to get to CCMI) and the instructions forgenerating the report are in the online help.

c. Ensure all Telco CLIMs are in the STARTED state.> STATUS CLIM $ZZCIP.O*CIP Status CLIM

Name Present State TraceO1002571 Yes STARTED OFFO1002572 Yes STARTED OFF

d. Determine which Telco CLIMs are configured as multi-link by using CCMI. See the Guideto Operations and Maintenance for HPE OpenCall Intelligent Network Server.

e. Depending on your Method of Procedure, if appropriate, deactivate the signal link providedby the CLIM you are about to upgrade by using CCMI. (The syntax for the instructions arein the online help.)

f. Abort the CLIM.> ABORT CLIM O1002571Open connections still exist, okay to continue? Y

g. Check that the CLIM was stopped.> STATUS CLIM O1002571CIP Status CLIM

Name Present State TraceO1002571 Yes STOPPED OFF

h. Update the form as shown in Table 11: Sample populated Telco CLIM upgrade form:

Table 11 Sample populated Telco CLIM upgrade form

Normaloperationsresumed?

CLIMrestarted?

Upgradedone ?

Switchandabort

B/upCLIMstarted?

B/up CLIMname

StoragepathProvider

RunningMaintProv?If yes,

TypeCLIMname

done?

whichone?

YYO1002572TelcoO1002571

NO1002571TelcoO1002572

i. Continue with “2. Upgrade the Telco CLIM” (page 139).

2. Upgrade the Telco CLIMa. Perform the software upgrade as described in “Updating CLIM Software Using the OSM

Low-Level Link (H- and J-Series RVUs)” (page 140) or “Updating Individual CLIM SoftwareUsing the CLIM Management Tool ” (page 142).

b. Return to this procedure and continue with “3. Resume Telco CLIM Normal Operations (skipif the host system is not running)” (page 139).

3. Resume Telco CLIM Normal Operations (skip if the host system is not running)a. Check that the upgraded Telco CLIM is operational.

> STATUS CLIM $ZZCIP.*CIP Status CLIM

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 139

Name Present State TraceN1002541 Yes STARTED OFFN1002542 Yes STARTED OFFN1002581 Yes STARTED OFFN1002582 Yes STARTED OFFN1012581 Yes STARTED OFFN1012582 Yes STARTED OFFO1002571 Yes STARTED OFFO1002572 Yes STARTED OFFS1002531 Yes STARTED OFFS1002532 Yes STARTED OFF

b. Start the Telco CLIM if it is STOPPED.c. If you deactivated the signal link provided by the CLIM you upgraded, reactivate it by using

CCMI.d. Check that the links and default activity are restored by using CCMI. See the Guide to

Operations and Maintenance. This may take several minutes.e. Update the form.You have now completed the procedure for upgrading a Telco CLIM. Continue upgrade operationsuntil all Telco CLIMs are updated.

Updating CLIM Software Using the OSM Low-Level Link (H- and J-Series RVUs)The OSM Low-Level Link can still be used for updating individual CLIM software for systemsrunning H- and J-series RVUs. However, if you are using OSM T0682H02^ADP or later, you canuse the CLIM Management Tool for updating individual CLIM software. For information, see“Updating Individual CLIM Software Using the CLIM Management Tool ” (page 142). The CLIMManagement Tool can also be used for updating all CLIM software while the system is down.For information, see “Upgrading CLIM Software or Firmware While the System is Down ”(page 160).This procedure uses the IP CLIM as an example but the steps are the same for all CLIM types.1. Log onto the OSM Low-Level Link on each CLIM.2. This dialog box is displayed:

3. Select the Software Update option and, if updating INS on a Telco CLIM, also select theConfigure box.

4. Click OK.The Software Update dialog box appears. If you selected multiple options, they are performedin sequential order; first the software update, then the INS Software Update.

5. Select the correct software version from the Available versions on NSC drop-downmenu.

140 Upgrading CIP

6. Click Update.7. Check the status in the log and ensure it shows that the software passed and that the version

matches what you selected. For example:

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 141

8. When the update is complete, click OK in the dialog box to reboot the CLIM.9. To check the CLIM status, log onto its iLO and use the psclim command.10. To check the version, from the iLO, use the cat /etc/vproc command. The version

should match your new version.11. Update the form.12. Continue with the resume normal operations step for your CLIM type.

Updating Individual CLIM Software Using the CLIM Management ToolFor systems running on H- and J-series software, the CLIM Management Tool replaces the DownSystem CLIM Firmware Update Tool in OSM Console Tools T0634 ABJ and later. It also replacesthe CLIM software update functionality of the OSM Low-Level Link, provided you have theprerequisites for using the CLIM Management Tool on H- and J-series. For information, see“Upgrading CLIM Software or Firmware While the System is Down ” (page 160).For systems running L-series software, the CLIM Management tool is required for CLIM softwareupdates. The OSM Low-Level Link is not supported.This section describes using the CLIM Management Tool to update CLIM software or (Telco)CLIM INS software on an individual CLIM while the system is running. For information on updatingsoftware on all CLIMs software while the system is down, see “Upgrading CLIM Software orFirmware While the System is Down ” (page 160).This procedure uses the IP CLIM as an example but the steps are the same for all CLIM types.1. From the Windows Start menu, select All Programs→HPOSM→CLIMManagement Tool.

142 Upgrading CIP

2. Select the Perform Single CLIM Software Update or the Perform Single CLIM INSSoftware Update or the Perform Down System CLIM Software/Firmware Update actionif updating INS on a Telco CLIM.

3. Enter the IP Address and root Password for the CLIM you wish to update. Click Continue.

4. If you select the Perform Single CLIM Software Update, OSM displays this screen:

5. Select the correct software version from the Select Software Version drop-down menuand click OK.

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 143

6. A confirmation dialog informs you that the update and reboot can take up to an hour. ClickYes to dismiss the confirmation dialog and start the update. The tool displays a Statuswindow from which you can track the progress of the update.

Upgrading CLIM Firmware with the System Running

NOTE: This is no longer the best method to update CLIM firmware during an RVU upgrade.Since you will need to bring down the system for the RVU migration, “Upgrading CLIM Softwareor Firmware While the System is Down ” (page 160) provides a faster, more efficient method.Update firmware only if it is flagged as down revision by OSM. Do not update firmware when itis flagged as compatible by OSM.

Preparing to Update CLIM Firmware with the System RunningThis section contains notes, guidelines, and cautions to be followed to reduce the risk ofinterrupting network or storage traffic during the firmware updates.

• Firmware versions must be compatible on the system. Verify all firmware versions. For moreinformation, see the NonStop Firmware Matrices document available on the web at http://www.hpe.com/info/nonstop-docs. To locate the document, in the main page, click HPEIntegrity NonStop Service Information under NonStop Technical Library.

• You can update the firmware on multiple CLIMs by using the OSM Service ConnectionMulti-Resource Actions dialog box. If you plan to perform a firmware update on multipleCLIMs at once, follow the same grouping scheme described in “Upgrading Multiple CLIMsin Parallel” (page 155).If the software or firmware update is to be done on a production NonStop system and storageor network traffic needs to be maintained, the updates of multiple CLIMs can still be donein parallel, but consideration has to be given not to affect storage or network traffic. Referto “Upgrading Multiple CLIMs in Parallel” (page 155) for the procedure.

• You may not need to update firmware on all Storage CLIMs; for example, if the firmwareupdate is for FC HBA firmware, you only need to upgrade Storage CLIMs that have an FCHBA installed.

144 Upgrading CIP

1. If upgrading firmware from SPRs, place the files in the currently running SYSnn so thatOSM can compare the new and current versions.

2. Check the firmware versions by using OSM Service Connection Multi-Resource Actionsdialog box.

3. Update firmware as appropriate.

• To ensure peak OSM performance, make sure that the Java runtime parameter is setappropriately for your system console, as described in the OSM Configuration Guide.

CAUTION:• For G2 and G5 CLIMs, if multiple CLIM component firmware updates are required, update

the SAS HBA firmware in slot 5 last. During a SAS update of the slot-5 HBA, the CLIM maybe rebooted automatically.

• Even though, in the OSM Multi-Resource window, these objects can be selected and anaction performed on them at the same time, internally, the OSM server performs theseactions one at a time to maintain system stability:

◦ CLIM FC card (BIOS and firmware)

◦ CLIM SAS card (BIOS and firmware)

◦ SAS Disk enclosure firmware

Divide Storage CLIMs into Primary and Backup Path GroupsThis optional procedure explains how to divide CLIMs into two groups such that the CLIMsconfigured as the primary and mirror paths for any given disk are not in the same group. Thepurpose is so you can update SAS card firmware and later reboot the CLIMs by group (as directed,

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 145

in “Performing CLIM Firmware Updates with the System Running” (page 150), and not bring downboth paths for any disk.

• Check the storage disk configuration on the running NonStop system.

• Make a primary group and a backup group based on the CLIMs configured as primary andbackup paths for disks.1. Find out through which CLIMs the disk paths are configured and the status of the paths:

a. Using the Multi-Resource Actions window, select the resource type CLIMAttached Disk.All the logical disks configured through CLIMs are listed.The Primary Path orBackup Path attributes show the configured CLIM informationof the disk.The Primary Path State and Backup Path State attribute show whether the paththrough the CLIM connected to the disk is up or down.

146 Upgrading CIP

2. Divide all the Storage CLIMs into two groups such that the same group does not haveboth CLIMs configured as primary and mirror paths for the same disk. For example, thedata shown in the images in previous step, the CLIMs must be divided as:

◦ Group 1 – S1002543, S1002533

◦ Group 2 – S1002541, S1002531

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 147

• Check which two CLIMs implement $ZTCP0 and $ZTCP1.At the TACL prompt, issue the command:TACL> SCF INFO SUBNET $ZTCP*.*, DETAIL

This shows which CLIMs implement the two processes. For example (IP addresses andsystem name removed):

In this example, CLIMs C1002581 and C1002583 implement the $ZTCP0 and $ZTCP1processes.

Estimating Time for CLIM Firmware UpdatesYou can use Table 12 (page 148) to estimate the total amount of time needed to update thespecified components in your environment.

Table 12 Firmware Update Time Estimates and Calculation Form

Estimated time for yourenvironment (fill in the

CommentsEstimated time(minutes)

Number ofcomponentsupdatedT#Object

value based on theinformation in theprevious columns)

A maximum of 8 areupdated in parallel.

2 to 4Up to 16T0848CLIM ROM

4 to 8Up to 32

5 to 7. No rebootrequired.

Up to 16T0848CLIM iLO

15 to 21Up to 32

2Multiple NICson different

T0849NIC

CLIMs (1 NICper CLIM)

2 to 4Up to 16T0846SmartArrayController

4 to 8Up to 32

148 Upgrading CIP

Table 12 Firmware Update Time Estimates and Calculation Form (continued)

Estimated time for yourenvironment (fill in thevalue based on theinformation in theprevious columns)Comments

Estimated time(minutes)

Number ofcomponentsupdatedT#Object

Single update2 to 41T0842SAS HBAFirmware

This firmware isupdated serially.

2 to 4 minutes per SASHBAs to be updated

>1

Single update2 to 41T0842SAS HBABIOS

This firmware isupdated serially.

2 to 4 minutes per SASHBAs to be updated

>1

Single update2 to 41T0843FC HBAFirmware

This firmware isupdated serially.

2 to 4 minutes per SASHBAs to be updated

>1

2 times the number ofNICs on the CLIM

Multiple NICson a singleCLIM

This firmware isupdated serially.

15 to 201T0841MSA70

15 to 20 minutes perMSA70

>1

8 to 101T0841D2700SAS diskenclosure

8 to 10 minutes perD2700

>1

15 minutes1T0841D3700SAS diskenclosureforNonStop X

15 minutes per D3700>1

8 to 101T0856M8390-12CG

8 to 10 minutes perM8390-12

>1

8 to 101T0856M8391-24x

8 to 10 minutes perM8391-24

>1

5 minutes1T0849CLIM IBHCA forNonStop X

5 minutes per CLIM IBHCA

>1

Total Time:

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 149

Performing CLIM Firmware Updates with the System RunningThis procedure presents a suggested sequence for updating CLIM firmware using the OSMService Connection.1. To update CLIM iLO firmware:

a. Open the OSM Service Connection Multi-Resource dialog box.b. Click Display →Multi-Resource Actionsc. Select the resource type CLIM.d. Choose the iLO Update action.e. Select all the CLIMs that show the iLO Compare State attribute as Down-rev.f. Add the selected CLIMs to the bottom pane.g. Click Perform Action.h. Check the estimated time in Table 12 (page 148) and wait for the updates to complete.

The progress bar at the bottom indicates the result of the performed actions

(Passed/Failed). A (Passed) or a (Failed) indication at the side of each componentshows the individual resource action result.

ClickAction Summary to view the summary of all the actions performed on the system.

150 Upgrading CIP

If this is the only firmware being updated, only an iLO reset is required.

2. Once the updates are completed, click Remove All to clear the bottom pane.3. To update ROM firmware:

a. Perform steps 1.a through 1.c.b. Choose the ROM Update action.c. Select all the CLIMs that show the ROM Compare State attribute as Down-rev and

add them to the bottom pane.d. Click Perform Action.e. Check the estimated time in Table 12 (page 148) and wait for the updates to complete.

(See the figures in step 1.h.)4. To update CLIM NIC firmware:

a. Perform steps 1.a through 1.b.b. Select the resource type CLIM NIC.c. Choose the Firmware Update action.d. Select all the CLIM NICs that show the FirmwareCompare State attribute asDown-rev.e. Add the selected CLIM NICs to the bottom pane.f. Click Perform Action.g. Check the estimated time in Table 12 (page 148) and wait for the updates to complete.

(See the figures in step 1.h.)5. To update CLIM smart array controller firmware:

a. Perform steps 1.a through 1.b.b. Select the resource type CLIM Smart Array Controller.c. Choose the Firmware Update action.d. Select all the CLIM Smart Array Controller that show the Firmware Compare State

attribute as Down-rev.e. Add the selected CLIM Smart Array Controllers to the bottom pane.f. Click Perform Action.g. Check the estimated time in Table 12 (page 148) and wait for the updates to complete.

(See the figures in step 1.h.)6. To update CLIM FC card BIOS:

a. Perform steps 1.a through 1.b.b. Select the resource type CLIM FC Card.

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 151

c. Select all the CLIM FC Cards that show the BIOSCompare State attribute asDown-revand choose the BIOS Update action.

d. Add the selected CLIM FC cards to the bottom pane.e. Click Perform Action.f. Check the estimated time in Table 12 (page 148) and wait for the updates to complete.

(See the figures in step 1.h.)7. Once the updates are completed, click Remove All to clear the bottom pane.8. To update FC card firmware:

a. Perform steps 1.a through 1.b.b. Select the resource type CLIM FC Card.c. Choose the Firmware Update action.d. Select all the CLIM FC Cards that show the Firmware Compare State attribute as

Down-rev and add them to the bottom pane.e. Click Perform Action.f. Check the estimated time in Table 12 (page 148) and wait for the updates to complete.

(See the figures in step 1.h.)9. To update SAS disk enclosure firmware:

a. Perform steps 1.a through 1.b.b. Select the resource type SAS Disk Enclosure.c. Choose the Firmware Update action.

NOTE: After you update the MSA70 firmware, perform a power cycle to complete theMSA70 firmware update. (Even though the updated firmware revision informationdisplays, the firmware is not completely updated until the power cycle occurs.)

d. Select all the SAS Disk Enclosures that show the Firmware Compare State attributeas Down-rev.

e. Add the selected SAS Disk Enclosures to the bottom pane.f. Click Perform Action.g. Check the estimated time in Table 12 (page 148) and wait for the updates to complete.

(See the figures in step 1.h.)10. To update CLIM SAS card BIOS:

a. Perform steps 1.a through 1.b.b. Select the resource type CLIM SAS Card.c. Choose the BIOS Update action.d. Select all the CLIM SAS Cards that show the BIOS Compare State attribute as

Down-rev.e. Add the selected CLIM SAS Cards to the bottom pane.f. Click Perform Action.g. Check the estimated time in Table 12 (page 148) and wait for the updates to complete.

(See the figures in step 1.h.)11. Once the updates are completed, click Remove All to clear the bottom pane.12. To update SAS card firmware:

a. Perform steps 1.a through 1.b.b. Update firmware of CLIM SAS cards that are not in slot 5:

i. Choose the Firmware Update action.ii. Select all the CLIM SAS cards that show the Firmware Compare State attribute

as Down-rev and that are not in slot 5 (that is, whose Resource Name does notend with $ZZCIP.Clim-Name.5), and add them to the bottom pane.

152 Upgrading CIP

iii. Click Perform Action.iv. Check the estimated time in Table 12 (page 148) and wait for the updates to

complete. (See the figures in step 1.h.)c. Once the updates are completed, click Remove All to clear the bottom pane.d. Update the down-rev CLIM SAS cards that are in slot 5 and the first group:

i. Choose the Firmware Update action.ii. Select the SAS cards of Storage CLIMs that show the Firmware Compare State

attribute as Down-rev that are in slot 5 (that is, whose Resource Name ends with‘$ZZCIP.Clim-Name.5), and whose CLIMs belong to the first group of StorageCLIMs to be updated (determined previously by looking at the primary and backuppaths of disks). Add these SAS Cards to the bottom pane.

iii. Group the SAS cards of half the Networking CLIMs that show the FirmwareCompare State attribute as Down-rev that are in slot 5 (that is, whose ResourceName ends with $ZZCIP.Clim-Name.5). (Include the CLIM implementing $ZTCP0in this group, but NOT the CLIM implementing $ZTCP1.) Add these SAS cards tothe bottom pane.

iv. Click Perform Action.

NOTE: During a SAS update of the slot-5 HBA, the CLIM may be rebootedautomatically.

v. Check the estimated time in Table 12 (page 148) and wait for the updates tocomplete. (See the figures in step 1.h.)

e. Step 12.d may result in some CLIMs being rebooted automatically, which will result inCLIMs transitioning to the STARTING state as shown by the SCF STATUS CLIM$ZZCIP.* command. If any CLIM has changed to the STARTING state, wait until therecovery is completed and the CLIM changes back to the STARTED state.

f. Once the updates are completed, click Remove All to clear the bottom pane.g. Wait for the updated CLIMs to return to the STARTED state, determined by using the

SCF STATUS CLIM $ZZCIP.* command to find the current statush. Update down-rev firmware of the remaining CLIM SAS cards that are in slot 5.

i. Choose the Firmware Update action.ii. Select the SAS cards of Storage CLIMs that show the Firmware Compare State

attribute as Down-rev, that are in slot 5 (that is, whose Resource Name ends with‘$ZZCIP.Clim-Name.5), and whose CLIMs belong to the second group of StorageCLIMs to be updated (determined previously by looking at the primary and backuppaths of disks). Add these SAS cards to the bottom pane.

iii. Select the SAS cards of the second group of Networking CLIMs that show theFirmware Compare State attribute as Down-rev, and are in slot 5 (that is, whoseResource Name ends with $ZZCIP.Clim-Name.5). (Include the CLIM implementing$ZTCP1 in this group.) Add these SAS cards to the bottom pane.

iv. Click Perform Action.

NOTE: During a SAS update of the slot-5 HBA, the CLIM may be rebootedautomatically.

v. Check the estimated time in Table 12 (page 148) and wait for the updates tocomplete. (See the figures in step 1.h.)

i. Step 12.h may result in some CLIMs being rebooted automatically which will result inCLIMs being transitioned to the STARTING state as shown by the SCF STATUS CLIM

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 153

$ZZCIP.* command. If any CLIM has changed to the STARTING state, wait until therecovery is completed and the CLIM changes back to STARTED state.

j. Wait for the updated CLIMs to return to the STARTED state by using the SCF STATUSCLIM $ZZCIP.* command to find the current status.

Once all the CLIMs and their components are updated, the CLIMs must be rebooted.Verify if any CLIM was automatically rebooted as a result of the firmware update in step 12.d or12.h. If so, do NOT reboot it again by using the CLIM reboot procedure in “Rebooting CLIMsWhen the System is Up” (page 154).

Rebooting CLIMs When the System is UpThis procedure reboots CLIMs in parallel while avoiding losing access to the OSM ServiceConnection, $SYSTEM, or any disk revives.1. Switch away the paths of the first group of Storage CLIMs:

a. Open the OSM Service ConnectionMulti-Resource Actionswindow by using the OSMService Connection window and clicking Display→Multi-Resource Actions.

b. Select the resource type CLIM.c. Choose the Switch Storage Paths Away action.d. Select the first group of Storage CLIMs to be updated (determined previously by looking

at the primary and backup paths of disks) and add them to the bottom pane.

NOTE: Do not select any Storage CLIM that already was rebooted at the end offirmware update procedure.

e. Click Perform Action.f. Wait for the updates to complete. See the figures in step 1.h of “Upgrading CLIM

Firmware with the System Running” (page 144).2. Add the first group of Networking CLIMs:

Select half of the Networking CLIMs (include the CLIM implementing $ZTCP0 in this half,but not the CLIM implementing $ZTCP1), and add them to the bottom pane. Do not selectany networking CLIM that already was rebooted at the end of the firmware-update procedure.

3. Reboot all the selected Storage and Networking CLIMs.a. Select Reboot.b. Click Perform Action.

4. Wait for the CLIMs to return to the STARTED state by using the SCF STATUS CLIM$ZZCIP.* command.

5. Click Remove All to clear the bottom pane.6. Switch away the paths of the second group of Storage CLIMs to be updated.

a. Select the second group of Storage CLIMs to be updated (determined previously bylooking at the primary and backup paths of disks) and add them to the bottom pane,but do not select any Storage CLIM that was already rebooted at the end of firmwareupdate procedure.

b. Choose the Switch Storage Paths Away action.c. Click Perform Action.d. Wait for the updates to complete. See the figures in step 2 of “Upgrading CLIM Firmware

with the System Running” (page 144).7. Select the second group of the Networking CLIMs:

Select the other half of the Networking CLIMs not included in the first set of reboots (includethe CLIM implementing $ZTCP1 in this half), but do not select any networking CLIM thatwas already rebooted at the end of firmware update procedure, and add them to the bottompane.

154 Upgrading CIP

8. Reboot all the selected Storage and Networking CLIMs.a. Select Reboot to reboot all the selected Storage and Networking CLIMs.b. Click Perform Action.

9. Wait for the CLIMs to return to the STARTED state by using the SCF STATUS CLIM$ZZCIP.* command.

Upgrading Multiple CLIMs in ParallelYou can upgrade four CLIMs simultaneously. This example uses these 10 CLIMs:

• Two Storage CLIMs providing dual paths to a set of disks.

• Two IP CLIMs that form a failover pair.

• Two IP CLIMs that are used for an Expand multi-line-path configuration.

• Two IP CLIMs that are not in any backup configuration.

• Two Telco CLIMs that provide multiple links for INS applications.In this example, the CLIMs are grouped by type, but you can also update multiple CLIM types inparallel. See “Upgrading Multiple CLIMs of Different Types” (page 160).To upgrade multiple CLIMs, update the software on each CLIM that is configured with a backup,one at a time, and ensure the first of each of these upgraded CLIMs is operational before updatingthe backup CLIMs. If you upgrade CLIMs that are not configured with some form of backup, planfor the unavailability of these network or storage resources.To update multiple CLIMs, open one OSM Low-Level Link or CLIM Management Tool sessionfor each CLIM.

CAUTION: To make sure there are sufficient resources, upgrade four or fewer CLIMs at atime.

Upgrading Groups of Storage CLIMsAlthough this example shows two Storage CLIMs, you can have four Storage CLIMs providingpaths to a disk volume. If so, update one CLIM per disk volume at a time.

NOTE: Examples of Storage CLIMs not in fault-tolerant configurations include Storage CLIMsthat are connected to a disk or tape that has no functioning backup path. If you have disks thatdo not have a backup path, only update the primary Storage CLIM that provides its path afterplanning for the unavailability of these disks.

1. For each Storage CLIM, check that the CLIM has a backup path by following steps 1 - 3 in“1. Prepare the Storage CLIM for Upgrade (skip if the host system is not running)” (page 132).Return to this procedure and fill in the group upgrade form as shown in this example(Table 13: Sample populated Storage CLIM group upgrade form). When you are filling inthe group form, put the primary Storage CLIMs in one upgrade group and the backup CLIMsin another group so that a path to each disk remains active when one of the CLIMs is stopped.

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 155

Table 13 Sample populated Storage CLIM group upgrade form

Normaloperationsresumed?

CLIMrestarted?

Upgradedone ?

Switchandabort

B/upCLIMstarted?

B/up CLIMname

Storagepath

RunningMaintProv?If

GroupTypeCLIMname

done?

yes,whichone?

YS1002533PAStorS1002531

MB

YS1002531BBStorS1002533

M

2. Perform the remaining preparation steps, steps 4 - 7, in “1. Prepare the Storage CLIM forUpgrade (skip if the host system is not running)” (page 132), but return to this procedure tocomplete the group form. (Do not perform the software upgrade yet.)

3. Look at the form, which tells you which CLIMs are in the first group (group A in this example)and, selecting up to four CLIMs from this group, perform “2. Upgrade the Storage CLIM”(page 134) on all the CLIMs simultaneously by using multiple sessions of OSM Low-LevelLink or CLIM Management Tool, one for each CLIM. For example:

4. For each CLIM in the group, perform “3. Resume Storage CLIM Normal Operations (skip ifthe host system is not running)” (page 134).

156 Upgrading CIP

Upgrading Groups of IP CLIMs

CAUTION: When upgrading multiple IP CLIMs at a time, do not upgrade the one where $ZTC0is configured or you will lose your session.

1. See steps 1 - 2 of “1. Prepare IP and IB CLIMs for Upgrade (skip if the host system is notrunning)” (page 136) to determine which IP CLIMs are configured as failover pairs then returnto this procedure. Do not perform the failover yet.

2. Divide all IP CLIM failover pairs in the system into the groups and update the form.• Upgrade Group A

N1002541

• Upgrade Group BN1002582

3. Determine if any CLIMs have $ZTCP0 and $ZTCP1.> INFO PROVIDER $ZZCIP.ZTCP0 , DETAILCIP Detailed info PROVIDER \MYSYS.$ZZCIP.ZTCP0

*TPName.................... $ZTCP0Type...................... MAINTENANCE*HostID.................... 1.2.3.4*Hostname.................. home1*TCP-Listen-Que-Min........ 128*BRecvPort................. No Ports Specified*CLIM...................... N1002581*IPAddress................. 192.168.36.10

> INFO PROVIDER $ZZCIP.ZTCP1 , DETAILCIP Detailed info PROVIDER \MYSYS.$ZZCIP.ZTCP1

*TPName.................... $ZTCP1Type...................... MAINTENANCE*HostID.................... 0.0.0.0*Hostname.................. osmlany*TCP-Listen-Que-Min........ 128*BRecvPort................. No Ports Specified*CLIM...................... N1002582*IPAddress................. 192.168.36.11

The maintenance Providers $ZTCP0 and $ZTCP1 are in N1002581 and N1002582.4. Divide the CLIMs associated with $ZTCP0 and $ZTCP1 into two different groups and update

the form accordingly.

CAUTION: If one of these CLIMs is not in the started state, or its eth0:0 interface is notin the started state, correct this condition before upgrading. An SCF STATUS PROVIDER$ZZCIP.ZTCP* , DETAIL command shows the status of the eth0:0 interface (ensure Statusand LkP show UP) and of the provider (ensure State and TPStatus show as Started).

• Upgrade Group AN1002541, N1002581

• Upgrade Group BN1002582

5. Determine which CLIMs are configured for Expand multi-line paths. See the ExpandConfiguration and Management Manual. In this example, the two IP CLIMs N1012581 and

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 157

N1012582 are configured in Provider CSAM5, which is the Provider for an Expandmulti-line-path configuration.

6. Make sure all lines part of the path are up.7. Divide these CLIMs into the groups and add them to the form.

Group AN1002541, N1002581, N1012581Upgrade Group BN1002582, N1002542, N1012582

8. Identify the IP CLIMs that are not configured with backups, either through IP failover orthrough Expand multi-line path redundancy. In this example, these CLIMs include N1002542and N1002581. N1002581 was already put in group A as part of the step to divide themaintenance Provider CLIMs. N1002542 goes in group B. (It is not actually necessary todivide the CLIMs that are not configured with backup into different groups because they areindependent. However, because CLIMs should only be upgraded in groups of four, it is agood practice to balance the number of CLIMs between groups.)Add them to the form.Upgrade Group BN1002582, N1002542

9. Complete the form as shown in Table 14: Sample populated IP CLIM group upgrade form:

Table 14 Sample populated IP CLIM group upgrade form

Normaloperationsresumed?

CLIMrestarted?

Upgradedone ?

Switchandabort

B/upCLIMstarted?

B/up CLIMname

Storagepath

RunningMaintProv?If

GroupTypeCLIMname

done?

yes,whichone?

YN1002582AIPN1002541

N/ABIPN1002542

N/AZTCP0BIPN1002581

YN1002541ZTCP1AIPN1002582

YN1012582AIPN1012581

YN1012581BIPN1012582

10. Return to steps 3 - 5 of “1. Prepare IP and IB CLIMs for Upgrade (skip if the host system isnot running)” (page 136) and perform the failover for the failover-configured CLIMs in theprimary group.

11. For up to four CLIMs in the first group, perform “2. Upgrade the IP or IB CLIMs” (page 137)by using multiple sessions of OSM Low-Level Link or CLIM Management Tool, one for eachCLIM.

12. For each CLIM in the group, perform step “3. Resume IP CLIM Normal Operations (skip ifthe host system is not running)” (page 137).

Upgrading Groups of Telco CLIMs

CAUTION: Make sure you have a second CLIM that is connected to the same set of linksbefore you perform the upgrade.

158 Upgrading CIP

1. Follow the information gathering steps, steps 1 - 4 of “1. Prepare the Telco CLIM for Upgrade(skip if the host system is not running)” (page 138) then return to this procedure.

2. Divide all Telco CLIM pairs in the system, where both CLIMs are in the started state and thelinks are also functioning, into groups, and enter them on the form as shown in Table 15:Sample populated Telco CLIM group upgrade form:

Table 15 Sample populated Telco CLIM group upgrade form

Normaloperationsresumed?

CLIMrestarted?

Upgradedone?

Switchandabort

B/upCLIMstarted?

B/up CLIMname

StoragepathProvider

RunningMaintProv?If

GroupTypeCLIMname

done?

yes,whichone?

YO1002572ATelcoO1002571

YO1002571BTelcoO1002572

3. Return to “1. Prepare the Telco CLIM for Upgrade (skip if the host system is not running)”(page 138), and perform steps 5 - 7, deactivating links and aborting the CLIMs in the firstgroup. Fill in the group form in this procedure.

4. For up to four CLIMs in the first group, perform step “2. Upgrade the Telco CLIM” (page 139)by using multiple sessions of OSM Low-Level Link or CLIM Management Tool, one for eachCLIM.

5. For each CLIM in the group, perform step “3. Resume Telco CLIM Normal Operations (skipif the host system is not running)” (page 139).

Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 159

Upgrading Multiple CLIMs of Different Types1. Follow the procedures for dividing the CLIMs into groups as described in “Upgrading Groups

of Storage CLIMs” (page 155), “Upgrading Groups of IP CLIMs” (page 157), and “UpgradingGroups of Telco CLIMs” (page 158) and complete the form as shown in Table 16: Samplepopulated IP CLIM group upgrade form:

Table 16 Sample populated IP CLIM group upgrade form

Normaloperationsresumed?

CLIMrestarted?

Upgradedone ?

Switchandabortdone?

B/upCLIMstarted?

B/up CLIMname

Storagepath

RunningMaintProv?Ifyes,whichone?GroupType

CLIMname

YN1002582AIPN1002541

BIPN1002542

ZTCP0BIPN1002581

YN1002541ZTCP1AIPN1002582

YN1012582AIPN1012581

YN1012581BIPN1012582

YO1002572ATelcoO1002571

YO1002571BTelcoO1002572

YS1002533PAStS1002531

MB

YS1002531MBStS1002533

B

2. Follow the procedures for completing the preparation steps for each CLIM type as describedin “Upgrading Groups of Storage CLIMs” (page 155), “Upgrading Groups of IP CLIMs”(page 157), and “Upgrading Groups of Telco CLIMs” (page 158).

3. Follow the procedures for upgrading the CLIMs, using appropriate groups such that a backupof each CLIM remains active during the procedure, by following the upgrade procedure asdescribed in “Upgrading Groups of Storage CLIMs” (page 155), “Upgrading Groups of IPCLIMs” (page 157), and “Upgrading Groups of Telco CLIMs” (page 158). You can upgrademultiple types of CLIMs at a time.

4. Follow the procedures for resuming operations as described in “Upgrading Groups of StorageCLIMs” (page 155), “Upgrading Groups of IP CLIMs” (page 157), and “Upgrading Groups ofTelco CLIMs” (page 158).

Upgrading CLIM Software or Firmware While the System is DownThis section describes how to update CLIM software and firmware during planned system downtime, such as during an RVU upgrade, and provides guidance on optimizing CLIM software andfirmware updates during an RVU upgrade. Updating CLIM software and firmware when thesystem is down, when there is no need to maintain network or storage traffic, is the fastest, mostefficient method.All CLIM firmware and/or software can be updated simultaneously through the CLIM ManagementTool for L-series RVUs. It can also be used for H- and J-series RVUs depending on your OSMserver version; see “Upgrading CLIM Software and Firmware” (page 128) for prerequisites and

160 Upgrading CIP

limitations. If not available, you can also use the Down System CLIM Firmware Update Tool toupdate all CLIM firmware simultaneously, but it cannot be used to update CLIM software.

Overview of Optimized CLIM Software and Firmware Update Procedure1. “Prepare CLIMs for Down System Firmware Update” (page 161)2. “Halt the Processors” (page 161)3. “Update CLIM Software on a Down System”4. “Update CLIM Firmware on a Down System” (page 162)5. “Load the System” (page 162)

Prepare CLIMs for Down System Firmware UpdateTo update CLIM firmware while the system is down, you must first perform the Prepare for DownSystem CLIM Management action, located under the CLIMs object in the OSM ServiceConnection before stopping the system. For earlier H- and J-series versions of OSM, the actionmay be called Prepare for Down System CLIM Firmware Update. For more information, seethe OSM Service Connection online help.Upon successful completion of this action, you will be able to perform the updates when thesystem is down using the CLIM Management Tool. For H- and J-series only, you can use theDown System CLIM Firmware Update Tool if the CLIM Management Tool is not installed.

Halt the ProcessorsHalt all the processors by using the OSM Low-Level Link (H- and J-series RVUs) or the OSMSystem Startup Tool (L-series), as described in the applicable software installation and upgradeguide associated with your CIP RVU or the online help for the OSM tool you are using.

Update CLIM Software on a Down SystemTo update software on all CLIMs while the system is down, use the CLIM Management Tool.CLIM software can be updated at the same time as CLIM firmware or independently.For NonStop X systems, you must use the CLIM Management Tool to update CLIM software.All CLIMs can be updated while the system is down, as described in this section, or for individualCLIMs while the system is running, as described in “Updating Individual CLIM Software Usingthe CLIM Management Tool ” (page 142).The CLIM Management Tool is installed on NonStop system consoles as part of the OSM ConsoleTools product. It is launched from the Windows programs list by selecting HP OSM→CLIMManagement Tool. To update CLIMs while the system is down, select the Perform DownSystem CLIM Software/Firmware Update action. For more information, see the CLIMManagement Tool online help.

NOTE: To also update CLIM firmware while the system is down, you must first perform anaction in the OSM Service Connection before stopping the system. For information, see “PrepareCLIMs for Down System Firmware Update” (page 161).

For NonStop systems running H- and J-series software, you can also use the CLIM ManagementTool to update CLIM software as described above, provided you have met the prerequisitesdescribed in “Upgrading CLIM Software and Firmware” (page 128). If these prerequisites are notmet, you can use the OSM Low-Level Link to update the software on CLIMs individually or inparallel, as described below.This procedure describes how to use the OSM Low-Level Link to update the CLIM software onall CLIMs in parallel. This applies only to NonStop systems running H- or J-series software andshould only be used if you cannot use the CLIM Management Tool.

NOTE: This procedure requires two NonStop system consoles (NSCs).

Upgrading CLIM Software or Firmware While the System is Down 161

1. Install CLIM software on both NSCs.You will update half of the CLIMs using the first NSC and the other half using the secondNSC.

2. From each NSC, start multiple OSM Low-Level Link sessions, one for each CLIM to beupdated.

3. For each OSM Low-Level Link session:a. From the initial pop-up dialog, select Software Update and click OK.b. In the Software Update dialog box, enter the IP address of the NSC.c. Select the software version to use for the update from the Available Versions drop-down

menu and click Update.d. Upon completion, a dialog box appears stating that the update is complete, a CLIM

reboot is required for the updates to take effect. Click OK to dismiss the dialog.

e. In the Software Update dialog box, click Reboot.

NOTE: The OSM Low-Level link automatically logs you off after the reboot.

Update CLIM Firmware on a Down SystemTo update all CLIM firmware while the system is down, having completed the action prescribedin “Prepare CLIMs for Down System Firmware Update” (page 161) before halting all processors:• For L-series, use the CLIM Management Tool, which is launched from the Windows Start

menu by selecting All Programs > HP OSM > CLIM Management Tool.• For H- and J-series, use the CLIM Management Tool if you have met the prerequisites

described in “Upgrading CLIM Software and Firmware” (page 128). If not, you can use theDown System CLIM Firmware Update Tool, which is launched from the Windows Start menuby selecting All Programs > HP OSM > Down System CLIM Firmware Update Tool.

For more information on using the tools, see the online help available from within the tool.When the firmware updates have completed, the OSM tool you used reboots all CLIMs thatrequire a reboot. You can now “Load the System” (page 162).

Load the SystemWhen all CLIM firmware updates have completed and the CLIM Management Tool or DownSystem CLIM Firmware Update Tool has rebooted any CLIMs that require a reboot, load theNonStop system as described in the applicable software installation and upgrade guide associatedwith your CIP RVU.Use the OSM Service Connection Multi-Resource Actions dialog box to confirm the CLIM firmwareversions.

Apply CLIM Hotfix Software PatchesFor CLIMs running the J06.20/L16.05 CLIM DVD, use the OSM CLIM Management Tool to applyany available hotfix software patches. Follow the instructions on the screen. You can use theSCF VERSION CLIM and SCF STATUS CLIM commands to display the patch version for aCLIM. You cannot use this tool to apply patches to CLIMs running older versions of the software.

162 Upgrading CIP

Falling Back to Conventional TCP/IP or NonStop TCP/IPv6NOTE: This section applies only to J-series and H-series RVUs.

This subsection provides fallback procedures for returning your system to use either conventionalTCP/IP or NonStop TCP/IPv6. In addition to reading these procedures, see “Managing theConfiguration Preservation” (page 105).

NOTE: Parallel Library TCP/IP fallback is not listed here as it requires that you fall back to aG-series RVU. This procedure assumes that you are on an H-series or J-series RVU.

Falling Back to Conventional TCP/IP or NonStop TCP/IPv61. Follow one of the shutdown procedures in this section to stop CIP.2. Switch over to the existing conventional TCP/IP or NonStop TCP/IPv6 environment.

Reset the DEFINEs, PARAMs, and transport-service provider name-set procedure calls foryour applications back to the conventional TCP/IP or TCP6SAM process name.a. Determine the name of your preferred transport-service provider name by using use

the LISTDEV command to obtain a list of running TCP/IP processes:> LISTDEV TCPIP

b. Change the transport-service provider name for Guardian and OSS applications to theconventional TCP/IP or TCP6SAM process by entering one of these commands:• ADD DEFINE =TCPIP^PROCESS^NAME, class map, file $tcpip-process-name

• PARAM TCPIP^PROCESS^NAME $tcpip-process-name

3. Change these procedure calls for Guardian and OSS socket applications:• socket_set_inet_name() (for Guardian applications)

• socket_transport_name_set() (for OSS applications)

Falling Back to Previous RVUs that Support the Multiple Providers perCLIM Feature

You can fall back to a previous RVU that is supported by Multiple Providers per CLIM, but keepan IP or IB CLIM at the new level if it is either configured with MULTIPROV OFF, or you installthe minimum SPRs to support the Multiple Providers per CLIM feature along with that RVU.Although Multiple Providers per CLIM support is supported with the L15.02/J06.14/H06.25 orsubsequent RVUs, you can also use Multiple Providers per CLIM on NonStop operating systemswith IP or IB CLIMs beginning with the J06.08/H06.19 RVUs with a defined set of SPRs. Referto the Cluster I/O Module (CLIM) Software Compatibility Reference for specific information onwhich SPRs are supported for each RVU.You only need to take fallback action on CLIMs configured with MULTIPROV ON. To determineif any CLIMs are configured in this manner, issue the SCF INFO CLIM $ZZCIP.* command.Delete the multiple provider associations and turn the MULTIPROV attribute off, as describedunder “Disabling the MULTIPROV Attribute” (page 122).

Falling Back to a Previous CLIM VersionIt should never be necessary to fall back to a previous CLIM version, but if you want to do so,have your service provider see the Reimaging or Downgrading a CLIM service procedure. If youhave to revert the software on the CLIMs during an RVU fallback, see the applicable softwareinstallation and upgrade guide associated with your CIP RVU. The procedures in those guidesaccount for the timing of CLIM fallback in the context of a system RVU fallback.

Falling Back to Conventional TCP/IP or NonStop TCP/IPv6 163

5 LUN Manager for Storage CLIMIn addition to this manual, see the SCF Reference Manual for the Storage Subsystem forcommands such as STATUS CLIM, INFO CLIM, and configuring a disk or tape through a CLIM.

Lunmgr CommandsThe lunmgr manages the LUN number assignments that the CLIM uses to communicate withthe NonStop host system. Command syntax for lunmgr is:CLIMCMD clim-name | IP-address -optionThe lunmgr accepts these command line options:

Approve CommandDisplays the next enclosure number assignment that requires approval and accepts approval orchange of the assigned number. Valid replies are y (approve), n (do not approve), or a base LUNnumber valid for the enclosure type. Yesall automatically approves all assignments at once.Verbose displays the enclosure table and enclosures present. The syntax is:-a [ yesall | verbose ] | --approve [ yesall | verbose ]

Valid user replies are:

Approvey

Do not approven

A base LUN number valid for the enclosure typelun

YesallAutomatically approves all assignments at once.

VerboseDisplays the enclosure table and enclosures present.

Binaryfind CommandFinds the physical identity and location of a device LUN. This command is like the --findcommand but produces a binary format output. It is not useful to an interactive user. The syntaxis:-b [lun] |--binaryfind [lun]

lunIs a decimal LUN number.

Clear CommandClears devices from the LUN table in kernel memory and blocks all subsequent lunmgr commandsexcept --unblock and --clear. If no slot is specified, the command clears the entire LUNtable. If a slot but no port is specified, the command clears all LUNs connected to the slot. Thisoption is used internally during maintenance procedures such as firmware replacement. NoNonStop I/O process should have any paths UP through the cleared port(s). The syntax is:-c [slot slotnum [port portnum]]| --clear [slot slotnum [port portnum]]

Delete CommandDeletes enclosure table entries but only if there are no corresponding device LUNs. If LUN isspecified, deletes one enclosure. If no LUN is specified, deletes all enclosures in the enclosuretable. Only enclosures without an existing device will be deleted. To remove existing devices,

164 LUN Manager for Storage CLIM

you can disconnect the SAS cable, remove disks from the slots or power off the disk enclosure.The syntax is:-d [lun]|--delete [lun]

lunIs a decimal LUN number.

If no lun is specified, deletes all enclosure table entries with no corresponding device LUNs.Confirms with "Are you sure?".

Enclosures CommandDisplays the enclosure table and enclosures present. The syntax is:-e |--enclosures

Example of lunmgr Enclosures CommandVerify that the CLIM can see the corresponding ESS port WWN and that it is in the CLIM'senclosure table with the lunmgr --e command.> CLIMCMD s1002532 lunmgr --enclosures

The system displays the enclosures. This example shows two ESS ports connected but not yetapproved into the enclosure table and one connected SAS disk enclosure that has been approved:-- Enclosure table --lun type stable address100 1 enclosure 500110a000781200-- Enclosures present --dev type stable address controller serial # revisionsda 2 port 50060e8004289406 slot 1, port 1sdw 2 port 50060e8004289416 slot 1, port 1sg63 1 enclosure 500110a000781200 slot 3, port 1, expander 1 SGA7060029 2.10

Type 1 is a SAS disk enclosure. Type 2 is an ESS port. You can identify the port WWNs of theESS in the stable-address column.

Find CommandFinds the physical identity of a device LUN. If no LUN is specified, find all devices. This providesadditional information which is not shown by --print. The syntax is:-f [lun] | --find [lun]

lunIs a decimal LUN number.

If no lun is specified, find all devices.

Example of lunmgr Find CommandTo obtain the Storage CLIM's LUN for the SCF ADD DISK command:> CLIMCMD s1002532 lunmgr --f

lunmgr displays the Storage CLIM's LUN:lun type controller location101 disk-sas slot 2, port 1, expander 1 enclosure ID 1 (#7CE407P22M), bay 1102 disk-sas slot 2, port 1, expander 1 enclosure ID 1 (#7CE407P22M), bay 2103 disk-sas slot 2, port 1, expander 1 enclosure ID 1 (#7CE407P22M), bay 31012 2 (disk-ess) slot 1, port 1 port 50060e8004289406, lun 12 (0xc)1513 2 (disk-ess) slot 1, port 1 port 50060e8004289416, lun 13 (0xd)

The LUN shown on the left (under lun) is the Storage CLIM's LUN that you use in the SCF ADDDISK command. The port and LUN on the right (under location) are the ESS's port WWN andLUN.

Help CommandDisplays a list of valid lunmgr options and effects. The syntax is:

Lunmgr Commands 165

-h | --help

led CommandTurns on or off an enclosure or disk locator LED. The syntax is:-l lun { on | off } |--led lun { on | off }

lunIs a decimal LUN number.

Print CommandDisplays a device LUN table entry from kernel memory. If no LUN is specified, display the entiredevice LUN table. The syntax is:-p [lun]| --print [lun]

If no lun is specified, find all devices.

Renumber CommandRenumber an old enclosure base LUN to a new value. Lunmgr rejects this command if any devicein the old enclosure has an I/O operation outstanding or there is already an enclosure with thenew LUN value. The syntax is:-r old new | --renumber old new

oldIs the old LUN value.

newIs the new LUN value.

If any device in old enclosure has an I/O outstanding or there is already an entry for new, returnsan error. Confirms with "Are you sure?".

Scan CommandScan all HBA ports for new devices. This option should be used after you create new ESS LUNsor new virtual tapes in a VTS so that the CLIM sees the new device LUNs. The syntax is:-s | --scan

Startover CommandClears the device LUN table, enclosure table, and enclosure LCDs. If the existing enclosure tableis significantly different from what is desired, then --startover followed by --approve maybe simpler to use than several --delete and --renumber commands. The syntax is:--startover

Unblock CommandUnblocks lunmgr so that all subsequent lunmgr commands are allowed. If multiple --clearcommands have been entered, then an equal number of --unblock commands must be enteredbefore other commands, including --update, are allowed. The syntax is:--unblock

Update CommandFinds new storage devices and assigns new device LUN numbers to them. The verbose optiondisplays the device table and devices present. This option is used internally whenever devices

166 LUN Manager for Storage CLIM

are added or removed, so it is rarely necessary to use --update interactively. The --approveand --unblock options automatically perform an --update.

• Recognizes and ignores non-storage devices.

• Recognizes known devices by stable attributes and updates volatile I/O address.

• Assigns new Storage CLIM LUN numbers to previously unknown storage devices.The syntax is:-u [ verbose ]| --update [ verbose ]

VerboseDisplays the device table and devices present.

Considerations for the Update CommandOnly 1024 LUNs are supported. If the device table is full, lunmgr displays this error message onthe screen and in the NonStop host system EMS log:Can't add lun lun_number. 1024 devices already in table.

L-series Storage CLIMs support 1024 LUNs and H- and J-series Storage CLIMs support 512LUNs and . The recovery is to make fewer LUNs visible to the CLIM by ESS or SAN switchzoning.

WWNs CommandDisplays the WWNs of all fibre channel HBA ports. The syntax is:-w | --wwns

Lunmgr Commands 167

6 IP CIP Migration, Compatibility and OperationalDifferences

The same methods of specifying a NonStop TCP/IPv6 transport-service provider are availablefor CIP. Once CIP is installed, applications can use CIP by specifying a CIPSAM process nameas their transport-service provider. An application can change transport-service providers whilerunning and can also have sockets using conventional NonStop TCP/IP, NonStop TCP/IPv6 andCIP at the same time. (Parallel Library TCP/IP cannot co-exist with NonStop TCP/IPv6.)This chapter covers:

• “Summary of High-Level Differences Between Previous TCP/IP Subsystems and CIP”

• “Operational Differences Between Previous TCP/IP Subsystems and CIP” (page 169)

• “Application Programming Differences Between NonStop TCP/IPv6 and CIP” (page 182)

• “TCP/IP Attributes in CIP” (page 188)

• “How to Migrate From NonStop TCP/IP or NonStop TCP/IPv6 to CIP” (page 197)For high-level comparisons of all NonStop networking products, see the NonStop NetworkingOverview.

Summary of High-Level Differences Between Previous TCP/IPSubsystems and CIP

Table 17 summarizes the differences between conventional TCP/IP, Parallel Library TCP/IP,NonStopTCP/IPv6, and CIP.

NOTE: To find out which servers support these subsystems, see the planning guide for yoursystem or the NonStop Networking Overview.

Table 17 High-Level Differences Between Conventional TCP/IP, Parallel Library TCP/IP,NonStop TCP/IPv6, and CIP

CIPNonStop TCP/IPv6Parallel Library TCP/IPConventional TCP/IP

Supported interface types:Ethernet (Gigabit) withJumbo frames

Supported interface types:Ethernet (Ethernet, FastEthernet, Gigabit Ethernetwith Jumbo frames)

Supported interface types:Ethernet (Ethernet, FastEthernet, Gigabit Ethernetwith Jumbo frames)

Supported interface types:

• ATM

• Ethernet (Ethernet, FastEthernet, GigabitEthernet without Jumboframes)

• SNAP (token-ring orEthernet)

• X.25

System configurationdatabase: Supports

System configurationdatabase: Supports

System configurationdatabase: Supports

System configurationdatabase: Does not support

Subsystem name: CIPSubsystem name: TCPIPV6Subsystem name: PTCPIPSubsystem name: TCPIP

transport-service providername: Any CIPSAM process

transport-service providername: Any TCP6SAM

transport-service providername: Any TCPSAM

Transport-service providername: ($ZTC0 default) or

name. ($ZTC0 default)Program name is CIPSAM.

process name. ($ZTC0default) Program name isTCP6SAM

process name. ($ZTC0default). Program name isTCPSAM.

any TCP/IP process name.Program name is TCPIP

SPI subsystem ID: ZCIPSPI subsystem ID: ZTC6SPI subsystem ID: ZTCPSPI subsystem ID: ZTCI

SPI subsystem number: 259SPI subsystem number: 246SPI subsystem number:220

SPI subsystem number: 80

168 IP CIP Migration, Compatibility and Operational Differences

Table 17 High-Level Differences Between Conventional TCP/IP, Parallel Library TCP/IP,NonStop TCP/IPv6, and CIP (continued)

CIPNonStop TCP/IPv6Parallel Library TCP/IPConventional TCP/IP

Transport service providerprocess: CIPSAM PROCESSobject

Transport service providerprocess: TCP6SAMPROCESS object

Transport service providerprocess: TCPSAMPROCESS object

Transport service providerprocess: TCP/IP PROCESSobject

TCP/IP and SCTP (see“Configuring Stream Control

TCP/IPTCP/IPSupported protocols

Transmission Protocol(SCTP) (IP and Telco CIP)”(page 104))

Operational Differences Between Previous TCP/IP Subsystems and CIPSeveral operational differences exist between CIP and previous NonStop host system TCP/IPsubsystems. The main differences are:

• CIP does not use the ServerNet LAN Systems Access (SLSA) subsystem.

• Routing configuration and behavior are different.

• IPSec is a new feature supported in CIP.

• The SUBNET object is only provided as a subordinate object for the CIPSAM (transportprovider) object for application backward-compatibility. You do not configure the SUBNET.

• There is no neighbor discovery and autoconfiguration (ND6HOSTD) process. In NonStopTCP/IPv6, the ND6HOSTD process received and processed IPv6 router advertisement (RA)packets and updated the global IPv6 address information in the DNS. You could use it forupdating the DNS with automatically generated IPv6 addresses.

• The SNMP TCP/IP subagent (TCPIPSA) is not supported and therefore you cannot collectinformation on the CLIM from the NonStop SNMP agent.

• The CIP operational interface is significantly different. Table 18: Subsystem TaskComparisonshows how conventional NonStop TCP/IP, Parallel Library TCP/IP, and NonStopTCP/IPv6 tasks are performed in CIP.

Table 18 Subsystem Task Comparison

In CIP, Use...In Parallel Library TCP/IPand NonStop TCP/IPv6,Use...

In Conventional TCP/IP,Use...

Task

SCF ABORT CLIM commandSLSA SCF ABORTADAPTER command

SLSA SCF ABORT SACcommand

Abort adapter(or module)

SCF ABORT PROCESS$ZZKRN.#CIPMON or

SCF ABORT PROCESS$ZZKRN.#TCPMON or

No equivalentAbort a MONobject

ABORT MON$ZZCIP.#ZCMnn

ABORT MON$ZZTCP.#ZPTMn

SCF ABORT PROCESS$ZZCIP command

SCF ABORT PROCESS$ZZTCP command

No equivalentAbort MANprocess

SCF ABORT PROVIDER$ZZCIP.provider-name

SCF ABORT PROCESS$TCP6SAM-process-name

SCF ABORT PROCESSTCP/IPprocess-namecommand

Abort transportservice providerprocess

CLIMCMD clim-nameclimconfig route - delete

SCF ABORT ROUTEcommand

SCF ABORT ROUTEcommand

Abort a networkroute.

command. In CIP, there is noneed to stop a route beforedeleting it

Operational Differences Between Previous TCP/IP Subsystems and CIP 169

Table 18 Subsystem Task Comparison (continued)

In CIP, Use...In Parallel Library TCP/IPand NonStop TCP/IPv6,Use...

In Conventional TCP/IP,Use...

Task

CLIMCMD clim-name ifstopinterface command

SCF ABORT SUBNETcommand

SCF ABORT SUBNETcommand

Abort a networkinterface frombeing used bythe subsystem.

SCF ABORT PROVIDERcommand

No equivalentNo equivalentAbort Provider

ADD PROCESS$ZZKRN.#ZZCIP command

SCF ADD PROCESS$ZZKRN.#ZZTCP command

No equivalentAdd a Managerprocess

ADD PROCESS$ZZKRN.#CIPMON command

No equivalentNo equivalentAdd a Monitorprocess

CLIMCMD clim-nameclimconfig interface -addcommand

SCF ADD SUBNET commandSCF ADD SUBNETcommand

Add a networkinterface

CLIMCMD clim-nameclimconfig arp -add command

SCF ADD ENTRY commandSCF ADD ENTRY commandAdd an entry inthe ARP table

CLIMCMD clim-nameclimconfig route -addcommand

SCF ADD ROUTE commandSCF ADD ROUTE commandAdd a networkroute

SCF ADD ROUTE commandNo equivalentNo equivalentAdd ahost-to-CLIMroute

No equivalentNo equivalentSCF ADD ADDRMAPcommand

Add addrmapobject

No equivalentNo equivalentSCF ADD SERVERcommand

Add serverobject

SCF ADD PROVIDERcommand

ADD SUBNET, LNPTPLISTNo equivalentAdd providerobject

SCF ADD CLIM commandSLSA SCF ADD ADAPTERSLSA SCF ADD ADAPTERAdd an adapter(or module)

CLIMCMD clim-nameclimconfig interface -modify

SCF ALTER SUBNETcommand

SCF ALTER SUBNETcommand

Alter attributevalues of anetwork interface command to change jumbo

frames and netmask. All otherattributes must be changed byusing the CLIMCMDclim-name | ip-addressclimconfig sysctl command.

SCF ALTER PROVIDERcommand and CLIMCMD

SCF ALTER MON commandSCF ALTER PROCESScommand

Alter networkenvironmentattributes sysctl command. (See

Chapter 3 (page 59) forinformation about thiscommand.

SCF ALTER PROVIDERcommand

No equivalentNo equivalentAlter providerobject

SCF DELETE and ADDROUTE commands

No equivalentNo equivalentAlter path to theCLIM

170 IP CIP Migration, Compatibility and Operational Differences

Table 18 Subsystem Task Comparison (continued)

In CIP, Use...In Parallel Library TCP/IPand NonStop TCP/IPv6,Use...

In Conventional TCP/IP,Use...

Task

CLIMCMD clim-nameclimconfig arp -deletecommand

SCF DELETE ENTRYcommand

SCF DELETE ENTRYcommand

Delete ARPentries

SCF DELETE ROUTEcommand

No equivalentNo equivalentDelete ahost-to-CLIMroute

SCF DELETE CLIM commandSLSA DELETE ADAPTERSLSA DELETE ADAPTERDelete adapter(or module)

SCF DELETE PROVIDERcommand

No equivalentNo equivalentDeletePROVIDERobject

CLIMCMD clim-nameclimconfig route -deletecommand

SCF DELETE ROUTEcommand

SCF DELETE ROUTEcommand

Delete networkroute

No equivalentNo equivalentSCF DELETE ADDRMAPcommand

DeleteADDRMAPobject

No equivalentNo equivalentSCF DELETE SERVERcommand

Delete SERVERobject

CLIMCMD clim-nameclimconfig interface -deletecommand

SCF DELETE SUBNETcommand

SCF DELETE SUBNETcommand

Delete networkinterface

CLIMCMD clim-nameclimconfig arp -info command

SCF INFO ENTRY commandSCF INFO ENTRYcommand

Get Info aboutentries in theARP table,neighbordiscovery codeor both

SCF INFO PROVIDERcommand for some variables

SCF INFO MON, DETAILcommand

SCF INFO PROCESS,DETAIL command

Get Info aboutnetworking

and CLIMCMD climconfigenvironmentsettings object -info commands,

depending on whichnetworking environmentsettings are needed.

No equivalentNo equivalentSCF INFO ADDRMAPcommand

Get Info aboutADDRMAPobject

CLIMCMD clim-nameclimconfig route -infocommand

SCF INFO ROUTE commandSCF INFO ROUTEcommand

Get Info aboutnetwork routes

No equivalentNo equivalentSCF INFO SERVERcommand

Get Info aboutthe SERVERobject

SCF INFO ROUTE commandNo equivalentNo equivalentGet Info aboutthe host-to-CLIMroute

SCF INFO PROVIDERcommand

INFO SUBNET commandLNP field

No equivalentGet Info aboutthe PROVIDERobject

Operational Differences Between Previous TCP/IP Subsystems and CIP 171

Table 18 Subsystem Task Comparison (continued)

In CIP, Use...In Parallel Library TCP/IPand NonStop TCP/IPv6,Use...

In Conventional TCP/IP,Use...

Task

SCF INFO PROCESScommand

SCF INFO PROCESScommand

No equivalentGet Info aboutthe MAN process

CLIMCMD clim-nameclimconfig route -infocommand

SCF INFO ROUTE commandSCF INFO ROUTEcommand

Get Info aboutcurrent attributesettings fornetwork routes

CLIMCMD clim-nameclimconfig interface -infocommand

SCF INFO SUBNETcommand

SCF INFO SUBNETcommand

Get Info aboutcurrent attributesettings for anetwork interface

SCF INFO ROUTE commandNo equivalentNo equivalentGet Info aboutcurrent attributesettings forhost-to-CLIMroutes

SCF INFO CLIM commandSLSA INFO ADAPTER, INFOSAC, INFO PIF

SLSA INFO ADAPTER,INFO SAC, INFO PIF

Get Info aboutthe adapterconfiguration

SCF INFO PROVIDERcommand

INFO SUBNET commandLNP field

No equivalentGet Info aboutthe PROVIDERobject

SCF INFO PROCESScommand

SCF INFO PROCESScommand

SCF INFO PROCESScommand

Get Info aboutthe process

No equivalentNo equivalentSCF INFO ADDRMAPcommand

Get Info aboutthe ADDRMAPobject

No equivalentNo equivalentSCF INFO SERVERcommand

Get Info aboutthe SERVERobject

SCF LISTOPENS MONcommand

SCF LISTOPENS MONcommand

No equivalentList informationaboutapplications withopen sockets inCPUs withinwhich a specifiedMON is running

SCF LISTOPENS PROVIDERcommand

SCF LISTOPENS PROCESScommand (for CIPSAMprocess)

SCF LISTOPENSPROCESS command

List informationaboutapplications withopen socketsassociated with atransportprovider

SCF NAMES ROUTEcommand

No equivalentNo equivalentGet Names ofhost-to-CLIMroute names

No equivalent. Entries are notnamed.

SCF NAMES ENTRYcommand

SCF NAMES ENTRYcommand

Get Names ofENTRY objects

No equivalent. Network routesare not named.

SCF NAMES ROUTEcommand

SCF NAMES ROUTEcommand

Get Names ofnetwork routes

172 IP CIP Migration, Compatibility and Operational Differences

Table 18 Subsystem Task Comparison (continued)

In CIP, Use...In Parallel Library TCP/IPand NonStop TCP/IPv6,Use...

In Conventional TCP/IP,Use...

Task

CLIMCMD clim-nameclimconfig interface -info allcommand

SCF NAMES SUBNETcommand

SCF NAMES SUBNETcommand

Get Names ofnetwork interfacenames

SCF PRIMARY PROCESScommand

SCF PRIMARY PROCESScommand

SCF PRIMARY PROCESScommand

Make Primaryprocess thebackup processand makebackup processthe primaryprocess

SCF START PROCESS$ZZKRN.#CIPMON command

SCF START MON commandNo equivalentStart MONobjects on eachprocessor

SCF START CLIM commandSLSA SCF START ADAPTERcommand

SLSA SCF STARTADAPTER command

Start an adapter(or module) forhost operations

If stopped by ifstop,CLIMCMD clim-name ifstart

SCF START SUBNETcommand

SCF START SUBNETcommand

Start a networkinterface

command, otherwise SCFSTART CLIM

None (a network route isstarted when it is added)

SCF START ROUTESCF START ROUTEcommand

Start networkroutes

SCF START PROVIDERcommand

No equivalent, LNPs arestarted when configured

No equivalentStartPROVIDERobject

SCF STATS MON commandfor socket send size

SCF STATS MON commandSCF STATS PROCESScommand

GetStatistics onstatistics forprotocol layers histogram. Obtain other

statistics with the Linux netstat-s command by enteringCLIMCMD clim-namenetstat -s -n. For betterperformance, always use the–n option.

No equivalentSCF STATS PROCESS forTCP6SAM command

SCF STATS PROCESScommand

GetStatistics foratransport-providerprocess

No equivalentSCF STATS ROUTEcommand

SCF STATS ROUTEcommand

GetStatistics forspecified route

No equivalentSCF STATS SUBNETcommand

SCF STATS SUBNETcommand

GetStatistics ona specifiedSUBNET

SCF STATS CLIM commandNo equivalentNo equivalentGet Statisticsabout the CLIMobject in the CIPsubsystem

No equivalentNo equivalentSCF STATS ADDRMAPcommand

Get Statisticsabout theADDRMAPobject

Operational Differences Between Previous TCP/IP Subsystems and CIP 173

Table 18 Subsystem Task Comparison (continued)

In CIP, Use...In Parallel Library TCP/IPand NonStop TCP/IPv6,Use...

In Conventional TCP/IP,Use...

Task

No equivalentSCF STATUS ENTRYcommand

SCF STATUS ENTRYcommand

Get dynamicStatus of aspecified entry

climcmd climnamenetstat –s

SCF STATUS MONcommand

No equivalentGet dynamicStatus of a MONprocess

SCF STATUS PROCESS$ZZCIP for MAN process

SCF STATUS PROCESS$ZZTCP command for MANprocess

SCF STATUS PROCESSTCP/IPprocess-namecommand

Get Status onprimary andbackupprocesses

No equivalentSCF STATUS PROCESSTCP6SAM-name

SCF STATUS PROCESSTCP/IP process-name

Get Status onthetransport-serviceprovider

CLIMCMD clim-nameclimstatus -o l

SCF STATUS SUBNETcommand

SCF STATUS SUBNETcommand

Get Status on anetwork interface

None, routes have no statusSCF STATUS ROUTEcommand

SCF STATUS ROUTEcommand

Get Status onnetwork routes

SCF STATUS CLIMclim-name, CLIMCMD

SCF STATUS ADAPTER$ZZLAN.adapter-name

SCF STATUS ADAPTER$ZZLAN.adapter-name

Get Status onthe adapter (ormodule) clim-name climstatus and

CLIMCMDclim-name psclimcommands. See Chapter 3(page 59) for informationabout these CLIMCMDcommands.

SCF STATUS PROVIDERcommand

No equivalentNo equivalentGet Status onthe PROVIDERobject

No equivalentNo equivalentSCF STATUS SERVERcommand

Get Status onthe SERVERobject

SCF STOP PROCESScommand. If the process is

SCF STOP PROCESScommand. (If the process is

No equivalent task is neededas there is no MAN process

Stop a MANprocess

configured as persistent, theconfigured as persistent, theABORT command must beSTOP command must beissued to the Kernelissued to the kernelsubsystem or the persistencesubsystem or the persistence

manager restarts it.) manager restarts it. See“Starting and Restarting CIP”(page 91). If there are opensockets, you ABORTPROCESS, FORCEDcommand.

SCF STOP MON if no opensockets, otherwise, ABORT

SCF STOP MON commandNo equivalent task is neededas there is no MON process

Stop a MONprocess

MON, FORCED command. (Ifthe process is configured aspersistent, the ABORTcommand must be issued tothe Kernel subsystem or thepersistence manager restarts

174 IP CIP Migration, Compatibility and Operational Differences

Table 18 Subsystem Task Comparison (continued)

In CIP, Use...In Parallel Library TCP/IPand NonStop TCP/IPv6,Use...

In Conventional TCP/IP,Use...

Task

it. See “Starting andRestarting CIP” (page 91).

CLIMCMD clim-name ifstopcommand

SCF STOP SUBNETcommand

SCF STOP SUBNETcommand

Stop a networkinterface

None, delete route withCLIMCMD climconfig route-delete command

SCF STOP ROUTEcommand

SCF STOP ROUTEcommand

Stop a networkroute

SCF STOP CLIM if no opensockets, otherwise, ABORTCLIM, FORCED command

SLSA SCF STOP ADAPTERcommand

SLSA SCF STOP ADAPTERcommand

Stop an adapter(or module)

SCF STOP PROCESSCIPSAM process-name. If

SCF STOP PROCESSTCP6SAM process-name

SCF STOP PROCESSTCP/IP process-name

Stopa transport-

persistent, SCF ABORTservice- PROCESS

$ZZKRN.#CIPSAM. Ifproviderpersistent and you only wantprocess to stop one CIPSAM process,you can stop it implicitly bystopping the PROVIDERobject upon which theCIPSAM process depends.

SCF STOP PROVIDER if noopen sockets, otherwise,

No equivalentNo equivalentStop aPROVIDERobject ABORT PROVIDER,

FORCED command

SCF SWITCH CLIMcommand

No equivalentNo equivalentSwitch the CLIM

CLIMCMD clim-nametcpdump (See the man page

SCF TRACE SUBNETcommand

SCF TRACE SUBNETcommand

Trace IPinterfaces

for information abouttcpdump.)

SCF TRACE PROCESScommand (traces theManager process)

SCF TRACE PROCESScommand

SCF TRACE PROCESScommand

Trace a process

SCF TRACE MON commandSCF TRACE MON commandNo equivalentTrace a MONprocess activities

SCF TRACE PROVIDERcommand (only one providerin a processor can be traced)

No equivalentNo equivalentTracePROVIDERobject

SCF TRACE CLIM commandNo equivalentNo equivalentTrace CLIMobject

SCF VERSION PROCESScommand

SCF VERSION PROCESScommand

No equivalentGet Versionlevel of MANprocess

SCF VERSION CLIMcommand

No equivalentNo equivalentGet Version ofthe CLIMsoftware

SCF VERSION MONcommand

SCF VERSION MONcommand

No equivalentGet Versionlevel of the MONobject

Operational Differences Between Previous TCP/IP Subsystems and CIP 175

SLSA SubsystemCIP does not use the SLSA subsystem. In conventional TCP/IP, Parallel Library TCP/IP andNonStop TCP/IPv6, there were two things you needed to do with the SLSA subsystem: Ensurethat it was running before you started using TCP/IP and associate a specific network interfacewith your TCP/IP transport-provider process. In the previous subsystems, you could use theSLSA DEVICENAME attribute of the SUBNET object to specify which interface the TCP/IPtransport-provider process would use to send and receive data.In CIP, there is no underlying subsystem that you have to ensure is running.In CIP, you can associate a transport-provider process (CIPSAM) with a CLIM but not with asingle interface on a CLIM. You associate a network CLIM with a Provider by using the PROVIDERattribute of the CLIM object. (A maintenance Provider can be associated with a CLIM but thereis no CLIM attribute for IP data Providers. See “ADD PROVIDER” (page 223) and “ADD ROUTE”(page 225).)

Network Partitioning DifferencesIn conventional TCP/IP, you can have multiple TCP/IP processes, each having one or moreinterfaces uniquely associated with it. In NonStop TCP/IPv6, you can configure the environmentto use logical-network partitioning, each partition having one or more interfaces uniquely associatedwith it.In CIP, with the MULTIPROV option OFF, you can use the SCF PROVIDER object for networkpartitioning but you can only restrict a whole CLIM to a Provider (partition). You cannot restrictindividual interfaces to a Provider. If you must associate an application with a specific IP address,bind the application to that IP address. Alternatively, you can use one interface or set of interfaceson a CLIM by just adding a subset of the possible physical interfaces (for example, eth1 andeth2).In CIP, with the MULTIPROV option ON, you can use the SCF PROVIDER object for networkpartitioning, with each PROVIDER having one or more interfaces on one or more CLIMs uniquelyassociated with it.

Confining Applications that Bind to INADDR_ANYServer applications that are not configured with a specific IP address to accept incoming TCP/IPrequests probably bind to INADDR_ANY. This allows the applications to accept requests on allIP addresses in the partition. You might be using network partitioning to confine such applicationsto a subset of the addresses on the system. However, many third-party applications can beconfigured to bind to a specific address so that they accept connections only to that address,much like binding to INADDR_ANY on a partition with one interface, as shown in this diagram:

For example, the TCP/IP parameters used by the iTP Secure WebServer are configured in theAccept command. If this command has no address option, the WebServer binds to INADDR_ANY.

176 IP CIP Migration, Compatibility and Operational Differences

However, if you add an address option with an IP address, the WebServer binds just to thataddress.

Routing DifferencesThe SCF ROUTE object plays a different role in the CIP environment than it did in the previoussubsystem environments. In the CIP subsystem, the ROUTE object allows you to prioritize theCLIM(s) to use when no specific route matching the destination is configured on any CLIM in theProvider. In the previous subsystems, the ROUTE object allowed you to specify a route for thefirst hop on the network. To specify a route for the first hop on the network in CIP, use theclimconfig route commands.

Failover Differences (Fault Tolerance)There are two forms of failover in CIP: CLIM-to-CLIM failover and interface-to-interface failover.CLIM-to-CLIM failover allows an interface on a CLIM to fail over to an interface on another CLIM.Interface-to-interface failover is provided by the bonding feature. Use the CLIMCMD Climconfigcommands to establish failover between interfaces on a CLIM and between interfaces on twodifferent CLIMs.Bonded interfaces share interface resources among multiple physical interfaces. They can beconfigured to be similar to NonStop TCP/IPv6 and Parallel Library TCP/IP failover with theSHAREDIP option, except that the interfaces must be in the same CLIM and are not limited tojust two interfaces.The NonStop TCP/IPv6 and Parallel Library TCP/IP NONSHAREDIP option is most similarCLIM-to-CLIM failover in that each interface has a different IP address until failover with someimportant differences.While most resources can be migrated during failover, some are lost if migration to a differentCLIM is required. Unlike NonStop TCP/IPv6 and Parallel Library TCP/IP, CIP does not migratesocketsthat have TCP or SCTP connections to the new CLIM. During a CLIM-to-CLIM failure,such sockets are closed and TCP or SCTP sessions lost. (For a description of interface resources,see “Failover in the CIP Subsystem” (page 31).Restoring resources to their home interface when it comes back up is not done automaticallyand requires you to issue an SCF SWITCH CLIM command. However, visiting resources usingan interface that fails do attempt restoration to their home interface automatically. The restoreprocedure is similar to a failover sequence in how it handles interface resource migration. See“CLIM Startup Behavior” (page 41) for information about how the CLIM manages recovery.For procedures for setting up bonded interfaces and CLIM-to-CLIM failover, see “ConfiguringBonded Interface Failover (IP CIP)” (page 86).

Differences That Affect Planning for CLIMs Instead of G4SAsIn CIP, there are differences from conventional TCP/IP and NonStop TCP/IPv6 in how the physicalinterfaces are divided among transport-service providers. These differences affect planningdecisions for the number of CLIMs needed to support some existing G4SA-based networkconfigurations.Each logical network partition (LNP) in NonStop TCP/IPv6 or conventional TCP/IP process canhave its own, independent set of resources (Ethernet interfaces). One interface on a G4SA canbe part of one partition or process while another interface can be part of another partition orinterface. The four different interfaces of one G4SA can belong to four different partitions orprocesses.In CIP, each Provider can include more than one CLIM but a CLIM cannot be divided amongdifferent Providers. Hence, all Ethernet interfaces on a CLIM can only belong to one Provider.

Operational Differences Between Previous TCP/IP Subsystems and CIP 177

If you had a network configuration with a G4SA split between four LNPs or TCP/IP processes,one interface on each, you may need to change your configuration set-up or add more CLIMsto achieve the same result.

IPv6 DifferencesAutomatic tunnels are not supported in CIP.

Fault Tolerant SocketsConventional TCP/IP is a NonStop process pair and therefore allows sockets to be transferredfrom an application in one processor to its backup on another. NonStop TCP/IPv6 and CIP donot support this socket feature.

Remote SocketsConventional TCP/IP is a process and can receive socket requests from remote NonStop systems.NonStop TCP/IPv6 does not support this feature, nor does CIP. The EXPANDSECURITY MONattribute is only useful if remote sockets are supported and hence is not supported in CIP.

New Error Codes when Using IPSecIf IPSec is being used, there might be some new error codes:

• EAGAIN is returned if there is no security association (SA) already established and an SAsetup is started between CIP and the client. (The connect receives an EAGAIN error.) Thenext connect that is done after the SA is established works fine.

• ESRCH is returned if the policy says that IPSec must be used, no keys have been enteredmanually, and racoon is not running.

Avoiding Interfaces With Link Pulse DownFor J06.04 to J06.09 and H06.16 to H06.20, conventional TCP/IP and NonStop TCP/IPv6 onlyselect interfaces that have link pulse up for sending connections or data. CIP does not check forlink pulse when selecting interfaces. If there are two interfaces (for example, eth2 and eth3)configured on the same subnet, and one interface loses link pulse, it is possible that the IP CLIMwill choose the interface that has link pulse down to send packets to that subnet. To avoid thisbehavior, either have the interface configured for failover or take the interface down (ifstop).Figure 13: Two Interfaces Connected To The Same Subnet (page 179) and Figure 14: Two CLIMsConnected to the Same Subnet (page 180) show configurations that may encounter routingproblems.Figure 13: Two Interfaces Connected To The Same Subnet shows subnet routes with thesecharacteristics:• There are two interfaces on the same IP subnet (A.0)

• Both interfaces have the same subnet route to the network

• eth3 is activated first (non-deterministic)

• The subnet route on eth3 is used for all outgoing connections to the network

• The route through eth3 continues to be used even after it has lost link pulseThe network becomes unreachable from a CLIM.

178 IP CIP Migration, Compatibility and Operational Differences

Figure 13 Two Interfaces Connected To The Same Subnet

Figure 14: Two CLIMs Connected to the Same Subnet shows subnet routes on two CLIMs:• There are two interfaces on two CLIMs of the provider on the same IP subnet (A.0)

• CLIMs are selected in round robin order for outgoing connections

• The route through CLIM B continues to be used even after it has lost link pulseThe network becomes unreachable for half of the outgoing connections.

Operational Differences Between Previous TCP/IP Subsystems and CIP 179

Figure 14 Two CLIMs Connected to the Same Subnet

As of L15.02 and later L-series RVUs, J06.10 and later J-series RVUs, and H06.21 and laterH-series RVUs, this problem has been fixed.

Error on Sockets When CIPSAM Process AbortsIn NonStop TCP/IPv6, when a SAM process is aborted, all existing sockets created using thatSAM return an error on the current or next operation. In CIP, when a SAM process is aborted,existing sockets continue unaffected, but no new sockets can be created. To obtain behaviorsimilar to NonStop TCP/IPv6, abort the Provider object.

Connecting to Non-Loopback Address after Binding to LoopbackConventional TCP/IP and NonStop TCP/IPv6 allow a socket bound to a loopback address toconnect to any local address, whether it is a loopback address or not. CIP allows such socketsonly to connect to a loopback address.

CIPSAM CommandsNonStop TCP/IPv6 provides a socket access method (SAM) SCF and SPI interface matchingthat of conventional TCP/IP for applications using that interface to get information about theTCP/IP subsystem. CIP also provides a SAM interface for the same reason, but supports fewercommands. Data that does not exist on CIP is displayed as dummy data for compatibility reasons.

180 IP CIP Migration, Compatibility and Operational Differences

The commands supported by NonStop TCP/IPv6 and those supported by CIP are:

SubnetRouteProcessCommand/Object

NonStop TCP/IPv6, CIPAbort

NonStop TCP/IPv6, CIPNonStop TCP/IPv6, , CIPNonstop TCP/IPv6, CIPInfo

NonStop TCP/IPv6Listopens

NonStop TCP/IPv6, CIPNonStop TCP/IPv6, , CIPNames

NonStop TCP/IPv6, CIPPrimary

NonStop TCP/IPv6NonStop TCP/IPv6NonStop TCP/IPv6Stats

NonStop TCP/IPv6, CIPNonStop TCP/IPv6NonStop TCP/IPv6Status

NonStop TCP/IPv6, CIPStop

NonStop TCP/IPv6, CIPTrace

NonStop TCP/IPv6, CIPVersion

Applications that expect the SAM process to have certain product numbers, versions, processname, or program name must be changed.

Configuring SWAN Adapters on a CLIMConfiguring SWAN adapters on a CLIM is the same as for standard IP, with one additional stepperformed on the Provider: the Provider must have the bootp receive port set. This is done withthe SCF ALTER PROVIDER command. In the following example, the SWAN TCP processes(Providers) are $ZTC0 and $ZTC1:24> alter prov $zzcip.ztc0, brecvport 6725> info prov $zzcip.ztc0, detail

CIP Detailed Info PROVIDER \NSBLDE6.$ZZCIP.ZTC0

*TPName.................... $ZTC0*Type...................... IPDATA*HostID.................... 0.0.0.0*Hostname.................. NSBLDE6*TCP-Listen-Que-Min........ 128*BRecvPort................. (67 )*Family.................... INET*Share-Ports............... 1000

Associated CLIMs:Name IndexC1002581 0

26> alter prov $zzcip.ztc1, brecvport 6727> info prov $zzcip.ztc1, detail

CIP Detailed Info PROVIDER \NSBLDE6.$ZZCIP.ZTC1

*TPName.................... $ZTC1*Type...................... IPDATA*HostID.................... 0.0.0.0*Hostname.................. NSBLDE6*TCP-Listen-Que-Min........ 128*BRecvPort................. (67 )*Family.................... INET*Share-Ports............... 1000

Operational Differences Between Previous TCP/IP Subsystems and CIP 181

Associated CLIMs:Name IndexC1002582 0

Application Programming Differences Between NonStop TCP/IPv6 andCIP

If your application makes sophisticated use of the NonStop TCP/IP, Parallel Library TCP/IP orTCP/IPv6 programming API, it may be affected by differences in the CIP API. Review this sectionto determine if your application might be affected. If the behavioral differences in the API do notactually result in real problems for your application, you can use the suppress-all-errors featureto allow your application to continue running in the case of minor differences in the CIPenvironment. See Suppressing Compatibility Errors.This section describes application features and behaviors that need to be changed for CIP. Topicsdescribed are:

• “Suppressing Compatibility Errors”

• “Bind to INADDR_ANY and a Specific Address on the Same Interface”

• “Changing Destination of a Connected UDP Socket”

• “Multicast Bind and Set or Join on Separate Interfaces”

• “Multicast Loopback”

• “Receiving Broadcasts on Specific Addresses”

• “Error after UDP Send to Unreachable Port” (page 184)

• “Conversion of Limited Broadcast to Subnet-Directed Broadcast” (page 184)

• “Round-Robin Socket Support Considerations”

• “Socket IOCTL Differences”

• “Socket Options”

• “Binding to a Recently Used Address and Port” (page 184)

Suppressing Compatibility ErrorsCIP does not support certain features supported by previous NonStop TCP/IP implementations.If you run an application in CIP that contains unsupported features, compatibility errors result.To allow applications not expecting these errors to run without modification, CIP supports aDEFINE to suppress errors caused by incompatibility:ADD DEFINE =CIP^COMPAT^ERROR, FILE SUPPRESS

If the DEFINE is set with a file name of “SUPPRESS” when an application starts, socket callsthat try to invoke a behavior allowed in a previous implementation but not in CIP return as ifsuccessful, even though the behavior did not occur as expected. If the DEFINE is not set or ifthe file name is not “SUPPRESS”, attempts to use behaviors that CIP does not support causesocket calls to return the appropriate error.

Bind to INADDR_ANY and a Specific Address on the Same InterfaceConventional TCP/IP and NonStop TCP/IPv6 consider a bind to INADDR_ANY on a TCP orSCTP socket to exclude IP addresses that are bound to a specific address in another socket, soit is allowed to have both a socket bound to INADDR_ANY and one bound to a specific addresson the same TCP or UDP port. CIP considers a bind to INADDR_ANY to include all IP addresses.If another socket is bound to a specific address on the same interface, an INADDR_ANY bindreceives an error.

182 IP CIP Migration, Compatibility and Operational Differences

In some cases, this incompatibility can be overcome by using one CLIM for applications usingspecific binds and another for INADDR_ANY binds, each in a different Provider. The only useof this feature that cannot be solved using more CLIMs is a server that binds to INADDR_ANYto act as a backup for other servers that each bind to a specific address.

Changing Destination of a Connected UDP SocketConventional TCP/IP and NonStop TCP/IPv6 select a local interface based on the destinationaddress for each connect operation done on an unbound UDP socket or one bound toINADDR_ANY. In CIP, once a connect operation is done on an unbound UDP socket or onebound to INADDR_ANY, the socket is implicitly bound to an address and interface on a CLIMthat has a route to the destination address. Subsequent connect operations are sent to the sameCLIM, even if it does not have a route to the new destination address. If the CLIM cannot reachthe destination, the application gets an EACCESS error. You can avoid a problem by ensuringthat all CLIMs in a Provider are configured with the same routes.

Multicast Bind and Set or Join on Separate InterfacesIn Conventional TCP/IP and NonStop TCP/IPv6, applications can bind (using the bind call) asocket to a multicast address on one interface, join (using the setsockopt call with the IP_ADD_MEMBERSHIP or IPV6_JOIN_GROUP option) a multicast group on another interface, and setthe multicast send interface (using the setsockopt with the IP_MULTICAST_IF orIPV6_MULTICAST_IF option) to yet another interface with no restrictions. In CIP, the interfacesthat are referred to for these operations must be on the same CLIM. Furthermore, each interfaceon a CLIM can fail over to a different CLIM, so CIP might need to rearrange the interfaces duringfailover. CIP requires binding as well as joining to a multicast group before receiving messagesfrom that group. If your applications use different interfaces for bind, join, and set, you need tochange them.

Multicast LoopbackIn Conventional TCP/IP and NonStop TCP/IPv6, an application that joins a multicast groupreceives data sent to that group even from the same interface or controller.In CIP, for IPv4, if the interfaces are on the same CLIM, an application will not receive the dataunless the sender sets the IP_MULTICAST_LOOP socket option and joins the receiver's multicastgroup. For IPv6, an application receives the data regardless of whether the sender sets theIP_MULTICAST_LOOP option and has joined the receiver's multicast group.

Receiving Broadcasts on Specific AddressesNonStop TCP/IPv6 and Conventional TCP/IP route incoming broadcast packets (IP Address255.255.255.255) to sockets bound to a specific IP address. CIP does not support this behavior.CIP has a Provider attribute that gives a list of the port numbers requiring emulation of the olderbehavior:BRECVPORT port [, port] …

This attribute specifies the UDP ports to receive broadcast messages on sockets bound to specificIP addresses as well as INADDR_ANY. Up to eight port numbers can be specified, each a portnumber not in the ephemeral or shared-port ranges. Ports not in the list can receive broadcastmessages only on sockets bound to INADDR_ANY.This attribute adds a configuration step, but makes application changes unnecessary. See “ADDPROVIDER” (page 223) and “ALTER PROVIDER” (page 227) for BRECVPORT syntax.

NOTE: BRECVPORT is not supported with CLIM-to-CLIM failover.

Application Programming Differences Between NonStop TCP/IPv6 and CIP 183

Error after UDP Send to Unreachable PortIf a UDP message is sent to an unreachable port, the resulting ICMP error always causesConventional TCP/IP and NonStop TCP/IPv6 to return an error on the next request. CIP sometimesdoes not return an error at all or returns the error on a subsequent request.

Conversion of Limited Broadcast to Subnet-Directed BroadcastIf the destination address is the limited broadcast address (255.255.255.255), conventionalTCP/IP and NonStop TCP/IPv6 convert the address to a subnet-directed broadcast address (thespecific subnetid and hostid are all ones) whether the socket is bound or unbound. CIP does thisconversion only if the socket is unbound.

Binding to a Recently Used Address and PortConventional TCP/IP and NonStop TCP/IPv6 allowed immediate reuse of an address and portif the SO_REUSEADDR socket option is set on the next use. CIP requires that theSO_REUSEADDR option be set on both the previous and next use. If the SO_REUSEADDRoption is not set on both the previous and next use, there can be a delay of up to several minutesthe address and port can be reused.

Round-Robin Socket Support ConsiderationsThe NonStop TCP/IPv6 and Parallel Library TCP/IP round-robin filtering feature introducedconsiderations for applications and some of these considerations also apply to CIP:

• If the first application that binds to a TCP or UDP port using round-robin filtering is a privilegeduser (for example, a super-group user), all further applications sharing the port must alsobe privileged.

• All applications must bind using the same family value (for example, AF_INET or AF_INET6).

• If your application uses round robin sockets where the same a TCP or UDP port is sharedbetween an IPv4 socket and an IPv6 socket, you must change the application to use differentTCP or UDPs for the different address families. Mixed family sockets cannot share the sameTCP or UDP.

Socket IOCTL DifferencesThis section documents the changes to IOCTL commands that can be issued from the Guardianlibrary calls socket_ioctl and socket_ioctl_nw and the Open System Services (OSS) system callioctl.

Adding and Deleting Routes by NameSIOCADDRT (add route) and SIOCDELRT (delete route) behave differently in CIP.Conventional TCP/IP and NonStop TCP/IPv6 can use route names to identify routes as well asaddresses. CIP does not have route names. CIP can add routes, but does not save or assign aroute name, so route names cannot be used to identify a route for deleting. If a route name isused with SIOCDELRT, the request is ignored if the compatibility error DEFINE is SUPPRESSor else returns an error.

Deleting ARP EntriesSIOCDARP (delete ARP entry) behaves differently.When an ARP table entry is deleted using an IOCTL command in conventional TCP/IP or NonStopTCP/IPv6, the entry is completely removed. CIP retains the entry, but shows its HW addressfield as incomplete.

184 IP CIP Migration, Compatibility and Operational Differences

Getting Netmask and Broadcast Address on IPv6 SocketsSIOCGIFBRDADDR (get broadcast address) and SIOCGIFNETMASK (get network addressmask) are supported differently in CIP, for IPv6 sockets.NonStop TCP/IPv6 allows these IOCTL commands on IPv4 and IPv6 sockets, but on IPv6 sockets,NonStop TCP/IPv6 returns IPv4 addresses. CIP does not support the operation on IPv6 socketsat all.

Socket OptionsSome socket options that are supported by NonStop TCP/IPv6 are not supported by or havechanged with CIP and require application changes. These options are set by the Guardiansetsockopt, setsockopt_nw library calls or the OSS setcsockopt system call.

Socket Options Supported DifferentlyThese socket options are supported differently in CIP:

Level IPPROTO_TCPThis TCP_SACKENA socket option for level IPPROTO_TCP, which enables TCP selectiveacknowledgements, is supported differently in CIP. Use the CLIMCMD {clim–name |ip–address} climconfig sysctl command to set the net.ipv4.tcp_sack parameter.

SO_PMTUThis socket option, which turns path discovery on and off, is not supported in CIP. Use theCLIMCMD {clim–name | ip–address} climconfig sysctl command to change thenet.ipv4.ip_no_pmtu_disc parameter.The SO_PMTU

TCP_RXMTCNTCIP does not support the socket option TCP_RXMTCNT but you can configure the interfaces toachieve the same result. Use the CLIMCMD {clim–name | ip–address} climconfig sysctlcommand to change the net.ipv4.tcp_retries2 parameter.

Unsupported Socket OptionsThese socket options are not supported by CIP.

Level IPPROTO_TCPSome NonStop TCP/IPv6 socket options for level IPPROTO_TCP are not supported by CIP:

• TCP_DROP_IDLEThis socket option, which was supported but not documented, is no longer supported. SeeTable 19 (page 187) for default behavior.

• IP_RECVDSTADDRThis socket option, which was supported but not documented, is no longer supported. SeeTable 19: Differences in Socket Options Defaults (page 187) for default behavior.

• TCP_KEEPINITThis socket option, which was supported but not documented, is no longer supported. SeeTable 19: Differences in Socket Options Defaults (page 187) for default behavior.

• TCP_MINRXMTThe TCP_MINRXMT socket option, which sets the minimum time for TCP retransmissiontimeouts is not supported in CIP.

Application Programming Differences Between NonStop TCP/IPv6 and CIP 185

• TCP_MAXRXMTThe TCP_MAXRXMT socket option, which sets the maximum time for TCP retransmissiontimeouts, is not supported in CIP.

• TCP_NODELACKThis socket option, which was supported but not documented, is no longer supported. SeeTable 19: Differences in Socket Options Defaults (page 187) for default behavior.

• TCP_PAWSThis socket option, which was supported but not documented, is no longer supported. SeeTable 19: Differences in Socket Options Defaults (page 187) for default behavior.

• TCP_PROBE_IDLEThis socket option, which was supported but not documented, is no longer supported. SeeTable 19: Differences in Socket Options Defaults (page 187) for default behavior.

• TCP_PUSHThis socket option, which was supported but not documented, is no longer supported. SeeTable 19: Differences in Socket Options Defaults (page 187) for default behavior.

• TCP_RXMTCNTThis socket option, which set the maximum time for a TCP retransmission timeout, is notsupported. See Table 19: Differences in Socket Options Defaults (page 187) for defaultbehavior.

• TCP_RPTR2RXTThis socket option, which was supported but not documented, is no longer supported. SeeTable 19: Differences in Socket Options Defaults (page 187) for default behavior.

• TCP_SACKENAThis socket option, which enabled TCP selective acknowledgements, is not supported. SeeTable 19: Differences in Socket Options Defaults (page 187) for default behavior.

• TCP_TOTRXMTVALThe TCP_TOTRXMTVAL socket option, which sets the maximum continuous time spentretransmitting without receiving an acknowledgement from the other endpoint, is not supportedin CIP.

• TCP_TSOPTENAThis socket option, which was supported but not documented, is no longer supported. SeeTable 19: Differences in Socket Options Defaults (page 187) for default behavior.

Level SOL_SOCKET

• SO_DONTROUTEThis socket option, which specifies not to route messages, is not supported. See Table 19:Differences in Socket Options Defaults (page 187) for default behavior.

• SO_PMTUThis socket option, which was supported but not documented, is no longer supported. SeeTable 19: Differences in Socket Options Defaults (page 187) for default behavior.

• SO_USELOOPBACKThis socket option, which was supported but not documented, is no longer supported. SeeTable 19: Differences in Socket Options Defaults (page 187) for default behavior.

186 IP CIP Migration, Compatibility and Operational Differences

New Socket Option SO_ACCPTCONNThe SO_ACCEPTCONN socket option is not supported by conventional TCP/IP or TCP/IPv6, butis supported by CIP.

Different Socket Options DefaultsTable 19 Differences in Socket Options Defaults

CIP Default

Previous TCP/IPSubsystemDefaultSocket OptionLevel

0SO_BROADCASTSOL_SOCKET

88000*61440SO_SNDBUFSOL_SOCKET

88000*61440SO_RCVBUFSOL_SOCKET

ENOPROTOOPT (With compatibilitydefine returns 0)

0TCP_SACKENAIPPROTO_TCP

ENOPROTOOPT (With compatibilitydefine returns 2)

2TCP_MINRXMTIPPROTO_TCP

ENOPROTOOPT (With compatibilitydefine returns 128)

128TCP_MAXRXMTIPPROTO_TCP

ENOPROTOOPT (With compatibilitydefine returns 12)

12TCP_RXMTCNTIPPROTO_TCP

ENOPROTOOPT (With compatibilitydefine returns 1440)

1440TCP_TOTRXMTVALIPPROTO_TCP

ENOPROTOOPT (With compatibilitydefine returns 0)

0SO_USELOOPBACKSOL_SOCKET

ENOPROTOOPT (With compatibilitydefine returns 0)

0TCP_RPTR2RXTIPPROTO_TCP

ENOPROTOOPT (With compatibilitydefine returns 75)

75TCP_KEEPINITIPPROTO_TCP

ENOPROTOOPT (With compatibilitydefine returns 0)

0TCP_PUSHIPPROTO_TCP

ENOPROTOOPT (With compatibilitydefine returns 0)

0TCP_NODELACKIPPROTO_TCP

ENOPROTOOPT (With compatibilitydefine returns 0)

UnsupportedTCP_TSOPTENAIPPROTO_TCP

ENOPROTOOPT (With compatibilitydefine returns 20)

20TCP_PAWSIPPROTO_TCP

ENOPROTOOPT (With compatibilitydefine returns 75)

75TCP_PROBE_IDLEIPPROTO_TCP

ENOPROTOOPT (With compatibilitydefine returns 600)

600TCP_DROP_IDLEIPPROTO_TCP

ENOPROTOOPT (With compatibilitydefine returns 0)

0IP_RECVDSTADDRIPPROTO_IP,IPPROTO_IPV6

ENOPROTOOPT (With compatibilitydefine returns 0) See “TCPPATHMTU”

0SO_PMTUSOL_SOCKET

(page 191) for procedures on how to setthe interface to provide this functionality.

*See “TCPRECVSPACE” (page 191) and “INITIAL-TTL” (page 189) for information about changing these defaults byusing the CLIMCMD {clim–name | ip–address} climconfig sysctl command.

Application Programming Differences Between NonStop TCP/IPv6 and CIP 187

TCP/IP Attributes in CIPSome conventional TCP/IP process and Parallel Library TCP/IP and NonStop TCP/IPv6 MONattributes are not supported in CIP and some are supported differently.

NonStop TCP/IPv6 Attributes and Their CIP EquivalentsMany of the TCP/IP stack environment variables that you set by using attributes in the NonStopTCP/IPv6 ALTER MON/SUBNET command are now set in the CLIM environment. This subsectionlists the attributes that you can configure on the NonStop TCP/IPv6 TCP6MON/SUBNET processand an equivalent way of configuring that attribute in CIP. The following table shows NonStopTCP/IPv6 attributes and the equivalent CIP action required to achieve the same result. ForNonStop TCP/IP attributes and their CIP equivalents, including default, minimum, and maximumvalues, see Table 20: TCP/IP Attribute Default Values and Ranges (page 194).

Do this in CIP:If you use this MON/SUBNET attribute in TCP/IPv6:

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.ipv4.ip_default_ttlvalue

“INITIAL-TTL” (page 189)

ADD PROVIDER“HOSTID” (page 189)

ADD PROVIDER“HOSTNAME” (page 190)

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.ipv4.ip_local_port_range'value value'

NOTE: Changes to this sysctl parameter must be madeon all CLIMs that share the same Provider. Also, allproviders sharing a CLIM must similarly share that sysctlvalue.

“MIN-EPHEMERAL-PORT, MAX-EPHEMERAL-PORT”(page 190)

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.ipv4.tcp_window_scalingvalue

“RFC1323-ENABLE” (page 190)

CLIMCMD {clim–name | ip–address} climconfigsysctl -updatenet.ipv4.tcp_keepalive_probes value

“TCPKEEPCNT” (page 190)

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.ipv4.tcp_keepalive_timevalue

“TCPKEEPIDLE” (page 190)

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.ipv4.tcp_keepalive_intvlvalue

“TCPKEEPINTVL” (page 190)

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.ipv4.tcp_retries2 value

“TCP-MAX-REXMIT-COUNT” (page 191)

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.ipv4.ip_no_pmtu_discvalue

“TCPPATHMTU” (page 191)

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.ipv4.tcp_rmem 'valuevalue value'

NOTE: Changes to this sysctl parameter must be madeon all CLIMs that share the same Provider. Also, allproviders sharing a CLIM must similarly share that sysctlvalue.

“TCPRECVSPACE” (page 191)

188 IP CIP Migration, Compatibility and Operational Differences

Do this in CIP:If you use this MON/SUBNET attribute in TCP/IPv6:

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.ipv4.tcp_sack value

“TCPSACKON” (page 192)

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.ipv4.tcp_wmem 'valuevalue value'

NOTE: Changes to this sysctl parameter must be madeon all CLIMs that share the same Provider. Also, allproviders sharing a CLIM must similarly share that sysctlvalue.

“TCPSENDSPACE” (page 192)

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.ipv4.tcp_tw_recyclevalue

NOTE: Changes to this sysctl parameter must be madeon all CLIMs that share the same Provider.This change in sysctl parameter requires a CLIM restart.Connections that go through TCP state aware nodes,such as firewalls, NAT devices or load balancers may seedropped frames. The more connections there are, themore likely you will see this issue.

“TCPTIMEWAIT” (page 192)

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.core.rmem_max value and

“UDPRECVSPACE” (page 193)

CLIMCMD clim-name climconfig sysctl -updatenet.core.rmem_default value

NOTE: Changes to this sysctl parameter must be madeon all CLIMs that share the same Provider. Also, allproviders sharing a CLIM must similarly share that sysctlvalue.

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.core.wmem_max value and

“UDPSENDSPACE” (page 193)

CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.core.wmem_default value

NOTE: Changes to this sysctl parameter must be madeon all CLIMs that share the same Provider. Also, allproviders sharing a CLIM must similarly share that sysctlvalue.

Controlled by climconfig sysctl, with the default as ON.CLIMCMD {clim–name | ip–address} climconfig

“IPV6RAENABLE” (page 193)

sysctl -update net.ipv6.conf.all.autoconf0 CLIMCMD{clim–name | ip–address}climconfig sysctl -updatenet.ipv6.conf.intf-name.autoconf 0

NOTE: The above commands are for disabling IPv6auto-configuration.

INITIAL-TTLThis NonStop TCP/IPv6 Monitor attribute, which specifies the initial value for UDP andTCPtime-to-live, can be set by using the CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.ipv4.ip_default_ttl command.

HOSTIDThis NonStop TCP/IPv6 Monitor attribute, which specifies the identification number (usually thehost number part of the Internet address that is assigned to this host) is set by using the NonStop

TCP/IP Attributes in CIP 189

host system SCF commands ADD PROVIDER or ALTER PROVIDER. (See Section Chapter 11(page 210) for more information about the HOSTID attribute.)

HOSTNAMEThis NonStop TCP/IPv6 Monitor attribute, which specifies the official name by which the NonStophost is known to the Internet, is set by using the NonStop host system SCF commands ADDPROVIDER or ALTER PROVIDER. (See Chapter 11 (page 210) for more information about theHOSTNAME attribute.)

MIN-EPHEMERAL-PORT, MAX-EPHEMERAL-PORTThese NonStop TCP/IPv6 Monitor attributes specify the starting and ending port numbers toallocate for TCP and UDP ephemeral ports. An equivalent effect can be created by using theCLIMCMD {clim–name | ip–address} climconfig sysctl -updatenet.ipv4.ip_local_port_range command.This attribute, if changed, must be the same on all CLIMs in a Provider.

RFC1323-ENABLEThis NonStop TCP/IPv6 Monitor attribute, which causes TCP to support TCP Large Windowsas documented in RFC 1323, can be set by issuing the CLIMCMD {clim–name | ip–address} climconfig sysctl -update net.ipv4.tcp_window_scaling value command. Wherevalue is:0 — disabled1 — enabled (default)

TCPKEEPCNTThis NonStop TCP/IPv6 Monitor attribute, which specifies the number of times a keep-alivepacket is sent without receiving an acknowledgment, can be set by issuing the CLIMCMD{clim–name | ip–address} climconfig sysctl -updatenet.ipv4.tcp_keepalive_probes command.

NOTE: The default for the TCPKEEPCNT attribute differs from that of the tcp_keepalive_probesattribute. To change the tcp_keepalive_probes default to match the TCPKEEPCNT default, issuethe CLIMCMD command:climconfig sysctl -update net.ipv4.tcp_keepalive_probes 8

TCPKEEPIDLEThis NonStop TCP/IPv6 Monitor attribute, which specifies the amount of time, in seconds, beforeTCP issues a keep-alive packet on sockets that have enabled this option, can be set by issuingthe CLIMCMD {clim–name | ip–address} climconfig sysctl -updatenet.ipv4.tcp_keepalive_time command.

NOTE: The default for the TCPKEEPIDLE attribute differs from that of the tcp_keepalive_timeattribute. To change the tcp_keepalive_time default to match the TCPKEEPIDLE default, issuethe CLIMCMD command:climconfig sysctl -update net.ipv4.tcp_keepalive_time 75

TCPKEEPINTVLThis NonStop TCP/IPv6 Monitor attribute, which specifies the time interval in seconds betweenretransmissions of unacknowledged keepalive packets, can be set by issuing the CLIMCMD{clim–name | ip–address} climconfig sysctl -updatenet.ipv4.tcp_keepalive_intvl command.

190 IP CIP Migration, Compatibility and Operational Differences

NOTE: The default for the TCPKEEPINTVL attribute differs from that of the tcp_keepalive_intvlattribute. To change the tcp_keepalive_intvl default to match the TCPKEEPINTVL default, issuethe CLIMCMD command:climconfig sysctl -update net.ipv4.tcp_keepalive_intvl 75

TCP-MAX-REXMIT-COUNTThis NonStop TCP/IPv6 Monitor attribute, which set the maximum number of continuousretransmissions allowed before a TCP connection was dropped, can be set by issuing theCLIMCMD {clim–name | ip–address} climconfig sysctl command. See “TCP_RXMTCNT”(page 185).

TCPPATHMTUThis NonStop TCP/IPv6 Monitor attribute is used to turn on Path MTU discovery. Path MTUdiscovery is on by default in CIP; if you want Path MTU discovery turned off, use the CLIMCMD{clim–name | ip–address} climconfig sysctl -update net.ipv4.ip_no_pmtu_disccommand.

TCPRECVSPACEThis NonStop TCP/IPv6 MON attribute, which sets the size of the window for receiving data forthe TCP protocol, can be set globally with the CLIMCMD {clim–name | ip–address} climconfigsysctl -update net.ipv4.tcp_rmem "value value value" command.This attribute, if changed, must be the same on all CLIMs in a Provider.The value variables affect kernel behavior for different conditions:

• The first value sets the minimum TCP receive send buffer space available for a single TCPsocket.

• The second value sets the default buffer space allowed for a single TCP socket.

• The third value sets the maximum TCP receive buffer space.You can also set the maximum and default sizes for socket buffers for all connections by usingthe climconfig sysctl -update net.core.rmem_max value andnet.core.rmem_default value sysctl commands.

NOTE: The net.ipv4.tcp_rmem parameter overrides the net.core.rmem_max andnet.core.rmem_default sysctl commands for TCP connections. Changes to this sysctlparameter must be made on all CLIMs that share the same Provider.To change the sysctl parameters on the CLIM:1. Stop the CLIMs and the Provider.2. Alter the sysctl parameters.3. Start the CLIMs and the Provider.If the CLIM is a Telco CLIM, reboot it.

BackgroundCIP supports the RFC1323 TCP high performance extensions. This includes large TCP windowsto support links with high latency or bandwidth. To make use of them, you must increase thesend and receive buffer sizes.

Programmatic AlternativeThe TCP send window size can also be set on individual sockets by setting the SO_RCVBUFoption.

TCP/IP Attributes in CIP 191

TCPSACKONThis NonStop TCP/IPv6 Monitor attribute, which specifies whether or not all TCP connectionsuse TCP selective acknowledgements (unless specifically disabled by an application) can be setby using the CLIMCMD {clim–name | ip–address}climconfig sysctl -updatenet.ipv4.tcp_sack command.

TCPSENDSPACEThis NonStop TCP/IPv6 MON attribute, which sets the size of the window for sending data forthe TCP protocol, can be set globally by using the CLIMCMD {clim–name |ip–address}climconfig sysctl -update net.ipv4.tcp_wmem "value valuevalue" command.This attribute, if changed, must be the same on all CLIMs in a Provider.The value variables affect kernel behavior for different conditions:

• The first value sets the minimum TCP send buffer space available for a single TCP socket.

• The second value sets the default buffer space allowed for a single TCP socket.

• The third value sets the maximum TCP send buffer space.You can also set the maximum and default sizes for socket buffers for all connections by usingthe climconfig sysctl -update net.core.wmem_max value and sysctlnet.core.wmem_default value sysctl commands.

NOTE: Changes to the sysctl net.core.wmem_default parameter must be made on allCLIMs that share the same Provider. To change the sysctl parameters:1. Stop the CLIMs and the Provider.2. Alter the sysctl parameters.3. Start the CLIMs and the Provider.If the CLIM is a Telco CLIM, reboot it.

The net.ipv4.tcp_wmem command overrides the net.core.wmem_max andnet.core.wmem_default sysctls for TCP connections.

BackgroundCIP supports the RFC1323 TCP high performance extensions. This includes large TCP windowsto support links with high latency or bandwidth. To make use of them, you must increase thesend and receive buffer sizes.

Programmatic AlternativeThe TCP send window size can also be set on individual sockets by setting the SO_SNDBUFoption.

TCPTIMEWAITThis NonStop TCP/IPv6 attribute, which sets the minimum amount of time in seconds that a TCPconnection remains in the TIME_WAIT state, can be set by using the command:CLIMCMD {clim-name | ip-address} climconfig sysctl -updatenet.ipv4.tcp_tw_recycle value command.If this parameter is set(1), the sockets will remain in TIME_WAIT state, which is a function of theround trip time of the connection.If this parameter is unset(0), the socket will remain in TIME_WAIT state for a fixed time of 60seconds.

192 IP CIP Migration, Compatibility and Operational Differences

This attribute must be same on all CLIMs that share the same provider. If there is a change inthe sysctl parameter value, restart the CLIM.Connections that go through TCP state aware nodes, such as firewalls, NAT devices or loadbalancers may see dropped frames. The more connections there are, the more likely you willsee this issue.

UDPRECVSPACEThis NonStop TCP/IPv6 Monitor attribute, which specifies the size of the window used for receivingdata for the UDP protocol, can be set by using the climconfig sysctl -updatenet.core.rmem_max value and climconfig sysctl -updatenet.core.rmem_default value commands.This attribute, if changed, must be the same on all CLIMs in a Provider. If the CLIM is a TelcoCLIM, reboot it.

UDPSENDSPACEThis NonStop TCP/IPv6 Monitor attribute, which specifies the size of the window used for sendingdata for the UDP protocol can be set by using the climconfig sysctl -updatenet.core.wmem_max value and climconfig sysctl -updatenet.core.wmem_default value commands.This attribute, if changed, must be the same on all CLIMs in a Provider. If the CLIM is a TelcoCLIM, reboot it.

IPV6RAENABLEIf this attribute is set to ON, the NonStop TCP/IPv6 implementation performs the following taskswhen a router advertisement (RA) is received:

Learns the IPv6 address of a router and installs defaultroutes in the TCP/IPv6 routing tables.

Router discovery

Learns IPv6 on-link prefix (ranges of IPv6 addresses thatare directly reachable on a given link).

On-Link prefix discovery

Automatically creates and deletes interface addresses.Stateless address configuration

Automatically configures datalink attributes such as hoplimit, reachable time, retransmit time, and link MTU.

Interface attribute configuration

ND6HOSTD process is responsible for updating the globaladdress information in DNS automatically.

Sends RA message to ND6HOSTD process

If this attribute is set to OFF, it disables the routing table and interface configuration update duringRA message processing. TCPMON still sends RA messages to ND6HOSTD process. The defaultis OFF.In CIP, this attribute is controlled by climconfig sysctl, with the default as ON.CLIMCMD {clim–name | ip–address} climconfig sysctl

-update net.ipv6.conf.all.autoconf 0CLIMCMD {clim–name | ip–address} climconfig sysctl

-update net.ipv6.conf.intf-name.autoconf 0

ND6HOSTD is not supported in CIP.

Attribute Default Values and RangesTable 20: TCP/IP Attribute Default Values and Ranges shows TCP/IPv6 attributes and theirdefault values and allowable ranges. Table 21: TCP/IP Attributes, CIP Equivalents, and their CIPDefault Values and Ranges (page 194) shows these same attributes, their CIP equivalents, andtheir CIP defaults values and allowable ranges.

TCP/IP Attributes in CIP 193

Table 20 TCP/IP Attribute Default Values and Ranges

TCP/IPv6 Maximum ValueTCP/IPv6 MinimumValue

TCP/IPv6 DefaultValueTCP/IPv6 Attribute

3064INITIAL-TTL

(MAX-EPHEMERAL-PORT-16)10241024MIN-EPHEMERAL-PORT

655351665024MAX-EPHEMERAL-PORT

——ONRFC1323–ENABLE

2016TCPKEEPCNT

7200175TCPKEEPIDLE (seconds)

1260175TCPKEEPINTVL(seconds)

12112TCP-MAX-REXMIT-COUNT

——ONTCPPATHMTU

6144051261440TCPRECVSPACE

——OFFTCPSACKON

6144051261440TCPSENDSPACE

6140051242080UDPRECVSPACE

92165129216UDPSENDSPACE

1–(MIN-EPHEMERAL-PORT)1023MAX-PRIV-PORT

——OFFIPV6RAENABLE

120160TCPTIMEWAIT (seconds)

Table 21: TCP/IP Attributes, CIP Equivalents, and their CIP Default Values and Ranges (page 194)shows TCP/IPv6 attributes, their CIP equivalents, and their CIP defaults values and allowableranges.

Table 21 TCP/IP Attributes, CIP Equivalents, and their CIP Default Values and Ranges

CIP Maximum Value

CIPMinimumValueCIP Default ValueCIP Equivalent AttributeTCP/IP Attribute

255064net.ipv4.ip_default_ttlINITIAL-TTL

65535–SHARE_PORTS.If the maximum value

102432768net.ipv4.ip_local_port_rangeMIN-EPHEMERAL-PORT

ofnet.ipv4.ip_local_port_rangeis set greater than64535 the CLIMdoesn't start withdefaultSHARE-PORTS value.

65535102461000net.ipv4.ip_local_port_rangeMAX-EPHEMERAL-PORT

(<50)9net.ipv4.tcp_keepalive_probesTCPKEEPCNT

7200net.ipv4.tcp_keepalive_timeTCPKEEPIDLE(seconds)

75net.ipv4.tcp_keepalive_intvlTCPKEEPINTVL(seconds)

194 IP CIP Migration, Compatibility and Operational Differences

Table 21 TCP/IP Attributes, CIP Equivalents, and their CIP Default Values and Ranges(continued)

CIP Maximum Value

CIPMinimumValueCIP Default ValueCIP Equivalent AttributeTCP/IP Attribute

15net.ipv4.tcp_retries2TCP-MAX-REXMIT-COUNT

00net.ipv4.ip_no_pmtu_discTCPPATHMTU

104857640964096–88000–1048576net.ipv4.tcp_rmemTCPRECVSPACE

104857601net.ipv4.tcp_sackTCPSACKON

104857640964096–88000–1048576net.ipv4.tcp_wmemTCPSENDSPACE

104857642080net.core.rmem_default/rmem_maxUDPRECVSPACE

10485769216net.core.wmem_default/wmem_maxUDPSENDSPACE

10231023(built-in)MAX-PRIV-PORT

101net.ipv6.conf.all.autoconfIPV6RAENABLE

100net.ipv4.tcp_tw_recycleTCPTIMEWAIT(seconds)

NonStop TCP/IPv6 Attributes Not Supported

ARPTIMER-REFRESHEDThis NonStop TCP/IPv6 Monitor attribute is not supported in CIP because CIP already restartsthe ARP timer on each reference and cannot be configured differently. This action is the sameas the NonStop TCP/IPv6 default.

TCPTIMEWAITThis NonStop TCP/IPv6 Monitor attribute is not supported in CIP. The TIME_WAIT period cannotbe configured in CIP. The application can use SO_REUSEADDR option to re-use the port.

ICMP-FILTER-PKTSThis NonStop TCP/IPv6 Monitor attribute is used to control the flow of the ICMP packets into thesystem. CIP supports filtering of ICMP packets through the general-purpose packet filteringfacility, iptables. If iptables is enabled on the CLIM, the following iptables rule can be added todrop all ICMP packets:CLIMCMD clim name climconfig iptables -I CIP_INPUT -p icmp -j DROP

For information on iptables , see “CIP iptables/ip6tables Support (climiptables)” (page 48).

DELAYACKSThis NonStop TCP/IPv6 Monitor attribute, which specifies whether acknowledgments for TCPpackets be sent immediately (as soon as a packet is received), is not supported in CIP. CIP usesa sophisticated ACK delay algorithm that makes this option unnecessary.

DELAYACKSTIMEThis NonStop TCP/IPv6 Monitor attribute, which specifies how much the delay time is before anACK (acknowledgment) is sent for a packet, is not supported in CIP.

ALLNETSARELOCALThis NonStop TCP/IPv6 Monitor attribute is a method of optimizing maximum segment size(MSS). CIP does not change the MSS advertisement based on whether the address is local. It

TCP/IP Attributes in CIP 195

uses the higher of the first hop device MTU and the /proc variable ip_rt_min_advmss, but maybe overridden by information stored in the routing table from previous connections to the sameremote address. The ALLNETSARELOCAL attribute therefore does not apply to CIP, but theadvertised MSS may not match that of NonStop TCP/IPv6.

MAX-PRIV-PORTThis NonStop TCP/IPv6 Monitor attribute, which specified the largest TCP and UDP port numberthat needed super-user access, is not supported by CIP. The value is fixed at 1023.

NONSHAREDOUTDISTThis NonStop TCP/IPv6 Monitor attribute, which specified whether or not the outbound datapaths for connections over nonshared IP failover pairs are distributed over both SUBNETs of thefailover pair, is not supported in CIP.In NonStop TCP/IPv6, interfaces configured for NONSHAREDIP failover have separate IPaddresses and outgoing data uses the usual routing table rules. (Only the first routing table matchis used in NonStop TCP/IPv6, however, so even if both interfaces have a route, only one isselected.) SHAREDIP always alternates between the two interfaces of a failover pair and thisoption tells TCP/IPv6 to do the same for NONSHAREDIP.In CIP, CLIM-to-CLIM failover most closely resembles the NonStop TCP/IPv6 NONSHAREDIPfailover. CIP uses round-robin rotation among the routes to CLIMs, so load balancing occurs aslong as routes to both CLIMs exist. You can ensure any static routes are added to both CLIMs;dynamic routes will match because the CLIMs must be on the same LAN segment. This optionis no longer needed in CIP. (See “Failover Differences (Fault Tolerance)” (page 177).)

PORT-SHARE-ENABLE-ALLThis NonStop TCP/IPv6 Monitor attribute allows applications running in different processors tobind to the same TCP or UDP yet have different IP addresses. CIP algorithms makes this attributeunnecessary, and it is therefore not supported in CIP. (This attribute enabled behavior uniqueto the NonStop TCP/IPv6 architecture.)

TCP-INIT-REXMIT-TIMEOUTThis NonStop TCP/IPv6 Monitor attribute, which sets the initial retransmit timer-value inmilliseconds to use on a TCP connection, is not supported in CIP.

TCP-MAX-REXMIT-TIMEOUTThis NonStop TCP/IPv6 Monitor attribute, which sets the maximum time value in millisecondsallowed for a TCP retransmission timeout, is not supported by CIP.

TCP-MIN-REXMIT-TIMEOUTThis NonStop TCP/IPv6 Monitor attribute, which set the minimum value allowed for the TCPretransmission timeout, is not supported by CIP.

TCP-TOTAL-REXMIT-DURATIONThis NonStop TCP/IPv6 Monitor attribute, which sets the total time a TCP connection can be inthe retransmission state without receiving an acknowledgement from the other endpoint beforethe TCP connection is dropped, is not supported in CIP.

TCPCWNDMULTIPLIERThis NonStop TCP/IPv6 Monitor attribute, which was used to calculate the initial TCP congestionwindow, is not supported by CIP. CIP uses its own algorithm to calculate the initial TCP congestionwindow, ranging from 1 to 4. Higher values are considered potentially harmful to overall networkstability and so the CIP defaults are used in CIP.

196 IP CIP Migration, Compatibility and Operational Differences

TCPCOMPAT42This NonStop TCP/IPv6 Monitor attribute, which set a flag to make the TCP6MON compatiblewith Berkeley Standard Distribution TCP/IP (BSD) 4.2 versions, is not supported by CIP. In BSD4.2, TCP sequence numbers were 32-bit signed values. Modern implementations of TCP useunsigned values. This option caused the initial sequence number to start in the range 2^31 ratherthan the full unsigned range of 2^32. Also, under BSD 4.2, keepalive packets must contain atleast one byte, or else the remote end does not respond. The default for this attribute was ON.

IRDP SUBNETThe IRDP SUBNET attribute enables or disables the ICMP Router Discovery Protocol on theSUBNET interface. IRDP is a mechanism for locating default routers. CIP does not support thisattribute.

How to Migrate From NonStop TCP/IP or NonStop TCP/IPv6 to CIPMigrate the Environment

If you are running multiple TCP/IP subsystems and want to use CIP for your application but thedefault TCP/IP process ($ZTC0) is assigned to either Nonstop TCP/IPv6 or conventional TCP/IP,you can migrate your application to the CIP subsystem by adding a DEFINE or PARAMestablishing another (non $ZTC0) CIPSAM process as the transport service provider in the TACLenvironment in which your program is running. The procedure documented here includes thatfinal step of setting the DEFINE or PARAM as well as the preliminary steps of preparing for usingthe CIP environment.To migrate to the CIP networking environment:1. Have your support provider install the CLIMs and bring up the subsystem.2. Make any changes to your applications required by the compatibility differences documented

in this chapter.3. Change the applications to use a CIPSAM process.

a. Find a CIPSAM process by using the SCF LISTDEV CIP command or create a CIPSAMprocess (see Chapter 2 (page 53)) that matches the name of the TCP/IP process yourapplications are using.

b. Set up the transport-service provider name for Guardian and OSS applications to theCIPSAM process by entering one of these commands:• ADD DEFINE =TCPIP^PROCESS^NAME, class map, file

$cipsam-process-name

• PARAM TCPIP^PROCESS^NAME $cipsam-process-name

• Use these procedure calls to set the transport-service provider to a CIPSAM process:

◦ socket_set_inet_name() (for Guardian applications)

◦ socket_transport_name_set() (for OSS applications)

How to Migrate From NonStop TCP/IP or NonStop TCP/IPv6 to CIP 197

7 Storage CLIM Migration, Compatibility and OperationalDifferences

The user applications, NonStop SQL/MP, NonStop SQL/MX and Disk Process 2 (DP2) canaccess the Storage CLIM devices without any changes.The Storage CLIM is managed by commands from both the Storage subsystem and the CIPsubsystem. The SCF product module for the storage subsystem uses the management object$ZZSTO and the SCF product module for the CIP subsystem uses the management object$ZZCIP.

NOTE: To find out if your system supports Storage CLIMs, see the planning guide for yoursystem or the NonStop Networking Overview.

You can perform these tasks by using the SCF product module in the storage subsystem:

• INFO CLIM $ZZSTO.clim-name

• STATUS CLIM $ZZSTO.clim-name

• SWITCH CLIM $ZZSTO clim-name

Alternatively, each of the above commands can be issued from the CIP subsystem by substituting$ZZCIP for $ZZSTO for the management process specification. The INFO and STATUScommands display different information if issued to the CIP subsystem. The SWITCH command,when issued to the CIP subsystem, moves the IP resources back to the home interfaces. Whenissued to the storage subsystem, the SWITCH command initiates disk-path switches for the disksconfigured through the CLIM and sometimes takes paths up or down. For more information aboutthe behavior of these commands when issued to the storage subsystem, see the SCF ReferenceManual for the Storage Subsystem.These major commands can be done only through the CIP subsystem:

• ADD CLIM $ZZCIP.clim-name

• DELETE CLIM $ZZCIP.clim-name

• START CLIM $ZZCIP.clim-name

• STOP CLIM $ZZCIP.clim-nameTable 22 (page 198) compares tools and tasks on IOAM or CLIM operations:

Table 22 IOAM and CLIM Based Operations Comparison

CLIM Based OperationsIOAM Based OperationsTool/Task

Storage CLIMFCSACommunication device

SAS disk enclosureFiber channel disk module FCDMBuilt-in storage

SCF for storage subsystem, SCF forCIP subsystem and CIP subsystem

SCF for storage subsystemManagement interface

CLIMCMD command line interface(CLI)

SCF command ADD CLIM$ZZCIP.clim-name

No equivalentAdd a CLIM

CLIMCMD lunmgr commandNo equivalentManage the LUN numbering to allowthe CLIM to communicate with ESSand attached storage

Table 23: CLIM Based Operations Information lists information sources for CLIM-based storageoperations.

198 Storage CLIM Migration, Compatibility and Operational Differences

Table 23 CLIM Based Operations Information

Information

SCF Reference Manual for the Storage SubsystemSCF for the storage subsystem $ZZSTO

This manual, Chapter 11 (page 210)SCF for the CIP subsystem $ZZCIP

This manual, Chapter 5 (page 164)How to manage LUN numbering

Your service provider has access to theCLuster I/OModule(CLIM) Installation and Configuration Guide and to otherservice procedures.

Installation and initial configuration of the CLIM

199

8 Collecting Data for CLIM IssuesThis chapter provides various procedures for collecting NonStop system data for different CLIMtypes in case of failures.

What to doFailure TypeCLIM Type

Create CLIM debug informationAllAll

Copy CLIM debug information toNonStop

AllAll

Collect EMS logs (both ZLOG and $0)AllAll

Collect iLO and IML logsCLIM hung/not responding/resetAll

Collect SSH specific informationSSOCLIM/CLIMCMD issuesAll

Collect lunmgr informationAllStorage

Collect SCF device configurationinformation

AllStorage

Collect network informationAllIP/Telco

Collect IB network statusAllIB and all CLIMs running L-series

Create CLIM Debug InformationTo create a compressed tar file containing debugging information for the CLIM, run the followingcommand at the TACL prompt:TACL->CLIMCMD clim-name clim onlinedebug... doneThe compressed tar file /home/debuginfo/clim-<yyyymmddhhmmss>.tgz hasbeen created.Termination Info: 0

CLIM Log FilesFor systems running L15.02/H06.23/J06.12 or later, OSM collects CLIM logs from CLIMs thatrecover from a crash. OSM only collects the logs whenever the CLIM transitions to STARTEDstate. OSM also has an action, “Collect CLIM Logs”, on the CLIMs object in the OSM ServiceConnection that can be used to collect logs for all CLIMs in the system.

Collecting CLIM Log Files using CLIMDBUGIn a CLIM failure, the debug information is automatically collected, zipped, and saved on theCLIM in the /home/debuginfo directory as a .tgz file. The CLIMDBUG tool detects the logfiles on the CLIM, copies them to the NonStop file system, and packs them into a single data file.On successful transfer to the NonStop Host, the CLIMDBUG tool deletes the log files from theCLIM. This operation can be executed only by a user who is either a member of the super groupor a member of the Safeguard SECURITY-CLIM-ADMIN group. Unauthorized invocations resultin a warning condition.

NOTE: Collecting CLIM log information using CLIMDBUG is supported on systems runningL15.02 and J06.12 or later RVUs.

Effective with the J06.13/H06.24 RVU, CLIMDBUG also collects the following information:• SCF configuration details of CIP subsystem

• SSH configuration details

200 Collecting Data for CLIM Issues

• EMS logs

• SSH logs

• NSK Software Configuration fileThe syntax is as follows:CLIMDBUG [/run-option /]{clim-name-pattern | ip-address }[pak file]

Where:run-option can be any of the options:online

Generates an online CLIM debug data file before transferring the debug files to the host.originator originator-name

Allows you to specify whether the tool is being invoked from another program or script.out out-file

Redirects the display text to the file out-file.outv var-name

Redirects the display text to the variable var-name.pri priority

Specifies the execution priority.clim-name-pattern

Specifies the CLIM name and supports patterns to target multiple CLIM names. The patternmay contain '?' for matching exactly one character and '*' for matching zero or more characters.

ip-addressSpecifies the IP address of the eth0 interface of the CLIM. It does not support any patternsto target multiple CLIMs.

pakFileAn optional parameter which specifies the file location for the debug file on the NonStop Hostfile system. The parameter may be of the format of $vol, $vol.subvol,$vol.subvol.filename, subvol.filename, or filename.

If vol or subvol is not specified, the default values are applied. If the filename is not specified,a unique filename from $vol.subvol is generated.If nothing is specified for the pakFile parameter, the default values are applied. The defaultvalues for $vol and subvol for the data file are $system and zservice respectively.

Example 24 Collect Debug Data From Single CLIM

\BLOKE.$SYSTEM.STARTUP 3> CLIMDBUG N1002582 $SYSTEM.OSMTEST

Debug Info CLIM \BLOKE.$ZZCIP.N1002582

PAK File....................$SYSTEM.OSMTEST.ZCL04D01Contents of PAK File......../home/debuginfo/clim-20101116220455.tgz

/home/debuginfo/clim-20101116220456.tgz/home/debuginfo/clim-20101116220457.tgz

Log File....................$SYSTEM.ZSERVICE.ZCL04L10

Termination Info: 0

Collecting CLIM Log Files using CLIMDBUG 201

Example 25 Collect Debug Data From Multiple CLIMs

\BLOKE.$SYSTEM.STARTUP 3> CLIMDBUG /online/ S100253*

Debug Info CLIM \BLOKE.$ZZCIP.S1002531

PAK File...................$SYSTEM.ZSERVICE.ZCL06D08Contents of PAK File......./home/debuginfo/clim-20101116220458.tgzLog File...................$SYSTEM.ZSERVICE.ZCL06L11

Debug Info CLIM \BLOKE.$ZZCIP.S1002533

PAK File.....................$SYSTEM.ZSERVICE.ZCL07D09Contents of PAK File........./home/debuginfo/clim-20101116220459.tgzLog File.....................$SYSTEM.ZSERVICE.ZCL07L11

Termination Info: 0

CLIMDBUG tool reports completion status on the last line of the displayed text as TerminationInfo:completion-code. The tool also, sets the :_completion:completioncode TACLvariable to an appropriate completion-code value.On successful execution, the tool reports the completion-code as zero. Unsuccessful executionresults in a non-zero completion-code. The errors are reported with positivecompletion-code where as warnings are reported with negative completion-code.

DescriptionCompletion-code

CLIMDBUG is invoked by a user who is neither a member of the super group nor a memberof the Safeguard SECURITY-CLIM-ADMIN group.

–1

There are no debug data files on the target CLIM–2

Success0

Syntax Error1

Less than 20 GB free disk space is available under the volume $vol on the NonStop filesystem where the data file needs to be created

2

clim-name-pattern is either invalid or it does not match any CLIM under the NonStophost

3

SSH connection could not be established to the target CLIM4

Failure in generating online CLIM debug data file on the target CLIM5

Failure in transferring debug data files from the target CLIM6

Failure in creating the data file on the NonStop Host7

OSM Event Viewer Log for CIP Event 5231CLIMDBUG tool logs an EMS event for invocations which result in either success or errorconditions. The following is the event log for CIP Event 5231:

Header_type: 1Checksum: F

Last_error: no_error (0)Last_error_tkncode: (0,0,0)Max_field_version: 0

SSID: TANDEM.CIP.H02Used_byte_length: 225

Buffer_byte_length: 225Console-Print: F

202 Collecting Data for CLIM Issues

Generating-CPU: 1Emphasis: F

Event-Number: CLIM Debug Info Collection Event (5231)Standard-defined-type: not-specified (0)

User-defined-type: undefined (0)Event-Hdr-Version: 2ZEMS-TKN-FORWARDED: F

Generation-Timestamp: 2011-06-24 01:34:15.060.473Logged-Timestamp: 2011-06-24 01:34:15.061.571

Node-Name: "\BLOKE"Node-Number: 85

Generating-PIN: 44Process-Descriptor: "\BLOKE.$Z0A9:3385669"ZEMS-TKN-REDUNDANT: FSuppress-Display: F

Userid: 255 255

Subject-Mark:CLuster IO Module:* "N1002582 "

(1,255,100): "CLIMDBUG N1002582 $SYSTEM.ZSERVICE.ZCL04D01[Termination Info: 0]"

NonStop-User-ID:- "SUPER.SUPER"

11-06-24 01:34:15 \BLOKE.$Z0A9 TANDEM.CIP.H02 005231 CLIM Debug InfoCollection Event

CLIM Name: N1002582

CLIMDBUG N1002582 $SYSTEM.ZSERVICE. ZCL04D01 [Termination Info: 0]

Initiated by NonStop user: SUPER.SUPER

Copying CLIM Debug Information to NonStopUse any of the methods described here to troubleshoot failures detected in the CLIM.

NOTE: If the system is running J06.12+, then the preferred method to collect the debuginformation is through OSM Service Connection. For more details, see “CLIM Log Files” (page 200)

Method 1: If the CLSFTP script is present on the NonStop system:1. List all the CLIM debug files.

TACL->CLIMCMD clim-name ls /home/debuginfoSSH client version T9999H06_21Jun2010_comForte_SSH_0088clim-20100802125044.tgzclimVersionTermination Info: 0

2. Obtain CLIM debug files. Be sure that you transfer all.tgz files in the /home/debuginfodirectory to NonStop.For example:TACL-> CLSFTP clim-name get clim-debug-filename nsk-filename\JUNO1.$SYSTEM.MM 10> clsftp C100271 get /home/debuginfo/clim-20100802125044.tgzclimtgz1CLSFTP - T0834 - version 1.2, 29-SEP-2009using $ZSSP0...SFTP client version T9999H06_21Jun2010_comForte_SFTP_0088Connecting to 192.168.200.21 via SSH2 process $ZSSP0 ...sftp> get /home/debuginfo/clim-20100802125044.tgz climtgz1Fetching /home/debuginfo/clim-20100802125044.tgz to climtgz1---------------------------------- -------- --- ------- ----------Filename BytesNow % Bytes/s Remaining---------------------------------- -------- --- ------- ----------/home/debuginfo/clim-20100802125044.tgz 0 0% 0.0KB --:--/home/debuginfo/clim-20100802125044.tgz 280KB 1% 280.0KB 01:19/home/debuginfo/clim-20100802125044.tgz 952KB 4% 476.0KB 00:45…/home/debuginfo/clim-20100802125044.tgz 22MB 99% 672.0KB 00:00---------------------------------- -------- --- ------- ----------

Copying CLIM Debug Information to NonStop 203

Filename BytesNow % Bytes/s TimeSpent---------------------------------- -------- --- ------- ----------/home/debuginfo/clim-20100802125044.tgz 22MB 100% 665.4KB 00:3423167953 bytes transferred in 34 seconds (665.4KB/s)sftp>SFTP Completion Code = 0\JUNO1.$SYSTEM.MM 11>

Method 2: If the CLSFTP script is not present on the NonStop system:1. Obtain IP address of CLIM.

SCF - T9082H01 - (04DEC06) (15NOV06) - 03/11/2010 12:33:02 System \NINJA(C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P.CIP Detailed Info CLIM \NINJA.$ZZCIP.C1002533Mode....................... STORAGEConfigured Location........ Group 100 , Module 2 , Slot 5 , Port 3 ,Fiber 3ConnPts.................... 2X1 Location................ Group 100 , Module 2 , Slot 5 , Port 3 ,Fiber 3Y1 Location................ Group 100 , Module 3 , Slot 7 , Port 3 , Fiber 3Net ID 1................. 0x000E3F62X2 Location................ Group 100 , Module 2 , Slot 5 , Port 3 , Fiber 4Y2 Location................ Group 100 , Module 3 , Slot 7 , Port 3 , Fiber 4SvNet ID 2................. 0x000E3F63Maintenance Interface IP... 192.168.37.33

2. Use the returned IP address to access the CLIM and transfer the files. Be sure that youtransfer all.tgz files in the /home/debuginfo directory to NonStop.For example:

<TACL> sftp –S $zssp0 –i $system.zservice.superkey root@ clim eth0IP: clim-filename nsk-filename\JUNO1.$SYSTEM.MM 14> sftp -S $zssp0 -i $system.zservice.superkeyroot@192.168.200.21:/home/debuginfo/clim-20100802125044.tgz climtgz2\JUNO1.$SYSTEM.MM 14..SFTP client version T9999H06_21Jun2010_comForte_SFTP_0088Connecting to 192.168.200.21 via SSH2 process $zssp0 ...Fetching /home/debuginfo/clim-20100802125044.tgz to climtgz2---------------------------------- -------- --- ------- ----------Filename BytesNow % Bytes/s Remaining---------------------------------- -------- --- ------- ----------/home/debuginfo/clim-20100802125044.tgz 0 0% 0.0KB --:--/home/debuginfo/clim-20100802125044.tgz 28KB 0% 28.0KB 13:27/home/debuginfo/clim-20100802125044.tgz 672KB 2% 336.0KB 01:05…./home/debuginfo/clim-20100802125044.tgz 22MB 98% 679.0KB 00:00---------------------------------- -------- --- ------- ----------Filename BytesNow % Bytes/s TimeSpent---------------------------------- -------- --- ------- ----------/home/debuginfo/clim-20100802125044.tgz 22MB 100% 665.4KB 00:3423167953 bytes transferred in 34 seconds (665.4KB/s)\JUNO1.$SYSTEM.MM 15>

3. Delete the .tgz files from the CLIM (execute this step for each .tgz file).TACL> CLIMCMD clim-name rm /home/debuginfo/clim-20090604152715.tgzTACL>

4. Send the files to Hewlett Packard Enterprise technical support.

Collecting iLO and IML LogsTo collect information for a CLIM that is hung or not responding when an automatic reset of aCLIM is detected:

204 Collecting Data for CLIM Issues

1. In the OSM Service Connection, locate the CLIM in the tree pane, right-click and selectActions.

2. Select Invoke iLO from the list of actions, and click Perform action.3. Log in with your username and password.4. Click IML. Copy the log information from the screen and include it in the case data.

Collecting iLO and IML Logs 205

5. Click iLO Event Log. Copy the log information from the screen and include it in the casedata.

Collecting lunmgr InformationTo collect lunmgr information for any failures detected in the Storage CLIM types:1. Save the output to a file.

TACL->CLIMCMD clim-name lunmgr -eTACL->CLIMCMD clim-name lunmgr -fTACL->CLIMCMD clim-name lunmgr -p

2. Send the output file to Hewlett Packard Enterprise technical support.

Collecting EMS LogsTo collect log information for any failures detected in the CLIM:1. Collect the files $system.zservice.zzsv* and $system.zlogNN.zzev*, which contain

the events for the period of interest.2. Send the files to Hewlett Packard Enterprise technical support.

Collecting SCF InformationTo collect SCF configuration information for any failures detected in the CLIM:1. Save output to a file.

TACL->scf info disk $*,obeyTACL->scf info disk $*,obeyTACL->scf status disk $*TACL->scf status disk $*

2. Send the output file to Hewlett Packard Enterprise technical support.

206 Collecting Data for CLIM Issues

Collecting Network InformationTo collect network configuration information for any failures detected in an IP, Telco or IB CLIM:

NOTE: IB CLIMs are not supported on NonStop X systems.

1. Use allow all error in SCF for the following commands:TACL> scf info clim $zzcip.*, detailTACL> scf status clim $zzcip.*, detailTACL> scf info prov $zzcip.*, detailTACL> scf status prov $zzcip.*, detailTACL> scf status prov $zzcip.*, route, cpu 0

Run the above commands on each running CPU.TACL> scf version $zzcipTACL> scf version mon $zzcip.*TACL> scf version clim $zzcip.*TACL> scf version $ztcp0TACL> scf version $ztcp1

2. Send the files to Hewlett Packard Enterprise technical support.

Collecting SSH InformationTo collect SSH specific information for failures such as SSOCLIM or CLIMCMD issues detectedwith the CLIMs:1. Save the output to a file.

TACL> scf info proc $zzkrn.ssh-*, detailTACL> scf status proc $zzkrn.ssh-*, detail

2. Collect the files $system.zssh.sshcfg,$system.zssh.sshdb, and$system.zssh.sshlog*.

3. Send the files to Hewlett Packard Enterprise technical support.

Collecting IB Network StatusTo collect the IB network status for any failures detected on an IB CLIM:1. Collect InfiniBand network status using the following command:

CLIMCMD clim-name ibstat > /tmp/ibstat.out

2. Send the /tmp/ibstat.out file to Hewlett Packard Enterprise technical support.

Collecting Network Information 207

9 Dump to ME Unit (L-Series Only)For NonStop X systems, both CPU 0 and CPU 1 are automatically dumped to the two CLIMsthat serve as ME Units in the event of a system outage. The MEUs store the encrypted CPUdump data on their local CLIM storage devices for subsequent upload to an NSK storage device.This automatic dump feature, also known as “CLIM Receive Dump," is enabled by default onNonStop X systems.The OSM Service Connection provides the following support:• A system-level “Enable/Disable Automatic CPU Dump to ME Unit” action to enable or disable

the automatic dump feature.• An “Upload CPU Dump from ME Unit” action that transfers the encrypted dump data from

a local CLIM storage device to an NSK storage device, where it is decrypted andpost-processed to get it into the expected format for analysis.

• A “Delete CPU Dump File from ME Unit” action to delete a dump file from a CLIM localstorage device without transferring it to NSK. This action is not needed after a successfulupload, as that action deletes the successfully uploaded dump file from the CLIM. You may,however, choose to delete the second occurrence of a dump if the first dump was alreadytransferred to NSK. Note that each MEU can store one dump per CPU at any given time.

The OSM System Startup provides a “Dump to ME Unit” system action that allows you to manuallydump those processors to the MEUs. It also provides a “Get Dump Info” action to display statusinformation for existing or in-progress dumps (automatic or manual) on both MEU00 and MEU01.The operations “Upload CPU Dump from ME Unit” and “Delete CPU Dump File from ME Unit”can be performed only by a user who is either SUPER.SUPER or a member of the SafeguardSECURITY-CLIM-ADMIN group.For more information, see the online help.

NOTE: The Dump to ME Unit functionality applies to CPU 0 and CPU 1 only; all other CPUsshould be dumped via the standard NonStop RCVDUMP utility.

For more information on Dump to ME Unit functionality, see the OSM Configuration Guide or theonline help available within the OSM Service Connection or OSM System Startup Tool.

208 Dump to ME Unit (L-Series Only)

10 Telco CIP Migration, Compatibility and OperationalDifferences

There are operational differences between configuring the 6763 Common CommunicationServerNet Adapter and CLIMs systems. This chapter describes those differences. The two biggestdifferences are the introduction of a new I/O subsystem (CIP) for CLIM configuration and theabsence of the SLSA subsystem.

NOTE: The Telco CLIM is not a replacement for the CCSA because it does not provide E1/T1support.

Table 24: IOAM and Telco CLIM Based Operations Comparison shows comparison betweentools and tasks on IOAM and CLIM based operations:

Table 24 IOAM and Telco CLIM Based Operations Comparison

CLIM Based OperationsIOAM Based OperationsTool/Task

Telco CLIM6763 CCSACommunication device

SCF for CIP subsystem and CIPsubsystem CLIMCMD command lineinterface (CLI)

SCF for the SLSA subsystemManagement interface

SCF command ADD CLIM$ZZCIP.CLIM-name

SCF command ADD ADAPTER$ZZLAN.adapter-name

Add a Telco communication device

No equivalentSCF command ADD LIF$ZZLAN.lif-name

Add a logical interface to a device

SCF command START CLIM$ZZCIP.CLIM-name

SCF command START ADAPTER$ZZLAN.adapter-name

Start a Telco communication device

SCF command STATUS CLIM$ZZCIP.CLIM-name or INFO CLIM$ZZCIP.CLIM-name

SCF command STATUS ADAPTER$ZZLAN.adapter-name or INFOADAPTER $ZZLAN.adapter-name

Obtain information about a Telcocommunication device

SCF command VERSION CLIM$ZZCIP.CLIM-name

No equivalentObtain version information aboutsoftware on a Telco communicationdevice

209

11 SCF Reference for CIPThis section provides information about:

• The Subsystem Control Facility (SCF)

• SCF commands available for CIP

• Trace commands available for CIP

SCF for Cluster I/O ProtocolsSCF provides an operator interface to an intermediate process, the Subsystem Control Point(SCP), which in turn provides the interface to the I/O processes of the various subsystems.The CIP subsystem runs on the NonStop system and the CLuster I/O Module (CLIM). This chapterexplains the SCF commands that control the SCF objects that reside on the NonStop host systemand on the CLIM.The CIP subsystem supports Ethernet connectivity.

SCF Commands for CIPMAN Compared to SCF Commands for CIPSAMThis section describes SCF command syntax for both the CIPMAN and the CIPSAM processes.CIPSAM SCF syntax differs from CIPMAN syntax because CIPSAM provides backwardcompatibility for applications. The CIPSAM and CIPMAN processes support different subordinateobjects and yield different command results for subordinate objects they share. For example,CIPMAN does not have a SUBNET object. The SUBNET object is supported for the CIPSAMprocess to allow applications to obtain information about the CLIM interfaces in a format that iscompatible with previous NonStop TCP/IP products. The object type name SUBNET, maintainedfor compatibility, really refers to a home CLIM interface as seen from the host. SUBNET objectnames are generated by CIPSAM and consist of “#SN” followed by a three-digit number. Theyare assigned to interfaces when the interfaces are first reported and do not change as long asthe CIP subsystem continues running. The INFO SUBNET command displays the CLIM andinterface name referenced by a SUBNET object. Also, INFO PROCESS for the CIPSAM processdisplays information an application would obtain from the INFO PROCESS command for theTCP6SAM process in NonStop TCP/IPv6, including a DETAIL option (not supported in INFOPROCESS for the CIPMAN process). The INFO PROCESS command for CIPSAM allowscompatibility for applications written for the conventional NonStop TCP/IP product.

NOTE: Many of the values for INFO PROCESS for CIPSAM are dummy values supplied forbackward compatibility only.

Conventional TCP/IP supplied detailed information on the TCP/IP process, which served as thetransport-service provider in that subsystem.Table 25: Commands and Object Types for CIPMAN lists commands and object types for CIPMAN:

210 SCF Reference for CIP

Table 25 Commands and Object Types for CIPMAN

Object Types

ROUTEPROVIDERPROCESSMONCLIMSCF Command

XXXXABORT

XXXADD

XXALTER

XXXDELETE

XXXXINFO

XXLISTOPENS

XXXXXNAMES

XPRIMARY

XXXSTART

XXSTATS

XXXXSTATUS

XXXXSTOP

XSWITCH

XXXXTRACE

XXXVERSION

Table 26: Commands and Object Types for CIPSAM lists commands and object types for CIPSAM:

Table 26 Commands and Object Types for CIPSAM

Object Types

SUBNETPROCESSSCF Command

XABORT

XXINFO

XNAMES

XPRIMARY

XSTATUS

XSTOP

XTRACE

XVERSION

Object TypesYou can monitor and control the CIP subsystem by issuing commands that act on one or moreCIP subsystem objects. Each object has an object type and an object name. The object typedescribes the type of object. The object name uniquely identifies the object within the system.Figure 15: CIP SCF Object Hierarchy shows the full object hierarchy for CIPMAN, CIPSAM, andthe CLIM software. The CIPMAN, CIPSAM, MON, CLIM, ROUTE, and PROVIDER objects resideon the NonStop host system and are controlled and displayed by SCF commands directed toCIPMAN, CIPSAM, or the persistence manager ($ZZKRN). This section describes those

Object Types 211

commands. The hostname, TCP/IP, interface, route, and arp objects reside in the CLIM and arecontrolled and displayed by the CLIM software commands and configuration files.

Figure 15 CIP SCF Object Hierarchy

CIPMAN PROCESS ObjectThe CIPMAN PROCESS object is the main management object on the NonStop host systemside of the CIP subsystem. The CIPMAN object is the root of the other configuration objects andis used to configure, control, and query the components of CIP on its local system.The CIPMAN process is started by the persistence manager. It is not involved in normal datatransfer or socket creation but is required for SCF commands, error recovery, and changes inobject status. It can be stopped for a short period, such as an online upgrade, with no affect onthe normal operation of the subsystem.For specific information about adding and starting the CIPMAN process, see “Starting CIP onthe NonStop Host System” (page 91). For general information about configuring generic processes(to be started and restarted as necessary by the persistence manager), see the SCF ReferenceManual for the Kernel Subsystem.

212 SCF Reference for CIP

CIPSAM ObjectThe CIPSAM process object represents a transport-service provider process. In CIP, the CIPSAMobject can be used only to display and control the CIPSAM process itself. The CIPSAM processis started by the persistence manager. For specific information about adding and starting theCIPSAM process, see “Starting CIP on the NonStop Host System” (page 91). For generalinformation about configuring generic processes (to be started and restarted as necessary bythe persistence manager), see the SCF Reference Manual for the Kernel Subsystem

MON ObjectThe MON object represents the CIPMON process and is used to query the subsystem on aprocessor or replace CIPMON and the CIP library. It is referenced in SCF commands as ZCMnn(no leading $ or # character), where nn is the two-digit processor number. The MON object canbe in one of either the STOPPED, STARTING, STARTED, or STOPPING states. (For definitionsof these states, see “Summary States” (page 216).)CIPMONs are started using the persistence manager. MON objects are added or deletedautomatically by CIPMAN to match the running processors. A MON object state of STARTEDindicates that CIPMON is running on the processor and CIPMAN has established communicationwith it. An individual CIPMON process can be manually stopped for online replacement or softwarereset by issuing a STOP or ABORT command to its MON object; the persistence manager thenautomatically restarts the CIPMON process. When the MON process is stopped, the operationof CIP on its processor is halted and existing sockets are closed.For specific information about adding and starting the CIPMON process, see “Configuring CIPProcesses for Persistence” (page 63). For general information about configuring generic processes(to be started and restarted as necessary by the persistence manager), see the SCF ReferenceManual for the Kernel Subsystem.

CLIM ObjectThe CLIM object on the NonStop host system represents the NonStop host system interface toa CLIM; it does not really represent the CLIM itself. The CLIM itself starts operating as soon asit boots the CLIM software, but the NonStop host system gains access to the CLIM by startingthe CLIM object. A CLIM object can be in one of either the STOPPED, STARTING, or STARTEDstate. (For definitions of these states, see “Summary States” (page 216).)The LOCATION attribute (used by systems in J-series and H-series RVUs only) gives the group,module, slot, port, and fiber of the ServerNet switch to which the actual CLIM is connected. Ifthe specified location does not reference an operational CLIM, then the CLIM object cannot enterthe STARTED state.

PROVIDER ObjectThe PROVIDER object represents a transport-service provider and directs socket requests to aspecific CLIM. Each Provider must have a corresponding CIPSAM process. You associate theProvider with the CIPSAM process when you add the Provider object. (See “ADD PROVIDER”(page 223).) When a socket is created, the socket is associated with the CIPSAM process that isset as the environment’s transport service provider for the session.The PROVIDER attribute of the CLIM specifies the IPDATA Provider object with which the CLIMis associated. Multiple CLIMs can be associated with each Provider. This feature allows socketapplications to treat the set of CLIMs associated with the same Provider object as a singlemulti-homed host. The sockets created by socket applications can be on any of the CLIMsassociated with the Provider depending on the local IP address associated with each socket. Ina Provider comprising multiple CLIMs, a socket that is bound to a specific local IP address otherthan a loopback address (IPv4 127.0.0.1 or IPv6 ::1) exists only in the CLIM containing thataddress. An outgoing connection or packet for these kinds of sockets is sent through that CLIM.However, sockets not yet bound, bound to INADDR_ANY, or bound to a loopback address might

Object Types 213

be used to listen for incoming connections or packets on addresses that exist in all the CLIMsof a Provider, so are replicated in all the CLIMs. If the socket is used for an outgoing connectionor for sending a packet, the host must choose one of the CLIMs to send it. This process usesthe destination address and is similar to IP routing, but is used only to select a CLIM within aProvider. With either type of binding, the sending CLIM performs its own IP routing to select aninterface and the first hop in the external network. See “ROUTE Object” and for more informationabout routing in CIP.The HOSTNAME and HOSTID attributes give the name returned by gethostname() and thenumber returned by the gethostid() socket library calls when the provider is selected.A PROVIDER can be in one of either the STARTED, STARTING, or STOPPED state. (Fordefinitions of these states, see “Summary States” (page 216).) If an application tries to create asocket when the Provider is not in the STARTED state, the application programmatic interface(API) returns an error. Aborting a Provider that has open sockets also causes the API to returnan error on the next or pending operation.For more information about the Provider object, see “ADD PROVIDER” (page 223).

ROUTE ObjectThe ROUTE object specifies which CLIM to use for default routing when there is no non-defaultrouting specified on any CLIM that can be used for routing to the specified destination and theconnection is not already tied to a specific CLIM. The ROUTE object is a method of selecting aCLIM for default routing when all other routing methods have failed (for example, no specificroute or rule exists that would cause a specific CLIM to be picked). The route used in the externalTCP/IP network is then determined by the configuration of network routes on the selected CLIM.See “Climconfig (Man Pages)” (page 307) for information about configuring network routes byusing the CLIMCMD climconfig tool. See “Routing in the CIP Subsystem” (page 29) for moreinformation about routing in CIP. Multiple CLIMs can define different default routes, however,and the ROUTE object on the NonStop host system controls which CLIM to select by assigninga PRIORITY attribute to each CLIM.The ROUTE is subordinate to the Provider object and requires a unique name. There are noreserved names.

SUBNET ObjectAn object represents the interface in the CIP subsystem. It is provided for backward compatibilityand its fully qualified name is of the format: $ZZCIP.#subnet-name. The subnet name can bea maximum of eight alphanumeric characters. SUBNET names are generated by CIPSAM, notthe user, and are always #SNnnnn, where nnnn is a unique number for each interface. The INFOSUBNET command displays the association between SUBNET names and CLIM interfaces.

Naming Convention SummaryTable 27: Object Naming Convention Summary and Reserved Names summarizes the reservednames for each object type and the naming convention rules.

Table 27 Object Naming Convention Summary and Reserved Names

Character LimitNamingRecommendation

First CharacterRequirement

Starting Symbol(Required)

ReservedNamesObject Type

5MON names areassignedautomatically.

N/ANoneZCMnnMON (CIPMON)

N/AN/AN/AN/AN/Anull

5The name isalways $ZZCIP.

N/A$$ZZCIPPROCESS(CIPMAN)

214 SCF Reference for CIP

Table 27 Object Naming Convention Summary and Reserved Names (continued)

Character LimitNamingRecommendation

First CharacterRequirement

Starting Symbol(Required)

ReservedNamesObject Type

5ZTCxx where xxare letters ornumeric digits.

Letter$NonePROCESS(CIPSAM)

8N, S, or OGroupLetterN/ANoneCLIMModule

Slot

Port

Fiber

7Limit to 5characters; use

LetterN/ANonePROVIDER

CIPSAM processname.

8NoneLetterN/ANoneROUTE

Wildcard SupportNormally, an SCF command line must include an object specifier composed of the object typeand an object name. For many commands, the CIP subsystem accepts object-name templates.In an object-name template, one object name can be used to indicate that multiple objects of agiven object type are to be affected by the command.Object-name templates allow you to specify multiple objects by entering either a single wild-cardcharacter, or text and one or more wild-card characters. In the CIP subsystem, you can use thesewild-card characters:

Use an asterisk (*) to represent a character string of undefined length. The first example gives status allCLIMs subordinate to $ZZCIP. The second gives information on all CLIMs subordinate to $ZZCIP that have

*

names starting with CL. The third gives status for all CLIMs subordinate to $ZZCIP that have names startingwith CL and ending with 5.

SCF> STATUS CLIM $ZZCIP.*

SCF> INFO CLIM $ZZCIP.CL*

SCF> STATUS CLIM $ZZCIP.CL*5

Use the question mark to represent a single unknown character in a specific position. For example,$ZZCIP.S?1 selects all object names subordinate to $ZZCIP that begin with S, end with 1, and containexactly one character between the S and the 1.

?

You can use wildcard characters in any combination.If you have set a default process name by using the ASSUME command, you can omit theprocess name and use the asterisk (*) to specify all objects of the specified object type underthe assumed process. For example, the next two commands set the default process to $ZZCIPand display information about all CLIMs under $ZZCIP:SCF> ASSUME PROCESS $ZZCIPSCF> INFO CLIM *

AbbreviationsCommand and object type names can be abbreviated as long as the abbreviation is notambiguous. Table 28: Command and Object Type Abbreviations shows the minimal abbreviationscurrently allowed for CIP commands and object types:

Wildcard Support 215

Table 28 Command and Object Type Abbreviations

AbbreviationObject TypeAbbreviationCommand

CLICLIMABABORT

MOMONADADD

PROCPROCESSALTALTER

PROVPROVIDERDELEDELETE

ROUROUTEINFINFO

LISTOLISTOPENS

NANAMES

PRIPRIMARY

STARSTART

STATUSTATUS

SWSWITCH

TRTRACE

VERSVERSION

Summary StatesThe CIP subsystem objects have operational states, known as summary states. The summarystate of an object at a given instant is important; certain commands have no effect on an objectwhen it is in one state but can affect the object when it is in another state.The summary states supported by the CIP subsystem are STARTED/UP, STARTING, STOPPING,and STOPPED/DOWN. Table 29: Object Summary States shows states for each object:

Table 29 Object Summary States

STOPPINGSTARTINGSTARTEDSTOPPEDObject

null

XXXCLIM

XXXXMON

XXPROCESS (CIPMANor CIPSAM)

XXXPROVIDER

XSUBNET

ROUTE

Table 30: Object State Descriptions describes object states:

Table 30 Object State Descriptions

The object is...In this state...

Running and ready to accept requests from other subsystem components. This state is calledSTARTED in SCF and UP in CIP.

STARTED

Defined (that is, the object exists) but is not accepting requests from other subsystem components.The STOPPED summary state is not applicable to the PROCESS object. If the PROCESS objectis not STARTED, it is undefined (that is, the process does not exist).

STOPPED

216 SCF Reference for CIP

Table 30 Object State Descriptions (continued)

The object is...In this state...

Attempting to start, either because a command was issued to start it or because it is recoveringfrom an error.

STARTING

Shutting down because a command was issued to stop it.STOPPING

Sensitive and Nonsensitive CommandsTable 31: Sensitive and Nonsensitive SCF Commands lists the sensitive and nonsensitive CIPSCF commands. For information about how to use sensitive and nonsensitive commands, seethe SCF Reference Manual for J-Series and H-Series RVUs.

Table 31 Sensitive and Nonsensitive SCF Commands

Nonsensitive CommandsSensitive Commands

INFO CommandsABORT Commands

LISTOPENS CommandsADD Commands

NAMES CommandsALTER Command

STATS Commands (without the RESET option)DELETE Commands

STATUS CommandsSTART Commands

VERSION CommandsSTATS Command (with the RESET option)

STOP Commands

SWITCH Commandss

PRIMARY Commands

TRACE Commands

SCF HELP FacilityThe SCF HELP CIP command provides an online help facility for the NonStop host system sideof CIP. The syntax is:HELP CIP [ command [ object-type ]]HELP CIP

Gives an overview of the CIP subsystem.HELP CIP command

Explains the specified CIP command.HELP CIP command object-type

Explains the specified CIP command/object-type combination.HELP CIP object-type

Explains for a specified CIP object type.HELP CIP error number

Provides more detailed information about an error.For example, you can obtain help about error 00004 by entering help CIP 4 as shown:

Example 26 Using Help to Obtain Information About an Error

4> help cip 4

HELP CIP 00004

Sensitive and Nonsensitive Commands 217

CIP E00004 Duplicate attribute specified.

Probable Cause

You specified an attribute more than once in a command.

Recommended Action

Omit the duplicate attribute and retry the command.5>

LISTDEV CIP and LISTDEV TCPIPWhen you need to obtain a list of CIP processes, use the LISTDEV CIP command. The SCFLISTDEV CIP command lists all the CIP processes and the SCF LISTDEV TCPIP command listsall the TCP/IP processes (including conventional TCP/IP and NonStop TCP/IPv6, if present). Aprogram name in the SCF LISTDEV display of CIPSAM indicates a CIP socket access methodprocess.

CIPMAN SCF CommandsABORT Commands

ABORT is a sensitive command used to halt the operation of the specified object even if it hasexisting users. If any sockets are using the object, a warning is first issued and the operator mustconfirm that execution is desired, unless the FORCED option is specified. The object is left inthe STOPPED state if the command succeeds.

ABORT CLIMThe ABORT CLIM command stops operations on the specified CLIM even if it has open sockets.Existing sockets are closed and the CLIM refuses all new connections that would have beendirected to the NonStop host system. If the associated PROVIDER object is in the STARTEDstate, that provider goes to the STARTING state.ABORT CLIM Command SyntaxABORT CLIM $ZZCIP.clim-name [,FORCED ][,INTFALL]

clim-nameIs the name of the CLIM to abort. A wildcard can specify a set of the CLIMs known to thissystem.

FORCEDCauses the command to execute without displaying a warning and request for operatorconfirmation.

INTFALLCauses all interfaces configured on the specified CLIM to be stopped, even the ones thatare running on other CLIMs due to failover. This option works even if the specified CLIM(s)are already in the STOPPED state.

Example 27: ABORT CLIM ends operation of N1002532.

Example 27 ABORT CLIM

> ABORT CLIM $ZZCIP.N1002532Open sockets still exist, okay to continue? Y

ABORT MONThe ABORT MON command terminates the operation of the CIPMON process, even if it hasopen sockets, clearing all connections and closing all sockets on its processor. If the process

218 SCF Reference for CIP

has been configured as persistent (AUTORESTART not equal to 1 in the command definingCIPMON as a generic process), the persistence manager restarts it.This command can be used for online replacement of the CIPMON and CIP Library modules, asdiscussed in Chapter 3 (page 59).ABORT MON Command SyntaxABORT MON $ZZCIP.ZCMnn [,FORCED]

MON $ZZCIP.ZCMnnidentifies the CIPMON process to ABORT. The variable nn can be 00 through 15. A wildcardcan specify multiple MONs in this system.

Example 28: ABORT MON ends operation of the CIPMON process on processor 3.

Example 28 ABORT MON

> ABORT MON $ZZCIP.ZCM03Open sockets still exist, okay to continue? Y

ABORT MON GuidelinesIf autorestart is off or if CIPMON is not configured under the persistence manager, you mustallow a delay of at least 15 seconds between an ABORT or STOP MON command and asubsequent START MON command. This 15 second delay is necessary because MONs onprocessors that have sockets take longer to change their status to STOPPED after an ABORTor STOP than those on processors that do not have sockets. If the START is issued before the15 second delay, MONs start only on processors that do not have sockets. MONs on processorswith sockets stay in the stopped state and you need to reissue the START command.

NOTE: The recommended autorestart value is 10. With this setting, the problem does notoccur.

ABORT PROCESSThe ABORT PROCESS command terminates the operation of the CIPMAN process, even ifthere are open sockets. Subordinate objects need not be stopped and are not affected unlessSUB ALL or SUB ONLY is specified. If the process has been configured as persistent(AUTORESTART not equal to 1 in the command defining CIPMAN as a generic process), thepersistence manager restarts it. This command can be used for online replacement of the CIPMANmodule.If SUB ALL or SUB ONLY is used, the CIP subsystem stops operation, and all existing socketsare cleared. If any sockets exist, the command displays a warning and request for operatorconfirmation. The FORCED option overrides the warning and confirmation request.ABORT PROCESS Command SyntaxABORT PROCESS $ZZCIP[, SUB [ ONLY | ALL | NONE ]][,FORCED ]

SUBDetermines the set of objects and subordinate objects that the command targets:• ONLY specifies that only subordinate objects are targets of the command.

• ALL specifies that the named object and the subordinate objects are targets of thecommand. This is the default used if the SUB keyword is used but no option is selected.

• NONE specifies that none of the subordinate objects are targets of the command. Thisis the default selected if the SUB keyword is not used.

CIPMAN SCF Commands 219

FORCEDCauses the command to execute without displaying a warning and request for operatorconfirmation.

Causes the command to execute without displaying a warning and request for operatorconfirmation.Example 29 stops the CIP subsystem until the persistence manager restarts it.

Example 29 ABORT PROCESS

> ABORT PROCESS $ZZCIP , SUB ALLOpen sockets still exist, okay to continue? Y

ABORT PROCESS GuidelinesMON objects are not affected even with the SUB ALL or SUB ONLY options

ABORT PROVIDERThe ABORT PROVIDER command terminates operations on a provider, even if the provider hasopen sockets. Existing sockets and connections associated with the provider are cleared.ABORT PROVIDER Command SyntaxABORT PROVIDER $ZZCIP.prov-name [,FORCED]

prov-nameIs the name of the provider to abort. A wildcard can specify a set of providers.

FORCEDCauses the command to execute without displaying a warning and request for operatorconfirmation.

Example 30 halts PROVIDER ZTC2 with no warning, even if sockets currently exist:

Example 30 ABORT PROVIDER

> ABORT PROVIDER $ZZCIP.ZTC2 , FORCED

ABORT PROVIDER GuidelinesHewlett Packard Enterprise recommends having a 15–second delay between issuing an ABORTPROVIDER command and issuing a DELETE PROVIDER command. This delay is especiallyrecommended for the MAINTENANCE PROVIDER.

ADD CommandsADD is a sensitive command that adds an object to the CIP subsystem. The fully qualified nameassigned to the created object must be unique. The ADD command does not support wildcardcharacters.The CIP subsystem does not support the ADD MON or ADD PROCESS command. Add theCIPMON and CIPMAN processes in the Kernel subsystem, as described in Chapter 3 (page 59).

ADD CLIMThe ADD CLIM command makes a CLIM known to the system by specifying the name andlocation of the CLIM. The subsystem does not reveal whether an operational CLIM exists at thespecified LOCATION until the CLIM object is started.ADD CLIM Command SyntaxADD CLIM $ZZCIP.clim-name,LOCATION (group, module, slot, port, fiber)[ , CONNPTS { 1 | 2 } ]

220 SCF Reference for CIP

[ , MODE STORAGE | [, MODE {IP | OPEN}][, MULTIPROV { ON | OFF } ][, PROVIDER prov-name] ]

ADD CLIM Command Syntax for NonStop X SystemsADD CLIM $ZZCIP.clim-name[ , MODE STORAGE | [, MODE {IP | OPEN}]

[, MULTIPROV { ON | OFF } ][, PROVIDER prov-name] ]

clim-nameSpecifies the name to be assigned to the CLIM. The name must be from one to eightalphanumeric characters long and use a leading alphabetic character. It must be uniquewithin this system. The name must be the same as the CLIM hostname defined in theclimconfig hostname command.Hewlett Packard Enterprise recommends using a naming convention that identifies the physicallocation of the CLIM. See “Naming Convention Summary” (page 214) for information abouthow to name the CLIM.

LOCATION (group ,module, slot, port, fiber )

NOTE: LOCATION is not supported on NonStop X systems.

Identifies the CLIM in terms of the physical location of the ServerNet switch to which the CLIMis connected. The group specifies the system enclosure, the module specifies the subset ofthe group, the slot specifies physical, labeled space in the module that identifies a particularServerNet PIC. The port identifies a specific ServerNet connector within the ServerNet switchto which the CLIM is connected by a ServerNet cable. The fiber identifies a specific connectorwithin ServerNet cable to which the CLIM is connected.Any one of the ServerNet ports to which the CLIM is connected can be specified and theother(s) are discovered automatically.The same location must not already be in use by another configured CLIM.The CLIM LOCATION attributes depend on whether your system has P-switches, VIOmodules, or Blade switches. Valid CLIM LOCATION attributes for each of these types are:

FiberPortSlotModuleGroup

not supported1, 2, 3, 44, 5, 6, 7, 8, 92 for X-fabric and3 for Y-fabric

100P-Switch

not supported1, 2, 3, 43, 42 for X-fabric and3 for Y-fabric

100VIO

1, 2, 3, 43, 4, 5, 6, 7, 85 for X-fabricand 7 forY-fabric

2 for X-fabric and3 for Y-fabric

100, 101, 102,103

Blade switch

CONNPTS { 1 | 2 }

NOTE: CONNPTS is not supported on NonStop X systems.

Indicates whether there are one or two ServerNet connections for each fabric between theCLIM and the NonStop host system. The default is 2 for a STORAGE-mode CLIM and 1 foran IP-mode CLIM.

MODE { IP | STORAGE | OPEN }Specifies the operation mode of the CLIM. IP mode provides access to TCP/IP networking.STORAGE mode provides access to disks and other storage devices. OPEN MODE providesaccess to the IB or Telco CLIM. The default MODE is IP.

CIPMAN SCF Commands 221

MULTIPROV { ON | OFF }Specifies whether the new CLIM will support association with multiple IPDATA providerssimultaneously. MULTIPROV OFF means that the CLIM can only be associated with theIPDATA provider specified by the PROVIDER attribute of that CLIM. MULTIPROV ON meansthat each data interface can be independently associated with an IPDATA provider.MULTIPROV ON is only supported on IP or IB CLIMs. The default is MULTIPROV OFF.

PROVIDER prov-nameIs the name of the single provider associated with an IP, Telco or IB CLIM when MULTIPROVis OFF. If this CLIM has the MULTIPROV attribute set to ON, this provider is only used foran initial provider association for that CLIM during migration from MULTIPROV OFF.The provider must already exist and must be of type IPDATA, but need not be started whenconfigured. This attribute is valid only for an IP, Telco or IB CLIM (i.e., a CLIM that can beused for TCP/IP networking).The same IPDATA provider can be associated with more than one CLIM. The default provideris ZTC0, which always exists and always is of type IPDATA.

Example 31 adds to the system a network CLIM named N1002533 that is connected to theServerNet switch in group 100, module 2, slot 5, port 3, fiber 3 and is associated with PROVIDERCSAM:

Example 31 ADD IP CLIM

> ADD CLIM $ZZCIP.N1002533, LOCATION (100,2,5,3,3), PROVIDER CSAM, MODE IP

Example 32 adds to a NonStop X system a network CLIM named NCLIM005 that is connectedvia InfiniBand and supports multiple providers:

Example 32 ADD IP CLIM, NonStop X

> ADD CLIM $ZZCIP.NCLIM005, MODE IP, MULTIPROV ON

Example 33 adds to and H- or J-series system a Storage CLIM named S1002531 that is connectedto the ServerNet switch in group 100, module 2, slot 5, port 3, fiber 1:

Example 33 ADD Storage CLIM

> ADD CLIM $ZZCIP.S1002531, LOCATION (100,2,5,3,1), MODE STORAGE

Example 34 adds to a NonStop X system a Storage CLIM named SCLIM000:

Example 34 ADD Storage CLIM, NonStop X

> ADD CLIM $ZZCIP.SCLIM000, MODE STORAGE

ADD CLIM Guidelines

• For a CLIM with MULTIPROV ON, an IPDATA provider is associated with each data interfacethat can be changed by the climconfig command. For an IP or OPEN MODE CLIM withMULTIPROV OFF, all data interfaces are associated with the IPDATA provider specified bythe PROVIDER attribute of that CLIM.

• The MULTIPROV attribute of a CLIM object has a direct impact on a CLIM-based configuration(a network configuration added using climconfig with the PROV attribute specified). Whenthe MULTIPROV attribute is changed, the CLIM-based configuration is updated by CIPsoftware to reflect the change in the MULTIPROV attribute. If MULTIPROV is changed fromOFF to ON, all network resources already configured on the CLIM are associated with theprovider specified by the PROVIDER attribute of the CLIM object. If MULTIPROV is changed

222 SCF Reference for CIP

from ON to OFF, all network resources configured on that CLIM (specified by the PROVIDERattribute of the climconfig command used to configure the network resource) will no longerbe explicitly associated with any specific provider, but are implicitly associated with thePROVIDER attribute of the CLIM object.

ADD PROVIDERThe ADD PROVIDER command creates a transport-service provider for application use. ThePROVIDER object allows you to specify certain characteristics for applications such as IPv4 orIPv6.ADD PROVIDER Command SyntaxADD PROVIDER $ZZCIP.prov-name[[,TYPE IPDATA][,SHARE-PORTS num-ports][,FAMILY {INET | DUAL}]|,TYPE MAINTENANCE, CLIM clim-name, IPADDRESS ip-addr][,TPNAME tp-name][,HOSTNAME hostname][,HOSTID hostid][,BRECVPORT (port [,port [...]])][,TCP-LISTEN-QUE-MIN queue-size]

prov-nameSpecifies the name given to the provider. The name must be from one to seven alphanumericcharacters long and use a leading alphabetic character. If the name is no more than fivecharacters long, it can serve as both the provider name and the CIPSAM process name; inthat case, omit the TPNAME option from the command. However, if the provider name ismore than five characters long, it cannot be a CIPSAM process name; in that case, you mustuse the TPNAME option to specify the CIPSAM process name. The provider name must beunique within this system.

TYPE {IPDATA | MAINTENANCE}Specifies the type of provider. IPDATA provider provides TCP/IP access by means of thedata Ethernet ports of one or more CLIMs associated with that IPDATA provider.MAINTENANCE provider provides TCP/IP access by means of the maintenance Ethernetinterface of a specific CLIM using a specific IP address. The default TYPE is IPDATA.

SHARE-PORTS num-portsIs the number of ports reserved for TCP, SCTP, and UDP shared-ephemeral ports that canbe on multiple CLIMs. Shared-ephemeral ports are those assigned by the CIP subsystemwhen an application has not bound to a specific IP address and interface. This attribute isvalid only for a provider of TYPE IPDATA. The default is 1000. Possible values are in therange from 100 to 4000.

FAMILY {INET | DUAL}Specifies the network mode of the provider. You can specify these modes:• INET – the provider is operated in IPv4 only mode

• DUAL – the provider is operated in both IPv4 mode and IPv6 modeThe default FAMILY is INET.

CLIM clim-nameIs the name of the CLIM associated with the Maintenance provider. This attribute is valid onlyfor a provider of TYPE MAINTENANCE. The CLIM must already have been added and mustbe of IP MODE (that is, it must support TCP/IP networking), but does not need to be started.The same CLIM must not be associated with any other Maintenance provider.

CIPMAN SCF Commands 223

IPADDRESS ip-addrSpecifies the IPv4 address associated with the Maintenance provider. This attribute is validonly for a provider of TYPE of MAINTENANCE. The IP address must be associated with themaintenance provider interface of the CLIM associated with the Maintenance provider (usingCLIM-based configuration) before the Maintenance provider can be accessible by socketapplications. Only class A, B, or C IP addresses are supported. IP address 127.*.*.* and Dand E type addresses are not supported.

TPNAME tp-nameIs the CIPSAM transport-service provider process name. This is the name applications useto select the provider. It must be a valid process name with a leading dollar sign ($). Thedefault value is the name of the PROVIDER object itself with a dollar sign ($) prepended.The process need not exist when you add the provider.

HOSTNAME hostnameIs the hostname returned by gethostname() when the transport-service provider is selected.The hostname is a string of up to 49 characters. The default is the Expand system namewithout the leading backslash (\).

HOSTID hostidIs the host ID returned by gethostid() when the provider is selected. The host ID is in dottedquad format similar to an IPv4 address (but it is not actually an IPv4 address). The defaultvalue is 0.0.0.0.

BRECVPORT ( [ , port ] [ , port ] ... )Specifies the UDPports that receive broadcast messages on sockets bound to specific IPaddresses or INADDR_ANY. Ports not in the list can receive broadcast messages only onsockets bound to INADDR_ANY. Up to eight port numbers can be specified. The range foreach port number is 1 to 65535. The default is no port specified.

NOTE: If any of the specified UDP ports are in the ephemeral or shared ephemeral portrange, the behavior is the same as those ports not being specified.

TCP-LISTEN-QUE-MIN queue-sizeIs the minimum queue length that is allocated on a TCP socket when a socket LISTEN orACCEPT_NW1 function call is handled. This value is used if the queue length specified inthe socket request is lower, otherwise the queue length in the socket request is used. Thedefault is 128. The range is 1 to 1024.

Example 35 adds an IPDATA provider named CSAM with an associated CIPSAM named $CSAM.The HOSTNAME is the local system name (MYSYS).

Example 35 ADD PROVIDER

> ADD PROVIDER $ZZCIP.CSAM

ADD PROVIDER Guidelines

• The CIP subsystem automatically adds a default IPDATA provider named ZTC0 duringsubsystem start up if that provider does not already exist. This default IPDATA providercannot be deleted.

• There is no access to the loopback IP address over Maintenance providers.

• PROVIDER objects of TYPE MAINTENANCE always operate in IPv4–only mode.

• The correct order for adding CLIM and PROVIDER objects to the CIP subsystem is:

224 SCF Reference for CIP

Add PROVIDER objects with IPDATA TYPE1.2. Add CLIM objects3. Add PROVIDER objects with MAINTENANCE TYPE

• Hewlett Packard Enterprise recommends having a 15 second delay between issuing aDELETE PROVIDER command and issuing an ADD PROVIDER command. This delay isespecially recommended for the MAINTENANCE provider.

ADD ROUTEThe SCF ADD ROUTE command creates a new ROUTE object in this system associated withan existing IPDATA provider. By adding a ROUTE, you can cause a provider to use a specificCLIM for default routing (when there is a valid default route configured on that CLIM). The SCFROUTE object creates a route from the host to the specified CLIM. (See “ROUTE Object”(page 214) for more information about using the ROUTE object in CIP.)ADD ROUTE Command SyntaxADD ROUTE $ZZCIP prov-name.route-name, CLIM clim-name, FAMILY { INET | INET6 | DUAL }[,PRIORITY priority]

prov-nameSpecifies the parent provider. The provider must already exist and must be of type IPDATA.

route-nameSpecifies the name to be assigned to the ROUTE. The name must be from one to eightalphanumeric characters long and use a leading alphabetic character. It must be uniquewithin the parent provider.

CLIM clim-nameIs the name of the CLIM associated with ROUTE. If the specified CLIM has the MULTIPROVattribute set to OFF, that CLIM must be associated with the parent provider (through thePROVIDER attribute of that CLIM). To be configured, the CLIM must already have beenadded, but need not be started. The same CLIM must not be associated with any otherROUTE object of the same family type with the same parent provider as this new ROUTEobject.

FAMILY { INET | INET6 | DUAL }Specifies the IP family for which this ROUTE object is applicable. This value can be:• INET, which indicates this ROUTE object is applicable to IPv4

• INET6, which indicates this ROUTE object is applicable to IPv6

• DUAL, which indicates this ROUTE object is applicable to both IPv4 and IPv6The default value is the same as the parent IPDATA provider object FAMILY (either INET orDUAL).

PRIORITY prioritySpecifies the relative priority level of ROUTE in relation to other ROUTE objects associatedwith the same provider. The priority value must be between 1 and 100. The default value is50.

Example 36 adds a route named ROUTE1 associated with parent PROVIDER ZTC0 and withN1002532. The priority is 50.

CIPMAN SCF Commands 225

Example 36 ADD ROUTE

> ADD ROUTE $ZZCIP.ZTC0.ROUTE1, CLIM N1002532

ALTER CommandThe ALTER command includes ALTER CLIM and ALTER PROVIDER.

ALTER CLIMThe ALTER CLIM command is a sensitive command that changes one or more attributes of anexisting CLIM in the target system. Only MULTIPROV and PROVIDER attributes can be changedusing the ALTER CLIM command.ALTER CLIM Command SyntaxALTER CLIM $ZZCIP.clim-name[, MULTIPROV { ON | OFF } ][, PROVIDER prov-name ]

clim-namespecifies the name of the CLIM to be altered.

MULTIPROV { ON | OFF }Specifies whether the new CLIM will support association with multiple IPDATA providerssimultaneously. MULTIPROV OFF means that the CLIM can only be associated with theIPDATA provider specified by the PROVIDER attribute of that CLIM. MULTIPROV ON meansthat each CLIM can be associated with multiple IPDATA providers. MULTIPROV ON is onlysupported on IP or IB CLIMs. The default is MULTIPROV OFF.

PROVIDER prov-nameIs the name of the single provider associated with an IP, Telco or IB CLIM when MULTIPROVis OFF. If this CLIM has the MULTIPROV attribute set to ON, this attribute is only used foran initial provider association for that CLIM during migration from MULTIPROV OFF.The provider must already exist and must be of type IPDATA. This attribute is valid only foran IP, Telco or IB CLIM (i.e., a CLIM that can be use for TCP/IP networking).The same IPDATA provider can be associated with more than one CLIM. The default provideris ZTC0, which always exists and always is of type IPDATA.

This command reconfigures CLIM N1002541 so its MULTIPROV attribute is ON.:

Example 37 ALTER CLIM With MULTIPROV ON

> ALTER CLIM $ZZCIP.N1002541, MULTIPROV ON

ALTER CLIM Guidelines

• If the specified CLIM has the MULTIPROV attribute set to OFF, the PROVIDER attributecan be altered only when the specified CLIM is in STOPPED state with no active interfacesfailed-over to any other CLIMs and there are no ROUTE objects associated with the specifiedCLIM.

• The MULTIPROV attribute can be altered to OFF only if the parent of all ROUTE objectsassociated with the specified CLIM is the same as the PROVIDER attribute of that CLIM.

• The MULTIPROV attribute can be altered to OFF when the specified CLIM is in STARTEDstate only if all configured network resources on the specified CLIM are associated with theprovider specified by the PROVIDER attribute of that CLIM.

• If both the MULTIPROV and PROVIDER attributes are being altered with the same commandline, the behavior is the same as first altering the PROVIDER attribute (assuming the previousvalue of the MULTIPROV attribute) followed by altering the MULTIPROV attribute. If eitherattribute cannot be altered, both attributes will not be changed and the command will fail.

226 SCF Reference for CIP

• If the MULTIPROV attribute is altered successfully while the CLIM is not in STARTED state,the CIP subsystem will attempt to make sure that the configuration on that CLIM matchesthe updated MULTIPROV attribute during CLIM start up. If the configuration on that CLIMcannot be converted to match the updated MULTIPROV attribute, the CLIM will not be ableto go to STARTED state and there will be an EMS event to indicate a configuration mismatchproblem. In particular, if the MULTIPROV attribute is OFF but the CLIM is configured withMULTIPROV ON and has any configured network resources associated with a providerother than the provider specified by the PROVIDER attribute of that CLIM object, then theCLIM configuration cannot be converted to MULTIPROV OFF.

• The CLIM may be altered in any state with the restrictions listed above.

ALTER PROVIDERThe ALTER PROVIDER command is a sensitive command that changes one or more attributesof an existing provider in the target system.ALTER PROVIDER Command SyntaxALTER PROVIDER $ZZCIP.prov-name[,TPNAME tp-name][,HOSTNAME hostname][,HOSTID hostid][,BRECVPORT {RESET |(port [,port [...]])][,TCP-LISTEN-QUE-MIN queue-size ][[,SHARE-PORTS num-ports] [,FAMILY {INET|DUAL}]|[,CLIM clim-name], IPADDRESS ip-addr]]

prov-namespecifies the name of the provider to be altered

For the attribute definitions, see “ADD PROVIDER” (page 223)Example 38 reconfigures PROVIDER ZTC1 so its HOSTID is 25.0.0.0.

Example 38 ALTER PROVIDER

> ALTER PROVIDER $ZZCIP.ZTC1, HOSTID 25.0.0.0

ALTER PROVIDER Guidelines

• The CLIM attribute and IPADDRESS attribute can be altered only when the specified provideris of MAINTENANCE TYPE and is in the STOPPED state.

• The SHARE-PORTS attribute can be altered only when the specified provider is of IPDATATYPE, the provider is in the STOPPED STATE, and all associated CLIMs are in theSTOPPED state (or there is no associated CLIM). Associated CLIMs include all CLIMs withMULTIPROV ON that have one or more interfaces associated with the specified provider.

• The FAMILY attribute can be altered only when the specified provider is of IPDATA TYPEand is in STOPPED state.

• HOSTNAME, HOSTID, BRECVPORT, and TCP-LISTEN-QUE-MIN attributes can be alteredeven when the specified provider is in the STARTING or STARTED state. However, the newattribute values do not apply retroactively. For example, only new socket requests after theALTER PROVIDER command completion are affected by the new attribute values.

• TPNAME can only be altered when the specified Provider is in the STOPPED state.

• Specifying BREVPORT RESET resets the list of UDP ports that receive broadcast messageson sockets bound to specific IP addresses or INADDR_ANY. The reset is to no ports specified.If you specify BRECVPORT with a list of ports, CIP sets the list of UDP ports that receivebroadcast messages on sockets bound to specific IP addresses or INADDR_ANY to thenew list of ports. The old list (if it existed) is ignored and no longer stored.

CIPMAN SCF Commands 227

DELETE CommandsDELETE is a sensitive command that removes the specified object from the subsystem.

DELETE CLIMThe DELETE CLIM command deletes the specified CLIM object from this system.DELETE CLIM Command SyntaxDELETE CLIM $ZZCIP.clim-name

clim-nameSpecifies the name of the CLIM to delete.

Example 39 deletes S1003741 from this system.

Example 39 DELETE CLIM

> DELETE CLIM $ZZCIP.S1003741

DELETE CLIM Command Guidelines

• The CLIM object must be in the STOPPED state, and no MAINTENANCE PROVIDER canexist that specifies the CLIM in its configuration. If an existing MAINTENANCE PROVIDERrefers to the CLIM in its configuration, you must delete the MAINTENANCE PROVIDERbefore deleting the CLIM.

• If there are any ROUTE objects subordinated to the associated IPDATA provider object thatpoint to the specified CLIM, you cannot delete the CLIM . You must delete those ROUTEobjects before deleting the CLIM.

• If there are any interfaces associated with the specified CLIM still running on a failover CLIM,you cannot delete the CLIM. Use the STATUS CLIM command to obtain the list of CLIMinterfaces that are still running. Use the ABORT CLIM, INTFALL command to stop theseinterfaces on the failover CLIM.

• If the CLIM is configured in STORAGE MODE and is being used by the storage subsystem,you cannot delete the CLIM.

DELETE PROVIDERThe DELETE PROVIDER command deletes the specified provider from this system. The providermust be in the STOPPED state, and no CLIM can exist that specifies the provider in itsconfiguration. For the IPDATA provider, if an existing CLIM refers to the provider in itsconfiguration, you must delete the CLIM before deleting the provider.The subordinated ROUTE objects must be deleted before the PROVIDER object can be deleted.DELETE PROVIDER Command SyntaxDELETE PROVIDER $ZZCIP.prov-name

prov-nameIs the name of the provider to delete.

Example 40 deletes the provider named ZTC2.

Example 40 DELETE PROVIDER

> DELETE PROV $ZZCIP.ZTC2

Guidelines

• The default IPDATA provider name ZTC0 cannot be deleted.

• The proper order for deleting objects is:

228 SCF Reference for CIP

Remove all ROUTE objects1.2. Remove all PROVIDER objects of TYPE MAINTENANCE3. Remove all CLIM objects4. Remove all PROVIDER objects of TYPE IPDATAThis order avoids the problem of a delete request being rejected due to the specified objectbeing referenced by other objects.

• Hewlett Packard Enterprise recommends a 15–second delay between issuing a DELETEPROVIDER command and issuing an ADD PROVIDER command. This delay is especiallyrecommended for the MAINTENANCE PROVIDER.

• The IPDATA provider object cannot be deleted if there are configured interfaces associatedwith the provider, including data interfaces configured on CLIMs that have the MULTIPROVattribute set to ON. To see these data interfaces, issue the CLIMCMD{clim-name|ip-address} climconfig prov -info {prov-name | all}, as described underclimconfig.prov(1).

DELETE ROUTEThe SCF DELETE ROUTE command deletes the specified ROUTE object from this system.DELETE ROUTE Command SyntaxDELETE ROUTE $ZZCIP.prov-name.route-name

prov-nameSpecifies the parent provider.

route-nameSpecifies the name of the ROUTE to delete.

Example 41 deletes a ROUTE named ROUTE2 associated with parent provider ZTC1.

Example 41 DELETE ROUTE

> DELETE ROUTE $ZZCIP.ZTC1.ROUTE2

INFO CommandsINFO is a non-sensitive command that displays the configured settings for the specified object.An asterisk (*) next to a field name in the display indicates that the attribute is alterable. By default,the command displays a summary of the object configuration. Some commands allow specificationof one or either of the following modifiers to change the output format:DETAIL

Specifies that the display is to include additional detailed information about the object.OBEYFORM

Causes the configuration to be displayed as ADD or ALTER commands so that it can bere-created.

INFO CLIMThe INFO CLIM command displays the configured attributes for the specified CLIM(s).

NOTE: The storage subsystem ($ZZSTO) also supports an INFO CLIM command. For syntaxand display examples, see the SCF Reference Manual for the Storage Subsystem.

INFO CLIM Command SyntaxINFO CLIM $ZZCIP.clim-name[,{DETAIL | OBEYFORM}]

clim-nameIs the name of the CLIM to display. A wildcard can specify multiple CLIMs.

CIPMAN SCF Commands 229

DETAILSpecifies that the display is to include additional detailed information about the CLIM.

OBEYFORMCauses the configuration to be displayed as ADD command(s), so that it can be re-created.

Example 42 displays summary information for all CLIMs recognized by this system.

Example 42 INFO CLIM, Summary, NonStop NS16000 Series Server

> INFO CLIM $ZZCIP.*CIP Info CLIM

Name Mode Location ConnPts ProviderN100241 IP (100 ,2 ,4 ,1) 2 ZTC0N100373 IP (100 ,2 ,5 ,1) 2 ZTC0S101252 STORAGE (101 ,2 ,5 ,1 ) 2 --S101373 STORAGE (101 ,3 ,7 ,3 ) 2 --

ModeShows the operating mode of the CLIM. An IP or IB CLIM provides access to TCP/IPnetworking. A STORAGE CLIM provides access to disks and other storage devices. A TelcoCLIM (Mode OPEN) provides access to Telco protocols to communicate with a Telco network.

LocationShows the location specified in the ADD CLIM command and is composed of five numbers:group, module, slot, port, and fiber.

ConnPtsShows whether there are one or two ServerNet connections for each fabric between the CLIMand the NonStop host.

ProviderShows the name of the IPDATA provider associated with a CLIM that is configured for IPMODE.

Example 43 shows summary information for all known CLIMs on a NonStop system.

Example 43 INFO CLIM, Summary, NonStop BladeSystem

> INFO CLIM $ZZCIP.*CIP Info CLIM

Name Mode Location ConnPts Provider *MultiProvN1002541 IP (100 ,2 ,5 ,4 ,1 ) 2 ZTC0 ONN1002551 IP (100 ,2 ,5 ,5 ,1 ) 2 ZTC0 ONN1002581 IP (100 ,2 ,5 ,8 ,1 ) 1 ZSAM1 OFFN1002553 STORAGE (100 ,2 ,5 ,5 ,3 ) 2 -- --

MultiProvShows whether the specified CLIM supports association with multiple IPDATA providerssimultaneously.

The other fields are the same as in the preceding example, Example 42Example 44 displays summary information for all NonStop X CLIMs recognized by this system.

Example 44 INFO CLIM With Summary Display, NonStop X

> INFO CLIM $ZZCIP.*CIP Info CLIM

Name Mode *Provider *MultiProv

230 SCF Reference for CIP

NCLIM000 IP ZTC0 ONNCLIM001 IP ZTC0 ONNCLIM002 IP ZSAM1 OFFNCLIM000 STORAGE -- --NCLIM001 STORAGE -- --

The field definitions are the same as in the previous two examples, Example 42 and Example 43.Example 45 displays detailed information for N1002541, which is configured for IP MODE.

Example 45 INFO CLIM, Detailed, IP CLIM, NonStop BladeSystem

> INFO CLIM $ZZCIP.N1002541, DETAILCIP Detailed Info CLIM \MYSYS.$ZZCIP.N1002541

Mode....................... IPConfigured Location........ Group 100 , Module 2 , Slot 5 , Port 4 , Fiber 1ConnPts.................... 2X1 Location................ Group 100 , Module 2 , Slot 5 , Port 4 , Fiber 1Y1 Location................ Group 100 , Module 3 , Slot 7 , Port 3 , Fiber 1SvNet ID 1................. 0x000E3F22X2 Location................ Group 100 , Module 2 , Slot 5 , Port 3 , Fiber 2Y2 Location................ Group 100 , Module 3 , Slot 7 , Port 3, Fiber 2SvNet ID 2................. 0x000E3F23Maintenance Interface IP... 192.168.37.41 (Last Known)

Network CLIM Information:*MultiProv.................. ON*Provider................... ZTC0Index...................... 2

Maintenance Providers Configured:ZTCP0 192.168.36.10

ModeShows the operating mode of the CLIM. An IP or IB CLIM provides access to TCP/IPnetworking. A STORAGE CLIM provides access to disks and other storage devices. A TelcoCLIM (Mode OPEN) provides access to Telco protocols to communicate with a Telco network.

Configured LocationLists the location configured in the ADD CLIM command.

ConnPtsShows whether there are one or two ServerNet connections for each fabric between the CLIMand the NonStop host.

X1 LocationShows the CLIM's expected X-fabric connection location based on the configured location.

Y1 LocationShows the CLIM's expected Y-fabric connection location based on the configured location.

SvNet ID 1Shows the CLIM ServerNet ID based on the configured location.

X2 LocationShows the CLIM’s expected second X-fabric connection location based on the configuredlocation. This attribute is applicable only when the CLIM’s CONNPTS attribute is 2.

Y2 LocationShows the CLIM’s expected second Y-fabric connection location based on the configuredlocation. This attribute is applicable only when the CLIM’s CONNPTS attribute is 2.

CIPMAN SCF Commands 231

SvNet ID 2Shows the CLIM’s second ServerNet ID based on the configured location. This attribute isapplicable only when the CLIM’s CONNPTS attribute is 2.

Maintenance Interface IPShows the dedicated service LAN (eth0) IP address of the CLIM.If the CLIM is in the STOPPED state, this field indicates the last known dedicated serviceLAN IP address. If the information is not known, Not Known is displayed. If the informationis based on last known information, but may not be accurate, (Last Known) is shown afterthe IP address.

MultiProvShows whether the specified IP, IB or Telco CLIM supports association with multiple IPDATAproviders simultaneously.

ProviderShows the name of the single IPDATA provider associated with an IP, IB or Telco CLIM withMULTIPROV OFF. For an IP, IB or Telco CLIM with MULTIPROV ON, this shows the nameof the IPDATA provider that would be associated with all networking objects configured onthe CLIM during conversion from MULTIPROV OFF CLIM-based configuration to MULTIPROVON CLIM-based configuration.

IndexShows the index value for this IP, IB or Telco CLIM within the associated IPDATA provider.This attribute is applicable only when the CLIM is configured IP, IB or Telco. This value isinternally generated by CIPMAN.

Maintenance Providers ConfiguredShows the name of maintenance providers that are associated with this CLIM and the IPaddresses that have been configured for each maintenance provider. This attribute isapplicable only when the CLIM is configured with IP MODE. This entry is not shown if nomaintenance provider is associated with this CLIM.

Example 46 INFO CLIM, Detailed, IP CLIM, NonStop X

> INFO CLIM $ZZCIP.NCLIM000, DETAILCIP Detailed Info CLIM \MYSYS.$ZZCIP.NCLIM000

Mode....................... IPX-FABRIC ID 0X0A030100Y-FABRIC ID 0X0A830100Maintenance Interface IP... 192.168.122.45 (Last Known)

Network CLIM Information:*MultiProv.................. OFF*Provider................... ZTC0Index...................... 1

Maintenance Providers Configured:ZTCP1 192.168.36.10

ModeShows the operating mode of the CLIM. An IP or IB CLIM provides access to TCP/IPnetworking. A STORAGE CLIM provides access to disks and other storage devices. A TelcoCLIM (Mode OPEN) provides access to Telco protocols to communicate with a Telco network.

X-Fabric IDShows the CLIM’s Fabric ID for X-Fabric. Value of 0 indicates that this information is notavailable.

232 SCF Reference for CIP

Y-Fabric IDShows the CLIM’s Fabric ID for Y-Fabric. Value of 0 indicates that this information is notavailable.

Maintenance Interface IPShows the dedicated service LAN (eth0) IP address of the CLIM.If the CLIM is in the STOPPED state, this field indicates the last known dedicated serviceLAN IP address. If the information is not known, Not Known is displayed. If the informationis based on last known information, but may not be accurate, (Last Known) is shown afterthe IP address.

MultiProvShows whether the specified IP, IB or Telco CLIM supports association with multiple IPDATAproviders simultaneously.

ProviderShows the name of the single IPDATA provider associated with an IP, IB or Telco CLIM withMULTIPROV OFF. For an IP, IB or Telco CLIM with MULTIPROV ON, this shows the nameof the IPDATA provider that would be associated with all networking objects configured onthe CLIM during conversion from MULTIPROV OFF CLIM-based configuration to MULTIPROVON CLIM-based configuration.

IndexShows the index value for this IP, IB or Telco CLIM within the associated IPDATA provider.This attribute is applicable only when the CLIM is configured with IP or OPEN MODE. Thisvalue is internally generated by CIPMAN.

Maintenance Providers ConfiguredShows the name of maintenance providers that are associated with this CLIM and the IPaddresses that have been configured for each maintenance provider. This attribute isapplicable only when the CLIM is configured with IP MODE. This entry is not shown if nomaintenance provider is associated with this CLIM.

This is a sample detailed display of Telco CLIM O1002543, (Open MODE):

Example 47 INFO CLIM Detailed, Telco CLIM, OPEN MODE, NonStop BladeSystem

> INFO CLIM $ZZCIP.01002543, DETAILCIP Info 01002543 DETAIL

CIP Detailed Info CLIM \MYSYS.$ZZCIP.01002543

Mode....................... OPENConfigured Location........ Group 100 , Module 2 , Slot 5 , Port 4, Fiber 3ConnPts.................... 2X1 Location................ Group 100 , Module 2 , Slot 5 , Port 4, Fiber 3Y1 Location................ Group 100 , Module 3 , Slot 7 , Port 4, Fiber 3SvNet ID 1................. 0x000E3F26X2 Location................ Group 100 , Module 2 , Slot 5 , Port 4, Fiber 4Y2 Location................ Group 100 , Module 3 , Slot 7 , Port 4, Fiber 4SvNet ID 2................. 0x000E3F27Maintenance Interface IP... 192.168.37.43

Network CLIM Information:MultiProv.................. OFFProvider................... ZSAM2Index...................... 0

For definitions of the fields, see Example 45 (page 231).This is a sample detailed display of S1002551, configured as Storage MODE:

CIPMAN SCF Commands 233

Example 48 INFO CLIM Detailed, Storage, NonStop BladeSystem

> INFO CLIM $ZZCIP.S1002551, DETAILCIP Detailed Info CLIM \MYSYS.$ZZCIP.S1002551

Mode....................... STORAGEConfigured Location........ Group 100 , Module 2 , Slot 5 , Port 5 , Fiber 1ConnPts.................... 2X1 Location................ Group 100 , Module 2 , Slot 5 , Port 5 , Fiber 1Y1 Location................ Group 100 , Module 3 , Slot 7 , Port 5 , Fiber 1SvNet ID 1................. 0x000E3F28X2 Location................ Group 100 , Module 2 , Slot 5 , Port 5 , Fiber 2Y2 Location................ Group 100 , Module 3 , Slot 7 , Port 5 , Fiber 2SvNet ID 2................. 0x000E3F29Maintenance Interface IP... 192.168.37.51

Example 49 INFO CLIM Detailed, Storage, NonStop X

> INFO CLIM $ZZCIP.SCLIM000, DETAILCIP Detailed Info CLIM \MYSYS.$ZZCIP.SCLIM000

Mode....................... STORAGEX-Fabric ID................ 0x0A020100Y-Fabric ID................ 0x0A820100Maintenance Interface IP... 192.168.122.35

For definitions of the fields, see the IP CLIM example.A sample display N1002531 in the form of a command (Obey) file is:

Example 50 INFO CLIM With OBEYFORM Display, NonStop BladeSystem

> INFO CLIM $ZZCIP.N1002531, OBEYFORMADD CLIM $ZZCIP.N1002531 , &

MODE IP , &CONNPTS 2 , &LOCATION (100 , 2 , 5 , 3 , 1 ) , &MULTIPROV OFF , &PROVIDER ZSAM2

Example 51 INFO CLIM With OBEYFORM Display, NonStop X

> INFO CLIM $ZZCIP.NCLIM000, OBEYFORMADD CLIM $ZZCIP.NCLIM000 , &

MODE IP , &MULTIPROV OFF , &PROVIDER ZSAM2

INFO PROCESSThe INFO PROCESS command displays attributes of the CIPMAN process. The DETAIL andOBEYFORM options are not valid for this command.INFO PROCESS Command SyntaxINFO PROCESS $ZZCIP

Example 52 displays summary information for CIPMAN on this system.

234 SCF Reference for CIP

Example 52 INFO PROCESS Summary

> INFO PROCESS $ZZCIPCIP Info PROCESS \MYSYS.$ZZCIP

PPID................ ( 2,289) BPID............... ( 3,271)

INFO PROVIDERThe INFO PROVIDER command displays the configured attributes for the specified PROVIDERson this system.INFO PROVIDER Command SyntaxINFO PROVIDER $ZZCIP.prov-name [,DETAIL | ,OBEYFORM]

provider-nameIs the name of the PROVIDER object about which to display information. A wildcard canspecify multiple providers.

DETAILSpecifies that the display is to include additional detailed information about the provider.

OBEYFORMCauses the configuration to be displayed as ADD or ALTER command(s), so that it can bere-created.

Example 53 displays summary information for all PROVIDER objects.

Example 53 INFO PROVIDER Summary Display

> INFO PROVIDER $ZZCIP.*CIP Info PROVIDER

Name *TPName TYPE *HOSTNAMEPROV1 $ZCSM1 IPDATA MYSYSZTC0 $ZTC0 IPDATA MYSYSZTCP0 $ZTCP0 MAINTENANCE MYSYSMAINT

NameIs the name of the provider.

*TPNameIs the name of the transport-service provider (CIPSAM) process.

TypeShows the type of provider. An IPDATA provider provides TCP/IP access by means of thedata Ethernet ports on one or more CLIMs associated with that IPDATA provider. TheMAINTENANCE provider provides TCP/IP access by means of the maintenance Ethernetinterface on a specific CLIM using a specific IP address.

*HOSTNAMEIs the name of the NonStop host system.

Example 54 shows the detailed configuration of ZTC0 (IPDATA Provider).

Example 54 INFO PROVIDER With Detailed Display

> INFO PROVIDER $ZZCIP.ZTC0, DETAILCIP Detailed Info PROVIDER \MYSYS.$ZZCIP.ZTC0

*TPName.................... $ZTC0Type...................... IPDATA*HostID.................... 0.0.0.0*Hostname.................. MYSYS

CIPMAN SCF Commands 235

*TCP-Listen-Que-Min........ 128*BRecvPort................ No Ports Specified*Family.................... INET*Share-Ports............... 1000

CLIMs Associated through CLIM’s PROVIDER Attribute:NameN1002541N1002551

CLIMs Providing Data Access:Name Index MultiProvN1002541 1 ON (Last Known)N1002551 2 OFFN1002543 3 ON

TPNameIs the CIPSAM transport-service provider process name. This is the name applications useto select the transport provider. It must be a valid process name with a leading dollar sign($). The default value is the name of the PROVIDER object itself with a dollar sign ($)prepended. The process need not exist when you add the provider.

TypeShows the type of provider. An IPDATA provider provides TCP/IP access by means of thedata Ethernet ports on one or more CLIMs associated with that IPDATA provider. AMAINTENANCE provider provides TCP/IP access by means of the maintenance Ethernetinterface of a specific CLIM using a specific IP address.

HostIDIs the host ID returned by gethostid() when the transport provider is selected. The host ID isan IPv4 address in dotted quad format. The default is 0.0.0.0.

HostnameIs the hostname returned by gethostname() when the transport provider is selected. Thehostname is a string of up to 49 characters. The default is the Expand system name withoutthe leading backslash (\).

TCP-Listen-Que-MinShows the minimum queue length that is allocated on a TCP socket when a socket LISTENor ACCEPT_NW1 function call is handled. This value is used if the queue length specifiedin the socket request is lower, otherwise the queue length in the socket request is used.

BRecvPortShows the list of UDP ports that receive broadcast messages on sockets bound to specificIP addresses or INADDR_ANY. Ports not in the list can receive broadcast messages onlyon sockets bound to INADDR_ANY. If no port has been specified, “No Ports Specified” isdisplayed.

NOTE: If any of the UDP ports shown are in the ephemeral or shared ephemeral portrange, the behavior is the same as those ports not being in the BRECVPORT list.

FamilySpecifies the network mode of the provider. INET family indicates the provider is operatedin IPv4 only mode. DUAL family indicates the provider is operated in both IPv4 mode andIPv6 mode.

Share-Portsshows the number of ports reserved for TCP and UDP shared-ephemeral ports. Ephemeralports are those assigned by CIP subsystem when an application has not bound to a specificport. This attribute is applicable only when PROVIDER TYPE is IPDATA.

236 SCF Reference for CIP

CLIMs Associated through CLIM’s PROVIDER AttributeLists the CLIMs associated with this provider. The PROVIDER attribute of these CLIMs isthis provider. This attribute is applicable only when the provider is of TYPE IPDATA.

NOTE: The list may be empty if there is no CLIM associated with the specified IPDATAprovider.

NameIs the name of the CLIM.

CLIMs Providing Data AccessLists the CLIMs actively providing network resources for use by this provider. Each of theseCLIMs contains one or more interfaces associated with this provider. This attribute is applicableonly when the provider is of TYPE IPDATA.

NOTE: The list may be empty if there is no CLIM actively providing resources to the specifiedIPDATA provider. This attribute is displayed using — for both Name and Index.

NameIs the name of the CLIM.

IndexIs the index value for the CLIM within the provider.

MultiProvIs the MULTIPROV attribute value of the CLIM. “OFF” means the CLIM has the MULTIPROVattribute set to OFF. “ON” means the CLIM has the MULTIPROV attribute set to ON andcurrently has active interfaces associated with this provider. “ON (Last Known)” means theCLIM has the MULTIPROV attribute set to ON and previously had active interfaces associatedwith this provider.

Example 55 shows detailed information for the provider ZTC0 (MAINTENANCE PROVIDER).

Example 55 INFO PROVIDER (Maintenance) Detailed

> INFO PROVIDER $ZZCIP.ZTCP0, DETAILCIP Detailed Info PROVIDER \MYSYS.$ZZCIP.ZTCP0

*TPName.................... $ZTCP0Type...................... MAINTENANCE*HostID.................... 0.0.0.0*Hostname.................. MYSYSMAINT*TCP-Listen-Que-Min........ 100*BRecvPort................ ( 109 , 1154 )*CLIM...................... N1003741*IPAddress................. 192.168.36.10

CLIMShows the name of the CLIM associated with the provider. This command is valid only for aPROVIDER of TYPE MAINTENANCE.

IP AddressShows the IP address associated with the provider. This attribute is valid only for a PROVIDERof TYPE MAINTENANCE.

Example 56 requests information for the PROVIDER ZTCP0 (maintenance provider) in the formof a command (Obey) file.

Example 56 INFO PROVIDER (Maintenance) With OBEYFORM

> INFO PROVIDER $ZZCIP.ZTCP0, OBEYFORMADD PROVIDER $ZZCIP.ZTCP0 , &

CIPMAN SCF Commands 237

TPNAME $ZTCP0 , &HOSTNAME “MYSYSMAINT” , &HOSTID 0.0.0.0 , &TCP-LISTEN-QUE-MIN 100 , &BRECVPORT ( 109 , 154 ),TYPE MAINTENANCE , &CLIM N1003741 , &IPADDRESS 192.168.36.10

Example 57 “INFO PROVIDER (IPDATA) With OBEYFORM” requests information for the providerPROV1 (IP Data Provider), in the form of a command (Obey) file.

Example 57 INFO PROVIDER (IPDATA) With OBEYFORM

> INFO PROVIDER $ZZCIP.PROV1, OBEYFORMADD PROVIDER $ZZCIP.PROV1 , &

TPNAME $ZCSM1 , &HOSTNAME “MYSYS” , &HOSTID 0.0.0.0 , &TCP-LISTEN-QUE-MIN 128 , &TYPE IPDATA , &FAMILY INET , &SHARE-PORTS 1000

NOTE: Special handling of OBEYFORM output is done for the default IPDATA provider (ZTC0).For example, it must be specified using ALTER instead of ADD because ZTC0 cannot be added.

NOTE: When the BRECVPORT attribute has no ports specified, the OBEYFORM output forthe non-default IPDATA provider (in ADD format) does not omit the BRECVPORT attribute. Fordefault IPDATA provider in ALTER format, the BRECVPORT attribute is specified as BRECVPORTRESET.

Example 58 shows the INFO PROVIDER command for the default IPDATA PROVIDER (ZTCO).This command provides the output in a different format because the default IPDATA providercannot be added. It can only be altered.

Example 58 INFO PROVIDER (ZTCO) With OBEYFORM

> ALTER PROVIDER $ZZCIP.ZTC0 , &TPNAME $ZTC0 , &HOSTNAME "MYSYS" , &HOSTID 0.0.0.0 , &TCP-LISTEN-QUE-MIN 128 , &BRECVPORT RESET , &FAMILY INET , &SHARE-PORTS 1000

For information about these attributes, see “INFO PROVIDER” (page 235).

INFO ROUTEThe SCF INFO ROUTE command displays the configuration of the specified ROUTE(s).INFO ROUTE Command SyntaxINFO ROUTE $ZZCIP.prov-name.route-name [,OBEYFORM]

prov-nameSpecifies the parent provider. A wildcard can specify multiple parent providers.

route-nameSpecifies the name of the ROUTE to display. A wildcard can specify multiple ROUTEs.

238 SCF Reference for CIP

OBEYFORMCauses the configuration to be displayed as ADD command(s), so that it can be re-created.

Example 59 shows the configuration of all ROUTE objects associated with provider PROV1.

Example 59 INFO ROUTE Summary

> INFO ROUTE $ZZCIP.PROV1.*CIP Info ROUTE

Name Family CLIM PriorityPROV1.DFLT1 DUAL N1003741 50PROV1.DFLT2 DUAL N1002532 90

Example 60 shows the configuration of ROUTE DFLT2 associated with provider PROV1 in theform of a command (Obey) file.

Example 60 INFO ROUTE With OBEYFORM

> INFO ROUTE $ZZCIP.PROV1.DFLT2, OBEYFORMADD ROUTE $ZZCIP.PROV1.DFLT2 , &

CLIM N1002532 , &FAMILY DUAL , &PRIORITY 90

For display field descriptions, see “ADD ROUTE” (page 225).

LISTOPENS CommandsLISTOPENS is a non-sensitive command that displays a list of the processes that currently haveopen sockets. By default, a summary of the processes and sockets is displayed. All commandsallow a DETAIL modifier to show additional, detailed information.

LISTOPENS MONThe LISTOPENS MON command displays a list of all sockets opened by processes in theprocessor containing the specified CIPMON.LISTOPENS MON Command SyntaxLISTOPENS MON $ZZCIP.ZCMnn [,DETAIL]

ZCMnnIdentifies the CIPMON process to which the command applies. nn is a two-digit value in therange 00 through 15. A wildcard can specify multiple MONs.

Example 61 displays a summary list of all processes in this system that have opened sockets inCIP:

Example 61 LISTOPENS MON Summary

> LISTOPENS MON $ZZCIP.*CIP Listopens MON \MYSYS.$ZZCIP.ZCM01

Openers Ppid State Proto Lport Provider CLIM\MYSYS.$ZPRP0 0,20 LISTEN TCP ECHO ZTCP0 N1002531\MYSYS.$RMAIL 1,162 LISTEN TCP 10293 ZTCP0 N1002531\MYSYS.$MYWEB 1,333 LISTEN TCP http ZTCP0 N1002531\MYSYS.$MYWEB 0,427 LISTEN TCP 5988 ZTCP0 N1002531

CIP Listopens MON \MYSYS.$ZZCIP.ZCM02

Openers Ppid State Proto Lport Provider CLIM\MYSYS.$ZTN0 2,24 LISTEN TCP telnet ZTC0 N1003742

CIPMAN SCF Commands 239

\MYSYS.$ZTN0 2,24 LISTEN TCP telnet ZTC0 N1003742\MYSYS.$ZTN1 2,35 LISTEN TCP telnet ZTC1 N1003742\MYSYS.$TEST6 2,325 LISTEN TCP 10513 ZTC1 N1003742\MYSYS 2,210 LISTEN UDP 5010 ZTC0 N1003742

OpenerIs the system name and process name of the process that opened the socket. If the processhas no name, then only the system name appears.

PpidIs the PID (cpu, process number) of the primary process that opened the socket.

BpidIs the PID (cpu, process number) of the backup process that opened the socket. If the processpair has no backup, the field is blank.

ProtoIs the protocol used to open the socket.

ProviderIs the provider used to open the socket.

CLIMIs the CLIM that contains the socket.

LportIs the local port number associated with the socket. Common port numbers are displayedwith a text name.

Example 62 displays detailed information about opened sockets in processor 2.

Example 62 LISTOPENS MON Detailed

>LISTOPENS MON $ZZCIP.*, DETAILCIP Detailed Listopens MON \SYSA.$ZZCIP.ZCM01

Opener:\SYSA.$ Ppid: 1,325 Bpid: 0, 0Plfn:6 Blfn:2Proto:TCP State:0x0000080 SendQ:0 RecvQ:0

Provider:CSAM1 CLIM:N1002532 CLIM-FD:14Lport:5000 Laddr:172.17.190.151FPort:0 Faddr:0.0.0.0

CIP Detailed Listopens MON \SYSA.$ZZCIP.ZCM02

Opener:\SYSA.$ Ppid: 2,304 Bpid: 0, 0Plfn:6 Blfn:1Proto:TCP State:0x0000080 SendQ:0 RecvQ:0

Provider:CSAM1 CLIM:N1002532 CLIM-FD:15Lport:0 Laddr:0.0.0.0FPort:0 Faddr:0.0.0.0

OpenerIs the system name and process name of the process that opened the socket. If the processhas no name, then only the system name appears.

PpidIs the PID (cpu, process number) of the primary process that opened the socket.

BpidIs the PID (cpu, process number) of the backup process that opened the socket. If the processpair has no backup, the field is blank.

240 SCF Reference for CIP

PlfnIs the logical file number of the socket in the primary process.

BlfnIs the logical file number of the socket in the backup process, or zero if the backup processdoes not exist or have the socket open.

ProtoIs the protocol used to open the socket.

StateIs the current state of the socket. The State value is either a translated text string for a TCPstate or a cumulative bitwise value in hex format that represents a socket state.Text value:

indicates the socket is connected to a remote socket.ESTAB

indicates the socket is in a listening state and is waiting for a connection from a remote hostLISTEN

indicates the socket is in the process of closingCLOSING

Hex value:

indicates the socket can’t send any more data to its peer.0x00010

indicates the socket can’t receive any more data from its peer.0x00020

indicates the socket is operated in a privileged mode. This usually means the application is startedby a super user.

0x00080

indicates the socket is operated in a non-blocking io mode.0x00100

indicates the socket is a listening socket.0x04000

indicates the socket has received a 0-byte indication. This usually means its peer socket is closed.0x08000

SendQIs the number of bytes of data in the send queue of the socket.

RecvQIs the number of bytes of data in the receive queue of the socket. If the socket state is"LISTEN" this is the number of connections queued on the socket yet to be accepted by theapplication.

ProviderIs the provider used to open the socket.

CLIMIs the CLIM that contains the socket.

CLIM-FDIs the CLIM software file descriptor number of the socket on the CLIM.

LportIs the local port number associated with the socket. Common port numbers are displayedwith a text name.

LaddrIs the local IP address associated with the socket.

CIPMAN SCF Commands 241

FportIs the remote port number associated with the socket. Common port numbers are displayedwith a text name. An asterisk (*) signifies that no remote port number is associated with thesocket.

FaddrIs the remote IP address associated with the socket.

LISTOPENS PROVIDERThe LISTOPENS PROVIDER command displays all sockets using the specified provider andidentifies the process that opened each socket.LISTOPENS PROVIDER Command SyntaxLISTOPENS PROVIDER $ZZCIP.prov-name [,DETAIL]

prov-nameIs the name of the provider to which the command applies. A wildcard can specify a set ofproviders.

Example 63 displays information about processes that have opened sockets on PROVIDERZTC0.

Example 63 LISTOPENS PROVIDER Summary

> LISTOPENS PROV $ZZCIP.ZTC0CIP Listopens PROVIDER \MYSYS.$ZZCIP.ZTC0

Openers Ppid State Proto Lport Provider CLIM\MYSYS.$MYWEB 1,333 LISTEN TCP http ZTC0 N1002532\MYSYS.$MYWEB 1,333 LISTEN TCP http ZTC0 N1002532

Openers Ppid State Proto Lport Provider CLIM\MYSYS.$ZTN0 2,24 LISTEN TCP telnet ZTC0 N1002532\MYSYS.$ZTN0 2,24 LISTEN TCP telnet ZTC0 N1002532\MYSYS 2,210 LISTEN UDP 5010 ZTC0 N1002532

OpenerIs the system name and process name of the process that opened the socket. If the processhas no name, then only the system name appears.

PpidIs the PID (cpu, process number) of the primary process that opened the socket.

BpidIs the PID (cpu, process number) of the backup process that opened the socket. If the processpair has no backup, the field is blank.

ProtoIs the protocol used to open the socket.

ProviderIs the provider used to open the socket.

CLIMIs the CLIM that contains the socket.

LportIs the local port number associated with the socket. Common port numbers are displayedwith a text name.

Example 64 displays detailed information about opened sockets using provider CSAM1.

242 SCF Reference for CIP

Example 64 LISTOPENS PROVIDER Detailed

>LISTOPENS PROV $ZZCIP.CSAM1, DETAIL CIP Detailed Listopens provider\EUROPA.$ZZCIP.CSAM

Blfn:5Plfn:2Bpid: 0,0Ppid: 2,480Opener:\EUROPA.$

RecvQ:0SendQ:0State:LISTENProto:TCP

CLIM-FD:41CLIM:*mult*Provider:CSAM

Laddr:0.0.0.0Lport:3333

Faddr:0.0.0.0FPort:0

Blfn:5Plfn:7Bpid:0,0Ppid: 2,480Opener:\EUROPA.$

RecvQ:0SendQ:0State:ESTABProto:TCP

CLIM-FD:34CLIM:DL385FProvider:CSAM

Laddr:172.17.188.142Lport:3333

Faddr:172.17.188.142FPort:22861

Blfn:5Plfn:2Bpid: 0,0Ppid: 2,500Opener:\EUROPA.$

RecvQ:0SendQ:0State:0x00180Proto:TCP

CLIM-FD:42CLIM:DL385GProvider:CSAM

Faddr:0.0.0.0FPort:0Laddr:172.17.188.152Lport:27501

Blfn:5Plfn:7Bpid: 0,0Ppid: 2,480Opener:\EUROPA.$

RecvQ:0SendQ:0State:0x080B0Proto:TCP

CLIM-FD:34CLIM:DL385FProvider:CSAM

Laddr:172.17.188.142Lport:3333

Faddr:172.17.188.142FPort:27818

OpenerIs the system name and process name of the process that opened the socket. If the processhas no name, then only the system name appears.

PpidIs the PID (cpu, process number) of the primary process that opened the socket.

BpidIs the PID (cpu, process number) of the backup process that opened the socket. If the processpair has no backup, the field is blank.

PlfnIs the logical file number of the socket in the primary process.

BlfnIs the logical file number of the socket in the backup process, or zero if the backup processdoes not exist or have the socket open.

ProtoIs the protocol used to open the socket.

CIPMAN SCF Commands 243

StateIs the current state of the socket. The State value is either a translated text string for a TCPstate or a cumulative bitwise value in hex format that represents a socket state.Text value:

indicates the socket is connected to a remote socket.ESTAB

indicates the socket is in a listening state and is waiting for a connection from a remote hostLISTEN

indicates the socket is in the process of closingCLOSING

Hex value:

indicates the socket can’t send any more data to its peer.0x00010

indicates the socket can’t receive any more data from its peer.0x00020

indicates the socket is operated in a privileged mode. This usually means the application is startedby a super user.

0x00080

indicates the socket is operated in a non-blocking io mode.0x00100

indicates the socket is a listening socket.0x04000

indicates the socket has received a 0-byte indication. This usually means its peer socket is closed.0x08000

SendQIs the number of bytes of data in the send queue of the socket.

RecvQIs the number of bytes of data in the receive queue of the socket. If the socket state is"LISTEN" this is the number of connections queued on the socket yet to be accepted by theapplication.

ProviderIs the PROVIDER used to open the socket.

CLIMIs the CLIM that contains the socket.

CLIM-FDIs the CLIM software file descriptor number of the socket on the CLIM.

LportIs the local port number associated with the socket. Common port numbers are displayedwith a text name.

LaddrIs the local IP address associated with the socket.

FportIs the remote port number associated with the socket. Common port numbers are displayedwith a text name. An asterisk (*) signifies that no remote port number is associated with thesocket.

FaddrIs the remote IP address associated with the socket.

NAMES CommandsNAMES is a non-sensitive command that displays a list of object types and names for the specifiedobjects.

244 SCF Reference for CIP

NAMES $ZZCIPThe NAMES command with no object type is identical to the “NAMES PROCESS”. The onlyrequired attribute for the NAMES command with no object type is the MAN process name, $ZZCIP.The NAMES PROCESS command shows the types and names of all objects subordinate to thespecified process.NAMES $ZZCIP Command SyntaxNAMES $ZZCIP

Example 65 NAMES $ZZCIP

> NAMES PROCESS $ZZCIPCIP Names PROCESS \MYSYS.$ZZCIP

PROCESS$ZZCIP

MON$ZZCIP.ZCM00 $ZZCIP.ZCM01 $ZZCIP.ZCM02 $ZZCIP.ZCM03

PROVIDER$ZZCIP.ZTC0 $ZZCIP.PROV1

CLIM$ZZCIP.N1002532 $ZZCIP.N1003741

NAMES CLIMThe NAMES CLIM command displays the names of the specified CLIMs known by this system.NAMES CLIM Command SyntaxNAMES CLIM $ZZCIP.clim-name

clim-nameSpecifies the CLIM names to display. If no such CLIM is known to this system, the output isan error message. A wildcard can specify multiple CLIMs.

Example 66 displays the names of all CLIMs known by this system.

Example 66 NAMES CLIM

> NAMES CLIM $ZZCIP.*CIP Names CLIM \MYSYS.$ZZCIP.*

CLIM

$ZZCIP.N1002532 $ZZCIP.N1003741 $ZZCIP.N1012542

NAMES MONThe NAMES MON command displays the names of the specified MON objects in this system.NAMES MON $ZZCIP.ZCMnn

ZCMnnIdentifies the CIPMON process names to display. nn is a two-digit value in the range 00through 15. A wildcard can specify multiple MONs in this system.

Example 67 displays the names of all MONs in this system:

CIPMAN SCF Commands 245

Example 67 NAMES MON

> NAMES MON $ZZCIP.*CIP Names MON \MYSYS.$ZZCIP.*

MON$ZZCIP.ZCM00 $ZZCIP.ZCM01 $ZZCIP.ZCM02 $ZZCIP.ZCM03

NAMES PROCESSThe NAMES PROCESS command displays the types and names of all objects subordinate tothe specified process.NAMES PROCESS Command Syntax> NAMES PROCESS $ZZCIP

This command displays the names and types of all objects subordinate to CIPMAN on this system.

Example 68 NAMES PROCESS

> NAMES PROCESS $ZZCIPCIP Names PROCESS \MYSYS.$ZZCIP

PROCESS$ZZCIP

MON$ZZCIP.ZCM00 $ZZCIP.ZCM01 $ZZCIP.ZCM02 $ZZCIP.ZCM03

PROVIDER$ZZCIP.ZTC0 $ZZCIP.PROV1

ROUTE$ZZCIP.ZTC0.ROUTE1 $ZZCIP.ZTC0.ROUTE2 $ZZCIP.PROV1.MYROUTE

CLIM$ZZCIP.N1002532 $ZZCIP.N1003741

NAMES PROVIDERThe NAMES PROVIDER command displays the names of the specified PROVIDER objects onthis system.NAMES PROVIDER Command SyntaxNAMES PROVIDER $ZZCIP.prov-name

prov-nameIdentifies the PROVIDER object names to display. A wildcard can specify multiple providers.

Example 69: NAMES PROVIDER displays the names of all providers known by this system:

Example 69 NAMES PROVIDER

> NAMES PROV $ZZCIP.*CIP Names PROVIDER \MYSYS.$ZZCIP.*

PROVIDER

$ZZCIP.SAM0 $ZZCIP.SAM1 $ZZCIP.SAM2

NAMES ROUTEThe NAMES ROUTE command displays the names of the specified ROUTE objects on thissystem.

246 SCF Reference for CIP

NAMES ROUTE Command SyntaxNAMES ROUTE $ZZCIP.prov-name.route-name

prov-nameSpecifies the parent provider. A wildcard can specify multiple parent providers.

route-nameSpecifies the name of the ROUTE to display. A wildcard can specify multiple ROUTEs.

Example 70 displays the names of all ROUTE objects known by this system.

Example 70 NAMES ROUTE

> NAMES ROUTE $ZZCIP.*CIP Names ROUTE \MYSYS.$ZZCIP.*

ROUTE$ZZCIP.ZTC0.ROUTE1 $ZZCIP.ZTC0.ROUTE2 $ZZCIP.PROV1.MYROUTE

PRIMARY CommandThe PRIMARY command changes the specified object in an object pair from the backup to theprimary.

PRIMARY PROCESSThe PRIMARY PROCESS command is a sensitive command that changes which process of theCIPMAN process pair is the primary.PRIMARY PROCESS Command SyntaxPRIMARY PROCESS $ZZCIP [,CPU cpu-number]

cpu-numberIs the new primary processor number. If you specify the current primary processor, thecommand does nothing. If you specify the current backup processor (or if you omit thisparameter), the command switches to the backup processor. If you specify a number otherthan the current primary or backup processor, the command returns an error.

This command switches CIPMAN to its backup process:

Example 71 PRIMARY PROCESS

> PRIMARY PROCESS $ZZCIP

START CommandsSTART is a sensitive command used to initiate operations on the specified object. The objectenters the STARTING state, then progresses to the STARTED state if no error occurs duringstartup.

START CLIMThe START CLIM command starts operations on the specified CLIM.If the device at the configured LOCATION does not quickly respond as an operational CLIM, theCLIM object stays in the STARTING state. If an operational CLIM responds later, the CLIM objectgoes to the STARTED state.Prior to J06.08 and H06.19, the START command for the CLIM did not check that climcmnd wasset up on that CLIM. As of J06.08 and H06.19, it does check.START CLIM Command SyntaxSTART CLIM $ZZCIP.clim-name

CIPMAN SCF Commands 247

clim-nameIs the name of the CLIM to start. A wildcard can specify a set of CLIMs.

This command starts operations on S1003741.

Example 72 START CLIM

> START CLIM $ZZCIP.S1003741

START PROCESSThe START PROCESS command starts the operation of all the objects in the CIP subsystemon this system. Because the target object is already started (by the persistence manager), theSUB ONLY option must be specified.START PROCESS Command SyntaxSTART PROCESS $ZZCIP, SUB ONLY

SUBDetermines the set of objects and subordinate objects that the command targets. ONLYspecifies that only subordinate objects are targets of the command.

This commands starts all the configured objects in the CIP subsystem on this system.

Example 73 START PROCESS

> START PROCESS $ZZCIP, SUB ONLY

START PROCESS GuidelinesMON objects are not affected by the START PROCESS, SUB ONLY command.

START PROVIDERThe START PROVIDER command starts operations on the specified provider. The provider goesto the STARTED state only if the associated CLIM is in the STARTED state; otherwise it goesto the STARTING state. The associated CIPSAM process need not be running for the providerto be STARTED, but applications cannot use the provider until the CIPSAM process is started.START PROVIDER Command SyntaxSTART PROVIDER $ZZCIP.prov-name

prov-nameIs the name of the provider to start. A wildcard can specify a set of providers.

Example 74 starts all configured providers:

Example 74 START PROVIDER

> START PROVIDER $ZZCIP.*

STATS CommandsSTATS is a non-sensitive command that displays statistical information for the specified object.The STATS command shows statistics related to the NonStop system, the CLIM software, andcommunication between the two. The Linux ip, and netstat commands and the climconfig routecommand get TCP/IP, interface, and route statistics for the CLIMs . To access the Linuxcommands, enter:CLIMCMD clim-name Linux-command

The RESET modifier resets the statistics to zero after displaying them. The command is sensitiveif you specify RESET.

248 SCF Reference for CIP

STATS CLIMThe STATS CLIM command displays statistical information kept by the NonStop EnterpriseDivision software on the specified CLIMs, which must be in the STARTED state.The statistics pertain to the operation of the CLIM software and the CLIM-side communicationwith the NonStop host system. To get TCP/IP protocol statistics, use the Linux netstat commandon the CLIM. (To obtain information about the netstat command, enter CLIMCMD clim-nameman netstat at the TACL prompt.)

NOTE: For better performance, always use the –n option with netstat.

STATS CLIM Command SyntaxSTATS CLIM $ZZCIP.clim-name [,RESET]

clim-nameIs the name of the CLIM for which to display statistical information. A wildcard can specify aset of CLIMs.

RESETResets statistics to zero after displaying them.

Example 75: STATS CLIM displays statistics for N1003741.

Example 75 STATS CLIM

> STATS CLIM $ZZCIP.N1003741CIP Stats CLIM \COCOA.$ZZCIP.N1003741

Sample Time ... 11 Jun 2008, 23:51:49.000Reset Time .... 09 Jun 2008, 2:28:39.000

CLIMMON STATSEvent Log Entries......... 0 Restarts.................. 1CLIMAGT Failures.......... 0 CIPSSRV0 Failures......... 0

CLIMAGT STATSEvent Log Entries........... 7Buffer denials.............. 0IT-API errors............... 4Last IT-API error code...... 12Linux errors................ 2Last Linux errno............ 22Current bfr bytes in use.... 0High bfr bytes in use....... 2048Total msgs sent............. 289299Total msgs received......... 289293Current connected Cpus...... 4 High connected Cpus......... 4Queued Commands............. 2 Failed Commands............. 0

CIPSSRV0 STATSEvent Log Entries........... 0Buffer denials.............. 0IT-API errors............... 0Last IT-API error code...... 0Linux errors................ 0Last Linux errno............ 0Current bfr bytes in use.... 1048727High bfr bytes in use....... 1048727Total msgs sent............. 69Total msgs received......... 76Total bytes sent............ 1080Total bytes received........ 1024Current connected Cpus...... 4 High connected Cpus......... 4Deferred Sends.............. 0 Failed Commands............. 0

CIPMAN SCF Commands 249

Current TCP Listen Sockets.. 0 High TCP Listen Sockets..... 0Current UDP Sockets......... 0 High UDP Sockets............ 1Current TCP Connections..... 0 High TCP Connections........ 1

CLIMMON STATSHeads the statistics taken from the CLIMMON process, which starts and monitors the otherCIP subsystem components on the CLIM.

Event Log EntriesShows the number of syslog entries generated by the CLIMMON process since the last reset.

RestartsShows the number of times CLIMMON restarted the CLIMAGT and CIPSSRVx processessince the last reset. All these processes are restarted when any one indicates a failure.

CLIMAGT FailuresShows the number of times the CLIMAGT process indicated a failure since the last reset.

CIPSSRVx FailuresShows the number of times the given CIPSSRV process indicated a failure since the lastreset. Only one CIPSSRV process (CIPSSRV0) is present in CIP.

CLIMAGT STATSHeads the statistics taken from the CLIMAGT process, which performs management requestsoriginating from the NonStop host system.

Event Log EntriesShows the number of syslog entries generated by the process since the last reset.

Buffer DenialsShows the number of times a buffer for communication with the NonStop host system couldnot be obtained since the last reset; this symptom indicates memory overflow.

IT-API ErrorsShows the number of errors returned from the low-level ServerNet communication handlerssince the last reset.

Last IT-API error codeShows the status code of the last IT-API error or zero if there has been no error.

Linux ErrorsShows the number of errors returned from the CLIM side of CIP since the last reset.

Last Linux errnoShows the errno value of the last CLIM software error or zero if there has been no error.

Current bfr bytes in useShows the amount of memory currently used for communication with the NonStop hostsystem.

High bfr bytes in useShows the highest amount of memory used for communication with the NonStop host systemsince the last reset.

Current connected CpusShows the current number of NonStop host system processors connected.

High connected CpusShows the highest number of NonStop host system processors connected at one time sincethe last reset.

Total msgs sentShows the total number of messages sent to all NonStop host system processors since thelast reset.

250 SCF Reference for CIP

Total msgs receivedShows the total number of messages received from all NonStop host system processorssince the last reset.

Queued CommandsShows the number of SCF commands queued for processing.

Failed CommandsShows the total number of SCF commands that could not be completed since the last reset.

CIPSSRVx STATSHeads the statistics taken from each CIPSSRV process, which performs application socketrequests. Only one CIPSSRV process (CIPSSRV0) is present in CIP. Statistics with the sametitle as those for the CLIMAGT contain the same information for the CIPSSRV process. Thoseunique to CIPSSRV follow:Total bytes sent

Shows the total number of data bytes sent to all NonStop host system processors.Total bytes received

Shows the total number of data bytes received from all NonStop host system processors.Deferred Sends

Shows the total number of times a send request could not be performed immediately.Failed Commands

Shows the total number of socket requests that could not be completed since the lastreset.

Current TCP Listen SocketsShows the current number of open TCP listen sockets.

High TCP Listen SocketsShows the highest number of TCP listen sockets open at one time since the last reset.

Current UDP SocketsShows the current number of open UDP sockets.

High UDP SocketsShows the highest number of UDP sockets open at one time since the last reset.

Current TCP ConnectionsShows the current number of TCP connections.

High TCP ConnectionsShows the highest number of TCP connections at one time since the last reset.

STATS MONThe STATS MON command displays the statistics kept by the specified CIPMON process orprocesses running on this system.STATS MON Command SyntaxSTATS MON $ZZCIP.ZCMnn, [RESET]

ZCMnnIdentifies the CIPMON process for which to display statistics. nn is a two-digit value in therange 00 through 15. A wildcard (*) can specify multiple CIPMONs.

Example 76: STATS MON displays statistics for the CIPMON object ZCM01.

Example 76 STATS MON

> STATS MON $ZZCIP.ZCM01CIP Stats MON \COCOA.$ZZCIP.ZCM00

CIPMAN SCF Commands 251

Sample Time ... 11 Jun 2008, 23:55:55.300Reset Time .... 07 Jun 2008, 16:15:13.781

SOCKET STATSTotal Recv Socket Reqs...... 0Total Recv Errors........... 0Total Send Socket Reqs...... 0Total Send Errors........... 0Data Bytes Sent............. 0Data Bytes Received......... 0Total Connections Out....... 0 Total Connections In........ 0Current TCP Listen Sockets.. 0 High TCP Listen Sockets..... 0Current UDP Sockets......... 0 High UDP Sockets............ 0Current TCP Connections..... 0 High TCP Connections........ 0

SOCKET SEND SIZE HISTOGRAMSize 1-128.................. 0 Size 129-256................ 0Size 257-512................ 0 Size 513-1024............... 0Size 1025-2048.............. 0 Size 2049-4096.............. 0Size 4097-8192.............. 0 Size 8193-12288............. 0Size 12289-16384............ 0 Size 16385-32768............ 0Size 32769 and larger....... 0

MON STATSTotal Messages Sent......... 0Total Messages Received..... 0Current Connected CLIMs..... 2 High Connected CLIMs........ 2Total Rejected Connections.. 129 Deferred Sends.............. 0

Total Recv Socket ReqsShows the total number of receive socket requests across all CLIMs since the last reset.

Total Recv ErrorsShows the total number of receive socket requests that returned an error since the last reset.

Total Send Socket ReqsShows the total number of send socket requests across all CLIMs since the last reset.

Total Send ErrorsShows the total number of send socket requests that returned an error since the last reset.

Data Bytes SentShows the total number of data bytes sent to all CLIMs since the last reset.

Data Bytes ReceivedShows the total number of data bytes received from all CLIMs since the last reset.

Total Connections OutShows the total number of connection requests sent to all CLIMs since the last reset.

Total Connections InShows the total number of connection requests received from all CLIMs since the last reset.

Current TCP Listen SocketsShows the current number of open TCP listen sockets.

High TCP Listen SocketsShows the highest number of open TCP listen sockets at one time since the last reset.

Current UDP SocketsShows the current number of open UDP listen sockets.

High UDP SocketsShows the highest number of UDP listen sockets open at one time since the last reset.

252 SCF Reference for CIP

Current TCP ConnectionsShows the current number of TCP connections.

High TCP ConnectionsShows the highest number of TCP connections at one time since the last reset.

SOCKET SEND SIZE HISTOGRAMShows the number of socket send requests across all CLIMs, organized by the length of therequest.

Size x-xxxxIs the count of socket sends between x and xxxx bytes.

Size 32769 and largerIs the count of socket sends greater than 32769 bytes.

Total Messages SentShows the total number of messages sent to all CLIMs since the last reset.

Total Messages ReceivedShows the total number of messages received from all CLIMs since the last reset.

Current connected CLIMsShows the current number of CLIMs connected.

High connected CLIMsShows the highest number of CLIMs connected at one time since the last reset.

Total Rejected ConnectionsShows the total number of attempts to connect to a CLIM that were rejected.

Deferred SendsShows the total number of times a send request could not be performed immediately.

STATUS CommandsSTATUS is a non-sensitive command that displays the current status of an object as viewed bythis system or CIPMON. Some STATUS commands accept the DETAIL option, which specifiesthat the display is to include additional, detailed status information about the object.

STATUS CLIMThe STATUS CLIM command displays the current status of the specified CLIM object(s) on thissystem. The summary display shows the summary state, which reflects the lastSTART/STOP/ABORT command issued to the object. The detailed display also shows the statusof the CLIM interfaces and the connections to the CLIM from the individual CIPMONs. Use theCLIM software climstatus command on the CLIM to display similar information from the viewpointof the CLIM.

NOTE: The storage subsystem ($ZZSTO) also supports a STATUS CLIM command. Forsyntax and display examples, see the SCF Reference Manual for the Storage Subsystem.

STATUS CLIM Command SyntaxSTATUS CLIM $ZZCIP.clim-name [,DETAIL]

clim-nameIs the name of the CLIM for which to display status information. A wildcard can specify a setof CLIMs.

Example 77: STATUS CLIM Summary, BladeSystem shows the state of all configured CLIMson a BladeSystem:

CIPMAN SCF Commands 253

Example 77 STATUS CLIM Summary, BladeSystem

> STATUS CLIM $ZZCIP.*CIP Status CLIM \MYSYS.$ZZCIP.*

Name Present State TraceN1002532 Yes STARTED OFFN1003741 Yes STARTED 1, 2N1012542 Yes STARTED 2

PresentIndicates whether an operational CLIM is present at the configured location and can haveany of the values

CLIM is connected at all configured locations and is usableYes

CLIM is connected at some but not all configured locations and is usablePartial

CLIM is not connected at any of the configured locations (not usable)No

Two or more CLIMs are connected to the configured locations (not usable)Conflict

A connection problem exists at one or more configured locations (not usable)Problem

StateIndicates the current summary state of the CLIM.

TraceShows a list of the processors that have started a trace on the CLIM, or OFF if none.

Example 78: STATUS CLIM Summary, NonStop X shows the state of all configured CLIMs onthe NonStop X system:

Example 78 STATUS CLIM Summary, NonStop X

> STATUS CLIM $ZZCIP.*CIP Status CLIM \MYSYS.$ZZCIP.*

Name Config State TraceNCLIM000 Yes STARTED OFFNCLIM001 Yes STARTED (X) 1, 2NCLIM002 No STARTING OFFNCLIM003 Mode Mismatch STARTING OFFSCLIM000 Yes STARTED 2SCLIM001 Yes STARTED OFF

ConfigIndicates whether a CLIM with the specified name is configured on this system, and can haveany of the values:

CLIM is configured correctly and is usableYes

CLIM is not configured (not usable)No

A device is configured with the specified name but is not a CLIM (not usable)Non-CLIM

MODE attribute of this CLIM object does not match the configured information within thehardware configuration database record (not usable)

Mode Mismatch

254 SCF Reference for CIP

StateIndicates the current summary state of the CLIM. If the CLIM is in STARTED state but canonly be accessed through a single fabric (X or Y), then there will be an additional (X) or (Y)after STARTED to indicate that access to the CLIM is only available on the specified fabric.

NOTE: The additional (X) or (Y) can only appear on NonStop X systems.

TraceShows a list of the processors that have started a trace on the CLIM, or OFF if none.

Example 79: STATUS CLIM Detailed displays detailed status information for C100271 on aNonStop system.

Example 79 STATUS CLIM Detailed

This example shows the Multiple Providers per CLIM option, MULTIPROV ON, and displaysoutput for multiple providers.> STATUS CLIM $ZZCIP.N100241, DETAIL, BladeSystemCIP Detailed Status CLIM \MYSYS.$ZZCIP.N100241

Mode...................... IPMultiProv................. ONCLIM HW Connection Status. ConnectedState..................... STARTEDConnPts................... 2X1 Location............... Group 100 , Module 2 , Slot 4 , Port 1Y1 Location............... Group 100 , Module 3 , Slot 4 , Port 1X2 Location............... Group 100 , Module 2 , Slot 4 , Port 2Y2 Location............... Group 100 , Module 3 , Slot 4 , Port 2X1 Connection Status...... ConnectedY1 Connection Status...... ConnectedX2 Connection Status...... ConnectedY2 Connection Status...... ConnectedTrace Status.............. OFF

Last Restart Time......... 02 Sep 2006, 22:38:50.000CLIM Hostname............. N1002411CIP SW Version............ T0853H01_01MAY2008_03MAR2008_Network SW Version........ T0691H01_01MAY2008_AAA_CLIMStorage SW Version........ T0830H01_01AUG2008_23JUL2008_AAANumber of Socket Servers.. 1CIP/Linux Version:Linux version 2.6.18-6-clim-amd64 (Debian 2.6.18.dfsg.1-18hpdeetch1hpde1.1) (brian.haley@hp.com) (gcc version 4.1.2 20061115 (prerelease) (Debian4.1.1-21)) #1 SMP PREEMPT Thu Feb 28 01:10:30 UTC 2008

Fabric Status:CIPMON Mgmt DataZCM00 XY-1 XY-1ZCM01 XY-2 XY-2ZCM02 XY-1 XY-1ZCM03 XY-2 XY-2

CLIM Maintenance Interface Status & IP Addresses:lo Sts:UP LkP:-- IPv4: 127.0.0.1

IPv6: ::1eth0 Sts:UP LkP:DOWN IPv4: 192.168.37.41

IPv6: fe80:0000:0000:0000:0214:38ff:feeb:db5a

Maintenance Provider Interface Status & IP Addresses:lo Sts:UP LkP:-- IPv4: 127.0.0.1

IPv6: ::1eth0:0 Sts:UP LkP:DOWN IPv4: 192.168.36.10Data Provider ZTC0 Interface Status & IP Addresses:Flg Name Status LkP Master / IP Family & Address

lo UP --IPv4: 127.0.1.2IPv4: 127.0.0.1IPv6: ::1

eth1 UP UPIPv4: 172.17.190.101IPv6: 3ffe:1200:0190:0002:0215:60ff:fe04:24deIPv6: 3ffe:1200:0190:0001:0215:60ff:fe04:24deIPv6: fe80:0000:0000:0000:0215:60ff:fe04:24de

CIPMAN SCF Commands 255

eth2 UP UPIPv4: 172.17.190.102IPv6: 3ffe:1200:0190:0002:0215:60ff:fe04:24dfIPv6: 3ffe:1200:0190:0001:0215:60ff:fe04:24dfIPv6: fe80:0000:0000:0000:0215:60ff:fe04:24df

(V) IPv4: 172.17.190.82(V) IPv6: 3ffe:1200:0190:0002:0215:60ff:fe04:42ed(V) IPv6: 3ffe:1200:0190:0001:0215:60ff:fe04:42ed(V) IPv6: fe80:0000:0000:0000:0215:60ff:fe04:42ed

Data Provider ZSAM1 Interface Status & IP Addresses:Flg Name Status LkP Master / IP Family & Address

lo UP --IPv4: 127.0.1.2IPv4: 127.0.0.1IPv6: ::1

eth3 UP UPIPv4: 172.17.190.103IPv6: 3ffe:1200:0190:0002:0215:60ff:fe04:257eIPv6: 3ffe:1200:0190:0001:0215:60ff:fe04:257eIPv6: fe80:0000:0000:0000:0215:60ff:fe04:257e

(F) eth4 DOWN DOWNIPv4: 0.0.0.0

(T) TUN1 UP -- eth3IPv6: fe80:0000:0000:0000:0111:5038:9999:1234

Data Provider JUNK Interface Status & IP Addresses: (Provider Does Not Exist)Flg Name Status LkP Master / IP Family & Address

lo UP --IPv4: 127.0.1.2IPv4: 127.0.0.1IPv6: ::1

eth5 RDY UPIPv4: 0.0.0.0

Interface Failover Configuration and Status:Flg Name Failover/(Assoc) Fovr Current Provider

N100241.eth1 N100251.eth1 Home N100241.eth1 ZTC0N100241.eth2 -- -- N100241.eth2 ZTC0

(V) N100251.eth2 N100241.eth2 BkOP N100241.eth2 ZTC0N100241.eth3 N100281.eth3 Home N100241.eth3 ZSAM1

(F) N100241.eth4 N100251.eth3 BkFO N100251.eth3 ZSAM1(T) N100241.TUN1 (N100241.eth3) Home N100241.TUN1 ZSAM1(P) N100241.eth5 -- -- N100241.eth5 JUNK(D) indicates an interface whose failover is directed externally by NonStop partner process

NOTE: The Fiber attribute might not be supported on your system. For more information, seethe planning guide for your system.

NOTE: CLIM Maintenance Interface Status & IP Addresses, Maintenance Provider InterfaceStatus & IP Addresses, and Data Interface Status & IP Addresses are usually available only ifthe CLIM is in the STARTED state.

ModeShows the operating mode of the CLIM. An IP, IB or Telco CLIM provides access to TCP/IPnetworking. A STORAGE CLIM provides access to disks and other storage devices. A TelcoCLIM (Mode OPEN) provides access to Telco protocols to communicate with a Telco network.

MultiProvIndicates whether the specified IP or IB CLIM supports association with multiple IPDATAproviders simultaneously.

CLIM HW Connection StatusIndicates overall hardware connectivity between a CLIM and this NonStop system at theconfigured locations and can have any of the values:

CLIM is connected at all configured locations and is usable.Connected

CLIM is connected at some but not all configured locations and is usable.Partially Connected

256 SCF Reference for CIP

CLIM is not connected at any of the configured locations (not usable).Not Connected

Two or more CLIMs are connected to the configured locations (not usable).Conflict

A connection problem exists at one or more configured locations (not usable).Connection Problem

StateShows the CLIM object state, either STOPPED, STARTING, or STARTED. If the object isSTOPPED, the subsequent fields are omitted. If the object is not STARTED, the CLIM restarttime, hostname, versions, and interface status fields are omitted.

ConnPtsShows whether there are one or two ServerNet connections configured per fabric betweenCLIM and the NonStop host system.

X1 LocationShows the CLIM’s first X-fabric location based on the configured location.

Y1 LocationShows the CLIM’s first Y-fabric location based on the configured location.

X2 LocationShows the CLIM’s second X-fabric location based on the configured location. This is applicableonly when CLIM’s CONNPTS attribute is 2.

Y2 LocationShows the CLIM’s second Y-Fabric location based on the configured location. This isapplicable only when CLIM’s CONNPTS attribute is 2.

X1 Connection Status, Y1 Connection Status, X2 Connection Status, Y2 Connection StatusIndicate whether the CLIM is connected to each ServerNet fabric at the expected location.X2 Connection Status and Y2 Connection Status are applicable only when the CLIM’sCONNPTS attribute is 2. The possible values are:

The CLIM is correctly connected at the specified location.Connected

No operational device is connected at the specified location.Not Connected

The specified location is not configured for connection with a CLIM.Port Misconfigured

The CLIM is not configured to be connected at the specified location.Location Mismatch

The CLIM is not configured to be connected to this system.System Mismatch

The MODE attribute of this CLIM object does not match the correspondingmode configured on the CLIM hardware.

Mode Mismatch

The number of ServerNet connections per fabric configured for this CLIMobject is different than the value configured on the CLIM hardware.

ConnPts Mismatch

Specified location is not a supported connection location for a CLIM on thissystem.

Unsupported Location

Trace StatusShows the processors that are tracing the CLIM and each trace file name. If no processor istracing the CLIM, the value in this field is OFF.

Last Restart TimeShows the time of the last CLIM software restart as saved by the CLIM.

CIP/Linux HostnameShows the CLIM software hostname configured on the CLIM. This must be identical to CLIMobject name.

CIPMAN SCF Commands 257

Network SW VersionShows the version of CIP subsystem network software running on the CLIM.

Storage SW VersionShows the version of Storage subsystem software installed on the CLIM.

Number of Socket ServersShows the number of Socket Server (CIPSSRV) processes running on the CLIM.

CIP/Linux VersionShows the version of CLIM software running on the CLIM. This value is retrieved from the/proc/version file.

Fabric StatusDisplays the CIPMON status, connections to the CLIM, and availability of the X and YServerNet fabrics for each running processor in the system. The Mgmt column shows themanagement connection to CLIMAGT, and the Data column shows the data path connectionsto the CIPSSRV processes. The possible values are:

CIPMON is down.MON-DOWN

CIPMON is up, but no connection is established.--

Connection is established; only the X fabric is available.X-

Connection is established; only the Y fabric is available.-Y

Connection is established; X and Y fabrics are available.XY

The number suffix (for example, -1) indicates the particular set of ServerNet fabrics beingused for the connection with the CLIM. For example XY-1 indicates that a connection isestablished on both fabrics using SvNet ID 1 (that is, ServerNet ID of the first set of ServerNetconnections).

CLIM Maintenance Interface Status & IP AddressesShows the dedicated service LAN interface (eth0) on the CLIM, giving the interface status(UP or DOWN), link pulse status, and IP address. If multiple IP addresses are associatedwith the maintenance interface, they are shown on separate lines.

Maintenance Provider Interface Status & IP AddressesShows the maintenance provider interface (eth0:0) on the CLIM configured to supportMaintenance Provider, showing:

Name of maintenance provider interface on the CLIM (eth0:0)Interface name

UP, DOWN or DNOP (down due to operator command)Interface status

UP, DOWN, or — if no link pulse statusLink pulse status

IP address family and actual IP address for the interfaceIP address(es)

If multiple IP addresses are associated with the maintenance provider interface, they areshown on separate lines.This attribute is applicable only when there is a maintenance provider interface configuredon the CLIM and if the CLIM has IP MODE. Link pulse status of the maintenance providerinterface is identical to link pulse status of CLIM dedicated service LAN interface.

258 SCF Reference for CIP

Data Provider prov-name Interface Status & IP AddressesShows the CLIM’s data interfaces on the CLIM for a particular provider, including:

Indicates a special condition of the interface or IP address:Flag

• (V) for IP address created to support failover from other CLIM

• (F) for interface that is currently active on a different CLIM)

• (T) for manually configured IPv6-over-IPv4 tunnel interface

• (X) indicates an interface whose failover configuration is invalid

Is the name of the interface on the CLIMInterface name

Is UP, RDY, DNOP, or DOWN.Interface status

• UP indicates the interface resources are active and usable

• RDY indicates the interface is usable but resources are not active

• DNOP indicates the interface is down due to an operator command (notusable)

• DOWN indicates the interface is down due to a failure on the CLIM (notusable)

Is UP, DOWN, or —Link pulse status

• UP indicates the link is active

• DOWN indicates the link is inactive

• — indicates no link pulse statusif no link pulse status

Is the name of the master interface if this is a slave interface (otherwise, thisattribute is empty)

Master name

Is the IP address family and actual IP address associated with the interfaceIP addresses

Physical interfaces other than eth0, logical interfaces, and bonded interfaces are shown.Slave interfaces show their master bonded interface in the column labeled Master. Each IPaddress associated with an interface (there can be multiple IP addresses) is shown onseparate line. More information about the CLIM interfaces can be retrieved using the CLIMsoftware ifconfig command on the CLIM.This attribute is applicable only if the CLIM is an IP, IB or Telco CLIM in the STARTED state.

NOTE: If the specified prov-name does not exist on the system, “(Provider Does NotExist)” will be appended to the header line. If the specified is not an IPDATA Provider,“(Provider Not IPDATA)” will be appended to the header line. In both cases, you cannot usethe interfaces associated with those providers.

Interface Failover Configuration and StatusShows the CLIM’s data interfaces failover configuration and status information. Field definitionsare:

Indicates a special condition of the interface:Flag

• (D) indicates interface whose failover is directed externally by NonStop partner process

• (V) indicates an interface failover from another CLIM

• (F) for an interface that is currently active on a different CLIM)

• (T) indicates a manually configured IPv6-over-IPv4 tunnel interface

CIPMAN SCF Commands 259

• (X) indicates an interface whose failover configuration is invalid

• (P) indicates an interface whose provider configuration is invalid or does not exist

Name of interface from the socket-application perspective, (host interface name)Interface name

Name of the failover interface for the specified interface or the name of the associateinterface for a tunnel interface. If this field is shown in parentheses, then it is an associateinterface.

Failover/(assoc)

Indicates the failover status of the interface:Failover status

• — indicates that no failover is configured

• HOME indicates that the interface is running on its home interface

• BkFO indicates that the interface is running on its failover interface due to a failurecondition

• BkOP indicates the interface is running on its failover interface due to an operatorrequest

• BkUN indicates the interface is running at its failover interface for an unknown reason.(CIPMAN has restarted.)

• BkDI indicates the interface is running at its failover interface due to directed failover

Indicates the current location of the interface (home interface or failover interface). If thereis no failover (HOME or __), the location is the same as the interface name. If there isfailover, then this field is identical to the failover interface at the time of the failover.

Current location

Indicates the name of the associated IPDATA provider.Provider

NOTE: Interface failover status is only applicable for an IP or IB CLIM.

NOTE: In special cases, current can be something other than the home interface or thecurrent failover interface. In such a case, current is the previous failover interface (whichwas correct at the time the interface failed over), but the failover configuration for that interfacehas changed to use a different failover interface.

Example 80: STATUS CLIM Detailed, NonStop X displays detailed status information on aNonStop X system:

Example 80 STATUS CLIM Detailed, NonStop X

This example shows the Multiple Providers per CLIM option, MULTIPROV ON, and displaysoutput for multiple providers.STATUS CLIM $ZZCIP.NCLIM000, DETAIL

> CIP Detailed Status CLIM \MYSYS.$ZZCIP.NCLIM000

Mode...................... IPMultiProv................. ONCLIM HW Config Status..... ConfiguredState..................... STARTEDTrace Status.............. OFF

Last Restart Time......... 02 November 2014, 12:28:50.000CLIM Hostname............. NCLIM000CIP SW Version............ T0853L01_01OCT2014_03SEP2014_ADANetwork SW Version........ T0691L01_01OCT2014_ADA_CLIM_G12Storage SW Version........ T0830L01_01OCT2014_23SEP2014_ABCNumber of Socket Servers.. 1Linux Version:Linux version 3.2.25-clim-5-amd64 #1 SMP Thu Feb 28 01:10:30 UTC 2014

Fabric Status:CIPMON Mgmt DataZCM00 XY-1 XY-1ZCM01 XY-1 XY-1

260 SCF Reference for CIP

ZCM02 XY-1 XY-1ZCM03 XY-1 XY-1

CLIM Maintenance Interface Status & IP Addresses:lo Sts:UP LkP:-- IPv4: 127.0.0.1

IPv6: ::1eth0 Sts:UP LkP:DOWN IPv4: 192.168.37.81

IPv6: fe80:0000:0000:0000:0214:38ff:feeb:db5a

Maintenance Provider Interface Status & IP Addresses:lo Sts:UP LkP:-- IPv4: 127.0.0.1

IPv6: ::1eth0:0 Sts:UP LkP:DOWN IPv4: 192.168.36.10

Data Provider ZTC0 Interface Status & IP Addresses:Flg Name Status LkP Master / IP Family & Address

lo UP --IPv4: 127.0.1.2IPv4: 127.0.0.1IPv6: ::1

eth1 UP UPIPv4: 172.17.190.101IPv6: 3ffe:1200:190:1:21f:29ff:fe0d:ac1eIPv6: 3ffe:1200:190:2:21f:29ff:fe0d:ac1eIPv6: fe80::21f:29ff:fe0d:ac1e

eth1 UP UPIPv4: 172.17.190.30IPv6: 3ffe:1200:0190:0002:0215:60ff:fe04:24deIPv6: 3ffe:1200:0190:0001:0215:60ff:fe04:24deIPv6: fe80:0000:0000:0000:0215:60ff:fe04:24de

eth2 UP UPIPv4: 172.17.190.102IPv6: 3ffe:1200:0190:0002:0215:60ff:fe04:24dfIPv6: 3ffe:1200:0190:0001:0215:60ff:fe04:24dfIPv6: fe80:0000:0000:0000:0215:60ff:fe04:24df

(V) IPv4: 172.17.190.82(V) IPv6: 3ffe:1200:0190:0002:0215:60ff:fe04:42ed(V) IPv6: 3ffe:1200:0190:0001:0215:60ff:fe04:42ed(V) IPv6: fe80:0000:0000:0000:0215:60ff:fe04:42ed

Data Provider ZSAM1 Interface Status & IP Addresses:Flg Name Status LkP Master / IP Family & Address

lo UP --IPv4: 127.0.1.2IPv4: 127.0.0.1IPv6: ::1

eth3 UP UPIPv4: 172.17.190.103IPv6: 3ffe:1200:0190:0002:0215:60ff:fe04:257eIPv6: 3ffe:1200:0190:0001:0215:60ff:fe04:257eIPv6: fe80:0000:0000:0000:0215:60ff:fe04:257e

(F) eth4 DOWN DOWNIPv4: 0.0.0.0

(T) TUN1 UP -- eth3IPv6: fe80:0000:0000:0000:0111:5038:9999:1234

Data Provider JUNK Interface Status & IP Addresses: (Provider Does Not Exist)Flg Name Status LkP Master / IP Family & Address

lo UP --IPv4: 127.0.1.2IPv4: 127.0.0.1IPv6: ::1

eth5 RDY UPIPv4: 0.0.0.0

Interface Failover Configuration and Status:Flg Name Failover/(Assoc) Fovr Current Provider

NCLIM000.eth1 NCLIM001.eth1 Home NCLIM000.eth1 ZTC0NCLIM000.eth2 -- -- NCLIM000.eth2 ZTC0

(V) NCLIM001.eth2 NCLIM000.eth2 BkOP NCLIM000.eth2 ZTC0NCLIM000.eth3 NCLIM002.eth3 Home NCLIM000.eth3 ZSAM1

CIPMAN SCF Commands 261

(F) NCLIM000.eth4 NCLIM001.eth3 BkFO NCLIM001.eth3 ZSAM1(T) NCLIM000.TUN1 (NCLIM000.eth3) Home NCLIM000.TUN1 ZSAM1(P) NCLIM000.eth5 -- -- NCLIM000.eth5 JUNK(D) indicates an interface whose failover is directed externally by NonStop partner

process

NOTE: CLIM Maintenance Interface Status & IP Addresses, Maintenance Provider InterfaceStatus & IP Addresses, and Data Interface Status & IP Addresses are usually available only ifthe CLIM is in the STARTED state.

ModeShows the operating mode of the CLIM. An IP or IB CLIM provides access to TCP/IPnetworking. A STORAGE CLIM provides access to disks and other storage devices. A TelcoCLIM (Mode OPEN) provides access to Telco protocols to communicate with a Telco network.

MultiProvIndicates whether the specified CLIM supports association with multiple IPDATA providerssimultaneously.

CLIM HW Config StatusIndicates whether a CLIM with the specified name is configured on this system and can haveany of the values:

CLIM is configured correctly and is useable.Configured

CLIM is not configured (not useable).Not Configured

A device is configured with the specified name but is not a CLIM (not useable).Non-CLIM

The MODE attribute of this CLIM object does not match the configured information withinthe hardware configuration database record (not usable).

Mode Mismatch

StateIndicates the current summary state of the CLIM. If CLIM is in STARTED state but can onlybe access through a single fabric (X or Y), then there will be an additional "(X)" or "(Y)" after"STARTED" to indicate that access to the CLIM is only available on the specified fabric.

Trace StatusShows the processors that are tracing the CLIM and each trace file name. If no processor istracing the CLIM, the value in this field is OFF.

Last Restart TimeShows the time of the last CLIM software restart as saved by the CLIM.

CLIM HostnameShows the CLIM software hostname configured on the CLIM. This must be identical to CLIMobject name.

CIP SW VersionShows the version of CIP software running on the CLIM.

Network SW VersionShows the version of CIP subsystem network software running on the CLIM.

Storage SW VersionShows the version of Storage subsystem software installed on the CLIM.

Number of Socket ServersShows the number of Socket Server (CIPSSRV) processes running on the CLIM.

262 SCF Reference for CIP

CIP/Linux VersionShows the version of CLIM software running on the CLIM. This value is retrieved from the/proc/version file.

Fabric StatusDisplays the CIPMON status, connections to the CLIM, and availability of the X and YServerNet fabrics for each running processor in the system. The Mgmt column shows themanagement connection to CLIMAGT, and the Data column shows the data path connectionsto the CIPSSRV processes. The possible values are:

CIPMON is down.MON-DOWN

CIPMON is up, but no connection is established.--

Connection is established; only the X fabric is available.X-

Connection is established; only the Y fabric is available.-Y

Connection is established; X and Y fabrics are available.XY

The number suffix (for example, -1) indicates the particular set of fabrics being used for theconnection with the CLIM. For example XY-1 indicates that a connection is established onboth fabrics.

CLIM Maintenance Interface Status & IP AddressesShows the dedicated service LAN interface (eth0) on the CLIM, giving the interface status(UP or DOWN), link pulse status, and IP address. If multiple IP addresses are associatedwith the maintenance interface, they are shown on separate lines.

Maintenance Provider Interface Status & IP AddressesShows the maintenance provider interface (eth0:0) on the CLIM configured to supportMaintenance Provider, showing:

Name of maintenance provider interface on the CLIM (eth0:0)Interface name

UP, DOWN or DNOP (down due to operator command)Interface status

UP, DOWN, or — if no link pulse statusLink pulse status

IP address family and actual IP address for the interfaceIP address(es)

If multiple IP addresses are associated with the maintenance provider interface, they areshown on separate lines.This attribute is applicable only when there is a maintenance provider interface configuredon the CLIM and if the CLIM has IP MODE. Link pulse status of the maintenance providerinterface is identical to link pulse status of CLIM dedicated service LAN interface.

Data Provider prov-name Interface Status & IP AddressesShows the CLIM’s data interfaces on the CLIM for a particular provider, including:

Indicates a special condition of the interface or IP address:Flag

• (V) for IP address created to support failover from other CLIM

• (F) for interface that is currently active on a different CLIM)

• (T) for manually configured IPv6-over-IPv4 tunnel interface

• (X) indicates an interface whose failover configuration is invalid

Is the name of the interface on the CLIMInterface name

CIPMAN SCF Commands 263

Is UP, RDY, DNOP, or DOWN.Interface status

• UP indicates the interface resources are active and usable

• RDY indicates the interface is usable but resources are not active

• DNOP indicates the interface is down due to an operator command (notusable)

• DOWN indicates the interface is down due to a failure on the CLIM (notusable)

Is UP, DOWN, or —Link pulse status

• UP indicates the link is active

• DOWN indicates the link is inactive

• — indicates no link pulse statusif no link pulse status

Is the name of the master interface if this is a slave interface (otherwise, thisattribute is empty)

Master name

Is the IP address family and actual IP address associated with the interfaceIP addresses

Physical interfaces other than eth0, logical interfaces, and bonded interfaces are shown.Slave interfaces show their master bonded interface in the column labeled Master. Each IPaddress associated with an interface (there can be multiple IP addresses) is shown onseparate line. More information about the CLIM interfaces can be retrieved using the CLIMsoftware ifconfig command on the CLIM.This attribute is applicable only if the CLIM is in the STARTED state.

NOTE: If the specified prov-name does not exist on the system, “(Provider Does NotExist)” will be appended to the header line. If the specified is not an IPDATA Provider,“(Provider Not IPDATA)” will be appended to the header line. In both cases, you cannot usethe interfaces associated with those providers.

Interface Failover Configuration and StatusShows the CLIM’s data interfaces failover configuration and status information. Field definitionsare:

Indicates a special condition of the interface:Flag

• (V) indicates an interface failover from another CLIM

• (F) for an interface that is currently active on a different CLIM)

• (T) indicates a manually configured IPv6-over-IPv4 tunnel interface

• (X) indicates an interface whose failover configuration is invalid

• (P) indicates an interface whose provider configuration is invalid or does not exist

Name of interface from the socket-application perspective, (host interface name)Interface name

Name of the failover interface for the specified interface or the name of the associateinterface for a tunnel interface. If this field is shown in parentheses, then it is an associateinterface.

Failover/(assoc)

Indicates the failover status of the interface:Failover status

• — indicates that no failover is configured

• HOME indicates that the interface is running on its home interface

• BkFO indicates that the interface is running on its failover interface due to a failurecondition

• BkOP indicates the interface is running on its failover interface due to an operatorrequest

264 SCF Reference for CIP

• BkUN indicates the interface is running at its failover interface for an unknown reason.(CIPMAN has restarted.)

• BkDI indicates the interface is running at its failover interface due to directed failover

Indicates the current location of the interface (home interface or failover interface). If thereis no failover (HOME or __), the location is the same as the interface name. If there isfailover, then this field is identical to the failover interface at the time of the failover.

Current location

Indicates the name of the associated IPDATA provider.Provider

NOTE: Interface failover status is only applicable for an IP or IB CLIM.

NOTE: In special cases, current can be something other than the home interface or thecurrent failover interface. In such a case, current is the previous failover interface (whichwas correct at the time the interface failed over), but the failover configuration for that interfacehas changed to use a different failover interface.

Example 81: STATUS CLIM Summary, NonStop X Systems enables you to use the STATUSCLIM command to obtain fabric connectivity information for NonStop X systems. If the State isSTARTED, the CLIM is accessible over both fabrics. If the state is STARTED (X), the CLIM isonly accessible over the X-fabric. If the state is STARTED (Y), the CLIM is only accessible overthe Y-fabric. This particular display of the STATUS CLIM state only applies to NonStop X systems.

Example 81 STATUS CLIM Summary, NonStop X Systems

> STATUS CLIM $ZZCIP.NCLIM000CIP Status CLIM \MYSYS.$ZZCIP.NCLIM000

Name Config State TraceNCLIM000 Yes STARTED OFF

Example 82: STATUS CLIM, Starting, BladeSystem displays detailed status information on aCLIM in STARTING state:

Example 82 STATUS CLIM, Starting, BladeSystem

> STATUS CLIM $ZZCIP.N1002541, DETAILCIP Detailed Status CLIM \MYSYS.$ZZCIP.N1002541

Mode...................... IPMultiProv................. ONCLIM HW Connection Status. Not ConnectedState..................... STARTINGConnPts................... 2X1 Location............... Group 100 , Module 2 , Slot 5 , Port 4 , Fiber 1Y1 Location............... Group 100 , Module 3 , Slot 7 , Port 4 , Fiber 1X1 Location............... Group 100 , Module 2 , Slot 5 , Port 4 , Fiber 2Y1 Location............... Group 100 , Module 3 , Slot 7 , Port 4 , Fiber 2X1 Connection Status...... Not ConnectedY1 Connection Status...... Not ConnectedX2 Connection Status...... Not ConnectedY2 Connection Status...... Not ConnectedTrace Status.............. OFF

Last Known Problem........ CLIM Hardware Not Available

Last Known MultiProv IPDATA Provider Associations:ZTC0ZSAM1

CIPMAN SCF Commands 265

Last Known ProblemShows last known reason for the CLIM staying in STARTING state. This entry applies toSTARTING state, only, and is not shown for CLIMs in STOPPED or STARTED state.

Last Known MultiProv IPDATA Provider AssociationsLists the IPDATA providers that are associated with this CLIM based on the last knownconfiguration information for that CLIM. This entry applies only when the CLIM hasMULTIPROV ON in STARTING or STOPPED state. If there are no known IPDATA providersassociated with a CLIM with MULTIPROV ON, no names are listed.

Example 83: STATUS CLIM, Detailed, Storage CLIM, BladeSystem displays detailed statusinformation for CLIM S1002553:

Example 83 STATUS CLIM, Detailed, Storage CLIM, BladeSystem

> STATUS CLIM $ZZCIP.S1002553, DETAILCIP Detailed Status CLIM \MYSYS.$ZZCIP.S1002553

Mode...................... STORAGECLIM HW Connection Status. ConnectedState..................... STARTEDConnPts................... 2X1 Location............... Group 100 , Module 2 , Slot 5 , Port 5 , Fiber 3Y1 Location............... Group 100 , Module 3 , Slot 7 , Port 5 , Fiber 3X2 Location............... Group 100 , Module 2 , Slot 5 , Port 5 , Fiber 4Y2 Location............... Group 100 , Module 3 , Slot 7 , Port 5 , Fiber 4X1 Connection Status...... ConnectedY1 Connection Status...... ConnectedX2 Connection Status...... ConnectedY2 Connection Status...... ConnectedTrace Status.............. OFF

Last Restart Time......... 02 Sep 2007, 12:40:55.000CLIM Hostname............. S1002541CIP SW Version............ T0853H01_01MAY2008_03MAR2008_Network SW Version........ T0691H01_01MAY2008_AAA_CLIMStorage SW Version........ TXXXXH06_19MAY2007_H06_YYYYYYYNumber of Socket Servers.. 1Linux Version:Linux version 2.6.18-6-clim-amd64 (Debian 2.6.18.dfsg.1-18hpdeetch1hpde1.1) (brian.haley@hp.com) (gcc version 4.1.2 20061115 (prerelease) (Debian4.1.1-21)) #1 SMP PREEMPT Thu Feb 28 01:10:30 UTC 2008

Fabric Status:CIPMON Mgmt DataZCM00 XY-1 XY-1ZCM01 XY-2 XY-2ZCM02 XY-1 XY-1ZCM03 XY-2 XY-2

CLIM Maintenance Interface Status & IP Addresses:lo Sts:UP LkP:-- IPv4: 127.0.0.1

IPv6: ::1eth0 Sts:UP LkP:DOWN IPv4: 192.168.37.53

For field descriptions, see the STATUS CLIM Detailed display for the IP CLIM.

NOTE: The Fiber attribute might not be supported on your system. For more information, seethe planning guide for your system.

Example 84: STATUS CLIM, Detailed, Storage CLIM, NonStop X displays the status of SCLIM002(Storage CLIM for NonStop XPF System) in STARTING state:

266 SCF Reference for CIP

Example 84 STATUS CLIM, Detailed, Storage CLIM, NonStop X

> STATUS CLIM $ZZCIP.SCLIM002, DETAILCIP Detailed Status CLIM \MYSYS.$ZZCIP.SCLIM002

Mode...................... StorageCLIM HW Config Status..... Not ConfiguredState..................... STARTINGTrace Status.............. OFF

Last Known Problem........ CLIM Hardware not available

CIPMAN SCF Commands 267

Example 85 STATUS CLIM, Detailed, T0971 VPROC

The SCF STATUS CLIM $ZZCIP interface displays the T0971 VPROC. This requires both NSKand CLIM to be running the new CIP code. If either NSK or the CLIM is running legacy CIP code,the T0971 VPROC may not be displayedSTATUS CLIM $ZZCIP.NCLIM000, DETAIL

>CIP Detailed Status CLIM \IBERIA.$ZZCIP.NCLIM000

Mode...................... IPMultiprov................. OFFCLIM HW Config Status..... ConfiguredState..................... STARTEDTrace Status.............. OFF

Last Restart Time......... 12 Jun 2015, 8:18:52.000CLIM Hostname............. NCLIM000CIP SW Version............ T0853L02_01AUG2015_22APR2015_BAH

Network SW Version........ T0691L02_01AUG2015_BAH_CLIM_A05Storage SW Version........ T0830L02_18FEB2015_02APR2015_BABPatch SW Version.......... T0971L02_09JUN2015_04JUN2015_BABNumber of Socket Servers.. 1Linux Version:Linux 3.2.30-clim-58.6-amd64 #1 SMP Wed Mar 25 14:08:15 UTC 2015

Fabric Status:CIPMON Mgmt DataZCM00 XY-1 XY-1ZCM01 XY-1 XY-1ZCM02 XY-1 XY-1ZCM03 XY-1 XY-1

CLIM Maintenance Interface Status & IP Addresses:eth0 Sts:UP Lkp:UP IPv4: 192.168.37.35

IPv6: fe80::2e76:8aff:fe4f:bf74

Maintenance Provider Interface Status & IP Addresses:eth0:0 Sts:UP Lkp:UP IPv4: 192.168.36.10

Data Provider ZTC0 Interface Status & IP Addresses:Flg Name Status LkP Master / IP Family & Address

lo UP --IPv4: 127.0.1.2IPv4: 127.0.0.1IPv6: ::1

eth4 UP DOWNIPv6: fe80::9e8e:99ff:fe4b:fef8

Interface Failover Configuration and Status:Flg Name Failover/(Assoc) Fovr Current Provider

NCLIM000.eth4 -- NCLIM000.eth4 ZTC0

STATUS MONThe STATUS MON command displays the current status of the specified MON(s), in this system.STATUS MON Command SyntaxSTATUS MON $ZZCIP.ZCMnn [,DETAIL]

ZCMnnIdentifies the CIPMON process for which to display status. nn is a two-digit value in the range00 through 15. A wildcard can specify multiple MONs in this system.

Example 86 displays the status of all CIP MONs in this system.

268 SCF Reference for CIP

Example 86 STATUS MON Summary

> STATUS MON $ZZCIP.*CIP Status MON \MYSYS.$ZZCIP.*

MON Pid Status Priority TraceZCM00 -1, -1 STOPPED -1 OFFZCM01 -1, -1 STOPPED -1 OFFZCM02 -1, -1 STOPPED -1 OFFZCM03 3,26 STARTED 200 OFFZCM05 5,26 STARTED 200 OFFZCM06 6,26 STOPPED 200 OFFZCM07 7,26 STARTED 200 OFF

Example 87 displays detailed status information for the MON named ZCM03:

Example 87 STATUS MON Detailed

> STATUS MON $ZZCIP.ZCM03, DETAILCIP Detailed Status MON \MYSYS.$ZZCIP.ZCM03

Heap Memory Limit........ 133615616Heap Memory Used......... 147832PID...................... ( 3, 26)Priority................. 200QIO Pool Current......... 729934QIO Pool Limit........... 0State.................... STARTEDTrace Status............. OFFTrace Filename...........

Fabric Status:CLIM Mgmt Data NumdataN1002532 XY-1 XY-1 1N1003741 XY-2 XY-2 1N1012542 X--1 X--1 1

Fabric StatusDisplays the connections to each known CLIM and the availability of the X and Y fabrics. TheMgmt column shows the management connection to CLIMAGT, the Data column shows thedata path connections to the CIPSSRV processes, and the Numdata column shows thenumber of CIPSSRV processes. The possible values are:

CIPMON is up, but no connection is established.--

Connection is established; only the X fabric is available.X-

Connection is established; only the Y fabric is available.-Y

Connection is established; both the X and Y fabrics are available.XY

The number suffix (for example, -1) indicates the particular set of fabrics being used for theconnection with the CLIM. For example, XY-1 indicates that a connection is established onboth fabrics using SvNet ID 1 (the ServerNet ID of the first set of ServerNet connections0.

STATUS PROCESSThe STATUS PROCESS command displays the current status of the CIPMAN process in thissystem.

CIPMAN SCF Commands 269

STATUS PROCESS Command SyntaxSTATUS PROCESS $ZZCIP [,DETAIL]

Example 88 displays the state of the CIPMAN process:

Example 88 STATUS PROCESS Summary

> STATUS PROCESS $ZZCIPCIP Status PROCESS \MYSYS.$ZZCIP

Name State PPID BPID Priority Trace

$ZZCIP STARTED ( 0, 22) ( 1, 11) 200 OFF

Example 89 displays the detailed state of the CIPMAN process:

Example 89 STATUS PROCESS Detailed

> STATUS PROCESS $ZZCIP, DETAILCIP Detailed Status PROCESS \MYSYS.$ZZCIP

Heap Memory Limit........ 133615616Heap Memory Used......... 69632PID Primary.............. ( 0, 22)PID Backup............... ( 1, 11)Priority................. 200QIO Pool Current......... 0QIO Pool Limit........... 0State.................... STARTEDTrace Status............. OFFTrace Filename...........

STATUS PROVIDERThe STATUS PROVIDER command displays the status of the specified providers in this system.STATUS PROVIDER Command SyntaxSTATUS PROVIDER $ZZCIP.prov-name [,{DETAIL | ROUTE[,CPU cpu]}]

prov-nameIs the name of the provider for which to display status information. A wildcard can specifymultiple providers.

DETAILSpecifies that the display is to include additional detailed status information about the provider.

ROUTESpecifies that the display is to show Provider-routing information. This option is not valid forthe MAINTENANCE provider.

CPU cpuSpecifies the CPU for which to obtain Provider-routing information. The Default is to letCIPMAN automatically select a CPU.

Example 90 displays the status of all known providers.

Example 90 STATUS PROVIDER Summary

> STATUS PROV $ZZCIP.*CIP Status PROVIDER

Name Status TPStatus TraceZCSAM STARTED Started OFFPROV1 STARTED Invalid (0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15)

270 SCF Reference for CIP

TPStatusShows the status of the transport-service provider process associated with the Provider. Thepossible values are:

The TP is running and is a CIPSAM process.Started

A process with the specified TP name is running but the program name is not CIPSAM.Invalid

No process with the specified TP name is running in the system.Stopped

TraceShows which processors that have started a trace on the Provider. OFF indicates that noprocessor is tracing the Provider.

Example 91 displays detailed status information for IPDATA PROVIDER ZTC0.

Example 91 STATUS PROVIDER Detail

-> STATUS PROV $ZZCIP.ZTC0, DETAILCIP Detailed Status PROVIDER \MYSYS.$ZZCIP.ZTC0

State…................. STARTEDTPStatus….............. StartedType….................. IPDATACurrent Access…........ ( 0, 1, 2, 3 )Trace Status:CPU FilenameOFF

Interface Status & IP Addresses:Name Current Status LkP Fovr Indexclim1.lo clim1.lo UP -- -- 0x00003001

Ipv4: 127.0.0.1Ipv6: ::1

clim1.eth1 clim1.eth1 UP UP HOME 0x00003002Ipv4: 172.17.190.101Ipv6: 3ffe:1200:0190:0002::24deIpv6: 3ffe:1200:0190:0001::24deIpv6: fe80::0215:60ff:fe04:24de

clim1.eth2 clim1.eth2 UP UP -- 0x00003003Ipv4: 172.17.190.102Ipv6: 3ffe:1200:0190:0002::24dfIpv6: 3ffe:1200:0190:0001::24dfIpv6: fe80::0215:60ff:fe04:24df

clim1.eth3 clim1.eth3 UP UP HOME 0x00003004Ipv4: 172.17.190.103Ipv6: 3ffe:1200:0190:0002::257eIpv6: 3ffe:1200:0190:0001::257eIpv6: fe80::0215:60ff:fe04:257e

clim1.eth4 clim2.eth3 UP DOWN BkFO 0x00003005Ipv4: 172.17.190.104Ipv6: 3ffe:1200:0190:0002::257fIpv6: 3ffe:1200:0190:0001::257fIpv6: fe80::0215:60ff:fe04:257f

clim2.lo clim2.lo UP -- -- 0x00004001Ipv4: 127.0.0.1Ipv6: ::1

clim2.eth1 clim2.eth1 UP UP HOME 0x00004002Ipv4: 172.17.190.81Ipv6: 3ffe:1200:0190:0002: 42ecIpv6: 3ffe:1200:0190:0001::42ecIpv6: fe80::0215:60ff:fe04:42ec

CIPMAN SCF Commands 271

clim2.eth2 clim1.eth2 UP UP BkDI 0x00004003Ipv4: 172.17.190.82Ipv6: 3ffe:1200:0190:0002::42edIpv6: 3ffe:1200:0190:0001::42edIpv6: fe80::0215:60ff:fe04:42ed

clim2.eth3 clim2.eth3 UP UP HOME 0x00004004Ipv4: 172.17.190.83Ipv6: 3ffe:1200:0190:0002: 4:42eeIpv6: 3ffe:1200:0190:0001::42eeIpv6: fe80::0215:60ff:fe04:42ee

clim2.eth4 clim2.eth4 UP DOWN HOME 0x00004005Ipv4: 172.17.190.84Ipv6: 3ffe:1200:0190:0002::42efIpv6: 3ffe:1200:0190:0001::42efIpv6: fe80::0215:60ff:fe04:42ef

Interfaces Failover Configuration and Status:F Home Sts LkP Backup Sts LkP Current Fovr

clim1.eth1 UP UP clim2.eth1 UP UP clim1.eth1 HOMEclim1.eth3 UP UP clim3.eth3 -- -- clim1.eth3 HOMEclim1.eth4 DOWN DOWN clim2.eth3 UP DOWN clim2.eth3 BkFOclim2.eth1 UP UP clim1.eth1 UP UP clim2.eth1 HOME

D clim2.eth2 DNOP DOWN clim1.eth2 UP UP clim1.eth2 BkDIclim2.eth3 UP UP clim3.eth3 -- -- clim2.eth3 HOMEclim2.eth4 UP UP clim3.eth4 -- -- clim2.eth4 HOME

TypeShows the type of provider. An IPDATA provider provides TCP/IP access through dataEthernet ports of one or more CLIMs associated with that IPDATA provider. A MAINTENANCEprovider provides TCP/IP access through the maintenance Ethernet interface of a specificCLIM using a specific IP address.

Current AccessShows the processors that have established access to the provider.

Trace StatusShows the processors that are tracing the provider and each trace file name.

FamilySpecifies the network mode of the provider. An INET family indicates the provider operatesonly in IPv4 mode. A DUAL family indicates the provider operates in both IPv4 mode andIPv6 mode.

Interface Status & IP AddressesShows the data interfaces associated with the provider, giving:

Is the interface name from socket application perspective (host interface name)Name

Is the current location of the interface (which can be different in the case of failover).If no failover is configured (HOME or —), Current is identical to the failover interfaceat the time of the failover. For the special interface lo, this field is empty.

Current

Is the interface status.Status

• UP indicates the interface resource is active and usable

• DNOP indicates the interface is down due to operator command. It is not usable.

• DOWN indicates the interface is down due to a failure on the CLIM. It is not usable.

• -- indicates no CLIM in the STARTED state is associated with the interface.

272 SCF Reference for CIP

Indicates the link pulse status:LkP

• UP indicates the link is active and usable

• DOWN indicates the link is down and not usable

• -- indicates there is no link pulse status

Is the failover status of the interface.Fovr

• -- indicates no failover is configured

• HOME indicates the provider is running on the home interface

• BkFO indicates the provider is running on the failover interface due to a failure

• BkOP indicates the provider is running on the failover interface due to an operatorrequest

• BkUN indicates the provider is running on the failover interface after a CIPMANrestart

• BkDI indicates the provider is running at backup interface due to directed failover.

Interface index value within the associated IPDATA ProviderIndex

IP address family and actual IP addresses associated with the interface. Each IPaddress (there can be multiple) is shown on a separate line.

IP address

Interface Failover Configuration and StatusShows the failover configuration and status for each data interfaces associated with theprovider that has been configured to support failover, showing:

Indicates special condition of interface:F

• T indicates a manually configured IPv6-over-IPv4 tunnel interface

• X indicates the interface whose failover configuration is invalid

• D indicates the interface whose failover is directed externally by NonStop partnerprocess

Indicates the home interface nameHome

Indicates the failover-interface name or the name of the associate interface for atunnel interface. (The associate interface is shown in parentheses.)

Failover/(Assoc)

Indicates the current location (which can be different in the case of a failover). If nofailover has occurred, that is, if this is the home interface, then this value is identical

Current

to the interface name. If a failover has occurred, then this value is identical to thefailover interface (at the time of failover).

Is the failover status of the interface.Fovr

• — indicates no failover is configured

• HOME indicates the provider is running on the home interface

• BkFO indicates the provider is running on the failover interface due to a failure

• BkOP indicates the provider is running on the failover interface due to an operatorrequest

• BkUN indicates the provider is running on the failover interface after a CIPMANrestart

• BkDI indicates the provider is running at backup interface due to directed failover.

For the home interface and the failover interface, these additional values are possible:

Interface statusSts

• -- Indicates the CLIM associated with the interface is not in the STARTED state

• UP indicates the interface resources are active and usable

CIPMAN SCF Commands 273

• RDY indicates the interface is usable but resources are not active

• DNOP indicates the interface is down due to an operator command, and is not usable

• DOWN indicates the interface is down due to a failure on the CLIM, and is not usable

Indicates the link pulse status (UP, DOWN, or, if there is no link-pulse status, —)LkP

Example 92 shows the detailed status of the MAINTENANCE PROVIDER ZTCP0.

Example 92 STATUS Maintenance PROVIDER Detail

> STATUS PROVIDER $ZZCIP.ZTCP0, DETAILCIP Detailed Status PROVIDER \MYSYS.$ZZCIP.ZTCP0

State.................... STARTEDTPStatus................. StartedType..................... MAINTENANCECLIM..................... N1003741Current Access........... ( 0, 1, 2, 3 )Trace Status:CPU Filename0 \MYSYS.$DATA.TEST1.TRCPRV

Interface Status & IP Address:Name Status LkP IP AddressN1003741.eth0:0 UP UP 192.168.36.10

CLIMShows the name of the CLIM associated with the MAINTENANCE provider. This attribute isapplicable only to provider with TYPE MAINTENANCE.

Interface Status & IP AddressShows the maintenance Provider interface associated with the provider, giving the name,interface status (UP, DNOP (down due to operator command, or DOWN), link pulse status,and IP address associated with the interface.

NOTE: This attribute is not shown unless the provider is in the STARTED state.

Example 93: STATUS PROVIDER Route displays status of a provider route:

Example 93 STATUS PROVIDER Route

> STATUS PROVIDER $ZZCIP.ZTC0, ROUTE, CPU 0CIP Detailed Status PROVIDER \MYSYS.$ZZCIP.ZTC0

Provider State.................. STARTEDProvider Routing Status (CPU 0):Destination/Prefix Length Type CLIM ROUTE PriIPv4: 192.168.0.0/8 G N1002532IPv4: default N1002532 ROUTE1 50IPv6: 3ffe:1200:0190:0002:0215:60ff:fe04:42ec/128 S N1002532IPv6: default N1002532 ROUTE1 50

Provider StateIndicates the PROVIDER object state, either STOPPED, STARTING, or STARTED.

CPUIndicates the processor where provider routing information is obtained.

274 SCF Reference for CIP

Destination/Prefix LengthIs the address family, IP address of the remote host or network that can be reachable via theCLIM specified in the CLIM field, and the number of bits in the prefix or subnet mask. Thekeyword default is shown for default routes (IP address and prefix length zero).

TypeIndicates the state, type, and origin of the route:

The destination is a gateway, not on the local subnetworkG

The route is for a specific host, not a networkH

The route was manually addedS

CLIMIs the CLIM through which the remote host or network specified in the DESTINATION fieldis to be reached.

ROUTEIs the name of the ROUTE object subordinated to the specified PROVIDER object that isassociated with the default route of the specified CLIM. This field is only shown for defaultroutes that have associated ROUTE object.

PriIs the priority of the ROUTE object subordinated to the specified PROVIDER object that isassociated with the default route of the specified CLIM. This field is only shown for defaultroutes that have associated ROUTE object.

STATUS PROVIDER GuidelinesThe STATUS PROVIDER ROUTE command is rejected if the PROVIDER object is of TYPEMAINTENANCE.

STOP CommandsSTOP is a sensitive command that halts the operation of the specified object. If existing socketsare using the object, the command fails. The object is left in the STOPPED state if the commandsucceeds.

STOP CLIMThe STOP CLIM command stops operations on the specified CLIM, provided that the systemhas no existing sockets using the CLIM. If the associated PROVIDER object is in the STARTEDstate, the provider goes to the STARTING state.STOP CLIM Command SyntaxSTOP CLIM $ZZCIP.clim-name

clim-nameIs the name of the CLIM to be stopped. A wildcard can specify a set of CLIMs.

Example 94: STOP CLIM stops the CLIM N1003741:

Example 94 STOP CLIM

> STOP CLIM $ZZCIP.N1003741

STOP MONThe STOP MON command terminates the specified CIPMON process on this system, providedthat there are no open sockets in its processor. If the process has been configured as persistent(AUTORESTART not equal to 1 in the command defining CIPMON as a generic process), the

CIPMAN SCF Commands 275

persistence manager restarts it. This command can be used for online replacement of the CIPMONand CIP Library modules.STOP MON Command SyntaxSTOP MON $ZZCIP.ZCMnn

ZCMnnIdentifies the CIPMON process to be stopped. nn is a two-digit value in the range 00 through15. A wildcard can specify a set of MONs in this system.

Example 95: STOP MON stops the MON ZCM03:

Example 95 STOP MON

> STOP MON $ZZCIP.ZCM03

STOP PROCESSThe STOP PROCESS command stops the operation of the CIPMAN process, provided that doingso would affect no open sockets. This can only occur if there are no active CIPMON processesrunning or all existing CLIM and PROVIDER objects are in the STOPPED state. Subordinateobjects states are not affected unless SUB ALL or SUB ONLY is specified. If the process hasbeen configured as persistent (AUTORESTART not equal to 1 in the command defining CIPMONas a generic process), the persistence manager restarts it.STOP PROCESS Command SyntaxSTOP PROCESS $ZZCIP [,SUB [ ONLY | ALL | NONE ] ]

SUBDetermines the set of objects and subordinate objects that the command targets:• ONLY specifies that only subordinate objects are targets of the command.

• ALL specifies that the named object and the subordinate objects are targets of thecommand. This is the default used if the SUB keyword is used but no option is selected.

• NONE specifies that none of the subordinate objects are targets of the command. Thisis the default selected if the SUB keyword is not used.

Example 96 stops the CIP subsystem on this system.

Example 96 STOP PROCESS

> STOP PROCESS $ZZCIP, SUB ALL

STOP PROCESS GuidelinesMON objects are not affected by STOP PROCESS even when the SUB ALL or SUB ONLY optionis specified.

STOP PROVIDERThe STOP PROVIDER command terminates operations on a provider, provided that the systemhas no existing sockets using the provider.STOP PROVIDER Command SyntaxSTOP PROVIDER $ZZCIP.prov-name

prov-nameIs the name of the provider to stop. A wildcard can specify a set of providers.

Example 97 stops the PROVIDER ZTC1.

276 SCF Reference for CIP

Example 97 STOP PROVIDER

> STOP PROVIDER $ZZCIP.ZTC1

STOP PROVIDER GuidelinesHewlett Packard Enterprise recommends a 15–second delay between issuing a STOP PROVIDERcommand and issuing a DELETE PROVIDER command. This delay is especially recommendedfor the MAINTENANCE PROVIDER.

SWITCH CLIMThe SWITCH CLIM command initiates a manual CLIM-to-CLIM failover operation. It can specifyeither a single interface or all the interfaces on a CLIM. The type of operation is given as aparameter and can be:

Migrate all the resources using the specified interface(s) to the alternate interface of their configuredfailover pair(s). Both home and visiting resources could be moved.

FAILOVER

Migrate the home resources of the specified interface(s) back to their home interface(s), reversing theactions of a previous automatic failover. Resources already on their home interface are not moved.

RESTORE

NOTE: Do not use the SWITCH command to fail over interfaces you plan to delete. Theinterface remains in the UP state when you use the SWITCH command. Before deleting aninterface, use ifstop. The ifstop command deactivates the interface, preventing autoconfiguredIPv6 addresses and link local addresses from being created in the interim.

NOTE: The storage subsystem ($ZZSTO) also supports a SWITCH CLIM command. Forsyntax and display examples, see the SCF Reference Manual for the Storage Subsystem.

SWITCH CLIM Command SyntaxSWITCH CLIM $ZZCIP.clim-name{,FAILOVER | ,RESTORE }{ [,INTF intf-name] | [, PROVIDER prov-name ] }[,FORCED]

clim-nameIs the name of the CLIM containing the interface(s) upon which to perform failover. Wildcardcharacters are not allowed.

FAILOVERMoves all resources off the specified interface(s) to the alternate failover location(s).

RESTOREMoves the home resources of the specified interface(s) back to the home interface(s).

INTF intf-nameSpecifies the name of a single interface for the failover operation. The CLIM name part ofthe interface name must not be specified. Wildcard characters are not allowed. If this optionand the PROVIDER option are omitted, then all interfaces on the CLIM are specified.

PROVIDER prov-nameSpecifies the name of a single IPDATA provider for the failover operation. All interfacesassociated with the specified IPDATA provider on that CLIM are affected by this failoveroperation. Wildcard characters are not allowed. If this option and the INTF option are omitted,all interfaces on the CLIM are specified.

FORCEDIndicates that no warning should be issued and confirmation is assumed.

Example 98 migrates all interface resources off of N1002532 to prepare for maintenance.

CIPMAN SCF Commands 277

Example 98 SWITCH CLIM

> SWITCH CLIM $ZZCIP.N1002532,FAILOVEROpen connections still exist, okay to continue? Y

Example 99 manually restores interface clim2.eth3 back to N1003741.

Example 99 SWITCH CLIM RESTORE

> SWITCH CLIM $ZZCIP.N1003741,RESTORE, INTF ETH3Open connections still exist, okay to continue? Y

SWITCH CLIM Guidelines

• For each specified interface, the interface must be up, a failover interface must be definedand valid, the destination CLIM must be in the STARTED state, and the destination interfacemust be up. No error is generated for interface resources that have already been migrated,but an error is given if interface resources cannot be migrated.

• Before migrating interface resources, each destination CLIM checks whether the migratingaddresses already exist on the IP network. If any do, CIP issues an error and does not switchthe interface. This behavior helps synchronize IP-address migration between the CLIMsinvolved. It does not affect other interfaces that are migrating at the same time. The SWITCHcommand does not complete until the outcome of the failover is known. If theduplicate-address check and resource migration may take some time, there could be a delaybefore SCF issues the next command prompt.

• Failover migrates nearly all interface resources, but not TCP or SCTP connections. If a TCPor SCTP connection would be lost during a manual failover, SCF issues a warning and theoperator must confirm that execution is desired, unless the FORCED option is specified.

TRACE CommandsTRACE is a sensitive command that controls trace-data collection for the specified object in aNonStop system. Trace data is saved in a disk file. You can later read the file by using the Ptraceutility, which is described in the PTrace Reference Manual.

NOTE: When logging the trace records to a file using the "log" command, PTrace abends ifthe log file exceeds 99,999 lines because a file on the NonStop host system can support amaximum of 99,999 lines only.

All TRACE commands accept these options:TRACE Command Syntax{,STOP |,TO file-spec[,{BULKIO|NOBULKIO}][,COUNT count][,LOCKSIZE locksize][,NOCOLL][,PAGES pages[,RECSIZE size][,SELECT {select-option|select-option ...}][,WRAP]}

STOPEnds the trace currently in progress. A TRACE command must include either the STOPoption or the TO option.

TO file-specStarts the trace collection and specifies the name of the file in which to store the results ofthe trace. A TRACE command must include either the STOP option or the TO option.

278 SCF Reference for CIP

BULKIO | NOBULKIODesignates whether TRACE should use bulk I/O for tracing. Bulk I/O is faster than conventionalI/O, reducing the number of missing frame errors reported by PTrace, but only one user canaccess the file at a time. The default value is BULKIO. BULKIO cannot be used with theNOCOLL option.

COUNT countSpecifies the number of trace records to be captured. The count is an integer in the range-1 through 32767. If it is omitted or equals -1, records are accumulated until the trace isstopped with the STOP option.

LOCKSIZE locksizeDesignates how much memory space, in units of pages, is locked down at one time. Thevalue must be less than or equal to the value of PAGES. The default value is the lesser ofPAGES and 64 pages.

NOCOLLIndicates that the trace collector process should not be initiated. The disk file is to be writtento by Guardian. The attributes WRAP and NOCOLL cannot be specified together.

PAGES pagesDesignates how much space, in pages, is allocated in the extended data segment used fortracing. Valid range is from 4 to 1024 pages. The default value is 64 pages.

RECSIZE sizeSpecifies the length, in bytes, of the data in the trace data records. The size is an integerfrom 16 to 4050 bytes. The default value is 120 bytes.

SELECT { select-option | ( select-option , ... ) }Selects the operations to be traced. Valid select options are described with each command.

WRAPSpecifies that when the trace disk file end-of-file (EOF) mark is reached, trace data wrapsaround to the beginning of the file and overwrites any data there.

TRACE CLIMThe TRACE CLIM command starts or stops tracing of CIP Library operations for the specifiedCLIM on the processor specified in the CPU modifier. Each CLIM can have no more than onetrace active at a time on each processor, but multiple CLIM/processor combinations can betracing simultaneously to different trace files.This command does not control tracing on the CLIM itself, but rather tracing of operations on theNonStop system for a particular CLIM. To trace on the CLIM, use CLIM software commands.TRACE CLIM Command SyntaxTRACE CLIM $ZZCIP.clim-name{,STOP |,TO file-spec[,{BULKIO|NOBULKIO}][,COUNT count][,LOCKSIZE locksize][,NOCOLL][,PAGES pages[,RECSIZE size][,SELECT {select-option|select-option ...}][,WRAP]}

clim-nameIdentifies the CLIM whose operations are to be traced.

CIPMAN SCF Commands 279

CPU cpuOptional with STOP and identifies the processor on which to stop tracing. If this option is notspecified, all processors stop tracing the CLIM. CPU is required with the TO option andidentifies the processor on which to start tracing the CLIM.

SELECT { select-opt | ( select-opt , … ) }Selects the operations to be traced. Valid select options are:

Trace all operations-1ALL

Trace calls in from external components to this CLIM0CALLIN

Trace calls out to external components from this CLIM1CALLOUT

Trace local calls for the CLIM in the CIP library2CALLLOCAL

Trace ping-related actions for this CLIM3PING

Trace CIP library state machine operations for this CLIM4SMACH

Trace IT-API interrupt events5ITAPIINTR

Trace IT-API events6ITAPIXFER

Trace messages between CIPMON and the CIP library for this CLIM7CMOMSG

Trace CIP library errors for CLIM8ERROR

Example 100 starts a trace of operations in processor 1 for N1003741 to file$DATA00.TRC1003741.CPU1.

Example 100 TRACE CLIM

> TRACE CLIM $ZZCIP.N1003741, TO $DATA00.TRC1003741.CPU1, CPU 1, RECSIZE 4050

TRACE MONThe TRACE MON command starts or stops tracing of CIPMON operations on a specific processor.Each processor can have at most one trace command active at a time, but multiple processorscan be tracing simultaneously to different trace files.TRACE MON Command SyntaxTRACE MON $ZZIP.ZCMnn{,STOP | ,TO file-spec[,{BULKIO|NOBULKIO}][,COUNT count][,LOCKSIZE locksize][,NOCOLL][,PAGES pages[,RECSIZE size][,SELECT {select-option |select-option ...}][,WRAP]}

ZCMnnIdentifies the CIPMON process to trace. nn is a two-digit value in the range 00 through 15.

SELECT { select-opt | ( select-opt , ... ) }Selects the operations to be traced. Valid select options are:

All other options-1ALL

CIPMON events0EVT

CIPMON internal messages1INTMSG

CIPMON internal memory resource mgmt2MEMORY

280 SCF Reference for CIP

CIPMON messages3MSG

CIPMON internal queue operations4QUEUE

CIPSREQ operations5REQ

CIPMON state machines operations6SMACH

CIPMON timer activities7TIMER

A combination of the most useful keywords above (default)8USEFUL

Example 101 starts a trace of memory allocation and other significant operations in ZCM02 tofile TRACE1.

Example 101 TRACE MON

> TRACE MON $ZZCIP.ZCM02, TO TRACE1, SELECT (USEFUL,MEMORY), RECSIZE 4050

TRACE PROCESSThe TRACE PROCESS command starts or stops tracing of CIPMAN operations. Only one tracecommand can be active at a time.

NOTE: Set the record size for TRACE PROCESS to 200.

TRACE PROCESS Command SyntaxTRACE PROCESS $ZZCIP.ZCM{,STOP | ,BACKUP[,{BULKIO|NOBULKIO}][,COUNT count][,LOCKSIZE locksize][,NOCOLL][,PAGES pages[,RECSIZE size][,SELECT {select-option|select-option ...}][,WRAP]}

BACKUPSpecifies that the current backup CIPMAN process is to be traced. The default is to trace theprimary process. The same process continues to be traced if its primary/backup statuschanges later.

SELECT { select-opt | ( select-opt , … ) }Selects the operations to be traced. Valid select options are:

All options listed below-1ALL

CIPMAN process management/operation0PROCESS

CIP subsystem objects management1OBJECT

CLIM connection management2CLIM

QIO memory and messages operations3QIO

SPI requests processing4SPI

CLIM hardware access management5HWACCESS

Configuration Database operations6CONFIG

Miscellaneous operations (Trace, EMS, Exception)7DEBUG

Example 102 starts a trace of CIPMAN to file TRACE2.

CIPMAN SCF Commands 281

Example 102 TRACE PROCESS

> TRACE PROCESS $ZZCIP, TO TRACE2, RECSIZE 4050

TRACE PROVIDERThe TRACE PROVIDER command starts or stops tracing of CIP Library operations for thespecified PROVIDER on the processor given in the CPU attribute. Only one provider can havethe trace active on a processor at a time and a provider can be traced on all or a set of processorsat a time to separate trace files. Different providers can be traced on different processorssimultaneously.Each provider can have no more than one trace active at a time on each processor, but multipleprovider/processor combinations can be tracing simultaneously to different trace files.

NOTE: Set the record size for TRACE PROVIDER to 300.

TRACE PROVIDER Command SyntaxTRACE PROVIDER $ZZIP.ZCM.prov-name{,STOP [,CPU cpu]|,TO file-spec[,{BULKIO | NOBULKIO}][,COUNT count][,LOCKSIZE locksize][,NOCOLL][,PAGES pages[,RECSIZE size][,SELECT {select-option|select-option ...}][,WRAP]}

prov-nameIdentifies the provider to trace.

CPU cpuOptional with STOP and identifies the processor on which to stop tracing. If this option is notspecified, all processors stop tracing the provider. CPU is required with the TO option andidentifies the processor on which to start tracing the provider.

SELECT { select-opt | ( select-opt , ... ) }Selects the operations to be traced. Valid select options are:

All available options-1ALL

PROVIDER events0EVT

PROVIDER input requests1REQIN

PROVIDER output requests2REQOUT

Provider logic events3LOGIC

Provider incoming data4DATIN

Provider outgoing data5DATOUT

This command starts a trace of PROVIDER ZTC1 on processor 0 to file $DATA00.TRZTC1.CPU0.

282 SCF Reference for CIP

Example 103 TRACE PROVIDER

> TRACE PROVIDER $ZZCIP.ZTC1, TO $DATA00.TRZTC1.CPU0, CPU 0, RECSIZE 4050

VERSION CommandsVERSION is a non-sensitive command that displays version information about the CIP subsystemcomponents. Some version commands recognize the DETAIL option, which provides additionalinformation.

VERSIONThe VERSION command with no object type is identical to the “VERSION PROCESS”. You mustspecify the MAN process name.VERSION Command SyntaxVERSION $ZZCIP

VERSION CLIMThe VERSION CLIM command displays the version numbers of software components runningon the specified CLIM. The version of components provided CIP is followed by the CLIM softwareversion.VERSION CLIM Command SyntaxVERSION CLIM $ZZCIP.clim-name [,DETAIL]

clim-nameIdentifies the CLIM for which to display version information. A wildcard can specify multipleCLIMs.

DETAILSpecifies that the display is to include additional version information.

Example 104 displays the version of N1012542

Example 104 VERSION CLIM Summary, IP

> VERSION CLIM $ZZCIP.N1012542VERSION CLIM \MYHOST.$ZZCIP.N1012542: T0853H01_01NOV2008_03SEP2008

CIP SW: T0853H01_01NOV2008_24SEP2008_AABNETWORK: T0691H01_01NOV2008_AAF_CLIMSTORAGE: T0830H01_01NOV2007_24SEP2008_SYSTEM: Linux version 2.6.18-6-clim-amd64 (Debian 2.6.18.dfsg.1-18hpdeetch

1hpde1.1) (brian.haley@hp.com) (gcc version 4.1.2 20061115 (prerelease) (Debian4.1.1-21)) #1 SMP PREEMPT Thu Feb 28 01:10:30 UTC 2008

CIP SWShows the version of CIP subsystem software running on the CLIM.

NETWORKShows the version of networking software running on the CLIM.

STORAGEShows the version of storage software running on the CLIM.

SYSTEMShows the version of system software running on the CLIM.

Example 105: VERSION CLIM Detailed, IP displays the version for CLIM N1002532:

Example 105 VERSION CLIM Detailed, IP

> VERSION CLIM $ZZCIP.N1002532, DETAILDetailed VERSION CLIM \MYHOST.$ZZCIP.N1002532

CIPMAN SCF Commands 283

SYSTEM \MYHOSTT0853H01_01NOV2008_24SEP2008GUARDIAN – T9060 – (Q06)SCF KERNEL – T9082H01 – (04DEC06) (15NOV06)CIP PM – T0695H01 – (01AUG2008) (H01 SCF AAB)CIP SW: T0853H01_01NOV2008_24SEP2008_AABNETWORK: T0691H01_01NOV2008_AAF_CLIMSTORAGE: T0830H01_01NOV2008_24SEP2008_SYSTEM: Linux version 2.6.18-6-clim-amd64 (Debian 2.6.18.dfsg.1-18hpdeetch

1hpde1.1) (brian.haley@hp.com) (gcc version 4.1.2 20061115 (prerelease) (Debian4.1.1-21)) #1 SMP PREEMPT Thu Feb 28 01:10:30 UTC 2008

VERSION MONThe VERSION MON command displays the version number of the specified CIPMON process.VERSION MON Command SyntaxVERSION MON $ZZCIP.ZCMnn [,DETAIL]

ZCMnnIdentifies the CIPMON process for which to display version information. nn is a value in therange 00 through 15. A wildcard can specify multiple CIPMONs.

DETAILCauses the command to display additional information, as shown in the second example.

Example 106 displays the versions of all CIPMONs on this system:

Example 106 VERSION MON Summary

> VERSION MON $ZZCIP.*Version MON \MYSYS.$ZZCIP.ZCM00: CIPMonitor - T0694H01_01AUG08_AAB_MON_Q41Version MON \MYSYS.$ZZCIP.ZCM01: CIPMonitor - T0694H01_01AUG08_AAB_MON_Q41Version MON \MYSYS.$ZZCIP.ZCM02: CIPMonitor - T0694H01_01AUG08_AAB_MON_Q41Version MON \MYSYS.$ZZCIP.ZCM03: CIPMonitor - T0694H01_01AUG08_AAB_MON_Q41Version MON \MYSYS.$ZZCIP.ZCM04: CIPMonitor - T0694H01_01AUG08_AAB_MON_Q41Version MON \MYSYS.$ZZCIP.ZCM05: CIPMonitor - T0694H01_01AUG08_AAB_MON_Q41Version MON \MYSYS.$ZZCIP.ZCM07: CIPMonitor - T0694H01_01AUG08_AAB_MON_Q41

Example 107: VERSION MON Detailed shows MON detailed version information for CIPMONon processor 3:

Example 107 VERSION MON Detailed

> VERSION MON $ZZCIP.ZCM03, DETAILVersion PROCESS \MYSYS.$ZZCIP.ZCM03CIPMonitor - T0694H01_01AUG2008_AAB_MON_Q41GUARDIAN - T9050 - {T06)SCF KERNEL - T9082H01 - (04DEC06) )15NOV06)CIP PM - T0695H01 - (05AUG2008) (H01 SCF AAB)

VERSION PROCESSThe VERSION PROCESS command displays the version number of the CIPMAN process.VERSION PROCESS Command SyntaxVERSION PROCESS $ZZCIP [,DETAIL]

Example 108 displays the version of CIPMAN.

284 SCF Reference for CIP

Example 108 VERSION PROCESS

> VERSION PROCESS $ZZCIPT0690H01_01AUG08_AAB_MAN_Q38

CIPSAM SCF CommandsThe SCF commands for CIPSAM support the PROCESS and SUBNET objects and require thename of a CIPSAM process running on this system. The SUBNET object refers to a home CLIMinterface as seen from the NonStop host system. SUBNET object names are generated byCIPSAM and consist of “#SN” followed by a four-digit number. They are assigned to interfaceswhen the interfaces are first reported and do not change as long as the CIP subsystem continuesrunning. The INFO SUBNET command displays the CLIM and interface name referenced by aSUBNET object.Table 26 lists the SCF commands and object types supported by the CIPSAM process. The pagenumber of the command description follows the command name.

ABORT Command, CIPSAMThe only supported ABORT command for CIPSAM is ABORT PROCESS.

ABORT PROCESSThe ABORT PROCESS command for CIPSAM stops and deletes the CIPSAM processimmediately, without regard for open sockets. Open sockets using the CIPSAM process are notaffected, but no new sockets can be created.ABORT PROCESS Command SyntaxABORT PROCESS $cipsam-name

cipsam-nameIs the name of the CIPSAM process to abort.

Example 109 displays the command to abort the CIPSAM process named $ZTC1.

Example 109 ABORT PROCESS

> ABORT PROCESS $ZTC1

INFO Commands, CIPSAMThe INFO PROCESS and INFO SUBNET commands are supported for the CIPSAM process.

INFO PROCESSThe INFO PROCESS command displays attributes of the CIPSAM process. For compatibilitywith the SAM process of TCP/IPv6, attributes that do not apply to CIP are displayed with zero(0) values.INFO PROCESS Command SyntaxINFO PROCESS $cipsam-name [,DETAIL]

cipsam-nameIs the name of the CIPSAM process for which to display information.

DETAILSpecifies that the display is to include additional detailed information about the object.

Example 110 displays summary information for the CIPSAM process named $ZTC1.

CIPSAM SCF Commands 285

Example 110 INFO PROCESS (CIPSAM) Summary

> INFO PROCESS $ZTC1CIP Info PROCESS \MYSYS.$ZTC1

*TCPSendSpace *TCPReceiveSpace *UDPSendSpace *UDPReceiveSpace

0 0 0 0

Example 110 displays detailed information for the CIPSAM process named $ZTC1:

Example 111 INFO PROCESS (CIPSAM) Detailed

> INFO PROCESS $ZTC1, DETAILCIP Detailed Info PROCESS \MYSYS.$ZTC1

*TCP Send Space......... 0 *TCP Receive Space...... 0*UDP Send Space......... 0 *UDP Receive Space...... 0*Delay Ack Time......... 0 *Delay Ack.............. OFF*Keep Alive Idle........ 0 *Keep Alive Retry Cnt... 0*Keep Alive Interval.... 0 QIO Limit.............. 0%*Host ID ............... 0.0.0.0*Host Name ............. See "SCF->HELP CIP info process" to view values.Program Filename ...... \MYSYS.SYSTEM.SYS00.CIPSAM*Debug.................. OFF*Full Dump.............. OFF*All Nets Are Local..... OFF*TCP Compat 42.......... OFF*EXPAND Security........ OFF*TCP Path MTU........... OFF*TCP Time Wait.......... 0Trace Status........... OFFTrace Filename ........*ARP Timer Refreshed ... ON*RFC1323 Enable ........ OFF*TCP Init Rexmit Timeout 0 ms*TCP Min Rexmit Timeout. 0 ms*TCP Listen Queue Min... 0*Initial TTL............ 0

The only attributes with real values are:Program Filename

Is the name of the file that is being executed for this CIPSAM process.Trace Status

ON when the process is being traced using SCF.Trace Filename

Is the name of the current trace file.Trace Status

ON when the process is being traced using SCF.Trace Filename

Is the name of the current trace file.ARPTIMER-REFRESHED

Always ON in the CIP environment. This attribute causes TCP to restart the ARP timer everytime the ARP table entry is referenced when transmitting an IP packet.

Some of the other attributes are no longer viewable with the CIP info process command but canbe checked by issuing a sysctl command. Some attributes are not applicable in CIP and someare still applicable and available through the INFO PROCESS CIPSAM command.

286 SCF Reference for CIP

TCP Send Spacetacl> CLIMCMD clim-name sysctl net.ipv4.tcp_wmem. Is the space reserved forsend operations for the TCP protocol.

TCP Receive Spacetacl> CLIMCMD clim-name sysctl net.ipv4.tcp_rmem. Is the space reserved forreceive operations for the TCP protocol.

UDP Send Spacetacl> CLIMCMD clim-name sysctl net.core.wmem_max or tacl> CLIMCMDclim-name sysctl net.core.wmem_default. Is the space reserved for send operationsfor the UDP protocol.

UDP Receive Spacetacl> CLIMCMD clim-name sysctl net.ipv4.tcp_rmem or tacl> CLIMCMDclim-name sysctl net.core.rmem_default. Is the space reserved for send operationsfor the UDP protocol.

Delay AckIs a switch indicating if TCP is delaying acknowledgments. This attribute no longer appliesin the CIP environment.

Delay Ack TimeIs the amount of time in 10 ms intervals that the acknowledgments are delayed. This attributeno longer applies in the CIP environment.

Keep Alive Idletacl> CLIMCMD clim-name sysctl net.ipv4.tcp_keepalive_time. Is the amountof time in seconds before TCP issues a keep-alive packet on sockets that have enabled thisoption. See also “TCP/IP Attributes in CIP” (page 188).

Keep Alive Retry Cnttacl> CLIMCMD clim-name sysctl net.ipv4.tcp_keepalive_probes. Is thenumber of times a keep-alive packet is sent without receiving an acknowledgment after whichthe TCP connection is dropped.

Keep Alive Intervaltacl> CLIMCMD clim-name sysctl net.ipv4.tcp_keepalive_intvl. Is the timeinterval in seconds between retransmissions of unacknowledged keep-alive packets. Seealso “TCP/IP Attributes in CIP” (page 188).

QIO Limitscf> STATUS MON $ZZCIP.ZCMnn, detail. Is a percentage between 0 and 100,representing the amount of queued I/O or shared memory allowed to this process.

Host Idscf> INFO Provider $ZZCIP.provider-name, DETAIL. Is the ID (usually the hostnumber part of the Internet address that is assigned to this host). It is a 32-bit number.

Host Namescf> INFO Provider $ZZCIP.provider-name , DETAIL. Is the official name bywhich the host upon which the TCP/IP process is running is known in the Internet. This is acharacter string no longer than 50 characters.

DebugNo longer applies in the CIP environment.

Full DumpNo longer required for the CIPSAM process as there is a dump function on the CLIM.

CIPSAM SCF Commands 287

ALLNETSARELOCALNo longer applies in the CIP environment. ALLNETSARELOCAL set to ON causes TCP touse the interface MTU as a base for the determination of the TCP Maximum Segment Size(MSS) for each non-local TCP connection. A non-local TCP connection is one that goes toanother network (not just another subnetwork). The default is ON. If this switch is OFF, TCPconforms to RFC-specified behavior and uses 512 bytes as the default MSS for non-localsegments. When ON, for example for Ethernet, the non-local MSS is 1460. This can be alarge benefit to performance.

TCPCOMPAT42No longer applies in the CIP environment. TCPCOMPAT42 was the flag used to set theTCP/IP process compatible with BSD4.2 versions. See “TCPCOMPAT42” (page 197) for moreinformation about this feature.

EXPANDSECURITYNo longer applies in the CIP environment. EXPANDSECURITY set to ON caused TCP tocheck if a SOCKET request from another NonStop Expand node has passed the Expandsecurity check.

TCPPATHMTUtacl> CLIMCMD clim-name sysctl net.ipv4.ip_no_pmtu_disc. If set to ON,causes TCP to use PATH MTU discovery on all TCP type sockets (SOCK_STREAM), unlessdisabled by the SETSOCKOPT for SO_PMTU. The default for this option is OFF. See also“TCP/IP Attributes in CIP” (page 188).

RFC1323-ENABLEtacl> CLIMCMD clim-name sysctl net.ipv4.tcp_window_scaling value.Where value is:0 — disabled1 — enabled (default)If set to 1, causes TCP to support TCP Large Windows as documented in RFC 1323. Whenthis option is enabled, the TCP/IP process uses the TCP Window Scale and Timestampoptions as described in RFC 1323. The largest TCP window supported is 262144 bytes whenthis option is enabled, and 65535 when the option is disabled.

TCP-INIT-REXMIT-TIMEOUTNot supported in the CIP environment. TCP-INIT-REXMIT-TIMEOUT was the initial retransmittimer value in milliseconds to use on a TCP connection.

TCP-MIN-REXMIT-TIMEOUTNot supported in the CIP environment. TCP-MIN-REXMIT-TIMEOUT was the minimum valueallowed for the TCP retransmission timeout.

TCP-LISTEN-QUE-MINscf> INFO Provider $ZZCIP.provider-name, DETAIL. Is the minimum queue lengththat is set on a TCP socket when the TCP/IP process handles a socket LISTEN orACCEPT_NW1 function call. This value is used if the queue length specified in the socketrequest is lower, otherwise the queue length in the socket request is used. The default valueis 5. The range is 1 to 1024.

INITIAL-TTLtacl> CLIMCMD clim-name sysctl net.ipv4.ip_default_ttl. Specifies the initialvalue for UDP and TCP TTL.

INFO SUBNETThe INFO SUBNET command displays attributes of the CLIM interfaces belonging to a CIPSAMprovider in a format compatible with previous NonStop TCP/IP products. Only IPv4 addresses

288 SCF Reference for CIP

are shown. Some field names in the header are tagged with an asterisk even though they arenot alterable.INFO SUBNET Command SyntaxINFO SUBNET $cipsam-name.subnet-name [,DETAIL]

cipsam-nameIs the CIPSAM process containing the SUBNET to display.

subnet-nameIs the internally-generated SUBNET name for the CLIM interface to display. A wildcard canspecify a set of SUBNETs.

DETAILSpecifies that the display is to include additional detailed status information about the SUBNET.

Example 112 shows info for all interfaces in the Provider associated with $ZTC02.

Example 112 INFO SUBNET (CIPSAM)-> INFO SUBNET $ZTC02.*CIP Info SUBNET \MYSYS.$ZTC02.*

Name Devicename *ADDRESS TYPE *SUBNETMASK SuName QIO *R

#SN0001 LO 127.0.0.1 LOOP-BACK %HFF000000 OFF N#SN0001 N1002532.lo 127.0.0.2 LOOP-BACK %HFFFFFFFF OFF N#SN0002 N1002532.ETH1 172.17.190.101 ETHERNET %HFFFFFF00 ON N#SN0003 N1002532.ETH2 172.17.190.102 ETHERNET %HFFFFFF00 ON N#SN0004 N1002532.ETH3 172.17.190.103 ETHERNET %HFFFFFF00 ON N#SN0005 N1002532.ETH4 172.17.190.104 ETHERNET %HFFFFFF00 ON N#SN0001 N1003741.lo 127.0.1.2 LOOP-BACK %HFFFFFFFF OFF N#SN0007 N1003741.BOND0 172.17.190.81 ETHERNET %HFFFFFF00 ON N#SN0008 N1003741.BOND1 172.17.190.83 ETHERNET %HFFFFFF00 ON N

NameShows the internally-generated SUBNET name #SNnnn.

DevicenameShows the home CLIM name and interface name associated with the SUBNET, convertedto upper case.

ADDRESSShows the first known IPv4 address associated with the CLIM interface.

TYPEShows the type of interface, LOOP-BACK for interfaces named “lo” and ETHERNET for allothers.

SUBNETMASKShows the subnet-mask for the first known IPv4 address associated with the CLIM interface.

SuNameIs always blank.

QIOShows OFF for interfaces named “lo” and ON for all others.

RAlways shows N.

Example 113 detailed info for the interface identified as SUBNET #SN004 in the Provider for$ZTC2.

Example 113 INFO SUBNET Detailed

> INFO SUBNET $ZTC2.#SN004,DETAILCIP Detailed Info SUBNET \MYSYS.$ZTC2.#SN004

CIPSAM SCF Commands 289

Name Devicename *ADDRESS TYPE *SUBNETMASK SuName QIO *R

#SN004 N1002532.ETH4 172.17.190.104 ETHERNET %HFFFFFF00 ON NTrace Status ........ OFFTrace Filename ......Interface MTU ....... 1500Gateway ............. OFF

Trace StatusIs always OFF. Tracing of CLIM interfaces is set up on the CLIM.

Trace FilenameIs always blank.

Interface MTUIs the Maximum Transfer Unit (MTU) size for the interface.

GatewayIs always OFF.

StateAlways shows STARTED.

NAMES SUBNET, CIPSAMThe only supported NAMES command for CIPSAM is NAMES SUBNET.

NAMES SUBNETThe NAMES SUBNET command shows the names of the specified SUBNETs. SUBNET namesare generated by CIPSAM for all CLIM interfaces existing within the Provider.NAMES SUBNET Command SyntaxNAMES PROCESS cipsam-name.subnet-name

cipsam-nameIs the name of the CIPSAM process containing the SUBNET names to display.

subnet-nameIdentifies the SUBNET object names to display. A wildcard can specify multiple SUBNETs.

Example 114 shows names for subnet $ZTCO:

Example 114 NAMES SUBNET (CIPSAM)

> NAMES SUBNET $ZTC0.*CIP Names SUBNET \MYSYS.$ZTC0.*

SUBNET#SN0001 #SN0002 #SN0003 #SN0004 #SN0005 #SN0006 #SN0007 #SN0008

PRIMARY Command, CIPSAMThe only supported PRIMARY command for CIPSAM is PRIMARY PROCESS.

PRIMARY PROCESSThe PRIMARY PROCESS command is a sensitive command that changes which process of theCIPSAM process pair is currently the primary. This command does not affect existing sockets.PRIMARY PROCESS Command SyntaxPRIMARY PROCESS $cipsam-name [,CPU cpu-number]

cipsam-nameIs the name of the CIPSAM process to switch.

290 SCF Reference for CIP

CPU cpu-numberSpecifies the processor number of the current backup process. If you omit this option, thecurrent backup processor is assumed. If you specify a processor other than the currentprimary or backup, the command returns an error.

Example 115 switches $ZTC1 to its backup process.

Example 115 PRIMARY PROCESS (CIPSAM)

> PRIMARY PROCESS $ZTC1, CPU CPU number of backup process

STATUS Command, CIPSAMThe only supported STATUS command for CIPSAM is STATUS SUBNET.

STATUS SUBNETThe STATUS SUBNET command displays the current status of CLIM interfaces belonging to aCIPSAM’s Provider in a format compatible with previous NonStop TCP/IP products.STATUS SUBNET Command SyntaxSTATUS SUBNET [$cipsam-name][.subnet-name]

cipsam-nameIs the name of the CIPSAM process containing the SUBNET names to display.

subnet-nameIs the internally-generated SUBNET name for the CLIM interface to display. A wildcard canspecify a set of SUBNETs. The INFO SUBNET command displays the SUBNET nameassociated with each CLIM interface.

Example 112 shows the status of all SUBNETs in $CSAM2’s Provider.

Example 116 STATUS SUBNET (CIPSAM)

> STATUS SUBNET $CSAM2.*CIP Status SUBNET \MYSYS.$CSAM2.*

Name Status

#SN0001 STARTED#SN0002 STARTED#SN0003 STOPPED#SN0004 STARTED#SN0005 STARTED#SN0006 STARTED#SN0007 STARTED#SN0008 STARTED

STOP Command, CIPSAMThe only supported STOP command for CIPSAM is STOP PROCESS.

STOP PROCESSThe STOP PROCESS command stops the operation of the specified CIPSAM process if it hasno open sockets. If sockets are open, the command returns an error.STOP PROCESS Command SyntaxSTOP PROCESS $cipsam-name

cipsam-nameIs the name of the CIPSAM process to stop.

CIPSAM SCF Commands 291

Example 117 stops the CIPSAM process named $ZTC1.

Example 117 STOP PROCESS (CIPSAM)

> STOP PROCESS $ZTC1

TRACE Command, CIPSAMThe only supported TRACE command for CIPSAM is TRACE PROCESS.

TRACE PROCESSThe TRACE PROCESS command starts or stops tracing of CIPSAM operations.TRACE PROCESS Command SyntaxTRACE PROCESS $cipsam-name{{,STOP |[,BACKUP]}{,TO file-spec |[,BACKUP count]|[,LOCKSIZE]|[,NOCOLL]|[,PAGES pages]|[,RECSIZE size]|[,WRAP]}}

PROCESS $cipsam-nameIs the name of the CIPMAN process. If you omit the object name, SCF uses the assumedobject name. For information about the ASSUME command, see the SCF Reference Manualfor J-Series and H-Series RVUs.

STOPDiscontinues the trace currently in progress.

TO file-specSpecifies the name of the file into which the results of the trace operation are to be placed.It is a required option if the STOP option is not used.

BACKUPIf BACKUP is specified, the command applies to the backup CIPMAN process (that is, thetrace is stopped or started on the backup). If omitted, the primary is assumed. CIPMAN mustbe running as a fault-tolerant process pair if this syntax is used. If primary CIPMAN is beingtraced when a takeover by backup CIPMAN occurs, the trace of the same CIPMAN continues,but most events that were being traced prior to the CIPMAN switch are no longer traced. Thisis because CIPMAN being traced is no longer the primary. If neither PRIMARY nor BACKUPis designated, primary CIPMAN is traced.

COUNT countcount is an integer in the range -1 to (32k-1). It specifies the number of trace records tobe captured. If COUNT is not specified (or is specified as -1), records are accumulated untilthe trace is stopped or the file file-spec is full.

NOCOLLIndicates that the trace collector process should not be initiated. The disk file is to be writtento by Guardian. The attributes WRAP and NOCOLL cannot be specified together.

PAGES pagespages specifies how many extended data segment pages are allocated when tracing. Aninteger value in the range 4 to 64 is expected. The default is 64 pages.

292 SCF Reference for CIP

RECSIZE sizesize is an integer in the range 1024 to 4050. It controls the length of the data in the tracedata records. The trace header not included in the RECSIZE. The default is 120 bytes. Eightbytes are used for the header, and 120 bytes are trace data.

WRAPSpecifies that when the trace disk file end-of-file (EOF) is reached, trace data wraps aroundto the beginning of the file and overwrites any data that is there.

This command starts a trace of $ZTC2 to file TRACE5.

Example 118 TRACE PROCESS (CIPSAM)

> TRACE PROCESS $ZTC2, TO TRACE5, RECSIZE 4050, SELECT ALL

VERSION Command, CIPSAMThe only supported VERSION command for CIPSAM is VERSION PROCESS.

VERSION PROCESSThe VERSION PROCESS command displays the version number of the specified CIPSAMprocess.VERSION PROCESS Command SyntaxVERSION PROCESS $cipsam-name

Example 119 displays the version of the CIPSAM process named $ZTC1:

Example 119 VERSION PROCESS

> VERSION PROCESS $ZTC1$ZTC1: T0693H01_01AUG2008_AAB_SAM_Q35

CIPSAM SCF Commands 293

12 CLIMCMD and CLIMCMD climconfig Commands (ManPages)

man pages are described in these sections:

• “Standalone Commands (Man Pages)” (page 297)

• “Climconfig (Man Pages)” (page 307)These sections contain the information for the individual man pages, and can also be vieweddirectly on the CLIM. The pages listed under Standalone Commands are separate programs thatare accessible through CLIMCMD, whereas those pages in the Climconfig section are accessiblethrough CLIMCMD climconfig, as described in those sections.You can view a list of these man pages in the Table of Contents of this manual or issue the manand help commands, as described under “Linux Man Page Documentation and Help” (page 20)and “Displaying Man Pages for CIP Commands” (page 85).For the Multiple Providers per CLIM enhancement effective with the H06.25/J06.14 RVU, thereis a standalone prov(1p) command and also a prov(1) climconfig command. To display thestandalone prov(1p) man page, you would issue the man page command man 1p prov, andto display the climconfig.prov(1) man page, you would issue the man 1 prov command. Syntaxfor man pages is described in detail in the sections documenting them; for this example, seeprov(1p) and climconfig.prov(1).

294 CLIMCMD and CLIMCMD climconfig Commands (Man Pages)

13 Support and other resourcesAccessing Hewlett Packard Enterprise Support

• For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:www.hpe.com/assistance

• To access documentation and support services, go to the HP Support Center – HewlettPackard Enterprise website:www.hpe.com/support/hpesc

Information to collect• Technical support registration number (if applicable)

• Product name, model or version, and serial number

• Operating system name and version

• Firmware version

• Error messages

• Product-specific reports and logs

• Add-on products or components

• Third-party products or components

Accessing updates• Some software products provide a mechanism for accessing software updates through the

product interface. Review your product documentation to identify the recommended softwareupdate method.

• To download product updates, go to either of the following:

HP Support Center – Hewlett Packard Enterprise Get connected with updates fromHP page:www.hpe.com/support/e-updates

◦

◦ Software Depot website:www.hpe.com/support/softwaredepot

• To view and update your entitlements, and to link your contracts, Care Packs, and warrantieswith your profile, go to the HP Support Center – Hewlett Packard EnterpriseMore Informationon Access to HP Support Materials page:www.hpe.com/support/AccessToSupportMaterials

IMPORTANT: Access to some updates might require product entitlement when accessedthrough the HP Support Center – Hewlett Packard Enterprise. You must have a HewlettPackard Enterprise Passport set up with relevant entitlements.

Accessing Hewlett Packard Enterprise Support 295

Websites

LinkWebsite

www.hpe.com/info/enterprise/docsHewlett Packard Enterprise Information Library

www.hpe.com/support/hpescHP Support Center – Hewlett Packard Enterprise

www.hpe.com/assistanceContact Hewlett Packard Enterprise Worldwide

www.hpe.com/support/e-updatesSubscription Service/Support Alerts

www.hpe.com/support/softwaredepotSoftware Depot

www.hpe.com/support/selfrepairCustomer Self Repair

www.hpe.com/info/insightremotesupport/docsInsight Remote Support

www.hpe.com/info/hpux-serviceguard-docsServiceguard Solutions for HP-UX

www.hpe.com/storage/spockSingle Point of Connectivity Knowledge (SPOCK)nl

Storage compatibility matrix

www.hpe.com/storage/whitepapersStorage white papers and analyst reports

Customer self repairHewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product.If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it atyour convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorizedservice provider will determine whether a repair can be accomplished by CSR.For more information about CSR, contact your local service provider or go to the CSR website:www.hpe.com/support/selfrepair

Remote supportRemote support is available with supported devices as part of your warranty, Care Pack Service,or contractual support agreement. It provides intelligent event diagnosis, and automatic, securesubmission of hardware event notifications to Hewlett Packard Enterprise, which will initiate afast and accurate resolution based on your product’s service level. Hewlett Packard Enterprisestrongly recommends that you register your device for remote support.For more information and device support details, go to the following website:www.hpe.com/info/insightremotesupport/docs

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs. Tohelp us improve the documentation, send any errors, suggestions, or comments to DocumentationFeedback (docsfeedback@hpe.com). When submitting your feedback, include the documenttitle, part number, edition, and publication date located on the front cover of the document. Foronline help content, include the product name, product version, help edition, and publication datelocated on the legal notices page.

296 Support and other resources

Standalone Commands (Man Pages)This section contains reference pages for standalone commands. These standalone commandshave a man-page format that includes the title of the man page, represented in man page format(for example, climstatus(1).These man pages are also available on the CLIM, using the "man" command through CLIMCMDor when logged into the CLIM directly with putty.

297

clim(1)NAMEclim -- query and control the CLIM software.

SYNOPSISCLIMCMD {clim-name|ip-address} clim [option]

clim Descriptionclim provides a set of commands to query and control the CLIM software, and to display theprocess status of each of the clim processes.

PARAMETERSabort

Abort and dump all CLIM processes.clearlog

Allows a CLIM that has stopped trying to restart itself after reaching a retry threshold to beresumed. Should be followed by 'clim start'.

disable-policy-routingDisables policy routing on the next CLIM reboot.

enable-policy-routingEnables policy routing on the next CLIM reboot. This is the default configuration.

infoProvides clim configuration information. This command displays the current value/status ofconfigurable clim parameters.

onlinedebugPackages clim-related information into a compressed tar file for debugging purposes.

rebootReboots the CLIM, after taking a system memory dump.

startStarts the CLIM software.

statusDisplays the process status of the CLIM processes. The details of the CLIM processes interms of system resource consumption are displayed. This is essentially the same as executingthe psclim command at the prompt.

ERROR MESSAGESNone.

CONSIDERATIONS1. If the application restart threshold is exceeded, the 'clim start' command will output an error

message and switch from doing an application level restart to doing a CLIM reboot.If the CLIM reboot threshold is exceeded, the 'clim start' command will output an errormessage and exit without attempting to do any further application-level restarts or reboots.Once the CLIM has given up attempting to restart the CLIM, operator intervention will berequired to enable the CLIM to restart. The operator can accomplish this by using the 'climclearlog' command, which will delete the log.

EXAMPLESNone.

298

SEE ALSOpsclim(1), climstatus(1)

299

climstatus(1)NAMEclimstatus -- displays CLIM specific status information

SYNOPSISCLIMCMD {clim-name|ip-address} climstatus [-o option]

climstatus Descriptionclimstatus is a program that provides active status information about active objects on specificCLIMs: (See climconfig(1) for information on obtaining permanent configuration information.)- NonStop connectivity status- EtherNet, Local Area Network (LAN)- Kernel IP Routing Table- CLIM OS hard disks- IP Security policies and associations- Interface Failover configuration- SNMP Configuration information- climprep configuration information- iptables and ip6tables configurationclimstatus, when invoked, provides status information of all the above-mentioned componentsby default. However, a user can view status information pertaining to a particular component byproviding a -o option to the climstatus command, followed by a character that represents thedesired component. The set of characters representing each component is listed underParameters.

PARAMETERSThis section lists the options that can be used after the -o option.c

Displays climprep information.f

Displays interface failover information.h

Displays the information pertaining to Filesystem Disk space usage on the CLIM. Displaysinformation specific to the Filesystem disk space and usage status, such as name, type, size,used and available amount of space, percentage of used space, and the mount point.

iDisplays the information pertaining to the IPSec, such as security policies and associations.

lDisplays the status information pertaining to Local Area Network (EtherNet) only. Displaysinformation specific to the Network such as the Interface name, type, status, link status, andIP addresses(both IPv4 and IPv6). The LAN information is categorized into three separateclasses: Maintenance, Maintenance Provider and Data. The interface "eth0" is the onboardinterface that has been reserved as the Maintenance interface and is used for clim internalhousekeeping activities. The other interfaces are open for normal Data usage.

mDisplays CLIM SNMP information.

300

rDisplays the status information pertaining to Kernel IP Routing Table. Displays informationspecific to the Kernel IPv4 routing table such as the Interface name, Destination IP address,Gateway, and Mask. In case of the Kernel IPv6 routing table, only Interface name, DestinationIP address, and Next Hop information is displayed.

sFor all CLIM types, this displays the CLIM mode, CLIM state, CLIM software start time, CLIMhostname, and CLIM software versions. For H- and J-series CLIMs, this also displays CLIMlocation and CLIM fabric status. CLIM fabric status is not shown by this option on NonStopX CLIMs; that information is available on NonStop X using the SCF STATUS CLIM command,as shown under Example 78: STATUS CLIM Summary, NonStop X.

tDisplays iptables and ip6tables information.

ERROR MESSAGESNone.

CONSIDERATIONSNone.

EXAMPLESNone.

SEE ALSONone.

301

ifstart(1)NAMEifstart -- start an interface

SYNOPSISCLIMCMD {clim-name|ip-address} ifstart interface

ifstart Descriptionifstart allows you to activate an interface if you have stopped the interface using the ifstopcommand. For all network interfaces (ethernet, ip-over-infiniband, bonding and tunnel interfaces),this command activates the specified interface.

PARAMETERSinterface

Specifies the name of the network interface that is to be started and made available to theNonStop host. The interface name can be specified as a physical or bonded interface name,for example, eth1 or bond0 or ib0, or a tunnel interface (for example, MYTUN).

ERROR MESSAGESThe interface interface-name is not configured.This command is not supported for this interface.climagt process is not executing.Interface is already in started state.

CONSIDERATIONSNone.

EXAMPLES> CLIMCMD N1002581 ifstart eth3

SEE ALSOIfstop(1), climconfig(1)

302

ifstop(1)NAMEifstop -- stop an interface

SYNOPSISCLIMCMD {clim-name|ip-address} ifstop interface [-force]

ifstop DescriptionUse the ifstop command to deactivate an interface. ifstop brings down the ethernet,ip-over-infiniband, bonding and tunnel interfaces and deactivates all the IP addresses and routesassociated with the network interface.

PARAMETERSinterface

Specifies the name of the network interface that is to be stopped and made unavailable tothe NonStop host. The interface name can be specified as a physical or bonded interfacename, for example, eth1 or bond0 or ib0, or a tunnel interface (for example, MYTUN).

-forceWhen used without –force option, ifstop prompts for confirmation before stopping the interface.If the –force option is used, ifstop stops the interface without prompting for the confirmation.

ERROR MESSAGESThe interface interface-name is not configured.This command is not supported for this interface.climagt process is not executing.Interface is in already in stopped state.The interface interface-name has a tunnel interface associated with it. The tunnel interfaceshould be stopped prior to stopping the specified interface.

CONSIDERATIONSIf there is a tunnel associated with the specified interface, and if the tunnel interface is UP, CIPdoes not allow the interface to be stopped.The tunnel interface must be stopped before its parent interface can be stopped.

EXAMPLES> CLIMCMD N1002581 ifstop eth3

SEE ALSOIfstart(1), climconfig(1)

303

prov(1p)NAMEprov -- execute a program under the context of a provider’s network stack

SYNOPSISCLIMCMD {clim-name|ip-address} prov {prov-name} {command}[arg1..argN]

prov DescriptionCLIMs utilize multiple independent network stacks, or “providers.” At any time, a CLIM can havesome of the following providers:%DEFAULT

The reserved network stack that is used for all data communications on CLIMs configuredin SCF with the MULTIPROV attribute set to OFF.

%MPROVA reserved network stack used to service the optional maintenance provider configurable onthe preconfigured SCF CLIM object.

%MAINTA reserved network stack used to host CLIM manageability processes that provide servicesto the preconfigured maintenance LAN.

provNameProvider objects registered with the “climconfig prov –add prov-name” command, on CLIMsconfigured in SCF with the MULTIPROV attribute set to ON.

PARAMETERSprov-name

Provider name.command

The command to be executed in the provider specified by prov-name.arg1..argN

Optional arguments to the command.

ERROR MESSAGESThe specified provider does not exist.

CONSIDERATIONSWhen logged into an interactive shell on the CLIM, commands that are network-sensitive willuse the services of the currently active provider, and so only have access to the networkconfiguration and devices that are in use by that provider.To select a different provider, the command must instead be run using the prov command, whichruns the program under the network stack context of the selected provider.Commands that are invoked from NSK, through CLIMCMD, allow the provider to be selected inCLIMCMD syntax, and do not require the “prov” command to be invoked.Only programs that utilize the network stack require the prov command to be used. Theseprograms include:- arp- ethtool- hplog

304

- ifconfig- ip addr show- ip route show- ip link show- mii-tool- netstat- ping- ping6- tcpdump- traceroute- traceroute6

EXAMPLES> CLIMCMD N1002581 prov zct1 ping 10.1.1.1> CLIMCMD N1002581 prov zsam traceroute 10.3.3.1> CLIMCMD N1002581 prov csam ethtool –i eth1

SEE ALSOclimconfig.prov(1), traceroute(1), ping(8), ethtool(8)

305

psclim(1)NAMEpsclim -- display the status of the CLIM processes

SYNOPSISCLIMCMD {clim-name|ip-address} psclim

psclim Descriptionpsclim is a derivation of the 'ps' command. It displays system information about the CLIMprocesses. The CLIM processes consist of climmon, confsync, climagt and one or more cipssrvand MEU (on L-series RVUs). The information being displayed consists of process PID, memoryused, percentage memory, percentage CPU time, accumulated CPU time, start time, run status,and start command.

PARAMETERSNone

ERROR MESSAGESNone

CONSIDERATIONSNone.

EXAMPLESCLIMCMD N1002581:~#psclimPID RSS %MEM %CPU TIME START STAT CMD6554 1648 0.0 0.0 00:00:00 14:56 S /usr/local/bin/climmon6555 2416 0.0 0.0 00:00:00 14:56 S cipssrv --number 06570 1174 0.0 0.0 00:00:00 14:56 S confsync6575 2192 0.0 0.2 00:00:00 14:56 S climagt --number 1

On storage CLIMs where the MEU runs, psclim will also include the MEU process:SCLIM000(%DEFAULT):~# psclimPID RSS %MEM %CPU TIME START STAT CMD4494 1060 0.0 0.0 00:00:12 Aug 5 Sl /usr/local/bin/climmon --time 1204513 1320 0.0 0.0 00:00:07 Aug 5 Sl confsync4514 4796 0.1 0.0 00:02:04 Aug 5 Sl cipssrv --number 04515 15392 0.3 0.3 00:14:14 Aug 5 Sl climagt --number 14530 25896 0.6 0.2 00:11:33 Aug 5 Sl meu

SEE ALSOps(1, clim(1), climstatus(1)

306

Climconfig (Man Pages)This section contains reference pages for the climconfig command. Climconfig commands havea man-page format that includes the title of the man page, represented in man page format (forexample, climconfig.arp(1).These man pages are also available on the CLIM, using the "man" command through CLIMCMDor when logged into the CLIM directly with putty.

307

climconfig(1)NAMEclimconfig -- configure network protocol parameters

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig command [parameter]

climconfig DescriptionThis command is a parameter to the CLIMCMD command-line interface. It allows you to configurenetwork, IPSec, climiptables, iptables, ip6tables, failover and SNMP parameters. Enter CLIMCMDat the TACL prompt on the NonStop system followed by the clim-name or CLIM IP address,climconfig and one or more command objects and associated parameters.

COMMANDSclimconfig supports the network configuration commands documented in this section.

ERROR MESSAGESNone.

EXAMPLES> CLIMCMD N1002581 climconfig arp -add eth1 -host 17.24.17.50 &-hwaddress 00:0E:7f:F5:6E:8A

SEE ALSOFor details about the climconfig command arguments, see the following man pages:CLIMCMD {clim-name|ip-address} man climconfig.all

CLIMCMD {clim-name|ip-address} man climconfig.arp

CLIMCMD {clim-name|ip-address} man climconfig.bondmode

CLIMCMD {clim-name|ip-address} man climconfig.climiptables

CLIMCMD {clim-name|ip-address} man climconfig.failover

CLIMCMD {clim-name|ip-address} man climconfig.hostname

CLIMCMD {clim-name|ip-address} man climconfig.interface

CLIMCMD {clim-name|ip-address} man climconfig.ip

CLIMCMD {clim-name|ip-address} man climconfig.ip6tables

CLIMCMD {clim-name|ip-address} man climconfig.iptables

CLIMCMD {clim-name|ip-address} man climconfig.prov

CLIMCMD {clim-name|ip-address} man climconfig.psk

CLIMCMD {clim-name|ip-address} man climconfig.remote

CLIMCMD {clim-name|ip-address} man climconfig.route

CLIMCMD {clim-name|ip-address} man climconfig.sa

CLIMCMD {clim-name|ip-address} man climconfig.slaveinterface

CLIMCMD {clim-name|ip-address} man climconfig.snmp

CLIMCMD {clim-name|ip-address} man climconfig.sp

CLIMCMD {clim-name|ip-address} man climconfig.sysctl

CLIMCMD {clim-name|ip-address} man climconfig.tunnel

CLIMCMD {clim-name|ip-address} man climconfig.vpn

308

climconfig.all(1)NAMEclimconfig.all -- display the entire CLIM configuration

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig all -info [-obeyform]

climconfig.all DescriptionThis command displays the entire CLIM configuration.

PARAMETERS–info

Displays the cumulative output of these commands:climconfig interface –info allclimconfig route –info allclimconfig arp –infoclimconfig snmp –infoclimconfig bondmode –infoclimconfig failover –infoclimconfig sysctl –info allclimconfig psk –infoclimconfig sp –infoclimconfig sa –infoclimconfig remote –infoclimconfig climiptables –infoclimconfig prov –info

–info —obeyformDisplays the cumulative output of these commands followed by the “exit” command:climconfig interface –info all -obeyformclimconfig snmp –info -obeyformclimconfig bondmode –info -obeyformclimconfig failover -info –obeyformclimconfig sysctl –info all -obeyformclimconfig psk -info -obeyformclimconfig sp -info -obeyformclimconfig sa -info -obeyformclimconfig remote -info -obeyformclimconfig climiptables -info -obeyformclimconfig prov –info -obeyform

ERROR MESSAGESNone.

EXAMPLES> CLIMCMD n100253 climconfig all –info

> CLIMCMD n100253 climconfig all –info —obeyform

309

climconfig.arp(1)NAMEclimconfig.arp -- manage arp entries

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig arp -add{eth0|interface} -host host -hwaddress MAC-address

CLIMCMD {clim-name|ip-address} climconfig arp -delete{eth0|interface} -host host

CLIMCMD {clim-name|ip-address} climconfig arp -info[-obeyform]

climconfig.arp DescriptionThis command:arp -add

adds information about ARP entries.arp -delete

deletes manually-added ARP entries.arp -info

displays manually-added and kernel-added ARP entries.The arp -add and arp -delete commands add to or delete from the /etc/network/interfaces file and if the interface is active, to the kernel. If the interface is not active, the addand delete commands affect only the /etc/network/interfaces file. The arp -infocommand displays information about ARP entries in the kernel (includes both manually-addedand automatically-added entries). Entries that are automatically added by the Kernel cannot bedeleted using this command. This command does not support InfiniBand interfaces.

PARAMETERSeth0

Specifies the dedicated service LAN interface.interface

Specifies an interface to configure. The interface can be either an existing physical interfacename (for example, eth2) or a bonding interface name (for example, bond0).

-host hostSpecifies the host. Use the host IP address for this parameter.

-hwaddress MAC-addressSpecifies the MAC address of the host.

-delete eth0Specifies the dedicated service LAN interface.

-delete interfaceSpecifies an interface (physical or bonding).

-infoDisplays information about ARP entries.

-obeyformGenerates user-configured ARP entries.

ERROR MESSAGESFor arp -add and arp -delete:

310

The interface interface-name is not configured.This command is not supported for the interface lo.This command is not supported for the interface eth0:0.This command is not supported for the interface tunnel-interface.The specified arp entry already exists for the interface-name.This command does not support InfiniBand interfaces.

EXAMPLES> CLIMCMD N1002581 climconfig arp -add eth1 –host 10.1.219.4–hwaddress 00:0E:7f:F5:6E:8A> CLIMCMD 17.21.201.2 climconfig arp -delete eth1–host 10.1.219.4> CLIMCMD n100253 climconfig arp -infoInterface : eth0IP Address : 10.1.199.1Hardware Address : 00:01:30:10:E6:50Hardware Type : etherFlags : CMask :

> CLIMCMD n100253 climconfig arp -info -obeyformclimconfig arp \

-add eth0 \-host 192.168.36.11 \-hwaddress 00:1c:c4:de:cf:ae

climconfig arp \-add eth0 \-host 10.1.232.113 \-hwaddress 00:1b:78:07:69:70

climconfig arp \-add eth0 \-host 10.1.232.1 \-hwaddress 00:19:bb:1c:0c:00

#CLIMCMD expects 'exit' to be the last command.#This is required to terminate CLIMCMD session.exitTermination Info: 0

311

climconfig.bondmode(1)NAMEclimconfig.bondmode -- change bonding mode, get bondmode info

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig bondmode-modify bonding-mode

CLIMCMD {clim-name|ip-address} climconfig bondmode-info [-obeyform]

climconfig.bondmode DescriptionThis command displays information about the bonding mode. The bonding mode applies to allthe bonding interfaces in the CLIM. Only one slave in the bond is active.The supported bonding modes are:mode=1 (active-backup)

Active-backup policy: Only one slave in the bond is active. A different slave becomes activeif, and only if, the active slave fails. The bond's MAC address is externally visible on only oneport (network adapter) to avoid confusing the switch. This mode provides fault tolerance. Theprimary option, specified in the climconfig slave interface command, affects the behavior ofthis mode.

mode=5 (balance-tlb)Adaptive transmit load balancing: channel bonding that does not require any special switchsupport. The outgoing traffic is distributed according to the current load (computed relativeto the speed) on each slave. Incoming traffic is received by the current slave. If the receivingslave fails, another slave takes over the MAC address of the failed receiving slave.

mode=6 (balance-alb)Adaptive load balancing: includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic,and does not require any special switch support. The receive load balancing is achieved byARP negotiation. The bonding driver intercepts the ARP Replies sent by the local system ontheir way out and overwrites the source hardware address with the unique hardware addressof one of the slaves in the bond such that different peers use different hardware addressesfor the server.

A different slave becomes active if the active slave fails. The bond MAC address is externallyvisible on only one network interface to avoid problems in the switch. This mode provides faulttolerance.Configuring the bonding mode applies to both bond interfaces, bond0 and bond1. Even if thosebonds are assigned to different providers on CLIMs with MULTIPROV ON, the bonding modestill applies to both.

PARAMETERS–modify bonding-mode

Specifies the bonding mode to be applied to all the bonding interfaces–info

Displays the configured bonding mode. The display format is:Bonding Mode : 1 ( active-backup )

–obeyformGenerates the configured bonding mode information in modify command format. The displayformat is:climconfig bondmode -modify bonding-mode

312

ERROR MESSAGESFor bondmode -modify, one or more of the Bonding interfaces is UPThe value of the bonding mode should be either 1, 5, or 6The software MAC address of the slaves slave interface and slave interface of bondinginterface bonding interface cannot be same for bonding mode mode.

EXAMPLES> CLIMCMD n100253 climconfig bondmode –info

Bonding Mode : 1 ( active-backup )

> CLIMCMD n100253 climconfig bondmode –info -obeyformclimconfig bondmode -modify 1

#CLIMCMD expects 'exit' to be the last command.#This is required to terminate CLIMCMD session.exitTermination Info: 0

313

climconfig.climiptables(1)NAMEclimconfig.climiptables -- configure climiptables

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig climiptables[-prov prov-name] -enable

CLIMCMD {clim-name|ip-address} climconfig climiptables[-prov prov-name] -disable [-force]

CLIMCMD {clim-name|ip-address} climconfig climiptables[-prov prov-name] -info [-obeyform]

CLIMCMD {clim-name|ip-address} climconfig climiptables[-prov prov-name] -status

climconfig.climiptables DescriptionThis command allows you to display and configure CLIM IP tables:climiptables -enable

activates configurations for the climiptables. Enable and disable states are persistent throughCLIM reboots and software updates.

climiptables -disabledeactivates configurations for the climiptables. Enable and disable states are persistentthrough CLIM reboots and software updates.

climiptables -infodisplays the state of the climiptables, iptables and ip6tables configurations.

climiptables -info -obeyformobtains the obeyform lines for configuring climiptables in add/delete command format.

climiptables -statusdisplays the state of the climiptables.

PARAMETERS-force

Used with the -disable option, causes the command to bypass user confirmation.-prov

Specifies a provider name. This option is mandatory for CLIMs that have MULTIPROV setto ON and cannot be used if MULTIPROV is set to OFF. Each provider has its own iptablesconfiguration. The provider name is case-insensitive and always converted to UPPER case.

-obeyformUsed with the -info option, obtains climiptables configuration in obeyform format.

ERROR MESSAGESFor climconfig climiptables [-enable | -disable [-force] | -info[-obeyform]]:Error: File /etc/clim/climiptables/state does not exist.Error: Cannot open the file /etc/clim/climiptables/state: error code.Error: invalid version string “version”, file “/etc/clim/climiptables/state”.Error: version string major, minor is not compatible, file “/etc/clim/climiptables/state”.Error: Invalid climiptables state file.

314

CONSIDERATIONSNone.

EXAMPLESTo enable climiptables:> CLIMCMD N1002581 climconfig climiptables -enable -force -prov MSC2

climiptables is now enabled> CLIMCMD N1002581 climconfig climiptables -disable -force -prov MSC2

Do you want to continue with DISABLING climiptables? yes/[no] - yesclimiptables is now disabled> CLIMCMD N1002581 climconfig climiptables -force -disable

climiptables is now disabled> CLIMCMD N1002581 climconfig climiptables -status

climiptables is currently enabled> CLIMCMD N1002581 climconfig climiptables -info

climiptables is currently enablediptables configuration:-N snmptrap-A CIP_INPUT -p tcp -m tcp --dport 162 -j snmptrap-A CIP_INPUT -p udp -m udp --dport 162 -j snmptrap-A snmptrap ! -s 100.100.100.56/32 -jREJECT --reject-with icmp-port-unreachable

ip6tables configuration:-P CIP_INPUT DROP

> CLIMCMD N1002581 climconfig climiptables -info -obeyform

climconfig climiptables -disable -forceclimconfig iptables -force -N abcclimconfig iptables -force -P CIP_INPUT ACCEPTclimconfig iptables -force -A abc -p tcp -j ACCEPTclimconfig ip6tables -force -P CIP_INPUT DROPclimconfig climiptables -enable#CLIMCMD expects 'exit' to be the last command.#This is required to terminate CLIMCMD session.exitTermination Info: 0

SEE ALSOclimconfig iptables, ip6tables

315

climconfig.failover(1)NAMEclimconfig.failover -- configure failover

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig failover -add src-interface-dest dest-clim-name.dest-interface[-autofo cip|dir]

CLIMCMD {clim-name|ip-address} climconfig failover -delete{src-interface|all} [-force]

CLIMCMD {clim-name|ip-address} climconfig failover -infoclim-name -interface {interface-name|all}[-obeyform]

climconfig.failover DescriptionThis command allows you to configure the failover behavior between CLIMs. You can configureboth physical and bonding interfaces to failover to an interface on a different CLIM.failover -add

adds a failover configuration to the failover.conf file. The command must be run for theCLIM that contains the src-interface for which the failover configuration is to be added.

failover -deletedeletes the failover configuration for the specified interface. The command must be run forthe CLIM that contains the src-interface with the failover configuration that is to bedeleted.

failover -infodisplays the failover configuration of the specified interface. This command can be run forany CLIM.

PARAMETERSsrc-interface

Specifies the native interface name. It can be a physical (Ethernet or InfiniBand) or bondinginterface.

dest-clim-nameSpecifies the destination CLIM.

dest-interfaceSpecifies the destination interface. The specified interface can be a physical interface (Ethernetor InfiniBand) or a bonding interface.

-allDeletes all of the failover configurations for the native CLIM.

clim-nameSpecifies the CLIM containing the interface whose failover configuration is to be displayed.

-climIs the interface containing the failover configuration to display. If you specify interface-namethe output is only one line.

interface-nameSpecifies the interface for the failover configuration. For the -info command, the display formatis: clim-name.interface-name.failover clim name.failover-interface

allSpecifies all failover configurations for the CLIM. The display format is:clim-name.interface-name failover-clim-name.failover-interface-name

316

-forceRuns the command without prompting for confirmation.

-obeyformGenerates failover configuration information in add command format.

-autofoInterface failover attribute. The options are as follows:• cip – If the primary interface goes down, the interface failover is initiated by CIP.

• partner – If the primary interface goes down, the interface failover is externally directedby NonStop partner process.

By default the automatic interface failover attribute is set to cip.

ERROR MESSAGESFor failover -add:

Invalid source interface.Invalid destination interface, it should be one of the eth[1-n], bond[0-n], or ib[0-n].Source and Destination CLIM name are same.Failover configuration for the source interface exists.The specified destination already exists.An Ethernet interface can failover only to another Ethernet interface. The dest-interfaceis not an Ethernet interface.An InfiniBand interface can failover only to another InfiniBand interface. The dest-interfaceis not an InfiniBand interface.The option “-autofo” is supported only for OPEN CLIMs.Failover configuration for the source interface does not exist.

For failover -delete:Failover configuration for the source interface does not exist.

For failover -info:The CLIM clim-name does not exist.The interface interface-name does not exist.

CONSIDERATIONSFailover of virtual interfaces is not supported.Failover configuration for a tunnel interface is not supported. Tunnel interfaces are automaticallyfailed over along with the parent physical or bonding interface.There cannot be multiple failover configurations for a source interface.Both of the interfaces in the failover pair must be configured as part of the same provider.lo, eth0, and eth0:0 cannot be configured to fail over.To achieve a failover configuration, two interfaces are associated as a failover pair.Each interface can be paired with no more than one other interface and each interface of a pairmust use either the other as its failover interface or no failover interface.At the time of configuration, the climconfig tool does not validate whether the failover configurationsfollow failover pairs. The host validates the configuration when the CLIM is STARTED.At the time of configuration, the climconfig tool does not validate whether the destination CLIMand destination interface exist and are part of the same provider. The NonStop server host doesthis validation when the CLIM is STARTED.-autofo option is supported only for OPEN CLIMs.

317

Both the interfaces in the failover pair must be configured with the identical failover attribute.If src-interface is Ethernet, then the dest-interface> should also be Ethernet.If src-interface is InfiniBand, then the dest-interface should also be InfiniBand.Only CLIM interfaces of the same type can be paired. Ethernet and InfiniBand interface pairingis invalid.For Example, Ethernet interfaces can be paired with only Ethernet interfaces and InfiniBand withonly InfiniBand interfaces.

EXAMPLES> CLIMCMD N1002581 climconfig failover -add eth1 -dest N1002582.eth1 -autofo partner (for open clims)

CLIMCMD N1002581 climconfig failover -add eth1 -dest N1002582.eth1 -autofo cip (for IP clims. You can even omit-autofo cip)

> CLIMCMD 192.168.37.81 climconfig failover -delete eth1

> CLIMCMD n100253 climconfig failover -info n100253 -interface eth1 -obeyformclimconfig failover \

-add eth1 \-dest n100254.eth2-autofo dir

#CLIMCMD expects 'exit' to be the last command.#This is required to terminate CLIMCMD session.exitTermination Info: 0

SEE ALSOclimconfig interface -add

318

climconfig.hostname(1)NAMEclimconfig.hostname -- manage the CLIM host name

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig hostname -modify hostname

CLIMCMD {clim-name|ip-address} climconfig hostname -info

climconfig.hostname DescriptionThis command modifies and displays the host name of the CLIM.

PARAMETERS–modify

Changes the host name of the specified CLIM.–info

Displays the host name of the specified CLIM.hostname

Specifies the host name to be modified. The hostname is converted to upper case.

ERROR MESSAGESNone

CONSIDERATIONSThe host name of a CLIM cannot be modified when the CLIM is in the STARTED state.The CLIM host name and the SCF CLIM object name must match. If you change the CLIM hostname, you also need to change the name of the CLIM in the host. Use SCF to delete the CLIMand then add a new CLIM with a name that matches the new host name you have assigned tothe CLIM.Hostname cannot exceed 8 characters.If there are any failover configurations existing for the CLIM for which you change the hostname,the climconfig tool automatically changes the source-CLIM name in its failover configurations.If the interfaces of the other CLIM are configured to fail over to this CLIM, manually change thefailover configurations of the other CLIMs.

EXAMPLES> CLIMCMD 172.18.105.17 climconfig hostname -infoN1002581> CLIMCMD 172.18.105.17 climconfig hostname -modify N100253

SEE ALSOSCF DELETE CLIM command, SCF ADD CLIM command

319

climconfig.hosts(1)NAMEclimconfig.hosts -- is used to allow IP address and host name pairs to be configured for localname resolution. The DNS resolver queries hosts list before resolving name queries throughexternal nameservers.

SYNOPSIShosts —add command:hosts -add ip address [-prov provider name]

-host hostname 1 [.... hostname N]

hosts —delete command:hosts -delete ip address [-prov provider name]

-host (all | hostname 1 [...., hostname N]) [-force]

hosts –info command:hosts -info [all | -prov (provider name] [-obeyform]

DESCRIPTIONThis command does the following:hosts –add

This command adds the mapping between an IP address and the list of host names into theprovider specific hosts configuration. The host names get added to the hosts configuration in thesame order as they are specified with –host option. If the IP address is already known, thespecified host names are added at the end of the list for that IP address.hosts –delete

This command deletes the specified list of host names from the provider specific hostsconfiguration.hosts –info

This command displays the existing hosts configuration either for a particular provider or for allthe providers existing on the CLIM. It displays only those entries which have been manuallyconfigured by the user.

PARAMETERSFor hosts —add:

-addThis option is for specifying the IPv4 or IPv6 address for which the host name mapping is to beadded.-provThis option is for specifying the name of the provider for which the IP address and host namemapping is to be added. This option must be specified if SCF MULTIPROV attribute for the CLIMis set to ON. If SCF MULTIPROV attribute is set to OFF, this option defaults to %DEFAULT.-hostThis option is for specifying the host names which are be mapped to the IP address specifiedwith -add option.For hosts –delete:

-deleteThis option is for specifying the IPv4 or IPv6 address for which the mapped host names are tobe deleted.-prov

320

This option is for specifying the name of the provider for which the mapped host names are tobe deleted. This option must be specified if SCF MULTIPROV attribute for the CLIM is set to ON.If SCF MULTIPROV attribute is set to OFF, this option defaults to %DEFAULT.-hostThis option is for specifying the mapped host names which are to be deleted. If all is specifiedthen the entire list of mapped host names is deleted from the hosts configuration.-forceIf this command is used without –force option, will ask the users confirmation before deleting thehosts configuration. If -force option is used, it will delete without prompting for the confirmation.For hosts –info:

-provThis option is for specifying the name of the provider for which the hosts configuration needs tobe displayed.-obeyformThis option displays hosts configuration information in the format of climconfig add commands.

ERROR MESSAGESFor hosts –add:

The specified IP address <IP address> is invalid.The maintenance LAN IP address cannot be mapped one or more host names.The specified host name <host name> is already configured.The specified host name “all” is invalid.The provider <provider name> is not configured.For hosts –delete:

The specified IP address <IP address> is invalid.The specified IP address <IP address> is not configured.The provider <provider name> is not configured.The specified host name <host name> is not configured.For hosts –info:

The provider provider name is not configured.The hosts configuration does not exist for the specified provider provider name.The hosts configuration does not exist for any of the providers.

CONSIDERATIONSIt is not permitted to map maintenance LAN IP address and maintenance provider IP address toone or more host names.

EXAMPLESFor hosts –add:

> CLIMCMD N1002571 climconfig hosts -add 15.282.17.1 -prov ztc0 -hostwebserver.example.com ftp.example.com

> CLIMCMD N1002571 climconfig hosts -add 15.282.17.2 -prov ztc1 -hostftp.example.com

For hosts –delete:

> CLIMCMD N1002571 climconfig hosts -delete 15.282.17.1 -prov ztc0 -hostftp.example.com

321

> CLIMCMD N1002571 climconfig hosts -delete 15.282.17.1 -prov ztc0 -hostftp.example.com webserver.example.com

For hosts –info:

> CLIMCMD N1002571 climconfig hosts –info all

> CLIMCMD N1002571 climconfig hosts –info –prov ZTC0

> CLIMCMD N1002571 climconfig hosts –info

> CLIMCMD N1002571 climconfig hosts –info all -obeyform

SEE ALSOclimconfig.resolver (1)

322

climconfig.interface(1)NAMEclimconfig.interface -- manage CLIM interfaces

SYNOPSISinterface -add command:CLIMCMD {clim-name|ip-address} climconfig interface -add{eth0:0|interface-name} [-prov prov-name] [-mtu mtu-value |-jumbo { on | off } ]

interface -delete command:CLIMCMD {clim-name|ip-address} climconfig interface -delete{eth0:0|interface-name}

interface -modify command for eth0 interface:CLIMCMD {clim-name|ip-address} climconfig interface -modifyeth0{ [-ipaddress ipv4-address -netmask ipv4-netmask] |[-autonegotiation on] |[-autonegotiation on -linespeed 1000 [-duplex full ] ] |[-autonegotiation { on | off } -linespeed {10 | 100} -duplex { half | full } ]}[-force]

interface -modify command for data interfaces:CLIMCMD {clim-name|ip-address} climconfig interface -modifyinterface-name{ [-mtu mtu-value] |[-jumbo { on | off } ] |[-autonegotiation on] |[-autonegotiation on -linespeed 1000 -duplex full]] |[-autonegotiation { on | off } -linespeed { 10 | 100 } -duplex { half | full } ] |[-macaddr {mac address | default} ]}[-force]

For changing the eth0 IP address:CLIMCMD {clim-name|ip-address} climconfig interface -modifyeth0 -ipaddress ipv4-address -netmask ipv4-netmask

For changing MTU settings:CLIMCMD {clim-name|ip-address} climconfig interface -modifyinterface-name -mtu mtu-value

For changing jumbo frame settings:CLIMCMD {clim-name|ip-address} climconfig interface -modifyinterface-name -jumbo { on | off }

For changing Ethernet card settings:CLIMCMD {clim-name | ip-address} climconfig interface -modifyinterface-name [ –force ]{[ -autonegotiation on ] |[ -autonegotiation on -linespeed 1000 [ –duplex full ] ] |[ -autonegotiation { on | off } –linespeed { 10 | 100 }-duplex { half | full } ] }

For changing the MAC address for physical and slave interfaces:CLIMCMD {clim-name|ip-address} climconfig interface -modifyinterface-name -macaddr {mac-address|default} [-force]

For displaying the configuration of an interface:CLIMCMD {clim-name|ip-address} climconfig interface -info{eth0|eth0:0|interface-name|all}[–obeyform]

323

climconfig.interface DescriptionThis command does the following:interface -add

adds the interface name to the /etc/network/interfaces file of the CLIM. The hostbrings up the interface when it is added.If the CLIM has MULTIPROV ON and the operator specifies the -prov command with thename of an unconfigured prov object, that object is implicitly added. Thus, for an unknownprovider, you can specify climconfig interface -add interface-name -provprov-name, which would be the equivalent of issuing the two commands, climconfigprov -add prov-name and climconfig interface -add interface-name -provprov-name.The interface can be added even when the CLIM is in the STARTED state.Slave interfaces can be added by using the slaveinterface –configure command. Ifa bonding interface does not have any slave interfaces, it is not activated by the host.

interface -deleteremoves the configured physical or bonding interface and its configuration (all the IP addressesand routes associated with the interface) from the /etc/network/interfaces file of CLIM.

interface -modifychanges the existing interface configuration in the CLIM /etc/network/interfaces file.For eth0, its IP address or MAC address settings can be modified. For modifying parametersof any option, only the modified parameter can be specified and other unmodified parametersneed not be specified. You can modify the jumbo setting, IP address, mtu, autonegotiationsettings, and MAC address individually, but not all on the same command. If an option doesnot exist, the new option and its parameter can be added. However, you cannot delete apreviously configured option. This command does not support InfiniBand interfaces.

interface -infodisplays the configuration of an interface. For a given interface, the IP address, netmask,gateway, minimum TCP Retransmission Timeout (RTO) value (in milliseconds), and otherinformation, are displayed. An interface can have both IPv4 and IPv6 addresses; in this case,the command displays both of the configuration details for the interface. The commanddisplays the configurations only for an interface existing in the /etc/network/interfacesfile. To display the configurations for an interface existing in the kernel, use the ifconfigcommand.

PARAMETERSeth0

Specifies the dedicated service LAN interface.eth0:0

Specifies the maintenance Provider LAN interface.interface

Refers to the physical (Ethernet or InfiniBand interface) or logical (software abstraction suchas bond or tunnel) interfaces on the CLIM.

interface-nameSpecifies the interface for the operation. For the -macaddr option, the interface, includingslave interfaces must be physical interfaces. For other options, the interface can be either aphysical interface (for example, eth1, ib0) or a bonding interface (for example, bond0).

-ipaddress ipaddressSpecifies an IPv4 address.

324

-provSpecifies a provider name. This option is mandatory for CLIMs that have MULTIPROV setto ON and cannot be used if MULTIPROV is set to OFF. Each provider has its own interfaceconfiguration. The provider name is case-insensitive and always converted to UPPER case.

-netmask netmaskSpecifies an IPv4 network address in dotted quad form.

allDisplays information for all interfaces.

-obeyformThis option displays the user-configured resources of an interface in add command format.

-mtuSets frame size for an interface. If the option is not specified, the default frame size is 1500.For physical and bonding interface allowable values are 1280 to 9000.For tunnel interfaces allowable values are 1280 to 65508.If the mtu option is set for bonding interface, it will also be applied to a slave interface.Setting mtu option separately for a slave interface is not allowed.You cannot specify both the jumbo and mtu options.mtu cannot be specified for eth0, eth0:0, and InfiniBand interfaces.Specifying mtu overrides previous values set for jumbo.

-jumbo onChanges jumbo frames for an interface other than eth0 or eth0:0. If jumbo is set (on), theframe size is 9000 bytes. If jumbo is reset (off), the frame size is1500 bytes. If the option isnot specified, the default frame size is 1500 bytes.The jumbo option has a limited set of allowable values (1500 - OFF and 9000 - ON) for framesize, whereas the mtu option supports a range of values. The mtu option is the recommendedmethod for setting the MTU size.The climconfig tool reports an error if the NIC does not support a frame size of 9000 bytes.If the jumbo option is set for a bonding interface, it will also be applied to a slave interface.Setting the jumbo option separately for a slave interface is not allowed.If the bonding interface is UP, the jumbo option is set and a slave interface is added that doesnot support frames of 9000 bytes, Climconfig reports an error while adding the slave interface.You cannot specify both the jumbo and mtu options.A jumbo frame cannot be set for eth0 and eth0:0.Specifying jumbo overrides previous values set for mtu.

-jumbo offDisables jumbo frames for an interface. The frame size is set to 1500 bytes. If this parameteris not specified, the jumbo option is reset and the frame size set to 1500 bytes.

-forceCauses the command to modify the interface without prompting for confirmation.

-autonegotiation onEnables autonegotiation.

-autonegotiation offDisables autonegotiation. -linespeed and -duplex options must be specified.

-linespeed 10Sets the linespeed to 10MB/sec.

325

-linespeed 100Sets the linespeed to 100MB/sec.

-linespeed 1000Sets the linespeed to 1000MB/sec. This option can be set only if -autonegotiation is setto on.

-duplex halfSets the duplex mode to half.

-duplex fullSets the duplex mode to full.

-macaddrSpecifies the MAC address to be assigned to the specified interface. If default is specified,the original hardware MAC address is assigned.

NOTE: When the interface is deleted from the configuration, either as a slave interface oran independent interface, the configured software MAC address is not retained with theinterface.

ERROR MESSAGESFor interface -add:

The interface interface-name is already configured as an independent interface.Interface interface-name is slave interface for a bonding interface. It cannot be configuredas an independent interface.Interface interface-name does not exist in the kernel.The -jumbo option is not supported for eth0/eth0:0.The -mtu option is not supported for eth0/eth0:0 or for ib0/ib1.Only one of -jumbo or -mtu options can be specified.A value within the range 1280 to 9000 must be specified for -mtu option.The –prov option is not supported for CLIM with SCF MULTIPROV option set to OFF.The –prov option must be specified for CLIM with SCF MULTIPROV option set to ON.The –prov option is not supported for eth0 and eth0:0.The specified provider name is invalid; it must not be more than seven characters and mustbe alpha-numeric characters with the first character being alphabetic.

For interface -delete:This command is not supported for the interface eth0.This command is not supported for the interface lo.The interface interface-name is not configured.The interface interface-name has a tunnel interface tunnel-interface-nameassociated with it.The interface interface-name is UP, cannot execute this command.Cannot execute this command for the interface eth0:0, with eth0:0 in use.

For interface -modify:This command is not supported for the interface lo.The -jumbo option is not supported for eth0/eth0:0 or ib0/ib1.The -mtu option is not supported for eth0/eth0:0.Only one of -jumbo or -mtu options can be specified.

326

A value within the range 1280 to 9000 must be specified for -mtu option.The IPv6 family cannot be specified for the eth0.-ipaddress option for the command - "climconfig interface -modify", is supported only for eth0.The interface interface-name is not configured.Cannot execute this command for the interface eth0 when the CLIM is in STARTED state.The tunnel interface and its parent interface have different jumbo settings.Internal Error in updating SLNP rules, error-code.The specified MAC address is not a software MAC address.The software MAC address ofthe slaves slave-interface-1 and slave-interface-2 of bonding interfacebonding-interface cannot be the same for bonding mode mode.This command is not supported for InfiniBand interfaces.The specified Jumbo value already exists for the interface.The specified interface does not support the specified speed and mode.

For interface -info:The interface interface-name is not configured.

WARNING MESSAGESFor interface -modify:

Warning: SNMP configuration file /etc/default/snmpd is missing.Warning: SNMP configuration file /etc/default/snmpd is corrupt.Warning: Cannot restart SNMP daemon.Warning: Cannot restart SNMP agents.Warning: Cannot write to SNMP configuration file /etc/default/snmpd.

CONSIDERATIONSConsiderations for interface -add:

The bonding interface will find an entry as one of the interfaces, with the slave interfacesconfigured within that bonding interface definition. Slave interfaces should not be added usingthis command. Slave interfaces for a bonding interface can be configured using the commandclimconfig slaveinterface -configure . . ..The climconfig tool does not allow addition of a virtual interface other than eth0:0.eth0:0 cannot be added when the CLIM is in the STARTED state.If the interface to be added is UP, it should first be brought down using the CLIMCMD ifstopcommand, and then added.

Considerations for interface -delete:You cannot delete eth0, the dedicated service LAN interface.lo, the loopback interface, cannot be deleted.This command cannot be executed when the specified interface is active (UP). Use theCLIMCMD ifstop command to deactivate the interface before deleting it.An interface cannot be deleted before deleting any tunnel interface associated with it.This command cannot be used to delete tunnel interfaces.eth0:0, the maintenance provider interface, cannot be deleted when eth0:0 is in use by theNonStop host.

Considerations for interface -modify:You cannot modify the IP address and netmask of eth0 when the CLIM is in the STARTEDstate. To modify the IP address on a CLIM, do a climcmd clim-name clim stop, then

327

a climcmd clim-name climconfig interface -modify eth0 -ipaddress neweth0 ip address -netmask 255.255.252.0. Then issue the SCF CLIM STARTcommand to restart the CLIM after the changes.An IPv6 address cannot be assigned to eth0 interface.The -jumbo option cannot be used for eth0 and eth0:0.If the Maximum Transfer Unit (MTU) of an active interface is changed using the jumbo option,a failover of that interface might occur.The loopback interface, lo, cannot be modified.Not all ethernet cards support all linespeeds and duplex modes.Fibre channel supports only –autonegotiation on.Gigabit ethernet standard requires auto-negotiation to be ON. You cannot specify SPEED1000 Mb/s and AUTONEGOTIATION OFF.A MAC address can be modified only for an interface that is DOWN (stopped). Therefore,effectively, eth0 MAC address cannot be changed.When a MAC address is being modified, the interface must not have been failed over.The software MAC addresses of all slaves of a bonding interface must be unique in bondingmodes 5 (balance-tlb) and 6 (balance-alb). A check is performed when you attempt to changethe bonding mode.If the eth0 IP address is being changed, the known host information SSHDB on the NonStophost must be modified. Here are the required steps:1. At the TACL prompt, enter:

Tacl> sshcom open $zssp0; mode client;info knownhost *:old-eth0-ip-address.22;exit

2. For each entry listed above (one per user), issue this command:sshcom open $zssp0; mode client;delete knownhost user-name:old-eth0-ip-address.22;exit

The old-eth0-ip-address is the IP address configured on eth0 that is being changedto a new IP address.

EXAMPLES> CLIMCMD N1002581 climconfig interface -add eth1 -jumbo on

> CLIMCMD N1002581 climconfig interface –add bond0 -jumbo on

> CLIMCMD N1002581 climconfig interface -delete eth1

> CLIMCMD N1002581 climconfig interface -modify eth0-ipaddress 192.168.37.81 -netmask 255.255.128.0

> CLIMCMD 192.168.37.81 climconfig interface -modify eth1-jumbo off

> CLIMCMD 192.168.37.81 climconfig interface -modify eth1-autonegotation off -linespeed 100 -duplex half

> CLIMCMD 192.168.37.81 climconfig interface –modify eth2–autonegotiation on –linespeed 1000

> CLIMCMD 192.168.37.81 climconfig interface -modify eth2-macaddr 00:16:b4:3B:90:EE

> CLIMCMD 192.168.37.81 climconfig interface -info all

328

> CLIMCMD 192.168.37.81 climconfig interface -info all -obeyform

SEE ALSOclimconfig ip -add

329

climconfig.ip(1)NAMEclimconfig.ip -- add or delete IP addresses

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig ip -add{eth0|eth0:0|interface} -ipaddress ip-address -netmask netmask

CLIMCMD {clim-name|ip-address} climconfig ip -delete interface-ipaddress ip-address -netmask netmask [-force]

climconfig.ip DescriptionThis command does the following:ip -add

adds an IP address to an existing interface. Multiple IP addresses can be added to an interface.ip -delete

deletes an IP address from the specified interface. The IP address is deleted from theconfiguration file. If the IP address exists in the kernel, it is deleted from the kernel.

PARAMETERSeth0

Specifies the dedicated service LAN interface.eth0:0

Specifies the maintenance provider LAN interface.interface

Specifies an interface. This parameter can be either a physical interface name (such aseth1, ib0), a bonding interface name (such as bond0), or a tunnel interface (such astun0).

-ipaddress ipaddressIs the new IP address to be assigned to the interface (for ip -add) or the IP address to bedeleted from the interface (for ip -delete). It can be an IPv4 or an IPv6 IP address.

-netmask netmaskSpecifies the netmask for the interface. For IPv4 addresses, use dotted quad format. ForIPv6 addresses, use the number of bits appropriate for the IPv6 address (for example, 64).

-delete interfaceDeletes an IP address for the specified physical or bonding interface from the /etc/network/interfaces file of the CLIM. This command also deletes the tunnel configurations associatedwith the interface.

-forceCauses the command to delete the IP address without prompting for confirmation.

ERROR MESSAGESFor ip -add:

The interface interface-name is not configured.This command is not supported for the interface lo.Configuring IPv6 "address" is not allowed for eth0 and eth0:0 interfaces.Interface "eth0" already has an IP.Interface "eth0:0" already has an IP.

330

The specified IP address already exists for the interface.Cannot execute this command for the interface interface-name when the CLIM is inSTARTED state.The "IPv4" family cannot be specified for the "tunnel interface".

For ip -delete:This command is not supported for the interface lo.The interface interface-name is not configured.The specified IP address ip-address is not configured for the interface.The IP address cannot be deleted from eth0.The IP address cannot be deleted from eth0:0 with eth0:0 in use.A route with the specified IP address as a –src exists.

WARNING MESSAGESFor ip -add:

Warning: SNMP configuration file /etc/default/snmpd are missing.Warning: SNMP configuration file /etc/default/snmpd are corrupt.Warning: Cannot restart SNMP daemon.Warning: Cannot write to SNMP configuration file /etc/default/snmpd.Cannot restart SNMP agents.

For ip -delete:Warning: Could not remove IPv4 compatible IPv6 address from the kernel.

CONSIDERATIONSFor ip -add:

For SNMP listening address configuration, when the IP address is added to eth0, theclimconfig tool updates the /etc/defaults/snmpd configuration file with the new listeningaddress as the dedicated service LAN IP.Tunnel interfaces can be assigned only with IPv6 addresses.An IPv6 address cannot be assigned to eth0 and eth0:0.Only one IPv4 address can be assigned to eth0 or eth0:0.The IP address is added either to the /etc/network/interfaces file, to the kernel, or toboth. The behavior is defined as:—If the specified interface is down, the IP address is added to the file.—If the CLIM is in the STOPPED state, the IP address is added to the file.—If the specified interface is UP and the CLIM is in the STARTED state, the IP address isadded to the file and to the kernel.The customer data interfaces, eth1 - eth5, cannot have IP addresses in the 192.168.*.* range,or whatever the dedicated service LAN address range is for the system.If the same static IPv6 address is configured and added to more than one CLIM, during theinterface activation, the IPv6 address being duplicated remains as a tentative address. ThisIPv6 address is not automatically removed from the kernel/file configuration by climconfig. Itis the operator's responsibility to remove such duplicate static IPv6 addresses from theconfiguration.

For ip -delete:The IP address cannot be deleted from eth0.The IP address cannot be deleted from eth0:0, with eth0:0 in use.

331

IP address from Loopback interface lo, cannot be deleted.All the routes belonging to an interface for a particular network are automatically deleted fromthe kernel when the last IPv4 address belonging to that network is deleted from the interface.However, the routes remain in the configuration file. These routes will come into effect onlywhen the interface is restarted (ifstop followed by ifstart) or when the routes are deleted andthen added back after adding at least one IPv4 address corresponding to that network. Forexample:interface -info eth5Interface : eth5Interface Type : Physical InterfaceMTU Size : 1500IP Address : 172.17.190.71

Netmask : 255.255.255.0ROUTE Details :- Route Type : Default Route

Destination Address : 0.0.0.0Netmask : 0.0.0.0Gateway Address : 172.17.190.1Metric : 0Minimum RTO : Unspecified

When the IP 172.17.190.71 is deleted, the default route 172.17.190.1 is automatically deletedfrom the kernel.

EXAMPLES> CLIMCMD N1002581 ip -add eth1 –ipaddress 172.17.190.71 –netmask 255.255.255.0

332

climconfig.ip6tables(1)NAMEclimconfig.ip6tables -- configure ip6tables

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig ip6tables[-prov prov-name] [-force] arguments

Or,CLIMCMD {clim-name|ip-address} climconfig ip6tables[-prov prov-name] arguments [-force]

climconfig.ip6tables DescriptionThis command supports the following options. If a command is labeled as sensitive, a userconfirmation is required for execution unless the -force option is also specified.--append | -A chain rule-specification [options]

This command appends one or more rules to the end of the selected chain. When the sourceand/or destination names resolve to more than one address, a rule will be added for eachpossible address combination. This command is valid only for the CIP_INPUT chain anduser-defined chains.

--delete | -D chain [rulenum | rule-specification [options]]This command deletes one or more rules from the selected chain. There are two versions ofthis command: the rule can be specified as a number in the chain (starting from 1 for the firstrule) or a rule to match. For the latter case, the specified rule must match an existing entryin the chain exactly. This command is valid only for the CIP_INPUT chain and user-definedchains. This is a sensitive command.

--insert | -I chain [rulenum] rule-specification [options]This inserts one or more rules in the selected chain as the given rule number. Number startsfrom 1. This is also the default if no rule number is specified. This command is valid only forthe CIP_INPUT chain and user-defined chains.

--replace | -R chain rulenum rule-specification [options]This command replaces a rule in the selected chain. If the source and/or destination namesresolve to multiple addresses, the command will fail. Rules are numbered starting at 1. Thiscommand is valid only for the CIP_INPUT chain and user-defined chains. This is a sensitivecommand.

--list | -L [chain [rulenum]]Lists all rules or the rule of the specified rule number in the selected chain. Any chain (includingthe built-in chains) can be listed. This command is valid for all chains including the Linuxbuilt-in chains, the CIP built-in chains, and all user-defined chains. If no chain is selected, allchains are listed.

--list-rules | -S [chain [rulenum]]Prints all rules or the rule of the specified rule number in the selected chain in form ofiptables/ip6tables commands. This command is valid only for the CIP_INPUT chain anduser-defined chains. If no chain is selected, all users chains, if any, and the CIP_INPUT chainare listed.

--flush | -F [chain]This command deletes all user-defined rules in a chain. This command is valid only for theCIP_INPUT chain and user-defined chains. If no chain is specified, this flushes all rules inthe CIP_INPUT chain and in all user-defined chains. The CIP_INPUT_p chain is not flushed.This is a sensitive command.

333

--zero | -Z [chain]This command zeros out the packet and bytes counters in the specified chain or all chainsif the chain name is not specified. This applies to all user-defined chains, the CIP built-inchain and Linux built-in chains if chain is not specified. A user may also specify the Linuxbuilt-in INPUT chain for this command.

--new | -N chainThis command creates a new user-defined chain by the given name. There must be no targetof that name already, or an error is returned. Creating a CIP reserved chain (a name beginswith CIP_) and any of the Linux built-in chains (INPUT, OUTPUT, and FORWARD) is notallowed.

--delete-chain | -X [chain]Delete the user-defined chain specified. There must be no references to the chain. If thereare, you must delete or replace the referring rules before the chain can be deleted. The chainmust also be empty, i.e. not containing any rules. If no argument is given, it will attempt todelete every user-defined chain in the table. The following built-in chains cannot be deleted:CIP_INPUT, CIP_INPUT_p, INPUT, OUTPUT, and FORWARD.

--rename-chain | -E old-chain new-chainThis command renames the specified user-defined chain to the user-supplied name. Anyreferences to the old chain name are automatically renamed by Linux iptables/ip6tables itself.The following built-in chains cannot be renamed: CIP_INPUT, CIP_INPUT_p, INPUT,OUTPUT, and FORWARD.

--policy | -P chain targetThis command sets the policy for the chain to the given target. Only a CIP built-in CIP_INPUTchain can be specified with a policy. Neither Linux built-in nor user-defined chains can bepolicy targets.Setting a policy to CIP_INPUT chain causes the target (the first and only rule) in CIP_INPUT_pchain to be replaced.

-h | -help | --helpThis command prints the climconfig iptables/ip6tables help information. If it is specified aftera match extension, some more information pertinent to that match could also be given.

PARAMETERS-prov

Specifies a provider name. This option is mandatory for CLIMs that have MULTIPROV setto ON and cannot be used if MULTIPROV is set to OFF. Each provider has its own iptablesconfiguration. The provider name is case-insensitive and always converted to UPPER case.

-forceUsed with a sensitive command, causes the command to bypass user confirmation. Must beeither ahead of the command or at end of the line.

[!] --protocol | -p protoTo match protocol proto, which is either a protocol name or number. Supported protocolsare: all(0), tcp(6), udp(17), icmpv6(58), esp(50), ah(51), and sctp(132). When the "!" argumentis used, the ‘match’ operation is changed to the ‘not match’ operation.

[!] --source | --src | -s address[/mask]To match a source address. Address can be either a network IPv4/IPv6 address (with /mask),or a plain IP address. The mask can be either a network mask or a plain number, specifyingthe number of 1s at the left side of the network mask. Thus, a mask of 24 is equivalent to255.255.255.0. When the "!" argument is used the ‘match’ operation is changed to the ‘notmatch’ operation.

334

[!] --destination | --dst | -d address[/mask]To match a destination address. Address can be either a network IP address (with /mask),or a plain IPv4/IPv6 address. The mask can be either a network mask or a plain number,specifying the number of 1s at the left side of the network mask. Thus, a mask of 24 isequivalent to 255.255.255.0. When the "!" argument is used the ‘match’ operation is changedto the ‘not match’ operation.

[!] --in-interface | -i interface_name[+]To match a packet by the interface in which it was received. If the interface name ends in a"+", then any interface which begins with this name will match. If this option is omitted, anyinterface name will match. When the "!" argument is used the ‘match’ operation is changedto the ‘not match’ operation.

--jump | -j targetJump to a target, which can be a user-defined chain, a built-in or extension target.

--match | -m match-module-nameLoad a match extension module.

--numeric | -nSelect numeric output of addresses and ports.

--table | -t tableSpecify table to manipulate. table must be ‘filter’.

--verbose | -vVerbose mode.

--line-numbersPrint line numbers when listing.

--exact | -xTo expand numbers (display exact values).

--set-counters | -c pkts bytesThis enables the administrator to initialize the packet and byte counters of a rule (duringINSERT, APPEND, REPLACE operations). For example,iptables -A CIP_INPUT -c 100 2000 -p tcp -i eth2--dport 21 -j ACCEPT

would set the rule in the CIP_INPUT chain for accepting ftp packets targeted for interfaceeth2 and, at the same time, initialize the number of packets accepted to be 100 and numberof bytes to be 2000.

Match Extensions ip6The supported match extensions are based on the Linux iptables man pages. They are subjectto future changes made by Linux iptables implementation.ah

Matches the SPIs in Authentication header of IPsec packets.[!] --ahspi spi[:spi][!] --ahlen length--ahres

commentAllows you to add comments (up to 256 characters) to any rule.--comment commentExample:

335

ip6tables -A CIP_INPUT -s fe80::221:5aff:fec9:1a32/64-m comment --comment 'A privatized IP block'

connbytesMatches by how many bytes/packets a connection has transferred.[!] --connbytes from:[to]--connbytes-dir {original|reply|both}--connbytes-mode {packets|bytes|avgpkt}Example:ip6tables .. -m connbytes --connbytes 10000:100000

--connbytes-dir both --connbytes-mode bytes ...

connlimitAllows you to restrict the number of parallel TCP connections to a server per client IP address(or address block).[!] --connlimit-above n--connlimit-mask prefix_lengthExamples:# allow 2 telnet connections per client hostip6tables -p tcp --syn --dport 80 -s fe80::/64-m connlimit

--connlimit-above 16 --connlimit-mask 64 -j REJECT

connmark *Matches packets in connections with value set by CONNMARK target.Not supported because it is valid only in the mangle table.

conntrackMatches additional connection tracking information.[!] --ctstate stateliststatelist is a comma-separated list of the connection states to match.[!] --ctproto l4proto[!] --ctorigsrc address[/mask][!] --ctorigdst address[/mask][!] --ctreplsrc address[/mask][!] --ctrepldst address[/mask]Matches against original/reply source/destination address.[!] --ctorigsrcport port[!] --ctorigdstport port[!] --ctreplsrcport port[!] --ctrepldstport portMatches against original/reply source/destination port (TCP/UDP/etc.) or GRE key.[!] --ctstatus [NONE|EXPECTED|SEEN_REPLY|ASSURED|CONFIRMED][,...][!] --ctexpire time[:time]--ctdir {ORIGINAL|REPLY}

dccp *Matches DCCP-specific fields and types.Not supported because CIP does not support Datagram Congestion Control Protocol.

336

dscp *Matches the 6-bit DSCP field within the TOS field in the IP header.Not supported because Differentiated Services Code Point is QoS related.

dstMatches parameters in Destination Options header.[!] --dst-len length--dst-opts type[:length][,type[:length]...]

espMatches the SPIs in ESP header of IPsec packets.[!] --espspi spi[:spi]

eui64Matches EUI-64 part of a stateless auto configured IPv6 address.

fragMatches parameters in the Fragment header.[!] --fragid id[:id][!] --fraglen length--fragres--fragfirst--fragmore--fraglast

hashlimitHashlimit for something like per destination-ip or per (destip, destport) tuple. It gives you theability to express:“1000 packets per second for every host in 192.168.0.0/16”“100 packets per second for every service of 192.168.1.1”with a single ip6tables rule.--hashlimit-upto amount[/second|/minute|/hour|/day]--hashlimit-above amount[/second|/minute|/hour|/day]--hashlimit-burst amount--hashlimit-mode {srcip|srcport|dstip|dstport},...--hashlimit-srcmask prefix--hashlimit-dstmask prefix--hashlimit-name foo--hashlimit-htable-size buckets--hashlimit-htable-max entries--hashlimit-htable-expire msec--hashlimit-htable-gcinterval msec

hbhMatches parameters in Hop-by-Hop Options header.[!] --hbh-len length--hbh-opts type[:length][,type[:length]...]

337

helperSpecifies the conntrack-helper module.[!] --helper string

hlMatches the Hop Limit field in the IPv6 header.[!] --hl-eq value--hl-lt value--hl-gt value

icmp6Matches ICMPv6-specific values.[!] --icmp-type {type[/code]|typename}Allows specification of the ICMPv6 type, which can be a numeric ICMPv6 type, type andcode, or one of the ICMPv6 type names shown by the command:ip6tables -p ipv6-icmp -h

iprangeMatches on a given arbitrary range of IP addresses.[!] --src-range from[-to][!] --dst-range from[-to]

ipv6headerMatches IPv6 extension headers and/or upper layer header.--soft[!] --header header[,header...]

lengthMatches the length of a packet against a value or range of values.[!] --length length[:length]

limitMatches a rule to a specified rate. A rule using this extension will match until this limit isreached (unless the '!' flag is used).[!] --limit rate [/second|/minute|/hour|/day]--limit-burst number

macMatches source MAC address.[!] --mac-source address

mark *Matches packets with value previously set by MARK target.Not supported because it is valid only in the mangle table.

mh *Matches the Mobility Header (MH) type.Not supported because CIP does not support ipv6-mh protocol.

multiportMatches a set of source or destination ports.[!] --source-ports | --sports port[,port|,port:port]...[!] --destination-ports | --dports port[,port|,port:port]...

338

[!] --ports port[,port|,port:port]...owner *

Matches various characteristics of the (locally generated) packet creator.Not supported because it is only valid in the OUTPUT and POSTROUTING chains.

physdev *Matches on the bridge port input and output devices enslaved to a bridge device.Not supported because CIP is not a bridge device.

pkttypeMatches link-layer packet type.[!] --pkt-type {unicast|broadcast|multicast}

policyMatches IPsec policy.--dir {in|out}--pol {none|ipsec}--strict[!] --reqid id[!] --spi spi[!] --proto {ah|esp|ipcomp}[!] --mode {tunnel|transport}[!] --tunnel-src addr[/mask][!] --tunnel-dst addr[/mask]--next

quotaImplements network quota by decrementing a byte counter with each packet.--quota bytesThe quota in bytes.

rateest *Rate estimator.Not supported because it is mainly for making routing decisions (mangle table).

realm *Matches the routing realm.Not supported because it is for dynamic routing.

recentMatches against dynamically constructed list of IP addresses.--name name[!] --set--rsource--rdest[!] --rcheck[!] --update[!] --remove--seconds seconds

339

--hitcount hits--rttl

rtMatches on IPv6 routing header.--rt-type [!] type--rt-segsleft [!] num[:num]--rt-len [!] length--rt-0-res--rt-0-addrs ADDR[,ADDR...]--rt-0-not-strict

sctpMatches SCTP-specific information.[!] --source-port | --sport port[:port][!] --destination-port | --dport port[:port][!] --chunk-types all|any|only chunktype[:flags] [...]

set *Matches IP sets which can be defined by ipset(8).Not supported because ipset is not supported.

stateAllows access to conntrack state for this packet.[!] --state statelistWhere statelist is a comma-separated list of the connection states to match. Possiblestates are INVALID, ESTABLISHED, NEW, and RELATED.

statisticMatches packets based on some statistic condition.--mode mode--probability p--every n--packet p

stringMatches a given string pattern.--algo bm|kmp--from offset

--to offset[!] --string pattern[!] --hex-string pattern

tcpMatches TCP-specific values.[!] --source-port | --sport port[:port][!] --destination-port | --dport port[:port][!] --tcp-flags mask comp

[!] --syn

340

[!] --tcp-option numbertcpmss

Matches the TCP MSS field of the TCP header.[!] --mss value[:value]

timeMatches the arrival time/date of packets.--datestart YYYY[-MM[-DD[Thh[:mm[:ss]]]]]--datestop MM[-DD[Thh[:mm[:ss]]]]]--timestart hh:mm[:ss]--timestop hh:mm[:ss][!] --monthdays day[,day...][!] --weekdays day[,day...]--utcInterprets the times given for --datestart, --datestop, --timestart and --timestop to be utc.--localtzInterprets the times given for --datestart, --datestop, --timestart and --timestop to be localkernel time. (Default)

tosMatches the 8 bits ToS (Type of Service) field in the IP header.[!] --tos value[/mask][!] --tos symbol

u32Tests whether quantities of up to 4 bytes extracted from a packet have specified values. Thespecification of what to extract is general enough to find data at given offsets from tcp headersor payloads.[!] --u32 testsThe argument amounts to a program in a small language described below:tests := location "=" value | tests "&&" location "=" valuevalue := range | value "," rangerange := number | number ":" numbera single number, n, is interpreted the same as n:n. n:m is interpreted as the range of numbers>=n and <=m.location := number | location operator numberoperator := "&" | "<<" | ">>" | "@"The operators &, <<, >> and && mean the same as in C. The = is really a set membershipoperator and the value syntax describes a set. The @ operator is what allows moving to thenext header.

udpMatches UDP-specific values.[!] --source-port | --sport port[:port][!] --destination-port | --dport port[:port]

Target Extensions ip6The supported target extensions are based on the Linux ip6tables man pages. They are subjectto future changes made by Linux ip6tables implementation.

341

logWhen the LOG target is set for a rule, the Linux kernel will print some information on allmatching packets (i.e., most IP header fields) to syslog. This is a "non-terminating target",i.e. rule traversal continues at the next rule. So if you want to LOG the packets you refuse,use two separate rules with the same matching criteria, first using target LOG, the next usingDROP (or REJECT).LOG has the following options:--log-level levelLevel of logging (keyword or numeric): debug (or 7), info (or 6), notice (or 5), warning (or 4),err (or 3), crit (or 2), alert (or 1), emerg (or 0).Default is warning if not specified. If the specified severity of log-level is ‘info’ or above (e.g.,warning), the log message is also sent to NSK host generating a 5232 EMS event in $0.NOTE: Care should be used so as to not flood EMS with events.--log-prefix prefixPrefix log messages with the specified prefix; up to 25 letters long, and useful for distinguishingmessages in the logs.--log-tcp-sequenceLog TCP sequence numbers. This is a security risk if the log is readable by users.--log-tcp-optionsLog options from the TCP packet header.--log-ip-optionsLog options from the IP packet header.--log-uidLog the userid of the process which generated the packet.Example 1:Both syslog and EMS display the message.climiptables –A CIP_INPUT –j LOG --log-level info --log-prefix“LOGDROP”

climiptables –A CIP_INPUT –j DROP

Example 2:The message is only logged in the syslog not in EMS.climiptables –A CIP_INPUT –j LOG --log-level debug --log-prefix“LOGDROP”

climiptables –A CIP_INPUT –j DROP

rejectUsed to send back an error packet in response to the matched packet: otherwise it isequivalent to DROP so it is a terminating TARGET, ending rule traversal. The following optioncontrols the nature of the error packet returned:--reject-with typeThe type given for ip6tables can beicmp6-no-routeno-routeicmp6-adm-prohibitedadm-prohibitedicmp6-addr-unreachable

342

addr-unreachicmp6-port-unreachableport-unreach

ERROR MESSAGESclimconfig ip6tables requires options/commands.Try 'climconfig ip6tables -h' for more information.climconfig ip6tables Error: File /etc/clim/climiptables/state does not exist.climconfig ip6tables Error: Cannot open the file /etc/clim/climiptables/state: error-code.Error: invalid version string 'version', file ‘/etc/clim/climiptables/state’.Error: version string major, minor is not compatible, file ‘/etc/clim/climiptables/state’.climconfig ip6tables Error: Invalid climiptables state file.climconfig ip6tables Error: max prefix length for '--log-prefix' is 25.climconfig ip6tables Error: Deleting/Appending/Renaming/Flushing a rule from/to the Linux built-inchain 'xxx’ is not allowed.climconfig ip6tables Error: Deleting/Appending/Renaming/Flushing a rule from/to the CIP policychain is not allowed.

CONSIDERATIONSNone.

EXAMPLES> climcmd n1002583 climconfig ip6tables -S-N ftp-N telnet-A CIP_INPUT -p tcp -m tcp --dport 20:21 -j ftp-A CIP_INPUT -p tcp -m tcp --dport 23 -j telnet-A ftp -i eth2 -j REJECT --reject-with icmp-port-unreachable-A telnet ! -i eth2 -j REJECT --reject-with icmp-port-unreachableTermination Info: 0

> climcmd n1002583 climconfig ip6tables -vLChain INPUT (policy ACCEPT 11 packets, 889 bytes)pkts bytes target prot opt in out source

destination7636 1970K ACCEPT all -- any any N1002583 anywhere657K 229M ACCEPT all -- eth0 any anywhere anywhere204 13045 CIP_INPUT all -- any any anywhere anywhere146 9781 CIP_INPUT_p all -- any any anywhere anywhere

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)pkts bytes target prot opt in out source

destination

Chain OUTPUT (policy ACCEPT 1313 packets, 246K bytes)pkts bytes target prot opt in out source

destination

Chain CIP_INPUT (1 references)pkts bytes target prot opt in out source

destination18 972 ftp tcp -- any any anywhere anywheretcp dpts:ftp-data:ftp4 224 telnet tcp -- any any anywhere anywheretcp dpt:telnet

Chain CIP_INPUT_p (1 references)

343

pkts bytes target prot opt in out sourcedestination

Chain ftp (1 references)pkts bytes target prot opt in out source

destination2 120 REJECT all -- eth2 any anywhere anywherereject-with icmp-port-unreachable

Chain telnet (1 references)pkts bytes target prot opt in out source

destination1 60 REJECT all -- !eth2 any anywhere anywherereject-with icmp-port-unreachable

Termination Info: 0

SEE ALSOclimconfig iptables, climiptables

344

climconfig.iptables(1)NAMEclimconfig.iptables -- configure iptables

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig iptables[-prov prov-name] [-force] arguments

Or,CLIMCMD {clim-name|ip-address} climconfig iptables[-prov prov-name] arguments [-force]

climconfig.iptables DescriptionThis command supports the following arguments. If a command is labeled as sensitive, a userconfirmation is required for execution unless the -force option is also specified.--append | -A chain rule-specification [options]

This command appends one or more rules to the end of the selected chain. When the sourceand/or destination names resolve to more than one address, a rule will be added for eachpossible address combination. This command is valid only for the CIP_INPUT chain anduser-defined chains.

--delete | -D chain [rulenum | rule-specification [options]]This command deletes one or more rules from the selected chain. There are two versions ofthis command: the rule can be specified as a number in the chain (starting from 1 for the firstrule) or a rule to match. For the latter case, the specified rule must match an existing entryin the chain exactly. This command is valid only for the CIP_INPUT chain and user-definedchains. This is a sensitive command.

--insert | -I chain [rulenum] rule-specification [options]This inserts one or more rules in the selected chain as the given rule number. Number startsfrom 1. This is also the default if no rule number is specified. This command is valid only forthe CIP_INPUT chain and user-defined chains.

--replace | -R chain rulenum rule-specification [options]This command replaces a rule in the selected chain. If the source and/or destination namesresolve to multiple addresses, the command will fail. Rules are numbered starting at 1. Thiscommand is valid only for the CIP_INPUT chain and user-defined chains. This is a sensitivecommand.

--list | -L [chain [rulenum]]Lists all rules or the rule of the specified rule number in the selected chain. Any chain (includingthe built-in chains) can be listed. This command is valid for all chains including the Linuxbuilt-in chains, the CIP built-in chains, and all user-defined chains. If no chain is selected, allchains are listed.

--list-rules | -S [chain [rulenum]]Prints all rules or the rule of the specified rule number in the selected chain in form ofiptables/ip6tables commands. This command is valid only for the CIP_INPUT chain anduser-defined chains. If no chain is selected, all users chains, if any, and the CIP_INPUT chainare listed.

--flush | -F [chain]This command deletes all user-defined rules in a chain. This command is valid only for theCIP_INPUT chain and user-defined chains. If no chain is specified, this flushes all rules inthe CIP_INPUT chain and in all user-defined chains. The CIP_INPUT_p chain is not flushed.This is a sensitive command.

345

--zero | -Z [chain]This command zeros out the packet and bytes counters in the specified chain or all chainsif the chain name is not specified. This applies to all user-defined chains, the CIP built-inchain and Linux built-in chains if chain is not specified. A user may also specify the Linuxbuilt-in INPUT chain for this command.

--new | -N chainThis command creates a new user-defined chain by the given name. There must be no targetof that name already, or an error is returned. Creating a CIP reserved chain (a name beginswith CIP_) and any of the Linux built-in chains (INPUT, OUTPUT, and FORWARD) is notallowed.

--delete-chain | -X [chain]Delete the user-defined chain specified. There must be no references to the chain. If thereare, you must delete or replace the referring rules before the chain can be deleted. The chainmust also be empty, i.e. not containing any rules. If no argument is given, it will attempt todelete every user-defined chain in the table. The following built-in chains cannot be deleted:CIP_INPUT, CIP_INPUT_p, INPUT, OUTPUT, and FORWARD.

--rename-chain | -E old-chain new-chainThis command renames the specified user-defined chain to the user-supplied name. Anyreferences to the old chain name are automatically renamed by Linux iptables/ip6tables itself.The following built-in chains cannot be renamed: CIP_INPUT, CIP_INPUT_p, INPUT,OUTPUT, and FORWARD.

--policy | -P chain targetThis command sets the policy for the chain to the given target. Only a CIP built-in CIP_INPUTchain can be specified with a policy. Neither Linux built-in nor user-defined chains can bepolicy targets.Setting a policy to CIP_INPUT chain causes the target (the first and only rule) in CIP_INPUT_pchain to be replaced.

-h | -help | --helpThis command prints the climconfig iptables/ip6tables help information. If it is specified aftera match extension, some more information pertinent to that match could also be given.

PARAMETERS-prov

Specifies a provider name. This option is mandatory for CLIMs that have MULTIPROV setto ON and cannot be used if MULTIPROV is set to OFF. Each provider has its own iptablesconfiguration. The provider name is case-insensitive and always converted to UPPER case.

-forceUsed with a sensitive command, causes the command to bypass user confirmation. Must beeither ahead of the command or at end of the line.

[!] --protocol | -p protoTo match protocol proto, which is either a protocol name or number. Supported protocolsare: all(0), tcp(6), udp(17), icmp(1), esp(50), ah(51), and sctp(132). When the "!" argumentis used, the ‘match’ operation is changed to the ‘not match’ operation.

[!] --source | --src | -s address[/mask]To match a source address. Address can be either a network IPv4/IPv6 address (with /mask),or a plain IP address. The mask can be either a network mask or a plain number, specifyingthe number of 1s at the left side of the network mask. Thus, a mask of 24 is equivalent to255.255.255.0. When the "!" argument is used the ‘match’ operation is changed to the ‘notmatch’ operation.

346

[!] --destination | --dst | -d address[/mask]To match a destination address. Address can be either a network IP address (with /mask),or a plain IPv4/IPv6 address. The mask can be either a network mask or a plain number,specifying the number of 1s at the left side of the network mask. Thus, a mask of 24 isequivalent to 255.255.255.0. When the "!" argument is used the ‘match’ operation is changedto the ‘not match’ operation.

[!] --in-interface | -i interface_name[+]To match a packet by the interface in which it was received. If the interface name ends in a"+", then any interface which begins with this name will match. If this option is omitted, anyinterface name will match. When the "!" argument is used the ‘match’ operation is changedto the ‘not match’ operation.

--fragment | -fTo match only the second and subsequent fragments of a datagram.

! --fragment | -fTo match only the first fragment, or an unfragmented datagram.

--jump | -j targetJump to a target, which can be a user-defined chain, a built-in or extension target.

--match | -m match-module-nameLoad a match extension module.

--numeric | -nSelect numeric output of addresses and ports.

--table | -t tableSpecify table to manipulate. table must be ‘filter’.

--verbose | -vVerbose mode.

--line-numbersPrint line numbers when listing.

--exact | -xTo expand numbers (display exact values).

--set-counters | -c pkts bytesThis enables the administrator to initialize the packet and byte counters of a rule (duringINSERT, APPEND, REPLACE operations). For example,iptables -A CIP_INPUT -c 100 2000 -p tcp -i eth2--dport 21 -j ACCEPT

would set the rule in the CIP_INPUT chain for accepting ftp packets targeted for interfaceeth2 and, at the same time, initialize the number of packets accepted to be 100 and numberof bytes to be 2000.

Match Extensions ipThe supported match extensions are based on the Linux iptables man pages. They are subjectto future changes made by Linux iptables implementation.addrtype

Matches packets based on address type. Valid address types are: UNSPEC, UNICAST,LOCAL, BROADCAST, ANYCAST, MULTICAST, BLACKHOLE, UNREACHABLE, PROHIBIT,THROW, NAT, XRESOLVE.[!] --src-type type[!] --dst-type type--limit-iface-in

347

ahMatches the SPIs in Authentication header of IPsec packets.[!] --ahspi spi[:spi]

commentAllows you to add comments (up to 256 characters) to any rule.--comment commentExample:iptables -A INPUT -s 192.168.0.0/16 -m comment--comment 'A privatized IP block'

connbytesMatches by how many bytes/packets a connection has transferred.[!] --connbytes from:[to]Matches packets from a connection whose packets/bytes/average packet size is more thanFROM and less than TO bytes/packets. If TO is omitted, only a FROM check is done. "!" isused to match packets not falling in the range:--connbytes-dir {original|reply|both}--connbytes-mode {packets|bytes|avgpkt}Example:iptables .. -m connbytes --connbytes 10000:100000

--connbytes-dir both--connbytes-mode bytes ...

connlimitAllows you to restrict the number of parallel TCP connections to a server per client IP address(or address block).[!] --connlimit-above n--connlimit-mask bitsExamples:# allow 2 telnet connections per client hostiptables -p tcp --syn --dport 23 -m connlimit

--connlimit-above 2 -j REJECT

connmark *Matches packets in connections with value set by CONNMARK target.Not supported because it is valid only in the mangle table.

conntrackMatches additional connection tracking information.[!] --ctstate stateliststatelist is a comma-separated list of the connection states to match.[!] --ctproto l4proto[!] --ctorigsrc address[/mask][!] --ctorigdst address[/mask][!] --ctreplsrc address[/mask][!] --ctrepldst address[/mask]Matches against original/reply source/destination address.[!] --ctorigsrcport port[!] --ctorigdstport port

348

[!] --ctreplsrcport port[!] --ctrepldstport portMatches against original/reply source/destination port (TCP/UDP/etc.) or GRE key.[!] --ctstatus [NONE|EXPECTED|SEEN_REPLY|ASSURED|CONFIRMED][,...][!] --ctexpire time[:time]--ctdir {ORIGINAL|REPLY}

dccp *Matches DCCP-specific fields and types.Not supported because CIP does not support Datagram Congestion Control Protocol.

dscp *Matches the 6-bit DSCP field within the TOS field in the IP header.Not supported because Differentiated Services Code Point is QoS related.

ecnMatches different ECN fields in the TCP and IPv4 headers.[!] --ecn-tcp-cwr[!] --ecn-tcp-ece[!] --ecn-ip-ect num

espMatches the SPIs in ESP header of IPsec packets.[!] --espspi spi[:spi]

hashlimitHashlimit for something like per destination-ip or per (destip,destport) tuple. It gives you theability to express:'1000 packets per second for every host in 192.168.0.0/16''100 packets per second for every service of 192.168.1.1'with a single iptables rule.--hashlimit-upto amount[/second|/minute|/hour|/day]--hashlimit-above amount[/second|/minute|/hour|/day]--hashlimit-burst amount--hashlimit-mode {srcip|srcport|dstip|dstport},...--hashlimit-srcmask prefix--hashlimit-dstmask prefix--hashlimit-name foo--hashlimit-htable-size buckets--hashlimit-htable-max entries--hashlimit-htable-expire msec--hashlimit-htable-gcinterval msec

helperSpecifies the conntrack-helper module.[!] --helper string

icmpThis extension is loaded if '--protocol icmp' is specified. It provides the following option:

349

[!] --icmp-type {type[/code]|typename}Allows specification of the ICMP type, which can be a numeric ICMP type, type/code pair, orone of the ICMP type names shown by the command: iptables -p icmp -h

iprangeMatches on a given arbitrary range of IP addresses.[!] --src-range from[-to][!] --dst-range from[-to]

lengthMatches the length of a packet against a value or range of values.[!] --length length[:length]

limitMatches a rule to a specified rate. A rule using this extension will match until this limit isreached (unless the '!' flag is used).[!] --limit rate [/second|/minute|/hour|/day]--limit-burst number

macMatches source MAC address.[!] --mac-source address

mark *Matches packets with value previously set by MARK target.Not supported because it is valid only in the mangle table.

multiportMatches a set of source or destination ports.[!] --source-ports | --sports port[,port|,port:port]...[!] --destination-ports | --dports port[,port|,port:port]...[!] --ports port[,port|,port:port]...

owner *Matches various characteristics of the (locally generated) packet creator.Not supported because it is only valid in the OUTPUT and POSTROUTING chains.

physdev *Matches on the bridge port input and output devices enslaved to a bridge device.Not supported because CIP is not a bridge device.

pkttypeMatches link-layer packet type.[!] --pkt-type {unicast|broadcast|multicast}

policyMatches IPsec policy.--dir {in|out}--pol {none|ipsec}--strict[!] --reqid id[!] --spi spi[!] --proto {ah|esp|ipcomp}

350

[!] --mode {tunnel|transport}[!] --tunnel-src addr[/mask][!] --tunnel-dst addr[/mask]--next

quotaImplements network quota by decrementing a byte counter with each packet.--quota bytesThe quota in bytes.

rateest *Rate estimator.Not supported because it is mainly for making routing decisions (mangle table).

realm *Matches the routing realm.Not supported because it is for dynamic routing.

recentMatches against dynamically constructed list of IP addresses.--name name[!] --set--rsource--rdest[!] --rcheck[!] --update[!] --remove--seconds seconds--hitcount hits--rttl

sctpMatches SCTP-specific information.[!] --source-port | --sport port[:port][!] --destination-port | --dport port[:port][!] --chunk-types all|any|only chunktype[:flags] [...]

set *Matches IP sets which can be defined by ipset(8).Not supported because ipset is not supported.

socketMatches if an open socket can be found by doing a socket lookup on the packet.

stateAllows access to conntrack state for this packet.[!] --state statelistWhere statelist is a comma-separated list of the connection states to match. Possiblestates are INVALID, ESTABLISHED, NEW, and RELATED.

statisticMatches packets based on some statistic condition.

351

--mode mode--probability p--every n--packet p

stringMatches a given string pattern.--algo bm|kmp--from offset

--to offset[!] --string pattern[!] --hex-string pattern

tcpMatches TCP-specific values.[!] --source-port | --sport port[:port][!] --destination-port | --dport port[:port][!] --tcp-flags mask comp

[!] --syn[!] --tcp-option number

tcpmssMatches the TCP MSS field of the TCP header.[!] --mss value[:value]

timeMatches the arrival time/date of packets.--datestart YYYY[-MM[-DD[Thh[:mm[:ss]]]]]--datestop YYYY[-MM[-DD[Thh[:mm[:ss]]]]]--timestart hh:mm[:ss]--timestop hh:mm[:ss][!] --monthdays day[,day...][!] --weekdays day[,day...]--utcInterprets the times given for --datestart, --datestop, --timestart and --timestop to be utc.--localtzInterprets the times given for --datestart, --datestop, --timestart and --timestop to be localkernel time. (Default)

tosMatches the 8 bits ToS (Type of Service) field in the IP header.[!] --tos value[/mask][!] --tos symbol

ttlMatches the Time to Live (TTL) field in the IP header.--ttl-eq ttl--ttl-gt ttl

352

--ttl-lt ttlu32

Tests whether quantities of up to 4 bytes extracted from a packet have specified values. Thespecification of what to extract is general enough to find data at given offsets from tcp headersor payloads.[!] --u32 testsThe argument amounts to a program in a small language described below:tests := location "=" value | tests "&&" location "=" valuevalue := range | value "," rangerange := number | number ":" numbera single number, n, is interpreted the same as n:n. n:m is interpreted as the range of numbers>=n and <=m.location := number | location operator numberoperator := "&" | "<<" | ">>" | "@"The operators &, <<, >> and && mean the same as in C. The = is really a set membershipoperator and the value syntax describes a set. The @ operator is what allows moving to thenext header.

udpMatches UDP-specific values.[!] --source-port | --sport port[:port][!] --destination-port | --dport port[:port]

Extensions with an asterisk (*) are not supported but are not disallowed by CIP.Target Extensions ipThe supported target extensions are based on the Linux iptables man pages. They are subjectto future changes made by Linux iptables implementation.log

When the LOG target is set for a rule, the Linux kernel will print some information on allmatching packets (i.e., most IP header fields) to syslog. This is a "non-terminating target",i.e. rule traversal continues at the next rule. If you want to LOG the packets you refuse, usetwo separate rules with the same matching criteria, first using target LOG, the next usingDROP (or REJECT).LOG has the following options:--log-level levelLevel of logging (keyword or numeric): debug (or 7), info (or 6), notice (or 5), warning (or 4),err (or 3), crit (or 2), alert (or 1), emerg (or 0).Default is warning if not specified. If the specified severity of log-level is 'info' or above (e.g.,warning), the log message is also sent to NSK host generating a 5232 EMS event in $0.NOTE: Care should be used so as to not flood EMS with events.--log-prefix prefixPrefix log messages with the specified prefix; up to 25 letters long, and useful for distinguishingmessages in the logs.--log-tcp-sequenceLog TCP sequence numbers. This is a security risk if the log is readable by users.--log-tcp-optionsLog options from the TCP packet header.

353

--log-ip-optionsLog options from the IP packet header.--log-uidLog the userid of the process which generated the packet.Example 1:Both syslog and EMS display the message.climiptables –A CIP_INPUT –j LOG --log-level info --log-prefix“LOGDROP”

climiptables –A CIP_INPUT –j DROP

Example 2:The message is only logged in the syslog not in EMS.climiptables –A CIP_INPUT –j LOG --log-level debug --log-prefix“LOGDROP”

climiptables –A CIP_INPUT –j DROP

rejectUsed to send back an error packet in response to the matched packet: otherwise it isequivalent to DROP so it is a terminating TARGET, ending rule traversal. The following optioncontrols the nature of the error packet returned:--reject-with typeThe type given for iptables can beicmp-net-unreachableicmp-host-unreachableicmp-port-unreachableicmp-proto-unreachableicmp-net-prohibitedicmp-host-prohibitedicmp-admin-prohibited

ERROR MESSAGESclimconfig iptables requires options/commands. Try 'climconfig iptables -h' for more information.climconfig iptables Error: File /etc/clim/climiptables/state does not exist.climconfig iptables Error: Cannot open the file /etc/clim/climiptables/state: error-codeError: invalid version string 'version', file ‘/etc/clim/climiptables/state’.Error: version string major, minor is not compatible, file ‘/etc/clim/climiptables/state’.climconfig iptables Error: Invalid climiptables state file.climconfig iptables Error: max prefix length for '--log-prefix' is 25climconfig iptables Error: Deleting/Appending/Renaming/Flushing a rule from/to the Linux built-inchain 'xxx’ is not allowed.climconfig iptables Error: Deleting/Appending/Renaming/Flushing a rule from/to the CIP policychain is not allowed.

CONSIDERATIONSNone.

354

EXAMPLES> climcmd n1002583 climconfig iptables -S-N ftp-N telnet-A CIP_INPUT -p tcp -m tcp --dport 20:21 -j ftp-A CIP_INPUT -p tcp -m tcp --dport 23 -j telnet-A ftp -i eth2 -j REJECT --reject-with icmp-port-unreachable-A telnet ! -i eth2 -j REJECT --reject-with icmp-port-unreachableTermination Info: 0

> climcmd n1002583 climconfig iptables -vLChain INPUT (policy ACCEPT 11 packets, 889 bytes)pkts bytes target prot opt in out source

destination7636 1970K ACCEPT all -- any any N1002583

anywhere657K 229M ACCEPT all -- eth0 any anywhere

anywhere204 13045 CIP_INPUT all -- any any anywhere

anywhere146 9781 CIP_INPUT_p all -- any any anywhere

anywhere

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)pkts bytes target prot opt in out source

destination

Chain OUTPUT (policy ACCEPT 1313 packets, 246K bytes)pkts bytes target prot opt in out source

destination

Chain CIP_INPUT (1 references)pkts bytes target prot opt in out source

destination18 972 ftp tcp -- any any anywhereanywhere tcp dpts:ftp-data:ftp4 224 telnet tcp -- any any anywhereanywhere tcp dpt:telnet

Chain CIP_INPUT_p (1 references)pkts bytes target prot opt in out source

destination

Chain ftp (1 references)pkts bytes target prot opt in out source

destination2 120 REJECT all -- eth2 any anywhereanywhere reject-with icmp-port-unreachable

Chain telnet (1 references)pkts bytes target prot opt in out source

destination1 60 REJECT all -- !eth2 any anywhereanywhere reject-with icmp-port-unreachable

Termination Info: 0

SEE ALSOclimconfig ip6tables, climiptables

355

climconfig.prov(1)NAMEclimconfig.prov -- configure prov

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig prov-add prov-name

CLIMCMD {clim-name|ip-address} climconfig prov-delete prov-name [-force]

CLIMCMD {clim-name|ip-address} climconfig prov-info {prov-name | all} [-obeyform]

climconfig.prov DescriptionThis command allows you to display and configure climconfig prov objects.All network objects configured on CLIMs with the MULTIPROV attribute set to OFF are associatedwith the provider that this CLIM is assigned to in the SCF CLIM object configuration.Network objects configured on CLIMs with the MULTIPROV attribute set to ON must be explicitlyassociated with a provider. That association is represented by a climconfig prov object.prov -add

configures a new provider association. The new provider will have a loop back interfaceconfigured automatically. The provider name must not be more than seven characters longand must be alpha-numeric characters with the first character being alphabetic, and shoulddirectly correspond to the name of the PROVIDER object in SCF that this CLIM will providenetwork services to. The name can be specified in case-insensitive manner. climconfigconverts the name to upper case.

prov -deletedeletes a provider association. All network objects configured using this provider associationshould be deleted first before deleting the prov object. If any network objects are associatedwith it, an error message is generated.

NOTE: The sp, sa, psk, remote, iptables and ip6tables objects will be automatically deletedif the provider is deleted, and no error will be generated.

prov -infodisplays all the configured provider associations.

prov -info -obeyformobtains the obeyform lines for configuring the provider association in add format.

PARAMETERS-force

Used with the -delete option, causes the command to bypass user confirmation.-obeyform

Used with the -info option, obtains the provider association configuration in obeyformformat.

ERROR MESSAGESFor climconfig prov -add:

Error: The specified provider name already exists.Error: The specified provider name is invalid; it must not be more than seven characters andmust be alpha-numeric characters with the first character being alphabetic.

356

For climconfig prov -delete:Error: The specified provider name does not exist.Error: The specified provider has one or more interfaces still associated with it.Error: The specified provider name is invalid; it must not be more than seven characters andmust be alpha-numeric characters with the first character being alphabetic.

CONSIDERATIONSClimconfig prov objects are added implicitly during interface addition, so this command is onlyrequired if a provider with only loopback needs to be added.The deletion of a provider results in deletion of IPSec and iptables objects. If you want to preservethis configuration for later re-use, you can first run climconfig all -info -obeyform tocapture the configuration of these objects.

EXAMPLESTo add the provider ztc1:> CLIMCMD n1002581 climconfig prov -add ztc1

To delete the provider ztc1:> CLIMCMD n1002581 climconfig prov -delete ztc1

To display all providers:> CLIMCMD n1002581 climconfig prov -info allztc0ztc1

To display all providers with the obeyform option:> CLIMCMD n1002581 climconfig prov -info all -obeyformclimconfig prov –add ztc0climconfig prov –add ztc1#CLIMCMD expects 'exit' to be the last command.#This is required to terminate CLIMCMD session.Exit

SEE ALSOprov.1p (man 1p prov)

357

climconfig.psk(1)NAMEclimconfig.psk -- configure pre-shared keys

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig psk -add[-prov prov—name] -ip {ip-address|fqdn}-k {hex-number|string}

CLIMCMD {clim-name|ip-address} climconfig psk -delete[-prov prov—name] -ip {ip-address|fqdn}

CLIMCMD {clim-name|ip-address} climconfig psk -info[-prov {prov—name | all}] [-ip {ip-address|fqdn}][-obeyform]

climconfig.psk DescriptionThis command does the following:psk -add

adds a pre-shared key for an IP address or fully-qualified domain name (FQDN) to thepsk.txt file. Both the -ip and -k parameters are required.

psk -deletedeletes the pre-shared key for a given IP address or deletes the FQDN from the psk.txtfile. The -ip parameter is required.

psk -infodisplays the pre-shared key for a given IP address or displays the FQDN from the psk.txtfile. The -ip parameter is optional; if it is omitted, all pre-shared keys for various IP addressesfrom the psk.txt file are displayed.

PARAMETERS-prov

Specifies a provider name. This option is mandatory for CLIMs that have MULTIPROV setto ON and cannot be used if MULTIPROV is set to OFF. Each provider has its own IPSecconfiguration. The provider name is case-insensitive and always converted to UPPER case.

-ip ip-addressSpecifies an IPv4 or IPv6 address.

-ip fqdnSpecifies a fully qualified domain name.

-k stringSpecifies a key as a series of hexadecimal digits preceded by 0x or double-quoted characterstring.

-obeyformDisplays the pre-shared key configuration in the format of add command(s).

ERROR MESSAGESFor psk -add:

Please give the correct options. (The wrong options are displayed.)For psk -delete:

The pre-shared key for the matched IP address is not found.For psk -info:

There are no pre-shared keys found for the matching IP address.

358

If no options are specified, all the pre-shared keys from the file psk.txt are displayed.

EXAMPLES> CLIMCMD n1002581 climconfig psk -add –ip 10.1.1.2–k 0x12abfe34

> CLIMCMD n1002581 climconfig psk -add –ip 10.3.3.2–k ""simple psk""

> CLIMCMD n1002581 climconfig psk -add –prov ztc0 –ip 10.3.3.2–k “simple psk”

> CLIMCMD n1002581 climconfig psk -delete –ip 10.3.3.2

> CLIMCMD n1002581 climconfig psk -delete –prov ztc0 –ip 10.3.3.2

> CLIMCMD n1002581 climconfig psk -info

> CLIMCMD n1002581 climconfig psk -info –ip 10.3.3.2

> CLIMCMD n1002581 climconfig psk -info –prov zsam1 –ip 10.2.2.1

> CLIMCMD n1002581 climconfig psk -info –prov ztc0 –obeyform

The sample display for the psk -info command is:10.3.3.2 simple psk

The sample display for the psk -info -obeyform command is:climconfig psk -add \

-ip 10.3.3.2 \-k "simple psk"

#CLIMCMD expects 'exit' to be the last command.#This is required to terminate CLIMCMD session.exitTermination Info: 0

359

climconfig.remote(1)NAMEclimconfig.remote -- manage remote configuration for security associations

SYNOPSISRemote configuration for authentication method of pre-shared key:CLIMCMD {clim-name | ip-address} climconfig remote -add[-prov prov—name] -ip {ip-address | anonymous}-M exchange_mode [-idtype address [-idvalue ip-address]| -idtype {fqdn | user_fqdn} -idvalue string| -idtype keyid -idvalue file][-peer_idtype address [-peer_idvalue ip-address]| -peer_idtype {fqdn | user_fqdn} -peer_idvalue string| -peer_idtype keyid -peer_idvalue file [-verify_identifier]][-dpd_delay seconds [-dpd_retry seconds][-dpd_maxfail number]]-E encryption_algorithm-H hash_algorithm [-A pre_shared_key]-D dh_group [-restart [-force]]

Remote configuration for authentication method of certificates:CLIMCMD {clim-name | ip-address} climconfig remote -add[-prov prov—name] -ip {ip-address | anonymous}-M exchange_mode [-idtype asn1dn [-idvalue string]][-peer_idtype asn1dn [-peer_idvalue string][-verify_identifier]]-pubcert certfile -privkey privkeyfile[-dpd_delay seconds [-dpd_retry seconds][-dpd_maxfail number]]-E encryption_algorithm-H hash_algorithm -A {rsasig | gssapi_krb}-D dh_group [-gssid string] [-restart [-force]]

Remote -delete command:CLIMCMD {clim-name | ip-address} climconfig remote -delete[-prov prov—name] -ip {ip-address | anonymous} [-restart[-force]]

Remote -add_proposal command for pre-shared key:CLIMCMD {clim-name | ip-address} climconfig remote–add_proposal [-prov prov—name] –ip {ip-address | anonymous}-E encryption_algorithm -H hash_algorithm[-A pre_shared_key]-D dh_group [-restart [-force]]

Remote -add_proposal command for certificates:CLIMCMD {clim-name | ip-address} climconfig remote–add_proposal [-prov prov—name] –ip {ip-address | anonymous}-E encryption_algorithm -H hash_algorithm-A {rsasig | gssapi_krb}-D dh_group [-gssid string] [-restart [-force]]

Remote -delete_proposal command:CLIMCMD {clim-name | ip-address}climconfig remote –delete_proposal[-prov prov—name] –ip {ip-address | anonymous}–tag tag-id [-restart [-force]]

Remote -info command:CLIMCMD {clim-name | ip-address} climconfig remote -info[-prov {prov—name | all}][-ip {ip-address | anonymous}][-obeyform]

360

climconfig.remote Descriptionremote -add

adds a remote entry into the configuration file racoon.conf.remote -add_proposal

adds an additional proposal for the remote ip-address into the configuration file racoon.conffor the phase 1 IKE negotiation. A maximum of 10 proposals can exist in a remoteconfiguration.

remote -deletedeletes a remote entry from the configuration file racoon.conf.

remote -delete_proposaldeletes a proposal with a tag identifier for the remote IP address from the configuration fileracoon.conf. At least one proposal must exist in a remote configuration.

remote -infodisplays the remote configurations from the configuration file racoon.conf.

PARAMETERS-prov

Specifies a provider name. This option is mandatory for CLIMs that have MULTIPROV setto ON and cannot be used if MULTIPROV is set to OFF. Each provider has its own IPSecconfiguration. The provider name is case-insensitive and always converted to UPPER case.

–ip ip-addressSpecifies the IP address in the configuration file racoon.conf for which the remotecommand is issued.

–ip anonymousIndicates that no IP address is specified.

–M exchange_modeDefines the exchange mode for phase 1 when the racoon is the initiator. This parameter alsodefines the acceptable exchange mode when the racoon is the responder. exchange_modeis one or more of: main, aggressive, or base. You can specify more than one mode byseparating them with a comma and enclosing them in double quotes. If you specify multiplemodes, the racoon uses the first mode when it is the initiator.

–idtypeSpecifies the identifier sent to the remote host and the type to use in the phase 1 negotiation.The value is one of: user_fqdn, fqdn, address, keyid, or asn1dn.

–idvalueSpecifies the idtype value. The value is one of: ip-address, string, file.

NOTE: When the value is of type file, the entire pathname has to be specified.

–peer_idtypeSpecifies the peer's identifier to be received. If it is not defined, racoon will not verify thepeer's identifier in ID payload transmitted from the peer. If it is defined, the behavior of theverification depends on the flag of verify_identifier. The value is one of: user-fqdn, fqdn,address, keyid or asn1dn.

–peer_idvalueSpecifies the peer_idtype value. The value is one of: ip-address, string, file.

NOTE: When the value is of type file, the entire pathname has to be specified.

361

–verify_identifierTo verify the peer's identifier, set this to on. In this case, if the value defined by -peer_idtypeis not the same as the peer's identifier in the ID payload, the negotiation will fail. The defaultis off.

–pubcert certfileSpecifies the file name of a public certificate.

–privkey privkeyfileSpecifies the file name of a private key. If you omit the –pubcert or -privkey option, thedefault behavior is to use the pre-shared key. The default path for pre-shared key is /etc/racoon/psk.txt.

–dpd_delay secondsActivates Dead Peer Detection (DPD) and specifies the time, in seconds, allowed betweentwo proof of liveliness requests. The default value is 0, which disables DPD monitoring butnegotiates DPD support.

–dpd_retry secondsSets the delay, in seconds, to wait for a proof of liveliness before considering it as failed andsend another request. The default value is 5. This is set only if dpd_delay is set.

–dpd_maxfail numberSets the maximum number of liveliness proofs to request, without reply, before consideringthe peer is dead. The default value is 5. This is set only if dpd_delay is set.

–A authentication_methodSpecifies the authentication method used for the phase 1 negotiation. This parameter isrequired. The method is one of the values: pre_shared_key, rsasig, or gssapi_krb.

–D dh_groupDefines the group used for the Diffie-Hellman exponentiations. This parameter is required.group is one of the values: modp768, modp1024, modp1536, modp2048, modp3072,modp4096, modp6144, or modp8192. You can also specify one of the numerals 1, 2, 5, 14,15, 16, 17, or 18 as the DH group number. When you choose aggressive mode, you mustdefine the same DH group in each proposal.

–E encryption_algorithmSpecifies the encryption algorithm used for the phase 1 negotiation. This parameter is required.The algorithm is one of the following: des, 3des, blowfish, cast128, or aes for Oakley.Do not use this parameter for other transforms.

–H hash_algorithmSpecifies the hash algorithm used for the phase 1 negotiation. This parameter is required.hash_algorithm is one of the values: md5, sha1, sha256, sha384, or sha512 for Oakley.

–gssid stringSpecifies the GSS-API endpoint name, to be included as an attribute in the SA, if thegssapi_krb authentication method is used. If gssid is not defined, the default valuehost/hostname' is used, where hostname is the value returned by the hostname command.

–tag tag-idThe tag identifier that identifies the proposal of a remote configuration. Tag ids are numberedfrom 1 to 10.

–restartCauses the newest racoon.conf file to be loaded by restarting the racoon daemon. Awarning about the restart of the racoon daemon is issued to inform users that the SAsestablished in the SAD will be disconnected.

362

–forceUsed with the -restart option, causes the command to bypass user confirmation.

-obeyformDisplays the remote configuration in the format of add command(s).

ERROR MESSAGESFor remote -add:

Please give the correct options. (The incorrect option is displayed.)For remote -delete:

The remote information for the matched IP-address is not found.For remote -info:

The remote information for the IP-address is not found.

CONSIDERATIONSThe configuration information is not loaded until the racoon daemon is restarted. To restart theracoon daemon, use the restart option.If no options are specified for the remote -info command all the remote information for theIP addresses contained in the configuration file racoon.conf are displayed.

EXAMPLES> CLIMCMD N1002581 climconfig remote -add –ip 10.1.1.2 –M main-dpd_delay 60 –E 3des –H md5 –A pre_shared_key –D modp768

> CLIMCMD 17.205.17.2 climconfig remote -add –ip anonymous –M main–E 3des –H md5 –A pre_shared_key –D modp768 –restart

> CLIMCMD n100253 climconfig remote -add –ip anonymous –M main–E 3des –H md5 –A pre_shared_key –D modp768 –restart -force

> CLIMCMD N1002581 climconfig remote -add –ip 10.1.1.2 –M main–pubcert pubkey.pem –privkey privkey.pem –E 3des –H md5 –A rsasig–D modp768 –restart

> CLIMCMD N1002581 climconfig remote -add –ip 10.1.1.2 –M main–pubcert pubkey.pem –privkey privkey.pem –E 3des –H md5 –A rsasig–D modp768 –restart -force

> CLIMCMD n100253 climconfig remote -add –ip anonymous –M main–pubcert pubkey.pem –privkey privkey.pem –E 3des –H md5 –A rsasig–D modp768

With the following command, you will be asked for confirmation that you want to restart the racoondaemon:> CLIMCMD N1002581 climconfig remote -delete –ip 10.1.1.2 –restart

The following command does not prompt for confirmation:> CLIMCMD N1002581 climconfig remote -delete –ip 10.1.1.2–restart -force

> CLIMCMD N1002581 climconfig remote -delete –ip anonymous

> CLIMCMD N1002581 climconfig remote –add_proposal –ip 10.1.1.2–E 3des –H md5 –A pre_shared_key –D modp768 –restart

> CLIMCMD N1002581 climconfig remote –delete_proposal –ip 10.1.1.2–tag 2 –restart –force

> CLIMCMD n100253 climconfig remote -info –ip anonymous

363

> CLIMCMD n100253 climconfig remote -add –prov ztc0 –ip 10.1.1.2–M main –dpd_delay 60 –E 3des –H md5 –A pre_shared_key –D modp768

> CLIMCMD n100253 climconfig remote -delete –prov ztc0–ip 10.1.1.2 –restart

> CLIMCMD n100253 climconfig remote –add_proposal –prov zsam1–ip 10.1.1.2 –E 3des –H md5 –A pre_shared_key –D modp768 –restart

> CLIMCMD n100253 climconfig remote –delete_proposal –prov zsam1–ip 10.1.1.2 –tag 2 –restart –force

> CLIMCMD n100253 climconfig remote –info –prov zsam1

> CLIMCMD n100253 climconfig remote –info –prov ztc1 –obeyform

> CLIMCMD 192.168.37.53 climconfig remote -info

Sample display for remote info:remote 10.2.2.1 {

exchange_mode main;proposal {

encryption_algorithm 3des;hash_algorithm sha1;authentication_method pre_shared_key;dh_group modp1024;

}}

> CLIMCMD n100253 climconfig remote -info -ip anonymous -obeyform

> CLIMCMD 192.168.37.53 climconfig remote -info -obeyform

The sample display for a remote -info -obeyform command is:climconfig remote -add \

-ip 10.2.2.1 \-M main \-E 3des \-H sha1 \-A pre_shared_key \-D modp1024

#CLIMCMD expects 'exit' to be the last command.#This is required to terminate CLIMCMD session.exit

SEE ALSOclimconfig psk, climconfig sa, climconfig sp

364

climconfig.resolver(1)NAMEclimconfig.resolver -- controls the configuration of CLIM’s DNS resolver library. The resolverconfiguration file contains information that is read by various routines of the resolver library.Typically, the resolver configuration file contains the following information - (1) List of searchdomains (2) IP addresses of the DNS name servers. The ordering of the nameservers is importantbecause they get queried by the resolver in the order they are listed in the resolver configuration.

SYNOPSISCLIMCMD {clim-name | ip-address} climconfig resolver -add[-prov provider-name]-search (domain1 [..,domain6])-nameserver (server1 [..,server3])

CLIMCMD {clim-name | ip-address} climconfig resolver -delete[-prov provider-name]-search (all | domain1 [.., domain6])-nameserver (all | server1 [.., server3]) [-force]

CLIMCMD {clim-name | ip-address} climconfig resolver -enableresolver [-prov provider-name] -enable

CLIMCMD {clim-name | ip-address} climconfig resolver -disableresolver [-prov provider-name] –disable [-force]

CLIMCMD {clim-name | ip-address} climconfig resolver -inforesolver -info [all | -prov provider-name] [-obeyform]

DESCRIPTIONThis command does the following:resolver —add

This command adds the specified list of search domains and IP addresses of nameservers intothe provider specific resolver configuration.The search domains and IP addresses of nameservers get added to the resolver configurationin the same order as they are specified with –search and –nameserver options respectively. Ifthere is a list of either search domains or nameservers already existing in the resolverconfiguration, the specified ones get added to the end of the existing list.It should be noted that the resolver configuration becomes effective only after the DNS nameresolution is enabled using "climconfig resolver [-prov provider-name] -enable"command.resolver —delete

This command deletes the specified search domains and IP addresses of nameservers from theprovider specific resolver configuration.If only –search option is specified with this command, then only the specified search domainsare deleted from the resolver configuration and the existing nameserver list remains unaffected.Similarly, if only –nameserver option is specified with this command, then only the specified IPaddresses of nameservers are deleted from the resolver configuration and the existing searchdomain list remains unaffected.resolver –enable

By default, DNS name resolution is disabled for all the providers existing on the CLIM. Thiscommand enables DNS name resolution for the specified provider.resolver –enable

By default, DNS name resolution is disabled for all the providers existing on the CLIM. Thiscommand enables DNS name resolution for the specified provider.

365

resolver –disable

This command disables the DNS name resolution for the specified provider.resolver –info

This command displays the existing resolver configuration either for a particular provider or forall the providers existing on the CLIM.

PARAMETERSForresolver —add:

-provSpecifies the name of the provider for which the resolver configuration is to be added. Thisoption must be specified if SCF MULTIPROV attribute for the CLIM is set to ON. If SCFMULTIPROV attribute is set to OFF, this option defaults to %DEFAULT.

–searchSpecifies the list of search domains to be added.

–nameserverSpecifies the list of IP addresses of nameservers to be added. These nameservers are queriedfor DNS resolution in the order they are listed in the resolver configuration.

NOTE:• A maximum of three IP addresses can be added in the nameserver list for a provider.

• A maximum of six domains can be added in the search list for a provider.

• The domain search list can be a maximum of 256 characters long.

Fordataresolver —delete:

-provThis option is for specifying the name of the provider for which the resolver configuration isto be deleted. This option must be specified if SCF MULTIPROV attribute for the CLIM is setto ON. If SCF MULTIPROV attribute is set to OFF, this option defaults to %DEFAULT.

-searchThis option is for specifying the list of search domains to be deleted. If all is specified thenthe entire search domain list is deleted from the resolver configuration.

—nameserverThis option is for specifying the list of IP addresses of nameservers to be deleted. If all isspecified then the entire nameserver list is deleted from the resolver configuration.

—forceIf this command is used without –force option, will ask the users confirmation before deletingthe resolver configuration. If –force option is used, it will delete without prompting for theconfirmation.

Forresolver —enable:

—provThis option is for specifying the name of the provider for which the DNS name resolution isto be enabled. This option must be specified if SCF MULTIPROV attribute for the CLIM isset to ON. If SCF MULTIPROV attribute is set to OFF, this option defaults to %DEFAULT.

366

—enableThis option is used to enable DNS name resolution for the provider specified with –provoption. If provider name is not specified then DNS name resolution is enabled for %DEFAULTprovider.

Forresolver –disable:

—provThis option is for specifying the name of the provider for which the DNS name resolution isto be disabled. This option must be specified if SCF MULTIPROV attribute for the CLIM isset to ON. If SCF MULTIPROV attribute is set to OFF, this option defaults to %DEFAULT.

—disableThis option is used to disable the DNS name resolution for the provider specified with –provoption. If provider name is not specified then DNS name resolution is disabled for %DEFAULTprovider.

—forceIf this command is used without –force option, will ask the users confirmation before disablingthe resolver configuration. If –force option is used, it will disable without prompting for theconfirmation.

Forresolver —info:

—provThis option is for specifying the name of the provider for which the resolver configurationneeds to be displayed.

—obeyformThis option displays resolver configuration information in the format of climconfig addcommands.

ERROR MESSAGESForresolver —add:

A maximum of three IP addresses can be added in the nameserver list.A maximum of six domains can be added in the search list for a provider.The specified nameserver IP address IP-address is not valid.The specified nameserver IP address IP address is already configured.The specified domain name domain name is already configured.The specified domain search list is more than 256 characters long.The specfied domain name “all” is invalid.The provider provider name is not configured.For resolver —delete:The specified domain name domain name is invalid.The specified domain name domain name is not configured.The specified nameserver IP address IP address is invalid.The specified nameserver IP address IP address is not configured.The provider provider name is not configured.The resolver configuration does not exist for the specified provider provider name.For resolver —enable:

367

The provider provider name is not configured.The resolver is already enabled.The resolver is already enabled for the provider provider name.For resolver —disable:The provider provider name is not configured.The resolver is already disabled.The resolver is already disabled for the provider provider name.For resolver –info:The provider provider name is not configured.The resolver configuration does not exist for the specified provider provider name.The resolver configuration does not exist for any of the providers.

CONSIDERATIONS• A maximum of three IP addresses can be added in the nameserver list for a provider.

• A maximum of six domains can be added in the search list for a provider.

• The domain search list can be at most 256 characters long.

EXAMPLESForresolver —add:> CLIMCMD N1002571 climconfig resolver -add -prov ztc0 -search ftp.example.com

> CLIMCMD N1002571 climconfig resolver -add -prov ztc0 -nameserver 15.282.17.1

> CLIMCMD N1002571 climconfig resolver -add -prov ztc0 -search webserver.example.com -nameserver 15.282.17.2

> CLIMCMD N1002571 climconfig resolver -add -prov %MAINT -search nsc.example.com -nameserver 192.281.18.1

Forresolver —delete> CLIMCMD N1002571 climconfig resolver -delete -prov ztc0 –search all –nameserver all

> CLIMCMD N1002571 climconfig resolver -delete -prov ztc0 -search ftp.example.com

> CLIMCMD N1002571 climconfig resolver -delete -prov ztc0 -search webserver.example.com -nameserver 15.282.17.115.282.17.2

Forresolver —enable:

> CLIMCMD N1002571 climconfig resolver -enable

> CLIMCMD N1002571 climconfig resolver –prov ZTC0 -enable

Forresolver —disable:

> CLIMCMD N1002571 climconfig resolver -disable

> CLIMCMD N1002571 climconfig resolver –prov ZTC0 -disable

Forresolver —info:

> CLIMCMD N1002571 climconfig resolver -info all

> CLIMCMD N1002571 climconfig resolver –info –prov ZTC1

> CLIMCMD N1002571 climconfig resolver -info all -obeyform

368

SEE ALSO

369

climconfig.route(1)NAMEclimconfig.route -- configure routes

SYNOPSISCommand to add IPv4 route (non-default):CLIMCMD {clim-name|ip-address} climconfig route -add{eth0|eth0:0 | interface} -target ipv4-address {-host | -net}[-netmask netmask] [-gateway gateway] [-mt metric][-minrto time] [-initcwnd number] [-src ipv4-address]

Command to add IPv6 route (non-default):CLIMCMD {clim-name|ip-address} climconfig route-add interface -target ipv6-address {-host|-net}[-netmask netmask] [-gateway gateway] [-mt metric][-minrto time] [-initcwnd number]

Command to add default IPv4 route:CLIMCMD {clim-name|ip-address} climconfig route -add{eth0|eth0:0|interface} -default -gateway gateway[-mt metric] [-minrto time] [-initcwnd number][-src ipv4-address]

Command to add default IPv6 route:CLIMCMD {clim-name|ip-address} climconfig route-add interface -default -gateway gateway [-mt metric][-minrto time] [-initcwnd number]

Command to delete IPv4/IPv6 routes:CLIMCMD {clim-name|ip-address} climconfig route -delete{ eth0|eth0:0 | interface} [-target ip-address] {-host|-net}[-netmask netmask] [-gateway gateway] [-default] [-force]

Command to delete default IPv4/IPv6 routes:CLIMCMD {clim-name|ip-address} climconfig route-delete { eth0|eth0:0 |interface} -default -gateway gateway

Command to obtain info about a route:CLIMCMD {clim-name|ip-address} climconfig route-info [-usrconfig | -obeyform]

Command to add a route to a host in a different network:CLIMCMD {clim-name| ip-address} climconfig route-add {eth0|eth0:0|interface} -net -target host-ip-gateway gateway

climconfig.route DescriptionThis command does the following:route -add

adds a static route through an interface to specific hosts or networks.route -delete

deletes a route from an interface.route -info

displays route information.

PARAMETERS{-add|-delete} eth0

Specifies the dedicated service LAN interface. Valid only for IPv4 routes.

370

{-add|-delete} eth0:0Specifies the maintenance Provider LAN interface. Valid only for IPv4 routes.

NOTE: eth0:0 is a logical interface and is hosted on the physical interface eth0 and boththe interfaces have to belong to same subnet. Climconfig will maintain the same set or routeson both the interfaces. If a route is added to either eth0 or eth0:0, climconfig will add it to botheth0 and eth0:0.

{-add|-delete} interfaceSpecifies one of the following interfaces:An existing physical interface (for example, eth1 or ib0).A bonding interface (for example, bond0).A point-to-point tunnel interface (for example, mytun). Only IPv6 routes can be added to atunnel interface.

–hostIndicates that the route is to the host within the network (within the same subnet). The–netmask, –net, –default, and –gateway parameters are not valid with the –hostparameter.

–netIndicates that the route is to the network or to a host in another network. The –defaultparameter is not valid with the –net parameter. Also:If –netmask is not specified, the route is to a host in a different subnet.If –netmask is specified, the route is a network route. For a network route, you can specifythe –gateway parameter.

–targetSpecifies the destination network or host. Specify a dotted-quad format IPv4 address or acolon-delimited IPv6 address.

–netmask netmaskSpecifies the netmask to be used. For an IPv4 address, specify the netmask as an IPv4address in dotted quad form; for an IPv6 address, specify the netmask as a number of bits(for example, 64). This parameter is not valid with the –default and –host options. If thisparameter is omitted and –net is specified, default netmask values are 255.255.255.255 forIPv4 routes and 128 for IPv6 routes.

–gatewaySpecifies a gateway address. This parameter is required if the –default parameter isspecified.

–mtSpecifies the distance to the target, measured in hops. This number is used to indicate thecost of the route so that the best route, potentially among multiple routes to the samedestination, is selected.

–minrtoSpecifies the minimum Retransmission Timeout (RTO) value, in milliseconds, to be usedwith the specified destination. Specify a decimal or integer value; for example, 5.5. Theminimum RTO depends on the clock interrupt frequency, and might therefore get modifiedwhen assigned to the kernel.If the failed over route is the same as the home route, the failed over route uses the homeroute's minrto value.

371

–initcwndSpecifies the maximum initial congestion window (cwnd) size in MSS (Maximal SegmentSize) of a TCP connection. It sets the initial congestion window size to n * MSS. Value isfrom 1 to 4294967295. This option is used to improve performance on routes to SWANconcentrators, with a recommended value of 7.

-defaultSpecifies to use the default route if no other route matches. This option is not valid with the–host, –net, –netmask, and –target options.

-usrconfigValid only with the route -info command. This option displays user-configured routesonly. If this option is omitted, the command displays the user configured routes and thedynamic routes added by the kernel.

-obeyformGenerates user-configured route (IPv4 and IPv6) information in add command format.

-forceIf used without –force option, this command prompts for confirmation before deleting theroute.

-srcThe source IP address to use for outgoing connections or UDP packets using this route ifthe socket is not bound to an IP address. The option is useful if there is an interface withmultiple IP Addresses and it is desired that outgoing client connection requests or UDPpackets using that interface use a particular IP Address on that interface to the specifiedlocation. The –src option is valid for IPv4 routes only.

This table shows possible option combinations for different route types:

-src–initcwnd–minrto–mt–gateway–netmask–target

optionaloptionaloptionaloptionaloptionaloptionalrequired–net

optionaloptionaloptionaloptionaloptionaloptionalrequired–host

optionaloptionaloptionaloptionalrequiredoptionaloptional–default

ERROR MESSAGESFor route -add:

This command is not supported for the interface lo.The interface interface-name is not configured.Configuring IPv6 route is not allowed for eth0 and eth0:0 interfaces.The IPv4 family cannot be specified for the tunnel interface.The specified route already exists for the interface-name.The specified IP Address ip-address is not configured for interface-nameThe –src parameter is not valid for an IPv6 route.

For route -delete:The interface interface-name is not configured.This command is not supported for the interface lo.The specified route is not configured for the interface-name.

372

CONSIDERATIONSValid combinations of options for different route types for route -add and route -deleteare:

If the -net option is specified, then -target is required, and -netmask, -gateway, and-mt (route -add only) are optional.If -host is specified, then -target is required, -netmask and -gateway are not required,and -mt (route -add only) is optional.If -default is specified, then -target and -netmask are not required, -gateway isrequired, and -mt (route -add only) is optional.If -all (route -delete only) is specified, then -target, -netmask, -gateway, and-mt (route -add only) are not valid.

A route added by the route -add command is added to the /etc/network/interfacesfile, to the kernel or to both, as follows:

If the specified interface is down, the route is added to the file.If the CLIM is in the STOPPED state, the route is added to the file.If the specified interface is UP and CLIM is in the STARTED state and ifactivate is issuedto the home resources by CLIMAGT, the route is added to the file and to the kernel.If the specified interface is UP and CLIM is in the STARTED state and ifdeactivate isissued to the home resources by CLIMAGT, the route is added to the file.

All the options specified with climconfig route –add -net (except the –mt option) shouldbe specified for climconfig route –delete –net.

-src is not valid for an IPv6 route.

EXAMPLES> CLIMCMD N1002581 climconfig route -add eth1 -net-target 10.9.1.1 -netmask 255.255.255.0-gateway 172.17.1.1

> CLIMCMD N1002582 climconfig route -add eth2 -default-gateway 10.1.1.1

> CLIMCMD N1002581 climconfig route -delete eth1 -net-target 10.9.1.1 –netmask 255.255.255.0

> CLIMCMD N1002582 climconfig route -delete eth2 -default-gateway 10.1.1.1

> CLIMCMD N1002583 climconfig route -info

CLIMCMD N1002583 climconfig route -infoMaintenance LAN routesInterface : eth0Destination : 192.168.0.0Netmask : 255.255.0.0Gateway : 0.0.0.0Flags : UMetric : 0Ref : 0Use : 0MinRTO : UnspecifiedInitCWND : UnspecifiedSrc : 192.168.37.83

Interface : loDestination : ::/0

373

Gateway : ::Metric : 0MinRTO : UnspecifiedInitCWND : UnspecifiedSrc : UnspecifiedInterface : loDestination : fe80::128Gateway :Flags : UMetric : 0Ref : 0Use : 2MinRTO : 5msInitCWND : UnspecifiedSrc : Unspecified

Maintenence provider routesInterface : eth0Destination : 192.168.0.0Netmask : 255.255.0.0Gateway : 0.0.0.0Flags : UMetric : 0Ref : 0Use : 0MinRTO : UnspecifiedInitCWND : UnspecifiedSrc : 192.168.36.10

Interface : loDestination : 1128Gateway :Metric : 0MinRTO : UnspecifiedInitCWND : UnspecifiedSrc : UnspecifiedInterface : loDestination : fe80::128Gateway :Flags : UMetric : 0Ref : 0Use : 2MinRTO : 5msInitCWND : UnspecifiedSrc : Unspecified

Data Provider ZTC1 routesInterface : eth1Destination : 10.1.0.0Netmask : 255.255.0.0Gateway : 10.1.1.1Flags : UMetric : 0Ref : 0Use : 0MinRTO : UnspecifiedInitCWND : 32768Src : 10.1.1.2

Termination Info: 0

> CLIMCMD 17.205.15.2 climconfig route -info -obeyform

374

climconfig route \-add eth1 \-default \-gateway 10.1.1.1

#CLIMCMD expects 'exit' to be the last command.#This is required to terminate CLIMCMD session.exitTermination Info: 0

SEE ALSOSCF ADD ROUTE command

375

climconfig.sa(1)NAMEclimconfig.sa -- configure security associations

SYNOPSISThe command for managing security associations to the configuration file ipsec-tools.confis:CLIMCMD {clim-name|ip-address} climconfig sa -add –manual[-prov prov—name] -s src-ip -d dst-ip -p protocol-i spi [-m {tunnel|transport}] algorithm [-load]

The command for adding proposals for a security association into the configuration fileracoon.conf is:CLIMCMD {clim-name|ip-address} climconfig sa -add[-prov prov—name]{ -s src-id -d dst-id -u upperspec|anonymous} [-P pfs_group] -E encryption_algorithm-A authentication_algorithm -C compression_algorithm[-restart [-force]]

The command for deleting a security association from the configuration file ipsec-tools.confis:CLIMCMD {clim-name|ip-address} climconfig sa -delete -manual[-prov prov—name] -s src-id -d dst-id -u upperspec|anonymous} -p protocol -i spi [-unload [-force]]

The command for deleting a security association from the configuration file racoon.conf is:CLIMCMD {clim-name|ip-address} climconfig sa -delete[-prov prov—name] {-s src-id -d dst-id -u upperspec|anonymous} [-restart [-force]]

The command for obtaining information about a security association is:CLIMCMD {clim-name|ip-address} climconfig sa -info[-prov {prov—name | all}] anonymous|[-s src-ip][-d dst-ip][-p protocol]|[-u upperspec]][-obeyform]

The command for unloading SAs from the SAD is:CLIMCMD {clim-name|ip-address} climconfig sa -stop[-prov prov—name][-s src-ip -d dst-ip-p {esp|ah|ipcomp}|-i spi-value][-force]

climconfig.sa DescriptionThe sa command does the following:sa -add

adds the proposals for a security association into the configuration file racoon.conf. Thecommand parameters are reformatted into a sainfo <...> format that the racoon daemonaccepts. The SA establishment depends on the application connect.

sa -add -manualadds a security association to the configuration file ipsec-tools.conf. The commandparameters are reformatted into an add <...> type of setkey command. The SA is notloaded into the SAD unless the -load option is specified.

sa -deletedeletes the security associations from the file racoon.conf. If there are any SAs activatedon the CLIM, they are not affected.

376

sa -delete -manual deletes the security associations from the file ipsec-tools.conf.If any SAs are activated on the CLIM, they are not affected. The SA is not unloaded from theSAD unless the -unload option is specified.

NOTE: The -manual part of the command must follow sa -add and sa -delete directly.

sa -infodisplays security association configurations from the file ipsec-tools.conf orracoon.conf. If no options are selected, all the SAs are listed from both of theseconfiguration files.

sa -stopunloads security associations from the SAD. If you specify any of the optional parameters inthe first group (-s, -p, -d, -i), you must specify all of them. sa -stop is one of the commandsfor deactivating VPN connections.

PARAMETERS-manual

When specified with the add subcommand, adds a security association into theipsec-tools.conf file. The command parameters are reformatted into an add <...>type of setkey command. The SA is not loaded into the SAD unless the -load option isspecified.When specified with the delete subcommand, deletes a security association from theipsec-tools.conf file. If there are any SAs activated on the CLIM, they are not impacted.The SA is not unloaded from the SAD unless the -unload option is specified.

-provSpecifies a provider name. This option is mandatory for CLIMs that have MULTIPROV setto ON and cannot be used if MULTIPROV is set to OFF. Each provider has its own IPSecconfiguration. The provider name is case-insensitive and always converted to UPPER case.

-s src-ipSpecifies the source IP address of the secure communication as either an IPv4 or IPv6address, and an optional port number enclosed in brackets, in the following form:address [/ prefix] [[port]]

prefix and port must be decimal numbers.-d |dst-id

Specifies the destination IP address of the secure communication as either an IPv4 or IPv6address, and an optional port number between square brackets, in the following form:address [/ prefix] [[port]]

-EIs the encryption algorithm. Supported algorithms are: des, 3des, des_iv64, des_iv32,rc5, rc4, idea, 3idea, cast128, blowfish, null_enc, twofish, rijndael, aes(used with ESP). This option is for the sa -add commands (not sa -add -manual) for whichthe configurations go into the racoon.conf file.

-AAuthentication algorithm. Supported algorithms include des, 3des, des_iv64, des_iv32,hmac_md5, hmac_sha1, hmac_sha256, hmac_sha384, hmac_sha512, non_auth (usedwith ESP authentication and AH). This option is for the sa -add commands (not sa -add-manual) for which the configurations go into the racoon.conf file.

377

-CCompression algorithm. The supported algorithm is deflate (used with IPComp). Thisoption is for the sa -add commands (not sa -add -manual) for which the configurations gointo the racoon.conf file.

-pSpecifies the protocol. protocol is one of : esp, ah, or ipcomp. You must specify one ofthese protocols.

-uUpper layer protocol to be specified. Any of the protocols from the /etc/protocols filecan be specified as upperspec, or icmp6, ip4, or any. any indicates any protocol. Aprotocol number can also be specified.

-i spiSpecifies the security parameter index (SPI) for the SAD. SPI must be a decimal number ora hexadecimal number with a 0x prefix. SPI values between 0 and 255 are reserved for futureuse by IANA and cannot be used.

NOTE: The SPI value must be unique.

-m modeSpecifies the mode. Possible values are: transport or tunnel.

-loadUsed with the sa add command. This is an optional parameter. If you specify this option,the SA is loaded into the SAD. For the sa add –auto command, you are warned that theracoon daemon will be restarted so as to load the newest racoon.conf file and that therestart will disconnect the SAs established in the SAD.

-PSpecifies the PFS group, which defines the group of Diffie-Hellman exponentiations. If PFSis not required, you can omit this parameter. Any proposal is accepted if this parameter isnot specified. group is one of following: modp768, modp1024, modp1536, modp2048,modp3072, modp4096, modp6144, modp8192. Or 1, 2, 5, 14, 15, 16, 17, or 18 can be usedto define the DH group number.

algorithm(for sa -add -manual only) is one of: -E ealgo key, -A aalgo key, or -C calgo [-R].-E ealgo key

Specifies the encryption algorithm for ESP. ealgo key is one of:3des-cbc (164-bit key)3des-deriv (192-bit key)aes-ctr (160/224/288-bit key)Blowfish-cbc (40- to 448-bit key)Cast128-cbc (40- to 128-bit key)des-cbc (64-bit key)des-deriv (64-bit key)null (0- to 2048-bit key)rijndael-cbc (128/192/256-bit key)twofish-cbc (0- to 256-bit key)

-A aalgo keySpecifies the authentication algorithm for ESP. aalgo key is one of:

378

Aes-xcbc-mac (128-bit key)hmac-md5 (128-bit key)hmac-sha1 (160-bit key)hmac-sha256 (256-bit key)hmac-sha384 (384-bit key)hmac-sha512 (512-bit key)hmac-ripemd160 (160-bit key)keyed-md5 (128-bit key)keyed-sha1 (160-bit key)null (0- to 2048-bit key)Tcp-md5 (8- to 640-bit key)

-C calgo [R]Specifies a compression algorithm for IPComp. calgo [R] is either deflate orAlgorithm.If -R is specified, the SPI field value is used as the IPComp compression parameter index(CPI) on wire as-is. If -R is not specified, the kernel uses well-known CPI on wire, andthe SPI field is used only as an index for kernel-internal usage.

keyMust be a double-quoted character string or a series of hexadecimal digits preceded by0x.

-unloadUsed with the sa -delete -manual command. This is an optional parameter; if it isspecified, the SA is unloaded from the SAD. The command prompts for confirmation to unloadthe SA from the SAD.

-restartUsed with the sa -add and sa -delete commands. This is an optional parameter; if it isspecified, the racoon daemon is restarted so that the newest racoon.conf is loaded.

NOTE: The restart of the racoon daemon leads to the disconnection of the SAs alreadyloaded into the SAD. A new connection established thereafter loads the SA into the SAD.You are prompted for confirmation to restart the racoon daemon.

-forceUsed with -unload or -restart to cause the command to bypass user confirmation.

-obeyformDisplays the security association configuration in the format of add command(s).

ERROR MESSAGESFor sa -add and sa -add -manual:

Please give the correct options. (The incorrect options are displayed.)For sa -delete and sa -delete -manual:

Please give the correct options. (The incorrect option is displayed.)The security association for the matched options is not found.

For sa -info:There are no security associations with the matched options.

For sa -stop:SA configuration(s) not unloaded from the SAD.

379

CONSIDERATIONSFor sa -info, if no options are specified, all the security associations in the configuration filesipsec-tools.conf and racoon.conf are listed.For sa -stop:The src-ip and dst-ip pair, upperspec and spi value are optional parameters. If the src-ipand dst-ip pair are specified, all the SAs that match the src-ip and dst-ip are unloadedfrom the SAD. If no option is specified, all the SAs currently loaded in the kernel are unloaded.Unless you specify the -force option, you are prompted for confirmation.

EXAMPLES> CLIMCMD N1002581 climconfig sa -add–manual –s 10.1.1.2 –d 10.3.3.2–p esp –i 0x200 –m transport–E 3des-cbc 0x123456789123456789123456789123456789123456789123–A hmac-md5 0x12345678912345678912345678912345

> CLIMCMD N1002581 climconfig sa -add -manual -s 10.1.1.2-d 10.3.3.2 -p esp -i 0x200 -m transport-E 3des-cbc 0x123456789123456789123456789123456789123456789123-A hmac-md5 0x12345678912345678912345678912345 -load

> CLIMCMD N1002581 climconfig sa -add –s 10.1.1.2–d 10.3.3.2 –u any –E 3des –A hmac_md5

> CLIMCMD N1002581 climconfig sa -add -s 10.1.1.2-d 10.3.3.2 -u any -E 3des -A hmac_md5 –restart

> CLIMCMD N1002581 climconfig sa -add -s 10.1.1.2-d 10.3.3.2 -u any -E 3des -A hmac_md5 –restart -force

> CLIMCMD N1002581 climconfig sa -delete –manual–s 10.1.1.2 –d 10.3.3.2 –p esp -i 0x200 –unload

> CLIMCMD N1002581 climconfig sa -delete -manual-s 10.1.1.2 -d 10.3.3.2 -p esp -i 0x200

> CLIMCMD N1002581 climconfig sa -delete -manual-s 10.1.1.2 -d 10.3.3.2 -p esp -i 0x200 -unload -force

> CLIMCMD N1002581 climconfig sa -delete –s 10.1.1.2–d 10.3.3.2 –u any

> CLIMCMD N1002581 climconfig sa -delete -s 10.1.1.2-d 10.3.3.2 -u any -restart

> CLIMCMD N1002581 climconfig sa -delete -s 10.1.1.2-d 10.3.3.2 -u any –restart -force

> CLIMCMD N1002581 climconfig sa -info

> CLIMCMD N1002581 climconfig sa -stop –s 10.1.1.2–d 10.3.3.2 –p esp –i 0x200

> CLIMCMD N1002581 climconfig sa -stop –s 10.1.1.2–d 10.3.3.2 –p esp –i 0x200 -force

> CLIMCMD N1002581 climconfig sa -stop

> CLIMCMD N1002581 climconfig sa –stop -force

380

> CLIMCMD N1002581 climconfig sa -add –prov ztc0 -s 10.1.1.2-d 10.3.3.2 -u any -E 3des -A hmac_md5

> CLIMCMD N1002581 climconfig sa -add -manual –prov zsam1-s 10.1.1.2-d 10.3.3.2 -p esp -i 0x200 -m transport-E 3des-cbc 0x123456789123456789123456789123456789123456789123-A hmac-md5 0x12345678912345678912345678912345 –load

> CLIMCMD N1002581 climconfig sa -delete -manual –prov zsam1-s 10.1.1.2 -d 10.3.3.2 -p esp -i 0x200 –unload -force

> CLIMCMD N1002581 climconfig sa -delete –prov ztc0 -s 10.1.1.2-d 10.3.3.2 -u any

> CLIMCMD N1002581 climconfig sa –info –prov zsam1

> CLIMCMD N1002581 climconfig sa –info –prov ztc1 –obeyform

> CLIMCMD N1002581 climconfig sa -info -obeyform

The sample output for sa -info -obeyform is:# Auto SAs:climconfig sa -add \

-s 5.5.5.7 \-d 6.6.6.7 \-u any \-P 18 \-E des_iv64 \-A des_iv64 \-C deflate

# Manual SAs:climconfig sa -add -manual \

-s 1.1.1.1 \-d 2.2.2.2 \-p esp \-i 1024 \-m transport \-E des-cbc 0x1122334455667788

#CLIMCMD expects 'exit' to be the last command.#This is required to terminate CLIMCMD session.exitTermination Info: 0

SEE ALSOclimconfig vpn and climconfig sp

381

climconfig.slaveinterface(1)NAMEclimconfig.slaveinterface -- configure bonding interfaces

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig slaveinterface-configure bonding-interface-name{ [-add interface-name ][ -delete interface-name ][ -primary interface-name ]| none ]}}

climconfig.slaveinterface DescriptionThis command configures existing bonding interfaces by adding or deleting slave interfaces.With this command, you can add new slave interfaces or delete existing slave interfaces. Theaddition or deletion of slave interfaces can be done dynamically (when the bonding interface isup). This command is not supported for InfiniBand interfaces.

PARAMETERSbonding-interface-name

Is the name of the bonding interface to be configured.-add interface

Adds a slave interface to a bonding interface. To add a slave interface to a bonding interface,specify the interface name along with the –add option.

-delete interfaceDeletes a slave interface from a bonding interface. To delete a slave interface from a bondinginterface, specify the interface name along with the –delete option.

-primary interface | noneSpecifies a slave as a primary slave. To remove a configured primary slave, specify -primarywith the none option.

ERROR MESSAGESThe slave interface slave-interface-name specified with -add and -delete option is thesame.The interface bonding-interface-name is not configured.The interface bonding-interface is not a bonding interface.Slave interface slave-interface-name is not configured for this bonding interface.The specified interface slave-interface-name is already a slave ofbonding-interface-name interface.This command is not supported for the interface eth0.The specified interface slave-interface-name is already configured as an independentinterface.The specified interface slave-interface-name does not exist in the kernel.The specified slave interface slave-interface-name is not a physical interface.The interface slave-interface-name is the first slave interface of the bonding interface andthe bonding interface is UP.The slave specified with –primary is not one of the configured slaves of this bond interface.bonding-interface-name is already configured with the specified primary slave.

382

bonding-interface-name is already configured without a primary slave.Bonding is not supported for InfiniBand interfaces.

CONSIDERATIONSThe bonding interface should be configured using the command climconfig interface–add bonding-interface before adding the slave interfaces.eth0 cannot be configured as a slave interface of a bonding interface.A physical interface cannot be a slave interface for more than one bonding interface.A physical interface cannot be configured independently before being configured as the slaveinterface.Dynamically deleting (that is, deleting when the bonding interface is UP) the first slave interfaceof a bonding interface is not allowed.Using the -primary option:In active-backup mode, the primary slave will always be the active slave, if functional.Example 1:Bond0 is configured with eth2 and eth3, without any slave specified as primary.If eth2 is configured as the first slave, it will be used as long as it is functional (link pulse is presentand interface driver indicates that the interface is present). eth2 is active and eth3 is passive. Ifeth2 fails, bond0 will start using eth3. If eth2 later becomes functional, bond0 continues to useeth3 and will switch to eth2 only if eth3 fails.Example 2:Bond0 is configured with eth2 and eth3, with eth2 specified as primary.eth2 will be used as long as it is functional (link pulse is present and interface driver indicatesthat the interface is present). If eth2 fails, bond0 will start using eth3. If eth2 later becomesfunctional, bond0 switches to eth2 from eth3, even though eth3 is functional.In balance-tlb mode, outgoing traffic is distributed according to the current load (computedrelative to the speed) on each slave. Incoming traffic is received by the primary slave. Transmissionof broadcasts and multicasts is done through the primary slave.In balance-alb mode, the outgoing and incoming traffic is distributed among all slaves.Transmission of broadcasts and multicasts is through the primary slave.Multiple instances of the –primary option are not allowed in a command line.The –primary option can be specified regardless of the bond interface status.If the slave interface specified as the primary is removed from the bonded interface, that interfacewill not have any slave configured as primary.When the configured primary slave is deleted from the bonding interface, a warning is issued.

EXAMPLES> climconfig slaveinterface -configure bond0 -add eth1

> climconfig slaveinterface -configure bond0 -delete eth1

> climconfig slaveinterface -configure bond0 –primary eth1

> climconfig slaveinterface -configure bond0 -add eth1–delete eth2 –primary eth3

> climconfig slaveinterface -configure bond0 –delete eth1–add eth3

383

SEE ALSOclimconfig interface -add

384

climconfig.snmp(1)NAMEclimconfig.snmp -- configure snmp

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig snmp -add trap-receiver-ipaddressCLIMCMD {clim-name|ip-address} climconfig snmp -delete trap-receiver-ipaddress

CLIMCMD {clim-name|ip-address} climconfig snmp -start

CLIMCMD {clim-name|ip-address} climconfig snmp -stop [-force]

CLIMCMD {clim-name|ip-address} climconfig snmp -info [-obeyform]

climconfig.snmp DescriptionThis command does the following:• snmp -add adds a trap receiver IP address to the /etc/snmp/snmpd.conf file and

restarts the SNMP daemon and agents. The trap receiver address defines the host thatreceives traps.

• snmp -delete deletes a trap receiver IP address from the /etc/snmp/snmpd.conf fileand restarts the SNMP daemon and agents.

• snmp -start explicitly starts the SNMP daemon and agents.

• snmp -stop explicitly stops the SNMP daemon and agents.

• snmp -info displays SNMP configuration information. The display format is:Trap Receiver IP Address ip-address-1

.

.

.ip-address-n

SNMP Agent State stateSNMP Agent Listening IP Address ip-address

PARAMETERStrap-receiver-ipaddress

Specifies the trap receiver IP address to be added to or deleted from the configuration file.-force

Causes the command to stop the SNMP daemon and agents without confirmation.–obeyform

Displays SNMP configuration information in add command format.

ERROR MESSAGESFor climconfig snmp -add:

• Trapsink already exists in SNMP configuration.

• Internal error cannot restart the SNMP daemon, error-code.

• Internal error cannot restart the SNMP agents, error-code.For climconfig snmp -delete:

• Trapsink already exists in SNMP configuration.

• Internal Error cannot restart SNMP daemon, error-code.

• Internal error cannot restart the SNMP agents, error-code.

385

For climconfig snmp -start:

• SNMP daemon and agents are already in started state.

• Internal error cannot start SNMP daemon, error-code.

• Internal error cannot start the SNMP agents, error-code.For climconfig snmp -stop:

• SNMP daemon and agents are already in stopped state.

• Internal Error cannot stop SNMP daemon, error-code.

• Internal error cannot stop the SNMP agents, error-code.

CONSIDERATION• You can designate multiple hosts to receive traps by using snmp -add to add additional

trap receiver IP addresses to the /etc/snmp/snmpd.conf file.

EXAMPLES> CLIMCMD N1002581 climconfig snmp -infoTrap Receiver IP Address 192.168.1.192

192.168.1.193192.168.1.194

SNMP Agent State STARTEDSNMP Agent Listening IP Address 192.1.1.1

> CLIMCMD N1002581 climconfig snmp -info -obeyformclimconfig snmp -add 192.168.1.192

#CLIMCMD expects 'exit' to be the last command.#This is required to terminate CLIMCMD session.exitTermination Info: 0

386

climconfig.sp(1)NAMEclimconfig.sp -- configure security policies

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig sp -add[-prov prov—name] -s src-range -d dst-range -u upperspec-dir {in|out } -policy {discard|none|ipsec}-protocol {esp|ah|ipcomp }-mode {tunnel -srcdst src_ip-dst_ip|transport }-level {use|require|unique|default} [-load]

CLIMCMD {clim-name|ip-address} climconfig sp -delete[-prov prov—name] -s src-range -d dst-range -u upperspec-dir {in|out } [-unload [-force]]

CLIMCMD {clim-name|ip-address} climconfig -info[-prov {prov—name | all}] [-s src-range ][-d dst-range] [-u upperspec][-obeyform]

CLIMCMD {clim-name|ip-address} climconfig sp -start[-prov prov—name] [ -s src-range -d dst-range [-u upperspec]]

CLIMCMD {clim-name|ip-address} climconfig sp -stop[-prov prov—name] [ -s src-range -d dst-range -u upperspec-dir {in|out }] [-force]

climconfig.sp DescriptionThis command does the following:sp -add

adds a security policy to the configuration file ipsec-tools.conf. The command parametersare reformatted into a spdadd < ...> type setkey command. The SP is not loaded intothe SPD unless the -load option is specified.

sp -deletedeletes a security policy from the configuration file ipsec-tools.conf. If any SPs werealready activated, they are not impacted. The SP is not unloaded from the SPD unless the-unload option is specified.

sp -infodisplays security policy information from the configuration file ipsec-tools.conf. If nooptions are selected, all the SPs are listed from the ipsec-tools.conf file.

sp -startloads security policies into the SPD. sp -start is one of the commands for activating VPNconnections.

sp -stopunloads security policies from the SPD. sp -stop is one of the commands for deactivatingVPN connections.

PARAMETERS-prov

Specifies a provider name. This option is mandatory for CLIMs that have MULTIPROV setto ON and cannot be used if MULTIPROV is set to OFF. Each provider has its own IPSecconfiguration. The provider name is case-insensitive and always converted to UPPER case.

-s src-rangeSpecifies the source of the secure communication as an IPv4 or IPv6 address and an optionalport number between square brackets. This takes the form:

387

address[/prefixlen][[port]]

-d dst-rangeSpecifies the destination of the secure communication as an IPv4 or IPv6 address and anoptional port number between square brackets. This takes the following form:address[/prefixlen][[port]]

-u upperspecSpecifies the upper layer protocol. Any of the protocols from the /etc/protocols file canbe specified as upperspec, icmp6, ip4, or any. The any option indicates any protocol.You can also specify the protocol number.

NOTE: The upperspec parameter does not work in the forwarding case.There are many protocols in /etc/protocols, but protocols other than TCP, UDP, andICMP may not be suitable to use with IPSec.

-dir directionSpecifies in or out.

-policy policyIs one of the values: discard, none, or ipsec.The discard parameter causes the packet-matching indexes to be discarded. The noneparameter causes the IPSec operation not to take place on the packet. The ipsec parametercauses the IPSec operation to take place on the packet.

-protocol protocolOne of: esp, ah, or ipcomp.

-mode modeEither transport or tunnel.

-srcdst src_ip-dst_ipSpecifies the end-point addresses of the tunnel. This parameter is specified as two addressesseparated by a hyphen (-). If -mode is transport, this option is not required. If -mode istunnel, this parameter is required.

-level policy-levelSpecifies the policy level. The value is one of: default, use, require, or unique. If theSA is not available in every level, the kernel requests the key-exchange daemon to establisha suitable SA.The default option causes the kernel, when the kernel processes the packet, to consultthe system-wide default for the protocol specified; for example, the esp_trans_deflevsysctl variable.The use sysctl option causes the kernel to use an SA if it is available; otherwise the kernelcontinues to run in normal operation.The require option causes the SA to be required whenever the kernel sends a packetmatched with the policy.The unique option is the same as the require option. Additionally, the unique optionallows the policy to match the unique out-bound SA. If policy level -level is specified asunique, racoon configures the SA for the policy.

-loadCauses the SP to be loaded into the SPD. This parameter optional, and is used with the sp-add command.

388

-unloadCauses the SP to be unloaded from the SPD. This parameter is optional, and is used withthe sp -delete command. Unless you specify the -force parameter, you are promptedfor confirmation for this command.

-forceCauses the command to run without confirmation.

-obeyformDisplays the security policy configuration in the format of add command(s).

ERROR MESSAGESFor sp -add:

Please give the correct options.For sp -delete:

Please give the correct options. (The incorrect option is displayed).The security policy for the matched options is not found.

For sp -start:SP configuration not found.

For sp -info:Please give the correct options. (The incorrect option is displayed.)There are no security policies with the matched options.

For sp -stop:SP configuration(s) not unloaded from the SPD.

CONSIDERATIONSFor sp -add:

The parameters protocol, mode and level are required and valid if and only if the parameterspecified for policy is ipsec.

For sp -stop:The src-ip, dst-ip and upperspec are optional parameters. If src-ip and dst-ip pairis provided, all SPs that match the src-ip and dst-ip are unloaded from the SPD. If nooption is provided, all the SPs currently loaded in the kernel are unloaded.Unless you specify -force you are prompted for confirmation to unload the SP(s) from theSPD.You must add the SP configurations separately for different IPSec protocols ESP and AH.However, in the file, the configuration is represented as a single configuration instead of twoseparate configurations. For example:spdadd 1.2.3.4 4.3.2.1 any -P in ipsec

ah/transport//requireesp/transport//require;

When you add the SP configuration for the second, different protocol and specify the -loadoption, the IPSec tool unloads the previous old SP configuration (AH or ESP protocol) fromthe SPD and loads the new SP configuration (both AH and ESP protocols) into the SPD.If you do not use the -load option, for example, if you do not load the SP configuration forthe second protocol added, you must unload the old SP configuration manually (climconfigsp -stop <...> command) and then load the new SP configuration manually (climconfigsp -start <...> command).

NOTE: If you try to load the new SP configuration without unloading the old SP configuration,the new SP configuration is not loaded into the SPD.

389

For sp -info:If no options are specified, the list of all security policies in the configuration fileipsec-tools-conf is displayed.

EXAMPLES> CLIMCMD N1002581 climconfig sp -add-s 10.1.1.0/24[any] -d 10.3.3.0/24[any]-u any -dir in -policy ipsec -protocol esp -modetunnel -srcdst 10.2.2.1-10.2.2.2 -level require -load

> CLIMCMD N1002581 climconfig sp -add -s 10.1.1.2-d 10.3.3.2 -u any -dir out -policy ipsec -protocol esp-mode transport -level require -load

> CLIMCMD N1002581 climconfig sp -delete -s 10.1.1.2-d 10.3.3.2 -u any -dir out -unload

> CLIMCMD N1002581 climconfig sp -delete -s 10.1.1.2-d 10.3.3.2 -u any -dir out -unload -force

> CLIMCMD N1002581 climconfig sp -info -s 10.1.1.0-d 10.3.3.0 -u any

> CLIMCMD N1002581 climconfig sp -info

> CLIMCMD N1002581 climconfig sp -stop

> CLIMCMD N1002581 climconfig sp -stop -force

> CLIMCMD N1002581 climconfig sp -info –obeyform

> CLIMCMD N1002581 climconfig sp -info –s 10.1.1.0–d 10.3.3.0 –u 1 -obeyform

> CLIMCMD N1002581 climconfig sp -add –prov ztc0–s 10.1.1.2 –d 10.3.3.2 –u any –dir out –policy ipsec–protocol esp –mode transport –level require –load

> CLIMCMD N1002581 climconfig sp -delete –prov ztc0–s 10.1.1.2 –d 10.3.3.2 –u any –dir out –unload –force

> CLIMCMD N1002581 climconfig sp –info –prov zsam1

> CLIMCMD N1002581 climconfig sp –info –prov ztc1 -obeyform

The sample output for sp -info -obeyform is:climconfig sp -add \

-s 10.1.1.2 \-d 10.3.3.2 \-u any \-dir out \-policy ipsec \-protocol esp \-mode transport \-level require

#CLIMCMD expects 'exit' to be the last command.#This is required to terminate CLIMCMD session.exitTermination Info: 0

390

SEE ALSOclimconfig.sa, climconfig.vpn

391

climconfig.sysctl(1)NAMEclimconfig.sysctl -- set or display CLIM kernel parameters

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig sysctl-update {clim-name|ip-address}CLIMCMD {clim-name|ip-address} climconfig sysctl -info {all|param-name}[-obeyform]

CLIMCMD {clim-name|ip-address} climconfig sysctl -delete param-nameparam-value

climconfig.sysctl DescriptionThis command sets the kernel parameter param-name values specified by param-value. Inaddition, this command causes an entry corresponding to the parameter to be added to or updatedin the configuration file /etc/clim/kernelparam.conf. The configuration file /etc/clim/kernelparam.conf is dedicated to maintaining only the customer-configured kernel parameters.When the CLIM is started, a script reads the /etc/clim/kernelparam.conf configurationfile and sets the user configured kernel parameters in the kernel. Your changes remain persistentacross CLIM reboots. To preserve changes made to the configuration file, a backup must bedone, which can be restored when the CLIM is updated or the disk is replaced.This command also displays the user-configured kernel parameters along with their correspondingvalues existing in the /etc/clim/kernelparam.conf file.This command internally invokes the Linux provided sysctl utility with the param-name andparam-value as arguments. Therefore, the behavior of this command is similar to that of theLinux provided sysctl utility. For information about the sysctl parameters, see the sysctl(8) manpage on the CLIM.

PARAMETERSparam-name

For sysctl -update, denotes the kernel parameter to be updated with the new value.For sysctl -info, specifies the kernel parameter in the /etc/clim/kernelparam.conffile to be displayed.For sysctl -delete, deletes the specified kernel parameter from the /etc/clim/kernelparam.conf file. The parameter value remains unchanged in the kernel and is resetto its default value when the CLIM is rebooted.

param-valueSpecifies the new value for the kernel parameter param-name.

allDisplays all the user-configured kernel parameters along with their corresponding values asthey exist in the /etc/clim/kernelparam.conf file.

-obeyformGenerates the modify kernel parameter commands.

ERROR MESSAGESThe error messages are the same as those returned by the Linux sysctl utility. See the sysctlman page for information about errors.

392

CONSIDERATIONS• If the param-value has multiple entries, you must specify the entries as space separated

values within single quotes.• Changes to these sysctl parameters must be done for every CLIM in a Provider:

net.core.rmem_default◦◦ net.core.rmem_max

◦ net.core.wmem_default

◦ net.core.wmem_max

◦ net.ipv4.ip_local_port_range

◦ net.ipv4.tcp_rmem

◦ net.ipv4.tcp_wmem

• If a sysctl is deleted, the change will come into effect only after a CLIM reboot.

• On a CLIM with MULTIPROV set to ON, the sysctl settings apply to all providers associatedwith that CLIM.

• Changes to sysctl parameters should not be made when the CLIM is in STARTED state. Tochange the sysctl parameters on the CLIM:1. Stop the CLIMs and the Provider(s).2. Alter the sysctl parameters.3. Start the CLIMs and the Provider(s).If the CLIM is an Open type, you must reboot it.

EXAMPLES> CLIMCMD n100253 climconfig sysctl -update net.ipv4.conf.all.forwarding 1

> CLIMCMD n100253 climconfig sysctl -update net.ipv4.tcp_rmem '4096 87380 1048576'

> CLIMCMD n100253 climconfig sysctl -info net.ipv4.tcp_rmemnet.ipv4.tcp_rmem = 4096 87380 1048576

> CLIMCMD n100253 climconfig sysctl -info allnet.ipv4.tcp_rmem = 4096 87380 1048576net.ipv4.conf.all.forwarding = 1

> CLIMCMD n100253 climconfig sysctl -info all -obeyformclimconfig sysctl -update net.ipv4.tcp_fin_timeout 60

#CLIMCMD expects 'exit' to be the last command.#This is required to terminate CLIMCMD session.exitTermination Info: 0

393

climconfig.tunnel(1)NAMEclimconfig.tunnel -- modify tunnel configuration

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig tunnel-add tunnel-interface -ipaddress ipv6-address-netmask netmask-endpoint {ipv4-address | any}-local ipv4-address[-ttltime ttl-time] - intf parent-interface[-mtu mtu-value | -jumbo { on | off } ]

CLIMCMD {clim-name|ip-address} climconfig tunnel -delete interface

CLIMCMD {clim-name|ip-address} climconfig tunnel -info{tunnel-interface|all}[-obeyform]

climconfig.tunnel DescriptionThis command does the following:tunnel -add

adds an IPv6-over-IPv4 (point-to-point) tunnel configuration to the /etc/network/interfaces file. IPv6 packets are encapsulated in IPv4 headers and sent across the IPv4infrastructure through the configured tunnel. If the -mtu option is not specified, the tunnelinterface is activated with an MTU size of 20 bytes less than its parent interface MTU size orwith a value of 1280, whichever is higher.

NOTE: When adding a tunnel interface to CLIMs with MULTIPROV ON, the tunnel is addedto the same provider that the parent interface belongs to and does not need to be explicitlyindicated in the command line.

tunnel -deletedeletes an existing tunnel interface. If the tunnel is active, the tunnel configuration cannot bedeleted.

tunnel -infodisplays tunnel configuration information for a specified tunnel interface. The display formatis:Interface Name tunnel-interfaceIPv6 Address ip-addressNetmask netmaskRemote Endpoint ip-addressLocal Endpoint ip-addressTTL Time ttltimeMTU Size value

If the Local Endpoint, Gateway, and TTL Time fields are not configured, they do not appearin the display.The -obeyform display format is:climconfig tunnel -add interface-name -ipaddressipv6–address

-netmask ipv6–prefix -endpoint ipv4–address-local ipv4–address -intf parent-interface[-mtu mtu-value][-ttltime ttl-time]

394

PARAMETERStunnel-interface

Is the name of the tunnel interface to be added, deleted, or displayed. The tunnel interfacename is case sensitive.

allDisplays the configurations of all the interfaces.

-obeyformFor a specified Tunnel interface name, displays Tunnel configuration in add command format.

–ipaddress ipv6-addressIs an IPv6 address.

–netmask netmaskIs the netmask for the IPv6 address, specified as a number of bits, for example, 64.

–endpoint {ipv4-address|any}Is the address of the tunnel endpoint. Specify either a dotted quad IPv4 address or any. If itis specified as any, the kernel determines the remote endpoint by examining the 6to4 addressand creates a 6to4 tunnel. 6to4 tunnels do not have an IPv6 link local address likepoint-to-point tunnels. The local IPv4 address will be added as an IPv6 compatible IPv4address. The kernel then encapsulates the packet and sends it to the IPv4 address embeddedin the packet.

–local ipv4-addressIs the address of the local endpoint, specified as a dotted quad IPv4 address.

–ttltime ttl-timeIs the TTL setting indicating the network time to live. The maximum value is 255.

–intf parent-interfaceSpecifies the parent interface name (for example, eth1 or bond1) that hosts the local endpointIPv4 address.

-mtuSets frame size for an interface. Allowable values are 1280 to 65508.You cannot specify both the jumbo and mtu options.Specifying the mtu option overrides previous values set for jumbo.

–jumbo { on | off }Sets or resets jumbo frames for a tunnel interface. If set to ON, the frame size is set to 9000bytes. If reset (OFF), the frame size is set to 1500 bytes.The jumbo option has a limited set of allowable values (1500 - OFF and 9000 - ON) for framesize, whereas the mtu option supports a range of values. The mtu option is the recommendedmethod for setting MTU size.You cannot specify both the jumbo and mtu options.Specifying jumbo overrides previous values set for mtu.

ERROR MESSAGESFor tunnel -add:

Tunnel interface interface is already configured as an independent interface.parent-interface is invalid parent interface.The interface parent-interface is not configured.The IP address ipv4-address specified with the -local option is not configured with thespecified interface parent-interface.

395

A tunnel for the specified endpoints exists.Another tunnel with the same endpoints should not exist.Only one of -jumbo or -mtu options can be specified.A value within the range of 1280 to 65508 must be specified for the -mtu option.

For tunnel -delete:The interface tunnel-interface is not configured.The interface tunnel-interface is UP; cannot execute this command.

For tunnel -info:Tunnel interface interface configuration does not exist.

CONSIDERATIONSFor L15.02/J06.10/H06.21 and later RVUs, tunnels can be added only in upper case, but existingtunnels in lower case are supported and do not need to be deleted and re-added.The parent interface and the local endpoint address should be configured before adding thetunnel interface.eth0, lo, and eth0:0 are not valid parent interfaces for a tunnel interface.A tunnel interface cannot be the parent interface of a tunnel interface.If the Maximum Transfer Unit (MTU) value of an active interface is changed using the jumbooption, a failover of that interface might occur.A different tunnel with the same endpoints cannot exist.

EXAMPLES> CLIMCMD N1002581 climconfig tunnel -add MYTUN1-ipaddress 2001:0db8:fff5:6::101-netmask 64 -endpoint 192.168.217.111 -local 192.168.217.35 -intf eth1

> CLIMCMD 100.253.17.2 climconfig tunnel -delete MYTUN1

> CLIMCMD N1002581 climconfig tunnel -info MYTUN1Interface : MYTUN1Interface Type : Point-to-Point Tunnel InterfaceMTU Size : 1280Associated Parent Interface Name: eth5Local Endpoint Address : 1.2.3.15Remote Endpoint Address : 1.2.3.4TTL value : UnspecifiedIP Address : dead:beef:face::1/64

> CLIMCMD N1002581 climconfig tunnel -info TUN2 -obeyformclimconfig tunnel \-add TUN2 \-ipaddress 3ffe::218:71ff:fe79:b378 \-netmask 64 \-local 173.17.190.40 \-endpoint 173.17.190.100 \-intf eth4#CLIMCMD expects 'exit' to be the last command.#This is required to terminate CLIMCMD session.exitTermination Info: 0

SEE ALSOclimconfig vpn

396

climconfig.vpn(1)NAMEclimconfig.vpn -- obtain information about virtual private networks

SYNOPSISCLIMCMD {clim-name|ip-address} climconfig vpn -status[-prov {prov—name | all}] [-s src-ip -d dst-ip]

climconfig.vpn DescriptionThis command displays the status of the VPN connection established between the source anddestination IP addresses. The security policy and the association loaded in the Security PolicyDatabase (SPD) and Security Association Database (SAD) are displayed in that order. -d and-s are optional parameters; if they are omitted, the status of all the VPN connections is shown.

PARAMETERS-s src-ip

Specifies the source IP address.-d dst-ip

Specifies the destination IP address.-prov

Specifies a provider name. This option is mandatory for CLIMs that have MULTIPROV setto ON and cannot be used if MULTIPROV is set to OFF. Each provider has its own IPSecconfiguration. The provider name is case-insensitive and always converted to UPPER case.

ERROR MESSAGESThe status for the VPN connection between src-ip and dst-ip is not found. Please check forthe correct options and retry again.

EXAMPLES> CLIMCMD N1002581 climconfig vpn -statusSecurity Policies from SPD:10.2.2.0/24[any] 10.1.1.2[any] any

in ipsecesp/tunnel/10.2.2.1-10.1.1.2/requireah/tunnel/10.2.2.1-10.1.1.2/requirecreated: Jun 22 20:48:13 2008 lastused:lifetime: 0(s) validtime: 0(s)spid=8 seq=2 pid=369refcnt=1

10.1.1.2[any] 10.2.2.0/24[any] anyout ipsecesp/tunnel/10.1.1.2-10.2.2.1/requireah/tunnel/10.1.1.2-10.2.2.1/requirecreated: Jun 22 20:48:13 2008 lastused:lifetime: 0(s) validtime: 0(s)spid=1 seq=1 pid=369refcnt=1

Security Associations from SAD:10.1.1.2 10.2.2.1

esp mode=tunnel spi=262906055(0x0faba0c7)reqid=0(0x00000000)E: 3des-cbc f1eee61a f2642ace 2c89c610 c245978d 7ea13336133d84d2A: hmac-md5 d34b8476 cb8bda72 9d1b8e0b 059f14adseq=0x00000000 replay=4 flags=0x00000000 state=maturecreated: Jun 22 21:03:02 2008current: Jun 22 21:03:22 2008

397

diff: 20(s) hard: 28800(s) soft: 23040(s)last: Jun 22 21:03:03 2008 hard: 0(s) soft: 0(s)current: 252(bytes) hard: 0(bytes) soft: 0(bytes)allocated: 3 hard: 0 soft: 0sadb_seq=3 pid=727 refcnt=0

10.2.2.1 10.1.1.2esp mode=tunnel spi=7523920(0x0072ce50) reqid=0(0x00000000)E: 3des-cbc b5e66f7b faeb03c3 4571b6ed 5686d721 c05350ad49e967c2A: hmac-md5 9206a14f 0f6dfb3a a2138e04 dc1c4140seq=0x00000000 replay=4 flags=0x00000000 state=maturecreated: Jun 22 21:03:03 2008current: Jun 22 21:03:22 2008diff: 19(s) hard: 28800(s) soft: 23040(s)last: Jun 22 21:03:03 2008 hard: 0(s) soft: 0(s)current: 408(bytes) hard: 0(bytes) soft: 0(bytes)allocated: 3 hard: 0 soft: 0sadb_seq=1 pid=727 refcnt=0

SEE ALSOclimconfig sa -stop, climconfig sp -start, climconfig sp -stop

398

A SCF Error MessagesThis appendix describes the CIP subsystem SCF error messages. Error messages are listedwith their accompanying subsystem programmatic interface (SPI) token.For operator messages, see the Operator Messages Manual.

CIP 00001 (zcip-err-cmd-not-implemented)CIP E00001 Command not implemented.

CauseYou entered a command that the CIP SCF product module does not support.EffectThe SCF command is not executed.RecoveryCheck the SCF section of this manual for a list of supported commands.

CIP 00002 (zcip-err-internal-error)CIP E00002 CIP SCF Product Module Internal Error - contact GCSC.

CauseCIP SCF Product Module encountered an internal error.EffectThe SCF command is not executed.RecoveryThis is a serious error. Send complete error information to your Global Customer SupportCenter for analysis.

CIP 00003 (zcip-err-case-out-of-range)CIP E00003 CIP SCF Product Module Internal Error: Case value out of range.

CauseAn invalid case value was generated with no associated case label.EffectThe SCF command is not executed.RecoveryThis is a serious error. Send complete error information to your Global Customer SupportCenter analyst for analysis.

CIP 00004 (zcip-err-cmd-attr-dup)CIP E00004 Duplicate attribute specified.

CauseYou specified an attribute more than once in a command.EffectThe SCF command is not executed.RecoveryOmit the duplicate attribute and retry the command.

CIP 00005 (zcip-err-wild-not-sup)CIP E00005 Object name object-name contains wild cards - not allowed for this command.

object-nameIs the object name string that generated the error.

399

CauseYou attempted to use wildcard characters (*,?) in an object name for a command that doesnot support wild-cards.EffectThe SCF command is not executed.RecoveryReissue the command without wild-card characters in the object name.

CIP 00006 (zcip-err-cip-internal)CIP E00006 INTERNAL ERROR: error-number, Origin origin,

Severity level for object-name.

error-numberSpecifies an internal error number.

originIndicates where the internal error originated, such as CIPMAN, CIPMON, CIPSREQ.

levelTells whether this error is informative, warning, fatal, or unrecognized.

object-nameIs the object name string that generated the error.

CauseAn internal error occurred within the CIP subsystem (CIPMAN, CIPMON, CIPSREQ).EffectThe SCF command is not executed.RecoveryThis is a serious error. Send complete error information to your Global Customer SupportCenter for analysis.

CIP 00007 (zcip-err-process-busy)CIP E00007 CIP process is busy - cannot process request.

CauseCIPMAN or one of the CIPMONs is busy and cannot process the given request at this time.CIPMAN or CIPMON is probably starting up.EffectThe SCF command is not executed.RecoveryRetry command later. If this problem persists, contact your service provider.

CIP 00008 (zcip-err-clim-inuse)CIP E00008 CLIM object-name is already assigned to another Provider or another Route.

object-nameIs the CLIM object specified in the ADD or ALTER PROVIDER, or ADD ROUTE command.

CauseThe CLIM name in an ADD or ALTER PROVIDER command is already assigned to anotherMaintenance Provider or the CLIM name in an ADD ROUTE command is already assigned toanother Route with an overlapping IP-address family.EffectThe CLIM cannot be assigned to two Maintenance Providers or Routes with an overlappingIP-address family.

400 SCF Error Messages

RecoveryAssign a different CLIM to the Maintenance Provider you want to add or alter or remove thecurrent Maintenance Provider that is using the specified CLIM. Use INFO CLIM, DETAILcommand to display the Maintenance Provider associated with that CLIM. Or assign a differentCLIM to the Route you want to add or assign a different IP address family to the Route youwant to add or remove the current Route that is using the specified CLIM. Use INFO ROUTEcommand to display the CLIM and IP address family associated with each ROUTE object.

CIP 00009 (zcip-err-tpname-inuse)CIP E00009 Transport Provider process specified for provider-name is already assigned to another Provider.

provider-nameIs the PROVIDER object specified in the ADD or ALTER PROVIDER command.

CauseThe transport provider process (CIPSAM process) name in an ADD or ALTER PROVIDERcommand is already assigned to another provider.EffectThe SCF command is rejected.RecoveryAssign a different transport provider process to the provider you want to add or alter or removethe current provider that is associated with the specified transport provider process. Use theSCF INFO PROVIDER command to display the transport provider processes assigned to theproviders in the CIP subsystem.

CIP 00010 (zcip-err-tpname-invalid)CIP E00010 tp-name is an invalid TP name.

tp-nameIs the name of transport provider process (CIPSAM process) specified in the ADD or ALTERPROVIDER command.

CauseThe specified transport provider process (CIPSAM process) name is not a valid transportprovider process name.EffectThe SCF command is rejected.RecoveryRe-issue the command with a valid transport provider process (TP) name.

CIP 00011 (zcip-err-location-invalid)CIP E00011 Invalid CLIM location location.

locationIs the CLIM location (group, module, slot, port, and, for systems that support it, fiber) that isinvalid.

CauseThe LOCATION attribute in an ADD CLIM command is invalid because:• One or more of the numbers contain invalid characters.• Any of the group, module, slot, port or fiber values are out of range.• Two or more values are inconsistent.EffectThe SCF command is rejected.

401

RecoveryRe-issue the command with a correct LOCATION.

CIP 00012 (zcip-err-location-inuse)CIP E00012 CLIM location location is in conflict with CLIM owner-name.

locationIs the specified CLIM location (group, module, slot, port, and, for some systems, fiber) inconflict with the location already in use by an existing CLIM or has ownership of location thatwould be required by the current ADD CLIM command.

owner-nameSpecifies the other CLIM which has ownership of that location either explicitly for example,has the exact same location specified in a previous ADD CLIM command) or implicitly (forexample, has an equivalent location to the location specified in a previous ADD CLIMcommand).

CauseThe LOCATION attribute in an ADD CLIM command is already configured by another CLIMobject.EffectThe SCF command is rejected.RecoveryRe-issue the command with a different LOCATION.

CIP 00013 (zcip-err-location-incompatible)CIP E00013 CLIM location location is invalid for this type of system.

locationIs the CLIM location (group, module, slot, port, or fiber) that is invalid.

CauseThe LOCATION attribute in an ADD CLIM command is invalid for this system.EffectThe SCF command is rejected.RecoveryRe-issue the command with a location that is valid for this type of system, or without LOCATIONattribute for CLIM (on NonStop X systems).

CIP 00015 (zcip-err-location-exclusive)CIP E00015 CLIM clim-name is associated with an existing maintenance Provider object.

clim-nameIs the CLIM object specified in the DELETE CLIM command.

CauseA DELETE CLIM command was issued for a CLIM object that is associated with an existingProvider object. You cannot delete a CLIM object until there are no PROVIDER objectsdependent on the specified CLIM.EffectThe SCF command is rejected.RecoveryTo remove the CLIM object, the PROVIDER object associated with the specified CLIM mustbe removed first. Use the INFO PROVIDER command to display the names of the providersand their associated CLIMs.

402 SCF Error Messages

CIP 00016 (zcip-err-cpu-not-avail)CIP E00016 The CIPMON in the specified processor to be traced is in the STOPPED state.

CauseThe user issued a TRACE command but there is no CIPMON to handle that request in thespecified processor.EffectThe SCF command is not executed.RecoveryIssue the START MON command, then retry the TRACE command.

CIP 00017 (zcip-err-qio-resource-short)CIP E00017 Command failed for object object-name due to QIO error error-number.

object-nameIs the name of the object that generated the error.

error-numberIs the QIO error number encountered.

CauseThe specified SCF command required use of QIO resources, but an error in manipulating theseQIO resources caused the command to fail.EffectSCF ignores the command.RecoveryCheck the condition that caused the given QIO error, resolve that condition, then retry the SCFcommand.

CIP 00018 (zcip-err-climconfig-db-fail)CIP E00018 Configuration failure due to cause on operation operation-type for object-name.

causeSpecifies what caused the error. The causes are:• Record not found• Record already exists• Obsolete record version• Record version too new• Database is locked by another process• Record information is corrupted• ConfigDB operation fails

operation-typeSpecifies the operation the object was performing when the error occurred. The operationsare:• Locking• Unlocking• Inserting• Deleting• Reading• Updating

403

object-nameIs the name of the object that generated the error.

CauseThe SCF command requires CIPMAN to manipulate the configuration database, but it failedas specified by the cause information.EffectSCF ignores the command.RecoveryCheck the command and correct all problems, then try the command again. If failure persists,contact your service provider with the cause and operation-type information.

CIP 00019 (zcip-err-open-sockets)CIP E00019 Cannot stop object-name, open sockets still exist.

object-nameIs the name of the object that generated the error.

CauseA STOP command cannot be executed because the object still has open sockets.EffectThe SCF command is rejected.RecoveryClose all sockets using the object and reissue the STOP command, or use the ABORTcommand instead of the STOP command.

CIP 00020 (zcip-err-obj-busy)CIP 00020 Object object-name is busy with other operations.

object-nameIs the name of the object that generated the error.

CauseThe object you issued the command to is busy performing other actions and cannot processthe SCF command.EffectSCF ignores the command.RecoveryWait, then try the command again. Contact your service provider if the problem persists.

CIP 00021 (zcip-err-cip-timeout)CIP 00021 CIP command timed out on object-name.

object-nameIs the name of the object that generated the error.

CauseA command expired before a response from the CLIM was received.EffectThe SCF command you entered was initiated, but successful completion cannot be guaranteed.RecoveryIf possible, check if the command completed successfully; otherwise, reissue the command.

CIP 00022 (zcip-err-inv-switch-cpu)CIP E00022 CPU is not the backup processor.

404 SCF Error Messages

CauseThe CPU parameter in a PRIMARY command was specified, but its value was not the backupprocessor number.EffectThe command is not executed.RecoveryUse the correct backup processor number or omit the CPU parameter.

CIP 00023 (zcip-err-hostname-invalid)CIP E00023 hostname is an invalid hostname.hostname

Is the hostname specified in the ADD or ALTER PROVIDER command.CauseThe specified hostname is not a valid hostname.EffectThe SCF command is rejected.RecoveryRe-issue the command with a valid hostname.

NOTE: hostname is a string from zcom-tkn-objname-01 (almost identical tozcom-tkn-objname).

CIP 00024 (zcip-err-filesystem)CIP E00024 Command failed for object object-name due to file system error error-number.object-name

Is the name of the object that generated the error.error-number

Is the NonStop host-system filesystem error number encountered.CauseA command failed during a file system operation on a specified file (most likely a trace filename).This caused the command to fail.EffectThe SCF command is rejected.RecoveryMake sure that a valid and correct filename is specified, then retry the SCF command.

NOTE: error-number is from zcip-tkn-cip-error-detail (field errcode).

CIP 00025 (zcip-err-name-reserved)CIP E00025 Object name object-name is currently reserved and cannot be used.CauseYou attempted to use an object name in an ADD command that is currently cannot be usedwithin CIP subsystem for the specified object type.EffectThe SCF command is not executed.RecoveryReissue the ADD command using different object name.

405

NOTE: The specified object name probably already has a corresponding CIP subsystemconfiguration record within the configuration database that cannot be used by the CIP subsystemfor some reason. See CIP EMS event 5206, 5306, and 5506 for more details.

CIP 00026 (zcip-err-attr-val-invalid)CIP E00026 Attribute value invalid: text.text

Is the text string describing the problem with the attribute value.CauseYou issued a command, and tried to assign an invalid value to an attribute.EffectThe SCF command is not executed.RecoveryReissue the command using a value for that attribute that is within the valid range.

NOTE: This is used internally by the SCF product module.

CIP 00027 (zcip-err-attr-incompatible)CIP E00027 Invalid attribute combination..CauseThe specified attribute conflicted with one or more of the other attributes on the command line.EffectThe SCF command is not executed.RecoveryRefer to the command descriptions (in the manual or help text) for information about whichattributes can be combined.

NOTE: This is used internally by the SCF product module.

CIP 00028 (zcip-err-cpu-attr-invalid)CIP E00028 CPU attribute not supported.CauseYou issued a TRACE MON or TRACE PROCESS command with the CPU attribute specified.Only TRACE CLIM and TRACE PROVIDER commands support the CPU attribute.EffectThe SCF command is not executed.RecoveryReissue SCF command without the CPU attribute.

NOTE: This is used internally by the SCF product module.

CIP 00029 (zcip-err-locksize-invalid)CIP E00029 LOCKSIZE must be less than or equal to PAGES.CauseYou issued a TRACE command with a LOCKSIZE value that was greater than the PAGESvalue.EffectThe SCF command is not executed.

406 SCF Error Messages

RecoveryRetry the command with a LOCKSIZE value that is less than or equal to the PAGES value. IfPAGES is not specified, LOCKSIZE must be less than or equal to 64 pages.

NOTE: This is used internally by the SCF product module.

CIP 00030 (zcip-err-cpu-attr-required)CIP E00030 CPU attribute is required.CauseYou issued a TRACE CLIM or TRACE PROVIDER command and specified the TO attributebut not the CPU attribute.EffectThe SCF command is not executed.RecoveryReissue the SCF command with the CPU attribute.

NOTE: This is used internally by the SCF product module.

CIP 00031 (zcip-err-context-invalid)CIP E00031 Request contains invalid or obsolete context information.CauseContinuation of an SCF command happens with invalid or obsolete context information. Thiscan happen if too much time has elapsed between the initial request and command continuation.EffectThe SCF command is not executed.RecoveryReissue the SCF command.

CIP 00032 (zcip-err-unsynch-mon)CIP E00032 One or more CIPMON processes are out of synch.CauseAn SCF request for configuration change (ADD, DELETE, or ALTER command) or state change(START, STOP, or ABORT command) cannot be executed because the CIPMAN processcannot communicate with one or more CIPMON processes to ensure consistency of CIPsubsystem configuration.EffectThe SCF configuration or state change command is not executed.RecoveryReissue the SCF command. If the problem persists for more than a short duration, locate theproblematic CIPMON process and fix the cause for that CIPMON process' inability to processthe request from the CIPMAN process.

CIP 00033 (zcip-err-sub-not-stopped)CIP E00033 One or more subordinate objects cannot be stopped.CauseA STOP or ABORT PROCESS SCF request with the SUB ALL option specified failed to stopthe CIPMAN process because the CIPMAN process cannot stop one or more subordinatedCLIM and PROVIDER objects.EffectThe CIPMAN process is not stopped.

407

RecoveryIf you only want to stop the CIPMAN process, reissue the STOP or ABORT PROCESS SCFrequest without the SUB option or with the SUB NONE option. If you want to stop all subordinateCLIM and PROVIDER objects as well as the CIPMAN process itself, use the ABORT PROCESSSCF request with the SUB ALL option. If the problem persists, investigate why the subordinateobjects cannot be stopped.

CIP 00034 (zcip-err-sub-not-supported)CIP E00034 Specified SUB option is not supported by command/object.CauseThe SUB option is specified and it is not compatible with the specified command or the SUBoption is omitted for a command that requires the SUB option.EffectThe SCF command is rejected.RecoveryMake sure that a valid SUB option is specified, then retry the SCF command.

CIP 00035 (zcip-err-cpu-down)CIP E00035 The specified processor is currently down.CauseYou issued a TRACE command but the specified processor is currently down.EffectThe SCF command is rejected.RecoveryReissue the TRACE command with a different processor.

CIP 00036 (zcip-err-wrong-prov-type)CIP E00036 PROVIDER object-name type is not compatible with this request.

object-nameIs the PROVIDER object specified in the ADD or ALTER CLIM, ADD or ALTER PROVIDER,or ADD ROUTE or STATUS PROVIDER, ROUTE or SWITCH CLIM, PROVIDER command.

CauseThe provider name in an ADD or ALTER CLIM, ADD or ALTER PROVIDER, or ADD ROUTEor STATUS PROVIDER, ROUTE or SWITCH CLIM, PROVIDER command belongs to a typethat is not compatible with the command.EffectThe SCF command is rejected.RecoveryReissue the SCF command with different provider that has the correct type or reissue SCFcommand with option that is compatible with the provider type. Use the INFO PROVIDERcommand to display the type of each provider.

CIP 00037 (zcip-err-invalid-clim)CIP E00037 CLIM object-name is invalid for this request.

object-nameIs the CLIM object specified in the ADD or ALTER PROVIDER, ALTER CLIM, or ADD ROUTEcommand.

CauseThe CLIM name in an ADD or ALTER PROVIDER command has operational mode that is notcompatible with the command. Or the target CLIM in an ALTER CLIM command has an

408 SCF Error Messages

operation mode that is not compatible with the attribute specified with the command. Or theCLIM name in an ADD ROUTE command is not associated with the parent PROVIDER objectof that Route and the MULTIPROV attribute of that CLIM is set to OFF.EffectThe SCF command is rejected.RecoveryReissue SCF ADD or ALTER PROVIDER command with different CLIM that has the correctoperational mode. Or reissue the SCF ALTER CLIM command with a different CLIM that hasthe correct operational mode. Or reissue the SCF ADD ROUTE command with CLIM andIPDATA provider names that are associated with each other or with a CLIM that has theMULTIPROV attribute set to ON. Use the INFO CLIM command to display the MULTIPROVattribute and the IPDATA provider associated with each CLIM.

CIP 00038 (zcip-err-route-exists)CIP E00038 CLIM clim-name is associated with an existing Route object.

clim-nameIs the CLIM object specified in the DELETE CLIM or ALTER CLIM command.

CauseA DELETE CLIM command was issued for a CLIM object that is associated with an existingRoute object. You cannot delete a CLIM object until there are no (Maintenance Provider orRoute) objects dependent on the specified CLIM. Or an ALTER CLIM a command was issuedfor a CLIM object that is associated with an existing Route object that would not be able toassociate with that CLIM object if the ALTER CLIM command successfully completes. Althougha Route object can be associated with any CLIM with MULTIPROV ON, a Route object cannotbe associated with a CLIM with MULTIPROV OFF unless the PROVIDER attribute of thatCLIM is the same as the parent of that Route object.EffectThe SCF command is rejected.RecoveryTo remove or alter the CLIM object, the Route object associated with the specified CLIM mustbe removed first. Use the INFO ROUTE command to display the CLIM associated with eachRoute object.

CIP 00039 (zcip-err-storage-inuse)CIP E00039 CLIM clim-name is in use by Storage Subsystem.

clim-nameIs the CLIM object specified in the DELETE CLIM command.

CauseA DELETE CLIM command was issued for a CLIM object (with STORAGE operation mode)that is being used by Storage Subsystem. You cannot delete a CLIM object until there is noreference from Storage Subsystem to the specified CLIM.EffectThe SCF command is rejected.RecoveryTo remove the CLIM object, the dependency of Storage Subsystem on the specified CLIMmust be removed first. See Storage Subsystem for more details.

CIP 00040 (zcip-err-interface-exists)CIP E00040 CLIM clim-name still has interfaces running on other CLIM(s).

clim-nameIs the CLIM object specified in the DELETE CLIM or ALTER CLIM command.

409

CauseA DELETE CLIM or ALTER CLIM command was issued for a CLIM object that is associatedwith one or more interfaces configured on that CLIM that are currently running on other CLIM(s).You cannot delete a CLIM object or alter PROVIDER attribute of a CLIM object withMULTIPROV OFF until there are no interfaces configured on that CLIM running on any CLIM.EffectThe SCF command is rejected.RecoveryTo remove the CLIM object, the interfaces associated with the specified CLIM must be removedfirst. Use the STATUS CLIM, DETAIL command to display the active interfaces associatedwith that CLIM. Use ABORT CLIM, INTFALL command to stop usage of all interfaces configuredon that CLIM.

CIP 00041 (zcip-err-clim-exists)CIP E00041 PROVIDER object-name is associated with an existing CLIM object.

object-nameIs the PROVIDER object specified in the DELETE PROVIDER command.

CauseA DELETE PROVIDER command was issued for an IPDATA provider object that is associatedwith an existing CLIM object. You cannot delete a PROVIDER object until there are no (CLIMor Route) objects dependent on the specified provider.EffectThe SCF command is rejected.RecoveryTo remove the IPDATA provider object, the CLIM object associated with the specified IPDATAprovider must be removed first. Use the INFO PROVIDER, DETAIL command to display thenames of the CLIM associated with that IPDATA provider.

CIP 00041 (zcip-err-clim-exists)CIP E00041 PROVIDER object-name is associated with an existing CLIM object.

object-nameIs the PROVIDER object specified in the DELETE PROVIDER command.

CauseA DELETE PROVIDER command was issued for an IPDATA provider object that is associatedwith an existing CLIM object. You cannot delete a PROVIDER object until there are no (CLIMor Route) objects dependent on the specified provider.EffectThe SCF command is rejected.RecoveryTo remove the IPDATA provider object, the CLIM object associated with the specified IPDATAprovider must be removed first. Use the INFO PROVIDER, DETAIL command to display thenames of the CLIM associated with that IPDATA provider.

CIP 00042 (zcip-err-object-unremovable)CIP E00042 PROVIDER object-name cannot be deleted.

object-nameIs the PROVIDER object specified in the DELETE PROVIDER command.

CauseA DELETE PROVIDER command was issued for the default PROVIDER object ($ZZCIP.ZTC0)which can never be deleted.

410 SCF Error Messages

EffectThe SCF command is rejected.RecoveryReissue SCF command with a different Provider.

CIP 00043 (zcip-err-intf-not-exist)CIP E00043 PROVIDER interface-name does not exist.

interface-nameIs the interface name specified in the SWITCH CLIM command.

CauseA SWITCH CLIM command was issued for an interface that does not exist.EffectThe SCF command is rejected.RecoveryReissue SCF command with the correct interface name.

CIP 00044 (zcip-err-intf-invalid)CIP E00044 Interface interface-name is invalid for specified CLIM.

interface-nameIs the interface name specified in the SWITCH CLIM command.

CauseA SWITCH CLIM command was issued for an interface that does not belong to the specifiedCLIM object.EffectThe SCF command is rejected.RecoveryReissue SCF command with the correct interface or CLIM name.

CIP 00045 (zcip-err-intf-no-fover)CIP E00045 Interface interface-name is not configured to support failover.

interface-nameIs the interface name specified in the SWITCH CLIM command.

CauseA SWITCH CLIM command was issued for an interface that is not configured to support failover.EffectThe SCF command is rejected.RecoveryReissue SCF command with the correct interface name.

CIP 00046 (zcip-err-intf-fover-invalidCIP E00046 Interface interface-name failover configuration cannot currently fail over.

interface-nameIs the interface name affected by the SWITCH CLIM command.

411

CauseA SWITCH CLIM command was issued, either implicitly or explicitly, that affects an interfacewhich is configured for failover, but the current condition makes failover to another CLIMimpossible. The possible conditions include:• A target CLIM or interface for failover does not exist or is invalid.• A target CLIM is currently not accessible.• An interface is brought down by an operator request.• The target CLIM does not have sufficient configuration information to bring up the interface.• The interface for failover has a visiting interface.EffectThe SCF command is rejected for that interface.RecoveryUse the STATUS CLIM, DETAIL command to display failover configurations for all interfacesconfigured on a CLIM. Ensure that the failover configuration is correct and valid on the targetCLIM and that the target CLIM is accessible. Then reissue the SCF command.

CIP 00047 (zcip-err-intf-fover-failCIP E00047 Failover attempt for interface interface-name failed.

interface-nameIs the interface name affected by the SWITCH CLIM command.

CauseAn attempt to fail over an interface as part of a SWITCH CLIM command failed and the specifiedinterface cannot be brought up on the target CLIM.EffectThe interface cannot be brought up on the target CLIM.RecoveryCheck CIP EMS event 5223 to find out more details about why the interface cannot be broughtup on the target CLIM. Correct the problem and reissue the SCF command.

CIP 00048 (zcip-err-clim-not-stoppedCIP E00048 CLIM(s) associated with PROVIDER object-name are not stopped.

object-nameIs the PROVIDER object specified in the ALTER PROVIDER command.

CauseThe provider name in an ALTER PROVIDER command (with SHARE-PORTS option) has oneor more associated CLIM(s) not in STOPPED state.EffectThe SCF command is rejected.RecoveryStop the CLIM(s) associated with the Provider by using the INFO PROVIDER, DETAIL commandto display the list of CLIMs associated with the Provider and then using the STOP or ABORTCLIM command to stop the associated CLIM(s). Reissue the SCF ALTER PROVIDER command.

CIP 00049 (zcip-err-ipaddr-invalidCIP E00049 ip-address is invalid.

ip-addressIs the IP address specified in the ADD CLIM command.

412 SCF Error Messages

CauseThe specified IP address is not a valid IP address for a maintenance Provider.EffectThe SCF command is rejected.RecoveryRe-issue the command with a valid IP address.

CIP 00050 (zcip-err-connpts-invalidCIP E00050 CONNPTS value connpts is invalid for specified location.

connptsIs the CONNPTS attribute value specified in the ADD or ALTER PROVIDER command.

CauseThe specified CONNPTS value is not valid or not valid for the specified location.EffectThe SCF command is rejected.RecoveryRe-issue the command with a valid CONNPTS attribute value.

CIP 00051 (zcip-err-family-invalidCIP E00051 FAMILY value family is invalid.

familyIs the FAMILY attribute value specified in the ADD ROUTE or PROVIDER or ALTERPROVIDER command.

CauseThe specified FAMILY value is not valid for the specified object type or the specified FAMILYvalue for ROUTE object is not valid for the specified parent provider object FAMILY.EffectThe SCF command is rejected.RecoveryRe-issue the command with a valid FAMILY attribute value.

CIP 00052 (zcip-err-priority-invalidCIP E00052 PRIORITY value priority is invalid for specified location.

priorityIs the PRIORITY attribute value specified in the ADD ROUTE command.

CauseThe specified PRIORITY value is not valid.EffectThe SCF command is rejected.RecoveryRe-issue the command with a valid PRIORITY attribute value.

CIP 00053 (zcip-err-active-mon)One or more CIPMON processes are still running.

CauseA STOP PROCESS SCF request failed to stop the CIPMAN process because one or moreCLIM or PROVIDER objects are not in a STOPPED state and one or more CIPMON processesare still running (i.e., one or more MON objects not in a STOPPED state).

413

EffectThe CIPMAN process is not stopped.RecoveryIf you only want to stop the CIPMAN process, issue the ABORT PROCESS SCF requestwithout the SUB option or with the SUB NONE option. If you want to stop all subordinate CLIMand PROVIDER objects as well as the CIPMAN process itself, use the ABORT PROCESSSCF request with the SUB ALL option. If the problem persists, investigate why the subordinateobjects cannot be stopped.

CIP 00054 (zcip-err-clim-config-mismatch)CLIM clim-name has incompatible configuration.

clim-nameis the CLIM object specified in the ALTER CLIM command.

CauseAn ALTER CLIM command was issued for a CLIM object whose configuration on the CLIM isnot compatible with the new attribute value and cannot be converted to be compatible with thenew attribute value. In particular, the MULTIPROV attribute cannot be altered to OFF if thereare any network resources configured on the CLIM that are associated with a provider that isnot the same as the PROVIDER attribute of that CLIM object.EffectThe SCF command is rejected.RecoveryTo alter the CLIM object, the configuration on the CLIM must first be updated to be compatiblewith the new attribute value. Then reissue the ALTER CLIM command.

CIP 00055 (zcip-err-interface-exists-prov)Provider prov-name still has active associated interfaces.

prov-nameis the PROVIDER name specified in the DELETE PROVIDER command.

CauseA DELETE PROVIDER command was issued for a PROVIDER object that is associated withone or more interfaces configured on one or more CLIMs. You cannot delete a PROVIDERobject until there are no active interfaces on any CLIMs associated with that provider. This canhappen when there are interfaces configured on a CLIM with MULTIPROV ON that areassociated with the target PROVIDER object even though the parent CLIM object is not directlyassociated with the PROVIDER object (via the PROVIDER attribute of that CLIM).EffectThe SCF command is rejected.RecoveryTo remove the PROVIDER object, the interfaces associated with the specified provider mustbe removed first. Use the STATUS PROVIDER, DETAIL command to display the activeinterfaces associated with that provider. On each CLIM, use “climconfig” to remove all interfacesassociated with that provider. On each CLIM, use “climconfig interface –info all” to list allinterfaces with their associated provider to find all interfaces associated with that provider onthat CLIM.

CIP 00056 (zcip-err-prov-not-exist)Provider prov-name does not exist.

prov-nameis the PROVIDER name specified in the SWITCH CLIM command.

414 SCF Error Messages

CauseA SWITCH CLIM command was issued for a provider that does not exist.EffectThe SCF command is rejected.RecoveryReissue SCF command with the correct provider name. (SCFPM Note: prov-name is fromzcip-tkn-provider-name.)

CIP 00057 (zcip-err-clim-incompatible)CLIM clim-name software version is incompatible.

clim-nameis the CLIM object specified in the ALTER CLIM command.

CauseAn ALTER CLIM command was issued for a CLIM object whose software version on the CLIMis not compatible with the new attribute value. In particular, the MULTIPROV attribute cannotbe altered to ON if the CLIM software does not support the MULTIPROV feature.EffectThe SCF command is rejected.RecoveryTo alter the CLIM object, the configuration on the CLIM software must first be updated to becompatible with the new attribute value. Then reissue the ALTER CLIM command.

CIP 00058 (zcip-err-interface-wrong-prov)CLIM clim-name has interfaces associated with other PROVIDER(s).

clim-nameis the CLIM object specified in the ALTER CLIM command.

CauseAn ALTER CLIM, MULTIPROV OFF command was issued for a CLIM object that has one ormore interfaces configured on it which are associated with a provider other than the PROVIDERattribute of the CLIM object even though the CLIM object is not in STARTED state. You cannotalter the MULTIPROV attribute of a CLIM object to OFF until all known interfaces for that CLIMare associated with the provider specified by the PROVIDER attribute of that CLIM object.EffectThe SCF command is rejected.RecoveryTo set the ALTER MULTIPROV attribute of the CLIM object to OFF, the interfaces associatedwith the specified CLIM and providers other than the PROVIDER attribute of that CLIM objectmust be removed first. Use the ABORT CLIM, INTFALL command to stop usage of all interfacesconfigured on that CLIM.

CIP 00059 (zcip-err-interface-wrong-prov)CLIM clim-name has no association with Provider prov-name.

clim-nameis the CLIM object specified in the SWITCH CLIM command.

prov-nameis the PROVIDER name specified in the PROVIDER option of the SWITCH CLIM command.

CauseA SWITCH CLIM, PROVIDER command was issued for a provider that does not have anyassociation with network resources configured on the specified CLIM.

415

EffectThe SCF command is rejected.RecoveryReissue SCF command with the correct provider name. (SCFPM Note: prov-name is fromzcip-tkn-provider-name.)

416 SCF Error Messages

B Fault CodesThis appendix documents fault codes that belong to the CIP subsystem and can appear in CIPsubsystem EMS messages.Many fault codes suggest checking software versions. To obtain this information:• Use SCF VERSION PROCESS $ZZCIP to obtain the CIPMAN version.• Use SCF VERSION MON $ZZCIP.mon to obtain the CIPMON software version.• Examine the VPROC $SYSTEM.SYSnn.ZCIPDLL file to obtain the ZCIPDLL version. (This

version should be the same as the CIPMON software version.)• Use SCF VERSION CLIM $ZZCIP.CLIM to obtain the CLIM software version or look in the

/etc/vprocfile on the CLIM.

Origin “CIP Manager” Fault Code 10031003CauseThe size of the message CIPMAN received from CIPMON is inconsistent with what is expected.EffectThe message is dropped without further processing.RecoveryCIPMAN automatically retries the operation. If this problem persists over an extensive periodof time, make sure the appropriate versions of software (CIPMAN, CIPMON, ZCIPDLL, CLIM)are running. If the problem persists, contact your Hewlett Packard Enterprise service provider.

Origin “CIP Manager” Fault Code 10111011CauseA configured CLIM object is now unusable due to a problem with hardware connectivity orhardware configuration. This can be caused by there being no CLIM connected at the configuredlocation, different devices connected on different fabrics corresponding to the same configuredlocation, or other connectivity problems. Or this can be caused by no configured CLIM hardwarewith the specified CLIM name, or the specified CLIM name corresponds to a non-CLIM device,or the configured CLIM hardware with the specified CLIM name is configured with a differentoperation mode. There should also be a CIP subsystem event 5211 or 5237 that providesmore detailed information.EffectThe specified CLIM object cannot be accessed.RecoveryMake sure that the correct CLIM hardware is connected at the correct locations and that theCLIM and the ServerNet or InfiniBand switch are configured correctly. Make sure that the CLIMis configured with the correct name and operation mode via the Configure CLIM action. ForNonStop X systems, CLIM configuration is performed through the OSM System ConfigurationTool. For systems running and H- and J-series software, CLIM configuration is performedthrough the OSM Low-Level Link.

Origin “CIP Manager” Fault Code 10121012CauseThere are no active CIPMON processes running in any processor on the system. This is mostlikely caused by an operator request.

417

EffectNo access to any CLIM or provider from any processor.RecoveryMake sure that CIPMON processes are started by the persistent manager. See “Starting CIPon the NonStop Host System” (page 91) for information about how to start CIPMON processes.

Origin “CIP Manager” Fault Code 10151015CauseAn attempt to read or write a configuration database record by the CIPMAN process fails.EffectFor reading of a non-critical configuration database record, CIPMAN continues without accessto the object corresponding to the configuration database record. For a critical configurationdatabase record, CIPMAN terminates and the backup CIPMAN takes over.RecoveryNone. This is an informational event. However, if an existing CIP subsystem object (such asa CLIM or Provider) is unexpectedly missing, you may want to restart the CIPMAN process.

Origin “CIP Manager” Fault Code 10171017CauseA configured CLIM object is now unusable due to a mismatch between configuration on theCLIM and configuration on the NonStop System.EffectThe specified CLIM object cannot be brought to STARTED state.RecoveryMake sure that the configuration on the CLIM is consistent with the configuration of the CLIMobject on the NonStop system. In particular, if the CLIM is configured with MULTIPROV setto OFF, all network resources on the CLIM must not be associated with any specific provideror all network resources on the CLIM must be associated with the IPDATA provider specifiedby the PROVIDER attribute of the CLIM object.

Origin “CIP Manager” Fault Code 10181018CauseA configured CLIM object is now unusable because the version of software running on thatCLIM does not support one or more features (such as MULTIPROV support) that have beenturned on for that configured CLIM object.EffectThe specified CLIM object cannot be brought to STARTED state.RecoveryMake sure that the CLIM is running software that can support the feature sets configured forthat CLIM object or turn off features that are not supported by the software running on theCLIM using theSCF ALTER CLIM command.

Origin “CIP Manager” Fault Code 10191019CauseA configured CLIM object is now unusable due to CIPMAN receiving invalid CLIM-basedconfiguration information from the CLIM.

418 Fault Codes

EffectThe message is dropped without further processing. The specified CLIM object cannot bebrought to STARTED state.RecoveryCIPMAN will automatically retry the operation. However, if this problem persists over anextensive period of time, the operator should make sure that an appropriate version of thesoftware (CIPMAN, CIPMON, ZCIPDLL, CLIM) are running and make sure that the configurationon the CLIM is consistent with the configuration of the CLIM object on the NonStop system. Ifthe problem still persists, contact your Hewlett Packard Enterprise representative.

Origin "CIP Manager" Fault Code 10201020CauseA configured CLIM object is now unusable because the operation mode configured on CLIMdoes not match the operation mode for the CLIM object on the NonStop system.EffectThe specified CLIM object cannot be brought to a STARTED state.RecoveryMake sure that the operation mode configured on the CLIM is consistent with the operationmode of the CLIM object on the NonStop system. Operator will likely have to reconfigure theCLIM with the correct operation mode via the Configure CLIM action. If the problem stillpersists, contact your Hewlett Packard Enterprise representative.

Origin “CIPMON” Fault Code 20012001CauseAn unexpected failure condition was encountered by a CIPMON process.EffectThe CIPMON process terminates. In an extreme case, the CIPMON processor may be halted.RecoveryIf the CIPMON processor is not halted, no recovery action is required. The CIPMON processis restarted automatically by the persistence manager. If the CIPMON processor is halted,perform a dump operation and reload the processor.

Origin “CIPMON” Fault Code 20022002CauseThe CIPMON process either (a) attempts to obtain an invalid type of resource, (b) attempts touse resources that are not sufficient for the current operation, or (c) cannot obtain necessaryresources (such as memory). Check the EMS event for more details.EffectThe current operation by CIPMON fails.RecoveryNone. CIP subsystem should automatically recover. If this problem persists, make sure sufficientresources are available. Check the EMS event for more details about the type of resourcesthat caused the problem. If this problem persists for an extended period of time, report theproblem to your Hewlett Packard Enterprise service provider.

Origin “CIPMON” Fault Code 20032003

419

CauseCIPMON detects that the information within an internal control block is not consistent with whatis expected.EffectThe CIPMON processor is halted.RecoveryThis is a serious problem. Send complete information to your Hewlett Packard Enterpriseservice provider.

Origin “CIPMON” Fault Code 20112011CauseEither (a) CIPMON detects an attempt to access an invalid state machine, or (b) a state machinecorresponding to a CIP subsystem object within CIPMON is put in an unexpected state.EffectFor (a), the CIPMON processor is halted. For (b), the CIP subsystem object corresponding tothe affected state machine is no longer accessible through that CIPMON process.RecoveryThis is a serious problem. Send complete information to your Hewlett Packard Enterpriseservice provider for analysis.

Origin “CIPMON” Fault Code 20132013CauseThe CIPMON process receives a message from either the CIPMAN process or a CLIM withversion information that does not match what the CIPMON process expects.EffectThe message is dropped or rejected.RecoveryMake sure the correct and matching software is running on both the NonStop host system andon the CLIM.

Origin “CIPMON” Fault Code 20222022CauseThe CIPMON process receives a response message from a CLIM that has a CLIM type thatwas not expected for that type of request.EffectThe message is dropped.RecoveryMake sure the correct and matching software is running on both the NonStop host system andon the CLIM.

Origin “CIPMON” Fault Code 20302030CauseA CIPMON process in either the STARTING or STARTED state is incompatible with the currentCIPMAN process. The CIPMAN protocol version is newer than that CIPMON protocol version.

420 Fault Codes

EffectThe CIP subsystem does not function properly. If CIPMON is already in the STARTED state,the current socket operations might work correctly but there are not any recovery actions. IfCIPMON is in the STARTING state, the CIP subsystem access through that processor is notavailable and additional MON object transient faults (Origin “CIPMON” Fault Code 2032) arelikely to be generated.RecoveryInstall the correct, compatible versions of CIPMAN and CIPMON.

Origin “CIPMON” Fault Code 20312031CauseA CIPMON process in either the STARTING or STARTED state is incompatible with the currentCIPMAN process. The CIPMAN protocol version is older than that CIPMON protocol version.EffectThe CIP subsystem does not function properly. If CIPMON is already in the STARTED state,the current socket operations might work correctly but there are not any recovery actions. IfCIPMON is in the STARTING state, the CIP subsystem access through that processor is notavailable and an additional MON object transient fault (Origin “CIPMON” Fault Code 2033) islikely to be generated.RecoveryInstall the correct, compatible version of CIPMAN and CIPMON.

Origin “CIPMON” Fault Code 20322032CauseA CIPMON process in the STARTING state is incompatible with the current CIPMAN process.The CIPMAN protocol version is newer than that CIPMON protocol version.EffectThe CIP subsystem does not function properly. The CIP subsystem access through thatprocessor is not availableRecoveryInstall the correct, compatible version of CIPMAN and CIPMON.

Origin “CIPMON” Fault Code 20332033CauseA CIPMON process in the STARTING state is incompatible with the current CIPMAN process.The CIPMAN protocol version is older than that CIPMON protocol version.EffectThe CIP subsystem does not function properly. The CIP subsystem access through thatprocessor is not available.RecoveryInstall the correct, compatible version of CIPMAN and CIPMON.

Origin “CIPMON” Fault Code 20342034CauseA CIPMON process is taking unusually long time to process a set of requests. This can becaused by insufficient QIO memory resources.

421

EffectRequests that goes through that particular CIPMON (such as some sockets operations andsome SCF requests) can be slower than normal.RecoveryNone. CIP subsystem should automatically recover. If this problem persists, the operator shouldmake sure that sufficient QIO memory are available. If this problem persists for extended periodof time, please report the problem to your Global Customer Support Center analyst for analysis.

Origin “CIPSREQ” Fault Code 30013001CauseThe operation is invalid for the current state of the object within the CIP subsystem dynamiclink library (ZCIPDLL).EffectThe operation fails.RecoveryMake sure the correct and matching CIPMON and ZCIPDLL are running. If not, this is a seriousproblem. Send complete information to your Hewlett Packard Enterprise service provider foranalysis.

Origin “CIPSREQ” Fault Code 30023002CauseThe operation invoked by the CIPMON process is invalid for the object type of the specifiedobject.EffectThe operation fails.RecoveryMake sure the correct and matching CIPMON and ZCIPDLL are running. If not, this is a seriousproblem. Send complete information to your Hewlett Packard Enterprise service provider foranalysis.

Origin “CIPSREQ” Fault Code 30033003CauseA DSM trace request is not consistent with the current tracing status of the specified object.EffectTrace operation fails.RecoveryNone. This is an informational message.

Origin “CIPSREQ” Fault Code 30043004CauseThe maintenance Provider object still has an associated interface within the CIP subsystemdynamic link library (ZCIPDLL) and its configuration cannot be modified.EffectThe ALTER PROVIDER request fails.

422 Fault Codes

RecoveryIf this problem persists, send complete information to your Hewlett Packard Enterprise supportprovider for analysis.

Origin “CIPSREQ” Fault Code 30053005CauseOne or more parameters that CIPMON passed into the CIP subsystem dynamic link library(ZCIPDLL) are invalid.EffectThe operation fails.RecoveryMake sure the correct and matching CIPMON and ZCIPDLL are running. If not, this is a seriousproblem. Send complete information to your Hewlett Packard Enterprise support provider foranalysis.

Origin “CIPSREQ” Fault Code 30063006CauseThe specified object does not exist within the CIP subsystem dynamic link library (ZCIPDLL).EffectThe operation fails. The object cannot be accessed on that processor.RecoveryThis is a serious problem. Send complete information to your Hewlett Packard Enterprisesupport provider for analysis.

Origin “CIPSREQ” Fault Code 30073007CauseSome needed resources are not available to the CIP subsystem dynamic link library (ZCIPDLL).EffectThe operation fails.RecoveryNone. The CIP subsystem should automatically recover. If this problem persists, make suresufficient resources are available. Check the EMS event for more details about the type ofresources that caused the problem. If this problem persists for an extended period of time,report the problem to your Hewlett Packard Enterprise support provider for analysis.

Origin “CIPSREQ” Fault Code 30103010CauseThe CIP subsystem dynamic link library (ZCIPDLL) encounters too many errors incommunication with the specified CLIM object.EffectAccess to the CLIM is lost.RecoveryNone. The CIP subsystem should automatically recover.

423

Origin “CIPSREQ” Fault Code 30123012CauseAn unexpected error within the state machine occurred for the specified object within the CIPsubsystem dynamic link library (ZCIPDLL).EffectThe operation fails.RecoveryThis is a serious problem. Send complete information to your Hewlett Packard Enterprisesupport provider for analysis.

Origin “CIPSREQ” Fault Code 30173017CauseThe CIP subsystem dynamic link library (ZCIPDLL) received an updated IP address or route(add or delete) from the CLIM that is not consistent with what is expected.EffectThe IP address or route is not updated within the CIP subsystem dynamic link library (ZCIPDLL)in that processor.RecoveryIf the problem persists, a CLIM reboot is recommended.

Origin “CIPSREQ” Fault Code 30183018CauseThe size of the message the CIP subsystem dynamic link library (ZCIPDLL) attempted to sendto the CLIM is too large.EffectThe operation fails.RecoveryMake sure the correct and matching CIPMON, ZCIPDLL, and CLIM software versions arerunning. If mismatched versions are not the cause, this is a serious problem. Send completeinformation to your Hewlett Packard Enterprise support provider for analysis.

Origin “CIPSREQ” Fault Code 30203020CauseThe CIP subsystem dynamic link library (ZCIPDLL) receives a data message from the CLIMthat is too small.EffectAccess to the CLIM is lost.RecoveryMake sure the correct and matching software is running on both the NonStop host system andon the CLIM. If mismatched versions are not the cause, this is a serious problem. Send completeinformation to your Hewlett Packard Enterprise support provider for analysis.

Origin “CIPSREQ” Fault Code 30213021

424 Fault Codes

CauseThe CIP subsystem dynamic link library (ZCIPDLL) encounters a socket operation error thatrequires CLIM access to be disconnected.EffectAccess to CLIM is lost.RecoveryMake sure that the correct and matching software is running on both the NonStop host systemand on the CLIM. If the problem persists, send complete information to your Hewlett PackardEnterprise service provider for analysis.

Origin “CIPSREQ” Fault Code 30233023CauseThe CIP subsystem dynamic link library (ZCIPDLL) detects that there is no active connectionwith the CLIM.EffectAccess to the CLIM is lost.RecoveryNone. The CIP subsystem should automatically recover.

Origin “CIPSREQ” Fault Code 30243024CauseThe CIP subsystem dynamic link library (ZCIPDLL) detects that the specified CLIM has aninvalid operation mode or has an invalid associated PROVIDER object.EffectThe CLIM object is not added.RecoveryMake sure that the correct and matching NonStop host software (CIPMAN, CIPMON andZCIPDLL) are running. If mismatched software is not the cause, this is a serious problem.Send complete information to your Hewlett Packard Enterprise service provider for analysis.

Origin “CIPSREQ” Fault Code 30253025CauseThe CIP subsystem dynamic link library (ZCIPDLL) detects that the specified PROVIDERobject still has one or more associated CLIM(s) so the PROVIDER object cannot be deleted.EffectThe PROVIDER object is not deleted.RecoveryMake sure that the correct and matching NonStop host software (CIPMAN, CIPMON andZCIPDLL) are running. If the problem persists, send complete information to your HewlettPackard Enterprise service provider for analysis.

Origin “CIPSREQ” Fault Code 30263026

425

CauseTCP/IP parameters from the specified CLIM either do not match the TCP/IP parameters fromthe CLIM(s) associated with the same provider that are already started, or the ephemeral portsinformation is inconsistent with the SHARE-PORTS attribute of the associated provider.Details are given in ErrorDetails1, ErrorDetail2, and ErrorDetail3.ErrorDetail1

Is an item defined in a sysctl parameter, displayed in hexadecimal:

Items defined in sysctl parameter net.ipv4.tcp_rmem:

mismatch for minimum tcp receive buffer size0x01

mismatch for default tcp receive buffer size0x02

mismatch for maximum tcp receive buffer size0x04

Items defined in sysctl parameter net.ipv4.tcp_wmem:

mismatch for minimum tcp send buffer size0x08

mismatch for default tcp send buffer size0x10

mismatch for maximum tcp send buffer size0x20

Items defined in sysctl parameter net.ipv4.ip_local_port_range:

mismatch for starting ephemeral port number0x40

mismatch for ending ephemeral port number0x80

Item defined in sysctl parameter net.ipv4.ip_local_port_range and PROVIDER share-ports value:

ephemeral port range start or end exceeds 655350x100

Item defined in sysctl parameter net.core.wmem_default:

mismatch for default socket send buffer0x200

Item defined in sysctl parameter net.core.wmem_max:

mismatch for maximum socket send buffer0x400

Item defined in sysctl parameter net.core.rmem_default:

mismatch for default socket receive buffer0x800

Item defined in sysctl parameter net.core.rmem_max:

mismatch for maximum socket receive buffer0x1000

ErrorDetail1 can be an accumulated value. If ErrorDetail1 is equal to 9 (1 + 8),that means there is a mismatch between the minimum TCP receive buffer size and theminimum TCP send buffer size. ErrorDetail2 and ErrorDetail3 will show themismatch values of the last case, that is, the minimum TCP send buffer size.

ErrorDetail2Is the value of the ErrorDetail1 item set for the Provider.

ErrorDetail3Is the mismatched value for the reporting CLIM.

EffectThe CLIM is not accessible from that processor.RecoveryMake sure that TCP/IP parameters on all CLIMs associated with the same PROVIDER objectare identical. Also, make sure the ephemeral port ranges on all CLIMs associated with the

426 Fault Codes

same PROVIDER object are the same and leave enough ports between maximum ephemeralport number and maximum valid port number for the SHARE-PORTS.

Origin “CIPSREQ” Fault Code 30293029CauseThe CIP subsystem dynamic link library (ZCIPDLL) could not obtain sufficient memory toprocess the addition of a new local IP address or new route provided by the CLIM.EffectThe IP address or route is not added within the CIP subsystem dynamic link library (ZCIPDLL)in that processor.RecoveryNone. The CIP subsystem should automatically recover. If this problem persists, make suresufficient QIO memory is available. If this problem still persists, report the problem to yourHewlett Packard Enterprise service provider for analysis.

Origin “CIPSREQ” Fault Code 30303030CauseThe CIP subsystem dynamic link library (ZCIPDLL) encounters an error when it attempts tocommunicate with MEASURE.• ErrorDetail1 = -1 indicates MEASURE is too old to support the CIP subsystem.• ErrorDetail1 = 1 indicates MEASURE is too busy to process this request.EffectThe CLIM object cannot be added.RecoveryFor ErrorDetail1 = -1, check the version of MEASURE. For ErrorDetail1 = 1, retry the operation.For all other ErrorDetail1 values, send complete information to your Hewlett Packard Enterpriseservice provider for analysis.

Origin “CIPSREQ” Fault Code 30313031CauseThe CIP subsystem dynamic link library (ZCIPDLL) receives a local IP address from the CLIMthat already exists for a different interface within the same provider.EffectThe IP address is not associated with the interface specified in the message from the CLIM.RecoveryCheck configuration of all CLIMs associated with the same PROVIDER object to make surethe same local IP address is not associated with more than one interface for all associatedCLIMs.

Origin “CIPSREQ” Fault Code 30323032CauseThe CIP subsystem dynamic link library (ZCIPDLL) cannot support any more objects of thespecified object type.EffectThe specified object cannot be added.

427

RecoveryNone. This is an informational message. If a new object is needed, an existing object must beremoved first.

Origin “CIPSREQ” Fault Code 30333033CauseThe CIP subsystem dynamic link library (ZCIPDLL) encounters a check-sum error for a datamessage from the specified CLIM.EffectAccess to the CLIM is lost.RecoveryThis is most likely a hardware problem. If the problem persists for the same CLIM, have theCLIM hardware replaced. If the problem persists for multiple CLIMs, there may be a hardwareproblem associated with a NonStop host system processor. Contact your Hewlett PackardEnterprise service provider for support.

Origin “CLIMAGT” Fault Code 51205120CauseCLIM configuration information (most likely the CLIM name) within the current START CLIMrequest from the NonStop host system does not match the CLIM configuration information ofthe first successful START CLIM request received by the CLIMAGT. This indicates that differentNonStop host system processors are sending START CLIM requests to the CLIMAGT withconflicting CLIM configuration information.EffectThe current START CLIM request is rejected. The CLIM is not accessible from that NonStophost system processor.RecoveryThis is a serious problem. Send complete information (both NonStop host system and CLIM)to your Hewlett Packard Enterprise support provider for analysis.

Origin “CLIMAGT” Fault Code 51215121CauseThe processor number associated with the START CLIM request from the NonStop host systemis not valid (for example, not between 0 and 15).EffectThe current START CLIM request is rejected. CLIM is not accessible from that NonStop hostsystem processor.RecoveryThis is a serious problem. Send complete information (both NonStop host system and CLIM)to your Hewlett Packard Enterprise support provider for analysis.

Origin “CLIMAGT” Fault Code 51225122CauseThe CLIM name provided within the START CLIM request from the NonStop host system doesnot match the CLIM host name information.

428 Fault Codes

EffectThe current START CLIM request is rejected. The CLIM is not accessible from that NonStophost system processor.RecoveryMake sure that CLIM hostname information matches the CLIM name on the NonStop hostsystem .

Origin “CLIMAGT” Fault Code 51245124CauseCLIMAGT calls to the transport library results in an error. This is most likely caused by aninability to obtain necessary resources.EffectThe current CLIM request failed.RecoveryMake sure there is sufficient memory on the CLIM. If the problem persists, reboot the CLIM.

Origin “CLIMAGT” Fault Code 51255125CauseThe CLIMAGT encounters an error when it attempts to fetch detailed information about a CLIMfor which this CLIM has backup information. This is likely caused by a stale directory entryunder /etc/clim/mirror with no files in the subdirectory associated with that CLIM name.EffectThe CLIM configuration cannot be obtained. The CLIM cannot be brought to the STARTEDstate.RecoveryIf the problem persists, reboot all CLIMs associated with the IPDATA provider belonging tothe problem CLIM. If that does not work, contact your Hewlett Packard Enterprise serviceprovider.

Origin “CLIMAGT” Fault Code 51265126CauseThe CLIMAGT cannot allocate memory.EffectThe current CLIM request failed.RecoveryMake sure there is sufficient memory on the CLIM. If the problem persists, reboot the CLIM.

Origin “CLIMAGT” Fault Code 51275127CauseThe CLIMAGT did not receive configuration information from CLIMMON.EffectThe current CLIM request failed.

429

RecoveryCheck if the CLIMMON process is running. Restart the CLIMMON process if necessary. If theproblem persists, send complete information to your Hewlett Packard Enterprise service providerfor analysis.

Origin “CLIMAGT” Fault Code 51285128CauseThe NonStop host system processor that sends the current request is not in the STARTEDstate with respect to that CLIM, so the current request cannot be processed.EffectThe current CLIM request failed.RecoveryNone. The CIP subsystem should automatically recover. If the problem persists, send completeinformation, especially from the NonStop host side, to your Hewlett Packard Enterprise serviceprovider for analysis.

Origin “CLIMAGT” Fault Code 51315131CauseThe interface specified in the current request does not seem to be a configured interface.EffectThe current CLIM request failed.RecoveryCheck to make sure interface is configured using climconfig command.

Origin “CLIMAGT” Fault Code 51325132CauseThe interface specified in the current request has been stopped by the operator.EffectCurrent CLIM request failed. Interface cannot be brought to active state.RecoveryBring the specified interface to an operational state by using the ifstart command.

Origin “CLIMAGT” Fault Code 51335133CauseThe tunnel interface specified in current request has its parent interface in a non-active state.EffectThe current CLIM request failed. This tunnel interface cannot be brought to the active state.RecoveryNone. The CIP subsystem should automatically recover. If the problem persists, send completeinformation (especially on the NonStop host system side including CIPMAN) to your HewlettPackard Enterprise support provider for analysis.

Origin “CLIMAGT” Fault Code 51345134

430 Fault Codes

CauseThe visiting interface specified in the current request is associated with a local interface thatis currently not active. The visiting interface can be brought up on the backup CLIM only if itsbackup interface is active on the backup CLIM.EffectThe current CLIM request failed. The visiting interface cannot be brought to the active state.RecoveryNone. The CIP subsystem should automatically recover. If the problem persists, send completeinformation, especially on the NonStop host system side, including CIPMAN, to your HewlettPackard Enterprise support provider for analysis.

Origin “CLIMAGT” Fault Code 51355135CauseThe local interface associated with the visiting interface specified in the current request cannotbe determined.EffectThe current CLIM request failed. The visiting interface cannot be operated upon.RecoveryNone. Use the climconfig command to make sure the CLIM has correct and valid configurationinformation. If the problem persists, send complete information (including the CIPMAN on theNonStop host system side and the failover and interface configuration information on the CLIMside) to your Hewlett Packard Enterprise support provider for analysis.

Origin “CLIMAGT” Fault Code 51365136CauseThe interface specified in the current request has one or more associated tunnel interfacesstill in the active state.EffectThe current CLIM request failed. The specified interface cannot be brought to the inactivestate.RecoveryNone. The CIP subsystem should automatically recover. If the problem persists, send completeinformation, especially on the NonStop host system side, including CIPMAN, to your HewlettPackard Enterprise support provider for analysis.

Origin “CLIMAGT” Fault Code 51375137CauseThe interface specified in the current request has one or more associated tunnel interfaces.EffectThe current CLIM request failed. The current CLIM request failed. The specified interfacecannot be brought to the inactive state.RecoveryNone. The CIP subsystem should automatically recover. If the problem persists, send completeinformation (especially on the NonStop host system side including CIPMAN) to your HewlettPackard Enterprise support provider for analysis.

431

Origin “CLIMAGT” Fault Code 51525152CauseThe interface activation failed. This can be caused by an interface configuration problem, theinterface still being active on a different CLIM, or other internal problems.EffectThe current CLIM request failed. The current CLIM request failed. The specified interfacecannot be brought to the active state.RecoveryMake sure the CLIM has correct and valid configuration information (by using the climconfigcommand). Otherwise, the CIP subsystem should automatically recover. If problem persists,send complete information (including the CLIM’s syslog information) to your Hewlett PackardEnterprise support provider for analysis.

Origin “CLIMAGT” Fault Code 51845184CauseThe CLIM is running a new version of CLIM software and is configured for multiple Providers(MULTIPROV ON) but the NonStop system is running an older version of CIP Subsystemsoftware that does not support MULTIPROV capability.EffectThe current CLIM request failed. The CLIM cannot move to STARTED state.RecoveryMake sure that the NonStop system is running a newer version of the CIP subsystem softwarethat supports MULTIPROV capability.

Origin “ITAPI” Fault Code 99CauseThe underlying connection between a NonStop host processor and a CLIM breaks.EffectThat CLIM is not accessible from that NonStop host processor.RecoveryThe CIP subsystem should automatically attempt to re-establish an iT-API connection. If theproblem persists, the CLIM may be hung. In that case, a CLIM reboot is recommended.

Origin “ITAPI” Fault Code 81958195CauseThe IT-API connection between a NonStop host system processor and a CLIM has beendisconnected. (IT-API is the transport connection between the NonStop host system and theCLIM.)EffectThat CLIM is not accessible from that NonStop host system processor.RecoveryThe CIP subsystem should automatically attempt to re-establish the IT-API connection. If theproblem persists, make sure the CLIM is correctly configured. If the problem is related to amemory problem, reboot the CLIM.

432 Fault Codes

Origin “ITAPI” Fault Code 81968196CauseA CLIM process has rejected an IT-API connection establishment. This can be caused byrunning out of resources or a mismatch between the version of software on the NonStop hostsystem and on CLIM.EffectThat CLIM is not accessible from that NonStop host system processor.RecoveryMake sure the version of software running on the NonStop host system and the CLIM arecorrect and match with each other. Otherwise, if the problem is resources related and persistsfor an extended period of time, reboot the CLIM.

Origin “ITAPI” Fault Code 81978197CauseAn attempt to establish the IT-API connection between the NonStop host system processorand a CLIM has failed. ErrorDetail2 information within the EMS event specified the cause offailure in communication.• ErrorDetail2 = 1 indicates a connectivity problem between the NonStop host processor

and the CLIM.• ErrorDetail2 = 5 indicates the IT-API transport library on the CLIM cannot create the

necessary data structure.• ErrorDetail2 not present is the same as ErrorDetail2 = 0 and indicates the CLIM process

is not running on the CLIM.EffectThat CLIM is not accessible from that NonStop host system processor.Recovery

• For ErrorDetail2 = 1, make sure that the correct CLIM hardware is connected at the correctlocations. If the CLIM hardware is correctly connected, check to see if the CLIM isoperational, the CLIM driver is loaded and the CLIM processes are running (by using theclimstatus command) and start CLIM processes if necessary. If CLIM software processesare not running due to excessive failure, make sure the original failure was attended to,then issue the clim clearlog command followed by the clim reboot command to put theCLIM back in an operational state.

• For ErrorDetail2 = 5, the CIP subsystem should automatically attempt to reestablish theIT-API connection. If the problem persists, CLIM reboot is recommended.

• For ErrorDetail2 not present, which is the same as ErrorDetail2 = 0, make sure the CLIMprocesses are running (by using the climstatus command) and start CLIM processes ifnecessary. If CLIM software processes are not running due to excessive failure, makesure the original failure was attended to and then issue the clim clearlog followed by theclim reboot command to put the CLIM back in an operational state.

Origin “ITAPI” Fault Code 81988198CauseThe IT-API connection between the NonStop host system processor and the CLIM has beenbroken. This is most likely caused by failure of the ServerNet connection or failure of the CLIM.EffectThat CLIM is not accessible from that NonStop host system processor.

433

RecoveryNone. The CIP subsystem should automatically try to re-establish the IT-API connection. Ifthe underlying problem persists, the IT-API connection establishment attempt will likely fail. Inthat case, the problem is likely to show up as CLIM Transient Fault event (5201) with ITAPIfault code of 8197. Please follow the recovery action for that fault code in that situation.

434 Fault Codes

Index

Symbols#ZZCIP, 64$SYSTEM.ZTCPIP, 65$ZCLA collector, 99$ZPM, 64$ZZCIP, 214$ZZSTO, 198192.168.*.* address range restriction, 51, 3316763 CCSA, 209

AAbbreviations, SCF command, 215ABORT commands

SCF, CIPMAN, 218–220SCF, CIPSAM, 285

accessingupdates, 295

ADD commands, SCF, 220–226ADD DEFINE command

CIP^COMPAT^ERROR, 182HOST file, 66NODE file, 67RESCONF file, 68resetting, 163suppressing errors, 182TCI/IP process, 163, 197

ADD PROVIDER command, 223Address resolution protocol (ARP), 72all climconfig command, 309ALLNETSARELOCAL, not supported, 196ALTER commands, SCF, 226–227Application programming differences, 182–185Applications

and failover, 31–45and name resolution, 47, 69and services, 69migration, to CIP, 168monitoring, 86running in both environments, 105starting, IP CIP only, 93that need high bandwidth, 27

Approve command, LUN manager, 164arp Linux command, 59arp, climconfig command, 310ARPTIMER-REFRESHED, not supported, 195Authentication events, 99Autoconfigured IPv6 addresses, 36Automatic tunnels, not supported, 178AUTORESTART attribute, 64

BBacking up

best practice, 53, 59CLIM configuration, 107configuration files, 106

Best practice, backing up, 53, 59

Binaryfind command, LUN manager, 164Binding to a recently used address and port,

considerations, 184Bonded interfaces, 39, 177bondmode climconfig command, 312BRECVPORT attribute

compatiblity, 183definition, 224example, 236

Broadcast, behavior differences, 184

Ccat Linux command, 59CCMI (Command Control and Monitoring Interface), 139CCSA (Common Communication ServerNet Adapter),

209cd Linux command, 59certificate authorities, 47Certificate revocation list (CRL)

how stored, 95setting up links to, 96

Certificate signing request, 47Certificates, X.509, 95CIP commands, custom, 61CIP^COMPAT^ERROR, 182CIPMAN process

as persistent process, 91object, 212replacing CIPMAN and CIPMON simultaneously, 127stopping, 111

CIPMON processdetermining openers of, 109file, 126identifying applications using, 109persistent, 91replacing CIPMAN and CIPMON simultaneously, 127stopping, 111

CIPSAM processadding, 92data, default, 53determining name of, 109listing, 218maintenance, default, 53new error codes, 180object, definition, 213operational differences, 180persistence, 91replacing, 128

CLCI terminal emulation, 109Clear command, LUN manager, 164Clearlog command, 113CLIM

adding and starting, 123CLIM-to-CLIM failover, 32–35configuration, backing up, 107configuration, restoring, 107failover architecture, 31–45

435

multiple CLIMs per Provider, 27object, definition, 213SNMP support, 48software installation, 130stopping, 111Storage CLIM overview, 50timezone, 114valid locations, 221

clim command, 112, 298CLIM firmware

upgrade with system down, 162upgrade with system running, 144

CLIM Management Tool , 161, 162CLIM Management Tool, L-series RVUs, 128, 142, 160CLIM software

upgrade with system down, 161upgrade with system running, 130

CLIM software and firmware, upgrading, 128CLIM-to-CLIM failover

as initiated by SWITCH CLIM, 277compared to NONSHAREDIP, 196configuration example, 56how to set up, 87migration comparison, 177overview, 32–45

CLIMBKUP command, 106CLIMCMD command

case sensitive, 61clim, 112climstatus, 77, 113ifstart, 94ifstop, 95Linux subcommands, 59lunmgr, 164man page command, 21syntax, 61traceroute, 112

Climconfig commandsall command, 309arp command, 310bondmode command, 312climiptables command, 314failover command, 316hostname command, 319hosts, 320interface command, 323ip command, 330iptables command, 333, 345man pages, 307prov command, 356psk command, 358remote command, 360resolver, 365route command, 370sa command, 376slaveinterface command, 382snmp command, 385sp command, 387sysctl command, 392

tunnel command, 394vpn command, 397

climiptables, climconfig command, 314Climiptables, displaying with climstatus, 78Climprep

displaying CLIM configuration, 84displaying with climstatus, 78

CLIMRSTR command, 106CLIMSCMP tool, 115climstatus command, 77, 300CLSFTP script, 121CLuster I/O Module see CLIMcmd, Linux wrapper command, 114Coexistence

NonStop TCP/IPv6 and conventional TCP/IP, 105with conventional TCP/IP, strategy, 108

Command Control and Monitoring Interface see CCMICommon Communication ServerNet Adapter see CCSACompatibility, IP CIP

address bind limitations, 182ALLNETSARELOCAL, not supported, 196application programming differences, 182–187ARPTIMER-REFRESHED, not supported, 195automatic tunnels, 178binding to a recently used address and port, 184broadcast differences, 184DELAYACKS, not supported, 195DELAYACKSTIME, not supported, 195deleting ARP entries, 184failover differences, 177fault tolerant sockets, 178HOSTID, setting, 190HOSTNAME, setting, 190ICMP-FILTER-PKTS, 195ioctl and socket_ioctl calls, 184IPPROTO_TCP, 185IPSec, 169IRDP, not supported, 197link pulse down, 178MAX-EPHEMERAL-PORT, 190MAX-PRIV-PORT, not supported, 196maximum time for retransmission timeouts, 186migrating the environment, 197MIN-EPHEMERAL-PORT, 190minimum time for retransmission timeouts, 185MON/SUBNET attributes, 188moving from G4SAs, 177multicast bind, set or join, 183multicast loopback, 183multiple listeners, 29ND6HOSTD process, 169netmask and broadcast address, 185network partitioning, 176new error codes for aborted CIPSAM process, 180new error codes for IPSec, 178new socket option, 187new UDP error, 184NONSHAREDOUTDIST, not supported, 196operational differences, 169–181

436 Index

overview, 168–197PORT-SHARE-ENABLE-ALL, not supported, 196program name, 168receiving broadcasts on specific addresses, 183remote sockets, 178resources, 177retransmission timeout count, 185RFC1323–ENABLE, 190round-robin socket support considerations, 184routes, deleting and adding, 184routing differences, 177setsockopt calls, 185SLSA subsystem, 169, 176SNMP TCPIPSA subagent, 169socket loopback bind behavior, 180socket migration, 177socket option default differences, 187socket options, 185–187SPI subsystem ID, 168SUBNET object, 169subsystem name, 168subsystem number, 168, 171supported interface types, 168suppressing compatibility errors, 182system configuration database, 168TCP selective acknowledegments, 185TCP selective acknowledgements, 185TCP-INIT-REXMIT-TIMEOUT, not supported, 196TCP-MAX-REXMIT-COUNT, 191TCP-MAX-REXMIT-TIMEOUT, not supported, 196TCP-MIN-REXMIT-TIMEOUT, not supported, 196TCP-TOTAL-REXMIT-DURATION, not supported, 196TCP/IP attributes, 188–197TCP_MAXRXMT, 186TCP_MINRXMT, 185TCP_TOTRXMTVAL, 186TCPCOMPAT42, not supported, 197TCPCWNDMULTIPLIER, not supported, 196TCPKEEPCNT, 190TCPKEEPIDLE, 190TCPKEEPINTVL, 190TCPPATHMTU, 191TCPRECVSPACE, 191TCPSACKON, 192time to live, 189total time for retransmission timeouts, 186transport-service provider, 168UDP sockets, 183UDPRECVSPACE, 193UDPSENDSPACE, 193

Compatibility, Storage CLIMDisk Process 2 (DP2), 198IOAM operations comparison, 198NonStop SQL/MP, 198NonStop SQL/MX, 198overview, 198–199

Compatibility, Telco CIP, 209Configuration database, 63Configuration files

backing up, 106CLIM interface, 44failover, 42, 43HOSTS, 65IP addresses, 42IPNODES, 66IPSec, 46ipsec-tools, 46name resolution, 65NETWORKS, 68PORTCONF, 71psk.txt, 46RESCONF, 47restoring, 106security certificates, 46, 47SERVICES, 69TACLCSTM, 66

contacting Hewlett Packard Enterprise, 295Conventional TCP/IP, coexistence with, 105CPU dump, 208Current UDP sockets, 251customer self repair, 296

Ddate Linux command, 59Dedicated service LAN

maintenance LISTNER process for, 54maintenance TELSERV process for, 54

Default processes, 53DELAYACKS, not supported, 195DELAYACKSTIME, not supported, 195Delete command, LUN manager, 165DELETE commands, SCF, 228–229Destructive Linux commands, 59, 114DHCP, 22Differences, between TCP/IP products, 168Disk Process 2 (DP2), 198Displaying

CIPSAM process, 218CLIM configuration, 84CLIM status information, 77Ethernet LAN status information, 79failover configuration, 83hard disk space usage, 83IP routing table, 81IPSec configuration, 83kernel routing table, 81MON and MAN processes, 218NonStop X status information, 79ServerNet status information, 78SNMP information, 84

dmsg Linux command, 59documentation

providing feedback on, 296Domain Name Resolver (DNR)

and RESCONF file, 67default behavior, 66overview, 65

Domain Name System (DNS)

437

default behavior, 66, 67overview, 47

Down System CLIM Firmware Update Tool, 161, 162Down System CLIM Firmware Update Tool, H- and

J-series RVUs, 128, 160dump files, automatic or manual, 208dumping processors to CLIMs, 208

EEAGAIN error, 178Echo, 109Enclosures command, LUN manager, 165ENOPROTOOPT, 187Environment, home terminal, 108Ephemeral ports, 190Errors, suppressing, 182ESRCH error, 178Eth0, 23Eth0:0, 23Ethernet 4 ServerNet adapter, 105Ethernet LAN status information, 79Ethernet subagent (ETHSA), 48ethtool Linux command, 59ethtool, displaying link speed, 114Event logging, 113Event Management System (EMS)

documentation, 112using to monitor network, 111

Event messagesauthentication events, 99SCF, 399

FFailover

architecture, 31–45behavior, 177CLIM-to-CLIM, 32–35configuration, displaying, 83how to configure, 56interface, configuration sequence, 86interface-to-interface, 31optimizing for, 87settings, 87

failover, climconfig command, 316Falling back

multiple providers, 163to a previous CIP version, 163to a previous CLIM version, 163

Fast Ethernet ServerNet adapter (FESA), 105Fault tolerance

architecture, 31–45configuring, 86differences, 177

Fault tolerant sockets, not supported, 178Files

$SYSTEM.ZTCPIP, 65back up, 106CIPMAN, replacing, 127CIPMON, replacing, 126

CIPSAM, replacing, 128configuration, CLIM interface, 44configuration, failover, 45configuration, IPv4 and failover, 42configuration, IPv6 and failover, 43configuration, name resolution, 65HOSTS, 65IPNODES, 66IPSec, configuration, 46ipsec-tools, configuration, 46NETWORKS, 68NODES, 67PORTCONF, 71PROTOCOL, 69psk.txt, configuration, 46racoon, configuration, 46RESCONF, configuring, 67RESCONF, DNS use of, 47restore, 106security certificates, 46, 47SERVICES, 69SMPLHOST, 66SMPLNETW, 68SMPLPORT, 71SMPLPROT, 69SMPLRESC, 68SMPLSERV, 70TACLCSTM, 66

Find command, LUN manager, 165Finger, determining name of opener, 109Firmware

estimating update time, 148upgrading, 160upgrading from SPRs, 145upgrading with system running, 144with system running, 150

FORCED option, 218free Linux command, 59FTP, determining name of opener, 109Fully qualified domain names (FQDNs), 46

GGeneric CIP processes, 64getaddrinfo(), 67, 69getnameinfo(), 67getnetbyaddr(), 68getnetbyname(), 68getservbyname(), 69getservbynumber(), 69Gigabit Ethernet 4-port ServerNet adapter (G4SA), 105Gigabit Ethernet ServerNet adapter (GESA), 105grep Linux command, 59

HHard disk space usage, displaying, 83Hash names, IPSec, 96Help command, LUN manager, 165High UDP Sockets, 251Home terminal, 108

438 Index

Host nameCLIM, 72NonStop host system, 65

HOSTID, MON attribute, 190hostname, climconfig command, 319HOSTNAME, MON attribute, 190HOSTS file, 47see also ADD DEFINE commandDNS file, 67editing, 65

hosts, climconfig command, 320How to

activate an interface, 94add a default route, 56change interface configuration, 56change Providers for a CLIM, 123change TCP/IP environments for applications, 163configure CIP, 63configure eth2 through eth5 data interfaces, 56configure failover, 56create physical interfaces, 56deactivate an interface, 95define CIP management objects, 64determine openers of the process, 109determine your home terminal, 108display CLIM status information, 77, 85display link speed, 114display man commands, 85display SNMP info, 84display the IP routing table, 81edit the HOSTS file, 65enter CIP commands, 61fall back to a previous version, 163get a list of CIP processes, 218list applications using CIP, 109list CIPSAM processes, 109monitor the network, 111ping LISTNER and TELSERV processes, 58reboot the CLIM, 113replace CIPMON, 126restart CIP, 127select a CIP transport-service provider, 168set host names, 65stop CIP, 111test access to the network, 111trace a datagram's route, 112troubleshoot, 112upgrade, 126verify lunmgr configuration, 115

hplog Linux command, 59

IIB CLIM, 49ICMP TIME_EXCEEDED message, 112ICMP-FILTER-PKTS, 195ICMP_PORT_UNREACHABLE message, 112ifconfig -a Linux command, 60ifconfig interface-name Linux command, 60ifconfig Linux command, 60

ifstart command, 302activating an interface, 94overview, 94

ifstop command, 303deactivating an interface, 95overview, 94

INFO CLIM $ZZSTO, 198INFO commands

SCF, CIPMAN, 229–239SCF, CIPSAM, 285–290

INITIAL-TTL, MON attribute, 189Installing

CIP, 126CLIM software, 130

Integrated Lights Out (iLO)changing passwords, 54collecting logs, 204overview, 26

Interfaceactivating, 94deactivating, 95setting, on CLIM, 72

interface, climconfig command, 323Internet protocol security see IPSecINTFALL, 44IOAM comparison, Storage CLIM, 198Ioctl call, 184, 185IOCTL command differences

SIOCADDRT, 184SIOCDARP, 184SIOCDELRT, 184SIOCGIFBRDADDR, 185SIOCGIFNETMASK, 185

IP addresses, duplicate, 114ip Linux command, 60IP routing table information, 81ip, climconfig command, 330IP_RECVDSTADDR, 185IPNODES file, 47, 66, 67IPPROTO_TCP, 185IPSec

climconfig sp command, 387compatibility, 169configuration, 43, 44configuration, displaying, 83configuring, 95configuring remote information, 98configuring security associations, 97configuring security policies, 97controlling Virtual Private Network, 98displaying information, 78files, 46hash names, 96managing, 98new error codes, 178overview, 45–47sa climconfig command, 376

IPSEC, climconfig script, 99iptables, climconfig command, 333, 345

439

IPv6configuring, 104migration behavior of, 36

IT-API, 432

JJoined-group multicast IP addresses, 36Jumbo frames, 323

Ethernet interface, 168SCF ALTER command, 170tunnel interface, 395

KKernel routing table information, 81Kernel subsystem

CIP commands for, 91configuring CIP with, 64stopping, 127

LLed command, LUN manager, 166less Linux command, 60LIF, and older TCP/IP products, 105Limitations, 177Link speed, displaying, 114Link-local IP addresses, 36Linux commands

cmd wrapper, 114destructive, 59, 114logging, 114unsupported, 22using, 59

LISTDEV CIP and TCPIP command, 109, 163, 218Listeners, multiple, 29LISTNER process

checking, 58default process, 54maintenance, 54PORTCONF file, use of, 71starting, 93stopping, 111

LISTOPENS commandMON, 118MON, identifying applications using TCP/IP, 109PROCESS, 109SCF, 239–244

Logging, 113Logical interface (eth0:0), 23Logical network partitioning (LNP), 176, 177ls Linux command, 60Lunmgr

approve command, 164binaryfind command, 164clear command, 164commands, 164delete command, 165enclosures command, 165find command, 165help command, 165

led command, 166print command, 166renumber command, 166scan command, 166startover command, 166unblock command, 166update command, 167wwns command, 167

lunmgr configuration, 115

MMaintenance Entity Units (MEUs), 25, 208, 306Maintenance Provider

default, 53overview, 23

Man page instructions, 21Management objects, 64MAX-EPHEMERAL-PORT, 190MAX-EPHEMERAL-PORT, MON attribute, 190MAX-PRIV-PORT, not supported, 196MEU, 208see also Maintenance Entity Unit

Migrating to CIP, procedures, 197Migration, IP CIP

address bind limitations, 182ALLNETSARELOCAL, not supported, 196application programming differences, 182–187ARPTIMER-REFRESHED, not supported, 195automatic tunnels, 178binding to a recently used address and port, 184broadcast differences, 184DELAYACKS, not supported, 195DELAYACKSTIME, not supported, 195deleting ARP entries, 184failover differences, 177fault-tolerant sockets, 178getting netmask and broadcast address, 185HOSTID, setting, 190HOSTNAME, setting, 190ICMP-FILTER-PKTS, 195ioctl and socket_ioctl calls, 184IPPROTO_TCP, 185IPSec, 169IRDP, not supported, 197link pulse down, 178MAX-EPHEMERAL-PORT, 190MAX-PRIV-PORT, not supported, 196maximum time for retransmission timeouts, 186migrating the environment, 197MIN-EPHEMERAL-PORT, 190minimum time for retransmission timeouts, 185MON attributes, 188moving from G4SAs, 177multicast bind, set or join, 183multicast loopback, 183multiple listeners, 29ND6HOSTD process, 169network partitioning, 176new error codes for aborted CIPSAM process, 180

440 Index

new error codes for IPSec, 178new socket option, 187new UDP error, 184NONSHAREDOUTDIST, not supported, 196operational differences, 169–181operational differences, CIPSAM, 180overview, 168–169PORT-SHARE-ENABLE-ALL, not supported, 196program name, 168receiving broadcasts on specific addresses, 183remote sockets, 178resources, 177retransmission timeout count, 185RFC1323–ENABLE, 190round-robin socket support considerations, 184routes, deleting and adding, 184routing differences, 177setsockopt calls, 185SLSA subsystem, 169, 176SNMP TCPIPSA subagent, 169SO_ACCEPTCONN, 187socket IOCTL differences, 184socket loopback bind behavior, 180socket migration, 177socket option default differences, 187socket options, 185–187SPI subsystem ID, 168SPI subsystem number, 168, 171SUBNET object, 169subsystem name, 168supported interface types, 168suppressing compatibility errors, 182system configuration database, 168TCP selective acknowledgements, 185TCP-INIT-REXMIT-TIMEOUT, not supported, 196TCP-MAX-REXMIT-COUNT, 191TCP-MAX-REXMIT-TIMEOUT, not supported, 196TCP-MIN-REXMIT-TIMEOUT, not supported, 196TCP-TOTAL-REXMIT-DURATION, not supported, 196TCP/IP attributes, 188–197TCP_MAXRXMT, 186TCP_MINRXMT, 185TCP_TOTRXMTVAL, 186TCPCOMPAT42, not supported, 197TCPCWINDMULTIPLIER, not supported, 196TCPKEEPCNT, 190TCPKEEPIDLE, 190TCPKEEPINTVL, 190TCPPATHMTU, 191TCPRECVSPACE, 191TCPSACKON, 192total time for retransmission timeouts, 186transport-service provider, 168UDP sockets, 183UDP time to live, 189UDPRECVSPACE, 193UDPSENDSPACE, 193

Migration, Storage CLIMDisk Process 2 (DP2), 198

IOAM operations comparison, 198NonStop SQL/MP, 198NonStop SQL/MX, 198overview, 198–199

Migration, Telco CIP, overview, 209mii-tool Linux command, 60MIN-EPHEMERAL-PORT, 190MIN-EPHEMERAL-PORT, MON attribute, 190mkdir Linux command, 60MON object, 213Monitoring CIP, 85more Linux command, 60Multicast

loopback, migration considerations, 183migration consideration, 183

Multiple listeners, with round robin sockets, 29Multiple Providers

ADD CLIM guidelines, 222ADD ROUTE, 225ALTER CLIM command, 226ALTER CLIM guidelines, 226changing, 123DELETE PROVIDER guidelines, 229disabling MULTIPROV, 122enabling MULTIPROV, 122falling back, 163independent remote entries, 98independent security associations, 98IPSec configuration files, 46iptables/ip6tables (climiptables) support, 48network partitioning, 176policy based routing, 72pre-shared key configurations, 97routing, 30security policies, 97setting up, 122using, 29

Multiple Providers per CLIM, 28MULTIPROV attribute, 28

NNAMES commands

SCF, CIPMAN, 244–247SCF, CIPSAM, 290

Names, suggested, 215Naming conventions, 53, 214ND6HOSTD process, not supported, 169Netstat command, 173, 249netstat command, 77netstat Linux command, 60Network partitioning, 176, 177Network-sensitive commands, provider specified, 59, 77,

112, 119NETWORKS file, 68Nonsensitive commands, 217NONSHAREDIP failover option, alternatives in CIP, 177NONSHAREDOUTDIST, not supported, 196NonStop I/O Essentials, 26NonStop SQL/MP, 198

441

NonStop SQL/MX, 198NonStop system console, 22NonStop TCP/IPv6, coexistence with, 105NonStop X status information, displaying, 79Null object, 211

OObject specifiers, 215Object types

CIPMAN, 212CIPSAM, 213CLIM, 213MON, 213overview, 211ROUTE, 214SUBNET, 214

Object-name templates, definition, 215One-to-one SCTP associations, 104Online upgrades, 126OpenCall software, 23, 104, 126, 139Openers

of CIPMONs, 109of TCP/IP process, 109

Operator messages, 399

PPARAM command

adding for transport-service provider, 163, 197DELETE, 93for TELSERV, 93precedence, 67resetting, 163RESOLVER ORDER, 67TCPIP^PROCESS^NAME, 93ZTNT^TRANSPORT^PROCESS^NAME, 93

passwd Linux command, 60Passwords, changing, 54Path MTU discovery, 191PEM format, 95Persistence

on the CLIM, 26on the host, 63, 65

Persistence managerfunction, 106process, 64

Persistent processesbehavior, 91starting, 91stopping, 127

Physical interfaceseth0, 23fault tolerance, 177

Ping command, 111ping Linux command, 60ping6 Linux command, 60Policy based routing

description, 72enabling, 113troubleshooting, 76

PORT-SHARE-ENABLE-ALL, not supported, 196PORTCONF file, 71Pre-shared secret keys

configuring, 96description, 47file, 46

PRIMARY commandSCF, CIPMAN, 247SCF, CIPSAM, 290

Primary CPU, 108Print command, LUN manager, 166processes

aborting, 111PROTOCOL file, 69Protocols

IP, supported, 27Telco, supported, 27

prov, climconfig command, 356prov.1p command, 304PROVIDER object, 213psclim command, 306psclim script, for monitoring, 86psk, climconfig command, 358PuTTY, 96pwd Linux command, 60

RRacoon, errors, 178Rebooting the CLIM, 113, 154receive dump application, 208Remote socket, 178remote support, 296remote, climconfig command, 360RENAME command, 126Renumber command, LUN manager, 166RESCONF file

DNR use of, 66, 67DNS use of, 47see also ADD DEFINE commandsample on SUT, 68

Reserved names$ZZCIP, 214ZCMnn, 214

resolver, climconfig command, 365Restarting

CIP, 93CLIM, 93

RestoringCLIM configuration, 107files, 106

Retrans timer field, 87RFC1323–ENABLE, MON attribute, 190rm Linux command, 60rmdir Linux command, 60Round-robin

CLIM routing, 30filtering, 104socket support considerations, 184

ROUTE object, description, 214

442 Index

route, climconfig command, 370Routes

deleting and adding migration differences, 184migration differences, 177policy based, 72routing behavior, 29tracing, 112

RUN command, LISTNER, 93

SScan command, LUN manager, 166Scout, CLIM software, 131SCTP

adding to PROTOCOLs file, 69configuring, 104IPSec, 95

Security association (SA)configuring, 97

Security certificates, 47Security policy database (SPD), 97Sensitive commands, 217ServerNet LAN Systems Access (SLSA), not suported,

176ServerNet status information, displaying, 78SERVICES file, 69Setsockopt calls, 185, 187SFTP

copy trace file to host, 120entering commands with CLSFTP script, 121

Share-portsattribute restrictions, 227example, 236setting, 223

SHAREDIP failover option, alternatives in CIP, 177SIOCADDRT, 184SIOCDARP, 184SIOCDELRT, 184SIOCGIFBRDADDR, 185Size 3260 and larger socket statistic, 253Size x—xxxx socket statistic, 253slaveinterface, climconfig command, 382SLSA subsystem, not supported, 176SMPLHOST file, 66SMPLNETW file, 68SMPLPORT file, 71SMPLPROT file, 69SMPLRESC file, 68SMPLSERV file, 70SNMP

information, displaying, 84overview, 48supported classes, 47

snmp, climconfig command, 385SO_BROADCAST, 187SO_DONTROUTE, 186SO_PMTU

not supported for IPPROTO_TCP, 185not supported for SQL_SOCKET, 186socket option differences, 187

SO_RCVBUF, 187SO_SNDBUF, 187SO_USELOOPBACK, 186, 187Socket

loopback bind behavior differences, 180migration behavior, 177option differences, 185–187unsupported options, 185

socket_ioctl call, 184socket_ioctl_nw call, 184socket_set_inet_name() library call, 163socket_transport_name_set() library call, 163Software, upgrading, 160Solicited-node multicast IP addresses, 36sp, climconfig command, 387SPI subsystem ID, 168SPI subsystem number, 168START commands, SCF, 247–248Starting

CIP, 55CIP on the CLIM, 92CIP on the NonStop host system, 91

STARTMODE attribute, 64Startover command, LUN manager, 166State, summary, 216Static routes, 56STATS commands, SCF, 248–253STATUS CLIM

for monitoring, 86for storage ($ZZSTO), 198

STATUS commandsSCF, CIPMAN, 253–275SCF, CIPSAM, 291

STOP commandsLISTNER process, 111SCF, CIPMAN, 275–277SCF, CIPSAM,, 291TELSERV process, 111

Stoppinggeneric processes, 127interfaces, 95provider objects, 111

Storage CLIM configuration, 115Storage devices, suppported, 198Subsystem name, 168Subsystem number, 168Summary states, 216support

Hewlett Packard Enterprise, 295Supported interface types, 168Supported IP protocols, 27Supported Telco protocols, 27Suppressing compatibility errors, 182SWAN

configuring adapters on a CLIM, 181multiple paths in a single Provider, 29

SWITCH CLIM $ZZSTO, 198SWITCH command

definition and usage, 277

443

for storage subsystem, 198migration differences, 177

Synchronization of time on CLIMs, 114synopsis, climconfig command, 376sysctl, climconfig command, 392System configuration database

adding CIP processes to, 63managing, 105support comparison between products, 168

SYSTEM STARTMODE attribute, 64Systems Insight Manager (SIM), 26

TTACL

process, 108WHO command, 108

TACLCSTM file, 66Task summary

preparing to stop CIP, 108stopping generic process, 110

TCPsockets, failover migration behavior, 36time-to-live, 189

TCP-INIT-REXMIT-TIMEOUT, not supported, 196TCP-MAX-REXMIT-COUNT, MON attribute, 191TCP-MAX-REXMIT-TIMEOUT, not supported, 196TCP-MIN-REXMIT-TIMEOUT, not supported, 196TCP/IP process

avoiding stopping connection when stopping CIP, 108backward compatibility for INFO, 210determining openers of, 109migrating, 197NonStop host system management, 23obtaining list, 218

TCP/IP subagent (TCPIPSA), 48TCP_DROP_IDLE, 185, 187TCP_KEEPINIT, 185, 187TCP_MAXRXMT, 186, 187TCP_MINRXMT, 185, 187TCP_NODELACK, 186, 187TCP_PAWS, 186, 187TCP_PROBE_IDLE, 186, 187TCP_PUSH, 186, 187TCP_RPTR2RXT, 186, 187TCP_RXMTCNT, 185, 186, 187TCP_SACKENA, 185, 186, 187TCP_TOTRXMTVAL, 186, 187TCP_TSOPTENA, 186, 187tcpdump command, 118, 119tcpdump Linux command, 60TCPIP^HOST^FILE, 66TCPIP^NODE^FILE, 67TCPIP^RESOLVER^NAME, 68TCPIP^RESOLVER^ORDER PARAM, 67TCPKEEPCNT, MON attribute, 190TCPKEEPIDLE, MON attribute, 190TCPKEEPINTVL, MON attribute, 190TCPPATHMTU, MON attribute, 191TCPRECVSPACE, 191

TCPRECVSPACE, MON attribute, 191TCPSACKON, MON attribute, 192TCPSENDSPACE, MON attribute, 192tee Linux command, 60Telco CLIM, 23

deactivating signal link, 139upgrading, 138

TELNET, determining name of opener, 109TELSERV

checking process, 58default process, 54starting, 93stopping, 111

Templates for object names, 215TFTP, 22Time synchronization, CLIM, 114top Linux command, 61touch Linux command, 61TPNAME attribute, 64TRACE commands

SCF, CIPMAN, 278–283SCF, CIPSAM, 292

Tracer utility, 111Traceroute command, 112traceroute Linux command, 61traceroute6 Linux command, 61Transport-service provider

adding, 223associating with a CLIM, 176association with physical interfaces, 177changing, 163CIPSAM object, 213coexistence with conventional TCP/IP, 108default, 168defining, 163determining name of, 163falling back to conventional TCP/IP, 163for conventional TCP/IP, 210getting statistics on, 173getting status for, 174how to select for CIP, 168listing openers of, 172network monitoring, 111partitioning, 176procedure calls for setting, 163process, 169PROVIDER object, 213restricting access to, 176SCF object for, 213selecting, 168setting, 197stopping, 169, 175TPNAME attribute, 224TPName attribute, 235, 236

TrapdestsSNMP, configuring, 48SNMP, displaying, 78, 84

TroubleshootingCLIMCMD command, 113

444 Index

duplicate IP addresses, 114network applications, 118routing, 76tools, 112with tcpdump, 118

tunnel, climconfig command, 394

UUDP

BRECVPORT attribute, 224connect, failover behavior, 42defining, PROTOCOL file, 69displaying current sockets, 251displaying high sockets for, 251ephemeral ports, 224, 236errors, 184in sample protocol file, 69in SERVICES file, 70MAX-PRIV-PORT, not supported, 196ports

BRECVPORT attribute, 183defining use of, 224ephemeral, 190, 223finding, 118receiving broadcasts on specific addresses, 183setting, 223specifying for broadcast messages, 183

receive window size, setting, 193send window size, setting, 193share-ports, setting, 223socket migration issues, 183sockets, failover migration behavior, 36time-to-live, 189unreachable port, 184

UDPRECVSPACE, MON attribute, 193UDPSENDSPACE, MON attribute, 193Unblock command, LUN manager, 166Update command, LUN manager, 167updates

accessing, 295Upgrades, online, 126Upgrading CIP, 126Upgrading CLIM software and firmware, overview, 128

VValid CLIM LOCATION attributes, 221VERSION commands

SCF, CIPMAN, 283–285SCF, CIPSAM, 293

Virtual private network (VPN) control, 47Visiting resources, 177vmstat Linux command, 61vpn, climconfig command, 397

Wwc Linux command, 61websites, 296

customer self repair, 296WHO command, 108

who Linux command, 61Wild-card support, 215

XX.509 certificates, 95

ZZCMnn, 214

445