SX6036T (T Suffix!) does not support 56G.I try to force a port to 56g and it won't let me.
MSX6036T-1BRR-1 [standalone: master] (config interface ethernet 1/21) # speed ?
That explains so much! Thank you! it's odd that the switch says 56g when it's really locked to 40g.SX6036T (T Suffix!) does not support 56G.
You would have to flash a different backplane firmware (the one for normal SX6036F or SX6036G) and patch the PN in the EEPROMs (and there are some magic flags which you would also have to patch)
Why is that even locked? Silicon binning? Marketing?SX6036T (T Suffix!) does not support 56G.
I looked the 6036G/F have 4tb/s backplanes while the T only has 2.9tb/s. so they are different. I don't know enough to say for sure, but I imagine that will be an ASIC limitation.Why is that even locked? Silicon binning? Marketing?
Market segmentation. I did successfully "unlock" / "crossflash" 2 SX6036T to SX6036G.Why is that even locked? Silicon binning? Marketing?
No they are not different. Hardware-wise the switches are completely identical.I looked the 6036G/F have 4tb/s backplanes while the T only has 2.9tb/s. so they are different. I don't know enough to say for sure, but I imagine that will be an ASIC limitation.
Dude...minor correction (but I love what you did!).All steps expressedly without any warranty whatsoever. Another person should look over this and check that I have not made any error. Only then continue.
- Login and enable shell access
- enable
- conf t
- license install LK2-RESTRICTED_CMDS_GEN2-88A1-NEWD-BPNB-1
- fae cable-stamping-unlock 40g_lr4
- conf write
- (wait a little?)
- _shell
- Remove U-Boot password so you can always boot/flash your way back into the switch
- /opt/tms/bin/mddbreq /config/db/initial set modify - /system/bootmgr/password string ''
- eetool -a bf -s UBPASSWD=""
- Dump EEPROMs
- /opt/tms/bin/mellaggra _read_fru 1 0x51 1000 fru_backplate.bin
- /opt/tms/bin/mellaggra _read_fru 0 0x50 1000 fru_cpu.bin
- Copy them off via SFTP etc. ZIP and please send them to me. Needed to finally clear remaining SX6012 vs true SX1012 differences...
- Make the switch ethernet only
- system profile eth-single-switch
- This may completely erase your config, if so, repeat what is written in Step 1.
- Try updating straight to e.g. through the web GUI
- I will send you another shell command to apply after that update via PM
- Quieten down the fans (this is for 2-PSU model only probably - if you get whining, increase FAN_MIN)
- mount -nwo remount,rw /
- vi /etc/rc.local
- I hope you know how to use vi. If not, hit d d a couple of times to delete everything, then i to insert, :wq to save
Bash:#!/bin/sh touch /var/lock/subsys/local # mount -nwo remount,rw / # vi /etc/rc.d/rc.local FAN_MIN="27" FAN_MAX="50" WAIT_MAX="10" # 5 minutes MDREQ1="/opt/tms/bin/mdreq action /system/chassis/actions/set-fan-speed fan_module string" MDREQ2="fan_number int8 1 fan_speed int8" MDREQ3="set_max uint8" i=1 while :; do PID=$(pidof clusterd) if [ -n "$PID" ]; then sleep 60 echo "Adjusting fan speed" $MDREQ1 "/MGMT/FAN1" $MDREQ2 $FAN_MIN $MDREQ3 $FAN_MAX break else sleep 30 i=$((i+1)) if [ $i -gt $WAIT_MAX ]; then echo "Timeout waiting for clusterd" break fi fi done exit 0
Remember the fans are also cooling transceivers. Issue if you live in Arizona, in northern Sweden not so much. So in final habitat with a stress test running why not check transceiver temps. Could be as simple as turning off spanning tree, loop ports, and then inject a few broadcasts. Briefly also with external fan blowing at transceivers from the side, then at stock fan speeds. I'm a collector of datasheets and repair manuals and like to check maximum temperature ratings for low rate of surprises.idle power consumption is...35w
Doesn't matter.On step 7.2 it should be vi /etc/rc.d/rc.local not vi /etc/rc.local
[admin@sx6012c etc]# ls -ald rc*
lrwxrwxrwx 1 13 Apr 30 2018 rc.local -> rc.d/rc.local
Understood, and I do intend to stress test it (will be hosting production loads) as this will become the core switch. (And I'm in the DC area, no Arizona level heat here...Remember the fans are also cooling transceivers. Issue if you live in Arizona, in northern Sweden not so much. So in final habitat with a stress test running why not check transceiver temps. Could be as simple as turning off spanning tree, loop ports, and then inject a few broadcasts. Briefly also with external fan blowing at transceivers from the side, then at stock fan speeds. I'm a collector of datasheets and repair manuals and like to check maximum temperature ratings for low rate of surprises.
doh! Had forgotten about that, and I must have screwed up while writing the fan script. Because doing vi /etc/rc.local didn't seem to save the file, but that is likely user error.Doesn't matter.Code:[admin@sx6012c etc]# ls -ald rc* lrwxrwxrwx 1 13 Apr 30 2018 rc.local -> rc.d/rc.local
/dev/mtdblock7 524288 491388 32900 94% /
/dev/mtdblock7 on / type jffs2 (ro,noatime)
I don't know if it makes a difference or not...this is a brand new 6036, plain vanilla Mellanox.Maybe forgot to mount / rw?I'm actually more curious if you did anything special to get your 6036's fans' PWM to 15%. I haven't unboxed my 6036 but my 6012s' fans will surge between PWM percentage of < 30% and maximum every 5-10 seconds.Code:/dev/mtdblock7 524288 491388 32900 94% / /dev/mtdblock7 on / type jffs2 (ro,noatime)
# mount -nwo remount,rw /
# vi /etc/rc.d/rc.local
FAN_MIN=“15”
FAN_MAX="50"
WAIT_MAX="10" # 5 minutes
MDREQ1="/opt/tms/bin/mdreq action /system/chassis/actions/set-fan-speed fan_module string"
MDREQ2="fan_number int8 1 fan_speed int8"
MDREQ3="set_max uint8"
i=1
while :; do
PID=$(pidof clusterd)
if [ -n "$PID" ]; then
sleep 60
echo "Adjusting fan speed"
$MDREQ1 “/FAN/FAN1" $MDREQ2 $FAN_MIN $MDREQ3 $FAN_MAX
$MDREQ1 “/FAN/FAN2” $MDREQ2 $FAN_MIN $MDREQ3 $FAN_MAX
$MDREQ1 “/FAN/FAN3” $MDREQ2 $FAN_MIN $MDREQ3 $FAN_MAX
$MDREQ1 “/FAN/FAN4” $MDREQ2 $FAN_MIN $MDREQ3 $FAN_MAX
$MDREQ1 “/PS1/FAN1" $MDREQ2 $FAN_MIN $MDREQ3 $FAN_MAX
break
else
sleep 30
i=$((i+1))
if [ $i -gt $WAIT_MAX ]; then
echo "Timeout waiting for clusterd"
break
fi
fi
done
exit 0