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

[mintchipmadness]

Hello,
I bought an ICX7250-48P off of ebay. I updated the firmware following the instructions of fohdeesha and I seem to be in a boot loop. The files I flashed were SPR0809d.bin and spz10115.bin. I attached the log of the boot up from putty. The router booted up fine with the switch firmware so I am wondering what would cause the router firmware to boot loop. I saw something in the logs saying the thread is detached but I am not sure that is it. Any help would be greatly appreciated.

Edit: If the issue is the primary flash, how do I boot from secondary flash? I haven't dealt with these command line switches before. If secondary works, will it be ok to just use the secondary flash going forward?

 

[fohdeesha]

Hello,
I bought an ICX7250-48P off of ebay. I updated the firmware following the instructions of fohdeesha and I seem to be in a boot loop. The files I flashed were SPR0809d.bin and spz10115.bin. I attached the log of the boot up from putty. The router booted up fine with the switch firmware so I am wondering what would cause the router firmware to boot loop. I saw something in the logs saying the thread is detached but I am not sure that is it. Any help would be greatly appreciated.

Edit: If the issue is the primary flash, how do I boot from secondary flash? I haven't dealt with these command line switches before. If secondary works, will it be ok to just use the secondary flash going forward?

your flash is fine (you can see it chucksums correctly during boot), it looks like your switch just doesn't like that version. Start by flashing the exact files/version from my guide (8080) so you have a known starting point - the bootloader version and OS version are somewhat tied together as well, so IDK what OS version you flashed. Once you're on 8080 and it's booting properly, then you can start flashing the newer UEFI images (like 8092+)

I'm guessing it has something to do with this, which should be handled without an issue but it looks like it could be causing a crash:

Uboot and FI booted from different partitions, Uboot: Secondary, FI: Primary
Cannot auto correct cross boot combination, other partition of uboot does not have recommended uboot for current booted FI image

either way that will all be fixed and taken care of by flashing the files from the guide and then once on 8080 flashing 8092 from in the OS

since yours isn't booting, this is how to flash from the bootloader (replace filenames with appropriate files)

#plug the management ethernet port into your network
#drop into the bootloader
#give the switch a temporary IP

setenv ipaddr 192.168.1.50
setenv netmask 255.255.255.0

#tell the switch the IP of your tftp server:
setenv serverip 192.168.1.51

#tell it the name of the OS firmware file:
setenv image_name ICX64R08030t.bin

#tell it name of bootloaader file:
setenv uboot kxz10105.bin

#flash the OS:
update_primary

#when that's done flash a new bootloader:
update_uboot

#when everything is done reboot the switch:
reset

 

[fohdeesha]

Recently got a 7450-48P that I am trying to setup now.
I was under the impression that the (only two, I know) rear 40G ports could be used either as stack/data port or broken out to 4x10g.
I was hoping to use one as uplink and break out the other, but I am unable to identify the required commands to configure the port;
the manual's not showing anything, web only showd something for the 7750 (breakout ethernet) which is not available on the 7450.

I saw earlier discussions re active vs passive dac, and potentially only one channel working but, didnt see the test results.

I am using a passive/dac 4:1 split that used to work in my MLX switch

the rear 40gbE breakout ports are on the ICX6610 - the ICX7450 does not have any 40gbE module cards that support breakout that I know of, so your two rear 40gbE cards will operate in 40gbE only

 

[Rand__]

Ah I was afraid of that, thanks

 

[mintchipmadness]

your flash is fine (you can see it chucksums correctly during boot), it looks like your switch just doesn't like that version. Start by flashing the exact files/version from my guide (8080) so you have a known starting point - the bootloader version and OS version are somewhat tied together as well, so IDK what OS version you flashed. Once you're on 8080 and it's booting properly, then you can start flashing the newer UEFI images (like 8092+)

I'm guessing it has something to do with this, which should be handled without an issue but it looks like it could be causing a crash:

Uboot and FI booted from different partitions, Uboot: Secondary, FI: Primary
Cannot auto correct cross boot combination, other partition of uboot does not have recommended uboot for current booted FI image

