Sponsored Content
Operating Systems AIX replacing the battery from the controller in DS4300 Post 302555432 by lo-lp-kl on Wednesday 14th of September 2011 05:48:21 PM
Old 09-14-2011
replacing the battery from the controller in DS4300

I hope this help

I have a similar issue with DS4500.

In this one we have to change 2 batteries but when we open the case there was 4 batteries and we dont have something to know which baterry is bad. Then we have to have all of them.

We dont have problems with the configuration or something else. We can do it online.

There are documentation but im sorry I dont remember the name of the paper. Try google.

Greetings
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

AIX 5.2 and DS4300 Storage

Hello, We're setting up a solution for a group of customers with 2 p520 servers and 1 DS4300 unit with 9 disks (at this stage). The meaning is to create two arrays on the DS4300. Both servers will be connected to the DS4300 unit and to both controllers (e.g. Controller 1 connected to server 1... (0 Replies)
Discussion started by: EricBE
0 Replies

2. Filesystems, Disks and Memory

AIX and DS4300 Storage Unit

Hello, We're setting up a solution for a group of customers with 2 p520 servers and 1 DS4300 unit with 9 disks (at this stage). The meaning is to create two arrays on the DS4300. Both servers will be connected to the DS4300 unit and to both controllers (e.g. Controller 1 connected to server 1... (0 Replies)
Discussion started by: EricBE
0 Replies

3. AIX

DS4300 firmware upgrade with AIX

Hi Guys, It's me again with this unending support of AIX43 ML 9. I finally able to test a migration from SSA to SAN, no problem. One problem, I bought some expansion of DS4300, two arrays. The IBM tech told me that before I can connect to the existing DS4300, I need to upgrade the firmware... (1 Reply)
Discussion started by: itik
1 Replies

4. AIX

Critical error after adding 6 new disks in DS4300

Hello, This morning we have added 6 new disks (73 Gb) to our DS4300, then created a new Array en then created a logical drive, after this was done, teh following error occourd on the last 3 (new)disks: Date/Time: 22-4-08 6:56:26 Sequence number: 5472 Event type: 282D Event category:... (1 Reply)
Discussion started by: topper
1 Replies

5. Solaris

setting up DS4300 SAN on Solaris

Hi Guys, What's the driver I needed for Solaris 8 and Solaris 10 for the DS4300, spark and intel base? It's my first time to setup on Solaris with DS4300, please give me advise on how to make it work fine. Thanks in advance, itik (3 Replies)
Discussion started by: itik
3 Replies

6. Solaris

SE 3510 Battery Issue

Hi everyone, I changed the batteries on 29-Jun-2008 for the storedges. But received error messages from the server today,I used the "-u" option to update the service date information but it syntaticaly fails. Why? Jul 4 12:00:03 auriga SUNWscsdServer: <rctrl8001> The battery on... (3 Replies)
Discussion started by: incredible
3 Replies

7. 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

8. Solaris

SUN 6540 Array with failed controller battery

Can someone point me to a procedure detailing the replacement of a failed battery in a SUN 6540 controller. Or describe the procedure. Thanks (1 Reply)
Discussion started by: USFE
1 Replies

9. AIX

IBM AIX - SAN Storage DS4300 issue

Hi, This is follow up to the post https://www.unix.com/aix/233361-san-disk-appearing-double-aix.html When I connected Pseries Machine HBA Card ( Dual Port ) directly to the SAN Storage DS4300 , I was able to see Host Port Adapter WWN numbers , although I was getting this message... (2 Replies)
Discussion started by: filosophizer
2 Replies
XCHANGEDEVICEDONTPRO(3) 												   XCHANGEDEVICEDONTPRO(3)

NAME
XChangeDeviceDontPropagateList, XGetDeviceDontPropagateList - query or change the dont-propagate-list for extension devices SYNOPSIS
#include <X11/extensions/XInput.h> int XChangeDeviceDontPropagateList( Display *display, Window window, int count, XEventClass *event_list, int mode); XEventClass* XGetDeviceDontPropagateList( Display *display, Window window, int *count); display Specifies the connection to the X server. window Specifies the window whose dont-propagate-list is to be queried or modified. event_list Specifies a pointer to a list of event classes. mode Specifies the mode.You can pass AddToList, or DeleteFromList. count Specifies the number of event classes in the list. DESCRIPTION
The XChangeDeviceDontPropagateList request modifies the list of events that should not be propagated to ancestors of the event window. This request allows extension events to be added to or deleted from that list. By default, all events are propagated to ancestor windows. Once modified, the list remains modified for the life of the window. Events are not removed from the list because the client that added them has terminated. Suppression of event propagation is not allowed for all input extension events. If a specified event class is one that cannot be suppressed, a BadClass error will result. Events that can be suppressed include DeviceKeyPress, DeviceKeyRelease, DeviceButtonPress, DeviceButtonRelease, DeviceMotionNotify, ProximityIn, and ProximityOut. XChangeDeviceDontPropagateList can generate a BadDevice, BadClass, or BadValue error. The XGetDeviceDontPropagateList request queries the list of events that should not be propagated to ancestors of the event window. XGetDeviceDontPropagateList can generate a BadClass or BadWindow error. DIAGNOSTICS
BadDevice An invalid device was specified. The specified device does not exist or has not been opened by this client via XOpenInputDevice. This error may also occur if some other client has caused the specified device to become the X keyboard or X pointer device via the XChangeKeyboardDevice or XChangePointerDevice requests. BadValue Some numeric value falls outside the range of values accepted by the request. Unless a specific range is specified for an argument, the full range defined by the argument's type is accepted. Any argument defined as a set of alternatives can generate this error. BadWindow An invalid window id was specified. BadClass An invalid event class was specified. 05/15/2013 XCHANGEDEVICEDONTPRO(3)
All times are GMT -4. The time now is 05:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy