9 More Discussions You Might Find Interesting
1. Web Development
Hi Ravinder,
Could you (and anyone else who wants to help out) check this PHP code and confirm it does what I expect it to do, which is to color a badge based on the weeks a member is active in the latest sequence? I did a cut-paste-change from my "days in sequence" PHP prototype script and it... (6 Replies)
Discussion started by: Neo
6 Replies
2. Solaris
Hi
I would like to know whether we can configure link based IPMP in private connectivity in Oracle RAC
Regarsd
---------- Post updated at 04:35 PM ---------- Previous update was at 04:27 PM ----------
Here I am taking about in case of private connectivity through cross cable (6 Replies)
Discussion started by: sb200
6 Replies
3. Shell Programming and Scripting
#!/bin/bash
for digit in $(seq 1 10)
do
if ping -c1 -w2 192.168.1.$digit &> /dev/null
then
echo "192.168.1.$digit is UP"
else
echo "192.168.1.$digit is DOWN"
fi
done (3 Replies)
Discussion started by: fusetrips
3 Replies
4. Solaris
Hi,
This may have already been raised previously so sorry for the duplication. What I want to achieve is have a physical server using link based IPMP setup in the global zone (not problem doing that) and then create a zone set as Shared-IP so when the servers NIC has an issue the IP will... (0 Replies)
Discussion started by: giles.cardew
0 Replies
5. Solaris
Hi All,
Need your help to explaining why when i configure 2 interface IPMP active-standby appear, INACTIVE and DEPRECATED parameter, detail screen shoot as below :
root@machine01 # ifconfig -a
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
inet... (6 Replies)
Discussion started by: Wong_Cilacap
6 Replies
6. AIX
Hi all,
I am new to HACMP. So sorry for the newie question. But I did search the forum and it seems that no one asks this before.
So if a 2-node cluster runs in active-active mode (and the same application), what is the benefit of using HACMP ?
If it runs in active-stanby, it is easy to... (9 Replies)
Discussion started by: qiulang
9 Replies
7. Solaris
Hi everybody,
One client asked me to configure network failover and load balancing for two Ethernet interfaces, I tried IPMP but I was unable to do so, because he's using his Gateway as firewall and PING is disabled.
so IPMP kept telling me that all interfaces failed because gateway can't be... (8 Replies)
Discussion started by: Sun Fire
8 Replies
8. Solaris
Hello,
I am wondering if its possible to do link state IPMP with load spreading on Solaris 10 with 3 addresses, 2 fixed and 1 virtual/floating.
I want to ensure the 'virtual' ip is the only one that can be used by applications. I know with probe based I could mark interfaces as deprecated... (1 Reply)
Discussion started by: Actuator
1 Replies
9. UNIX for Advanced & Expert Users
Hey,
I have few Questions :
1. How to Check/Find who all are the users accessing the server using their id ?
2. How to Check who is the active user or non active user (whose id exists but the access privileges has been removed) ?
I am presently using AIX5.3 as a server.
Please suggest... (3 Replies)
Discussion started by: varungupta
3 Replies
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)