either way that will all be fixed and taken care of by flashing the files from the guide and then once on 8080 flashing 8092 from in the OS

since yours isn't booting, this is how to flash from the bootloader (replace filenames with appropriate files)

#plug the management ethernet port into your network
#drop into the bootloader
#give the switch a temporary IP

setenv ipaddr 192.168.1.50
setenv netmask 255.255.255.0

#tell the switch the IP of your tftp server:
setenv serverip 192.168.1.51

#tell it the name of the OS firmware file:
setenv image_name ICX64R08030t.bin

#tell it name of bootloaader file:
setenv uboot kxz10105.bin

#flash the OS:
update_primary

#when that's done flash a new bootloader:
update_uboot

#when everything is done reboot the switch:
reset

Thank you for the reply. I really appreciate it. I apologize for being new but how do I drop into the bootloader from the management port? I looked at your guide and I couldn't find the information. Thank you.

 

[neb50]

Thank you for the reply. I really appreciate it. I apologize for being new but how do I drop into the bootloader from the management port? I looked at your guide and I couldn't find the information. Thank you.

Hit 'b' as it is booting? That is what I remember reading on some of the other models in this thread.

 

[mintchipmadness]

Hit 'b' as it is booting? That is what I remember reading on some of the other models in this thread.

Thank you. I was thinking there was something special with the management port but I guess I was over thinking it.

 

[mintchipmadness]

your flash is fine (you can see it chucksums correctly during boot), it looks like your switch just doesn't like that version. Start by flashing the exact files/version from my guide (8080) so you have a known starting point - the bootloader version and OS version are somewhat tied together as well, so IDK what OS version you flashed. Once you're on 8080 and it's booting properly, then you can start flashing the newer UEFI images (like 8092+)

I'm guessing it has something to do with this, which should be handled without an issue but it looks like it could be causing a crash:

Uboot and FI booted from different partitions, Uboot: Secondary, FI: Primary
Cannot auto correct cross boot combination, other partition of uboot does not have recommended uboot for current booted FI image

either way that will all be fixed and taken care of by flashing the files from the guide and then once on 8080 flashing 8092 from in the OS

since yours isn't booting, this is how to flash from the bootloader (replace filenames with appropriate files)

#plug the management ethernet port into your network
#drop into the bootloader
#give the switch a temporary IP

setenv ipaddr 192.168.1.50
setenv netmask 255.255.255.0

#tell the switch the IP of your tftp server:
setenv serverip 192.168.1.51

#tell it the name of the OS firmware file:
setenv image_name ICX64R08030t.bin

#tell it name of bootloaader file:
setenv uboot kxz10105.bin

#flash the OS:
update_primary

#when that's done flash a new bootloader:
update_uboot

#when everything is done reboot the switch:
reset

It worked!! Thank you. I flashed the firmware and bootloader files from your link and it booted perfectly. I then flashed the original firmware and bootloader files that caused the problem and the switch booted without issue.

 

[fohdeesha]

that'll be $4300

 

[cesmith9999]

@fohdeesha you're cheap...

Chris

 

[fohdeesha]

@fohdeesha you're cheap...

Chris

It's the holidays, I'm in a giving mood!

 

[Rand__]

the rear 40gbE breakout ports are on the ICX6610 - the ICX7450 does not have any 40gbE module cards that support breakout that I know of, so your two rear 40gbE cards will operate in 40gbE only

I see I can't even force the port down to 10 to use an adapter:/
Can I replace either the 40G module with a 4x SFP+ module (while keeping the other at 40, data usage for switch to switch interconnect) ?

Also, can I connect the management interface to a port on the switch? Having some issues with that one... its not working on the 7450 itself and not on one other switch, but on a third. Very weird

Edit - just verified that the ports are all good. One of the runs is rather long (30m), but it works fine with a pi attached. Both Cisco (one working [short run], one not [long run]) have identical config (VLAN1 untagged/access)

Edit 2 - its not the length of the run, added another small switch in between, switch is reachable but 7450 not. This one is really giving me a hard time...

 

[LodeRunner]

I see I can't even force the port down to 10 to use an adapter:/
Can I replace either the 40G module with a 4x SFP+ module (while keeping the other at 40, data usage for switch to switch interconnect) ?

