Sorry Eong, got exhausted. So should the switch not upgraded with some of the core capabilites ?
While i recognize 'workarounds' are going to be required for L2 and GW, expected the basic
IB at 56GbE since its a F model, 648node, not sure what else.
Assuming for the moment i followed the rooting correctly, what is the procedure to break out from enable into bash?
From there, I can start doing some MFG changes/service starts, but i'm very fuzzy how the core licenses got wiped; these were in the db and not persistent across the upgrade?
Is the ppc model strictly jffs2, or has anybody tried ubifs/squash with success...maybe cleans up NAND ECC errs?
I stumbled over this MTD in the customer_rootflop.sh
# 16 MB NOR Flash:
# /dev/mtd0 [nmp] kernel 1 (raw partition, uImage kernel, cp / dd)
# /dev/mtd1 [nmp] kernel fdt 1 (raw partition, DTB, cp / dd)
# /dev/mtd2 [nmp] kernel 2 (raw partition, uImage kernel, cp / dd)
# /dev/mtd3 [nmp] kernel fdt 2 (raw partition, DTB, cp / dd)
# /dev/mtd4 [nmp] u-boot env (raw partition, U-boot env, cp / dd)
# /dev/mtd5 [nmp] u-boot (raw partition, U-boot, cp / dd)
#
# 1024 MB NAND Flash:
# /dev/mtdblock6 / [root 1] ro root (jffs2)
# /dev/mtdblock7 / [root 2] ro root (jffs2)
# /dev/mtdblock8 /config rw config db (jffs2)
# /dev/mtdblock9 /var rw general, logs (jffs2)
So definitely concerned to see:
|> Partition 1:
|> version: (Could not determine image version -- install in progress?)
is this normal, with this partition ( /dev/mtdblock6 ) ? that first boot into mini-kernel was a 2hr+ terminal flood of ecc errors so i'm second-guessing that i need to touch up a bunch.
I'm new to high-end gear modding for personal use, appreciate any tips & tricks that work.
~t2