Force10 VLT between two MXL's doesn't seem to be passing traffic

These last two weekends we've been doing maintenance was to get our new Dell blade chassis onto the network, and we're having a ton of problems getting this setup - thinking I might be in a bit over my head networking wise. Basically the setup is in the back of the Dell M1000e chassis we have two Force10 MXL switches. Then we have two Dell N4032 core switches that we're connecting them to. So we're trying to setup a MLAG between the N4032 switches, a VLT to connect to the two MXL switches together and then another MLAG/VLT between the MXL's and N4032's using two 40GbE links per MLAG.

We're PRETTY sure the issue we're having is that the VLT between the two MXL's isn't passing traffic. Something we plug into MXL1 isn't able to communicate with a device we plug into MXL2 - and this traffic should be flowing across the VLT link - yet it's not. If I do a show vlt brief, I get:

VLT Domain Brief ------------------ Domain ID: 1 Role: Secondary Role Priority: 8000 ICL Link Status: Up HeartBeat Status: Up VLT Peer Status: Up Version: 6(8) Local System MAC address: e4:f0:04:76:6f:7c Remote System MAC address: e4:f0:04:76:6e:90 Remote system version: 6(8) Delay-Restore timer: 90 seconds Delay-Restore Abort Threshold: 60 seconds Peer-Routing : Disabled Peer-Routing-Timeout timer: 0 seconds Multicast peer-routing timeout: 150 seconds MXL-Switch2# 

Which LOOKS like it's up at least. But I don't know WTF we're missing. This is the config we have for the VLT:

MXL1: protocol lldp advertise management-tlv system-description system-name ! protocol spanning-tree rstp no disable bridge-priority 0 ! protocol spanning-tree rstp no disable bridge-priority 0 ! vlt domain 1 peer-link port-channel 127 back-up destination 10.10.100.209 primary-priority 1 ! interface fortyGigE 0/33 no ip address no shutdown ! interface fortyGigE 0/37 no ip address no shutdown ! interface Port-channel 127 description VLT no ip address channel-member fortyGigE 0/33,37 no shutdown MXL2: protocol lldp advertise management-tlv system-description system-name ! protocol spanning-tree rstp no disable bridge-priority 4096 ! vlt domain 1 peer-link port-channel 127 back-up destination 10.10.100.208 primary-priority 8000 ! interface fortyGigE 0/33 no ip address no shutdown ! interface fortyGigE 0/37 no ip address no shutdown ! interface Port-channel 127 description VLT no ip address channel-member fortyGigE 0/33,37 no shutdown 

Is anyone familiar with Force10 VLT and can determine if I have something messed up here or not? I'm kind of at whit's end here. We're going to call Dell and have them take a look at it as well. Doing these maintenance windows is a pain because one wrong command and we drop all our iSCSI traffic, so it's a pain in the ass because we have to shut down over 300 VMs every time, as well as do a site failover on our Exchange DAG so email stays up. :irk: I've pulled two all nighters in the past week so at this point I'm probably so sleep deprived I'm missing something stupid.

Might not even be the VLT at all, maybe MLAG issue, but I don't think so as the MLAG traffic going to the core switches shouldn't affect the problem we're having with traffic flowing in between the two MXL's.