Brocade ICX Series (cheap & powerful 10gbE/40gbE switching)
- Thread starter fohdeesha
- Start date
EDIT - Sorry I missed that you already purchased the transceivers. If you can return them then...
Have you looked at AOC? If you are in the united states then pricing might be right.
for example: NEW Mellanox MC2206310-015 15 Meter 40GB 40 Gb QSFP to QSFP AOC Fiber Cable 9782206310015 | eBay
Last edited:
Have you checked fs.com?
A 40Gb using LC is going to be a BiDi, so not cheap compared to normal home budgets and pricing for a MTP/MPO type.
Nice. That's about $30 cheaper than the Fiber cables I was looking at. And because I messed up already... I can use these as stack links or uplinks correct?
Yes I did look at FS and about choked. I figured 40G was all LC or breakout. I did not even think to check.
yes. I have some shorter ones (2m) that I used to stack (till my spare 6610's got flakey) and now use as host interconnects to a TNC filer.
btw, I did not search or look very hard. There may be some cheaper ones on the bay as well. Simply a quick check that met your criteria.
Thankyou. I added them to my watch list. I appreciate the quick response and follow up!
first, im sure there is an answer posted already some where but having a heck of a time finding it or generating a search for what im trying to find. doing my due dilagents i've combed through the forum and get the impression its possible but can't seem to find a specific answer or method? that said, my outlet temp is kicking into fan speed 2 by 1 degree. how does one go about changing the fan threshold to increase the temp the second speed kicks in? again, sorry to just ask directly but i've searching for a while and can't seem to find what i'm looking for. feel free to post a link rather than explaining if it is possible.
What is the room temperature and load of the switch? There have been reports of the heatsinks popping off the ASICs and causing hell with temps until resecured.
Unfortunately you can not log permit actions.
Hi hi,
I still don't know what I'm doing wrong and now I'm just confused as to what's happening. As dos said, the 64xx series boots slower, but I somehow am unable to reach the bootloader. The switch is booting and functional, and I can see it on my network as an ethernet connected device(even when it's only on the management ethernet port). I can even navigate to the IP and reach the login page, but I am just so confused as to what I'm doing wrong with the serial cable. I'm still not getting output on PuTTy with the cisco console cable.
I still don't know what I'm doing wrong and now I'm just confused as to what's happening. As dos said, the 64xx series boots slower, but I somehow am unable to reach the bootloader. The switch is booting and functional, and I can see it on my network as an ethernet connected device(even when it's only on the management ethernet port). I can even navigate to the IP and reach the login page, but I am just so confused as to what I'm doing wrong with the serial cable. I'm still not getting output on PuTTy with the cisco console cable.
Ah frick the pinouts are different. But that explains even less about how I managed to get ANY output the first time round.
those are matching pinouts. transmit to recieve and vice versa. they're standard cisco style rj45 serial ports and will work with any of those adapters, if you're not getting output it usually turns out to be a driver issue under windows with all the ftdi's and related knockoffs. sometimes a reboot after the driver installs helps
Might want to try booting the ubuntu (pick your linux poison) live CD to see if that terminal works.
it might be possible whomever had the switch last changed the default baud rate to something other than 9600. can you see the boot process kick off at all with the serial cable or do you see nothing? as others said its possible that cable is toast. as long as you are using like a ft232r there shouldn't been any drivers required to install for any os. i have piles of these cables of all different types (db9, rj45, etc) and they all work. do you have another device like a cisco or some server to test? i even have some connected to my esxi servers as an additional last resort connection method for headless servers, so they are pretty versatile and should be easy to confirm functionality.
Last edited:
I had some serial output to PuTTy's console, then when I rebooted no more serial output. I've tried Windows 7,10, Arch and Debian. I rebooted after installing the FTDI drivers, and tried uninstalling them too. Like this is what's so frustrating. How did I get output once, then never reach the bootloader again with the same settings? I feel mucho dumb dumb, like I'm missing something super simple.
Unfortunately, no, I don't have any other managed switches. The only one i have is an unmanaged TP link one.
i haven't had a whole bunch of time to dig into the switch config yet, but just a quick poke looks like allow ssh only on the management vrf which is probably how they indented to restrict access. in addition there is an "ip ssh client" configuration that you can specifiy specific client ips that are allowed.
try a different cable. you might be spinning your wheels unnecessarily. i can promise you, that's how all of us ended up with so many of these cables over the years. that and aquiring extra from manufactures directly.