Sponsored Content
Operating Systems Solaris Server M4000 server lost connectivity to storagetek 2540 Post 302865353 by hicksd8 on Friday 18th of October 2013 08:04:05 AM
Old 10-18-2013
The first thing to try is to re-seat the Fibre Channel cables between the StorageTek and the Sun.

Next, can you connect to the StorageTek console to check that it's alive?
 

10 More Discussions You Might Find Interesting

1. Solaris

Sun Sparc T2000 + StorageTek 2540 - Help, I'm lost

I have a Sun Sparc T2000 (Solaris 10 05-08) and have installed a PCI-X 4GB Single Port HBA card in it. I have one StorageTek 2540 array that I would like to connect to the T2000. For the moment it would be a single path connection, but I've ordered a 2nd HBA, so eventually it would be... (4 Replies)
Discussion started by: soliberus
4 Replies

2. Solaris

One StorageTek 6140 vs Two (2) 2540 's?

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

3. UNIX for Dummies Questions & Answers

Help with restarting SUN m4000 server

I'm trying to power on our SUN m4000 server after a recent shutdown. When I try to connect to the xscf console I'm getting prompted for a password. The system is not asking for a login just a password. Below is the output from the xscf console. Anyone know how I can safely get back to the... (0 Replies)
Discussion started by: orahi001
0 Replies

4. Solaris

Sun StorageTek 2540 - shutdown matrix

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

5. Solaris

Storagetek 2540

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

6. Hardware

Storagetek 2540

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

7. Solaris

M4000 Server Issue

Dear Team, This time i am facing some problems in Sun SPARC M4000 server. I have a doubt, when we are upgrading the firmware if XSCF , the OBP is also upgraded. What about server OBP, Is that upgardation need to be done separately ? what about DVD-ROM, HARD DISK firmware.... (3 Replies)
Discussion started by: sudhansu
3 Replies

8. Hardware

StorageTek 2540 battery failed

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

9. Hardware

Storagetek 2540

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

10. Solaris

StorageTek 2540 SAN array

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
usoc(7D)							      Devices								  usoc(7D)

NAME
usoc - universal serial optical controller for Fibre Channel arbitrated loop (SOC+) device driver DESCRIPTION
The Fibre Channel adapter is an SBus card that implements two full duplex Fibre Channel interfaces. Each interface can connect to a Fibre Channel arbitrated loop (FC-AL). The usoc device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL. FILES
/kernel/drv/usoc 32-bit ELF kernel module /kernel/drv/sparcv9/usoc 64-bit ELF kernel module ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ |Interface stability |Unknown | +-----------------------------+-----------------------------+ |Availability |SUNWusoc | +-----------------------------+-----------------------------+ SEE ALSO
fctl(7D), sbus(4), fcp(7D), fp(7D), ssd(7D) Writing Device Drivers Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994 Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996 Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998 Fabric Channel Loop Attachment (FC-FLA), NCITS TR-20:1998 DIAGNOSTICS
The following messages are logged and may also appear on the system console. On the console these messages are preceded by: usoc%d: where usoc%d: is the per-port instance number of the usoc controller. Fibre Channel is ONLINE The Fibre Channel loop is now online. Fibre Channel Loop is ONLINE The Fibre Channel loop is now online. Fibre Channel Loop is OFFLINE The Fibre Channel loop is now offline. attach failed: device in slave-only slot. Move soc+ card to another slot. attach failed: alloc soft state. Driver did not attach, devices will be inaccessible. attach failed: bad soft state. Driver did not attach, devices will be inaccessible. attach failed: unable to map eeprom Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to map XRAM Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to map registers Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to access status register Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to install interrupt handler Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible. attach failed: unable to access host adapter XRAM Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to write host adapter XRAM Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: read/write mismatch in XRAM Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. SunOS 5.10 20 Jul 1999 usoc(7D)
All times are GMT -4. The time now is 02:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy