| Title: | HSJ30/40 Product Conference |
| Moderator: | SSDEVO::EDMONDS |
| Created: | Mon Jul 12 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1264 |
| Total number of notes: | 4958 |
I noticed that V3.1J-0 of the hsof that has shipped to customers
has the CACHE_UPS option available. It is not documented in the release
notes that shipped with the the program card or the user/service guide
that ship with the card.
If you set the controller to CACHE_UPS you no
longer get the battery status. Is there any way to check the battery
via the cli when you set CACHE_UPS? If not then I assume you don't get
a message if the battery goes bad. It would be nice to be able to run
in CACHE_UPS but still be able to check the condition of the battery.
Joe
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1253.1 | Not supported | SSDEVO::RMCLEAN | Tue May 20 1997 10:32 | 2 | |
No and... We do NOT support CACHE_UPS switch on 40's that is why it is not documented. | |||||
| 1253.2 | not supported??? | TOPTEN::AVERBACH | Tue May 20 1997 12:27 | 4 | |
Simple question....so why is it there????
| |||||
| 1253.3 | TOPTEN::AVERBACH | Tue May 20 1997 15:05 | 12 | ||
I guess I can figure out why it is not supported. There are no
leds to tell wether the batteries are charged or not (unlike the
hsx50). So then I assume there is now way to tell if a battery is good
or bad short of set nocache_ups which requires a reboot.
Unfortunately if you get a customer or some fs guy (such as myself) who
has hsx50's and is aware of the cacheups and has suffered thru several
bad battery experiences they may set it without thinking about the
consequences.
Call me guilty,
Joe
| |||||
| 1253.4 | Yup good guess you got most of it | SSDEVO::RMCLEAN | Thu May 22 1997 12:07 | 1 | |
You are getting warm ;-.]... There are too many possiblities for abuse. | |||||
| 1253.5 | More CACHE_UPS | TOPTEN::AVERBACH | Tue May 27 1997 13:15 | 24 | |
Now that I have set CACHE_UPS on several HSJ40's and have not had
the oppurtunity to set NOCACHE_UPS, I assumed that I would not be able
to tell if there was a battery failure, at least by our dialogue in the
previous entries. However, this weekend one of the HSJ40's starting
logging the following instance code 02052301 and the following last
fail code 010B2380. Both of these say that the cache battery is failed
or low. The batteries were replaced and all appears well.
So what good would CACHE_UPS do you if the controller is going to
restart it self anyway?
Is there some amount of time involved where you would get the instance
code before the last fail/controller restart?
Lastly, since there is some mechanism to notify you of a battery
failure then why isn't CACHE_UPS supported?
Thanks,
Joe
restart?
| |||||