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 till then my database instance get crashes. so i want to confirm from my machines that whether fiber cards is ok. i usually use
Code:
fcinfo hba-port
it always connected and says online
plz guide what else should i check , any commands etc
regards
Moderator's Comments:
It is a bit hard to understand your post when you do not check your spelling . Please use your in browser spell checker before posting.
Hi all,
I have a compatibly issues with a new hardware
My config is the following one :
Solaris 10
V490 Hardware
2 X HBA Qlogic 2310f cards
An HP EVA 5000 for storage ...
Veritas VxVM 4.1 MP1
When I reboot my server, VxVM is trying to mount/use the volume before it's... (0 Replies)
I need information what maximum error level on FC card need clasification of critical level (SAN mass storidge)
Please write screenshot from utility fcutil whith test option.
Pawel (0 Replies)
Hi,
I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine.
The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards.
Can anyone suggest how to determine my HBA hardware ?
Thanks,
Ron.
... (3 Replies)
Hi,
I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine.
The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards.
Can anyone suggest how to determine my HBA hardware ?
Thanks,
Ron.
... (4 Replies)
I installed a FC array for the first time and everything looks OK
in mpathadm, cfgadm, but I don't know what to do next.
# stmsboot -L
non-STMS device name STMS device name
------------------------------------------------------------------
/dev/rdsk/c2t1d0 ... (3 Replies)
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)
Hello,
I am trying to set up Channel Bonding on a RHEL6 Virtual Box VM. I have 2 ethernet cards on the machine which are set up in Internal Network mode. I followed all the steps exactly as mentioned in the RHEL6 deployment Guide, but for some reason i think results are not correct. Here are my... (13 Replies)
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:
{0} ok setenv auto-boot? false
auto-boot? = false
{0} ok reset-all
SPARC T3-1B,... (10 Replies)
Discussion started by: fretagi
10 Replies
LEARN ABOUT NETBSD
isp
ISP(4) BSD Kernel Interfaces Manual ISP(4)NAME
isp -- Qlogic based SCSI and FibreChannel SCSI Host Adapters
SYNOPSIS
isp* at pci? dev? function? (PCI)
isp* at sbus? slot ? offset ? (SBus)
scsibus* at isp?
DESCRIPTION
This driver provides access to SCSI or FibreChannel devices.
SCSI features include support for Ultra SCSI and wide mode transactions for SCSI, and LVD (for the ISP1080 and ISP1280),
Fibre Channel support uses FCP SCSI profile for FibreChannel. and uses Class 3 connections only. Support is available for Public and Pri-
vate loops. Command tagging is supported for all (in fact, FibreChannel requires tagging).
CONFIGURATION
An optional flags 0x80 appended to the above isp* declarations will disable the download of driver firmware, which means you use whatever
firmware is running on the card. If no firmware is running on the card, the driver cannot operate the card.
An optional flags 0x40 appended to the above isp* declarations (can be OR'd in with the other config flags option) will keep the driver from
looking at device or bus NVRAM settings (this is in case NVRAM is just wrong and you have the card in a platform where it is inconvenient to
change NVRAM settings on the card).
HARDWARE
Supported cards include:
ISP1000
SBus Fast Wide, Ultra Fast Wide cards, Single Ended or Differential cards.
PTI SBS440
Performance Technology ISP1000 variants.
ISP1020
Qlogic 1020 Fast Wide and Differential Fast Wide PCI cards.
ISP1040
Qlogic 1040 Ultra Wide and Differential Ultra Wide PCI cards.
PTI SBS450
Performance Technology ISP1040 variants.
Qlogic 1240
Qlogic 1240 Dual Bus Ultra Wide and Differential Ultra Wide PCI cards.
Qlogic 1080
Qlogic 1280 LVD Ultra2 Wide PCI cards.
Qlogic 1280
Qlogic 1280 Dual Bus LVD Ultra2 Wide PCI cards.
Qlogic 2100
Qlogic 2100 and 2100A Copper and Optical Fibre Channel Arbitrated Loop
Qlogic 2102
Qlogic Dual Loop 2100A Optical Fibre Channel Arbitrated Loop PCI cards.
Qlogic 2200
Qlogic 2200 Copper and Optical Fibre Channel Arbitrated Loop PCI cards.
Qlogic 2202
Qlogic 2200 Dual Bus Optical Fibre Channel Arbitrated Loop PCI cards.
Qlogic 2204
Qlogic 2200 Quad Bus Optical Fibre Channel Arbitrated Loop PCI cards.
Qlogic 2300
Qlogic 2300 2-Gigabit Optical Fibre Channel PCI cards.
Qlogic 2312
Qlogic 2300 2-Gigabit Dual Channel Optical Fibre Channel PCI cards.
PTI SBS470
Performance Technology ISP2100 variants.
Antares P-0033
Antares Microsystems ISP2100 variants.
Qlogic 2400
Qlogic 2400 4-Gigabit Optical Fibre Channel PCI cards.
Qlogic 2500
Qlogic 2500 8-Gigabit Optical Fibre Channel PCI cards.
SEE ALSO cd(4), intro(4), scsi(4), sd(4), st(4)AUTHORS
The isp driver was written by Matthew Jacob for NASA/Ames Research Center.
BUGS
The driver currently ignores some NVRAM settings.
The driver currently doesn't do error recovery for timed out commands very gracefully.
Sometimes, when booting, the driver gets stuck waiting for the Fibre Channel firmware to tell it that the loop port database is ready. In
this case you'll see an announcement that the loop state has a value of 0x1. To unwedge the system, unplug and replug the fibre channel con-
nection, or otherwise cause a LIP (Loop Initialization Primitive sequence) - this will kick the firmware into getting unstuck.
BSD June 24, 2009 BSD
01-23-2020
