Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Issue with Fiber Channel cards in Solaris
Operating Systems Solaris Issue with Fiber Channel cards in Solaris Post 303043317 by janakors on Friday 24th of January 2020 02:39:50 AM
Old 01-24-2020
the storgae controller is huawei with fol details


Code:
Device Model:	5300 V5
Version:	V500R007C30
Patch Version:	SPC100 SPH103
SN:	xxxxxxxxxxxxxxxxxxxx
WWN:	xxxxxxxxxxxxxxxxxxxx

My Fc cards on T4-2 servrs are
Code:
HBA Port WWN: xxxxxxxxxxxxxxxxxxx
        OS Device Name: /dev/cfg/c3
        Manufacturer: QLogic Corp.
        Model: 371-4325-02
        Firmware Version: 05.06.04
        FCode/BIOS Version:  BIOS: 2.02; fcode: 2.03; EFI: 2.01;
        Serial Number: 0402H00-1232035501
        Driver Name: qlc
        Driver Version: 20120717-4.01
        Type: N-port
        State: online
        Supported Speeds: 2Gb 4Gb 8Gb 
        Current Speed: 8Gb 
        Node WWN: xxxxxxxxxxxxxxxxxxx
HBA Port WWN: xxxxxxxxxxxxxxxxxxxxxxx
        OS Device Name: /dev/cfg/c4
        Manufacturer: QLogic Corp.
        Model: 371-4325-02
        Firmware Version: 05.06.04
        FCode/BIOS Version:  BIOS: 2.02; fcode: 2.03; EFI: 2.01;
        Serial Number: 0402H00-1232035501
        Driver Name: qlc
        Driver Version: 20120717-4.01
        Type: N-port
        State: online
        Supported Speeds: 2Gb 4Gb 8Gb 
        Current Speed: 8Gb 
        Node WWN: xxxxxxxxxxxxxxx

now bencmarking is already done by another team and its ok as the same is working in other data cntre very well

--- Post updated at 01:39 PM ---

i have changed the cables connecting machines to storage controller and then change the SFPS in FC cards even the issue persist. then i also change the ports at
Fiber switch but issue remains the same . now from the same switch and on the same WWN on storgae controller we have another database running + other chaisis but no issue there so i guess it will be the FC cards which is messing so that why i asked for any commnds to check the constant connectivity of this FC cards or any thing else for the same purpose

Regards
 

10 More Discussions You Might Find Interesting

1. Solaris

x25 cards on solaris 8

Has anyone configured one of these things, I cant seem to find any documentation on sunsolve, I want to verify that it is up and running... (1 Reply)
Discussion started by: csaunders
1 Replies

2. Solaris

VxVM/Hba cards/Solaris 10 FS issue

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)
Discussion started by: unclefab
0 Replies

3. HP-UX

Fiber Channel statistic & error level

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)
Discussion started by: pawel_ul
0 Replies

4. UNIX for Advanced & Expert Users

How do I know which HBA cards' hardware I have (on Solaris 10) ?

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)
Discussion started by: ronbarak
3 Replies

5. Solaris

How do I know which HBA cards' hardware I have (on Solaris 10) ?

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)
Discussion started by: ronbarak
4 Replies

6. Solaris

Fiber Channel StorageTek Array Visible to OS

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)
Discussion started by: photon
3 Replies

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

8. Solaris

Solaris 10 new fiber connected tape

Hello all, how can i see configured fc tapes in solaris system and how can i install a new fc shared tape device , thanks Best Regards (2 Replies)
Discussion started by: bogacd
2 Replies

9. IP Networking

Channel bonding Issue - Bond0 interface not getting up in on RHEL6

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)
Discussion started by: Rohit Bhanot
13 Replies

