iQstor report commands

March 8, 2010 at 4:22 pm (Technology, TechTips) (, )

Are you like me and need to generate system reports from your iQstor SAN units for debugging purposes?

Well then you’re in luck!  Below you will find the commands that will run the report command on both controllers.  It will also run the syslogd command on both controllers.  Simply specify the start and end dates for the syslogd command.

This will send the output to the terminal that you are on.  So, if you are going to telnet into the controllers, I suggest that you use the script tool to start your telnet session with.  Then when you are done, you just ctrl-d out of script and you’ll have the output files ready to send back into iQstor for them to look at.

And without further delay, here are the commands:

report
rrcii -C report
syslogd -q -a 3/4/10 -b 3/8/10
rrcii -C {syslogd -q -a 3/4/10 -b 3/8/10}
Advertisements

Permalink Leave a Comment

Bad RAM on iQstor.

February 10, 2010 at 2:55 pm (Technology, TechTips) (, , )

I have a iQstor 2880 SAN device.  Recently I was logged into one of the controllers and noticed some strange error messages showing up on the console:

10:49:11, Wednesday, 02/10/2010
: EXCEPTION: Dram Error detected:      count=19 cause=4000 esr_c_0004=20000 esr_c_000C=0 esr_c_Lcause=1 esr_c_Lerr=7cc2a2b6
Dram Error being handled: count=19 cause=4000 esr_c_0004=20000 esr_c_000C=0 esr_c_Lcause=1 esr_c_Lerr=7cc2a2b6
Dram Error recovered:      count=19 cause=4000 esr_c_0004=20000 esr_c_000C=0 esr_c_Lcause=1 esr_c_Lerr=7cc2a2b6

If you see errors like this, it indicates that you have bad RAM on the controller that you are logged into.  Now, the important thing to note here is that these memory errors will only show up on the console of the controller that has the bad RAM.  The messages will not be placed into syslog OR copied to the console of all controllers.  The best way to verify which controller has the bad RAM is to open a telnet session to both controllers and leave them up for a while.  Wait for the console posted error to show up and then you have confirmation on which controller to switch out the memory on.

Now, if only iQstor would get the errors to trigger an alert, copy to both consoles (with detail of which console has bad RAM, and syslog.

Permalink Leave a Comment