Brocade ICX Series (cheap & powerful 10gbE/40gbE switching)

[dennisp]

Front to back including the handles is 17-3/8, but I'd go 17-1/2 just to be safe, the SFP ports protrude slightly from the front for example. You're also going to need right angle power cables to stay within those limits. Not sure what options you would have for the QSFP though.

Based on the ears I have, that config will only work if you put 2 screws through the large square vent holes and maybe rig up something with washers to hold it in place. Even then you are only hanging it on 3 screws per side. You could mount it upside down and get two regular screw holes to line up in a similar mid-unit position, but then you're hanging it on two screws per side, and these things are not light. For comparison, the standard position hold using 6 screws per side.

 

[klui]

2. I noticed in one of the pictures from an ebay seller that you can mount the rack ears a bit further to the back than normal, like this:

View attachment 18312

Does anybody have the measurement of the distance represented by the red line above? How many inches is that?

4-5/8" which requires only 3 screws in the "B" mounting holes. This is a valid configuration for telecom racks since the fulcrum is moved more towards the load but if your rack has doors, they probably won't close.



There are other intermediary distances between 0" and 4-5/8" but they only accommodate 1 or 2 screws. Not a problem if you have something underneath like a server with proper rails.

 

[tryingtorunservers]

Hi, I recently got a second-hand ICX7150-C12P, and it seems to behave a bit differently:

1. It came with the switch firmware on primary and router firmware on secondary
2. Out of the box, it failed to boot from primary then falls back to secondary
3. After flashing both to latest firmware, primary seems to work again
4. It comes with a predefined user `super`, but when I attempted to factory reset the switch, it'd still boot into the user/password prompt

Technically, I can boot with `no password` and change the password, but the fact that the user isn't wiped from factory reset makes me wonder if the flash is defective and that there may be other lingering settings. I'm not really sure how to diagnose this problem, and would like advice into even where to start poking.

Thank you,

 

[dennisp]

Interesting, my ears are exactly the same as @klui except it only says R/L, and there are no holes in the B locations. These would only work in a flush mount config, not a telecom rack. For what it's worth, the R side is inscribed with this:

42-1001007- 01
FOXCONN 05/29/2012

And the L side is:

42-1001008- 02
FOXCONN 05/29/2012

 

[klui]

Interesting, my ears are exactly the same as @klui except it only says R/L, and there are no holes in the B locations. These would only work in a flush mount config, not a telecom rack.

Is your 6610 24 port?

 

[dennisp]

Is your 6610 24 port?

Both are 48 w/ PoE. They are Rev. A power, so I guess 2012 could be the manufacture date? Maybe they refined the design of the ears in later models.

 

[klui]

My 6610 48PoE came with a Rev B PSU. Ebay has 24/48 PoE/non-PoE whose ears don't have B holes. Strange.

 

[fohdeesha]

yall mf usin brocade sheeeeeeeet

 

[fohdeesha]

Hello everyone, I have been silent for a long time, since only now I have all the components necessary to start dipping my toes in this field.
I had bought myself a 2nd hand FCX648S-HPOE off eBay (I only needed 24 POE ports, however this was cheaper, including shipping to my country) last year, though I only managed to get myself an RS232 add-on board (not PCIe, just direct to the serial connector on the motherboard) from a dead Lenovo slim PC a month or two ago, and an RS232 cable a few days ago.

I use Solus on my desktop (dying AsRock H97M, in a few weeks I should have the money to order a 2nd hand ASUS H97 Pro Gamer off AliExpress), and it does use /dev/ttySx, however I am unable to get any terminal output off my switch with PicoCom.

Being the rookie I am, I have tried looking through the manuals and documentation (both of the switch, and PicoCom), however I could not find anything that could help me get dropped off to a terminal, and I have no idea whether I am doing something wrong , or if there is something that is simply not working on the hardware.

One of my main reasons for getting the switch was to learn, since I have also started taking online CCNA and CCNP courses.
And while the PSU fans certainly sound like a vaccum cleaner, it isn't nearly what I had come to expect, and I could certainly sleep in the same room without any issues.

Did you get this figured out? It's probably the serial cable, I'm guessing it's a bull modem/rollover cable - the fcx has a male port, so you would have to be using a female to female serial cable, and most of those are rollover. You need a straight through serial cable, either a regular one with a little female to female adapter on the end, or a female to female straight through cable

Also you are an absolute madman for being able to sleep in the same room as a PoE fcx

 

