10-26-2012 03:02 AM
I haven't heard of the 'supportSave -all' argument yet.
Typically if you just run 'supportSave' it will prompt you for a server to upload the log.
In the target directory it should create a bunch of gz files (they typically look something like <switchname>-S0cp-<timestamp>.<SSAVE_section>.txt.ss.gz).
Or else you configure 'supportFtp' and then just run 'supportSave -c' which will use that configuration.
Otherwise 'supportShow' will do as well I guess ..
10-26-2012 04:17 AM
I don't see anything sticking out, 'df' output is ok, the 'bootenv' variables look standard (just compared with a B300 in my lab) etc.
Could you try upgrading to another release in the 6.1.x family first? Otherwise you may want to open a case with BRCD support.
10-26-2012 04:21 AM
this is official Brocade path Upgrade procedure.
Upgrade path to Brocade FOS 6.4.2a or FOS v7.0.0x for Open Systems environments:
FOS 6.0.0c FOS 6.1.2c FOS 6.2.2f FOS 6.3.2d FOS 6.4.2a FOS 7.0.0x
try another FOS package i.e. 6.2.2LETTER instead the one you used.
Keep in mind - I don't have at the moment the list on the hand - Brocade build some package which are intended for specific plattforms only, with other word the package contained only the signature for specific plattforms.
if you get the same error with FOS 6.2.2, then try first to upgrade to any FOS 6.1.x however higher as the current 6.1.0c