Fibre channel link down on booting Solaris server Post: 303020012

Sponsored Content

Operating Systems Solaris Fibre channel link down on booting Solaris server Post 303020012 by fretagi on Thursday 12th of July 2018 04:25:32 AM

07-12-2018

Registered User

Fibre channel link down on booting Solaris server

Hi

I had power issue that affected a server, in which I had power ON the server SPARC T1-B3 running solaris 10.
After power on the system stops at ok prompt, them I issued the following commands:

Code:

{0} ok setenv auto-boot? false
auto-boot? =            false
{0} ok reset-all


SPARC T3-1B, No Keyboard
Copyright (c) 1998, 2010, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.32.1, 65024 MB memory available, Serial #98354310.
Ethernet address 0:21:28:dc:c4:86, Host ID: 85dcc486.



{0} ok probe-scsi-all
/pci@400/pci@2/pci@0/pci@4/pci@0/pci@2/SUNW,qlc@0,1
QLogic QEM3572  Host Adapter FCode(SPARC): 3.06  08/19/09
ISP Firmware version 4.06.02
Fibre Channel Link down
Possible causes: No cable, incorrect connection mode or data rate
SFP state: 8Gb Present

/pci@400/pci@2/pci@0/pci@4/pci@0/pci@2/SUNW,qlc@0
QLogic QEM3572  Host Adapter FCode(SPARC): 3.06  08/19/09
ISP Firmware version 4.06.02
Fibre Channel Link down
Possible causes: No cable, incorrect connection mode or data rate
SFP state: 8Gb Present

/pci@400/pci@1/pci@0/pci@7/pci@0/usb@0,2/hub@3/storage@2
  Unit 0   Removable Read Only device    AMI     Virtual CDROM   1.00

/pci@400/pci@1/pci@0/pci@4/pci@0/pci@2/SUNW,qlc@0,1
QLogic QEM3572  Host Adapter FCode(SPARC): 3.06  08/19/09
ISP Firmware version 4.06.02
Fibre Channel Link down
Possible causes: No cable, incorrect connection mode or data rate
SFP state: 8Gb Present

/pci@400/pci@1/pci@0/pci@4/pci@0/pci@2/SUNW,qlc@0
QLogic QEM3572  Host Adapter FCode(SPARC): 3.06  08/19/09
ISP Firmware version 4.06.02
Fibre Channel Link down
Possible causes: No cable, incorrect connection mode or data rate
SFP state: 8Gb Present

/pci@400/pci@1/pci@0/pci@2/LSI,sas@0

FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00

Target 9
  Unit 0   Disk   SEAGATE  ST930003SSUN300G 0B70
  SASDeviceName 5000c50039c1548b  SASAddress 5000c50039c15489  PhyNum 0
Target a
  Unit 0   Disk   SEAGATE  ST930003SSUN300G 0B70
  SASDeviceName 5000c50039bdd4cb  SASAddress 5000c50039bdd4c9  PhyNum 1

{0} ok

So I am not able to boot.
I found it very strange to have these errors because, all I had was a power failure to the blade, and I have managed to power on successfully the other blade on the same chassis

fretagi

View Public Profile for fretagi

Find all posts by fretagi

7 More Discussions You Might Find Interesting

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

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

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

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.

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

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

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

LEARN ABOUT NETBSD

xpci

XPCI(4) 						 BSD/xen Kernel Interfaces Manual						   XPCI(4)

NAME

     xpci -- Xen frontend paravirtualized PCI pass-through driver

SYNOPSIS

     xpci* at xenbus?
     pci* at xpci?

DESCRIPTION

     The xpci driver is the frontend part of the PCI pass-through functionality that can be used by Xen guest domains to communicate with PCI
     devices.

     From a guest point of view, xpci is similar to a pci(4) bus, except that the guest talks with the PCI backend driver instead of the real
     physical device directly.

     When the host domain is NetBSD, the xpci driver is backed by a pciback(4) driver within the dom0.

SEE ALSO

     pci(4), pciback(4), xenbus(4)

HISTORY

     The xpci driver first appeared in NetBSD 5.1.

AUTHORS

     The xpci driver was written by Manuel Bouyer <bouyer@NetBSD.org>.

SECURITY CONSIDERATIONS

     As PCI passthrough offers the possibility for guest domains to send arbitrary PCI commands to a physical device, this has direct impact on
     the overall stability and security of the system.	For example, in case of erroneous or malicious commands, the device could overwrite physi-
     cal memory portions, via DMA.

BSD
								  January 8, 2011							       BSD