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

60
MEM Entitle:25.00% MEM Max:(none) Usage:6.85%
CPU Entitle:7.69% CPU Max:(none) Usage:0.00%
If you need to modify any of the managed networking service fields for an existing container instance,
use the
srp –replace containername –service network –id <instance> command to alter
one or more of the existing values for the container instance. The instance value should exist in the
container configuration. Refer to the
srp –list containername –service network –v output for
appropriate instance reference.
Example 12.5: Replacing the network configuration for id 3
# srp -r myContainer -s network -id 3 ip_address=fe80::4 iface=lan0
Enter the requested values when prompted, then press return.
Enter "?" for help at prompt. Press control-c to exit.
Add IP address to netconf file? [yes]
Gateway server IP address: [0]
Press return or enter "yes" to process this template.
Do you wish to continue? [yes]
replace compartment network service rules succeeded
replace ipaddress fe80::4 succeeded
12.3 Configuring additional routing entries
You can configure additional routing entries for each container by modifying the global view
/etc/rc.config.d/netconf[-ipv6] configuration file. HP recommends that you copy an
existing route entry for the chosen container, and then modify it so it reflects the desired settings for
the container’s new route entry. The ROUTE_SOURCE field for the new entry must match a valid IP
address for the container (this serves as the tag for route entries). Also, to make sure that the route
entry is only applied when the IP address is available for the container, configure the ROUTE_SKIP
field for the new route entry to “true”. Edit the appropriate netconf file (netconf for IPv4
addresses and netconf-ipv6 for IPv6 addresses) as follows:
1. Copy an existing routing entry that matches the container IP address for which you want to
add a new routing entry.
For example:
ROUTE_DESTINATION[1]="default"
ROUTE_SKIP[1]=”true”
ROUTE_MASK[1]=""
ROUTE_GATEWAY[1]="<GatewayIP>"
ROUTE_COUNT[1]="1"
ROUTE_ARGS[1]=""
ROUTE_SOURCE[1]="<container_IP>"
2. Change the array index ([1] in the example above) for each variable in the new block to an
unused number (for example, [10]they do not have to be sequential).
3. Modify the necessary fields to create a net route entry for the 192.168.1.0 network, keeping
the container IP address of the ROUTE_SOURCE[] entry intact for the matching container.
For example:
ROUTE_DESTINATION[10]=”192.168.1.0”
ROUTE_SKIP[10]=”true”