HP-UX Containers (SRP) A.03.00 Administrator's Guide

59
ROUTE_MASK[10]=”255.255.255.0”
ROUTE_GATEWAY[10]=”<Gateway2_IP>”
ROUTE_COUNT=[10]=”1”
ROUTE_ARGS[10]=””
ROUTE_SOURCE[10]=”<container_IP>”
The <Gateway2_IP> field must be reachable from the <container_IP> address by being
on the same subnet as the <container_IP> address.
NOTE: You should be familiar with shell scripting when managing the network configuration, as well
as syntax for the route(1m) and ifconfig(1m) commands.
12.4 Network configuration for the global view
Any IP address that is not associated with a container will be managed as belonging to the global
view. When you run the srp_sys -setup command, the tool defines a compartment rule that
associates all global view IP addresses with the INIT-private compartment. When a process
running in the global view needs to connect to another system, the source IP address is chosen from a
set of global view IP addresses. To see the list of IP addresses that are active for the global view, run
getrules –T INIT-private to generate a list of addresses that are available.
Several fields in the /etc/rc.config.d/netconf file have significance in the HP-UX Containers
enabled configuration. Fields to note include:
INTERFACE_SKIP
Determines whether /sbin/net script will enable the interface
entry. A default value of “false” implies the entry will be created on
system boot and when the script is manually run.
A container interface should always be set to “true”.
INTERFACE_STATE
Determines the default state of an interface entry. Valid values are
“up”, “down”, and “force”. The default is “up”. The “force”
state is used in conjunction with interfaces that support force-to-wire
behavior.
ROUTE_SKIP
Determines whether /sbin/net script will enable the route entry. A
default value of “false” implies that the entry will be created on
system startup and when the script is run manually.
A container route entry should always be set to “true”.
ROUTE_PARAMS
Any trailing arguments that the route(1m) command supports can
be included. The “force” option can be used for route entries where
the force-to-wire behavior is needed.
ROUTE_SOURCE
Explicitly identifies the source IP address to be used for the route entry.
This is required by all container route entries, and HP recommends it
for all global view routes as a best practice.
IPV4_CMGR_TAG and
IPV6_CMGR_TAG
Container specific field inserted by the srp command to manage all
container related entries in the netconf file or netconf-ipv6 file.
This field is required for every container interface entry to identify the
associated container and the container instance id.
When manually managing route and interface entries in the /etc/rc.config.d/netconf and
/etc/rc.config.d/netconf-ipv6 files, pay attention to the index of each array variable that is
specified. There is no correspondence in the index used for route entries and the index used for
interfaces. The IPV4_CMGR_TAG and IPV6_CMGR_TAG values are used to identify container