[fohdeesha]

Hi, I recently got a second-hand ICX7150-C12P, and it seems to behave a bit differently:

1. It came with the switch firmware on primary and router firmware on secondary
2. Out of the box, it failed to boot from primary then falls back to secondary
3. After flashing both to latest firmware, primary seems to work again
4. It comes with a predefined user `super`, but when I attempted to factory reset the switch, it'd still boot into the user/password prompt

Technically, I can boot with `no password` and change the password, but the fact that the user isn't wiped from factory reset makes me wonder if the flash is defective and that there may be other lingering settings. I'm not really sure how to diagnose this problem, and would like advice into even where to start poking.

Thank you,

You just have much newer firmware flashed then, I believe in the 8092 and up train is when they added a mandatory default password for security reasons: https://docs.commscope.com/bundle/f...UID-32D3BB01-E600-4FBE-B555-7570B5024D34.html

Also you'll want to run "sz disable" too as these later trains also come with their cloud phone home central config crap enabled by default. The sz disable command turns it all off

 

[pubsub]

Can anyone give me some guidance on PVLANs and routing? I'm trying to set up an isolated PVLAN for a guest network. The idea is that none of the hosts on the network can interact with each other -- only with the internet firewall running OPNsense. My OPNsense box has 4 x 1GbE Intel NICs that I have connected to my 6610 switch stack as an LACP group. The firewall interacts with various VLANs using frame tagging only through this LACP group.

So far I've set up VLAN 40 named "GUEST-VLAN" and VLAN 41 named "GUEST-PVLAN". It's my understanding that ports in VLAN 40 will be "promiscuous" ports and is where the firewall link should reside.

The manual states that "LAG ports are not allowed in any PVLAN" so I won't be able to simply add my firewall as a promiscuous VLAN via its LACP ports. However, (and I couldn't find where the manual states this but the CLI won't let me do it) I can't add a virtual interface to the group either; the CLI says "Private VLANs cannot be configured on vlans with ve configured".

Is there any way to connect my firewall to my guest PVLAN without adding any additional cabling? Or will that be a requirement?

 

[seatrope]

Question for all the networking experts like @kapone : any reason why i couldn’t use pfsense as the dedicated firewall with pihole on a rpi4 doing DNS and DHCP for several VLANs, using the 6610 to do all the layer 3 routing? My understanding is that pihole 5 does serve DHCP to non-connected subnets.

does anyone have direct experience with this particular setup? I’m a VLAN noob here and a bit hesitant to take the leap,

thanks all!

 

[kapone]

Question for all the networking experts like @kapone : any reason why i couldn’t use pfsense as the dedicated firewall with pihole on a rpi4 doing DNS and DHCP for several VLANs, using the 6610 to do all the layer 3 routing? My understanding is that pihole 5 does serve DHCP to non-connected subnets.

does anyone have direct experience with this particular setup? I’m a VLAN noob here and a bit hesitant to take the leap,

thanks all!

Who? Me? I aint no expert.

But yeah, there is nothing stopping you from doing what you want. I run almost the same configuration, except I use a Windows Server (I have an AD domain) for DHCP/DNS. As long as your PiHole can do that, (i.e. DHCP/DNS for VLANs) you're good to go.

 

[kapone]

Question for the 6610 owners out there:

The material here says the 6610 is 16" deep, no matter the number of ports.

1. Does that depth figure include the fan and power supply handles in the back, or is it just for the chassis itself (not including the handles)?

View attachment 18311

2. I noticed in one of the pictures from an ebay seller that you can mount the rack ears a bit further to the back than normal, like this:

View attachment 18312

Does anybody have the measurement of the distance represented by the red line above? How many inches is that?

I'm trying to see if I can fit a 6610 in the rack I have on order. I'm considering if it's worth going with a bigger one just for this.

Thanks!

It's 16" deep, without the handles.

Your second pic, is how you'd mount it on a two-post rack, vs a four-post rack, where the front of the switch is flush with the edges of the rack (front or back).

Couldn't tell you about the red line, never used it in a two post rack. And I aint de-racking mine to measure it...

 

[RealJamesDean]

Is there anything like a 6450 basic admin guide for dummies out there? I'm not trying to do much beyond L2 stuff at the moment. Especially looking for guidance in setting up SFP and SFP+ modules and bonding ports with LACP.

 

[Bladerunner]

