HP NonStop Cluster I/O Protocols (CIP) Configuration and Management Manual HP Part Number: 541613-024 Published: March 2014 Edition: J06.05 and subsequent J-series RVUs; H06.
© Copyright 2008, 2009, 2010, 2011, 2012, 2013, and 2014 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents About This Document...................................................................................13 Supported Release Version Updates (RVUs)................................................................................13 Intended Audience..................................................................................................................13 New and Changed Information................................................................................................
Configure the Eth1 Through Eth5 Interfaces (Does Not Apply to Storage CIP)..................................65 Configure CLIM-To-CLIM Failover (Applies to IP CIP Only, Not Storage CIP)....................................66 Check Network Applications (Does Not Apply to Storage CIP).....................................................68 3 CIP Configuration and Management...........................................................69 Using Linux Commands and Custom CIP Commands..................................
Logging Messages................................................................................................................113 Configuring IPv6 (IP CIP).......................................................................................................113 Running Applications in Multiple Environments (IP CIP)..............................................................113 Managing the Configuration Preservation................................................................................
5 LUN Manager for Storage CIP.................................................................170 Lunmgr Commands...............................................................................................................170 approve Command..........................................................................................................170 Binaryfind Command.......................................................................................................170 Clear Command.....................
Storage CIP Migration, Compatibility and Operational Differences...............204 8 Collecting Data for CLIM Issues................................................................206 Create CLIM Debug Information.............................................................................................206 CLIM Log Files......................................................................................................................206 Collecting CLIM Log Files using CLIMDBUG........................
PRIMARY Command, CIPSAM...........................................................................................287 STATUS Command, CIPSAM..............................................................................................287 STOP Command, CIPSAM.................................................................................................288 TRACE Command, CIPSAM...............................................................................................288 VERSION Command, CIPSAM..........
Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 OSM Service Connection displays for CIP...........................................................................31 Distribution of Functionality in the CIP Subsystem..................................................................32 Multiple CLIMs per Provider, Example Configuration.............................................................33 Multiple Providers per CLIM, Example Configuration..................................
20 21 22 23 24 25 26 27 28 29 30 TCP/IP Attributes, CIP Equivalents, and their CIP Default Values and Ranges..........................200 IOAM and CLIM Based Operations Comparison................................................................204 CLIM Based Operations Information.................................................................................205 IOAM and Telco CLIM Based Operations Comparison........................................................215 Commands and Object Types for CIPMAN...
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 INFO CLIM, Detailed, IP CLIM.........................................................................................236 INFO CLIM Detailed, Telco CLIM, OPEN MODE................................................................237 INFO CLIM Detailed, Storage.........................................................................................
93 94 95 96 97 98 99 100 101 102 103 104 105 VERSION MON Detailed................................................................................................281 VERSION PROCESS.......................................................................................................281 ABORT PROCESS...........................................................................................................281 INFO PROCESS (CIPSAM) Summary.......................................................................
About This Document This manual provides overview information about the HP NonStopTM™ 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 J06.05 and H06.16 and subsequent J-series and H-series RVUs until otherwise indicated in a replacement publication.
New and Changed Information in the 541613-022 Edition Authentication Events These are the updates associated with Authentication Events, effective with the H06.27/J06.16 RVU: • In Chapter 3, added new section “Configuring Transport of Authentication Events from CLIM” (page 108). IPSec Changes • In Chapter 1, added resources to table, “Interface Resource Failover Behavior” (page 40).
New and Changed Information in Previous Editions Changes to 541613-021 include: DL380p Gen8 CLIMs These are the updates associated with DL380p Gen8 CLIMs, which are effective with the H06.26/J06.15 RVU: • In Chapter 1 under “CLIMCMD Tool” (page 29), added Note and Example showing how to set the TACL parameter SUPPRESSCLIENTBANNER to display the SSH Client banner. • In Chapter 1 under “Integrated Lights Out (iLO)” (page 30), changed iLO 2 designation to iLO to include all iLO versions.
• In Chapter 3 under “On the CLIM” (page 86), indicated that the provider option must be used for CLIMs using the MULTIPROV ON option. • In Chapter 3, changed examples under: ◦ “Ethernet LAN Status” (page 88) ◦ “Kernel Routing Table Information” (page 89) ◦ “Hard Disk Space Usage” (page 91) ◦ “IPSec Configuration” (page 91) • In Chapter 3, deleted obsolete information from Example 13: “CLIM-to-CLIM Failover (IP CIP)” (page 95).
• In Chapter 10 under “LISTOPENS PROVIDER” (page 245), added the MULTIPROV option to the syntax. • In Chapter 10, made changes to several commands to support Multiple Providers per CLIM: ◦ “ADD CLIM” (page 226): Added the new MULTIPROV option and changed the PROVIDER option. Added a new section, ADD CLIM Guidelines. ◦ “ADD PROVIDER” (page 228): Modified the character length under prov-name to seven characters. ◦ “ADD ROUTE” (page 230): Changed the CLIM clim-name option to add the MULTIPROV option.
Man Page Updates for Multiple Providers per CLIM • Modified the following man pages under Climconfig (Man Pages) to support Multiple Providers per CLIM: ◦ climconfig.all(1) ◦ climconfig.arp(1) ◦ climconfig.bondmode(1) ◦ climconfig(1) ◦ climconfig.climiptables(1) ◦ climconfig.interface(1) ◦ climconfig.ip6tables(1) ◦ climconfig.iptables(1) ◦ climconfig.prov(1) ◦ prov(1p) ◦ climconfig.psk(1) ◦ climconfig.remote(1) ◦ climconfig.route(1) ◦ climconfig.sa(1) ◦ climconfig.
• In Chapter 4, added bullet to the Caution under “Upgrading CLIM Software and Firmware” (page 135). • In Chapter 4, changed information under “Preparing to Update CLIM Firmware with the System Running” (page 150) and “Firmware Update Time Estimates and Calculation Form” (page 154). • In Chapter 4, revised section “Upgrading CLIM Software or Firmware While the System is Down ” (page 165). • In Chapter 6, rewrote section “Network Partitioning Differences” (page 182).
◦ Added new man page, climconfig.iptables(1). ◦ Added new man page, climconfig.ip6tables(1). • For the failover command, climconfig.failover(1), updated error message to read: “Invalid destination interface, it should be one of the eth[1-n], bond[0-n] or ib[0-n].” • For the interface command, climconfig.interface(1), updated the -mtu parameter and error messages to indicate no support for InfiniBand. • For the sp command, climconfig.
• Updated climconfig.snmp(1). • Updated climconfig.sp(1). • Updated climconfig.sysctl(1). • Updated climconfig.tunnel(1). CLIM-to-CLIM Replication Replicate CLIM-to-CLIM updates include: • Added new subsection to Chapter 3: “Replicating the Configurations from One CLIM to Another CLIM” (page 99). OSM Down System CLIM Firmware Update Tool OSM Down System CLIM Firmware Update Tool updates include: • Rewrote and rearranged text concerning software and firmware updates in Chapter 4.
• Updated the “PARAMETERS” and “ERROR MESSAGES” section of the climconfig.interface(1) man pages. • Replaced instances of “net.ipv4.tcp_rfc1337” with “net.ipv4.tcp_window_scaling” as applicable. • Removed instances of “TCPTIMEWAIT”, as it is not supported for J06.10+ RVUs. Notation Conventions General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words.
| Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times.
?123 CODE 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 exactly as shown. For example: Backup Up. Italic Text Italic text indicates variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets Brackets enclose items that are sometimes, but not always, displayed.
Related Information Procedures that apply to the CIP subsystem but which are documented in other HP manuals are not duplicated here. This subsection provides a guide to those procedures and other related documentation. Related Documents CIP Subsystem Operations In addition to this manual, to operate the CIP subsystem, you may need to refer to the SCF Reference Manual for the Kernel Subsystem for information about managing persistence for generic processes.
HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to: pubs.comments@hp.com Include the document title, part number, and any comment, error found, or suggestion for improvement you have concerning this document.
1 Overview The Cluster I/O Protocols (CIP) subsystem provides a configuration and management interface for I/O on certain HP Integrity NonStop systems. To find out if your system supports CIP, see appropriate planning guide; for example, for NS16000 Series systems, see the NS16000 Series Planning Guide. You can also find information about which networking products are supported on your system in the NonStop Networking Overview.
The CLIM can be configured for: • IP protocols (IP CLIM and IP CLIM Carrier Grade (CG) IP CLIMs are configured with a Mode attribute of IP • Storage protocols (Storage CLIM and Storage CLIM CG) Storage CLIMs are configured with a Mode attribute of STORAGE • Telco protocols (Telco CLIM and Telco CLIM CG) Telco CLIMs are configured with a Mode attribute of OPEN • IB protocols (IB CLIM) IB CLIMs are configured with a Mode attribute of OPEN NOTE: To find out if your system supports Telco or IB CLIMs, se
NOTE: The physical interface eth0 connects each CLIM to the dedicated service LAN. Only IP and Telco CLIMs can have the logical interface eth0:0 and the associated maintenance Providers. NOTE: In this manual, unless stated explicitly otherwise, “Provider” refers to an IPDATA Provider. Maintenance Provider Restrictions • There is no failover support for the maintenance Provider. However, HP recommends configuring two maintenance Providers running on different CLIMs with different IP addresses.
NOTE: The default behavior of CLIMCMD is to not display the SSH Client banner. Effective with the J06.15 RVU, the SSH Client banner can be displayed in the output of CLIMCMD by setting the TACL parameter SUPPRESSCLIENTBANNER to ‘N’ before executing CLIMCMD. To revert to the default behavior, explicitly set the TACL param SUPPRESSCLIENTBANNER to any value other than ‘N’. For example: > $SYSTEM SYSTEM 25> climcmd N1002531 psclim PID RSS %MEM %CPU TIME START STAT CMD 4829 1024 0.0 0.
Figure 1 OSM Service Connection displays for CIP For more information about using the OSM Service Connection, see the OSM Service Connection User's Guide and the NonStop Operations Guide. The OSM Low Level Link is used to: • Configure CLIMs, as described in the CLuster I/O Module (CLIM) Installation and Configuration Guide. • Upgrade CLIM software, as described in Chapter 4 (page 133). HP NonStop I/O Essentials NonStop I/O Essentials is a plug-in to HP Systems Insight Manager (SIM).
Telco connectivity with management facilities and Telco applications on the NonStop host and Telco protocols on the CLIM. The CIP subsystem resides partly on the NonStop host system and partly on the CLIM. In the CIP subsystem, IP functionality is distributed between the NonStop system and the CLIM. Figure 2: Distribution of Functionality in the CIP Subsystem shows this distribution of functionality.
Figure 3 Multiple CLIMs per Provider, Example Configuration Multiple Providers per CLIM Effective with the H06.25/J06.14 RVU, a CLIM can be associated with multiple data providers simultaneously. You can enable or disable this Multiple Providers per CLIM functionality on a per-CLIM basis by setting a new MULTIPROV attribute of each CLIM object. The MULTIPROV attribute is not valid for a CLIM with STORAGE MODE. See “ADD CLIM” (page 226), “ALTER CLIM” (page 231), and climconfig.prov(1).
Figure 4 Multiple Providers per CLIM, Example Configuration Using Multiple Providers You 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. To associate a CLIM and all of its interfaces with multiple providers, set the MULTIPROV attribute of the CLIM object to ON using the ADD CLIM or ALTER CLIM command. See “ADD PROVIDER” (page 228) and “ADD CLIM” (page 226).
Network routes are configured on the CLIMs. You specify static routes by using CLIMCMD climconfig commands. Dynamic routes are created by the system as the result of various protocol events. CIP keeps separate routing tables for IPv4 and IPv6 destinations. Default routes have a prefix or subnet-mask length of zero and indicate where to send packets or connections when no other routes match the destination address. Default routes can be static or dynamic.
6. ROUTE PRIORITY attribute value are considered. If there is more than one with the same highest value, one is round-robin selected from that group. CLIMs with no ROUTE object are considered to have the lowest priority, and if those are all that are available, one of them is round-robin selected. If no available CLIMs have a default network-route entry, then no route can be found. Return an error to the application.
Figure 5 Intra-CLIM Interface Failover CLIM-to-CLIM Failover – Overview CLIM-to-CLIM failover is invoked when a CLIM fails, a non-slave physical interface or bonded interface fails, or an SCF SWITCH command is issued. Physical interfaces fail when their driver indicates a physical fault or link pulse remains down. Bonded interfaces fail when all their slave interfaces fail.
As of the H06.21 and J06.10 RVUs, CLIM-to-CLIM failover is supported for all types of 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 desired but fault handling must be done explicitly by the applications in that case.
Figure 7: Full CLIM Failover shows what happens when an entire CLIM fails. In the figure, CLIM2 has failed and the resources for all its interfaces have moved to interfaces in other CLIMs. The NonStop OS has updated its tables to refer to their new locations.
• “Fail Back (Restore Behavior)” (page 44) • “Failover Failure” (page 45) • “CLIM Startup Behavior” (page 45) Interface Names and Resources On the NonStop system, interfaces are given a unique name within a Provider by pre-pending the CLIM home interface name with the CLIM name and a period (.). For instance: n1002531.eth4 or n1012542.bond0. Physical and bonded interfaces are tied to physical ports and so cannot move in a literal sense.
Table 1 Interface Resource Failover Behavior (continued) Resource Created by Intra-CLIM Failover CLIM-to-CLIM Failover TCP connections Applications Shared Not migrated, client can reestablish the connections SCTP connections Applications Shared Not migrated, client can reestablish the connections Static IPv6-over-IPv4 Tunnels Configuration Shared Migrated when interface containing the local address is migrated IPSec PSKs Configuration Shared Not migrated, must be configured the same on the
Table 2 Interface Type for Failover Behavior Interface Type Characteristics Failover Loopback • Reflects output back to its input • Named lo Exists in every CLIM so failover is not needed. Cannot be configured for failover, but does have an entry in the NonStop OS interface table. • Corresponds to a physical Ethernet interface connected to a user network Can be configured for CLIM-to-CLIM failover. The backup interface can be a physical or bonded interface.
to the others. The number of bonded interfaces and the number of slaves in each is limited only by the number of data LAN interfaces on the CLIM. Typically, the bonded interface takes up the MAC address of its first slave. A bonded interface can be configured to use one of several policies for fault tolerance and bandwidth aggregation. CIP supports all current policy modes as long as their prerequisites are met. See “climconfig.bondmode Description” (page 306) for descriptions of the bonding modes.
Table 3 CLIM-to-CLIM Failover (continued) Failure Definition Probable Causes Resulting Failover Action CLIM-initiated interface down on a data LAN interface • CLIMCMD ifstop command No failover, but interface resources using the interface become unavailable. Failure indication, loss of link pulse, or CLIM-initiated interface down on maintenance interface • NIC hardware failure No action.
Failover Failure When a CLIM-to-CLIM failover operation is started, the host tries to migrate the resources to the failover interface and to the home interface alternately, separated by 10 seconds. If the resources are successfully brought up on one of the interfaces, failover is complete. If the resources cannot be brought up on either interface within 10 seconds, the failover has failed.
same IP address is re-created in the failover CLIM. Any state-changing operations done on the 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 but one CLIM if this was not already been done by a previous bind. Sockets associated with TCP and SCTP connections do not survive a failure.
Routes Static routes configured for an interface are migrated during failover. They are copied to the failover CLIM from the home CLIM as part of the interface configuration and are added when the failover logical interface is started. Dynamic routes were created as the result of information received from routers in the external network and are not failed over. The failover CLIM has or obtains similar information when it starts taking over the workload of the failed interface.
IPv6-over-IPv4 tunnel interfaces are not directly configured for failover; rather, they follow the interface containing their configured local address. The interface name configured on the home CLIM is used on the failover CLIM; therefore, tunnel interface names must not be the same on the home and failover CLIMs. Interface Status Control The CLIMCMD utilities ifstart and ifstop are provided to bring interfaces up and down, respectively.
IPSec security associations (SAs) can either be configured to be manually added to the security association database (SAD), with fixed predetermined secret keys, or can be configured to be automatically negotiated with the remote node. Since manually added SAs pose a security risk over a period of time, HP discourages this practice, and recommends configuration of automatically negotiated SAs instead.
File Description In CIP, Modify by using the... ipsec-tools.conf IPSec Security Policies (SPs) and manually configured Security Associations (manual SAs). “climconfig.sp Description” (page 364) and “climconfig.sa Description" (page 354)“climconfig.sa Description” (page 362)and “climconfig.sp Description” (page 372) psk.txt– pre-shared secret key for racoon IKE phase 1 The pre-shared secret keys are contained in the file psk.txt.
The Open System Services (OSS) environment inherits these Guardian-environment defines and also uses the RESCONF files. For information about using the resolver in applications, see the TCP/IP Programming Manual or the Open 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, see the Open System Services Management and Operations Guide.
customer data. (However, the Telco CLIM only supports copper Ethernet interfaces.) Another, built-in Ethernet interface can also be used for customer data. See the system planning guide for your system for more information about where the CLIM fits into your NonStop system. For carrier grade CLIMs, contact your service provider for more information. NOTE: The CLIM is intended only for the NonStop host system I/O functionality described in this manual. HP does not support any other use of the CLIM.
1 2 Slot 1: ServerNet PCIe card Slot 2: 2-port network interface card, from left to right: 2A: eth 4 3 4 5 6 7 8 9 10 11 12 2B: eth 5 Slot 3 (empty) Slot 4 (empty) Slot 5 (empty) Slot 6 (empty) Four ServerNet ports, from left to right: XB, YB, XA, YA LAN 4: eth 3 customer-usable interface LAN 3: eth 2 customer-usable interface ILO: Maintenance LAN interface LAN 2: eth 1 customer-usable interface LAN 1: Maintenance LAN interface.
2 Slot 1: ServerNet PCIe card Slot 2: One port network interface card: 3 2A: eth 4: customer-usable optical interface Slot 3: One port network interface card: 1 3A: eth 5: customer-usable optical interface Slot 4 (empty) Slot 5 (empty) Slot 6 (empty) Four ServerNet ports, from left to right: XB, YB, XA, YA LAN 4: eth 3 customer-usable interface LAN 3: eth 2 customer-usable interface ILO: Maintenance LAN interface LAN 2: eth 1 customer-usable interface LAN 1: Maintenance LAN interface.
Figure 13 DL380p Gen8 IP CLIM and Telco CLIM Interfaces, Option 2 Three Copper, Two Optical Interfaces 1 2 3 4 5 6 7 8 9 10 11 Slot 1: ServerNet PCIe card Slot 2 from left to right: Ethernet 5 and Ethernet 4 ports Slot 3: (empty) Ethernet 5 port Ethernet 4 port Four ServerNet ports, from left to right: AY, AX, BY, BX ILO: Maintenance LAN interface LAN 1: Maintenance LAN interface.
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 the CLIM, either through CLIMCMD or Nonstop I/O Essentials to configure and control iptables/ip6tables. • Automatic failover of iptables/ip6tables rules is not supported.
1 2 3 4 5 6 7 8 9 10 11 Slot 1: ServerNet PCIe card Four ServerNet ports, from left to right: XB, YB, XA, YA Slot 2 (empty) Slot 3 (empty) Slot 4: Two InfiniBand ports, from left to right: ib1, ib0 Slot 5 (empty) Slot 6 (empty) LAN 4: eth3 customer-usable interface LAN 3: eth2 customer-usable interface ILO: Maintenance LAN interface LAN 2: eth1 customer-usable interface LAN 1: Maintenance LAN interface.
Storage CLIM For 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 ports Figure 15: DL385 G2 or G5 Storage CLIM Interfaces (page 58) shows interfaces for the DL385 G2 or G5 Storage CLIM.
6 7 8 9 10 11 12 Slot 6 (empty) Four ServerNet ports, from left to right: XB, YB, XA, YA LAN 4: no connect LAN 3: no connect ILO: Maintenance LAN interface. LAN 2: no connect LAN 1: Maintenance LAN interface.
Component Product Number Socket access method T0693 Monitor processes, Library T0694 Subsystem Control Facility (SCF) product module T0695 Trace facility T0696 kIT-API software T0715 comForte SSH T0801 Storage CIP software T0830 CLIMCMD T0834 CLIM DVD installation software T0853 CLIM DVD source T0891 For descriptions of the manager, monitor, and socket access method processes, as well as the trace facility and SCF, see Chapter 10 (page 216).
Example of eth1 - eth5 or bond0 - bond1 Address Restriction When eth1 has an address in the 192.168.*.*/16 range, the dedicated LAN must not have an address in the 192.168.*.*/16 range. Example of Destination Restriction via Gateway When eth1 has an address of 10.10.10.10/16 and tries to communicate with a remote host which has an address in the 192.168.*.*/16 range, the dedicated LAN must not have an address in the 192.168.*.*/16 range.
2 Quick Start The installation of the CLIM is a service procedure; therefore, some basic configuration tasks have been performed. • Two CLIMs are connected to the NonStop host system. • Management facilities OSM and SCF are installed and configured on the NonStop host system. • 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.
Table 4 CLIM and Attached Storage Device Default Naming Conventions (continued) Resource Type Naming Convention Example Description corresponds to the same CLIM as N1002532.
Table 4 CLIM and Attached Storage Device Default Naming Conventions (continued) Resource Type Naming Convention WANBoot process Automatically created by WANMGR SWAN adapter Snumber 1 Example Description S19 Nineteenth SWAN adapter in the system The fiber number only applies to NonStop BladeSystems. CAUTION: Do not change the names of the $ZTCP0 and $ZTCP1 processes, as doing so could lead to internal errors.
• 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 passwd comForte SSH client version T9999H06_11Feb2008_comForte_SSH_0078 Enter new UNIX password: hpnonstop Retype new UNIX password: hpnonstop passwd: password updated successfully Termination Info: 0 3. Change the iLO and maintenance interface passwords for each CLIM.
NOTE: You must name physical interfaces eth1, eth2, eth3, eth4 and eth5 and bonded interfaces bond0 or bond1. These procedures assume you have two CLIMs, each configured with physical interfaces eth1 and eth2 and bonded interface bond0. This example shows how to change eth1 and eth2 on one 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 of qualifying the CLIM.
> DELETE CLIM N1002532 CIP E00015 CLIM $ZZCIP.N1002532 is associated with an existing Maintenance Provider object. 4. Find the associated Maintenance Provider: > INFO CLIM N1002532, detail CIP Detailed info CLIM \MYSYS.$ZZCIP.N1002532 Mode........................... Configured Location............ ConnPts........................ X1 Location.................... Y1 Location.................... SvNet ID 1.....................
N1002532 N1002531 IP IP (100 ,2 ,5 ,3 ,2) (100 ,2 ,5 ,3 ,1) 1 1 ZTC01 ZTC01 OFF OFF Configure two-way failover for the bond1 and eth4 interfaces from source N1002532 to target N1002531: > > > > CLIMCMD CLIMCMD CLIMCMD CLIMCMD N1002532 N1002532 N1002531 N1002531 climconfig climconfig climconfig climconfig failover failover failover failover –add –add –add –add bond1 -dest N1002531.bond1 eth4 -dest N1002531.eth4 bond1 -dest N1002532.bond1 eth4 -dest N1002532.
3 CIP Configuration and Management This chapter explains the tasks involved in configuring, running, and managing the CIP subsystem on the NonStop host system and on the CLIM. Tasks that are only relevant for IP CIP, Storage CIP or Telco CIP are identified throughout the text. For information about the LUN manager, see Chapter 5 (page 170). The tasks covered in this chapter are: CAUTION: Best Practice: You should always back up the configuration files after changing any configuration information.
Table 5 Sample Safe Linux Commands (continued) Linux Command Specify Provider Task Description Location ifconfig interface-name X Displays status for the given interface. See the ifconfig man page for more information. ifconfig -a X Displays status of all interfaces, even those that are down. See the ifconfig man page for more information. (other forms of this command are not supported) ip addr show X Displays all the IP addresses for each of the network interfaces.
Table 5 Sample Safe Linux Commands (continued) Linux Command Specify Provider traceroute X Prints the route that packets take to the network host. See the traceroute man page for more information. traceroute6 X Traces path to a network host. See the traceroute6 man page for more information. Task Description Location vmstat Reports virtual memory statistics. See the vmstat man page for more information. wc Prints newline, word, and byte counts for each file.
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 the IP address is specified, the command line interface uses SSH to run remote commands on the CLIM. For a MULTIPROV ON CLIM, -provider specifies the provider in which the command should be executed. If you omit command[arguments] from the CLIMCMD command, a list of supported Linux commands for the specified CLIM is displayed.
Configuring CIP Processes for Persistence Three types of CIP processes run on the NonStop host system: • CIPMAN. The CIPMAN process is the main management component on the NonStop host system side of the CIP subsystem. The CIPMAN object is the root of all other CIP configuration 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 on each NonStop host system.
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 for some 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 to the CIP subsystem on the NonStop host system.
Using the Domain Name Server is the preferred way of resolving names on the network. If a name 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 to your 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...] The IP_address is a 32-bit numeric value expressed in dotted decimal form.
# 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 16.107.182.52 grand-poohbah bobafet-xx 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.
Configure the RESCONF File The DNR resolves domain names to IP addresses using either DNS or a HOSTS file to provide the translation. If you did not set the TCP^HOST^FILE or TCP^NODE^FILE parameter, the DNR assumes it must use DNS. To determine which DNS to use, the DNR interrogates the RESCONF file. 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 IP addresses of DNS servers to consult.
# arpanet 10 arpa ucb-ether 46 ucbether Modify this file for your environment.
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 the service. Sample SERVICES File: SMPLSERV The site update tape (SUT) comes with a sample SERVICES file that is installed into $SYSTEM.ZTCPIP.
login shell printer courier uucp biff who syslog talk route new-rwho rmonitor monitor pcserver srvr ingreslock 513/tcp 514/tcp 515/tcp 530/tcp 540/tcp 512/udp 513/udp 514/udp 517/udp 520/udp 550/udp 560/udp 561/udp 600/tcp cmd spooler rpc uucpd comsat whod router routed new-who rmonitord # # # # no passwords used line printer spooler experimental uucp daemon # # # # experimental experimental experimental ECD Integrated PC board 1524/tcp You may need to edit the SERVICES file for the DSM/SCM Planner
On the CLIM Configuring the CLIM involves a variety of tasks: • “Setting the Host Name” (page 81) • “Defining Networking Interfaces (IP CLIM Only)” (page 81) • “Mapping IP Addresses to Ethernet Addresses (ARP) (IP CLIM Only)” (page 81) Setting the Host Name The 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).
Figure 18: Bound Socket Problem Configuration Without Policy Based Routing shows a bound 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 configured on the CLIM. • eth3 is activated first (non-deterministic). • The subnet route on eth3 is used for all outgoing connections to the network. • The socket is bound to the A.11, IP address on eth1.
Figure 19 Bound Socket Problem Configuration With Policy Based Routing Figure 20 (page 84) 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 configured on the CLIM.
Figure 20 Server Socket Problem Configuration Without Policy Based Routing With policy based routing enabled and no configuration change, the response is sent on the same interface that the request came in on, as shown in Figure 21 (page 85): 84 CIP Configuration and Management
Figure 21 Server Socket Problem Configuration With Policy Based Routing This CLIMCMD {clim-name | ip-address} climstatus -or report shows the additional tables created by policy routing: $SYSTEM.SABUN 22> climcmd n1002571 climstatus -or SSH client version T9999H06_21Jun2010_comForte_SSH_088 ------------------------------------------------------------------------------------IPv4 routing table TABLE main: 10.11.12.0/24 dev eth5 proto kernel scope link src 10.11.12.109 172.17.213.
Displaying the CIP Configuration This section describes how to display information on the NonStop host system and on the CLIM. On the NonStop Host System To display the configurations of CIP objects on the NonStop host system, use the SCF INFO command and specify the name of the object.
Displaying CLIM Status Information With climstatus The climstatus script displays status information for CLIM objects and devices, including the ServerNet, the Ethernet LAN, the kernel IP routing table, and hard disk drives. Invoke climstatus either from the command line by using the CLIMCMD command from TACL or (partially) from I/O Essentials. (I/O Essentials allows you to show Routing Table Information, which is equivalent to climstatus -o r).
CIP/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..................... STORAGE State.................... STARTED ConnPts.................. 2 X1 Location..............
Name lo Status UP LkP -- eth3 UP UP Master / IP Family & Address IPv4: 127.0.0.1 IPv6: ::1 IPv4: 172.17.190.
hoplimit 4294967295 Data Provider ZTC0 IPv4 Routing table TABLE main: 1.1.1.1 dev eth2 scope host metric 5 1.1.1.0/24 dev eth2 proto kernel scope link src 1.1.1.14 1.1.1.0/24 dev eth1 proto kernel scope link src 1.1.1.15 1.1.1.0/24 dev eth3 proto kernel scope link src 1.1.1.13 TABLE ETH1: 1.1.1.0/24 dev eth1 TABLE ETH2: 1.1.1.1 dev eth2 scope host 1.1.1.0/24 dev eth2 metric 5 TABLE ETH3: 1.1.1.
::1.2.3.4/128 U 0 0 ::3.4.5.6/128 U 0 0 ::4.3.2.1/128 U 0 0 ::16.107.192.195/128 U 0 0 ::127.0.0.1/128 U 0 0 ::172.17.190.2/128 U 0 0 ::172.17.190.5/128 U 0 0 ::172.17.214.50/128 U 0 0 3ffe:1200:aaaa:bbbb::/128 U 0 0 :: 2 lo 2 lo 2 lo 2 lo 2 lo 2 lo 2 lo 2 lo 2 lo :: :: :: :: :: :: :: :: Hard Disk Space Usage This display shows information pertaining to hard disk space usage. Example 7 Climstatus Command Hard Disk Space Usage \MYSYS.$SYSTEM.
out ipsec esp/transport//require created: Feb 8 14:54:57 2007 lastused: lifetime: 0(s) validtime: 0(s) spid=1 seq=1 pid=369 refcnt=1 10.3.3.2[any] 10.1.1.2[any] any fwd ipsec esp/transport//require created: Feb 8 14:54:57 2007 lastused: lifetime: 0(s) validtime: 0(s) spid=18 seq=0 pid=369 refcnt=1 --------------------------------------------------Data Provider ZTC0 Security Associations --------------------------------------------------10.1.1.2 10.3.3.
CLIMPREP Configuration: VERSION CONNECTED_GMS SYS_NAME SNET_SPEED NETWORK_CLIM DISK_CLIM NUM_SNET_CONN SWITCH_TYPE PCI_SLOTS 1 100.2.3.3.0 MYSYS 2 1 0 2 1 1.2C,2.1F,3.DC,4.1F,5.VO Displaying System Information Use the psclim tool to display system information about CLIM processes. The psclim command shows the process PID, memory used, percentage memory, percentage CPU time, accumulated CPU time, start time, run status, and start command. For field descriptions, see the ps(1) man page.
Monitoring CIP Because CIP resides on both the NonStop host system and the CLIM, monitoring it requires use of the Subsystem Control Facility (SCF) and the CLIMCMD CLI.
1. 2. 3. Use interface to add a bonded interface. Use ip to add an IP address to the bonded interface. Use slaveinterface to configure the bonded interface with multiple slave interfaces. With multiple physical interfaces configured for each bonding interface, when one physical interface 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 interface when using bond mode 1.
Netmask Details Route Type Destination Address Netmask Gateway Address Metric Minimum RTO InitCWND Auto Negotiation Details Status Line Speed Duplex Software MAC Address : : : : : : : : : : : : : : 255.255.252.0 Interface Interface IP Type Address Netmask : : : : eth0:0 Logical Interface 16.107.201.144 255.255.252.0 Type Size Address Netmask Details Route Type Destination Address Netmask Gateway Address Metric Minimum RTO InitCWND : : : : : : : : : : : : : ib1 Physical Interface 2044 16.107.201.
Metric Interface Interface Jumbo IP : : : : : : Type Frame Address Netmask 0 eth0:0 Logical Interface NO 192.168.36.11 255.255.0.0 Termination Info: 0 4. Set up bond mode C1002581 and C1002582 on LAN A: > > > > 5.
Figure 22 Configuration State 8. Configure failover on C1002581: > CLIMCMD C1002581 climconfig failover –add bond0 –dest C1002582.bond0c 9. Configure LAN B. > 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.
Figure 23 Configuration State Replicating the Configurations from One CLIM to Another CLIM To replicate any portion or the entire configuration from one CLIM to another CLIM, use the IN and 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.
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 shown in the second command, below. climconfig interface -add eth5 climconfig ip -add eth5 -ipaddress \ 172.18.7.5 -netmask 255.255.255.0 exit 2. Pass this file to the /IN/ run-option: CLIMCMD /IN config/ C1002581 Linux C1002581 2.6.
2. Add the CIPMON process to the system configuration database by using SCF to the kernel subsystem: > 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 by using SCF to the Kernel subsystem: > ADD PROCESS $ZZKRN.#CIPSAM, AUTORESTART 10, PRIMARYCPU 0,& BACKUPCPU 1, NAME $ZTC02, PROGRAM $SYSTEM.SYSTEM.
Restarting CIP on the NonStop Host System To restart the NonStop host system side of the CIP subsystem, you can stop and restart all the objects subordinate to CIPMAN. This is like a reboot of the subsystem; all active connections are stopped. CAUTION: If you are not running an alternative TCP/IP subsystem, connect to CLCI by using the OSM Low Level Link. (CLCI provides a primitive terminal emulation when no other TCP/IP subsystem is available, but has limited functionality.
CLIMCMD {clim-name | IP-address} ifstart interface interface Specifies the network interface name to be used by the NonStop host system for all interface functionality. 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.
Configuring IPSec (IP CIP) Internet protocol security (IPSec) provides application-transparent encryption services for IP network traffic. You can set up IPSec on an IP-address-to-IP-address basis, and optionally on a UDP 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 (Man Pages)” (page 301) for detailed syntax of the IPSec configuration commands.
Setting Up Links to the Certificate Revocation List (CRL) and to the Certificate Authority (CA) To set up links to the certificate revocation list (CRL) use this command (which executes using open SSL): 1. Create a TACL macro file called clinks (for example) with these lines (substituting real values for the parameters): ?tacl macro CLIMCMD %1% ln -s /etc/racoon/certs/%2% /etc/racoon/certs/`openssl x509 -noout -hash < /etc/racoon/certs/%2%`.
NOTE: There are independent security policy configurations for each provider when the MULTIPROV option is ON for a particular CLIM, and the -prov argument must be specified to select the desired provider's configuration.
NOTE: There are independent remote entries for each provider when the MULTIPROV option is ON for a particular CLIM. Climconfig Command Description remote –add Add remote entry into racoon.conf configuration file remote –delete Delete proposals for remote IP address from racoon.conf configuration file remote –info Display proposals and other configurations for the remote IP address from the racoon.
-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 CLIM The CLIM Authentication Transport feature transports the authentication events from the CLIM to the NonStop Host System. These authentication events record various security-related activities on the CLIM. For example, events are generated by the SSHD process running on the CLIM when a remote user attempts to log on to the CLIM.
TACL> #SET #INFORMAT TACL TACL> EMSDIST COLLECTOR $ZCLA, TYPE P, TEXTOUT [#MYTERM] Retrieving the Events from the $ZCLA by an Application This feature will allow security audit applications running on NonStop to access these logs and include them in the audit reports. The application can retrieve these events from the collector $ZCLA. Please refer to the EMS Manual for details on procedures to be used to retrieve the EMS messages from the alternative collector.
Climconfig Command Description climiptables -status Display the state of the climiptables climiptables -info Display the state of the climiptables and the iptables and ip6tables configurations climiptables -info -obeyform Generate obeyform lines for the current iptables and ip6tables configurations Configuring iptables/ip6tables The command syntax for climconfig iptables is climconfig iptables [HP options] arguments [-force] The command syntax for climconfig ip6tables is climconfig ip6tables [HP op
Chain CIP_INPUT (1 references) pkts bytes target prot opt in 18 972 ftp tcp -- any tcp dpts:ftp-data:ftp 4 224 telnet tcp -- any tcp dpt:telnet out any source anywhere destination anywhere any anywhere anywhere out source destination Chain ftp (1 references) pkts bytes target prot opt in out 2 120 REJECT all -- eth2 any reject-with icmp-port-unreachable source anywhere destination anywhere Chain telnet (1 references) pkts bytes target prot opt in out 1 60 REJECT all -- !eth2 any reject-with icm
10 2 528 snmptrap 117 snmptrap tcp udp --- any any Chain CIP_INPUT_p (1 references) pkts bytes target prot opt in any any anywhere anywhere anywhere anywhere out source destination Chain snmptrap (2 references) pkts bytes target prot opt in out 11 581 REJECT all -- any any reject-with icmp-port-unreachable tcp dpt:snmp-trap udp dpt:snmp-trap source destination !100.100.100.
endport. The =PTCPIP^FILTER^UDP^PORTS key limits the shared UDP ports to 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. If you 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.
Managing the Configuration Database on the NonStop Host System Save your configuration database before configuring CIP for the first time and record the name and date of the saved database. This saved configuration database can be used if higher RVUs of CIP are incompatible with the CIP records residing in the system configuration database. If a new RVU of CIP is incompatible with the data stored in the configuration database, you can restore the saved configuration database and reconfigure CIP.
clim-name Is the name of the CLIM to be backed up or restored. ip-address Is the IP address of the CLIM to be backed up or restored. hostname Is the hostname of the CLIM to be backed up or restored, without the subsystem qualifier. For example: C1002531. file-name Is the name of the file on the NonStop system in which the backup configuration is stored. If file-name is not specified, the default file name is BACKUPGZ.
The following table shows examples of behavior for the CLIMBKUP command and indicates differences in behavior between different releases: Example Command Backup File and Location (J06.06 and Behavior and File Backup Locations for H06.17 and later RVUs) Previous RVUs CLIMBKUP N1002531 $system.n1002531.backupgz Same CLIMBKUP N1002531 file-name $system.n1002531.file-name $current-vol.file-name.backupgz CLIMBKUP N1002531 subvol.file-name $system.subvolume.
a. Enter WHO at the TACL prompt: > WHO \HOME.$SYSTEM.SYSTEM 2> WHO Home terminal: $ZTNP1.#PTYPRAB TACL process: \HOME.$Z34A Primary CPU: 2 (NSR-G) Default Segment File: $SYSTEM.#0000382 Pages allocated: 24 Pages Maximum: 1024 Bytes Used: 32820 (1%) Bytes Maximum: 2097152 Current volume: $SYSTEM.SYSTEM Saved volume: $SYSTEM.SYSTEM Userid: 255,255 Username: SUPER.SUPER Security: "AAAA" Logon name: SUPER.SUPER The TELSERV process, $ZTNP1, is listed next to the HOME TERMINAL field.
$ZTN0 $ZTN0 $ZTN0 $ZTN0 $ZTN0 $ZTN0 $ZTN0 $ZTN0 $ZTN0 $Z07S 0,277 0,277 0,277 0,277 0,277 0,277 0,277 0,277 0,277 0,331 3 5 10 7 4 8 9 6 12 1 0 0 0 0 0 0 0 0 0 0 TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP telnet telnet telnet telnet telnet telnet telnet telnet telnet ftp In the above display, you would record all the opener processes: $ZPT0, $ZTN0, $ZTF0, $Z0KW, $Z0KX, $ZTN0, and $Z07S to be stopped.
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 the appropriate 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.
invoked when a CLIM stops because of issues in software. A snapshot file that captures the CLIM debug files is created when a CLIM has failed due to a software or hardware problem or when a CLIM is aborted by the operator by using the CLIMCMD clim abort command. The snapshot is created as /home/debuginfo/clim-date-time.tgz. (date-time is computed and replaced automatically).
> 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 info SSH client version T9999H06_21Jun2010_comForte_SSH_0088 policyRouting: Enabled Termination Info: 0 Event Logging The CIP subsystem generates NonStop host system reporting of CLIM issues.
Detecting Duplicate IP Addresses As of RVU J06.10 / H06.21, CIP detects duplicate IPv4 addresses and MAC addresses in 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 address may occur. This alarm must be manually deleted.
clim-name-1 Specifies the name of the first storage CLIM to be compared. clim-name-2 Specifies the name of the second storage CLIM to be compared. CLIMSCMP Considerations CLMSCMP must be run by a member of the SUPER group. CLIMSCMP displays its completion status with a message completion code. Successful termination results in a completion code equal to zero.
• Disk enclosure is configured but not connected to the CLIM: TACL> CLIMSCMP C1002581 C1002582 Warning: Enclosure disconnected from the CLIM 'C1002581' C1002581: lun type stable address serial # 200 1 enclosure 500143800045e880 --- revision --- Termination Info: -3 • Disk enclosure is connected to both the CLIMs, but not configured on one of the CLIMs: TACL> CLIMSCMP C1002581 C1002582 Error: Enclosure configured on the CLIM 'C1002581' but not on the CLIM 'C1002582' C1002581: lun 200 type 1
Termination Info: 0 CLIMSCMP Messages Error messages: • Error: Only SUPER group users are allowed to run '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 Network Applications Using Tcpdump To trace and collect network traffic, you can use the Linux tcpdump command. On systems running J06.06 or later J-series RVUs or H06.17 or later H-series RVUs, you can then transfer those files to the NonStop host. CAUTION: For pre-J06.06/H06.17 RVUs, do not use SFTP to transfer dumps and logs from CLIMs to the NonStop host system. The only supported SFTP application for transferring files between the CLIM and the console on pre-J06.06/H06.
>climcmd n1002582 mkdir /home/mylog comForte SSH client version T999H06_14Oct2008_comForte_SSH_0081 Termination Info: 0 > == List the directory and files > > climcmd N1002582 ls -lrt /home/mylog comForte SSH client version T999H06_14Oct2008_comForte_SSH_0081 total 0 2. Capture the data. 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.
NOTE: This SFTP syntax can be used for 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 tcpd10 comForte SSH client version T999H06_14Oct2008_comForte_SSH_0081 Connecting to 192.0.2.1...
$system.zservice.zclimid file shows the CLIM name to 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 ID N1002571 01 N1002573 02 N1002581 03 N1002582 04 N1002583 05 S1002531 06 S1002533 07 8 RECORDS TRANSFERRED Files named ‘ZCL04*’ belong to CLIM debug files from CLIM N1002582.
NOTE: An SCF PROVIDER object must also exist or be added. Disabling the MULTIPROV Attribute To disable MULTIPROV for an existing CLIM object, follow these steps: Example 17 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.
Example 18 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: > START CLIM $ZZCIP.clim-name > START PROVIDER $ZZCIP.
> SCF INFO PROVIDER $ZZCIP.prov-name, DETAIL b. Delete the unused providers: > > > > SCF SCF SCF SCF STOP PROVIDER $ZZCIP.prov-name ABORT PROCESS $ZZKRN.process-name DELETE PROCESS $ZZKRN.process-name DELETE PROVIDER $ZZCIP.prov-name For detailed information on how to use these commands, refer to “SCF Reference for CIP” (page 216) and “CLIMCMD and CLIMCMD climconfig Commands (Man Pages)” (page 290).
4 Upgrading CIP This chapter provides procedures for online upgrading of CIP on the host and both online and down system methods for upgrading CLIM software and firmware (see “Upgrading CLIM Software and Firmware” (page 135)). This chapter also provides information on falling back to previous TCP/IP subsystems and provides a pointer to information on falling back to previous CLIM versions if needed. Each procedure stands alone.
> ABORT MON $ZZCIP.ZCMprocessor-number Open connections still exist, okay to continue? Y 7. 8. The CIPMON processes are restarted automatically. Check to make sure each one is up before doing the next one. Restart the measure subsystem. Replace CIPMAN (Only) TCP/IP socket connections are not lost during this procedure. Storage paths are also unaffected by this procedure. 1. Rename the existing CIPMAN file by using the TACL command: > RENAME $SYSTEM.SYSnn.CIPMAN, $SYSTEM.SYSnn.CIPMANx 2. 3.
> START PROCESS $ZZKRN.CIPMON 13. Restart the Measure subsystem. CAUTION: You must connect to CLCI by using the OSM Low Level Link to perform this procedure. (CLCI provides a primitive terminal emulation when TCP/IP subsystem is available, but has limited functionality.) To connect to CLCI using OSM Low Level Link: From the File menu, select Start Terminal Emulator > For Startup TACL. This launches a CLCI TACL session. Replace CIPSAM TCP/IP socket connections are lost during this procedure.
system down time, such as during RVU upgrades. As a result of this new option, this chapter now contains completely separate procedures for: • “Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic” (page 136) • “Upgrading CLIM Software or Firmware While the System is Down ” (page 165) 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.
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 1. 2. 3. 4. 5. 6.
2. Click the setup icon, then follow the prompts to load the CLIM software on the system console. NOTE: The download from Scout of T0853 provides all necessary components. Identifying the Target Software 1. 2. 3. List the existing software versions for all CLIMs by using the SCF VERSION CLIM $ZZCIP.* command. List the available software version for the CLIM available on the NonStop console by using OSM Low-Level Link.
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.
NOTE: The STATUS CLIM $ZZSTO.clim-name shows the status of the disk volumes belonging to this CLIM and shows the active path (denoted by the asterisk (*) in the State field). 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 , DETAIL STORAGE - Detailed Status CLIM \MYSYS.$ZZSTO.
Table 8 Sample populated Storage CLIM upgrade form CLIM name Type S1002531 St Running Maint Prov? If yes, which Storage one? path B/up CLIM name P B/up Switch CLIM CLIM and abort Upgrade restarted started ? done ? done ? ? S1002533 Y S1002531 Y Normal operations resumed? Y MB S1002533 St B M i. Continue with “2. Upgrade the Storage CLIM” (page 141). 2. Upgrade the Storage CLIM a. b.
> RESET DISK $DATA00-MB > START DISK $DATA00-MB STORAGE W01001 To START the disk, SCF must revive the information on \MYSYS.$DATA00-MB. This operation might IMPACT system performance, 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 storage subsystem. > STATUS CLIM $ZZSTO.S1002531 , DETAIL STORAGE - Detailed Status CLIM \MYSYS.$ZZSTO.
h. i. Update the form. 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 upgrade operations until all Storage CLIMs are upgraded. Upgrading IP CLIMs CAUTION: During this procedure, the IP CLIM loses connectivity. 1. Prepare IP CLIMs for Upgrade (skip if the host system is not running) This example shows the preparation step for a failover-configured CLIM.
N1002582.bond0 N1002582.bond1 N1002582.eth3 T N1002541.tun624 N1002541.bond0 N1002541.eth3 N1002541.eth2 N1002541.eth1 d. UP UP UP UP UP UP UP UP UP UP UP UP UP UP UP UP N1002541.bond0 N1002541.eth1 N1002541.eth3 (N1002541.eth2) N1002582.bond0 N1002582.eth3 UP UP UP -UP UP --- UP UP UP -UP UP --- N1002541.bond0 N1002541.bond1 N1002541.eth3 N1002541.tun624 N1002541.bond0 N1002541.eth3 N1002541.eth2 N1002541.eth1 BkOP BkOP BkOP -Home Home --- Abort the CLIM. > ABORT CLIM $ZZCIP.
N1002541.eth3 N1002541.eth2 N1002541.eth1 UP UP UP UP UP UP N1002582.eth3 UP --- UP --- N1002541.eth3 N1002541.eth2 N1002541.eth1 Home --- N1002582.bond0, N1002582.bond1 and N1002582.eth3 have a status of UP, show Home in the Fovr field and show themselves as the current interfaces in the Current field. They have been restored to the default. You have now completed the procedure for upgrading an IP CLIM. Continue upgrade operations until all IP CLIMs are upgraded.
e. f. Depending on your Method of Procedure, if appropriate, deactivate the signal link provided by the CLIM you are about to upgrade by using CCMI. (The syntax for the instructions are in the online help.) Abort the CLIM. > ABORT CLIM O1002571 Open connections still exist, okay to continue? Y g. Check that the CLIM was stopped. > STATUS CLIM O1002571 CIP Status CLIM Name Present O1002571 Yes h.
You have now completed the procedure for upgrading a Telco CLIM. Continue upgrade operations until all Telco CLIMs are updated. Updating CLIM Software Using the OSM Low-Level Link 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 the Configure box. Click OK. 4.
6. Click Update. 7. Follow the instructions displayed by OSM Low-Level Link to reboot the CLIM.
8. 9. Click OK. Check the status in the log and ensure it shows that the software passed and that the version matches what you selected.
10. Click Reboot. 11. To check the CLIM status, log onto its iLO and use the psclim command. 12. To check the version, from the iLO, use the cat /etc/vproc command. The version should match your new version. 13. Update the form. 14. Continue with the resume normal operations step for your CLIM type. Upgrading CLIM Firmware with the System Running NOTE: This is no longer the best method to update CLIM firmware during an RVU upgrade.
6. Click OK to dismiss both the Java Runtime Settings and Java Control Panel dialog boxes. 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 may be rebooted automatically.
CLIM Firmware Updates with the System Running” (page 155)), and not bring down both 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 and backup 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 CLIM Attached Disk.
2. Divide all the Storage CLIMs into two groups such that the same group does not have both CLIMs configured as primary and mirror paths for the same disk.
• 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 and system name removed): In this example, CLIMs C1002581 and C1002583 implement the $ZTCP0 and $ZTCP1 processes. Estimating Time for CLIM Firmware Updates You can use Table 11 (page 154) to estimate the total amount of time needed to update the specified components in your environment.
Table 11 Firmware Update Time Estimates and Calculation Form (continued) Estimated time for your environment (fill in the value based on the information in the previous columns) Object T# Number of components updated SAS HBA Firmware T0842 1 2 to 4 Single update >1 2 to 4 minutes per SAS HBAs to be updated This firmware is updated serially. 1 2 to 4 Single update >1 2 to 4 minutes per SAS HBAs to be updated This firmware is updated serially.
g. h. Click Perform Action. Check the estimated time in Table 11 (page 154) 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 component shows the individual resource action result. Click Action Summary to view the summary of all the actions performed on the system. If this is the only firmware being updated, only an iLO reset is required. 2. 3.
d. e. Click Perform Action. Check the estimated time in Table 11 (page 154) 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 Firmware Compare State attribute as Down-rev. e. Add the selected CLIM NICs to the bottom pane. f. Click Perform Action. g.
d. e. f. g. Select all the SAS Disk Enclosures that show the Firmware Compare State attribute as Down-rev. Add the selected SAS Disk Enclosures to the bottom pane. Click Perform Action. Check the estimated time in Table 11 (page 154) 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.
g. h. Wait for the updated CLIMs to return to the STARTED state, determined by using the SCF STATUS CLIM $ZZCIP.* command to find the current status 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.
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. Click Remove All to clear the bottom pane. Switch away the paths of the second group of Storage CLIMs to be updated. a.
NOTE: Examples of Storage CLIMs not in fault-tolerant configurations include Storage CLIMs that are connected to a disk or tape that has no functioning backup path. If you have disks that do not have a backup path, only update the primary Storage CLIM that provides its path after planning 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.
4. For each CLIM in the group, perform “3. Resume Storage CLIM Normal Operations (skip if the host system is not running)” (page 141). Upgrading Groups of IP CLIMs CAUTION: When upgrading multiple IP CLIMs at a time, do not upgrade the one where $ZTC0 is configured or you will lose your session. 1. 2. See steps 1 - 2 of “1. Prepare IP CLIMs for Upgrade (skip if the host system is not running)” (page 143) to determine which IP CLIMs are configured as failover pairs then return to this procedure.
*BRecvPort................. No Ports Specified *CLIM...................... N1002581 *IPAddress................. 192.168.36.10 > INFO PROVIDER $ZZCIP.ZTCP1 , DETAIL CIP Detailed info PROVIDER \MYSYS.$ZZCIP.ZTCP1 *TPName.................... Type...................... *HostID.................... *Hostname.................. *TCP-Listen-Que-Min........ *BRecvPort................. *CLIM...................... *IPAddress................. $ZTCP1 MAINTENANCE 0.0.0.0 osmlany 128 No Ports Specified N1002582 192.168.
Table 13 Sample populated IP CLIM group upgrade form Running Maint Prov? If yes, B/up which Storage CLIM one? path B/up CLIM name started ? CLIM name Type Group N1002541 IP A N1002542 IP B N1002581 IP B ZTCP0 N1002582 IP A ZTCP1 N1012581 IP N1012582 IP N1002582 Switch and CLIM Normal abort Upgrade restarted operations done ? done ? ? resumed? Y N/A N/A N1002541 Y A N1012582 Y B N1012581 Y 10. Return to steps 3 - 5 of “1.
Upgrading Multiple CLIMs of Different Types 1.
requisite software, and also perform an action in the OSM Service Connection before halting the system: • OSM Service Connection, T0682 H02 ACV or later This SPR must be installed on $SYSTEM.SYS00 (having it in any other $SYSTEM.SYSnn is insufficient) for the Down System CLIM Firmware Update to work correctly. • OSM Console Tools product T0634 G06 ABB and later • SSH product T0801 ABA or later • Update OSM Low Level Link to the requisite version as specified in the T0853 softdoc.
d. Click Update. When the update is complete, it displays a dialog box stating that the update is complete. e. Click OK. f. Click Reboot in the I Software Update dialog box. OSM Low-Level Link automatically logs you off after the reboot. Update CLIM Firmware on a Down System Use the Down System CLIM Firmware Update Tool, located on the NonStop system console, to perform the firmware updates.
Down System CLIM Firmware Update action before halting all processors, as described in “Prepare CLIMs for Down System Firmware Update” (page 166). Use the Down System CLIM Firmware Update Tool, installed on NonStop system consoles as part of the OSM Console Tools product T0634 G06 ABB (and later), to perform the CLIM firmware updates. The Down System CLIM Firmware Update Tool is launched from the Windows Start menu by selecting All Programs > HP OSM > Down System CLIM Firmware Update Tool.
Falling Back to Previous RVUs that Support the Multiple Providers per CLIM Feature You can fall back to a previous RVU that is supported by Multiple Providers per CLIM, but keep an IP and OPEN MODE (Telco or IB) CLIM at the new level if it is either configured with MULTIPROV OFF, or you install the minimum SPRs to support the Multiple Providers per CLIM feature along with that RVU. Although Multiple Providers per CLIM support is effective with the J06.14/H06.
5 LUN Manager for Storage CIP In addition to this manual, see the SCF Reference Manual for the Storage Subsystem for commands such as STATUS CLIM, INFO CLIM, and configuring a disk or tape through a CLIM. Lunmgr Commands The lunmgr manages the LUN number assignments that the CLIM uses to communicate with the NonStop host system.
lun Is 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 Command Displays the enclosure table and enclosures present. The syntax is: -e | --enclosures Example of Lunmgr Enclosures Command Verify that the CLIM can see the corresponding ESS port WWN and that it is in the CLIM's enclosure table with the lunmgr --enclosures command.
-l lun { on | off } | --led lun { on | off } lun Is a decimal LUN number. Print Command Displays a device LUN table entry from kernel memory. If no LUN is specified, display the entire device LUN table. The syntax is: -p [lun]| --print [lun] If no lun is specified, find all devices. Renumber Command Renumber an old enclosure base LUN to a new value. This command fails if any device in the old enclosure has an I/O operation outstanding or there is already an enclosure with the new LUN value.
• Assigns new Storage CLIM LUN numbers to previously unknown storage devices. • Recognizes the CLIM boot disk and excludes it from the LUN Table. The syntax is: -u [ verbose ]| --update [ verbose ] Verbose Displays the device table and devices present. Considerations for the Update Command Only 512 devices per CLIM are supported. If the device table is full, lunmgr displays this error message on the screen and in the NonStop host system EMS log: Can't add lun lun_number. 512 devices already in table.
6 IP CIP Migration, Compatibility and Operational Differences The same methods of specifying a NonStop TCP/IPv6 transport-service provider are available for CIP. Once CIP is installed, applications can use CIP by specifying a CIPSAM process name as their transport-service provider. An application can change transport-service providers while running and can also have sockets using conventional NonStop TCP/IP, NonStop TCP/IPv6 and CIP at the same time.
Table 16 High-Level Differences Between Conventional TCP/IP, Parallel Library TCP/IP, NonStop TCP/IPv6, and CIP (continued) Conventional TCP/IP Parallel Library TCP/IP NonStop TCP/IPv6 CIP Transport service provider process: TCP/IP PROCESS object Transport service provider process: TCPSAM PROCESS object Transport service provider process: TCP6SAM PROCESS object Transport service provider process: CIPSAM PROCESS object Supported protocols TCP/IP TCP/IP TCP/IP and SCTP (see “Configuring Stream Cont
Table 17 Subsystem Task Comparison Task In Conventional TCP/IP, Use... In Parallel Library TCP/IP and In CIP, Use... NonStop TCP/IPv6, Use... Abort adapter (or SLSA SCF ABORT SAC module) command SLSA SCF ABORT ADAPTER command SCF ABORT CLIM command Abort a MON object No equivalent SCF ABORT PROCESS $ZZKRN.#TCPMON or ABORT MON $ZZTCP.#ZPTMn SCF ABORT PROCESS $ZZKRN.#CIPMON or ABORT MON $ZZCIP.
Table 17 Subsystem Task Comparison (continued) Task In Conventional TCP/IP, Use... In Parallel Library TCP/IP and In CIP, Use... NonStop TCP/IPv6, Use... clim-name | ip-address climconfig sysctl command. Alter network environment attributes SCF ALTER PROCESS command SCF ALTER MON command SCF ALTER PROVIDER command and CLIMCMD sysctl command. (See Chapter 3 (page 69) for information about this command.
Table 17 Subsystem Task Comparison (continued) Task In Conventional TCP/IP, Use... In Parallel Library TCP/IP and In CIP, Use... NonStop TCP/IPv6, Use...
Table 17 Subsystem Task Comparison (continued) Task In Conventional TCP/IP, Use... In Parallel Library TCP/IP and In CIP, Use... NonStop TCP/IPv6, Use... Get Names of No equivalent host-to-CLIM route names No equivalent Get Names of ENTRY objects SCF NAMES ENTRY command SCF NAMES ENTRY command No equivalent. Entries are not named. Get Names of network routes SCF NAMES ROUTE command SCF NAMES ROUTE command No equivalent. Network routes are not named.
Table 17 Subsystem Task Comparison (continued) Task In Conventional TCP/IP, Use... In Parallel Library TCP/IP and In CIP, Use... NonStop TCP/IPv6, Use...
Table 17 Subsystem Task Comparison (continued) Task In Conventional TCP/IP, Use... In Parallel Library TCP/IP and In CIP, Use... NonStop TCP/IPv6, Use...
attribute of the SUBNET object to specify which interface the TCP/IP transport-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 a single interface on a CLIM. You associate a network CLIM with a Provider by using the PROVIDER attribute of the CLIM object.
the network. To specify a route for the first hop on the network in CIP, use the climconfig 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.
Remote Sockets Conventional 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 MON attribute is only useful if remote sockets are supported and hence is not supported in CIP.
Figure 24 Two Interfaces Connected To The Same Subnet Figure 25: 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 pulse The network becomes unreachable for half of the outgoing connections.
Figure 25 Two CLIMs Connected to the Same Subnet As of J06.10 and later J-series RVUs and H06.21 and later H-series RVUs, this problem has been fixed. Error on Sockets When CIPSAM Process Aborts In NonStop TCP/IPv6, when a SAM process is aborted, all existing sockets created using that SAM 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.
The commands supported by NonStop TCP/IPv6 and those supported by CIP are: Command/Object Process Abort NonStop TCP/IPv6, CIP Info Nonstop TCP/IPv6, CIP Listopens NonStop TCP/IPv6 Names Route Subnet NonStop TCP/IPv6, , CIP NonStop TCP/IPv6, CIP NonStop TCP/IPv6, , CIP NonStop TCP/IPv6, CIP Primary NonStop TCP/IPv6, CIP Stats NonStop TCP/IPv6 NonStop TCP/IPv6 NonStop TCP/IPv6 Status NonStop TCP/IPv6 NonStop TCP/IPv6 NonStop TCP/IPv6, CIP Stop NonStop TCP/IPv6, CIP Trace NonStop TC
Associated CLIMs: Name Index C1002582 0 Application Programming Differences Between NonStop TCP/IPv6 and CIP If your application makes sophisticated use of the NonStop TCP/IP, Parallel Library TCP/IP or TCP/IPv6 programming API, it may be affected by differences in the CIP API. Review this section to determine if your application might be affected.
this feature that cannot be solved using more CLIMs is a server that binds to INADDR_ANY to act as a backup for other servers that each bind to a specific address. Changing Destination of a Connected UDP Socket Conventional TCP/IP and NonStop TCP/IPv6 select a local interface based on the destination address for each connect operation done on an unbound UDP socket or one bound to INADDR_ANY.
Conversion of Limited Broadcast to Subnet-Directed Broadcast If the destination address is the limited broadcast address (255.255.255.255), conventional TCP/IP and NonStop TCP/IPv6 convert the address to a subnet-directed broadcast address (the specific subnetid and hostid are all ones) whether the socket is bound or unbound. CIP does this conversion only if the socket is unbound.
Socket Options Some socket options that are supported by NonStop TCP/IPv6 are not supported by or have changed with CIP and require application changes. These options are set by the Guardian setsockopt, setsockopt_nw library calls or the OSS setcsockopt system call. Socket Options Supported Differently These socket options are supported differently in CIP: Level IPPROTO_TCP This TCP_SACKENA socket option for level IPPROTO_TCP, which enables TCP selective acknowledgements, is supported differently in CIP.
• TCP_PAWS This socket option, which was supported but not documented, is no longer supported. See Table 18: Differences in Socket Options Defaults (page 193) for default behavior. • TCP_PROBE_IDLE This socket option, which was supported but not documented, is no longer supported. See Table 18: Differences in Socket Options Defaults (page 193) for default behavior. • TCP_PUSH This socket option, which was supported but not documented, is no longer supported.
Different Socket Options Defaults Table 18 Differences in Socket Options Defaults Previous TCP/IP Subsystem Default Level Socket Option CIP Default SOL_SOCKET SO_BROADCAST SOL_SOCKET SO_SNDBUF 61440 88000* SOL_SOCKET SO_RCVBUF 61440 88000* IPPROTO_TCP TCP_SACKENA 0 ENOPROTOOPT (With compatibility define returns 0) IPPROTO_TCP TCP_MINRXMT 2 ENOPROTOOPT (With compatibility define returns 2) IPPROTO_TCP TCP_MAXRXMT 128 ENOPROTOOPT (With compatibility define returns 128) IPPROTO_TCP T
NonStop TCP/IPv6 Attributes and Their CIP Equivalents Many of the TCP/IP stack environment variables that you set by using attributes in the NonStop TCP/IPv6 ALTER MON/SUBNET command are now set in the CLIM environment. This subsection lists the attributes that you can configure on the NonStop TCP/IPv6 TCP6MON/SUBNET process and an equivalent way of configuring that attribute in CIP. The following table shows NonStop TCP/IPv6 attributes and the equivalent CIP action required to achieve the same result.
If you use this MON/SUBNET attribute in TCP/IPv6: Do this in CIP: “TCPSENDSPACE” (page 197) CLIMCMD {clim–name | ip–address} climconfig sysctl -update net.ipv4.tcp_wmem 'value value value' NOTE: Changes to this sysctl parameter must be made on all CLIMs that share the same Provider. Also, all providers sharing a CLIM must similarly share that sysctl value. “TCPTIMEWAIT” (page 198) CLIMCMD {clim–name | ip–address} climconfig sysctl -update net.ipv4.
HOSTNAME This NonStop TCP/IPv6 Monitor attribute, which specifies the official name by which the NonStop host is known to the Internet, is set by using the NonStop host system SCF commands ADD PROVIDER or ALTER PROVIDER. (See Chapter 10 (page 216) for more information about the HOSTNAME attribute.) MIN-EPHEMERAL-PORT, MAX-EPHEMERAL-PORT These NonStop TCP/IPv6 Monitor attributes specify the starting and ending port numbers to allocate for TCP and UDP ephemeral ports.
TCP-MAX-REXMIT-COUNT This NonStop TCP/IPv6 Monitor attribute, which set the maximum number of continuous retransmissions allowed before a TCP connection was dropped, can be set by issuing the CLIMCMD {clim–name | ip–address} climconfig sysctl command. See “TCP_RXMTCNT” (page 191). TCPPATHMTU This NonStop TCP/IPv6 Monitor attribute is used to turn on Path MTU discovery.
ip–address}climconfig sysctl -update net.ipv4.tcp_wmem "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 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.
This attribute, if changed, must be the same on all CLIMs in a Provider. If the CLIM is an Open type, reboot it. UDPSENDSPACE This NonStop TCP/IPv6 Monitor attribute, which specifies the size of the window used for sending data for the UDP protocol can be set by using the climconfig sysctl -update net.core.wmem_max value and climconfig sysctl -update net.core.wmem_default value commands. This attribute, if changed, must be the same on all CLIMs in a Provider. If the CLIM is an Open type, reboot it.
Table 19 TCP/IP Attribute Default Values and Ranges (continued) TCP/IPv6 Attribute TCP/IPv6 Minimum TCP/IPv6 Default Value Value TCP/IPv6 Maximum Value TCPKEEPIDLE (seconds) 75 1 7200 TCPKEEPINTVL (seconds) 75 1 1260 TCP-MAX-REXMIT-COUNT 12 1 12 TCPPATHMTU ON — — TCPRECVSPACE 61400 512 61400 TCPSACKON OFF — — TCPSENDSPACE 61400 512 61400 UDPRECVSPACE 42080 512 61400 UDPSENDSPACE 9216 512 9216 MAX-PRIV-PORT 1023 IPV6RAENABLE OFF — — TCPTIMEWAIT (seconds) 60 1 1
Table 20 TCP/IP Attributes, CIP Equivalents, and their CIP Default Values and Ranges (continued) CIP Default Value CIP Minimum Value TCP/IP Attribute CIP Equivalent Attribute CIP Maximum Value UDPSENDSPACE net.core.wmem_default/wmem_max 9216 1048576 MAX-PRIV-PORT (built-in) 1023 1048576 IPV6RAENABLE net.ipv6.conf.all.autoconf 1 0 1 TCPTIMEWAIT (seconds) net.ipv4.
In NonStop TCP/IPv6, interfaces configured for NONSHAREDIP failover have separate IP addresses and outgoing data uses the usual routing table rules. (Only the first routing table match is used in NonStop TCP/IPv6, however, so even if both interfaces have a route, only one is selected.) SHAREDIP always alternates between the two interfaces of a failover pair and this option tells TCP/IPv6 to do the same for NONSHAREDIP.
How to Migrate From NonStop TCP/IP or NonStop TCP/IPv6 to CIP Migrate the Environment If you are running multiple TCP/IP subsystems and want to use CIP for your application but the default 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 PARAM establishing another (non $ZTC0) CIPSAM process as the transport service provider in the TACL environment in which your program is running.
7 Storage CIP Migration, Compatibility and Operational Differences The user applications, NonStop SQL/MP, NonStop SQL/MX and Disk Process 2 (DP2) can access the Storage CIP devices without any changes. There are operational differences between configuring the storage subsystem on IOAM based systems and on CLIM based systems. This chapter describes those differences.
Table 21 IOAM and CLIM Based Operations Comparison (continued) Tool/Task IOAM Based Operations CLIM Based Operations Management interface SCF for storage subsystem SCF for storage subsystem, SCF for CIP subsystem and CIP subsystem CLIMCMD command line interface (CLI) Add a storage communication device No equivalent SCF command ADD CLIM $ZZCIP.
8 Collecting Data for CLIM Issues This chapter provides various procedures for collecting NonStop system data for different CLIM types in case of failures.
• SSH logs • NSK Software Configuration file The 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.
Example 20 Collect Debug Data From Single CLIM \BLOKE.$SYSTEM.STARTUP 3> CLIMDBUG N1002582 $SYSTEM.OSMTEST Debug Info CLIM \BLOKE.$ZZCIP.N1002582 PAK File....................$SYSTEM.OSMTEST.ZCL04D01 Contents 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 Example 21 Collect Debug Data From Multiple CLIMs \BLOKE.$SYSTEM.
OSM Event Viewer Log for CIP Event 5231 CLIMDBUG tool logs an EMS event for invocations which result in either success or error conditions.
CLSFTP - T0834 - version 1.2, 29-SEP-2009 using $ZSSP0... SFTP client version T9999H06_21Jun2010_comForte_SFTP_0088 Connecting to 16.107.200.21 via SSH2 process $ZSSP0 ... sftp> get /home/debuginfo/clim-20100802125044.tgz climtgz1 Fetching /home/debuginfo/clim-20100802125044.tgz to climtgz1 ---------------------------------- -------- --- ------- ---------Filename BytesNow % Bytes/s Remaining ---------------------------------- -------- --- ------- ---------/home/debuginfo/clim-20100802125044.tgz 0 0% 0.
23167953 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.tgz TACL> 4. Send the files to HP technical support. Collecting iLO and IML Logs To collect information for a CLIM that is hung or not responding when an automatic reset of a CLIM is detected: 1. Open the iLO window. Invoke the OSM Service Connection on the NonStop Console. 2.
4. 212 Click IML. Copy the log information from the screen and include it in the case data.
5. Click iLO Event Log. Copy the log information from the screen and include it in the case data. Collecting lunmgr Information To collect lunmgr information for any failures detected in the Storage CLIM types: 1. Save the output to a file. TACL->CLIMCMD clim-name lunmgr -e TACL->CLIMCMD clim-name lunmgr -f TACL->CLIMCMD clim-name lunmgr -p 2. Send the output file to HP technical support. Collecting EMS Logs To collect log information for any failures detected in the CLIM: 1. Collect the files $system.
Collecting Network Information To collect network configuration information for any failures detected in an IP, Telco or IB CLIM: 1. Use allow all error in SCF for the following commands: TACL> TACL> TACL> TACL> TACL> scf scf scf scf scf info clim $zzcip.*, detail status clim $zzcip.*, detail info prov $zzcip.*, detail status prov $zzcip.*, detail status prov $zzcip.*, route, cpu 0 Run the above commands on each running CPU. TACL> TACL> TACL> TACL> TACL> 2.
9 Telco CIP Migration, Compatibility and Operational Differences There are operational differences between configuring the 6763 Common Communication ServerNet Adapter and CLIMs systems. This chapter describes those differences. The two biggest differences are the introduction of a new I/O subsystem (CIP) for CLIM configuration and the absence of the SLSA subsystem. NOTE: The Telco CLIM is not a replacement for the CCSA because it does not provide E1/T1 support.
10 SCF Reference for CIP This section provides information about: • The Subsystem Control Facility (SCF) • SCF commands available for CIP • Trace commands available for CIP SCF for Cluster I/O Protocols SCF 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).
Table 24 Commands and Object Types for CIPMAN Object Types SCF Command CLIM MON PROCESS PROVIDER ABORT X X X X ADD X X ALTER X X DELETE X X X INFO X X X LISTOPENS NAMES X X X ROUTE X X X X PRIMARY X X X START X X X STATS X X STATUS X X X X STOP X X X X SWITCH X TRACE X X X X VERSION X X X Table 25: Commands and Object Types for CIPSAM lists commands and object types for CIPSAM: Table 25 Commands and Object Types for CIPSAM Object Types SCF Comm
The hostname, TCP/IP, interface, route, and arp objects reside in the CLIM and are controlled and displayed by the CLIM software commands and configuration files. Figure 26 CIP SCF Object Hierarchy CIPMAN PROCESS Object The CIPMAN PROCESS object is the main management object on the NonStop host system side of the CIP subsystem. The CIPMAN object is the root of the other configuration objects and is used to configure, control, and query the components of CIP on its local system.
CIPSAM Object The CIPSAM process object represents a transport-service provider process. In CIP, the CIPSAM object can be used only to display and control the CIPSAM process itself. The CIPSAM process is started by the persistence manager. For specific information about adding and starting the CIPSAM process, see “Starting CIP on the NonStop Host System” (page 100).
replicated in all the CLIMs. If the socket is used for an outgoing connection or for sending a packet, the host must choose one of the CLIMs to send it. This process uses the destination address and is similar to IP routing, but is used only to select a CLIM within a Provider. With either type of binding, the sending CLIM performs its own IP routing to select an interface and the first hop in the external network. See “ROUTE Object” and for more information about routing in CIP.
Table 26 Object Naming Convention Summary and Reserved Names (continued) Object Type Reserved Names Starting Symbol (Required) First Character Requirement Naming Recommendation Character Limit PROCESS (CIPSAM) None $ Letter ZTCxx where xx are letters or numeric digits. 5 CLIM None N/A Letter N, S, or OGroup 8 Module Slot Port Fiber PROVIDER None N/A Letter Limit to 5 characters; use CIPSAM process name.
Table 27 Command and Object Type Abbreviations Command Abbreviation Object Type Abbreviation ABORT AB CLIM CLI ADD AD MON MO ALTER ALT PROCESS PROC DELETE DELE PROVIDER PROV INFO INF ROUTE ROU LISTOPENS LISTO NAMES NA PRIMARY PRI START STAR STATUS STATU SWITCH SW TRACE TR VERSION VERS Summary States The CIP subsystem objects have operational states, known as summary states.
Table 29 Object State Descriptions (continued) In this state... The object is... STARTING Attempting to start, either because a command was issued to start it or because it is recovering from an error. STOPPING Shutting down because a command was issued to stop it. Sensitive and Nonsensitive Commands Table 30: Sensitive and Nonsensitive SCF Commands lists the sensitive and nonsensitive CIP SCF commands.
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 TCPIP When you need to obtain a list of CIP processes, use the LISTDEV CIP command. The SCF LISTDEV CIP command lists all the CIP processes and the SCF LISTDEV TCPIP command lists all the TCP/IP processes (including conventional TCP/IP and NonStop TCP/IPv6, if present).
configured as persistent (AUTORESTART not equal to 1 in the command defining CIPMON as a generic process), the persistence manager restarts it. This command can be used for online replacement of the CIPMON and CIP Library modules, as discussed in Chapter 3 (page 69). ABORT MON Command Syntax ABORT MON $ZZCIP.ZCMnn [,FORCED] MON $ZZCIP.ZCMnn identifies the CIPMON process to ABORT. The variable nn can be 00 through 15. A wildcard can specify multiple MONs in this system.
Causes the command to execute without displaying a warning and request for operator confirmation. Example 25 stops the CIP subsystem until the persistence manager restarts it. Example 25 ABORT PROCESS > ABORT PROCESS $ZZCIP , SUB ALL Open sockets still exist, okay to continue? Y ABORT PROCESS Guidelines MON objects are not affected even with the SUB ALL or SUB ONLY options ABORT PROVIDER The ABORT PROVIDER command terminates operations on a provider, even if the provider has open sockets.
clim-name Specifies the name to be assigned to the CLIM. The name must be from one to eight alphanumeric characters long and use a leading alphabetic character. It must be unique within this system. The name must be the same as the CLIM hostname defined in the climconfig hostname command. HP recommends using a naming convention that identifies the physical location of the CLIM. See “Naming Convention Summary” (page 220) for information about how to name the CLIM.
The provider must already exist and must be of type IPDATA, but need not be started when configured. This attribute is valid only for a CLIM which has IP or OPEN MODE (i.e., a CLIM that can be used for TCP/IP networking). The same IPDATA provider can be associated with more than one CLIM. The default provider is ZTC0, which always exists and always is of type IPDATA.
case, omit the TPNAME option from the command. However, if the provider name is more than five characters long, it cannot be a CIPSAM process name; in that case, you must use the TPNAME option to specify the CIPSAM process name. The provider name must be unique within this system. TYPE {IPDATA | MAINTENANCE} Specifies the type of provider. IPDATA provider provides TCP/IP access by means of the data Ethernet ports of one or more CLIMs associated with that IPDATA provider.
to INADDR_ANY. Up to eight port numbers can be specified. The range for each 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 port range, the behavior is the same as those ports not being specified. TCP-LISTEN-QUE-MIN queue-size Is the minimum queue length that is allocated on a TCP socket when a socket LISTEN or ACCEPT_NW1 function call is handled.
but need not be started. The same CLIM must not be associated with any other ROUTE object of the same family type with the same parent provider as this new ROUTE object. FAMILY { INET | INET6 | DUAL } Specifies the IP family for which this ROUTE object is applicable.
Example 31 ALTER CLIM With MULTIPROV ON > ALTER CLIM $ZZCIP.N1002541, MULTIPROV ON ALTER CLIM Guidelines • The MULTIPROV and PROVIDER attributes can be altered only when the specified CLIM is not in STORAGE MODE. • If the specified CLIM has the MULTIPROV attribute set to OFF, the PROVIDER attribute can be altered only when the specified CLIM is in STOPPED state with no active interfaces failed-over to any other CLIMs and there are no ROUTE objects associated with the specified CLIM.
Example 32 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 provider is of MAINTENANCE TYPE and is in the STOPPED state. • The SHARE-PORTS attribute can be altered only when the specified provider is of IPDATA TYPE, the provider is in the STOPPED STATE, and all associated CLIMs are in the STOPPED state (or there is no associated CLIM).
that are still running. Use the ABORT CLIM, INTFALL command to stop these interfaces 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 PROVIDER The DELETE PROVIDER command deletes the specified provider from this system. The provider must be in the STOPPED state, and no CLIM can exist that specifies the provider in its configuration.
Example 35 DELETE ROUTE > DELETE ROUTE $ZZCIP.ZTC1.ROUTE2 INFO Commands INFO 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.
Example 37 INFO CLIM, Summary > INFO CLIM $ZZCIP.* CIP Info CLIM Name N1002541 N1002551 N1002581 N1002553 Mode IP IP IP,STORAGE STORAGE Location (100 ,2 ,5 (100 ,2 ,5 (100 ,2 ,5 (100 ,2 ,5 ,4 ,5 ,8 ,5 ,1 ,1 ,1 ,3 ) ) ) ) ConnPts 2 2 1 2 Provider *MultiProv ZTC0 ON ZTC0 ON ZSAM1 OFF --- Location Shows the location specified in the ADD CLIM command and is composed of five numbers: group, module, slot, port, and fiber. For descriptions of the fields, see Example 38.
SvNet ID 1 Shows the CLIM ServerNet ID based on the configured location. X2 Location Shows the CLIM’s expected second X-fabric connection location based on the configured location. This attribute is applicable only when the CLIM’s CONNPTS attribute is 2. Y2 Location Shows the CLIM’s expected second Y-fabric connection location based on the configured location. This attribute is applicable only when the CLIM’s CONNPTS attribute is 2.
Maintenance Interface IP... 16.105.172.20 Network CLIM Information: MultiProv.................. OFF Provider................... ZSAM2 Index...................... 0 For definitions of the fields, see Example 38 (page 236). This is a sample detailed display of S1002551, configured as Storage MODE: Example 40 INFO CLIM Detailed, Storage > INFO CLIM $ZZCIP.S1002551, DETAIL CIP Detailed Info CLIM \MYSYS.$ZZCIP.S1002551 Mode....................... Configured Location........ ConnPts....................
INFO PROVIDER Command Syntax INFO PROVIDER $ZZCIP.prov-name [,DETAIL | ,OBEYFORM] provider-name Is the name of the PROVIDER object about which to display information. A wildcard can specify multiple providers. DETAIL Specifies that the display is to include additional detailed information about the provider. OBEYFORM Causes the configuration to be displayed as ADD or ALTER command(s), so that it can be re-created. Example 43 displays summary information for all PROVIDER objects.
N1002541 N1002551 N1002543 1 2 3 ON (Last Known) OFF ON TPName Is the CIPSAM transport-service provider process name. This is the name applications use to 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. Type Shows the type of provider.
CLIMs Providing Data Access Lists the CLIMs actively providing network resources for use by this provider. Each of these CLIMs contains one or more interfaces associated with this provider. This attribute is applicable only when the provider is of TYPE IPDATA. NOTE: The list may be empty if there is no CLIM actively providing resources to the specified IPDATA provider. This attribute is displayed using — for both Name and Index. Name Is the name of the CLIM.
Example 47 “INFO PROVIDER (IPDATA) With OBEYFORM” requests information for the provider PROV1 (IP Data Provider), in the form of a command (Obey) file. Example 47 INFO PROVIDER (IPDATA) With OBEYFORM > INFO PROVIDER $ZZCIP.PROV1, OBEYFORM ADD PROVIDER $ZZCIP.PROV1 , & TPNAME $ZCSM1 , & HOSTNAME “MYSYS” , & HOSTID 200.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).
Name PROV1.DFLT1 PROV1.DFLT2 Family DUAL DUAL CLIM Priority N1003741 50 N1002532 90 Example 50 shows the configuration of ROUTE DFLT2 associated with provider PROV1 in the form of a command (Obey) file. Example 50 INFO ROUTE With OBEYFORM > INFO ROUTE $ZZCIP.PROV1.DFLT2, OBEYFORM ADD ROUTE $ZZCIP.PROV1.DFLT2 , & CLIM N1002532 , & FAMILY DUAL , & PRIORITY 90 For display field descriptions, see “ADD ROUTE” (page 230).
Ppid Is the PID (cpu, process number) of the primary process that opened the socket. Bpid Is the PID (cpu, process number) of the backup process that opened the socket. If the process pair has no backup, the field is blank. Proto Is the protocol used to open the socket. Provider Is the provider used to open the socket. CLIM Is the CLIM that contains the socket. Lport Is the local port number associated with the socket. Common port numbers are displayed with a text name.
State Is the current state of the socket. The State value is either a translated text string for a TCP state or a cumulative bitwise value in hex format that represents a socket state. Text value: ESTAB indicates the socket is connected to a remote socket. LISTEN indicates the socket is in a listening state and is waiting for a connection from a remote host CLOSING indicates the socket is in the process of closing Hex value: 0x00010 indicates the socket can’t send any more data to its peer.
LISTOPENS PROVIDER Command Syntax LISTOPENS PROVIDER $ZZCIP.prov-name [,DETAIL] prov-name Is the name of the provider to which the command applies. A wildcard can specify a set of providers. Example 53 displays information about processes that have opened sockets on PROVIDER ZTC0. Example 53 LISTOPENS PROVIDER Summary > LISTOPENS PROV $ZZCIP.ZTC0 CIP Listopens PROVIDER \MYSYS.$ZZCIP.ZTC0 Openers \MYSYS.$MYWEB \MYSYS.$MYWEB Ppid 1,333 1,333 Openers \MYSYS.$ZTN0 \MYSYS.
Opener:\EUROPA.$ Ppid: 2,480 Bpid:0,0 Plfn:7 Blfn:5 Proto:TCP State:ESTAB SendQ:0 RecvQ:0 Provider:CSAM CLIM:DL385F CLIM-FD:34 Lport:3333 Laddr:172.17.188.142 FPort:22861 Faddr:172.17.188.142 Opener:\EUROPA.$ Ppid: 2,500 Proto:TCP Provider:CSAM Lport:27501 Bpid: 0,0 State:0x00180 CLIM:DL385G Plfn:2 Blfn:5 SendQ:0 RecvQ:0 CLIM-FD:42 Laddr:172.17.188.152 FPort:0 Faddr:0.0.0.
Hex value: 0x00010 indicates the socket can’t send any more data to its peer. 0x00020 indicates the socket can’t receive any more data from its peer. 0x00080 indicates the socket is operated in a privileged mode. This usually means the application is started by a super user. 0x00100 indicates the socket is operated in a non-blocking io mode. 0x04000 indicates the socket is a listening socket. 0x08000 indicates the socket has received a 0-byte indication.
Example 55 NAMES $ZZCIP > NAMES PROCESS $ZZCIP CIP 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 CLIM The NAMES CLIM command displays the names of the specified CLIMs known by this system. NAMES CLIM Command Syntax NAMES CLIM $ZZCIP.clim-name clim-name Specifies the CLIM names to display. If no such CLIM is known to this system, the output is an error message.
NAMES PROCESS Command Syntax > NAMES PROCESS $ZZCIP This command displays the names and types of all objects subordinate to CIPMAN on this system. Example 58 NAMES PROCESS > NAMES PROCESS $ZZCIP CIP Names PROCESS \MYSYS.$ZZCIP PROCESS $ZZCIP MON $ZZCIP.ZCM00 $ZZCIP.ZCM01 PROVIDER $ZZCIP.ZTC0 $ZZCIP.PROV1 ROUTE $ZZCIP.ZTC0.ROUTE1 CLIM $ZZCIP.N1002532 $ZZCIP.ZCM02 $ZZCIP.ZCM03 $ZZCIP.ZTC0.ROUTE2 $ZZCIP.PROV1.MYROUTE $ZZCIP.
Example 60 NAMES ROUTE > NAMES ROUTE $ZZCIP.* CIP Names ROUTE \MYSYS.$ZZCIP.* ROUTE $ZZCIP.ZTC0.ROUTE1 $ZZCIP.ZTC0.ROUTE2 $ZZCIP.PROV1.MYROUTE PRIMARY Command The PRIMARY command changes the specified object in an object pair from the backup to the primary. PRIMARY PROCESS The PRIMARY PROCESS command is a sensitive command that changes which process of the CIPMAN process pair is the primary.
Example 62 START CLIM > START CLIM $ZZCIP.S1003741 START PROCESS The START PROCESS command starts the operation of all the objects in the CIP subsystem on this system. Because the target object is already started (by the persistence manager), the SUB ONLY option must be specified. START PROCESS Command Syntax START PROCESS $ZZCIP, SUB ONLY SUB Determines the set of objects and subordinate objects that the command targets. ONLY specifies that only subordinate objects are targets of the command.
The statistics pertain to the operation of the CLIM software and the CLIM-side communication with the NonStop host system. To get TCP/IP protocol statistics, use the Linux netstat command on the CLIM. (To obtain information about the netstat command, enter CLIMCMD clim-name man netstat at the TACL prompt.) NOTE: For better performance, always use the –n option with netstat. STATS CLIM Command Syntax STATS CLIM $ZZCIP.
CLIMMON STATS Heads the statistics taken from the CLIMMON process, which starts and monitors the other CIP subsystem components on the CLIM. Event Log Entries Shows the number of syslog entries generated by the CLIMMON process since the last reset. Restarts Shows the number of times CLIMMON restarted the CLIMAGT and CIPSSRVx processes since the last reset. All these processes are restarted when any one indicates a failure.
Queued Commands Shows the number of SCF commands queued for processing. Failed Commands Shows the total number of SCF commands that could not be completed since the last reset. CIPSSRVx STATS Heads the statistics taken from each CIPSSRV process, which performs application socket requests. Only one CIPSSRV process (CIPSSRV0) is present in CIP. Statistics with the same title as those for the CLIMAGT contain the same information for the CIPSSRV process.
Total Recv Socket Reqs...... Total Recv Errors........... Total Send Socket Reqs...... Total Send Errors........... Data Bytes Sent............. Data Bytes Received......... Total Connections Out....... Current TCP Listen Sockets.. Current UDP Sockets......... Current TCP Connections..... 0 0 0 0 0 0 0 0 0 0 SOCKET SEND SIZE HISTOGRAM Size 1-128.................. Size 257-512................ Size 1025-2048.............. Size 4097-8192.............. Size 12289-16384............ Size 32769 and larger.......
High TCP Connections Shows the highest number of TCP connections at one time since the last reset. SOCKET SEND SIZE HISTOGRAM Shows the number of socket send requests across all CLIMs, organized by the length of the request. Size x-xxxx Is the count of socket sends between x and xxxx bytes. Size 32769 and larger Is the count of socket sends greater than 32769 bytes. Total Messages Sent Shows the total number of messages sent to all CLIMs since the last reset.
N1003741 N1012542 Yes Yes STARTED STARTED 1, 2 2 Present Indicates whether an operational CLIM is present at the configured location and can have any of the values Yes CLIM is connected at all configured locations and is usable Partial CLIM is connected at some but not all configured locations and is usable No CLIM is not connected at any of the configured locations (not usable) Conflict Two or more CLIMs are connected to the configured locations (not usable) Problem A connection problem exists
Linux Version: Linux 3.2.12-clim-5-amd64 #1 SMP Fri Apr 27 22:27:05 UTC 2012 Fabric Status: CIPMON Mgmt ZCM00 XY-1 ZCM01 XY-1 ZCM02 XY-1 ZCM03 XY-2 ZCM04 XY-1 ZCM05 XY-2 ZCM06 XY-2 ZCM07 XY-1 ZCM08 XY-1 ZCM09 XY-2 ZCM10 XY-2 ZCM11 XY-1 ZCM12 XY-2 ZCM13 XY-1 ZCM14 XY-1 ZCM15 XY-2 Data XY-1 XY-1 XY-1 XY-2 XY-1 XY-2 XY-2 XY-1 XY-1 XY-2 XY-2 XY-1 XY-2 XY-1 XY-1 XY-2 CLIM Maintenance Interface Status & IP Addresses: lo Sts:UP Lkp:-IPv4: 127.0.0.1 IPv6: ::1 eth0 Sts:UP Lkp:UP IPv4: 16.107.184.
eth4 UP UP IPv4: IPv6: IPv6: IPv6: 172.17.190.33 3ffe:1200:190:2:21f:29ff:fe0d:ac1f 3ffe:1200:190:1:21f:29ff:fe0d:ac1f fe80::21f:29ff:fe0d:ac1f Data Provider LOOP Interface Status & IP Addresses: Flg Name Status LkP Master / IP Family & Address lo UP -IPv4: 127.0.3.2 IPv4: 127.0.0.1 IPv6: ::1 Interface Failover Configuration and Status: Flg Name Failover/(Assoc) Fovr C100271.eth5 C100263.eth5 Home C100271.bond1 -(T) C100271.TUN0 (C100271.eth1) Home C100271.eth1 C100263.eth1 Home C100271.
ConnPts Shows whether there are one or two ServerNet connections configured per fabric between CLIM and the NonStop host system. X1 Location Shows the CLIM’s first X-fabric location based on the configured location. Y1 Location Shows the CLIM’s first Y-fabric location based on the configured location. X2 Location Shows the CLIM’s second X-fabric location based on the configured location. This is applicable only when CLIM’s CONNPTS attribute is 2.
Fabric Status Displays the CIPMON status, connections to the CLIM, and availability of the X and Y ServerNet fabrics for each running processor in the system. The Mgmt column shows the management connection to CLIMAGT, and the Data column shows the data path connections to the CIPSSRV processes. The possible values are: MON-DOWN CIPMON is down. -- CIPMON is up, but no connection is established. X- Connection is established; only the X fabric is available.
• DNOP indicates the interface is down due to an operator command (not usable) • DOWN indicates the interface is down due to a failure on the CLIM (not usable) Link pulse status Is UP, DOWN, or — • UP indicates the link is active • DOWN indicates the link is inactive • — indicates no link pulse status if no link pulse status Master name Is the name of the master interface if this is a slave interface (otherwise, this attribute is empty) IP addresses Is the IP address family and actual IP address associ
Current location Indicates the current location of the interface (home interface or failover interface). If there is no failover (HOME or __), the location is the same as the interface name. If there is failover, then this field is identical to the failover interface at the time of the failover. Provider Indicates the name of the associated IPDATA provider. NOTE: Interface failover status is only applicable when CLIM has IP or OPEN MODE.
Mode...................... CLIM HW Connection Status. State..................... ConnPts................... X1 Location............... Y1 Location............... X2 Location............... Y2 Location............... X1 Connection Status...... Y1 Connection Status...... X2 Connection Status...... Y2 Connection Status...... Trace Status..............
Example 73 displays detailed status information for the MON named ZCM03: Example 73 STATUS MON Detailed > STATUS MON $ZZCIP.ZCM03, DETAIL CIP Detailed Status MON \MYSYS.$ZZCIP.ZCM03 Heap Memory Limit........ Heap Memory Used......... PID...................... Priority................. QIO Pool Current......... QIO Pool Limit........... State.................... Trace Status............. Trace Filename...........
Example 75 STATUS PROCESS Detailed > STATUS PROCESS $ZZCIP, DETAIL CIP Detailed Status PROCESS \MYSYS.$ZZCIP Heap Memory Limit........ Heap Memory Used......... PID Primary.............. PID Backup............... Priority................. QIO Pool Current......... QIO Pool Limit........... State.................... Trace Status............. Trace Filename...........
Example 77 displays detailed status information for IPDATA PROVIDER ZTC0. Example 77 STATUS PROVIDER Detail -> STATUS PROV $ZZCIP.ZTC0, DETAIL CIP Detailed Status PROVIDER \MYSYS.$ZZCIP.ZTC0 State.................... TPStatus................. Type..................... Family................... Current Access........... Trace Status............. STARTED Started IPDATA DUAL ( 0, 1, 2, 3 ) OFF Interface Status & IP Addresses: Name Current lo N1002532.lo N1003741.lo N1002532.eth1 N1002532.eth1 N1002532.
N1003741.eth2 N1003741.eth3 (X) N1003741.eth4 DNOP DOWN UP UP UP UP N1002532.eth2 N1002532.eth4 UP UP N1002532.eth2 DOWN DOWN N1003741.eth3 --N1003741.eth4 BkOP HOME HOME Type Shows the type of provider. An IPDATA provider provides TCP/IP access through data Ethernet ports of one or more CLIMs associated with that IPDATA provider. A MAINTENANCE provider provides TCP/IP access through the maintenance Ethernet interface of a specific CLIM using a specific IP address.
Interface Failover Configuration and Status Shows the failover configuration and status for each data interfaces associated with the provider that has been configured to support failover, showing: F Indicates special condition of interface: • T indicates a manually configured IPv6-over-IPv4 tunnel interface • X indicates the interface whose failover configuration is invalid Home Indicates the home interface name Failover/(Assoc) Indicates the failover-interface name or the name of the associate interfa
CLIM Shows the name of the CLIM associated with the MAINTENANCE provider. This attribute is applicable only to provider with TYPE MAINTENANCE. Interface Status & IP Address Shows 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.
STATUS PROVIDER Guidelines The STATUS PROVIDER ROUTE command is rejected if the PROVIDER object is of TYPE MAINTENANCE. STOP Commands STOP is a sensitive command that halts the operation of the specified object. If existing sockets are using the object, the command fails. The object is left in the STOPPED state if the command succeeds. STOP CLIM The STOP CLIM command stops operations on the specified CLIM, provided that the system has no existing sockets using the CLIM.
SUB Determines 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 the command. 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. This is the default selected if the SUB keyword is not used.
NOTE: Do not use the SWITCH command to fail over interfaces you plan to delete. The interface remains in the UP state when you use the SWITCH command. Before deleting an interface, use ifstop. The ifstop command deactivates the interface, preventing autoconfigured IPv6 addresses and link local addresses from being created in the interim. NOTE: The storage subsystem ($ZZSTO) also supports a SWITCH CLIM command. For syntax and display examples, see the SCF Reference Manual for the Storage Subsystem.
It does not affect other interfaces that are migrating at the same time. The SWITCH command does not complete until the outcome of the failover is known. If the duplicate-address check and resource migration may take some time, there could be a delay before SCF issues the next command prompt. • Failover migrates nearly all interface resources, but not TCP or SCTP connections.
RECSIZE size Specifies the length, in bytes, of the data in the trace data records. The size is an integer from 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. WRAP Specifies that when the trace disk file end-of-file (EOF) mark is reached, trace data wraps around to the beginning of the file and overwrites any data there.
Example 86 TRACE CLIM > TRACE CLIM $ZZCIP.N1003741, TO $DATA00.TRC1003741.CPU1, CPU 1, RECSIZE 4050 TRACE MON The 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 processors can be tracing simultaneously to different trace files. TRACE MON Command Syntax TRACE MON $ZZIP.
[,COUNT count] [,LOCKSIZE locksize] [,NOCOLL] [,PAGES pages [,RECSIZE size] [,SELECT {select-option|select-option ...}][,WRAP]} BACKUP Specifies that the current backup CIPMAN process is to be traced. The default is to trace the primary process. The same process continues to be traced if its primary/backup status changes later. SELECT { select-opt | ( select-opt , … ) } Selects the operations to be traced.
CPU cpu Optional with STOP and identifies the processor on which to stop tracing. If this option is not specified, all processors stop tracing the provider. CPU is required with the TO option and identifies the processor on which to start tracing the provider. SELECT { select-opt | ( select-opt , ... ) } Selects the operations to be traced.
NETWORK: T0691H01_01NOV2008_AAF_CLIM STORAGE: 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) (Debian 4.1.1-21)) #1 SMP PREEMPT Thu Feb 28 01:10:30 UTC 2008 CIP SW Shows the version of CIP subsystem software running on the CLIM. NETWORK Shows the version of networking software running on the CLIM. STORAGE Shows the version of storage software running on the CLIM.
Example 93 VERSION MON Detailed > VERSION MON $ZZCIP.ZCM03, DETAIL Version PROCESS \MYSYS.$ZZCIP.ZCM03 CIPMonitor - T0694H01_01AUG2008_AAB_MON_Q41 GUARDIAN - T9050 - {T06) SCF KERNEL - T9082H01 - (04DEC06) )15NOV06) CIP PM - T0695H01 - (05AUG2008) (H01 SCF AAB) VERSION PROCESS The VERSION PROCESS command displays the version number of the CIPMAN process. VERSION PROCESS Command Syntax VERSION PROCESS $ZZCIP [,DETAIL] Example 94 displays the version of CIPMAN.
INFO PROCESS The INFO PROCESS command displays attributes of the CIPSAM process. For compatibility with the SAM process of TCP/IPv6, attributes that do not apply to CIP are displayed with zero (0) values. INFO PROCESS Command Syntax INFO PROCESS $cipsam-name [,DETAIL] cipsam-name Is the name of the CIPSAM process for which to display information. DETAIL Specifies that the display is to include additional detailed information about the object.
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 every time 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 can be checked by issuing a sysctl command.
Host Id scf> INFO Provider $ZZCIP.provider-name, DETAIL. Is the ID (usually the host number part of the Internet address that is assigned to this host). It is a 32-bit number. Host Name scf> INFO Provider $ZZCIP.provider-name , DETAIL. Is the official name by which the host upon which the TCP/IP process is running is known in the Internet. This is a character string no longer than 50 characters. Debug No longer applies in the CIP environment.
otherwise the queue length in the socket request is used. The default value is 5. The range is 1 to 1024. INITIAL-TTL tacl> CLIMCMD clim-name sysctl net.ipv4.ip_default_ttl. Specifies the initial value for UDP and TCP TTL. INFO SUBNET The INFO SUBNET command displays attributes of the CLIM interfaces belonging to a CIPSAM provider in a format compatible with previous NonStop TCP/IP products. Only IPv4 addresses are shown.
QIO Shows OFF for interfaces named “lo” and ON for all others. R Always shows N. Example 99 detailed info for the interface identified as SUBNET #SN004 in the Provider for $ZTC2. Example 99 INFO SUBNET Detailed > INFO SUBNET $ZTC2.#SN004,DETAIL CIP Detailed Info SUBNET \MYSYS.$ZTC2.#SN004 Name Devicename *ADDRESS TYPE #SN004 N1002532.ETH4 172.17.190.104 Trace Status ........ OFF Trace Filename ...... Interface MTU ....... 1500 Gateway .............
PRIMARY Command, CIPSAM The only supported PRIMARY command for CIPSAM is PRIMARY PROCESS. PRIMARY PROCESS The PRIMARY PROCESS command is a sensitive command that changes which process of the CIPSAM process pair is currently the primary. This command does not affect existing sockets. PRIMARY PROCESS Command Syntax PRIMARY PROCESS $cipsam-name [,CPU cpu-number] cipsam-name Is the name of the CIPSAM process to switch. CPU cpu-number Specifies the processor number of the current backup process.
STOP Command, CIPSAM The only supported STOP command for CIPSAM is STOP PROCESS. STOP PROCESS The STOP PROCESS command stops the operation of the specified CIPSAM process if it has no open sockets. If sockets are open, the command returns an error. STOP PROCESS Command Syntax STOP PROCESS $cipsam-name cipsam-name Is the name of the CIPSAM process to stop. Example 103 stops the CIPSAM process named $ZTC1.
COUNT count count is an integer in the range -1 to (32k-1). It specifies the number of trace records to be captured. If COUNT is not specified (or is specified as -1), records are accumulated until the trace is stopped or the file file-spec is full. NOCOLL Indicates that the trace collector process should not be initiated. The disk file is to be written to by Guardian. The attributes WRAP and NOCOLL cannot be specified together.
11 CLIMCMD and CLIMCMD climconfig Commands (Man Pages) man pages are described in these sections: • “Standalone Commands (Man Pages)” (page 291) • “Climconfig (Man Pages)” (page 301) These sections contain the information for the individual man pages, and can also be viewed directly on the CLIM.
Standalone Commands (Man Pages) This section contains reference pages for standalone commands. These standalone commands have 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 CLIMCMD or when logged into the CLIM directly with putty.
clim(1) NAME clim -- query and control the CLIM software. SYNOPSIS CLIMCMD {clim-name|ip-address} clim [option] clim Description clim provides a set of commands to query and control the CLIM software, and to display the process status of each of the clim processes. PARAMETERS abort Abort and dump all CLIM processes. clearlog Allows a CLIM that has stopped trying to restart itself after reaching a retry threshold to be resumed. Should be followed by 'clim start'.
SEE ALSO psclim(1), climstatus(1) 293
climstatus(1) NAME climstatus -- displays CLIM specific status information SYNOPSIS CLIMCMD {clim-name|ip-address} climstatus [-o option] climstatus Description climstatus is a program that provides active status information about active objects on specific CLIMs: (See climconfig(1) for information on obtaining permanent configuration information.
r Displays the status information pertaining to Kernel IP Routing Table. Displays information specific 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, Destination IP address, and Next Hop information is displayed. s Displays the status information pertaining to ServerNet only.
ifstart(1) NAME ifstart -- start an interface SYNOPSIS CLIMCMD {clim-name|ip-address} ifstart interface ifstart Description ifstart allows you to activate an interface if you have stopped the interface using the ifstop command. For all network interfaces (ethernet, ip-over-infiniband, bonding and tunnel interfaces), this command activates the specified interface. PARAMETERS interface Specifies the name of the network interface that is to be started and made available to the NonStop host.
ifstop(1) NAME ifstop -- stop an interface SYNOPSIS CLIMCMD {clim-name|ip-address} ifstop interface [-force] ifstop Description Use 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 routes associated with the network interface. PARAMETERS interface Specifies the name of the network interface that is to be stopped and made unavailable to the NonStop host.
prov(1p) NAME prov -- execute a program under the context of a provider’s network stack SYNOPSIS CLIMCMD {clim-name|ip-address} prov {prov-name} {command} [arg1..argN] prov Description CLIMs utilize multiple independent network stacks, or “providers.” At any time, a CLIM can have some of the following providers: %DEFAULT The reserved network stack that is used for all data communications on CLIMs configured in SCF with the MULTIPROV attribute set to OFF.
- 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 ALSO climconfig.
psclim(1) NAME psclim -- display the status of the CLIM processes SYNOPSIS CLIMCMD {clim-name|ip-address} psclim psclim Description psclim is a derivation of the 'ps' command. It displays system information about the CLIM processes. The CLIM processes consist of climmon, confsync, climagt and one or more cipssrv. The information being displayed consists of process PID, memory used, percentage memory, percentage CPU time, accumulated CPU time, start time, run status, and start command.
Climconfig (Man Pages) This section contains reference pages for the climconfig command. Climconfig commands have a man-page format that includes the title of the man page, represented in man page format (for example, climconfig.arp(1). These man pages are also available on the CLIM, using the "man" command through CLIMCMD or when logged into the CLIM directly with putty.
climconfig(1) NAME climconfig -- configure network protocol parameters SYNOPSIS CLIMCMD {clim-name|ip-address} climconfig command [parameter] climconfig Description This command is a parameter to the CLIMCMD command-line interface. It allows you to configure network, IPSec, climiptables, iptables, ip6tables, failover and SNMP parameters. Enter CLIMCMD at 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.
climconfig.all(1) NAME climconfig.all -- display the entire CLIM configuration SYNOPSIS CLIMCMD {clim-name|ip-address} climconfig all -info [-obeyform] climconfig.all Description This command displays the entire CLIM configuration.
climconfig.arp(1) NAME climconfig.arp -- manage arp entries SYNOPSIS CLIMCMD {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 Description This command: arp -add adds information about ARP entries. arp -delete deletes manually-added ARP entries.
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 clim1 climconfig arp -add eth1 –host 15.76.219.4 –hwaddress 00:0E:7f:F5:6E:8A > CLIMCMD 17.21.201.2 climconfig arp -delete eth1 –host 15.76.219.
climconfig.bondmode(1) NAME climconfig.bondmode -- change bonding mode, get bondmode info SYNOPSIS CLIMCMD {clim-name|ip-address} climconfig bondmode -modify bonding-mode CLIMCMD {clim-name|ip-address} climconfig bondmode -info [-obeyform] climconfig.bondmode Description This command displays information about the bonding mode. The bonding mode applies to all the bonding interfaces in the CLIM. Only one slave in the bond is active.
ERROR MESSAGES For bondmode -modify, one or more of the Bonding interfaces is UP The value of the bonding mode should be either 1, 5, or 6 The software MAC address of the slaves and of bonding interface cannot be same for bonding mode .
climconfig.climiptables(1) NAME climconfig.climiptables -- configure climiptables SYNOPSIS CLIMCMD {clim-name|ip-address} climconfig [-prov prov-name] -enable CLIMCMD {clim-name|ip-address} climconfig [-prov prov-name] -disable [-force] CLIMCMD {clim-name|ip-address} climconfig [-prov prov-name] -info [-obeyform] CLIMCMD {clim-name|ip-address} climconfig [-prov prov-name] -status climiptables climiptables climiptables climiptables climconfig.
CONSIDERATIONS None.
climconfig.failover(1) NAME climconfig.failover -- configure failover SYNOPSIS CLIMCMD {clim-name|ip-address} climconfig failover -add src-interface -dest dest-clim-name.dest-interface CLIMCMD {clim-name|ip-address} climconfig failover -delete {src-interface|all} [-force] CLIMCMD {clim-name|ip-address} climconfig failover -info clim-name -interface {interface-name|all}[-obeyform] climconfig.failover Description This command allows you to configure the failover behavior between CLIMs.
-force Runs the command without prompting for confirmation. -obeyform Generates failover configuration information in add command format. ERROR MESSAGES For 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.
> CLIMCMD n100253 climconfig failover -info clim2 eth1 SOURCE DESTINATION FAMILY clim2.eth1 clim1.eth1 INET clim1.eth2 clim3.eth1 INET > CLIMCMD n100253 climconfig failover –info climx –interface eth1 SOURCE DESTINATION climx.eth1 climy.eth2 > CLIMCMD n100253 climconfig failover –info climx –interface eth1 -obeyform climconfig failover \ -add eth1 \ -dest climy.eth2 #CLIMCMD expects 'exit' to be the last command. #This is required to terminate CLIMCMD session.
climconfig.hostname(1) NAME climconfig.hostname -- manage the CLIM host name SYNOPSIS CLIMCMD {clim-name|ip-address} climconfig hostname -modify hostname CLIMCMD {clim-name|ip-address} climconfig hostname -info climconfig.hostname Description This 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.
climconfig.interface(1) NAME climconfig.
climconfig.interface Description This command does the following: interface -add adds the interface name to the /etc/network/interfaces file of the CLIM. The host brings up the interface when it is added. If the CLIM has MULTIPROV ON and the operator specifies the -prov command with the name of an unconfigured prov object, that object is implicitly added.
-prov Specifies a provider name. This option is mandatory for CLIMs that have MULTIPROV set to ON and cannot be used if MULTIPROV is set to OFF. Each provider has its own interface configuration. The provider name is case-insensitive and always converted to UPPER case. -netmask netmask Specifies an IPv4 network address in dotted quad form. all Displays information for all interfaces. -obeyform This option displays the user-configured resources of an interface in add command format.
-linespeed 100 Sets the linespeed to 100MB/sec. -linespeed 1000 Sets the linespeed to 1000MB/sec. This option can be set only if -autonegotiation is set to on. -duplex half Sets the duplex mode to half. -duplex full Sets the duplex mode to full. -macaddr Specifies the MAC address to be assigned to the specified interface. If default is specified, the original hardware MAC address is assigned.
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.
eth0 ip address -netmask 255.255.252.0. Then issue the SCF CLIM START command 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.
SEE ALSO climconfig ip -add 320
climconfig.ip(1) NAME climconfig.ip -- add or delete IP addresses SYNOPSIS CLIMCMD {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 Description This command does the following: ip -add adds an IP address to an existing interface. Multiple IP addresses can be added to an interface.
Cannot execute this command for the interface interface-name when the CLIM is in STARTED 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.
All the routes belonging to an interface for a particular network are automatically deleted from the 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 only when the interface is restarted (ifstop followed by ifstart) or when the routes are deleted and then added back after adding at least one IPv4 address corresponding to that network.
climconfig.ip6tables(1) NAME climconfig.ip6tables -- configure ip6tables SYNOPSIS CLIMCMD {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 Description This command supports the following options. If a command is labeled as sensitive, a user confirmation is required for execution unless the -force option is also specified.
--zero | -Z [chain] This command zeros out the packet and bytes counters in the specified chain or all chains if the chain name is not specified. This applies to all user-defined chains, the CIP built-in chain and Linux built-in chains if chain is not specified. A user may also specify the Linux built-in INPUT chain for this command. --new | -N chain This command creates a new user-defined chain by the given name. There must be no target of that name already, or an error is returned.
[!] --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 is equivalent to 255.255.255.0. When the "!" argument is used the ‘match’ operation is changed to the ‘not match’ operation.
connbytes Matches 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 ... connlimit Allows you to restrict the number of parallel TCP connections to a server per client IP address (or address block).
Not supported because Differentiated Services Code Point is QoS related. dst Matches parameters in Destination Options header. [!] --dst-len length --dst-opts type[:length][,type[:length]...] esp Matches the SPIs in ESP header of IPsec packets. [!] --espspi spi[:spi] eui64 Matches EUI-64 part of a stateless auto configured IPv6 address. frag Matches parameters in the Fragment header.
hl Matches the Hop Limit field in the IPv6 header. [!] --hl-eq value --hl-lt value --hl-gt value icmp6 Matches ICMPv6-specific values. [!] --icmp-type {type[/code]|typename} Allows specification of the ICMPv6 type, which can be a numeric ICMPv6 type, type and code, or one of the ICMPv6 type names shown by the command: ip6tables -p ipv6-icmp -h iprange Matches on a given arbitrary range of IP addresses.
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. pkttype Matches link-layer packet type. [!] --pkt-type {unicast|broadcast|multicast} policy Matches IPsec policy.
--rt-type [!] type --rt-segsleft [!] num[:num] --rt-len [!] length --rt-0-res --rt-0-addrs ADDR[,ADDR...] --rt-0-not-strict sctp Matches 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. state Allows access to conntrack state for this packet.
time Matches 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...] --utc Interprets the times given for --datestart, --datestop, --timestart and --timestop to be utc. --localtz Interprets the times given for --datestart, --datestop, --timestart and --timestop to be local kernel time.
LOG has the following options: --log-level level Level 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.
ERROR MESSAGES climconfig 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’.
destination 120 REJECT all -eth2 reject-with icmp-port-unreachable 2 Chain telnet (1 references) pkts bytes target prot opt in destination 1 60 REJECT all -- !eth2 reject-with icmp-port-unreachable Termination Info: 0 any anywhere out source any anywhere anywhere anywhere SEE ALSO climconfig iptables, climiptables 335
climconfig.iptables(1) NAME climconfig.iptables -- configure iptables SYNOPSIS CLIMCMD {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 Description This command supports the following arguments. If a command is labeled as sensitive, a user confirmation is required for execution unless the -force option is also specified.
--zero | -Z [chain] This command zeros out the packet and bytes counters in the specified chain or all chains if the chain name is not specified. This applies to all user-defined chains, the CIP built-in chain and Linux built-in chains if chain is not specified. A user may also specify the Linux built-in INPUT chain for this command. --new | -N chain This command creates a new user-defined chain by the given name. There must be no target of that name already, or an error is returned.
[!] --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 is equivalent to 255.255.255.0. When the "!" argument is used the ‘match’ operation is changed to the ‘not match’ operation.
ah Matches the SPIs in Authentication header of IPsec packets. [!] --ahspi spi[:spi] comment Allows you to add comments (up to 256 characters) to any rule. --comment comment Example: iptables -A INPUT -s 192.168.0.0/16 -m comment --comment 'A privatized IP block' connbytes Matches 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 than FROM and less than TO bytes/packets.
[!] --ctreplsrcport port [!] --ctrepldstport port Matches 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.
Allows specification of the ICMP type, which can be a numeric ICMP type, type/code pair, or one of the ICMP type names shown by the command: iptables -p icmp -h iprange Matches on a given arbitrary range of IP addresses. [!] --src-range from[-to] [!] --dst-range from[-to] length Matches the length of a packet against a value or range of values. [!] --length length[:length] limit Matches a rule to a specified rate.
[!] --tunnel-src addr[/mask] [!] --tunnel-dst addr[/mask] --next quota Implements network quota by decrementing a byte counter with each packet. --quota bytes The 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. recent Matches against dynamically constructed list of IP addresses.
--probability p --every n --packet p string Matches a given string pattern. --algo bm|kmp --from offset --to offset [!] --string pattern [!] --hex-string pattern tcp Matches TCP-specific values. [!] --source-port | --sport port[:port] [!] --destination-port | --dport port[:port] [!] --tcp-flags mask comp [!] --syn [!] --tcp-option number tcpmss Matches the TCP MSS field of the TCP header. [!] --mss value[:value] time Matches the arrival time/date of packets.
u32 Tests whether quantities of up to 4 bytes extracted from a packet have specified values. The specification of what to extract is general enough to find data at given offsets from tcp headers or payloads. [!] --u32 tests The argument amounts to a program in a small language described below: tests := location "=" value | tests "&&" location "=" value value := range | value "," range range := number | number ":" number a single number, n, is interpreted the same as n:n.
--log-uid Log 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.
-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-unreachable Termination Info: 0 > climcmd n1002583 climconfig iptables -vL Chain INPUT (policy ACCEPT 11 packets, 889 bytes) pkts bytes target prot opt in out source destination 7636 1970K ACCEPT all -- any any N1002583 anywhere 657K 229M ACCEPT all -- eth0 any anywhere anywhere 204 13045 CIP_INPUT all -- any any anywhere anywhere 146 9781 CIP_INP
climconfig.prov(1) NAME climconfig.prov -- configure prov SYNOPSIS CLIMCMD {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 Description This command allows you to display and configure climconfig prov objects.
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 and must be alpha-numeric characters with the first character being alphabetic. CONSIDERATIONS Climconfig prov objects are added implicitly during interface addition, so this command is only required if a provider with only loopback needs to be added.
climconfig.psk(1) NAME climconfig.psk -- configure pre-shared keys SYNOPSIS CLIMCMD {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.
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.
climconfig.remote(1) NAME climconfig.
climconfig.remote Description remote -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.conf for the phase 1 IKE negotiation. A maximum of 10 proposals can exist in a remote configuration. remote -delete deletes a remote entry from the configuration file racoon.conf.
–verify_identifier To verify the peer's identifier, set this to on. In this case, if the value defined by -peer_idtype is not the same as the peer's identifier in the ID payload, the negotiation will fail. The default is off. –pubcert certfile Specifies the file name of a public certificate. –privkey privkeyfile Specifies the file name of a private key. If you omit the –pubcert or -privkey option, the default behavior is to use the pre-shared key. The default path for pre-shared key is /etc/ racoon/psk.txt.
–force Used with the -restart option, causes the command to bypass user confirmation. -obeyform Displays the remote configuration in the format of add command(s). ERROR MESSAGES For 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.
> 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.
climconfig.route(1) NAME climconfig.
{-add|-delete} eth0:0 Specifies 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 both the interfaces have to belong to same subnet. Climconfig will maintain the same set or routes on both the interfaces. If a route is added to either eth0 or eth0:0, climconfig will add it to both eth0 and eth0:0.
4294967295. This option is used to improve performance on routes to SWAN concentrators, with a recommended value of 7. -default Specifies to use the default route if no other route matches. This option is not valid with the –host, –net, –netmask, and –target options. -usrconfig Valid only with the route -info command. This option displays user-configured routes only. If this option is omitted, the command displays the user configured routes and the dynamic routes added by the kernel.
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 is required, 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.
Src : Unspecified Interface : lo Destination : 1128 Gateway : Metric : 0 MinRTO : Unspecified InitCWND : Unspecified Src : Unspecified Interface : lo Destination : fe80::128 Gateway : Flags : U Metric : 0 Ref : 0 Use : 2 MinRTO : 5ms InitCWND : Unspecified Src : Unspecified Maintenence provider routes Interface : eth0 Destination : 16.107.168.0 Netmask : 255.255.252.0 Gateway : 0.0.0.0 Flags : U Metric : 0 Ref : 0 Use : 0 MinRTO : Unspecified InitCWND : Unspecified Src : 16.107.168.
Interface : eth1 Destination : 16.107.170.0 Netmask : 255.255.255.0 Gateway : 16.107.170.1 Flags : U Metric : 0 Ref : 0 Use : 0 MinRTO : Unspecified InitCWND : 32768 Src : 16.107.170.31 Termination Info: 0 > CLIMCMD 17.205.15.2 climconfig route -info -obeyform climconfig route \ -add eth0 \ -default \ -gateway 15.146.232.1 #CLIMCMD expects 'exit' to be the last command. #This is required to terminate CLIMCMD session.
climconfig.sa(1) NAME climconfig.sa -- configure security associations SYNOPSIS The command for managing security associations to the configuration file ipsec-tools.conf is: 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 file racoon.
NOTE: The -manual part of the command must follow sa -add and sa -delete directly. sa -info displays security association configurations from the file ipsec-tools.conf or racoon.conf. If no options are selected, all the SAs are listed from both of these configuration files. sa -stop unloads security associations from the SAD. If you specify any of the optional parameters in the first group (-s, -p, -d, -i), you must specify all of them. sa -stop is one of the commands for deactivating VPN connections.
-p Specifies the protocol. protocol is one of : esp, ah, or ipcomp. You must specify one of these protocols. -u Upper layer protocol to be specified. Any of the protocols from the /etc/protocols file can be specified as upperspec, or icmp6, ip4, or any. any indicates any protocol. A protocol number can also be specified. -i spi Specifies the security parameter index (SPI) for the SAD. SPI must be a decimal number or a hexadecimal number with a 0x prefix.
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 or Algorithm. If -R is specified, the SPI field value is used as the IPComp compression parameter index (CPI) on wire as-is.
The src-ip and dst-ip pair, upperspec and spi value are optional parameters. If the src-ip and dst-ip pair are specified, all the SAs that match the src-ip and dst-ip are unloaded from 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 clim1 climconfig sa -add –manual –s 10.1.1.2 –d 10.3.3.
-A hmac-md5 0x12345678912345678912345678912345 –load > CLIMCMD clim1 climconfig sa -delete -manual –prov zsam1 -s 10.1.1.2 -d 10.3.3.2 -p esp -i 0x200 –unload -force > CLIMCMD clim1 climconfig sa -delete –prov ztc0 -s 10.1.1.2 -d 10.3.3.2 -u any > CLIMCMD clim1 climconfig sa –info –prov zsam1 > CLIMCMD clim1 climconfig sa –info –prov ztc1 –obeyform > CLIMCMD clim1 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.
climconfig.slaveinterface(1) NAME climconfig.slaveinterface -- configure bonding interfaces SYNOPSIS CLIMCMD {clim-name|ip-address} climconfig slaveinterface -configure bonding-interface-name { [-add interface-name ] [ -delete interface-name ] [ -primary interface-name ] | none ]}} climconfig.slaveinterface Description This 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.
Bonding is not supported for InfiniBand interfaces. CONSIDERATIONS The 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 slave interface.
climconfig.snmp(1) NAME climconfig.snmp -- configure snmp SYNOPSIS CLIMCMD {clim-name|ip-address} climconfig snmp -add trap-receiver-ipaddress CLIMCMD {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.
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.
climconfig.sp(1) NAME climconfig.
address[/prefixlen][[port]] -d dst-range Specifies the destination of the secure communication as an IPv4 or IPv6 address and an optional port number between square brackets. This takes the following form: address[/prefixlen][[port]] -u upperspec Specifies the upper layer protocol. Any of the protocols from the /etc/protocols file can be specified as upperspec, icmp6, ip4, or any. The any option indicates any protocol. You can also specify the protocol number.
-unload Causes the SP to be unloaded from the SPD. This parameter is optional, and is used with the sp -delete command. Unless you specify the -force parameter, you are prompted for confirmation for this command. -force Causes the command to run without confirmation. -obeyform Displays the security policy configuration in the format of add command(s). ERROR MESSAGES For sp -add: Please give the correct options. For sp -delete: Please give the correct options. (The incorrect option is displayed).
For sp -info: If no options are specified, the list of all security policies in the configuration file ipsec-tools-conf is displayed. EXAMPLES > CLIMCMD clim1 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 -mode tunnel -srcdst 10.2.2.1-10.2.2.2 -level require -load > CLIMCMD clim1 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 clim1 climconfig sp -delete -s 10.1.1.
climconfig.sysctl(1) NAME climconfig.sysctl -- set or display CLIM kernel parameters SYNOPSIS CLIMCMD {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-name param-value climconfig.sysctl Description This command sets the kernel parameter param-name values specified by param-value.
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.
climconfig.tunnel(1) NAME climconfig.tunnel -- modify tunnel configuration SYNOPSIS CLIMCMD {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.
PARAMETERS tunnel-interface Is the name of the tunnel interface to be added, deleted, or displayed. The tunnel interface name is case sensitive. all Displays the configurations of all the interfaces. -obeyform For a specified Tunnel interface name, displays Tunnel configuration in add command format. –ipaddress ipv6-address Is an IPv6 address. –netmask netmask Is the netmask for the IPv6 address, specified as a number of bits, for example, 64.
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. CONSIDERATIONS As of J06.10 and H06.
climconfig.vpn(1) NAME climconfig.vpn -- obtain information about virtual private networks SYNOPSIS CLIMCMD {clim-name|ip-address} climconfig vpn -status [-prov {prov—name | all}] [-s src-ip -d dst-ip] climconfig.vpn Description This command displays the status of the VPN connection established between the source and destination IP addresses. The security policy and the association loaded in the Security Policy Database (SPD) and Security Association Database (SAD) are displayed in that order.
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: 0 sadb_seq=3 pid=727 refcnt=0 10.2.2.1 10.1.1.
A SCF Error Messages This appendix describes the CIP subsystem SCF error messages. Error messages are listed with 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. Cause You entered a command that the CIP SCF product module does not support. Effect The SCF command is not executed. Recovery Check the SCF section of this manual for a list of supported commands.
CIP 00005 (zcip-err-wild-not-sup) CIP E00005 Object name object-name contains wild cards not allowed for this command. object-name Is the object name string that generated the error. Cause You attempted to use wildcard characters (*,?) in an object name for a command that does not support wild-cards. Effect The SCF command is not executed. Recovery Reissue the command without wild-card characters in the object name.
object-name Is the CLIM object specified in the ADD or ALTER PROVIDER, or ADD ROUTE command. Cause The CLIM name in an ADD or ALTER PROVIDER command is already assigned to another Maintenance Provider or the CLIM name in an ADD ROUTE command is already assigned to another Route with an overlapping IP-address family. Effect The CLIM cannot be assigned to two Maintenance Providers or Routes with an overlapping IP-address family.
location Is the CLIM location (group, module, slot, port, and, for systems that support it, fiber) that is invalid. Cause The 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. Effect The SCF command is rejected. Recovery Re-issue the command with a correct LOCATION.
Cause A DELETE CLIM command was issued for a CLIM object that is associated with an existing Provider object. You cannot delete a CLIM object until there are no PROVIDER objects dependent on the specified CLIM. Effect The SCF command is rejected. Recovery To remove the CLIM object, the PROVIDER object associated with the specified CLIM must be removed first. Use the INFO PROVIDER command to display the names of the providers and their associated CLIMs.
• Record information is corrupted • ConfigDB operation fails operation-type Specifies the operation the object was performing when the error occurred. The operations are: • Locking • Unlocking • Inserting • Deleting • Reading • Updating object-name Is the name of the object that generated the error. Cause The SCF command requires CIPMAN to manipulate the configuration database, but it failed as specified by the cause information. Effect SCF ignores the command.
CIP 00021 (zcip-err-cip-timeout) CIP 00021 CIP command timed out on object-name. object-name Is the name of the object that generated the error. Cause A command expired before a response from the CLIM was received. Effect The SCF command you entered was initiated, but successful completion cannot be guaranteed. Recovery If 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.
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. Cause You attempted to use an object name in an ADD command that is currently cannot be used within CIP subsystem for the specified object type. Effect The SCF command is not executed. Recovery Reissue the ADD command using different object name.
Recovery Reissue 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. Cause You issued a TRACE command with a LOCKSIZE value that was greater than the PAGES value. Effect The SCF command is not executed. Recovery Retry the command with a LOCKSIZE value that is less than or equal to the PAGES value.
Recovery Reissue the SCF command. If the problem persists for more than a short duration, locate the problematic CIPMON process and fix the cause for that CIPMON process' inability to process the request from the CIPMAN process. CIP 00033 (zcip-err-sub-not-stopped) CIP E00033 One or more subordinate objects cannot be stopped.
Effect The SCF command is rejected. Recovery Reissue the SCF command with different provider that has the correct type or reissue SCF command with option that is compatible with the provider type. Use the INFO PROVIDER command to display the type of each provider. CIP 00037 (zcip-err-invalid-clim) CIP E00037 CLIM object-name is invalid for this request. object-name Is the CLIM object specified in the ADD or ALTER PROVIDER, ALTER CLIM, or ADD ROUTE command.
Cause A 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 no reference from Storage Subsystem to the specified CLIM. Effect The SCF command is rejected. Recovery To remove the CLIM object, the dependency of Storage Subsystem on the specified CLIM must be removed first. See Storage Subsystem for more details.
Effect The SCF command is rejected. Recovery To remove the IPDATA provider object, the CLIM object associated with the specified IPDATA provider must be removed first. Use the INFO PROVIDER, DETAIL command to display the names of the CLIM associated with that IPDATA provider. CIP 00042 (zcip-err-object-unremovable) CIP E00042 PROVIDER object-name cannot be deleted. object-name Is the PROVIDER object specified in the DELETE PROVIDER command.
Effect The SCF command is rejected. Recovery Reissue SCF command with the correct interface name. CIP 00046 (zcip-err-intf-fover-invalid CIP E00046 Interface interface-name failover configuration cannot currently fail over. interface-name Is the interface name affected by the SWITCH CLIM command. Cause A SWITCH CLIM command was issued, either implicitly or explicitly, that affects an interface which is configured for failover, but the current condition makes failover to another CLIM impossible.
Recovery Stop the CLIM(s) associated with the Provider by using the INFO PROVIDER, DETAIL command to display the list of CLIMs associated with the Provider and then using the STOP or ABORT CLIM command to stop the associated CLIM(s). Reissue the SCF ALTER PROVIDER command. CIP 00049 (zcip-err-ipaddr-invalid CIP E00049 ip-address is invalid. ip-address Is the IP address specified in the ADD CLIM command. Cause The specified IP address is not a valid IP address for a maintenance Provider.
Recovery Re-issue the command with a valid PRIORITY attribute value. CIP 00053 (zcip-err-active-mon) One or more CIPMON processes are still running. Cause A STOP PROCESS SCF request failed to stop the CIPMAN process because one or more CLIM or PROVIDER objects are not in a STOPPED state and one or more CIPMON processes are still running (i.e., one or more MON objects not in a STOPPED state). Effect The CIPMAN process is not stopped.
with that provider. On each CLIM, use “climconfig interface –info all” to list all interfaces with their associated provider to find all interfaces associated with that provider on that CLIM. CIP 00056 (zcip-err-prov-not-exist) Provider prov-name does not exist. prov-name is the PROVIDER name specified in the SWITCH CLIM command. Cause A SWITCH CLIM command was issued for a provider that does not exist. Effect The SCF command is rejected. Recovery Reissue SCF command with the correct provider name.
clim-name is the CLIM object specified in the SWITCH CLIM command. prov-name is the PROVIDER name specified in the PROVIDER option of the SWITCH CLIM command. Cause A SWITCH CLIM, PROVIDER command was issued for a provider that does not have any association with network resources configured on the specified CLIM. Effect The SCF command is rejected. Recovery Reissue SCF command with the correct provider name. (SCFPM Note: prov-name is from zcip-tkn-provider-name.
B Fault Codes This appendix documents fault codes that belong to the CIP subsystem and can appear in CIP subsystem 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.
Effect For reading of a non-critical configuration database record, CIPMAN continues without access to the object corresponding to the configuration database record. For a critical configuration database record, CIPMAN terminates and the backup CIPMAN takes over. Recovery None. This is an informational event. However, if an existing CIP subsystem object (such as a CLIM or Provider) is unexpectedly missing, you may want to restart the CIPMAN process.
Effect The CIPMON process terminates. In an extreme case, the CIPMON processor may be halted. Recovery If the CIPMON processor is not halted, no recovery action is required. The CIPMON process is restarted automatically by the persistence manager. If the CIPMON processor is halted, perform a dump operation and reload the processor.
Origin “CIPMON” Fault Code 2022 Cause The CIPMON process receives a response message from a CLIM that has a CLIM type that was not expected for that type of request. Effect The message is dropped. Recovery Make sure the correct and matching software is running on both the NonStop host system and on the CLIM. Origin “CIPMON” Fault Code 2030 Cause A CIPMON process in either the STARTING or STARTED state is incompatible with the current CIPMAN process.
Effect The CIP subsystem does not function properly. The CIP subsystem access through that processor is not available. Recovery Install the correct, compatible version of CIPMAN and CIPMON. Origin “CIPMON” Fault Code 2034 Cause A CIPMON process is taking unusually long time to process a set of requests. This can be caused by insufficient QIO memory resources. Effect Requests that goes through that particular CIPMON (such as some sockets operations and some SCF requests) can be slower than normal.
Effect The ALTER PROVIDER request fails. Recovery If this problem persists, send complete information to your HP support provider for analysis. Origin “CIPSREQ” Fault Code 3005 Cause One or more parameters that CIPMON passed into the CIP subsystem dynamic link library (ZCIPDLL) are invalid. Effect The operation fails. Recovery Make sure the correct and matching CIPMON and ZCIPDLL are running. If not, this is a serious problem. Send complete information to your HP support provider for analysis.
Recovery This is a serious problem. Send complete information to your HP support provider for analysis. Origin “CIPSREQ” Fault Code 3017 Cause The 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. Effect The IP address or route is not updated within the CIP subsystem dynamic link library (ZCIPDLL) in that processor. Recovery If the problem persists, a CLIM reboot is recommended.
Effect Access to the CLIM is lost. Recovery None. The CIP subsystem should automatically recover. Origin “CIPSREQ” Fault Code 3024 Cause The CIP subsystem dynamic link library (ZCIPDLL) detects that the specified CLIM has an invalid operation mode or has an invalid associated PROVIDER object. Effect The CLIM object is not added. Recovery Make sure that the correct and matching NonStop host software (CIPMAN, CIPMON and ZCIPDLL) are running. If mismatched software is not the cause, this is a serious problem.
0x80 mismatch for ending ephemeral port number Item defined in sysctl parameter net.ipv4.ip_local_port_range and PROVIDER share-ports value: 0x100 ephemeral port range start or end exceeds 65535 Item defined in sysctl parameter net.core.wmem_default: 0x200 mismatch for default socket send buffer Item defined in sysctl parameter net.core.wmem_max: 0x400 mismatch for maximum socket send buffer Item defined in sysctl parameter net.core.
Effect The CLIM object cannot be added. Recovery For ErrorDetail1 = -1, check the version of MEASURE. For ErrorDetail1 = 1, retry the operation. For all other ErrorDetail1 values, send complete information to your HP service provider for analysis. Origin “CIPSREQ” Fault Code 3031 Cause The CIP subsystem dynamic link library (ZCIPDLL) receives a local IP address from the CLIM that already exists for a different interface within the same provider.
Recovery This is a serious problem. Send complete information (both NonStop host system and CLIM) to your HP support provider for analysis. Origin “CLIMAGT” Fault Code 5121 Cause The processor number associated with the START CLIM request from the NonStop host system is not valid (for example, not between 0 and 15). Effect The current START CLIM request is rejected. CLIM is not accessible from that NonStop host system processor. Recovery This is a serious problem.
Effect The current CLIM request failed. Recovery Make sure there is sufficient memory on the CLIM. If the problem persists, reboot the CLIM. Origin “CLIMAGT” Fault Code 5127 Cause The CLIMAGT did not receive configuration information from CLIMMON. Effect The current CLIM request failed. Recovery Check if the CLIMMON process is running. Restart the CLIMMON process if necessary. If the problem persists, send complete information to your HP service provider for analysis.
Recovery None. The CIP subsystem should automatically recover. If the problem persists, send complete information (especially on the NonStop host system side including CIPMAN) to your HP support provider for analysis. Origin “CLIMAGT” Fault Code 5134 Cause The visiting interface specified in the current request is associated with a local interface that is currently not active. The visiting interface can be brought up on the backup CLIM only if its backup interface is active on the backup CLIM.
Origin “CLIMAGT” Fault Code 5152 Cause The interface activation failed. This can be caused by an interface configuration problem, the interface still being active on a different CLIM, or other internal problems. Effect The current CLIM request failed. The current CLIM request failed. The specified interface cannot be brought to the active state. Recovery Make sure the CLIM has correct and valid configuration information (by using the climconfig command).
Effect That CLIM is not accessible from that NonStop host system processor. Recovery Make sure the version of software running on the NonStop host system and the CLIM are correct and match with each other. Otherwise, if the problem is resources related and persists for an extended period of time, reboot the CLIM. Origin “ITAPI” Fault Code 8197 Cause An attempt to establish the IT-API connection between the NonStop host system processor and a CLIM has failed.
Index #ZZCIP, 73 $SYSTEM.ZTCPIP, 74 $ZCLA collector, 108 $ZPM, 73 $ZZCIP, 220 $ZZSTO, 204 192.168.*.
failover architecture, 36–48 IP CLIM overview, 52–55 multiple CLIMs per Provider, 32 object, definition, 219 overview, 27 SNMP support, 51 software installation, 137 stopping, 118 Storage CLIM overview, 58 Telco CLIM overview, 52 timezone, 121 valid locations, 227 clim command, 120, 292 CLIM firmware upgrade with system down, 168 upgrade with system running, 150 CLIM software upgrade with system down, 166 upgrade with system running, 136 CLIM software and firmware, upgrading, 136 CLIM-to-CLIM failover as in
overview, 174–203 PORT-SHARE-ENABLE-ALL, not supported, 202 program name, 174 receiving broadcasts on specific addresses, 189 remote sockets, 184 resources, 183 retransmission timeout count, 191 RFC1323–ENABLE, 196 round-robin socket support considerations, 190 routes, deleting and adding, 190 routing differences, 183 setsockopt calls, 191–190 SLSA subsystem, 175, 182 SNMP TCPIPSA subagent, 175 socket loopback bind behavior, 186 socket migration, 183 socket option default differences, 193 socket options, 19
overview, 50 Downgrade see Falling back DP2 see Disk Process 2 E EAGAIN error, 184 Echo, 117 Enclosures command, LUN manager, 171 ENOPROTOOPT, 193 Environment, home terminal, 116 Ephemeral ports, 196 Errors, suppressing, 188 ESRCH error, 184 ESS disk volume, naming convention, 63 Eth0, 29 Eth0:0, 28 Ethernet 4 ServerNet adapter, 113 Ethernet LAN status information, 88 Ethernet subagent (ETHSA), 51 ethtool Linux command, 69 ethtool, displaying link speed, 122 Event logging, 121 Event Management System (EMS)
High UDP Sockets, 255 Home terminal, 116, 117 Host name CLIM, 81 NonStop host system, 74 HOSTID, MON attribute, 195 hostname, climconfig command, 313 HOSTNAME, MON attribute, 196 HOSTS file, 50 see also ADD DEFINE command DNS file, 77 editing, 75 How to activate an interface, 102 add a default route, 66 change interface configuration, 66 change Providers for a CLIM, 130 change TCP/IP environments for applications, 168 configure CIP, 72 configure eth2 through eth5 data interfaces, 65 configure failover, 66 c
configuring security policies, 105 controlling Virtual Private Network, 107 displaying information, 87 files, 49 hash names, 104 managing, 107 new error codes, 184 overview, 48–50 sa climconfig command, 362 IPSEC, climconfig script, 108 iptables, climconfig command, 324, 336 IPv6 configuring, 113 migration behavior of, 40 IT-API, 414 Joined-group multicast IP addresses, 40 Jumbo frames, 314 Ethernet interface, 174 SCF ALTER command, 177 tunnel interface, 379 Logging, 121 Logical interface (eth0:0), 28 Log
MIN-EPHEMERAL-PORT, 196 minimum time for retransmission timeouts, 191 MON attributes, 194 moving from G4SAs, 183 multicast bind, set or join, 189 multicast loopback, 189 multiple listeners, 34 ND6HOSTD process, 175 network partitioning, 182 new error codes for aborted CIPSAM process, 186 new error codes for IPSec, 184 new socket option, 192 new UDP error, 189 NONSHAREDOUTDIST, not supported, 201 operational differences, 175–187 operational differences, CIPSAM, 186 overview, 174–175 PORT-SHARE-ENABLE-ALL, no
netstat Linux command, 70 Network partitioning, 182, 183 Network-sensitive commands, provider specified, 69, 86, 119, 126 NETWORKS file, 77 Nonsensitive commands, 223 NONSHAREDIP failover option, alternatives in CIP, 183 NONSHAREDOUTDIST, not supported, 201 NonStop I/O Essentials, 31 NonStop SQL/MP, 204 NonStop SQL/MX, 204 NonStop TCP/IPv6, coexistence with, 113 Null object, 217 O Object specifiers, 221 Object types CIPMAN, 218 CIPSAM, 219 CLIM, 219 MON, 219 overview, 217 ROUTE, 220 SUBNET, 220 Object-name
rm Linux command, 70 rmdir Linux command, 70 Round-robin CLIM routing, 35 filtering, 112 socket support considerations, 190 ROUTE object, description, 220 route, climconfig command, 356 Routes deleting and adding migration differences, 190 migration differences, 183 policy based, 81 routing behavior, 34 tracing, 119 RUN command, LISTNER, 101 S SA see Security association SAS disk volume , naming convention, 63 Scan command, LUN manager, 172 Scout, CLIM software, 137 SCTP adding to PROTOCOLs file, 78 config
Supported interface types, 174 Supported IP protocols, 32 Supported Telco protocols, 32 Suppressing compatibility errors, 188 SWAN adapter, 64 configuring adapters on a CLIM, 187 multiple paths in a single Provider, 34 SWITCH CLIM $ZZSTO, 204 SWITCH command definition and usage, 273 for storage subsystem, 204 migration differences, 183 Synchronization of time on CLIMs, 121 synopsis, climconfig command, 362 sysctl, climconfig command, 376 System configuration database adding CIP processes to, 72 managing, 11
process, 175 PROVIDER object, 219 restricting access to, 182 SCF object for, 219 selecting, 174 setting, 203 stopping, 176, 181 TPNAME attribute, 229 TPName attribute, 239, 240 Trapdests SNMP, configuring, 51 SNMP, displaying, 87, 92 Troubleshooting CLIMCMD command, 120 duplicate IP addresses, 122 network applications, 126 routing, 85 tools, 119 with tcpdump, 126 tunnel, climconfig command, 378 U UDP BRECVPORT attribute, 229 connect, failover behavior, 46 defining, PROTOCOL file, 78 displaying current sock
