System Controller battery (BATTERY at SC/BAT/V_BAT has exceeded low warning) failure in T-series servers.

Yogesh Raheja

Yogesh working as a Consultant in Unix Engineering by profession. And he has multiple years experience in Solaris, Linux , AIX and Veritas Administration. He has been certified for SCSA9, SCSA10, SCNA10, VXVM, VCS, ITILv3. He is very much passionate about sharing his knowledge with others. Specialties: Expertize in Unix/Solaris Server, Linux (RHEL), AIX, Veritas Volume Manager, ZFS, Liveupgrades, Storage Migrations, Cluster deployment (VCS and HACMP) and administration and upgrade on Banking, Telecom, IT Infrastructure, and Hosting Services.

Loading Facebook Comments ...

5 Responses

  1. Gaurav says:

    good Article, It will help in daily routine for replacing battery on many Solaris boxes.

    we can also see output of failed battery in prtdiag -v also

  2. Yogesh Raheja says:

    Hi Gaurav, nopes you cant see the error in prtdiag. But you will be able to see the error messages in /var/adm/messages.

  3. Vinit garg says:

    Hi,here i have one confusion, After poweron the server when we execute uptime it shows 4631 days,Now my question is from where uptime command getting this info,Isn’t it getting this info from SC card & what exactly happened after reboot that it started showing correct time.Also if we are using NTP then we shouldn’t set time in server it will automatically will be in sync when OS will be up.Please explain

  4. Ramdev says:

    Hi Vinit, every machine , at motherboard level, will a hardware system clock supported by a battery.  

               Whenever we first install the machine ( i mean hardware), the system hardware clock will keep tickining-on as long as the supporting battery alive. And during the time ,  if there is an OS configured on that machine, OS uses the hardware clock time as OS time. And whenever  we  power-on / shutdown the system, the OS will log the time in the internal OS logs….. Uptime actually calculates the time by comparing the current time with the actual boot time ( logged inside the wtmpx). 

    >> when the network operating systems like windows/solaris/linux configured as ntp clients, during their boot they will pick up the ntp  time and will set their current time to ntp server time, instead of using hardware clock. 

  5. Vinit garg says:

    Ram still confused….:(:(
    Let’s take step by step,Suppose at 10pm I run poweroff -y ,Now as per Your saying OS will log the 10pm timing info in it’s wtmpx file .
    Suppose It took 1 hr to replace the battery & at 11pm I execute poweron -c then again as soon as OS will come up it will log the 11pm timing info in it’s wtmpx file So when we will run uptime then it must show it’s correct timing as wtmpx is now updated..

Leave a Reply

Your email address will not be published.

[contact-form to='' subject='New Learning Request Submitted'][contact-field label='Name' type='name' required='1'/][contact-field label='Email' type='email' required='1'/][contact-field label='Learning Request' type='textarea' required='1'/][contact-field label='Are you Looking for ' type='radio' required='1' options='Paid Training,Free Training'/][/contact-form]

What is your Learning Goal for Next Six Months ? Talk to us