Not a good experience with going to 08.0.92b on an ICX 7150-C12P from 08.0.70c.

I couldn't go directly from 70 to 92 because 70 is a non-UFI while 92 is. I had to go to 08.0.80 non-UFI first. I decided to have primary on 80f and secondary 92b. The upgrade to 80f was straightforward. copy from tftp to flash the 80f's bootrom, image to primary, then reload. The nice thing was after bootup the PoE FW is automatically updated. And the system prints progress to the console. The ICX6610 running 08.0.30u does not print progress but prevents you from rebooting until the PoE FW is done after a manual upgrade. show logging will display progress.

The problem was upgrading the secondary to 92b. Because it's a unified image, the bootrom is embedded in the ufi.bin file. When I boot back to 80f, I'm met with a boot-monitor version mismatch at startup. Back in 92b, it shows there are primary and secondary boot code partitions. They both are the version recommended for 92 but the copy to flash bootrom command has been deprecated and there are no commands to replace the primary boot code. Under 80f, there is only one flash bootrom command and there is no way to specify which partition to use. What's more 92b displays "Moving app to flash...." upon every boot and takes an annoyingly long (~15 sec) time. Going back from 92b to 80f loses some stacking/trunk port definitions if there is no pre-8090-startup-backup file. What was a convenience of PoE FW auto flashing is now a hassle. Switching between versions will cause during first reboot into the partition upgrade/downgrade of PoE FW which takes around 2 minutes.

The above served me right because reading the Software Upgrade guide shows Ruckus recommending upgrades of pre-08.0.80 by

flash 80 bootrom
flash non-UFI 80 image primary
reboot
flash 92 image primary
flash 92 image secondary
reboot

There is no support for different versions between partitions if their recommended bootroms are different.

Keeping 80f on primary for now.

Hi @klui,

I just upgraded to 08.0.95ca from 80f (non-UFI) following the Ruckus FastIron Software Upgrade Guide, 08.0.95 and ran into what I think is the same boot-monitor version mismatch issue as you did. I'm new here and your post was the only relevant Google hit I could find. Was able to resolve it and wanted to share in case the info helps you or anyone else.

I ran:

copy tftp flash 192.168.x.x mnz10114.bin bootrom
copy tftp flash 192.168.x.x SPR08080f.bin primary
boot system flash primary
copy tftp flash 192.168.x.x SPR08095caufi.bin primary
write memory
boot system flash primary
copy tftp flash 192.168.x.x SPR08095caufi.bin secondary
boot system flash primary

show boot-monitor and show flash outputs:

ICX7150-48ZP-Router>show boot-monitor
Stack unit 1:
Current Version :  10.1.14
Recommended Version:  10.1.19   (Mismatch)

ICX7150-48ZP-Router>show flash
Stack unit 1:
  NAND Type: Micron NAND 2GiB (x 1)
  Compressed Pri Code size = 33554432, Version:08.0.95cT213 (SPR08095ca.bin)
  Compressed Sec Code size = 33554432, Version:08.0.95cT213 (SPR08095ca.bin)
  Compressed Pri Boot Code size = 786944, Version:10.1.14T225 (mnz10114)
  Compressed Sec Boot Code size = 786944, Version:10.1.19T225 (mnz10119)
  Code Flash Free Space = 1095577600

Oddly even Ruckus' Upgrade Guide documentation shows a boot code mismatch (2.f.) after re-copying the 95 UFI to secondary (2.d.), except theirs was opposite mine (their primary boot code is newer and their secondary is older).

Simply rerunning the primary copy again got the boot code updated to match. I'm guessing if the secondary is behind, re-running it would work as well.

copy tftp flash 192.168.x.x SPR08095caufi.bin primary
write memory
reload

Afterward:
show boot-monitor

Stack unit 1:
Current Version :  10.1.19
Recommended Version:  10.1.19

show flash

Stack unit 1:
  NAND Type: Micron NAND 2GiB (x 1)
  Compressed Pri Code size = 33554432, Version:08.0.95cT213 (SPR08095ca.bin)
  Compressed Sec Code size = 33554432, Version:08.0.95cT213 (SPR08095ca.bin)
  Compressed Pri Boot Code size = 786944, Version:10.1.19T225 (mnz10119)
  Compressed Sec Boot Code size = 786944, Version:10.1.19T225 (mnz10119)
  Code Flash Free Space = 1054224384

 

[Bladerunner]

