Cluster I/O Protocols (CIP) Configuration and Management Manual (H06.16+, J06.05+)

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.
NOTE: The round-robin feature is used only for listening (server) sockets and not client sockets.
Logging Messages
The CLIM software logs error and some informational messages to /var/log/syslog as do the
kernel and most other applications. Messages from the CLIM software always include the component
name. The messages are forwarded to the Event Management System (EMS) on the NonStop host
system.
Configuring IPv6 (IP CIP)
This section provides an example of configuring IPv6.
1. Configure IPv6 for the eth4 interfaces on each CLIM:
> CLIMCMD n1002532 climconfig ip -add eth4
-ipaddress 2001:0db8:0:0:0:0:1428:57ab -netmask 64
This interface is installed in network 2001:0db8:0:0/64.
> CLIMCMD n1002531 climconfig ip -add eth4
-ipaddress 2001:0db8:0:0:0:0:1428:57ac -netmask 64
This interface is also in network 2001:0db8:0:0/64.
2. Add a default IPv6 static route to the eth4 interfaces on each CLIM.
> CLIMCMD n1002532 route –add eth4 -default –gateway 2001:0db8:0:0:0:0:0:1
> CLIMCMD n1002531 route –add eth4 -default –gateway 2001:0db8:0:0:0:0:0:1
Running Applications in Multiple Environments (IP CIP)
You may run applications in the conventional TCP/IP, NonStop TCP/IPv6 and CIP environments.
If you are using ATM or token-ring adapters your applications must use conventional TCP/IP. If
you are using Ethernet adapters, you can run your application in all environments.
Conventional TCP/IP and NonStop TCP/IPv6 environments cannot share the same LIF but they can
share an Ethernet 4 ServerNet adapter (E4SA) or Gigabit Ethernet 4-port ServerNet adapter (G4SA)
as those adapters have multiple LIFs. However, a Fast Ethernet ServerNet adapter (FESA) and a
Gigabit Ethernet ServerNet adapter (GESA) have only one LIF, so they can only support one
environment. Only CIP can run on a CLIM.
Managing the Configuration Preservation
The system configuration database (CONFIG) is part of the NonStop Kernel subsystem. The
conventional TCP/IP subsystem (NonStop TCP/IP) does not participate in the system configuration
database, but NonStop TCP/IPv6 and CIP do (although their configuration databases are not
compatible). When you configure CIP for the first time, the SCF objects are added to the system
configuration database and any alterations to those objects also update the configuration of those
objects in the system configuration database. The system configuration database stores your
subsystem configuration and can be accessed at any time to restore the subsystem to its last
configuration.
The CIPMAN, when started, starts any subordinate objects that are stored in the system configuration
database.
Logging Messages 113