Physical connections and configuration of LACP on Unity 600 for file services

I dont follow what sense that would make

each SP has its own networking

If you configure LACP for ports on SPA the system will automatically configure LACP for the same ports on SPB

Otherwise after a SP failover the interfaces using the lacp wouldnt work

Of course the ports on the switches need to be configured accordingly

I would suggest to actually configure it on a Unity system and it should become clear that when creating an LACP you dont even get to select which SP

Here is the answer - the command uemcli /net/la show displays aggregated ports on SPA and SPB:

Both members of SPA link aggregation have to be connected to their own LACP port group on the switch side. Both members of SPB link aggregation have to be connected to their own separate LACP port group on the switch side.

Can you share the LACP Configuration you have done on the switch end. 

Also if the switch ports are on 100M and unity ports are 10G, can we create LACP for this config?

I have two links from different ISPs for the replication. How can i load balance between those two links? Can i add two uplinks to a LAG to transfer replication data to the destination switch?

For FILE STORAGE, the unity uses only one SP for connectivity, by other hand, iscsi traffic uses both SPs for I/O in an active/active fashion for I/O load balance, since multi-path/failover is done at host level, not in the storage side, iscsi interfaces does not support LACP.

In case of FILE STORAGE (NAS Server) you can only configure ports for the same SP since the I/O works in active/passive between SPs in this case, so, when creating a LACP for FILE STORAGE, you should use only ports for the same SP, and connect each port on a different switch (if stacked switches are in place), or connect both ports of the same SP in the same switch, in case you are using standalone switches (no stack) for FILE STORAGE. (For standalone switches, a FSN setup is mandatory in order to survive from a switch port failure, since the SPs does not failover if a port down occurs).

The Unity failover the configuration for FILE STORAGE in the standby SP in case of a SP failure, that's why you need to MIRROR the cabling between SPs to correct configure a failover scenario for FILE STORAGE.

 

 

Hello Dinesh-sengar,

FSN does provide redundancy.  Here are 2 links to some white papers. The first link is to DELL EMC UNITY HIGH AVAILABILITY, and the second link is to Dell EMC Unity Family Configuring High Availability.

https://dell.to/3onFVo0

https://dell.to/3tT8WsP

Hi All,

Does FSN also provides redundancy in case Port on a I/O module of Unity fails. It’s kind of confusing as mostly it’s written it only provides redundancy when network switch fails.