Hi folks,

I've got two clustered F740s here with second level virtual interfaces configured for failover. The failover works fine on 5.3D20, but we've been unable as of yet to get it to work with anything 5.3.1 and beyond. We'd really like to move to 5.3.2D3 since it includes a fix to the ever-annoying NDMP file descriptor leak which makes it necessary to reboot our filers every week. I've tried moving forward to 5.3.2D3 several times for testing purposes, and it's yielded some very peculiar results, ranging from dropping both boxes off the network on takeover to what seems like some sort of persistence of nonexistent vif configs accross reboots. As I say, very peculiar. The netapp folks are equally puzzled. I'm really tired of hearing the phrases "that can't be" or "that makes no sense" (mostly from myself :P ). My question is, has anyone else gotten this configuration to work successfully in 5.3.2? Is anyone else using this configuration or something similar with trunked failover of interfaces in a cluster? Has anyone else been rebooting their boxes once a week for 3 months while they wait for a fix?

# Setup trunk1. # ifconfig e0 mediatype 100tx-fd ifconfig e3a mediatype 100tx-fd vif create multi trunk1 e0 e3a

# Setup trunk2. # ifconfig e3c mediatype 100tx-fd ifconfig e3d mediatype 100tx-fd vif create multi trunk2 e3c e3d

# Setup second level trunk. # vif create single secondlev1 trunk1 trunk2 vif favor trunk1

# Configure for failover. # ifconfig secondlev1 partner secondlev2

# Bring up secondlev1. # ifconfig secondlev1 `hostname`-11 netmask 255.255.255.0

The partner is of course the same except for the names of the trunks and the names in the setup and configuration of the second level trunk. As I say, works fine in 5.3D20, broken as hell in 5.3.1 and beyond.

Frustrated,

Mark Stoltzfus Susquehanna Partners