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

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).
NOTE: The CLIM hostname must match the SCF CLIM object name. If the CLIM hostname and
SCF CLIM object name do not match, the CLIM does not go to the STARTED state.
Defining Networking Interfaces (IP CLIM Only)
The CLIMCMD climconfig interface command sets the protocols, IP addresses, and other parameters
for the interface. Using this command, you can add an interface, delete an interface, view and
modify attributes of existing interfaces. See climconfig.interface(1).
You may configure the interfaces eth1, eth2, eth3, eth4, and eth5 for data communications. Eth0
and eth0:0 are pre-configured.)
Mapping IP Addresses to Ethernet Addresses (ARP) (IP CLIM Only)
ARP maps IP addresses to hardware MAC addresses. The CLIM usually builds the ARP cache
automatically as it discovers the MAC addresses of other entities, but you can also add, delete,
and view ARP cache entries by using the “climconfig.arp Description” (page 304).
Policy Based Routing
NOTE: Policy based routing applies to all providers for CLIMs with the MULTIPROV ON option.
For J06.04 to J06.09 and H06.16 to H06.20 RVUs, you cannot associate an application with a
specific interface on a CLIM by binding to the IP address configured on that interface. For these
RVUs, if you need to restrict access of an application to an interface, you can use one interface
or set of interfaces on a CLIM by just adding a subset of the possible physical interfaces (for
example, eth1 and eth2).
As of J06.10 and later J-series RVUs and H06.21 and later H-series RVUs, you can use policy
based routing to ensure that the interface with the IP address bound to a socket will be used by
that socket for outgoing network traffic, or that an interface with an IP address in the source address
of the network packet is used for routing the packet. This feature is enabled by default, but you
can disable it.
Use the CLIMCMD {clim-name | ip-address} clim command to enable or disable policy
routing. The default is on. See “CLIMCMD clim Command” (page 120) for syntax.
Figure 18: Bound Socket Problem Configuration Without Policy Based Routing (page 82) and
Figure 20: Server Socket Problem Configuration Without Policy Based Routing (page 84) show
configurations that may encounter routing problems. Figure 19: Bound Socket Problem Configuration
With Policy Based Routing (page 83) and Figure 21: Server Socket Problem Configuration With
Policy Based Routing (page 85) show the same configurations with policy routing enabled, which
alleviates the routing problems.
Policy Based Routing 81