Fibre channel link down on booting Solaris server


 
Thread Tools Search this Thread
Operating Systems Solaris Fibre channel link down on booting Solaris server
# 8  
Old 07-23-2018
It does not boot in any of them:

for disk0, just stays like below

Code:
{0} ok boot disk0
Boot device: /pci@400/pci@1/pci@0/pci@2/@0/disk@p0  File and args:

for disk disk1 :
Code:
 ok boot disk1
Boot device: /pci@400/pci@1/pci@0/pci@2/@0/disk@p1  File and args:
ERROR: boot-read fail


Can't locate boot device

for disk2

Code:
{0} ok boot disk2
Boot device: /pci@400/pci@1/pci@0/pci@2/@0/disk@p2  File and args:
ERROR: boot-read fail


Can't locate boot device

and for disk3

Code:
{0} ok boot disk3
Boot device: /pci@400/pci@1/pci@0/pci@2/@0/disk@p3  File and args:
ERROR: boot-read fail


Can't locate boot device

{0} ok

# 9  
Old 07-23-2018
So none of those disks are bootable.

Did the system boot via the FC link which is now down?

Do you know from which disk it should boot?

It is possible that the proper boot disk is local disk0 which has sustained filesystem damage during the power cut. You may need to boot from DVD and fsck this filesystem. If that doesn't work you may need to recover some files from backup. It is likely that the FC link is down as far as the SC is concerned because Solaris isn't running and the QLogic driver isn't therefore loaded.

Last edited by hicksd8; 07-23-2018 at 01:55 PM..
This User Gave Thanks to hicksd8 For This Post:
# 10  
Old 07-24-2018
Hi

I have logged in at the ILOM management port of this blade and I found a fault, but I dont know if this fault its hardware or software:

I have started the fault management shell:

Code:
-> start /CMM/faultmgmt/shell
Are you sure you want to start /CMM/faultmgmt/shell (y/n)? y

faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
/CH/BL3                                                       degraded
faultmgmtsp> fmadm faulty
------------------- ------------------------------------ -------------- --------
Time                UUID                                 msgid          Severity
------------------- ------------------------------------ -------------- --------
2018-07-11/11:04:55 1a96f137-6015-c606-eaad-f1f971e1caa9 SPX86-8000-1D  Critical

Fault class : fault.chassis.device.fail

FRU         : /CH/BL0
              (Part Number: 541-4197-06)
              (Serial Number: 1005LCB-1126D4037D)

Description : A device necessary to support a configuration is missing.

Response    : The service required LED on the chassis will be illuminated.

Impact      : The chassis may be powered down.

Action      : The administrator should review the ILOM event log for
              additional information pertaining to this diagnosis.  Please
              refer to the Details section of the Knowledge Article for
              additional information.

------------------- ------------------------------------ -------------- --------
Time                UUID                                 msgid          Severity
------------------- ------------------------------------ -------------- --------
2018-07-12/08:17:34 6114a8ae-b70d-6648-be20-867e12d83674 SPX86-8000-1D  Critical

Fault class : fault.chassis.device.fail

FRU         : /CH/BL3
              (Part Number: 541-4197-06)
              (Serial Number: 1005LCB-1126D4037P)

Description : A device necessary to support a configuration is missing.

Response    : The service required LED on the chassis will be illuminated.

Impact      : The chassis may be powered down.

Action      : The administrator should review the ILOM event log for
              additional information pertaining to this diagnosis.  Please
              refer to the Details section of the Knowledge Article for
              additional information.

faultmgmtsp>

/CH/BL3, its the server with this issue.

I have run a few commands:

Code:
-> show faulty
Target              | Property               | Value
--------------------+------------------------+---------------------------------
/CMM/faultmgmt/0    | fru                    | /CH/BL0
/CMM/faultmgmt/0/   | class                  | fault.chassis.device.fail
 faults/0           |                        |
/CMM/faultmgmt/0/   | sunw-msg-id            | SPX86-8000-1D
 faults/0           |                        |
/CMM/faultmgmt/0/   | uuid                   | 1a96f137-6015-c606-eaad-f1f971e1
 faults/0           |                        | caa9
/CMM/faultmgmt/0/   | timestamp              | 2018-07-11/11:04:55
 faults/0           |                        |
/CMM/faultmgmt/0/   | detector               | /CH/BL0/ERR
 faults/0           |                        |
/CMM/faultmgmt/0/   | fru_part_number        | 541-4197-06
 faults/0           |                        |
/CMM/faultmgmt/0/   | fru_serial_number      | 1005LCB-1126D4037D
 faults/0           |                        |
/CMM/faultmgmt/0/   | chassis_serial_number  | 1126BD0E75
 faults/0           |                        |
/CMM/faultmgmt/1    | fru                    | /CH/BL3
/CMM/faultmgmt/1/   | class                  | fault.chassis.device.fail
 faults/0           |                        |
/CMM/faultmgmt/1/   | sunw-msg-id            | SPX86-8000-1D
 faults/0           |                        |
/CMM/faultmgmt/1/   | uuid                   | 87864a2c-e6f7-ecad-a1cb-c75349fa
 faults/0           |                        | 0735
/CMM/faultmgmt/1/   | timestamp              | 2018-07-23/15:44:44
 faults/0           |                        |
