UNSOLVED
Unity Network Configuration
I am unclear how failover works on the network ports of the Unity system. We recently purchased multiple Unity systems and are in the initial configuration stage. If we have a Unity 300 with a 4 port 1GB module on each sp, and we combine the ports in pairs using LACP, and we are connecting to two separate switches for redundancy, and the switches do not support LACP across switches, how will the failover work, and what is the best practice in connecting the ports to the switches. If two of the ports go down that are combined together with LACP, will the system automatically switch the traffic over to the other SP (which is connected to a redundant switch using the same LACP configuration), and no outage will occur. I am familiar with how FSN works on the Celerra, but I couldn't find a good document that explains this type of scenario.
Your question:
we combine the ports in pairs using LACP, and we are connecting to two separate switches for redundancy, and the switches do not support LACP across switches
No, it will not work if LACP is not supported by the switch. This feature is "Network Switch" dependent and Unity (or any other OS) just act as a client.
Rainer_EMC
6 Operator
•
8645 Posts
1926
0
Posted January 19th, 2017 11:00
FSN functionality isnt available on the Unity System currently
so each of the 2-port LACP devices will need to get an Independent Interface which its own IP adress
On the Unity side there is no failover between them.
From the client side it depends on the protocol.
A modern CIFS Client (Windows Server 2012 / Windows 8 or newer) uses SMB3 with SMB multichannel.
There a client should get both IP's when connecting to the Unity CIFS server and can continue without interruption if one fails.
For NFS you could specify both IP's for the Mount - but that will only help on network failure when you remount.
The easiest way would be to use switches that support cross-switch link aggregation.