control Live mig network choice

stefws

Member
Jan 29, 2015
302
4
18
Denmark
siimnet.dk
Got a testlab with two cluster networks, a private 3x1Gbs bonded and a public 100Mbs:

corosync.conf snippet:
...
nodelist {
node {
name: node5
nodeid: 3
quorum_votes: 1
ring0_addr: 10.0.0.55
ring1_addr: <public node5>
}
node {
name: node6
nodeid: 2
quorum_votes: 1
ring0_addr: 10.0.0.56
ring1_addr: <public node6>
}
node {
name: node7
nodeid: 1
quorum_votes: 1
ring0_addr: 10.0.0.57
ring1_addr: <public node7>
}
}

# Both networks works fine:
# corosync-cfgtool -s
Printing ring status.
Local node ID 2
RING ID 0
id = 10.0.0.56
status = ring 0 active with no faults
RING ID 1
id = <public node6>
status = ring 1 active with no faults

I just want to make sure live migration always happens across ring0 network, thus I've assigned unqualified host names in /etc/hosts to ring0 NW:

/etc/hosts snippet:
...
#
# Ceph vlan 10
10.0.0.1 n1.ceph n1
10.0.0.2 n2.ceph n2
10.0.0.3 n3.ceph n3
10.0.0.4 n4.ceph n4
#
# PVE ring0
10.0.0.55 node5 node5.ring0
10.0.0.56 node6 node6.ring0
10.0.0.57 node7 node7.ring0

node6# cat /etc/resolv.conf
search <public domain>
nameserver <NS1>
nameserver <NS2>

node6# cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.

passwd: compat
group: compat
shadow: compat
gshadow: files

hosts: files dns
networks: files

protocols: db files
services: db files
ethers: db files
rpc: db files

netgroup: nis

only live mig. don't pick the ring0 (privat) network now but ring1 (public), it briefly did pick ring0 before last 'dist-upgrade' though... hm wondering why no longer. Hints appreciated!
 
Hi,

You can set the migration network in the datacenter.cfg.
Please check if you have set it there.
 
  • Like
Reactions: stefws
migration: [type=]<secure|insecure> [,network=<CIDR>]
For cluster wide migration settings.

network=<CIDR>
CIDR of the (sub) network that is used for migration.

type=<insecure | secure> (default = secure)
Migration traffic is encrypted using an SSH tunnel by default. On secure, completely private networks this can be disabled to increase performance.
 
parse error in '/etc/pve/datacenter.cfg' - 'migration': invalid format - format error
migration.type: value 'insecure ' does not have a value in the enumeration 'secure, insecure'

and also:

parse error in '/etc/pve/datacenter.cfg' - 'migration': invalid format - format error
migration.type: value 'secure ' does not have a value in the enumeration 'secure, insecure'

And it still picks ring1/public/slow NW for live migration
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!