Also, can I connect the management interface to a port on the switch? Having some issues with that one... its not working on the 7450 itself and not on one other switch, but on a third. Very weird

Edit - just verified that the ports are all good. One of the runs is rather long (30m), but it works fine with a pi attached. Both Cisco (one working [short run], one not [long run]) have identical config (VLAN1 untagged/access)

Edit 2 - its not the length of the run, added another small switch in between, switch is reachable but 7450 not. This one is really giving me a hard time...

Yes, you should be able to use the 4x10 SFP+ in any of the 3 mod slots on the 7450.

 

[Rand__]

Maybe I got a lemon but this 7450 is really annoying.
Maybe its the fw; it came with a 90 line from the vendor and I have not downgraded since I needed to get it going. Will try that next.

Edit: looks like I started with a lot of mistakes into this whole experiment ...
" (do NOT use the dedicated management port). "

Regardless of that I am probably using the wrong FW and have not set it up according to the recommendations; still the question remains why the mgmt port will work on switch A but not on switch B with identical port/vlan/stp settings

 

[csementuh]

post the output of "show run" and "show sz status" and "show sz logs"

Thanks man, I appreciate you willing to help!

My pihole reports this entry several times a minute:

2020-12-29 11:39:50

A

sw-registrar.ruckuswireless.com

utm.local

Blocked (exact blacklist)

IP (0.0ms)

That shows coming from my Untangle box, which shows up like that since I use it for DHCP and pihole contacts it for local name resolution. So it doesn't show coming from my Brocade switch directly, but this 7250-48P is the only Brocade/Ruckus device I have running on the network and I 100% assume it to be the culprit.

Here's the requested info, I've cut out my VLAN and port names so it isn't a mile long.

show run
Current configuration:
!
ver 08.0.80eT213
!
stack unit 1
  module 1 icx7250-48p-poe-port-management-module
  module 2 icx7250-sfp-plus-8port-80g-module
!
!
!
no inline power ethernet 1/1/35 to 1/1/36
aaa authentication web-server default local
aaa authentication login default local
enable telnet authentication
enable aaa console
hostname fl-es1
ip dhcp-client disable
ip dns domain-list 200freedomlane.com
ip dns server-address 192.168.1.1 9.9.9.9
ip route 0.0.0.0/0 192.168.1.1
!
no telnet server
username admin password .....
!
!
snmp-server community ..... ro
!
!
clock summer-time
clock timezone gmt GMT-05
!
!
ntp
disable serve
server 216.239.35.0
server 216.239.35.4
!
!
!
sz disable
!
no sz registrar
!
!
!
end

show sz status

============    SZ Agent State Info     ===================
Config Status: Disabled Operation Status: Disabled
State: DISABLED             Prev State: INIT                 Event: NONE

SWR List            : None
Active List         : None
DHCP Option 43      : No
DHCP Opt 43 List    : None
Passive List        : None
Merged List         : None
Merged Idx: 0    IP : 0.0.0.0

SZ IP Used          : 0.0.0.0
SZ Query Status     :
        Not Initiated

SSH Tunnel Status - :
  Tunnel Status     : Not Initiated
  CLI IP/Port       : /0
  SNMP IP/Port      : /0
  Syslog IP/Port    : /0

Timer Status        : Not Running

The logs showed entries from early Sep and then seemed to end on Sep 10th. I've grabbed the last couple entries. That doesn't make sense since I'm still getting DNS hits as we speak.

EDIT It looks like my log output is being truncated here and there are current entries. I can't figure out the correct syntax to get current date info.
show sz logs | begin xxx may work if I can use it to search for today.

IP Addrs:
Sep  9 15:57:34:54.186.0.83
Sep  9 15:57:34:54.191.58.33
Sep  9 15:57:34:34.208.35.231
Sep  9 15:57:34:
Sep  9 15:57:34:Resolved swr_ip:54.186.0.83
Sep  9 15:57:34:ca_connect_via_https>Init request to 54.186.0.83 Method: 3 URL: /api/v2/switches/DUQ3219N108
Sep  9 15:57:34:https_connmgr_send_request>Entered.
Sep  9 15:57:34:https_connmgr_send_request>Starting Connect with con: 0 req: 0 Comb:00000000
Sep  9 15:57:34:https_connmgr_send_request>Done.
Sep  9 15:57:34:https_client_callback>with Action: 4097 -- User-Data: 00000000
Sep  9 15:57:34:https_client_callback:125>Connect:Rx Handle 1 My hdl-0/0
Sep  9 15:57:36:http_conn_mgr_outgoing_connection_ready_cb>Entered.
Sep  9 15:57:36:http_conn_mgr_outgoing_connection_ready_cb>HTTP Send with con: 0 req: 0 Comb:00000000
Sep  9 15:57:36:http_conn_mgr_outgoing_connection_ready_cb>Done.
Sep  9 15:57:36:https_client_callback>with Action: 4115 -- User-Data: 00000000
Sep  9 15:57:36:https_client_callback:148>Get/Post:Rx Handle 1 My hdl-0/0
Sep  9 15:57:37:http_conn_mgr_receive_data_ready_cb>Entered.
Sep  9 15:57:37:http_conn_mgr_receive_data_ready_cb>HTTP Recv with con: 0 req: 0 Comb:00000000
Sep  9 15:57:37:http_conn_mgr_receive_data_ready_cb>Done.
Sep  9 15:57:37:http_conn_mgr_remote_close_connection_cb>Entered.
Sep  9 15:57:37:http_conn_mgr_remote_close_connection_cb>HTTP Closing con: 0 req: 0 Comb:00000000
Sep  9 15:57:37:https_client_callback>with Action: 4098 -- User-Data: 00000000
Sep  9 15:57:37:https_client_callback:166>Recv:Rx Handle 1 My hdl-0/0
Sep  9 15:57:37:Enter sz_agt_swr_query_resp_cb with status: 404, buf: , parm: 0
Sep  9 15:57:37:Start SZ_SWR_TIMER with time_out: 57570544
Sep  9 15:57:37:ca_stop_timer>Cancelled Timer id 0, rc=0
Sep  9 15:57:37:ca_start_timer:-89159962>Started timer with l/p 57570544/57570544 for u17, rc 0, id 0
Sep  9 15:57:37:Switch registrar discovery failed with http status = 404
Sep  9 15:57:37:https_client_callback>with Action: 4099 -- User-Data: 00000000
Sep  9 15:57:37:https_client_callback:135>Close:Rx Handle 1 My hdl-0/0
Sep 10 07:57:05:ca_stop_timer>Cancelled Timer id 0, rc=344846205
Sep 10 07:57:05:sz_swr_discovery>Attempting Switch Registrar DISCOVER count = 1144
Sep 10 07:57:05:Enter sz_send_swr_query_request with source = 0
Sep 10 07:57:05:Resolving Switch REGISTRAR FQDN: sw-registrar.ruckuswireless.com
Sep 10 07:57:05:FQDN Info for ca_resolve_fqdn
Sep 10 07:57:05:IP Count:   3 FQDN: sw-registrar.ruckuswireless.com
IP Addrs:
Sep 10 07:57:05:34.208.35.231
Sep 10 07:57:05:54.191.58.33
Sep 10 07:57:05:54.186.0.83
Sep 10 07:57:05:
Sep 10 07:57:05:Resolved swr_ip:34.208.35.231
Sep 10 07:57:05:ca_connect_via_https>Init request to 34.208.35.231 Method: 3 URL: /api/v2/switches/DUQ3219N108
Sep 10 07:57:05:https_connmgr_send_request>Entered.
Sep 10 07:57:05:https_connmgr_send_request>Starting Connect with con: 0 req: 0 Comb:00000000
Sep 10 07:57:05:https_connmgr_send_request>Done.
Sep 10 07:57:05:https_client_callback>with Action: 4097 -- User-Data: 00000000
Sep 10 07:57:05:https_client_callback:125>Connect:Rx Handle 1 My hdl-0/0
Sep 10 07:57:07:http_conn_mgr_outgoing_connection_ready_cb>Entered.
Sep 10 07:57:07:http_conn_mgr_outgoing_connection_ready_cb>HTTP Send with con: 0 req: 0 Comb:00000000
Sep 10 07:57:07:http_conn_mgr_outgoing_connection_ready_cb>Done.
Sep 10 07:57:07:https_client_callback>with Action: 4115 -- User-Data: 00000000
Sep 10 07:57:07:https_client_callback:148>Get/Post:Rx Handle 1 My hdl-0/0
Sep 10 07:57:07:http_conn_mgr_receive_data_ready_cb>Entered.
Sep 10 07:57:07:http_conn_mgr_receive_data_ready_cb>HTTP Recv with con: 0 req: 0 Comb:00000000
Sep 10 07:57:07:http_conn_mgr_receive_data_ready_cb>Done.
Sep 10 07:57:07:http_conn_mgr_remote_close_connection_cb>Entered.
Sep 10 07:57:07:http_conn_mgr_remote_close_connection_cb>HTTP Closing con: 0 req: 0 Comb:00000000
Sep 10 07:57:07:https_client_callback>with Action: 4098 -- User-Data: 00000000
Sep 10 07:57:07:https_client_callback:166>Recv:Rx Handle 1 My hdl-0/0
Sep 10 07:57:07:Enter sz_agt_swr_query_resp_cb with status: 404, buf: , parm: 0
Sep 10 07:57:07:Start SZ_SWR_TIMER with time_out: 57570544
Sep 10 07:57:07:ca_stop_timer>Cancelled Timer id 0, rc=0
Sep 10 07:57:07:ca_start_timer:-31587303>Started timer with l/p 57570544/57570544 for u17, rc 0, id 0
Sep 10 07:57:07:Switch registrar discovery failed with http status = 404
Sep 10 07:57:07:https_client_callback>with Action: 4099 -- User-Data: 00000000
Sep 10 07:57:07:https_client_callback:135>Close:Rx Handle 1 My hdl-0/0
Sep 10 23:56:35:ca_stop_timer>Cancelled Timer id 0, rc=349544543
Sep 10 23:56:35:sz_swr_discovery>Attempting Switch Registrar DISCOVER count = 1145
Sep 10 23:56:35:Enter sz_send_swr_query_request with source = 0
Sep 10 23:56:35:Resolving Switch REGISTRAR FQDN: sw-registrar.ruckuswireless.com
Sep 10 23:56:35:FQDN Info for ca_resolve_fqdn
Sep 10 23:56:35:IP Count:   3 FQDN: sw-registrar.ruckuswireless.com
IP Addrs:
Sep 10 23:56:35:54.191.58.33
Sep 10 23:56:35:34.208.35.231
Sep 10 23:56:35:54.186.0.83
Sep 10 23:56:35:
Sep 10 23:56:35:Resolved swr_ip:54.191.58.33
Sep 10 23:56:35:ca_connect_via_https>Init request to 54.191.58.33 Method: 3 URL: /api/v2/switches/DUQ3219N108
Sep 10 23:56:35:https_connmgr_send_request>Entered.
Sep 10 23:56:35:https_connmgr_send_request>Starting Connect with con: 0 req: 0 Comb:00000000
Sep 10 23:56:35:https_connmgr_send_request>Done.
Sep 10 23:56:35:https_client_callback>with Action: 4097 -- User-Data: 00000000
Sep 10 23:56:35:https_client_callback:125>Connect:Rx Handle 1 My hdl-0/0
Sep 10 23:56:38:http_conn_mgr_outgoing_connection_ready_cb>Entered.
Sep 10 23:56:38:http_conn_mgr_outgoing_connection_ready_cb>HTTP Send with con: 0 req: 0 Comb:00000000
Sep 10 23:56:38:http_conn_mgr_outgoing_connection_ready_cb>Done.
Sep 10 23:56:38:https_client_callback>with Action: 4115 -- User-Data: 00000000
Sep 10 23:56:38:https_client_callback:148>Get/Post:Rx Handle 1 My hdl-0/0
Sep 10 23:56:38:http_conn_mgr_receive_data_ready_cb>Entered.
Sep 10 23:56:38:http_conn_mgr_receive_data_ready_cb>HTTP Recv with con: 0 req: 0 Comb:00000000
Sep 10 23:56:38:http_conn_mgr_receive_data_ready_cb>Done.
Sep 10 23:56:38:http_conn_mgr_remote_close_connection_cb>Entered.
Sep 10 23:56:38:http_conn_mgr_remote_close_connection_cb>HTTP Closing con: 0 req: 0 Comb:00000000
Sep 10 23:56:38:https_client_callback>with Action: 4098 -- User-Data: 00000000
Sep 10 23:56:38:https_client_callback:166>Recv:Rx Handle 1 My hdl-0/0
Sep 10 23:56:38:Enter sz_agt_swr_query_resp_cb with status: 404, buf: , parm: 0
Sep 10 23:56:38:Start SZ_SWR_TIMER with time_out: 57570544
Sep 10 23:56:38:ca_stop_timer>Cancelled Timer id 0, rc=0
Sep 10 23:56:38:ca_start_timer:25985660>Started timer with l/p 57570544/57570544 for u17, rc 0, id 0
Sep 10 23:56:38:Switch registrar discovery failed with http status = 404
Sep 10 23:56:38:https_client_callback>with Action: 4099 -- User-Data: 00000000
Sep 10 23:56:38:https_client_callback:135>Close:Rx Handle 1 My hdl-0/0
Sep 11 10:20:53:ca_stop_timer>Cancelled Timer id 0, rc=354242886
Sep 11 10:20:59:sz_execute_state_machine>Entering with state/event: INIT/0, DISABLE/2005
Sep 11 10:20:59:sz_execute_state_machine>Exit with state/event: DISABLED/1, NONE/2000 RC: 1
End i/max/iter 250/250/0

 

[Zer0Day]

Picked up a 7150-48zp recently (the multigig poe+ model with redundant internal PSU/fan support), and it seems to have the early dev uboot firmware that's been found in the wild recently (boot output attached). I can setenv and TFTP successfully, but update_primary and update_uboot aren't options. uboot help menu shows the following commands:

u-boot> help
? - alias for 'help'
base - print or set address offset
bdinfo - print Board Info structure
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootelf - Boot from an ELF image in memory
bootm - boot application image from memory
bootp - boot image via network using BOOTP/TFTP protocol
bootvx - Boot vxWorks from an ELF image
bootz - boot Linux zImage image from memory
chpart - change active partition
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
cplddl - cplddl - To perform cpld download
crc32 - checksum calculation
dhcp - boot image via network using DHCP/TFTP protocol
echo - echo args to console
editenv - edit environment variable
env - environment handling commands
erase - erase FLASH memory
exit - exit script
ext2load- load binary file from a Ext2 filesystem
ext2ls - list files in a directory (default /)
false - do nothing, unsuccessfully
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
fatsize - determine a file's size
fatwrite- write file into a dos filesystem
fdt - flattened device tree utility commands
flinfo - print FLASH memory information
go - start application at address 'addr'
gpio_read- Read from GPIO
gpio_write- write to GPIO
hash - compute hash message digest
help - print command description/usage
i2c - I2C sub-system
iminfo - print header information for application image
imxtract- extract a part of a multi-image
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loadx - load binary file over serial line (xmodem mode)
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
md - memory display
mdc - memory display cyclic
mdio - MDIO utility commands
mii - MII utility commands
mm - memory modify (auto-incrementing address)
mtdparts- define flash/nand partitions
mtest - simple RAM read/write test
mw - memory write (fill)
mwc - memory write cyclic
nand - NAND sub-system
nboot - boot from NAND device
nfs - boot image via network using NFS protocol
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
sf - SPI flash sub-system
showvar - print local hushshell variables
sleep - delay execution for some time
source - run script from memory
test - minimal test like /bin/sh
tftp -
tftpboot- boot image via network using TFTP protocol
tftpput - TFTP put command, for uploading files to a server
time - run commands and summarize execution time
true - do nothing, successfully
ubi - ubi commands
ubifsload- load file from an UBIFS filesystem
ubifsls - list files in a directory
ubifsmount- mount UBIFS volume
ubifsumount- unmount UBIFS volume
usb - USB sub-system
usbboot - boot from USB device
version - print monitor, compiler and linker version
u-boot>

