02-21-2012 01:23 PM
I have a Brocade 4900 with 64 ports and FOS 6.4.2a.
portstatsshow -i 0-512 -f
the switch had a kernel panic and rebooted.
I use this command in a script to also analyse some SW48000 and DCX.
Does anyone know if this problem will be fixed in FOS 7 ?
02-22-2012 03:01 AM
can you attach the output of errdump and errdumpall commands, to see if there is any event about the panic.
On the other hand, you can check the Defects fixed in FOS 7.x in each version Release notes.
02-22-2012 04:28 AM
attached is the errdump output from the relevant date 2012/02/20.
I can't see anythin that brings me further.
Sometimes things are fixed without mention when nobody noticed the mistake.
02-22-2012 12:02 PM
my guess is that the used range is causing your issue. I would suggest that you add your script a function to query the switch typ and run then portstatsshow -i 0-63 on this kind of switch.
03-24-2012 04:22 PM
got some infos from our maintenance partner:
... had contact to Brocade and they have confirm the issue with the portstatsshow command is a known defect.
The defect is listed as
Software 'verify' error detected when portstatsshow was executed with invalid index (999) and the -f option
It is fixed in the next major release ( 7.1.x)
At this point we have no schedule for FOS 7.1.x release.
03-24-2012 08:25 PM
--->>> I have a Brocade 4900 with 64 ports and FOS 6.4.2a.
keep in mind, FOS 7.x or higher is not supported on Old 4G Plattforms incl. 4900, 48000 etc.
want to ask, from of you get this info about DEFECT000376141 ?
03-25-2012 11:34 PM
I tested this on a Brocade 300 with FOS . The switch didn't panic but the protstatsshow hangs with high CPU load and it took a while until the command completed.
.this is sad cause this method to issue the command "portstatsshow -i 0-512 -f" is a good choise to generic script.
I am doing every day a supportsave to the environment and my script parses the supportsave information to avoid self scripted issues to the switches as far as possible.