Le 19/06/2013 16:40, Jakob Curdes a écrit :
Hi, I amtrying to setup IPaddr2 resources on a cman-managed cluster
which need to be bound to VLAN interfaces on linux. I have something like
bond1 with a static address 192.168.10.2
bond1.0001 (unnumbered)
and want to configure a IPaddr2 resource on bond1.0001.
However regardless what I try it does not work; I tried using the nic
parameter and the label parameter, passing the VLAN ID as label:
pcs resource create VLAN_003_IP ocf:heartbeat:IPaddr2 ip=192.168.11.2
cidr_netmask=24 op monitor interval=30s nic=bond1 iflabel=0003
ERROR: Unable to create resource/fence device
Call cib_create failed (-76): Name not unique on network
It seems that in the old heartbeat v1 times it was possible to specify a
VLAN interface with something like
192.168.1.1/29/eth0.30
How can I do this nowadays?
Thank you for hints,
Jakob Curdes
I do not use pcs but I have, as many people a lot of the following
resources:
primitive eth0.8HA ocf:heartbeat:IPaddr2 \
params ip="192.168.X.Y" cidr_netmask="28" nic="eth0.8" \
op monitor on-fail="restart" interval="10s"
$ ip addr ls eth0.8
16: eth0.8@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1496 qdisc
noqueue state UP
link/ether 00:14:22:21:59:81 brd ff:ff:ff:ff:ff:ff
inet 127.10.10.10/32 brd 127.10.10.10 scope host eth0.8
inet 192.168.X.Y/28 brd 192.168.X.Z scope global eth0.8
It works just fine.
The vlan interface must be up (as in ifup eth0.8) and also need to
satisfy the following requirement from "sudo crm ra meta IPaddr2" (hence
the 127.10.10.10/32 IP):
"There must be at least one static IP address, which is not managed by
the cluster, assigned to the network interface."
--
Cheers,
Florian Crouzat
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
