Veritas 5230 Appliance, Jumbo Frames, and 10Gb LACP/bond

[elanmbx]

Does anyone have this configuration running in their environment?  I've been told that the previous NBU admin tried to get their 5230s set up with LACP on the 10Gb interfaces and that it did not work (jumbo frames configured).  Details are vague, but the rumor I received 3rd had was that "Veritas believed it was a driver issue with the intel NIC"

Just wondering if anyone has ever heard of or experienced anything like this.  I'm trying to convince them to have another go at it (we are getting a new 5230) so that we can avoid having multiple individual 10Gb interfaces with multiple VLANs tagged to each interface.  I want our standard to be all 4 10Gb bonded wtih ALL VLANs tagged on the single bond.

[RiaanBadenhorst]

I've used the LACP a lot but I've not had to/wanted to do anything with Jumbo frames. Just turned it on and that was it.

[elanmbx]

Update on this issue: still haven't been able to sort out if this is supported.  I will be opening an official case to get it validated.

Also - there is no way to configure a Tagged-VLAN interface for jumbo frames from either the CLISH or the GUI from what I can tell.  I have a case open for this issue already.  I have jumbo frames configured on the "physical" interface devices (eth<n>), but the VLAN-tagged interfaces (vlan<nnn>) are NOT configured with an MTU of 9000.

EXAMPLE OF INTERFACE CONFIG DIFFERENCES

# ifconfig eth7
eth7      Link encap:Ethernet  HWaddr 90:E2:BA:84:43:3D
          inet6 addr: fe80::92e2:baff:fe84:433d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
          RX packets:10953899 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11837290 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:203271190567 (193854.5 Mb)  TX bytes:3569607307 (3404.2 Mb)

# ifconfig vlan801
vlan801   Link encap:Ethernet  HWaddr 90:E2:BA:84:43:3D
          inet addr:192.168.130.175  Bcast:192.168.131.255  Mask:255.255.254.0
          inet6 addr: fe80::92e2:baff:fe84:433d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10696317 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11596011 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:197668466093 (188511.3 Mb)  TX bytes:3553589533 (3388.9 Mb)

vlan801 (eth7 ): 10Gb/s   FC    PLUGGED|UP           192.168.130.175  - No IPv6 -

[sdo]

Just curious as to what levels of backup data ingest speeds you think you need to attain and sustain ?   And to which types of target storage, MSDP or Advanced Disk or FC tape or a mixture ?

[elanmbx]

To be honest, I'm *mainly* interested in the simplicity.  I want a single 40Gb bond with ALL my various VLANs tagged to that single bond.  As it is, the folks who originally architected the appliances ended up with 4 individual 10Gb links with various VLANs tagged individually to each one.  No redundancy, complex config - all the things that violate my KISS mantra.

And my target storage is all over the map, currently.  MSDP, Adv, tape, more tape, etc.