Assigning iSCSI disk trafic to a virtual bridge

pmard

New Member
May 23, 2011
4
0
1
Hello Proxmoxers

I have successfully installed proxmox on Supermicro/Scale hardware.

- The server has six (6) NIC's available. Two internal and four on an Intel Quad card.
- I have created two bonds, eth4,eth5 as bond0, eth0,eth1,eth2,eth3 as bond1.
- vmbr0 uses bond0, vmbr1 uses bond1
- I have created iSCSI targets and associated a 64GB LUN residing on the Scale Cluster
- I have created a new VM, residing on the Scale LUN after creating an LVM volume and installed a W2k8r2 on it. Everything works fine.

However, I can not figure out how to specify which one of the two virtual bridges to use for disk traffic, vmbr0 is used as default. I would like to separate regular network traffic from iSCSI disk traffic assigning vmbr1/bond1 for this.

Any clues greatly appreciated.

Cheers,
///peo


How do I point the iSCSI disk traffic across a specific vmbr (directing the disk traffic across the quad card
 
I have done similar except I used the 4 onboard nics and just created one bond w/ trunk interface. Then I created a separate "vlan" for the iscsi traffic to go across. Below you will see my /etc/network/interfaces file:

Code:
auto lo
iface lo inet loopback

# interface GigabitEthernet5/45 on the core switch
auto eth0
iface eth0 inet manual

# interface GigabitEthernet5/46 on the core switch
auto eth1
iface eth1 inet manual

# interface GigabitEthernet5/47 on the core switch
auto eth2
iface eth2 inet manual

# interface GigabitEthernet5/48 on the core switch
auto eth3
iface eth3 inet manual

auto bond0
iface bond0 inet manual
slaves eth0 eth1 eth2 eth3
bond_miimon 100
bond_mode 4

auto bond0.1
iface bond0.1 inet manual
vlan-raw-device bond0

auto bond0.2
iface bond0.2 inet manual
vlan-raw-device bond0

auto bond0.3
iface bond0.3 inet manual
vlan-raw-device bond0

auto bond0.4
iface bond0.4 inet manual
vlan-raw-device bond0

auto bond0.5
iface bond0.5 inet manual
vlan-raw-device bond0

auto bond0.6
iface bond0.6 inet manual
vlan-raw-device bond0

auto bond0.7
iface bond0.7 inet manual
vlan-raw-device bond0

auto bond0.8
iface bond0.8 inet manual
vlan-raw-device bond0

auto bond0.9
iface bond0.9 inet manual
vlan-raw-device bond0

auto bond0.10
iface bond0.10 inet manual
vlan-raw-device bond0

auto bond0.11
iface bond0.11 inet manual
vlan-raw-device bond0

auto bond0.12
iface bond0.12 inet manual
vlan-raw-device bond0

auto bond0.13
iface bond0.13 inet manual
vlan-raw-device bond0

auto bond0.14
iface bond0.14 inet manual
vlan-raw-device bond0

auto bond0.15
iface bond0.15 inet manual
vlan-raw-device bond0

auto bond0.20
iface bond0.20 inet manual
vlan-raw-device bond0

auto vmbr0
iface vmbr0 inet static
    address 10.8.2.40
    netmask 255.255.255.0
    gateway 10.8.2.1
    bridge_ports bond0.2
    bridge_stp off
    bridge_fd 0

auto vmbr1
iface vmbr1 inet manual
bridge_ports bond0.1
bridge_stp off
bridge_fd 0

#auto vmbr2
#iface vmbr2 inet manual
#bridge_ports bond0.2
#bridge_stp off
#bridge_fd 0

auto vmbr3
iface vmbr3 inet manual
bridge_ports bond0.3
bridge_stp off
bridge_fd 0

auto vmbr4
iface vmbr4 inet manual
bridge_ports bond0.4
bridge_stp off
bridge_fd 0

auto vmbr5
iface vmbr5 inet manual
bridge_ports bond0.5
bridge_stp off
bridge_fd 0

auto vmbr6
iface vmbr6 inet manual
bridge_ports bond0.6
bridge_stp off
bridge_fd 0

auto vmbr7
iface vmbr7 inet manual
bridge_ports bond0.7
bridge_stp off
bridge_fd 0

auto vmbr8
iface vmbr8 inet manual
bridge_ports bond0.8
bridge_stp off
bridge_fd 0

auto vmbr9
iface vmbr9 inet manual
bridge_ports bond0.9
bridge_stp off
bridge_fd 0

auto vmbr10
iface vmbr10 inet manual
bridge_ports bond0.10
bridge_stp off
bridge_fd 0

auto vmbr11
iface vmbr11 inet manual
bridge_ports bond0.11
bridge_stp off
bridge_fd 0

auto vmbr12
iface vmbr12 inet manual
bridge_ports bond0.12
bridge_stp off
bridge_fd 0

auto vmbr13
iface vmbr13 inet manual
bridge_ports bond0.13
bridge_stp off
bridge_fd 0

auto vmbr14
iface vmbr14 inet manual
bridge_ports bond0.14
bridge_stp off
bridge_fd 0

auto vmbr15
iface vmbr15 inet manual
bridge_ports bond0.15
bridge_stp off
bridge_fd 0

auto vmbr20
iface vmbr20 inet static
address 192.168.130.50
netmask 255.255.0.0
bridge_ports bond0.20
bridge_stp off
bridge_fd 0

auto vmbr21
iface vmbr21 inet static
address 192.168.131.50
netmask 255.255.0.0
bridge_ports bond0.20
bridge_stp off
bridge_fd 0


vmbr20 and vmbr21 are my san vlans. Maybe this helps you some.
 
Hello Kameleon,

Thank you for your prompt and helpful reply.
If I understand the file you submitted correct something like this is what I could use:
---
# Content of /etc/network/interfaces file
auto lo iface lo inet loopback

# Physical interfaces installed in the cradle
# interface GbE Patch Cable tp019
auto eth0 iface eth0 inet manual
# interface GbE Patch Cable tp020
auto eth1 iface eth1 inet manual
# interface GbE Patch Cable tp021
auto eth2 iface eth2 inet manual
# interface GbE Cable marked tp022
auto eth3 iface eth3 inet manual
# interface GbE Cable marked tp023
auto eth4 iface eth4 inet manual
# interface GbE Cable marked tp023
auto eth5 iface eth5 inet manual

# Bonding/trunking goes here, bond0 for regular networking bond1 for iSCSI:
auto bond0
iface bond0 inet manual
slaves eth4 eth5
bond_miimon 100
bond_mode 4

auto bond1
iface bond1 inet manual
slaves eth0 eth1 eth2 eth3
bond_miimon 100
bond_mode 4

# Vlan goes here
# First regular networking
auto bond0.1 iface bond0.1
inet manual vlan-raw-device bond0
# Then iSCSI disk traffic
auto bond1.1 iface bond1.1
inet manual vlan-raw-device bond1

# Next come the virtual bridges

# vmbr0 for regular traffic across eth4 and eth5,

# vmbr1 for iSCSI across eth0 through eth3.

auto vmbr0
iface vmbr0 inet static
address 192.168.0.141
netmask 255.255.255.0
gateway 192.168.0.1
bridge_ports bond0.1
bridge_stp off
bridge_fd 0

auto vmbr1
iface vmbr1 inet static
address 192.168.1.141
netmask 255.255.0.0
bridge_ports bond1.1
bridge_stp off
bridge_fd 0
#EOF

I notice you use a netmask of 255.255.0.0 in your file for vmbr20, is that correct?

Again thank you for your help! I will deploy this file tomorrow and see what happens.

Cheers,
///peo