Use "eth0", not "eth0:0" for the "nic" nvpair.
As the script built-in docs say:
The base network interface on which the IP address will be brought
online.
If left empty, the script will try and determine this from the
routing table.
Do NOT specify an alias interface in the form eth0:1 or anything here;
rather, specify the base interface only.
Димитър Бойн wrote:
Hi,
How do I get rid of these type warnings? -
“May 28 18:56:52 c001mlb_node01a lrmd: [18066]: info: RA output:
(ip-c001drbd01a:monitor:stderr) eth0:0: warning: name may be invalid”
My resource is configured (and seems to work just fine) by:
<primitive class="ocf" provider="heartbeat" type="IPaddr2"
id="ip-c001drbd01a">
<instance_attributes id="ia-ip-c001drbd01a">
<nvpair id="ia-ip-c001drbd01a-ip" name="ip" value="192.168.80.213"/>
<nvpair id="ia-ip-c001drbd01a-nic" name="nic" value="eth0:0"/>
</instance_attributes>
<operations>
<op id="op-ip-c001drbd01a" name="monitor" interval="21s"
timeout="5s"/>
</operations>
</primitive>
Thanks!
./Dimitar Boyn
------------------------------------------------------------------------
_______________________________________________
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
_______________________________________________
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
