Nic Teaming

Hello,
I have installed Open-e on hp server that has two NICs, I plugged each NIC to different switch on the same vLAN. How can I create NIC Teaming? To avoid nic failure/switch failure.

Thanks,

Quote:

---

Originally Posted by habibalby

Hello,
I have installed Open-e on hp server that has two NICs, I plugged each NIC to different switch on the same vLAN. How can I create NIC Teaming? To avoid nic failure/switch failure.

Thanks,

---

http://www.open-e.com/download/libra...t_file/get/114

look at page 31

Hello,
Thanks for your reply, but my subnet is only one and I don't have another subnet. Can I set the bounding/Teaming on the same subnet?

CONFIGURATION SEVERAL NETWORK ADAPTERS IN THE SAME SUBNETWORK "Where is this document"?

Thanks,

Quote:

---

Originally Posted by habibalby

Hello,
Thanks for your reply, but my subnet is only one and I don't have another subnet. Can I set the bounding/Teaming on the same subnet?

CONFIGURATION SEVERAL NETWORK ADAPTERS IN THE SAME SUBNETWORK "Where is this document"?

Thanks,

---

ftp://software:enterforupdate@ftp.op...ultiple_IP.pdf

hello,

link is invalid.

Thanks,

Quote:

---

Originally Posted by habibalby

hello,

link is invalid.

Thanks,

---

http://www.fishbowlnetwork.com/multiple_IP.pdf

However, this doesn't fulfill my requirement.

What is stated in this document is to connect two hosts in the same sub-network. My requirement is to have nic teaming in each server and I can present iSCSI target as a Virtual IP. So, in my iSCSI initiator, I have to put the VIP only. Is this can be achieved in Open-e?

Thanx,

Hello,

I have tested the below in my VMWare WorkStation and I have seen it it's working, but is it the way how it should be configured?

Here's its;

I have added two interfaces, eth0 and eth1,

eth0 = 192.168.112.220
eth1 = 192.168.112.221
gw = 192.168.112.2

In the network > Setup > Interfaces, I have selected both of the Interfaces and selected Bounding Mode = balance-rr.

I have given the bound0 IP 192.168.112.222 gw IP = 192.168.112.2l

Ping stop working on 220 and 221 and only 222 is the one which is ping-able.

Ctrl+Alt+N and I have selected Routing, I have added routing to be 0.0.0.0 mask 255.255.255.0 goes via 192.168.112.2 for interface bound0.

Testing,

in my ESX test, I have added the 192.168.112.222 as the iSCSI target and it detected the iSCSI LUN.

I disconnected eth0 and ping to 192.168.112.222 ping is alive and scanning the iSCSI adapter in ESX, LUN still exists.

I disconnected eth1 and ping to 192.168.112.222 ping is alive and scanning the iSCSI adapter in ESX, LUN still exists.


Is this the way how it should work?

Thanks,

Ping node should not be pointing to a DSS system - we recommend a UPS or firewall or the VMware server as you have it now.

I think this video might help here.

http://www.open-e.com/library/webcasts-and-videos/
2010.02 Open-E DSS V6 AutoFailover with VMware 4.0

I have DSS with two interfaces, currently ESX pointed to the eth0 only. I want to simulate the nic teaming/redundancy if one nic goes down, the other should takes over and iSCSI initiator won't be down to lose the connection which will lead to entire VMs hosted on that DSS will be down.

If I configure the eth0 and eth1 in the same subnet and bounding mode as balance-rr with the same subnet IP as eth0 and eth1, will this work?

In the VMware workstation, I have seen it working and if disconnect one nic, the iSCSI target won't go down as the link will be available via the other interface.

Sounds like you want failover functionality:

http://www.open-e.com/library/webcasts-and-videos/
2010.10 How to update DSS V6 with Auto Failover - EN

Hello,
No, I don't want failover between primary and secondary DSS. I need the nic to be teamed and I will be having nic redundancy on physical switch level. Then, inside the ESX, I will configure Multipathing.

This is my needs.

Thanks

DSS Nic Teaming Configuration is attached.

http://www.filesend.net/download.php...3d41e7c9fdabf8