10. Solaris

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: {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 LINUX

fcinfo

fcinfo(1M)																fcinfo(1M)

NAME

       fcinfo - Fibre Channel HBA Port Command Line Interface

SYNOPSIS

       fcinfo hba-port [-l] [HBA_port_WWN...]

       fcinfo  remote-port [-ls] [-p HBA_port_WWN] [REMOTE_port_WWN...]

       fcinfo [-V]

       fcinfo [-?]

       fcinfo  is  a  command  line interface that collects administrative information on fibre channel host bus adapter (HBA) ports on a host. It
       also collects data on any fibre channel targets that may be connected to those ports in a Storage Area Network (SAN).

   SUBCOMMANDS
       The following subcommands are supported:

       hba-port

	   Lists information for the HBA port referenced by the specified HBA_port_WWN. If HBA_port_WWN is not specified, all  fibre  channel  HBA
	   ports on the host will be listed.

       remote-port

	   Lists  the remote-port information for those remote ports that are specified. If no REMOTE_port_WWN is specified, all remote ports that
	   are visible through HBA_port_WWN are listed.

OPTIONS

       The following options are supported:

       -l, --linkstat

	   Lists the link error statistics information for the port referenced by the specified HBA_port_WWN or REMOTE_port_WWN.

       -p HBA_port_WWN, --port HBA_port_WWN

	   Retrieve remote port information from the HBA_port_WWN of the local HBA port on the host. The -p option  can  only  be  used  with  the
	   remote-port subcommand and is a mandatory option.

       -s, --scsi-target

	   Lists  the SCSI target information for all remote ports the user has asked for. The -p, --port option must always be specified and must
	   be a valid HBA port on the host. This HBA port will be used as the initiator for which to retrieve the SCSI level  target  information.
	   Note that this will only function on remote port fibre channel World-Wide Names that support an FC4 type of SCSI.

       -V, --version

	   Prints the version information.

       -?, --help

	   Prints the usage information.

EXAMPLES

       Example 1: Listing all HBA ports

       The following command lists all fibre channel HBA ports on the host:

       # fcinfo hba-port

       HBA Port WWN: 210000e08b074cb5
	       OS Device Name: /dev/cfg/c1
	       Manufacturer: QLogic Corp.
	       Model: 375-3108-xx
	       Type: N-port
	       State: online
	       Supported Speeds: 1Gb 2Gb
	       Current Speed: 2Gb
	       Node WWN: 200000e08b074cb5
       HBA Port WWN: 210100e08b274cb5
	       OS Device Name: /dev/cfg/c2
	       Manufacturer: QLogic Corp.
	       Model: 375-3108-xx
	       Type: N-port
	       State: online
	       Supported Speeds: 1Gb 2Gb
	       Current Speed: 2Gb
	       Node WWN: 200100e08b274cb5
       HBA Port WWN: 210000e08b072ab5
	       OS Device Name: /dev/cfg/c3
	       Manufacturer: QLogic Corp.
	       Model: 375-3108-xx
	       Type: L-port
	       State: online
	       Supported Speeds: 1Gb 2Gb
	       Current Speed: 2Gb
	       Node WWN: 200000e08b072ab5
       HBA Port WWN: 210100e08b272ab5
	       OS Device Name: /dev/cfg/c4
	       Manufacturer: QLogic Corp.
	       Model: 375-3108-xx
	       Type: N-port
	       State: online
	       Supported Speeds: 1Gb 2Gb
	       Current Speed: 2Gb
	       Node WWN: 200100e08b272ab5

       Example 2: Listing HBA ports and link statistics

       The following command lists information for the HBA ports and the link statistics for those ports:

       # fcinfo hba-port -l 210000e08b074cb5 210100e08b274cb5

       HBA Port WWN: 210000e08b074cb5
	       OS Device Name: /dev/cfg/c1
	       Manufacturer: QLogic Corp.
	       Model: 375-3108-xx
	       Type: N-port
	       State: online
	       Supported Speeds: 1Gb 2Gb
	       Current Speed: 2Gb
	       Node WWN: 200000e08b074cb5
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 0
		       Loss of Signal Count: 0
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0
       HBA Port WWN: 210100e08b274cb5
	       OS Device Name: /dev/cfg/c2
	       Manufacturer: QLogic Corp.
	       Model: 375-3108-xx
	       Type: N-port
	       State: online
	       Supported Speeds: 1Gb 2Gb
	       Current Speed: 2Gb
	       Node WWN: 200100e08b274cb5
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 0
		       Loss of Signal Count: 0
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0

       Example 3: Listing all remote ports

       The following command lists all remote ports that are visible through the given HBA port:

       # fcinfo remote-port -p 210100e08b274cb5

       Remote Port WWN: 50020f230000b4af
	       Active FC4 Types: SCSI
	       SCSI Target: yes
	       Node WWN: 50020f200000b4af
       Remote Port WWN: 210000e08b07daa6
	       Active FC4 Types: SCSI
	       SCSI Target: no
	       Node WWN: 200000e08b07daa6
       Remote Port WWN: 20030003ba27c788
	       Active FC4 Types: SCSI
	       SCSI Target: yes
	       Node WWN: 10000003ba27c788
       Remote Port WWN: 210000e08b096a60
	       Active FC4 Types: SCSI,IP
	       SCSI Target: no
	       Node WWN: 200000e08b096a60

       Example 4: Listing remote ports and link statistics

       The following command lists information for the remote ports and the link statistics for those ports:

       # fcinfo remote-port -l -p 210100e08b272ab5

       Remote Port WWN: 210100e08b296a60
	       Active FC4 Types: SCSI,IP
	       SCSI Target: no
	       Node WWN: 200100e08b296a60
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 0
		       Loss of Signal Count: 0
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0
       Remote Port WWN: 20030003ba27d56d
	       Active FC4 Types: SCSI
	       SCSI Target: yes
	       Node WWN: 10000003ba27d56d
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 4765165
		       Loss of Signal Count: 4765165
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0
       Remote Port WWN: 210100e08b27f7a6
	       Active FC4 Types: SCSI
	       SCSI Target: no
	       Node WWN: 200100e08b27f7a6
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 0
		       Loss of Signal Count: 0
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0
       Remote Port WWN: 50020f230000b897
	       Active FC4 Types: SCSI
	       SCSI Target: yes
	       Node WWN: 50020f200000b897
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 7
		       Loss of Signal Count: 7
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0
       Remote Port WWN: 210100e08b27daa6
	       Active FC4 Types: SCSI
	       SCSI Target: no
	       Node WWN: 200100e08b27daa6
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 0
		       Loss of Signal Count: 0
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0
       Remote Port WWN: 210000e08b074cb5
	       Active FC4 Types: SCSI,IP
	       SCSI Target: no
	       Node WWN: 200000e08b074cb5
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 0
		       Loss of Signal Count: 0
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0
       Remote Port WWN: 210100e08b296060
	       Active FC4 Types: SCSI
	       SCSI Target: no
	       Node WWN: 200100e08b296060
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 0
		       Loss of Signal Count: 0
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0

       Example 5: Listing all SCSI targets and link statistics

       The following command lists all remote ports as well as the link statistics and scsi-target information:

       # fcinfo remote-port  -sl -p 210100e08b272ab5

       Remote Port WWN: 210100e08b296a60
	       Active FC4 Types: SCSI,IP
	       SCSI Target: no
	       Node WWN: 200100e08b296a60
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 0
		       Loss of Signal Count: 0
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0
       Remote Port WWN: 20030003ba27d56d
	       Active FC4 Types: SCSI
	       SCSI Target: yes
	       Node WWN: 10000003ba27d56d
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 4765165
		       Loss of Signal Count: 4765165
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0
	       LUN: 0
		 Vendor: SUN
		 Product: T4
		 OS Device Name: /dev/rdsk/c4t20030003BA27D56Dd0s2
	       LUN: 1
		 Vendor: SUN
		 Product: T4
		 OS Device Name: /dev/rdsk/c4t20030003BA27D56Dd1s2
       Remote Port WWN: 210100e08b27f7a6
	       Active FC4 Types: SCSI
	       SCSI Target: no
	       Node WWN: 200100e08b27f7a6
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 0
		       Loss of Signal Count: 0
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0
       Remote Port WWN: 50020f230000b897
	       Active FC4 Types: SCSI
	       SCSI Target: yes
	       Node WWN: 50020f200000b897
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 7
		       Loss of Signal Count: 7
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0
	       LUN: 0
		 Vendor: SUN
		 Product: T300
		 OS Device Name: Unknown
	       LUN: 1
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d1s2
	       LUN: 2
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d2s2
	       LUN: 3
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d3s2
	       LUN: 4
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d4s2
	       LUN: 5
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d5s2
	       LUN: 6
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d6s2
	       LUN: 7
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d7s2
	       LUN: 8
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d8s2
	       LUN: 9
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d9s2
	       LUN: 10
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d10s2
	       LUN: 11
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d11s2
	       LUN: 12
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d12s2
	       LUN: 13
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d13s2
	       LUN: 14
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d14s2
	       LUN: 15
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d15s2
       Remote Port WWN: 210100e08b27daa6
	       Active FC4 Types: SCSI
	       SCSI Target: no
	       Node WWN: 200100e08b27daa6
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 0
		       Loss of Signal Count: 0
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0
       Remote Port WWN: 210000e08b074cb5
	       Active FC4 Types: SCSI,IP
	       SCSI Target: no
	       Node WWN: 200000e08b074cb5
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 0
		       Loss of Signal Count: 0
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0
       Remote Port WWN: 210100e08b296060
	       Active FC4 Types: SCSI
	       SCSI Target: no
	       Node WWN: 200100e08b296060
	       Link Error Statistics:
		       Link Failure Count: 0
		       Loss of Sync Count: 0
		       Loss of Signal Count: 0
		       Primitive Seq Protocol Error Count: 0
		       Invalid Tx Word Count: 0
		       Invalid CRC Count: 0

       Example 6: Listing SCSI target information

       The following command lists all remote ports as well as the scsi-target information:

       # fcinfo remote-port  -s -p 210100e08b272ab5

       Remote Port WWN: 210100e08b296a60
	       Active FC4 Types: SCSI,IP
	       SCSI Target: no
	       Node WWN: 200100e08b296a60
       Remote Port WWN: 20030003ba27d56d
	       Active FC4 Types: SCSI
	       SCSI Target: yes
	       Node WWN: 10000003ba27d56d
	       LUN: 0
		 Vendor: SUN
		 Product: T4
		 OS Device Name: /dev/rdsk/c4t20030003BA27D56Dd0s2
	       LUN: 1
		 Vendor: SUN
		 Product: T4
		 OS Device Name: /dev/rdsk/c4t20030003BA27D56Dd1s2
       Remote Port WWN: 210100e08b27f7a6
	       Active FC4 Types: SCSI
	       SCSI Target: no
	       Node WWN: 200100e08b27f7a6
       Remote Port WWN: 50020f230000b897
	       Active FC4 Types: SCSI
	       SCSI Target: yes
	       Node WWN: 50020f200000b897
	       LUN: 0
		 Vendor: SUN
		 Product: T300
		 OS Device Name: Unknown
	       LUN: 1
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d1s2
	       LUN: 2
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d2s2
	       LUN: 3
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d3s2
	       LUN: 4
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d4s2
	       LUN: 5
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d5s2
	       LUN: 6
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d6s2
	       LUN: 7
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d7s2
	       LUN: 8
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d8s2
	       LUN: 9
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d9s2
	       LUN: 10
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d10s2
	       LUN: 11
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d11s2
	       LUN: 12
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d12s2
	       LUN: 13
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d13s2
	       LUN: 14
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d14s2
	       LUN: 15
		 Vendor: SUN
		 Product: T300
		 OS Device Name: /dev/rdsk/c4t50020F230000B897d15s2
       Remote Port WWN: 210100e08b27daa6
	       Active FC4 Types: SCSI
	       SCSI Target: no
	       Node WWN: 200100e08b27daa6
       Remote Port WWN: 210000e08b074cb5
	       Active FC4 Types: SCSI,IP
	       SCSI Target: no
	       Node WWN: 200000e08b074cb5
       Remote Port WWN: 210100e08b296060
	       Active FC4 Types: SCSI
	       SCSI Target: no
	       Node WWN: 200100e08b296060

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNW			   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Evolving			   |
       +-----------------------------+-----------------------------+

       attributes(5)

ERROR MESSAGES

       Errors that can occur in addition to the errors normally associated with system administration commands:

       HBA_port_WWN: not found

       REMOTE_port_WWN: not found

								    17 Feb 2005 							fcinfo(1M)
All times are GMT -4. The time now is 03:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy