Sponsored Content
Full Discussion: HBA problem...? at SF V890
Operating Systems Solaris HBA problem...? at SF V890 Post 302461710 by mbah_jiman on Tuesday 12th of October 2010 05:19:36 AM
Old 10-12-2010
HBA problem...? at SF V890

Dear All,

I need your help. I have server like this
SunOS 5.10 Generic_141444-09 sun4u sparc SUNW,Sun-Fire-V890

with messages like this...
Code:
Oct 10 17:07:52  iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x403
Oct 10 17:07:52  scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
Oct 10 17:07:52         Invalid ioctl opcode = 0x403
Oct 10 17:07:54  iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x403
Oct 10 17:07:54  scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
Oct 10 17:07:54         Invalid ioctl opcode = 0x403
Oct 10 17:07:56  iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x403
Oct 10 17:07:56  scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
Oct 10 17:07:56         Invalid ioctl opcode = 0x403
Oct 10 17:07:58  iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x403
Oct 10 17:07:58  scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
Oct 10 17:07:58         Invalid ioctl opcode = 0x403
Oct 11 17:07:52  iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x403
Oct 11 17:07:52  scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
Oct 11 17:07:52         Invalid ioctl opcode = 0x403
Oct 11 17:07:54  iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x403
Oct 11 17:07:55  scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
Oct 11 17:07:55         Invalid ioctl opcode = 0x403
Oct 11 17:07:57  iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x403
Oct 11 17:07:57  scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
Oct 11 17:07:57         Invalid ioctl opcode = 0x403
Oct 11 17:07:59  iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x403
Oct 11 17:07:59  scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
Oct 11 17:07:59         Invalid ioctl opcode = 0x403

So what's problem with my server...??

Best Regards
WisnuSmilie

Last edited by DukeNuke2; 10-12-2010 at 06:48 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

V890 Benefits over V880

Hello, Need to know all benefits\differences for V890 over V880. We are really keen to know about this. Can anybody please take out some time and get us the information. Regards, Narinder (4 Replies)
Discussion started by: narinderd
4 Replies

2. Solaris

Problem installing Solaris on a V890 using flash

I am trying to use a flash image to install a v890. I have the image on another box. I am trying to use ftp to pull down the image. But, when i go though the install, choose flash, enter the ftp info, it can not ever connect to the server. I've never had this trouble before. There are 4... (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

3. Solaris

Installing Solaris 8 on a V890

Question, I have a new V890 preloaded witrh Solaris 10. Due to SW compatibility I need to run Sol 8 on the server. When running boot cdrom from the ok prompt, I get amessages looking for a location on the CDROM to find the startup install SW. The path must be different from what's on Sol 10 install... (4 Replies)
Discussion started by: stocksj
4 Replies

4. UNIX for Advanced & Expert Users

Hardware HBA problem

I have worked with Qlogic (Sun) fiber cards a lot and with Emulex fiber cards only a little. Here is the scenario: I have a Sun 490 with 3 Emulex cards in it. A pair are for the 6120 array that is attached, the other is a direct attach so our SAN for Veritas Netbackup to back up the system.I... (0 Replies)
Discussion started by: lm_admin_dh
0 Replies

5. Solaris

Atached storage to v890 --- very slow

Hello Experts, I have a StorEdge 3320 attached to V890, the problem is that I am copying data from v890's internal hdds to 3320's hdds, it is taking a-lot of time, the transfer is very slow. while I have checked the transfer from V890's internal hdd to another machines it is good. So, its mean... (15 Replies)
Discussion started by: bluetooth
15 Replies

6. Solaris

How to enable hba port of a two port hba card

Hi, i have a two port hba card in solaris 10 system one of which is disabled. How to enable and configure the other port. ---------- Post updated at 08:17 AM ---------- Previous update was at 03:40 AM ---------- please help :( (7 Replies)
Discussion started by: rishiraaz
7 Replies

7. Hardware

boot problem sun V890

hello i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message: Enabling system bus....... Done Initializing CPUs......... Done Initializing boot memory.. RAM-Copy CRC failure!Can't start: No image found FATAL: Can't find/decompress... (0 Replies)
Discussion started by: bahjatm
0 Replies

8. Solaris

v890 cannot boot

I just received a v890. I cannot get it to boot via CDROM nor can I access the SC prompt because I do not know the password. I am attempting to access it via serial cable to a Linux box. What is the best way to proceed? (25 Replies)
Discussion started by: LittleLebowski
25 Replies

9. Solaris

V890 serial console inaccessible

I am battling to get a V890 up and running. The system appears to have AUTOBOOT=false, so no OS comes up when it's powered on, and I do not have the credentials to get to the RSC management console. Output to ttya serial console ends at "Probing I/O buses", I assume because output is then being... (4 Replies)
Discussion started by: dstmark
4 Replies

10. Solaris

Could you run this benchmark? (Especially if you have a V880 or V890)

Hi all I am currently using a T5120 to write and run some simulation code I've been working on which heavily relies on large matrix multiplication procedures. I am posting this to call out for some of you run and share the results of a simple benchmark I've written to compare the matrix... (1 Reply)
Discussion started by: toguro123
1 Replies
ISCSI(4)						   BSD Kernel Interfaces Manual 						  ISCSI(4)

NAME
iscsi -- iSCSI initiator SYNOPSIS
To compile this driver into the kernel, place the following line in the kernel configuration file: device iscsi Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): iscsi_load="YES" DESCRIPTION
The iscsi subsystem provides the kernel component of an iSCSI initiator. The initiator is the iSCSI client, which connects to an iSCSI tar- get, providing local access to a remote block device. The userland component is provided by iscsid(8) and both the kernel and userland are configured using iscsictl(8). The iscsi subsystem is responsible for implementing the "Full Feature Phase" of the iSCSI protocol. SYSCTL VARIABLES
The following variables are available as both sysctl(8) variables and loader(8) tunables: kern.iscsi.ping_timeout The number of seconds to wait for the target to respond to a NOP-Out PDU. In the event that there is no response within that time the session gets forcibly restarted. kern.iscsi.iscsid_timeout The number of seconds to wait for ctld(8) to establish a session. After that time iscsi will abort and retry. kern.iscsi.login_timeout The number of seconds to wait for a login attempt to succeed. After that time iscsi will abort and retry. kern.iscsi.maxtags The maximum number of outstanding IO requests. kern.iscsi.fail_on_disconnection Controls the behavior after an iSCSI connection has been dropped due to network problems. When set to 1, a dropped connection causes the iSCSI device nodes to be destroyed. After reconnecting, they will be created again. By default, the device nodes are left intact. While the connection is down all input/output operations are suspended, to be retried after the connection is reestablished. SEE ALSO
iscsi.conf(5), iscsictl(8), iscsid(8) HISTORY
The iscsi subsystem first appeared in FreeBSD 10.0. AUTHORS
The iscsi subsystem was developed by Edward Tomasz Napierala <trasz@FreeBSD.org> under sponsorship from the FreeBSD Foundation. BSD
September 11, 2014 BSD
All times are GMT -4. The time now is 11:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy