Been playing around a little more with the VDX6720, more as something to do than a real need to do anything with it. I managed to get the lingering configs (oh, and the "raslog", which had entries back to EARLY 2014) cleared out, I believe with no vcs or a subcommand thereof, I'd have to double check. (It's not like it's running right now. I DID mention it was bloody loud, yes?) That caused all those TenGigabitEthernet 2/0/X interfaces to become TenGigabitEthernet 0/X.

I also discovered that the version of Network OS is absurdly ancient - it's running a 4.11 variant, and they're currently at 7 or later - but given first Brocade's datacenter arm and now Extreme's position on licensing and support requirements for OS updates, I'm not going to even bother trying getting newer versions of NOS.

(Allow me a moment to sing the praises of Ruckus. They are the ONLY company in the enterprise networking space I'm aware of that posts all of their current and past OS updates for their switches available for free with, at most, a free login account. Docs are there too. And more, I've never gotten spam from them with the free account signup either. They were definitely the better part of Brocade and I'm glad they've been able to move relatively freely under Arris. Hopefully with the Arris acquisition, that doesn't change any time soon.)

One of the more interesting things I found out last night is the optics support. First, a generic DAC/twinax passive cable simply causes the switch to immediately admin-down the interface, and turning it back on simply repeats the process. I expected this to be honest, as I'd seen reports on the internet that not only does it require Brocade-branded cables, but they need to be ACTIVE cables as well. What surprised me though was that there was no issue at all with optics.

I've only got a couple of Mellanox SFP+ 10GB-SR optics to test with, but once the interface was admined up and the SFP+ was installed, it immediately recognized a connected optic and simply logged the change. No requirement for something like Cisco's service unsupported-transceiver or anything like that. I would expect it doesn't report signal levels, like the Ruckus ones don't, but I'm okay with that. I was able to hook it up over multimode OM3 to the Mellanox ConnectX-2 in my desktop PC and get 10G link with no problems, and once I figured out VLAN configs, it passed traffic just fine.

A note on Network OS: It's very much Cisco-like; if you're used to the Ruckus/Foundry FastIron line and its successors, things will throw you a bit. For instance, you add a VLAN to an interface in the Cisco manner (meaning, switchport access vlan XXX), but you configure SVIs in the FastIron manner (meaning, interface ve XXX). Confusingly, you create the VLAN with interface vlan XXX but that is NOT where you put the IP address - that still requires a ve interface. Also, the physical interfaces do NOT start in switchport mode; you need to configure them. Fortunately, just the bare command switchport works.

The other big surprise was when I hooked it up to my Kill-a-Watt. I'm currently only running a single PSU on it, and I've seen some scary numbers floated about (one said average usage was over 200W). Turns out, at least with only the single SFP+ module in it, it was idling at 55w pretty much dead on the nose. That's admittedly more than my ICX6450-24P and my pfSense box put together, but it's altogether reasonable compared to both what I expected and some of the more brutal Cisco 10G switches on the used market. Rebooting it to test (ow, ow, my ears!) showed that even screaming at boot it never exceeded 80w. I'm sure it CAN, and in fact WILL with a bunch of SFP+ modules installed and operating, but even so it's much more reasonable than I was afraid of.

All told it's not a terrible option, especially for what I paid for it, but I think I'm still going to sell it. My ultimate goal is to get an ICX6610-24, then run that in a mixed stack with my current ICX6450-24P. This lets the 6450 sit in the center of the house for user ports, with a single fiber breakout cable running from the 6610 in the rack to the 6450 for the stack. Since I'll be refinishing the basement at some point in the near future, that will allow me some flexibility with cabling runs without having to tear apart new construction just to change cable runs, and I've still got only the single logical switch to manage.