I can tftp to memory, but from there how can I tell what flash address to copy the bin files to for this model?

 

[klui]

I have seen some switches whose management ports don't work. It's an old HW rev, or engineering sample, if you will. I thought I read that some switches could have their management ports disabled/damaged? Mellanox (I2C pins)?

@fohdeesha would know for sure about Brocades.

 

[Rand__]

I have seen some switches whose management ports don't work. It's an old HW rev, or engineering sample, if you will. I thought I read that some switches could have their management ports disabled/damaged? Mellanox (I2C pins)?

Yes, had that on an ES SX6012, and my SN2700 has issues with the console port, but that one is swappable at least.
Here its working 100% of the time with one switch, and 0% of the time with another.
Doesn't make sense at all

 

[Zer0Day]

I have seen some switches whose management ports don't work. It's an old HW rev, or engineering sample, if you will. I thought I read that some switches could have their management ports disabled/damaged? Mellanox (I2C pins)?

@fohdeesha would know for sure about Brocades.

Don't think that's the case here, as I am able to successfully TFTP an image via the management port into RAM after setting all my environment variables to my local subnet:

u-boot> md 64000000
64000000: 4c494e58 02130000 01c727f8 3bd58087    LINX......'.;...
64000010: 36d212a7 00000000 00000000 6c000000    6...........l...
64000020: 00000000 00000000 00000000 00000000    ................
64000030: 9e138c5e 08005006 53505230 38303830    ...^..P.SPR08080
64000040: 66000000 00000000 08005000 00000000    f.........P.....
64000050: 00000000 00000000 00000000 00000000    ................
64000060: 00000000 00000000 00000000 00000000    ................
64000070: 00000000 00000000 00000000 00000000    ................
64000080: 00000000 00000000 00000000 00000000    ................
64000090: 00000000 00000000 00000000 00000000    ................
640000a0: 00000000 00000000 00000000 00000000    ................
640000b0: 00000000 00000000 00000000 00000000    ................
640000c0: 00000000 00000000 00000000 00000000    ................
640000d0: 00000000 00000000 00000000 00000000    ................
640000e0: 00000000 00000000 00000000 00000000    ................
640000f0: 00000000 00000000 00000000 00000000    ................
u-boot>

