Sponsored Content
Operating Systems Solaris Connect Solaris 10 to NetApp filer using Emulex single port HBAs. Post 302244630 by gwhelan on Wednesday 8th of October 2008 10:04:55 AM
Old 10-08-2008
Hi Pupp,

Thanks for your reply. I have worked through the documentation which was really helpful. My problem now is that lptuil does not recognise the two HBAs I have installed. When I run the lputil utility it returns nothing. My system does see the devices. I have run the utility /opt/EMLXemlxu/bin/emlxdrv. Below is what it sees. Because both the HBA's are LP11000-S, I cannot bind the lpfc driver to that device. They can only use the emulex driver.



lpfc fd00 no no no LP11000 and LP11002
lpfc fe00 no no no LPe11000,LPe11002 and LPe11004
emlxs fc10 yes no yes LP11000-S and LP11002-S (emlxs only)

emlxdrv> set_lpfc fc10

ERROR: lpfc cannot bind to a Sun device (fc10).

I now need to know how to configure this HBA (LP11000-S) for persistent bindings to a NetApp filer? Any ideas?

Thanks.
 

9 More Discussions You Might Find Interesting

1. Solaris

Use DFM Netapp 3.01 R1 on Solaris 8

I have this problem when i integrate a new san switch in DFM 3.01 R1 : dfm fcswitch add switchname1 Error: Host switchname2 (11197) already exists. switchname2 is a similar san switch but in another fabric, switchname2 is already integrated in DFM database. Bests Regards Olivier (2 Replies)
Discussion started by: omainfroy
2 Replies

2. Solaris

emulex card on solaris 9

Hello, I am new on solaris. We will connect our sun solaris system to the SAN and add 2 Emulex card on the system (solaris 9). Who have already done this and can give me the procedure to follow ? driver to install multipath etc... Thanks in advance Emmanuel (1 Reply)
Discussion started by: emma32
1 Replies

3. UNIX for Advanced & Expert Users

Solaris 10 x86_64 - Emulex Fibrechannel drivers

Hello! I'm having problems to install Emulex fibrechannel card drivers to a HP DL580 G5 running Solaris 10 x86_64. Any of you guys had this problem or knows the answer? =) cfgadm gives me the following info, which seems to say that it is ok? But the card has'nt logged into the switch... (0 Replies)
Discussion started by: Esaia
0 Replies

4. Solaris

Netapp filer LUN Resize. Commands to run on Solaris afterwards.

Hi, I need to increase a veritas filesystem I have currently mounted on a Solaris 10 server. We can resize the LUN on the NetApp filer no problem. What I need to know is what do I do next on the Solaris 10 server I have so that it will see the increase in size. Do I run 'devfsadm' to... (3 Replies)
Discussion started by: gwhelan
3 Replies

5. Solaris

Can't see Netapp LUN on Solaris using LPFC after reboot.

Hi, I've just edited this post. I found the solution for this. Thanks. (0 Replies)
Discussion started by: gwhelan
0 Replies

6. Solaris

Solaris 10 / NetApp volumes - Forbidden: You don't have permission to access...

Hi all We have a couple of solaris zones running a jboss app in a cluster. Each zone has a shared netapp volume mounted to /app/xxx with everything under that subdir apart from jboss which is local to each zone in /app/jboss-3.2.5 There is a symlink in /app/xxx/jboss-3.2.5 which points to... (0 Replies)
Discussion started by: skewbie
0 Replies

7. Solaris

Netapp filer details - command?

What command can I use to find out details about a netapp filer. I have a directory that is a filer i would like to know details about the source host/folder that it points to. Thanks. (2 Replies)
Discussion started by: jjohnson
2 Replies

8. Solaris

How to mount a NetApp snapshoot to a Solaris server?

Hi I have NetApp lun, that was mounted on server as a file system that failed, and that server is no longer in use, but I would like to use that file system on another server. The NetApp Admin, told me he can present that lun to my other system, but my problem is how to mount it? Because that... (8 Replies)
Discussion started by: fretagi
8 Replies

9. Solaris

Solaris 10 installing on Cisco UCS doesn't see HBAs

The chassis config is right... this blade can boot to VMware ESXi and see HBAs and LUNs. Solaris isn't seeing the HBAs at all... luxadm probe returns ERROR: No Fibre Channel Adapters found. fcinfo hba-port -l returns No Adapters Found. prtdiag -v gets me: ==== Upgradeable Slots... (3 Replies)
Discussion started by: jnojr
3 Replies
sata(7D)							      Devices								  sata(7D)