Hi all, I configured NTP in client-only mode with Google's time servers according to @fohdeesha's ICX 7150 guide, but all four of them are being tagged as "reject" ("This peer is rejected by the selection algorithm.") and stratum 16. Currently running 08.0.95ca on a 7150-48ZP.
Would greatly appreciate any help or guidance anyone can offer.

The official documentation's NTP Client Mode Configuration Example shows adding a peer in addition to multiple server entries. Is that strictly required? Am I missing something else? I'd really love the datetimes on the logs to correspond with reality...

NTP Status Output Reference
NTP Association Output Reference
NTP Association Details Output Reference

Relevant outputs below:

SW-CORE>show ntp status
Clock is unsynchronized, no reference clock
NTP server mode is disabled, NTP client mode is enabled
NTP master mode is disabled, NTP master stratum is 8
NTP is not in panic mode

SW-CORE>show ntp associations
address                                   Domain name                             Reference Clock  st  when  poll  Reach delay  offset   disp
~ 216.239.35.0                            None                                     INIT            16     -    64     0   0.00    0.000 15937.
~ 216.239.35.4                            None                                     INIT            16     -    64     0   0.00    0.000 15937.
~ 216.239.35.8                            None                                     INIT            16     -    64     0   0.00    0.000 15937.
~ 216.239.35.12                           None                                     INIT            16     -    64     0   0.00    0.000 15937.
* synced, # selected, + candidate, - outlayer, x falseticker, ~ configured, **More characters in domain name

SW-CORE>ping 216.239.35.0
Sending 1, 16-byte ICMP Echo to 216.239.35.0, timeout 5000 msec, TTL 64
Type Control-c to abort
Reply from 216.239.35.0    : bytes=16 time=22ms TTL=107
Success rate is 100 percent (1/1), round-trip min/avg/max=22/22/22 ms.

SW-CORE>show ntp association detail
216.239.35.0 configured server, reject,  stratum 16
ref ID INIT, time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
our mode client, peer mode server, our poll intvl 16, peer poll intvl 64,
root delay 0 msec, root disp 0, root dist 15.93802499
delay 0 msec, offset 0 msec, dispersion 15937.,
precision 2**-16, version 4
org time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
rcv time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
xmt time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
filter delay       0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter offset      0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter disp    16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000
filter epoch         576       118       185       249       313       380       444       511

216.239.35.4 configured server, reject,  stratum 16
ref ID INIT, time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
our mode client, peer mode server, our poll intvl 16, peer poll intvl 64,
root delay 0 msec, root disp 0, root dist 15.93802499
delay 0 msec, offset 0 msec, dispersion 15937.,
precision 2**-16, version 4
org time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
rcv time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
xmt time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
filter delay       0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter offset      0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter disp    16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000
filter epoch         576       117       181       247       312       379       446       511

216.239.35.8 configured server, reject,  stratum 16
ref ID INIT, time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
our mode client, peer mode server, our poll intvl 16, peer poll intvl 64,
root delay 0 msec, root disp 0, root dist 15.93801000
delay 0 msec, offset 0 msec, dispersion 15937.,
precision 2**-16, version 4
org time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
rcv time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
xmt time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
filter delay       0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter offset      0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter disp    16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000
filter epoch         577       119       184       250       314       380       444       510

216.239.35.12 configured server, reject,  stratum 16
ref ID INIT, time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
our mode client, peer mode server, our poll intvl 16, peer poll intvl 64,
root delay 0 msec, root disp 0, root dist 15.93799500
delay 0 msec, offset 0 msec, dispersion 15937.,
precision 2**-16, version 4
org time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
rcv time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
xmt time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
filter delay       0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter offset      0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter disp    16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000
filter epoch         578       117       184       249       314       381       448       513

 

[Archos]

Is there anything like a 6450 basic admin guide for dummies out there? I'm not trying to do much beyond L2 stuff at the moment. Especially looking for guidance in setting up SFP and SFP+ modules and bonding ports with LACP.

There is some good stuff here: NetAdmin.us Website

The ICX Configuration Tool (GUI) can generate L2 switch config based on your input.

Terry Henry also has alot of good snippets on different things: https://www.youtube.com/c/TerryHenry/videos

 

[pod]

Hi all, I configured NTP in client-only mode with Google's time servers according to @fohdeesha's ICX 7150 guide, but all four of them are being tagged as "reject" ("This peer is rejected by the selection algorithm.") and stratum 16. Currently running 08.0.95ca on a 7150-48ZP.
Would greatly appreciate any help or guidance anyone can offer.