/CMM/faultmgmt/1/   | detector               | /CH/BL3/ERR
 faults/0           |                        |
/CMM/faultmgmt/1/   | fru_part_number        | 541-4197-06
 faults/0           |                        |
/CMM/faultmgmt/1/   | fru_serial_number      | 1005LCB-1126D4037P
 faults/0           |                        |
/CMM/faultmgmt/1/   | chassis_serial_number  | 1126BD0E75
 faults/0           |                        |

->

I also run some repaired commands:

Code:
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
/CH/BL3                                                       degraded
faultmgmtsp> fmadm repaired /CH/BL3
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
/CH/BL3                                                       degraded
faultmgmtsp> fmadm repaired /CH/BL3
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
/CH/BL3                                                       degraded
faultmgmtsp> fmadm repair /CH/BL3
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
/CH/BL3                                                       degraded
faultmgmtsp> fmadm repair /CH/BL3
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
faultmgmtsp>
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
/CH/BL3                                                       degraded
faultmgmtsp>

still in degraded mode.

From this I concluded that perhaps the SP (service processor) is faulty and needs to be replaced. But not sure
# 11  
Old 09-28-2018
I guess it's too late for this response,



but I will leave this comment here in case someone is useful


In case of Solaris boot from SAN, for any Storage Brand, is necessary execute additional steps in the OPENBOOT prompt, basically this steps are related to configure the FC HBA at low level, in order to indicate the FC topology and select the boot disk from the HBA level. When you set the ID disk in the HBA level, then the FC link come up.


The steps to config the HBA in the OPENBOOT prompt depend of any HBA brand/model.


There are manuals of Emulex and QLOGIC with this information.


Only to put a short example, for EMULEX.


NOTE *****
This is just a fragment of the manual, please review the complete procedure.



Code:
 
Specify the topology for the target Fibre Channel boot disk:

a.   At the OK> prompt, type the following and press ENTER
" <device path name>" select-dev
(Example: " /pci@1f,4000/lpfc@4" select-dev)
b.   At the OK> prompt, type the appropriate command and press ENTER:
FC-AL: set-fc-al
FC-SW: set-ptp
c.   At the OK> prompt, type unselect-dev and press ENTER

Follow these steps to set the boot device ID:
At the OK> prompt, type
 " /pci@1f,4000/lpfc@4" select-dev and press ENTER.
At the OK> prompt, type the appropriate command and press ENTER:
FC-AL: did  e4  0  2  set-boot-id
FC-SW: wwpn 5006.0482.bbff.4e0f 0 2  set-boot-id

Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Solaris

Issue with Fiber Channel cards in Solaris

hi everone i am experiencing disconnectivity from storage to My database machines. i have doubt on my FC cards in my sparc T4-2 machines. i want to know how should i check from my solaris that whether the cards are ok or not because once the disks get disconnect from SAN so it come back again but... (5 Replies)
Discussion started by: janakors
5 Replies

2. Solaris

Fibre Channel link not ready on Netra 240

Hi, One of my Netra 240 went into hung state and I had to reboot it. I powered it off and tried booting it again but unsuccessful. It is not connected to SAN and have local disks. Not able to boot in failsafe mode too. There are two disks of 72GB, both are mirrored in SVM. It complains about... (5 Replies)
Discussion started by: solaris_1977
5 Replies

3. AIX

[ASK] - AIX Fibre Channel behavior

Hello all, Let me introduce about the context and my environment. We have an AIX 6.1 system, it has 4 FC channels / > lsdev -Cc adapter | grep fcs fcs0 Available 23-T1 Virtual Fibre Channel Client Adapter fcs1 Available 23-T1 Virtual Fibre Channel Client Adapter fcs2 Available 23-T1... (14 Replies)
Discussion started by: Phat
14 Replies

4. Hardware

Fibre Channel HBA recommendations?

We will be buying new Xeon E5-based servers for our datacenter and were wondering which Fibre Channel host bus adapters we should select for these. The choices are Emulex or QLogic (8Gb FC HBAs). Anybody have any recommendations on which is the better choice? Thanks in advance. (1 Reply)
Discussion started by: atahmass
1 Replies

5. Solaris

USCSICMD ioctl calls for Fibre Channel(FC) devices on Solaris 10?

Hi , I have wrtitten a C program that issues USCSICMD ioctl call to the tape devices attached on solaris sparc 10. I was able to get the required information from all SCSI tape devices attached using the utility. But, whenever it is run on FC attached tape drives , the program returns an error... (0 Replies)
Discussion started by: naveen448
0 Replies

6. AIX

Power6 Virtual Fibre Channel Adapter

Hello, Searched in all IBM Redbooks and on the internet and couldn't find anything about the new feature of POWER 6 which Virtual Fibre ( Fiber ) channel adapter. It is similar to virtual scsi adapter. In my client partition I created the virtual Fibre Adapter mapped it with the VIO... (1 Reply)
Discussion started by: filosophizer
1 Replies

7. AIX

Fibre channel drivers on RS/6000 aix 5L

Want to configure IBM raid strorage but the aix 5L cds do not have the drivers for the fibre channels. The machine is RS/6000. I have gone to IBM downlaodable sites but i can't find the drivers? help pliz:mad: (4 Replies)
Discussion started by: Zim-Aix-Guru
4 Replies
Login or Register to Ask a Question

Featured Tech Videos