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
2009/5/29 Димитър Бойн :
> Thank you, Neil!
>
> I have already tried this but eth0 has IP Address "on boot"
> The resource does not start if I change the "nic" value tp eth0 only :(
> and I indeed need it to be just additional eth0:0.
Thats what it would normally do.
It adds an alias to an already
d need it to be just additional eth0:0.
Any ideas what could be wrong?
Thanks!
./Dimitar Boyn
-Original Message-
From: Neil Katin [mailto:linu...@askneil.com]
Sent: Thursday, May 28, 2009 9:29 PM
To: pacema...@clusterlabs.org
Subject: Re: [Pacemaker] eth0:0: warning: name may be invalid
Use &q
sage-
From: Neil Katin [mailto:linu...@askneil.com]
Sent: Thursday, May 28, 2009 9:29 PM
To: pacema...@clusterlabs.org
Subject: Re: [Pacemaker] eth0:0: warning: name may be invalid
Use "eth0", not "eth0:0" for the "nic" nvpair.
As the script built-in docs say:
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
