SE 3510 Battery Issue


 
Thread Tools Search this Thread
Operating Systems Solaris SE 3510 Battery Issue
# 1  
Old 07-05-2008
Incredible has a couple of good points there. The firmware version is VERY old, I haven't seen a 3.27 version in probably two years. The sscs version is also very old, and didn't have all of the features which are available in the later versions. With older versions some of the settings still have to be performed through the out-of-band interface on the array either by serial connection or the network interface.
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Linux

Battery always 0%

Im running Ubuntu 9.04 and the battery indicator on my laptop always reads 0% no matter what. Whether im charging or discharging, the pop up says: "Computer is running on battery power Laptop battery discharging (0.0%) Battery discharge time is currently unknown" When plugged in it says... (2 Replies)
Discussion started by: Charbs
2 Replies

2. UNIX for Advanced & Expert Users

3510 Disk Array Problem

I have a 3510 disk array attached to a T2000 server. The dmesg command shows disk error as follows and is generated a couple of times during the day Aug 18 03:35:51 myserver SUNWscsdMonitor: <rctrl6042> Standard General Event, CHL:2 ID:22 Drive NOTICE: Drive Recovered Error - 5F8E1F... (1 Reply)
Discussion started by: Tirmazi
1 Replies

3. Solaris

EFI Disk labels on 3510 raid array

Hi Peeps, Can anyone help me an EFI lablel on a 3510 raid array that I cannot get rid of, format -e and label just asks you if you want to label it. Want an SMI label writing to it. Anyone got any ideas on how to remove the EFI label? Thanks in advance Martin (2 Replies)
Discussion started by: callmebob
2 Replies

4. Solaris

adding existing disks to a 3510 array

I would like to extend a logical drive on our 3510. I have four unallocated disks which I would like to use for this purpose. The 3510 supports a Sun Cluster but for now all I wish to see is a "new" disk when I run format. I am a little familiar with the telnet/ssh session on the 3510 but am... (2 Replies)
Discussion started by: malcqv
2 Replies

5. UNIX for Advanced & Expert Users

Problemwith 3510 array.

I have 2 3510FC arrays, one a JBOD with (7) 146GB drives, and the other with dual RAID controllers, also (7) 146GB drives. The idea was to get 1TB mirrored. Anyway, after installing the Enterprise Storage Manager on a connected V880, I was able to use the "sccli" command and see/configure all the... (7 Replies)
Discussion started by: ridgeback00
7 Replies

6. UNIX for Dummies Questions & Answers

A1000 Battery Question

After searching and finding the link to the A1000 pdf ( http://192.18.99.138/805-7147/805-7147.pdf ) my questions are: 1) I have a battery failure on a A1000. I know that caching is disabled and it reports to see log. After reading the manual I have learned that the battery is a data-cache... (2 Replies)
Discussion started by: finster
2 Replies
Login or Register to Ask a Question
BATTERY-STATS-COLLECTOR(8)				      System Manager's Manual					BATTERY-STATS-COLLECTOR(8)

NAME
battery-stats-collector - Collect statistics about battery charge SYNOPSIS
battery-stats-collector [option] ... DESCRIPTION
Does exactly as it says on the tin - it will collect information from the APM subsystem and write it to a log file. Normally battery-stats-collector will be invoked by the system startup scripts. OPTIONS
battery-stats follow the usual GNU command line syntax, with long options starting with two dashes (`-'). -V, --version Show version of battery-stats-collector and exit. -h, --help Show summary of options and exit. -s, --syslog Log error messages to syslog, rather than stderr. Note that messages regarding invalid command line parameters will still go to stderr. -o filename, --output filename Append statistics to the given file. The default filename is /var/log/battery-stats -1, --once Only collect a single sample and exit. The default is to loop continiously. -i seconds, --interval=seconds Sampling intervals in seconds. If not specified, stats will be collected every 30 seconds. -I, --ignore-missing-battery Keeps quiet about missing batteries. This stops the warnings on stderr/syslog that would otherwise occur when the battery is miss- ing. -F samplecount, --flush=samplecount Flushes data to the logfile every <samplecount> samples. A value of zero turns off flushing altogether. If left unspecified, bat- tery-stats-collector will assume a value of 1, i.e. flush at every write. Setting the value too low will tend to keep the disk spinning (and use battery needlessly). Setting the value too high will loose statistics in case of an improper shutdown. Note that since battery-stats-collector uses the standard Ansi C library, data will still be flushed periodically (regardless of this setting) once the buffer fills up. The size of the buffer is platform dependent, but 4Kb and 8Kb seem pretty normal. FILES
/var/log/battery-stats Default file for writing battery charge samples to. SEE ALSO
battery-graph(1) Newer versions of this program may (or may not) be available at http://karl.jorgensen.com/battery-stats AUTHOR
This manual page was written by Karl E. Jorgensen <karl@jorgensen.com>, for the Debian GNU/Linux system (but may be used by others). September 18, 2002 BATTERY-STATS-COLLECTOR(8)