NAME
sata - Solaris SATA framework DESCRIPTION
Serial ATA is an interconnect technology designed to replace parallel ATA technology. It is used to connect hard drives, optical drives, removable magnetic media devices and other peripherals to the host system. For complete information on Serial ATA technology, visit the Serial ATA web site at http://www.serialata.org. Up to 32 SATA devices may be plugged directly to each SATA HBA supported by the Solaris SATA framework. The actual number of pluggable devices my be lower, and is limited by a number of device ports on the SATA HBA. The maximum data rate is either 1.5Gb/sec. or 3.0Gb/sec., depending on the capability of a SATA device and SATA HBA controller. The Solaris SATA framework adheres to the Serial ATA 1.0a specification and supports SATA-2 signaling speed 3.0Gb/sec. SATA devices that are connected to SATA HBAs controlled by a SATA framework-compliant HBA driver are treated by the system as SCSI devices. The Solaris SCSI disk driver (sd(7D)) is attached as a target driver for each device node created by the SATA framework. You can use the cfgadm(1M) utility to manage hot plugged and unplugged SATA devices. FILES
/kernel/misc/sata 32-bit ELF kernel module (x86). /kernel/misc/amd64/sata 64-bit ELF kernel module (x86). ATTRIBUTES
See attributes(5) for descriptions of the following attribute: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |x86 | +-----------------------------+-----------------------------+ |Availability |SUNWckr | +-----------------------------+-----------------------------+ SEE ALSO
cfgadm(1M), prtconf(1M), cfgadm_sata(1M), attributes(5), ahci(7D), marvell88sx(7D), nv_sata(7D), sd(7D), si3124(7D) Serial ATA 1.0a Specification -- Serial ATA International Organization. Serial ATA II (Extension to Serial ATA 1.0.a.) -- Serial ATA International Organization. http://www.sun.com/io DIAGNOSTICS
The messages described below may appear on the system console as well as being logged. All messages are presented in one of the following formats and are followed by the diagnostic message: sata: WARNING: <controller/devices/.. path>: or: sata: NOTICE: <controller/devices/.. path>: ...where <controller/devices/.. path> identifies a specific SATA HBA issuing a diagnostic message shown below. SATA port X: link lost. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been lost. SATA port X: link established. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been established. SATA port X: device reset. The device plugged to the specified SATA device port has been reset. The reset may be due to a communication or command error, command timeout, or an explicit request from the host. SATA port X failed. The specified SATA device port failed and is in an unusable state. You can change the port state by deactivating the port and activat- ing it again using cfgadm SATA hardware-specific commands (see cfgadm_sata(1M)). SATA port X error. An error was detected in specified SATA device port operations. SATA device detached at port X. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been lost and could not be re-established. The SATA framework assumes that the device is unplugged from the specified SATA device port. SATA device detected at port X. Communication( via serial link) between the HBA and the device plugged to the specified empty SATA device port has been established. The SATA framework assumes that the new device is plugged to the specified SATA device port. SATA disk device at port X. This message is followed by a disk description specifying the disk vendor, serial number, firmware revision number and the disk capa- bilities. SATA CD/DVD (ATAPI) device at port X. This message is followed by a SATA CD/DVD description specifying the DVD vendor, serial number, firmware revision number and the DVD capabilities. SATA device at port X cannot be configured. Application(s) accessing previously attached device have to release it before newly inserted device can be made accessible. The port cannot be configured because there is application using the previous attached device, so the application must release it, then the newly inserted device can be configured. Application(s) accessing previously attached SATA device have to release it before newly inserted device can be made accessible. The target node remained and it belongs to a previously attached device. This happens when the file was open or the node was waiting for resources at the time the associated device was removed. Instruct event daemon to retry the cleanup later. sata: error recovery request for non-attached device at cport X. When error recovery is requested, the device is not yet attached. SATA device at port X will not be power-managed. When property "pm-capable" on the target device node setting fails, the SATA device won't be power-managed. SATA disk device at port X does not support LBA. The disk device plugged into specified SATA device port does not support LBA addressing and cannot be used. Cannot identify SATA device at port X - device will not be attached. IDENTIFY (PACKET) DEVICE data cannot be retrieved successfully after the device is attached to the SATA port. sata: <HBA driver name><instance number>:hba attached failed. The SATA HBA instance attach operation failed. This HBA instance cannot be configured and is not available. sata: invalid ATAPI cdb length<command cdb length>. The length of the command cdb is greater than that the device can support. sata: invalid sata_hba_tran version X for driver <HBA driver name>. The specified SATA HBA driver and the SATA framework are incompatible. The driver cannot attach and SATA HBAs controlled by this driver (and devices plugged to this SATA HBA ports) are not available. sata_hba_attach: cannot create SATA attachment point for port X. The specified SATA device port cannot be configured in the system and a device plugged to this port could not be not be configured and used. sata_create_target_node: cannot create target node for device at port X. The device target node for the device plugged to the specified SATA device port could not be created. As a result, the device cannot be configured and used. SunOS 5.11 5 Sep 2007 sata(7D)
All times are GMT -4. The time now is 05:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy