Set the EPROM variable to assign unique MAC addresses to all ethernet interfaces on the host:
# eeprom local-mac-address?=true
Reboot the system after setting the eprom variable to complete the address setup. The base IP addresses must be configured on the interfaces before the MultiNICB agent controls the interfaces. You can configure these addresses at system start up using /etc/hostname.XXX initialization files. Refer to the following examples for more information.
These examples demonstrate setting up test IP addresses for your clustered systems. These IP addresses allow the agent determine if the NIC works. The agent determines that the NIC works if it receives responses for the ping packets that it sends to other nodes on the network. You do not need to perform the following steps for the floating IP addresses. The agent performs these steps.
In the file /etc/hostname.qfe0, add the following two lines:
north-qfe0 netmask + broadcast + deprecated -failover up \
addif north netmask + broadcast + up
Where north-qfe0 is the test IP address that the agent uses to determine the state of the qfe0 network card.
In the file /etc/hostname.qfe4, add the following line:
north-qfe4 netmask + broadcast + deprecated -failover up
Where north-qfe4 is the test IP address that the agent uses to determine the state of the qfe4 network card.
In the example, north-qfe0 and north-qfe4 are the host names that correspond to test IP addresses. north is the host name that corresponds to the test IP address.
<resource name="mnb_res1" type="MultiNICB">
<attribute name="Device" context = "sysA">
<val key="en1">11.123.148.47</val>
<val key="en2">11.123.148.48</val>
<attribute name="Device" context = "sysB">
<val key="en1">11.123.148.49</val>
<val key="en2">11.123.148.50</val>
<attribute name="Gateway"><scalar>11.123.144.1</scalar> </attribute>
<resource name="ipmb_res1" type="IPMultiNICB">
<attribute name="Address"><scalar>11.123.148.51</scalar> </attribute>
<attribute name="MultiNICBResName"><scalar>
VR_Group.mnb_res1</scalar></attribute>
<attribute name="NetMask"><scalar>255.255.252.0 </scalar></attribute>
<link parent="ipmb_res1" child="mnb_res1"/>
Device@sysa = { en0 = "10.128.8.42", en1 = "10.128.8.43" }
Device@sysb = { en0 = "10.128.8.44", en1 = "10.128.8.45" }
NetworkHosts = "10.128.8.10 10.128.8.45"
The following is an example IPMultiNICB and MultiNIC_Unix configuration for HPUX.
<resource name="mnicb" type="MultiNICB">
<attribute name="NetworkHosts">
<resource name="ipmnicb" type="IPMultiNICB">
<attribute name="Address"><scalar>"1.1.1.4"</scalar> </attribute>
<attribute name="BaseResName"><scalar>"mygrp1.mnicb" </scalar></attribute>
<attribute name="NetMask"><scalar>"255.255.255.0" </scalar></attribute>
<link parent="ipmnicb" child="mnicb"/>
<resource name="ipmnicb1" type="IPMultiNICB">
<attribute name="Address"><scalar>"1.1.1.5"</scalar> </attribute>
<attribute name="BaseResName"><scalar>"mygrp1.mnicb"
<attribute name="NetMask"><scalar>"0xFFFFFF00"</scalar> </attribute>
<link parent="ipmnicb1" child="mnicb"/>
<resource name="mnb_res1" type="MultiNICB">
<attribute name="Device" context = "sysA">
<val key="bge1">11.123.148.33</val>
<val key="bge2">11.123.148.34</val>
<attribute name="Device" context = "sysB">
<val key="bge1">11.123.148.35</val>
<val key="bge2">11.123.148.36</val>
<resource name="ipmb_res1" type="IPMultiNICB">
<attribute name="Address"><scalar>11.123.15.72</scalar> </attribute>
<attribute name="BaseResName"><scalar>VR_Group.mnb_res1 </scalar></attribute>
<link parent="ipmb_res1" child="mnb_res1"/>
UserNames = { admin = "cDRpdxPmHpzS." }
SystemList = { north = 0, south = 1 }
AutoStartList = { north, south }
// A parallel group for the MultiNICB resource
SystemList = { north = 0, south = 1 }
AutoStartList = { north, south }
Device @north = { qfe0, qfe4 }
Device @south = { qfe0, qfe4 }