use with care !

for datamovers with 1G interfaces

.server_config server_2 -v "bcm cge2 stop"

this will stop traffic for cge0 and failover to standby device in FSN.

to re-enable it

.server_config server_2 -v "bcm cge2 start"

for 10G optical should be

.server_config server_2 -v "bcmXG fxg-1-1 stop"

.server_config server_2 -v "bcmXG fxg-1-1 start"

Thank you Dynamox.... What if the port is 10G fibre channel, can't i use the same command..

Our VNX2 uses the bxgv2 driver, so I had to do the following:

.server_config server_2 -v "bxgv2 fxg-1-1 down"

.server_config server_2 -v "bxgv2 fxg-1-1 up"

One thing I noticed was that when I brought the interface down, ALL traffic to the fsn would fail until I brought it back up.  When I brought it back up, however, the traffic had failed over to the other interface.  This was verified both in the switches by looking at where the MAC was, as well as when repeating the process above we did not lose link subsequent times.  When performing the same process later on the other 10G NIC in the fsn the identical pattern happened (all traffic froze until the NIC came up, at which point it immediately failed to the other switch).  During all of this the switches showed link UP, even though the NIC stats on the VNX showed link DOWN.

that's not supposed to happen, defeats the purpose of having FSN. Did you try physical disconnecting one of the members and see what happens ?   I don't have any VNX2 File but i see that in the command you used down/up instead of stop/start, not sure if it makes difference.

Hi gsilver_akuna,

Could you please output of following commands?

1. nas_version

2. server_version ALL

3. If possible post server_logs (last 10-15 lines) when you run following commands

.server_config server_2 -v "bxgv2 fxg-1-1 down"

.server_config server_2 -v "bxgv2 fxg-1-1 up"

Thanks,