I was hoping to follow roughly the process Fodeesha described HERE, but with my hardware I'm sure the offset addresses will be different. It may be a moot point however, as I tried getting more info from uboot and found this:

u-boot> bdinfo
arch_number = 0x0000127F
boot_params = 0x60200000
DRAM bank   = 0x00000000
-> start    = 0x60000000
-> size     = 0x3FE00000
eth0name    = bcm_xgs_gmac-0
ethaddr     = 78:A6:E1:42:04:F4
current eth = bcm_xgs_gmac-0
ip_addr     = 10.225.100.217
baudrate    = 9600 bps
TLB addr    = 0x9FDF0000
relocaddr   = 0x9FD0C000
reloc off   = 0xAFD0C000
irq_sp      = 0x9F4FBEF0
sp start    = 0x9F4FBEE0

u-boot> coninfo
List of available devices:
serial   00000003 IO stdin stdout stderr
eserial0 00000003 IO

u-boot> version

U-Boot 2016.01-Broadcom XLDK-3.8.1-svn20827 (Dec 12 2016 - 09:36:45 +0800)
armeb-linux-gcc.br_real (Buildroot 2015.11.1-svn18338) 4.9.3
GNU ld (GNU Binutils) 2.24

u-boot> flinfo

Bank # 1: missing or unknown FLASH type
u-boot>

..which seems to indicate that the flash is missing or corrupt, so I'm not sure if I'd be able to copy to it in the first place. Input welcome but if I cant see flash this one's probably going back from whence it came. Unless it could be configured to load an image from USB/TFTP on every bootup?

 

[LodeRunner]

Do any of the nand commands work for getting info?

As far as USB boot, I see the USB boot command in the uboot list, but I've never set that up, so no idea what formatting requirements are.