The official documentation's NTP Client Mode Configuration Example shows adding a peer in addition to multiple server entries. Is that strictly required? Am I missing something else? I'd really love the datetimes on the logs to correspond with reality...

NTP Status Output Reference
NTP Association Output Reference
NTP Association Details Output Reference

Relevant outputs below:

SW-CORE>show ntp status
Clock is unsynchronized, no reference clock
NTP server mode is disabled, NTP client mode is enabled
NTP master mode is disabled, NTP master stratum is 8
NTP is not in panic mode

SW-CORE>show ntp associations
address                                   Domain name                             Reference Clock  st  when  poll  Reach delay  offset   disp
~ 216.239.35.0                            None                                     INIT            16     -    64     0   0.00    0.000 15937.
~ 216.239.35.4                            None                                     INIT            16     -    64     0   0.00    0.000 15937.
~ 216.239.35.8                            None                                     INIT            16     -    64     0   0.00    0.000 15937.
~ 216.239.35.12                           None                                     INIT            16     -    64     0   0.00    0.000 15937.
* synced, # selected, + candidate, - outlayer, x falseticker, ~ configured, **More characters in domain name

SW-CORE>ping 216.239.35.0
Sending 1, 16-byte ICMP Echo to 216.239.35.0, timeout 5000 msec, TTL 64
Type Control-c to abort
Reply from 216.239.35.0    : bytes=16 time=22ms TTL=107
Success rate is 100 percent (1/1), round-trip min/avg/max=22/22/22 ms.

SW-CORE>show ntp association detail
216.239.35.0 configured server, reject,  stratum 16
ref ID INIT, time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
our mode client, peer mode server, our poll intvl 16, peer poll intvl 64,
root delay 0 msec, root disp 0, root dist 15.93802499
delay 0 msec, offset 0 msec, dispersion 15937.,
precision 2**-16, version 4
org time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
rcv time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
xmt time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
filter delay       0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter offset      0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter disp    16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000
filter epoch         576       118       185       249       313       380       444       511

216.239.35.4 configured server, reject,  stratum 16
ref ID INIT, time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
our mode client, peer mode server, our poll intvl 16, peer poll intvl 64,
root delay 0 msec, root disp 0, root dist 15.93802499
delay 0 msec, offset 0 msec, dispersion 15937.,
precision 2**-16, version 4
org time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
rcv time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
xmt time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
filter delay       0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter offset      0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter disp    16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000
filter epoch         576       117       181       247       312       379       446       511

216.239.35.8 configured server, reject,  stratum 16
ref ID INIT, time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
our mode client, peer mode server, our poll intvl 16, peer poll intvl 64,
root delay 0 msec, root disp 0, root dist 15.93801000
delay 0 msec, offset 0 msec, dispersion 15937.,
precision 2**-16, version 4
org time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
rcv time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
xmt time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
filter delay       0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter offset      0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter disp    16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000
filter epoch         577       119       184       250       314       380       444       510

216.239.35.12 configured server, reject,  stratum 16
ref ID INIT, time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
our mode client, peer mode server, our poll intvl 16, peer poll intvl 64,
root delay 0 msec, root disp 0, root dist 15.93799500
delay 0 msec, offset 0 msec, dispersion 15937.,
precision 2**-16, version 4
org time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
rcv time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
xmt time 0.0 (19:00:00.0 GMT-05 Sun Dec 31 1899)
filter delay       0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter offset      0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000
filter disp    16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000 16000.000
filter epoch         578       117       184       249       314       381       448       513

Are you using the dns names time1.google.com, time2.google.com...? I would guess they do the Cloudflare no direct access thing.

 

[kapone]

Question for the 6610 owners out there:

The material here says the 6610 is 16" deep, no matter the number of ports.

1. Does that depth figure include the fan and power supply handles in the back, or is it just for the chassis itself (not including the handles)?

View attachment 18311

2. I noticed in one of the pictures from an ebay seller that you can mount the rack ears a bit further to the back than normal, like this:

View attachment 18312

Does anybody have the measurement of the distance represented by the red line above? How many inches is that?

I'm trying to see if I can fit a 6610 in the rack I have on order. I'm considering if it's worth going with a bigger one just for this.

Thanks!

I did a rough measurement, without de-racking mine at home, and the red line should be ~6.5".