12-20-2016
2540-M2 Firmware
Hi all,
Does anyone know how to upgrade the controller firmware on a storagetek 2540-M2 Array?
Thanks in advance
Martin
10 More Discussions You Might Find Interesting
1. Solaris
We're moving our production 3510FC to development, so we need to replace the production 3510FC. The 6140 is nice, but pricey.
Here's the question: Would two 2540's (RAID 10) be 'faster' than one 3510? (RAID 10) and faster than one 6140 (RAID 10)?
One StoregeTek 6140 (16x72GB 15k rpm fc-al... (12 Replies)
Discussion started by: buddhavelvet
12 Replies
2. Solaris
I can't seem to get my host to see a 2540 array.
I have 3 arrays right now. (2) 2540's.. let's call them 2540A and 2540B and (1) 6140. 2540A and the 6140 are configured and mounted on the same linux host.
For the life of me, I cannot get the other problem-child 2540B to be recognized by the... (6 Replies)
Discussion started by: buddhavelvet
6 Replies
3. Solaris
Hi,
I have a simple question on how to correctly disable the matrix?
Looking for the Common Array Manager and I do not see this option...
Thank for help (3 Replies)
Discussion started by: bieszczaders
3 Replies
4. Solaris
Hi peeps,
Was wondering if anyone can help me, got a couple of storagetek 2540's that I need to configure. Trouble is I think they were brought as second user as all that came with them was cables.
Does anyone know how to configure them (i.e. create raid sets and map to Luns and present... (1 Reply)
Discussion started by: callmebob
1 Replies
5. Hardware
Hello all !
I am a beginner about system and networking , and after some research on internet , i didn't find any relevant information , so i post here , if someone have an experience with this kind of material or if some documentation about how to connect my storage device on my server.
I... (2 Replies)
Discussion started by: acorradi
2 Replies
6. Hardware
Hi all,
My Sun StorageTek 2540 have redundant batteries, but a battery was failed.
# /opt/SUNWstkcam/bin/sscs list -d MyStorage1 fru
Name FRU Alarm State Status Revision Unique Id
-------------------------- ----------- --------... (2 Replies)
Discussion started by: buyantugs
2 Replies
7. Hardware
Hi Guys and Gals,
Wionder if you could help me, got a problem with a controller on a storagetek 2540, dead when fully powered up but if you reboot, it is ok for a couple of seconds (and you can ping it). Then once the array is fully up, it goes faulty and is un-pingable.
Had anyone... (4 Replies)
Discussion started by: callmebob
4 Replies
8. Hardware
Hi Guys and Gals,
does anyone know how to update the firmware on the drives in a storagetek 2540?
Thanks in advance
Rgrds
Martin (0 Replies)
Discussion started by: callmebob
0 Replies
9. Solaris
Bought a Sun StorageTek 2540 SAN array a few years ago from a company that was going out of business. When we first set it up, we were able to get all the software (Common Array Manager) and firmware directly from Sun.
We just upgraded the drives, but the array is too large for the firmware. Now... (6 Replies)
Discussion started by: edison303
6 Replies
10. Solaris
Hello Dears,
My server hots cannot contacted my array disk 2540 by using out-of-band Ethernet Cable.
The Controller Ethernet port is off , I replace the ethernet cable but not OK
I reboot the server and the Array disk 2540 but Not OK.
Please somebody know how to solve this issue?
... (1 Reply)
Discussion started by: ghislino
1 Replies
LEARN ABOUT NETBSD
firmware_free
FIRMLOAD(9) BSD Kernel Developer's Manual FIRMLOAD(9)
NAME
firmload -- Firmware loader API for device drivers
SYNOPSIS
#include <dev/firmload.h>
int
firmware_open(const char *drvname, const char *imgname, firmware_handle_t *fhp);
int
firmware_close(firmware_handle_t fh);
off_t
firmware_get_size(firmware_handle_t fh);
int
firmware_read(firmware_handle_t fh, off_t offset, void *buf, size_t size);
void *
firmware_malloc(size_t size);
void
firmware_free(void *buf, size_t size);
DESCRIPTION
firmload provides a simple and convenient API for device drivers to load firmware images from files residing in the file system that are nec-
essary for the devices that they control. Firmware images reside in sub-directories, one for each driver, of a series of colon-separated
path prefixes specified by the sysctl variable hw.firmware.path.
FUNCTIONS
The following functions are provided by the firmload API:
firmware_open(drvname, imgname, fhp)
Open then firmware image imgname for the driver drvname. The path to the firmware image file is constructed by appending the string
``/drvname/imgname'' to each configured path prefix until opening the firmware image file succeeds. Upon success, firmware_open()
returns 0 and stores a firmware image handle in the location pointed to by fhp. Otherwise, an error code is returned to indicate the
reason for failure.
firmware_close(fh)
Close the firmware image file associated with the firmware handle fh. Returns 0 upon success or an error code to indicate the reason
for failure.
firmware_get_size(fh)
Returns the size of the image file associated with the firmware handle fh.
firmware_read(fh, offset, buf, size)
Reads from the image file associated with the firmware handle fh beginning at offset offset for length size. The firmware image data
is placed into the buffer specified by buf. Returns 0 upon success or an error code to indicate the reason for failure.
firmware_malloc(size)
Allocates a region of wired kernel memory of size size. Note: firmware_malloc() may block.
firmware_free(buf, size)
Frees a region of memory previously allocated by firmware_malloc().
SEE ALSO
autoconf(9), malloc(9), vnsubr(9)
HISTORY
The firmload framework first appeared in NetBSD 4.0.
AUTHORS
Jason Thorpe <thorpej@NetBSD.org>
BSD
January 17, 2006 BSD