SAN setup

K

kameleon

Guest
Ok, I have 2 servers with only 2 NIC's in them and 1 other one with 4 that I am testing proxmox 2.0 RC1 on. I want to use half of the ports on each strictly for SAN access. So for the two machines that means 1 port and the other machine means 2 ports. On each I want to be able to have full multipath setup. However I am just a little confused how I will accomplish this. Here is what I am wanting:

eth1 in each of the servers to have 4 virtual interfaces (eth1.1, eth1.2, eth1.3, eth1.4 I suppose)
Each of the virtual interfaces to have static IP's and a set MTU of 9000
Only proxmox will see these connections as once I figure out how, I plan to set the VM's disks on the SAN and test HA functions

My current /etc/network/interfaces is as follows:

Code: 
auto lo
iface lo inet loopback

# interface GigabitEthernet1/0/4 on the IS Rack switch
auto eth0
iface eth0 inet manual

# interface GigabitEthernet1/0/6 on the core switch
#auto eth1
#iface eth1 inet manual

#auto vlan1
#iface vlan1 inet manual
#vlan-raw-device eth0

auto vlan2
iface vlan2 inet manual
vlan-raw-device eth0

auto vlan3
iface vlan3 inet manual
vlan-raw-device eth0

auto vlan4
iface vlan4 inet manual
vlan-raw-device eth0

auto vlan5
iface vlan5 inet manual
vlan-raw-device eth0

auto vlan6
iface vlan6 inet manual
vlan-raw-device eth0

auto vlan7
iface vlan7 inet manual
vlan-raw-device eth0

auto vlan8
iface vlan8 inet manual
vlan-raw-device eth0

auto vlan9
iface vlan9 inet manual
vlan-raw-device eth0

auto vlan10
iface vlan10 inet manual
vlan-raw-device eth0

auto vlan11
iface vlan11 inet manual
vlan-raw-device eth0

auto vlan12
iface vlan12 inet manual
vlan-raw-device eth0

auto vlan13
iface vlan13 inet manual
vlan-raw-device eth0

auto vlan14
iface vlan14 inet manual
vlan-raw-device eth0

auto vlan15
iface vlan15 inet manual
vlan-raw-device eth0

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

auto vmbr0
iface vmbr0 inet static
        address 10.8.1.151
        netmask 255.255.255.0
        gateway 10.8.1.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

#auto vmbr1
#iface vmbr1 inet manual
#bridge_ports vlan1
#bridge_stp off
#bridge_fd 0

auto vmbr2
iface vmbr2 inet manual
bridge_ports vlan2
bridge_stp off
bridge_fd 0

auto vmbr3
iface vmbr3 inet manual
bridge_ports vlan3
bridge_stp off
bridge_fd 0

auto vmbr4
iface vmbr4 inet manual
bridge_ports vlan4
bridge_stp off
bridge_fd 0

auto vmbr5
iface vmbr5 inet manual
bridge_ports vlan5
bridge_stp off
bridge_fd 0

auto vmbr6
iface vmbr6 inet manual
bridge_ports vlan6
bridge_stp off
bridge_fd 0

auto vmbr7
iface vmbr7 inet manual
bridge_ports vlan7
bridge_stp off
bridge_fd 0

auto vmbr8
iface vmbr8 inet manual
bridge_ports vlan8
bridge_stp off
bridge_fd 0

auto vmbr9
iface vmbr9 inet manual
bridge_ports vlan9
bridge_stp off
bridge_fd 0

auto vmbr10
iface vmbr10 inet manual
bridge_ports vlan10
bridge_stp off
bridge_fd 0

auto vmbr11
iface vmbr11 inet manual
bridge_ports vlan11
bridge_stp off
bridge_fd 0

auto vmbr12
iface vmbr12 inet manual
bridge_ports vlan12
bridge_stp off
bridge_fd 0

auto vmbr13
iface vmbr13 inet manual
bridge_ports vlan13
bridge_stp off
bridge_fd 0

auto vmbr14
iface vmbr14 inet manual
bridge_ports vlan14
bridge_stp off
bridge_fd 0

auto vmbr15
iface vmbr15 inet manual
bridge_ports vlan15
bridge_stp off
bridge_fd 0

What confuses me I guess is I already have vlans in there riding on eth0. I just have never attempted this and all my searching gets me not much help. Has anyone else tried this type of setup?
 
Should it be as easy as adding this to the top:

Code: 
auto eth1
allow-hotplug eth1
iface eth1 inet static
    address 192.168.130.53
    netmask 255.255.255.0

auto eth1:1
allow-hotplug eth1:1
iface eth1:1 inet static
    address 192.168.131.53
    netmask 255.255.255.0
    
auto eth1:2
allow-hotplug eth1:2
iface eth1:2 inet static
    address 192.168.132.53
    netmask 255.255.255.0
    
auto eth1:3
allow-hotplug eth1:3
iface eth1:3 inet static
    address 192.168.133.53
    netmask 255.255.255.0

I only ask because I am waiting on my crimpers to get here so I can make cables to run to the new switch from the SAN so I cannot test right this moment. Thanks!
 
kameleon said:
Should it be as easy as adding this to the top:

Code: 
auto eth1
allow-hotplug eth1
iface eth1 inet static
    address 192.168.130.53
    netmask 255.255.255.0

auto eth1:1
allow-hotplug eth1:1
iface eth1:1 inet static
    address 192.168.131.53
    netmask 255.255.255.0
    
auto eth1:2
allow-hotplug eth1:2
iface eth1:2 inet static
    address 192.168.132.53
    netmask 255.255.255.0
    
auto eth1:3
allow-hotplug eth1:3
iface eth1:3 inet static
    address 192.168.133.53
    netmask 255.255.255.0

I only ask because I am waiting on my crimpers to get here so I can make cables to run to the new switch from the SAN so I cannot test right this moment. Thanks!
Click to expand...
Hi,
that can't work!
You need an real bond. But why you failover with 1 nic? And if i understand right only for san-nic and not the other network?
Why you don't use both NICs as bond and use vlan-tagging over the bond (simply create an SAN-bridge on this bond). The only thing is the MTU - i guess you can run only one MTU for all traffic.

But i'm no bonding expert.

Udo
 
I wasn't trying to "fail over" per se but rather give the interface 4 different ip's so it could communicate on all 4 interfaces of the SAN. Now that you mention it though it does make sense to just do both NIC's in the machine as a bond and pass both VM and SAN traffic over that bond since I now have a switch that can do jumbo frames. Thanks for that "stick upside the head".... I needed it. ;)
 
So now I just need to figure out how to get the 4 interfaces so I can connect to the multipath of the SAN. Here is what I have for the interfaces file so far:

Code: 
auto lo
iface lo inet loopback

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

# interface 
auto eth1
iface eth1 inet manual

# interface 
auto eth2
iface eth2 inet manual

# interface 
auto eth3
iface eth3 inet manual

auto bond0
iface bond0 inet manual
slaves eth0 eth1 eth2 eth3
bond_miimon 100
bond_mode 6
mtu 9000

#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.20
iface bond0.20 inet manual
vlan-raw-device bond0

auto vmbr0
iface vmbr0 inet static
        address 10.8.1.151
        netmask 255.255.255.0
        gateway 10.8.1.1
        bridge_ports bond0
        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 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

However I don't see how I can get 4 different IP's on there. I must be missing something.
 
Hi,
with using an "address xx.xx.xx.xx" at the bridge (vmbr1...)??
BTW. you use vmbr0 without vlan-tagging - some people have issues with mixing tagged and untagged traffic.
Perhaps you should also use an vlan for this?!

Udo
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back