The questions you should be asking your DBA are:
- Are these addresses supposed to be fixed to this particular RAC cluster node, or movable to another node?
- If movable, is the RAC setup going to use HP Serviceguard or perhaps Oracle Clusterware to manage the movable cluster resources?
If these addresses are supposed to always stay on this node, then they are regular IP Aliases. There is no difference in setting them up on APA devices vs. regular NICs.
An IP Alias, also known as a secondary IP address, is automatically generated when you use ifconfig to assign an IP address to lan<existing interface>:<alias number> and deleted when you set its IP address to 0.0.0.0. In /etc/rc.config.d/netconf file, these are configured just like regular network interfaces.
Serviceguard also has a command for assigning an IP alias to a particular interface with a dynamically-chosen alias number, but you don't need it if you want to keep the alias numbers fixed. (Note: alias number 0 means the "main" IP adress for the interface, i.e. "lanXX:0" is the same as just "lanXX".)
If these addresses are supposed to be movable, then they should be configured to the cluster infrastructure that is supposed to move them when necessary. In HP-UX RAC setups, this is often HP Serviceguard, but I think it may be possible to use Oracle Clusterware for this purpose too.
If Oracle Clusterware is being used,
lan900:801 1500 10.0.12.0 10.0.88.33 365885981 0 10611780 0 0
lan900:802 1500 10.0.12.0 10.0.88.37 6031497 0 359001 0 0
These two lines look a bit odd. Are they from the output of "netstat -i" or a similar command?
Anyway, they don't quite have the right information for configuring the network interfaces. At minimum, you'll need two things for each interface (or alias): the desired IP address and the netmask. This output only reveals the IP addresses used, but it won't specify the netmask exactly: there is only the network address and the interface IP address.
Also, the information on those lines doesn't seem to be quite consistent: with a network address like 10.0.12.0, you would expect the netmask to be 255.255.255.0, but then 10.0.88.* does not fit into that network. If you relax the netmask enough to allow 10.0.12.* and 10.0.88.* to fit in the same IP network segment, then the network address won't be valid any more.
The tightest netmask that allows 10.0.12.* and 10.0.88.* to exist in the same IP segment is /17 = 255.255.128.0, but then the network address must be 10.0.0.0, according to the ipcalc tool on my Linux system:
$ ipcalc 10.0.12.0/17
Address: 10.0.12.0 00001010.00000000.0 0001100.00000000
Netmask: 255.255.128.0 = 17 11111111.11111111.1 0000000.00000000
Wildcard: 0.0.127.255 00000000.00000000.0 1111111.11111111
=>
Network: 10.0.0.0/17 00001010.00000000.0 0000000.00000000
HostMin: 10.0.0.1 00001010.00000000.0 0000000.00000001
HostMax: 10.0.127.254 00001010.00000000.0 1111111.11111110
Broadcast: 10.0.127.255 00001010.00000000.0 1111111.11111111
Hosts/Net: 32766 Class A, Private Internet
MK
