Run the following command on the host systems. The highlighted area tells us that we have Virtual Fibre Channel Adapter, which mean we are vios client and the adapter is a virtual that was provided by the vios server.
Update: I also found a great tool called "hbainfo" at http://www.tablespace.net/hbainfo/ I tested it on 6.1 as well as 7.1, and it works great on both. The o/p below is from 6.1 though.
isvp17> lscfg -vpl fcs0 fcs0 U8233.E8B.065D51P-V1-C36-T1 Virtual Fibre Channel Client Adapter Network Address.............C05076037CF00000 ROS Level and ID............ Device Specific.(Z0)........ Device Specific.(Z1)........ Device Specific.(Z2)........ Device Specific.(Z3)........ Device Specific.(Z4)........ Device Specific.(Z5)........ Device Specific.(Z6)........ Device Specific.(Z7)........ Device Specific.(Z8)........C05076037CF00000 Device Specific.(Z9)........ Hardware Location Code......U8233.E8B.065D51P-V1-C36-T1 PLATFORM SPECIFIC Name: vfc-client Node: vfc-client@30000024 Device Type: fcp Physical Location: U8233.E8B.065D51P-V1-C36-T1 Now, let us log onto the vios server itself, and see what kind on HBA adapter it is using to connect to the storage system. This tells us that the adapter that we are using a dual port 8Gb adapter. telnet (vios server name) IBM Virtual I/O Server login: padmin padmin's Password: Last unsuccessful login: Mon Jan 24 09:13:56 MST 2011 on /dev/pts/0 from sig-9-65-56-25.mts.ibm.com Last login: Sun Feb 20 14:34:26 MST 2011 on /dev/pts/0 from 9.57.85.97 $ oem_setup_env # lscfg -vpl fcs0 fcs0 U78A0.001.DNWK129-P1-C1-T1 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03) Part Number.................10N9824 Serial Number...............1B046059F8 Manufacturer................001B EC Level....................D77040 Customer Card ID Number.....577D FRU Number..................10N9824 Device Specific.(ZM)........3 Network Address.............10000000C9AA5388 ROS Level and ID............02781174 Device Specific.(Z0)........31004549 Device Specific.(Z1)........00000000 Device Specific.(Z2)........00000000 Device Specific.(Z3)........09030909 Device Specific.(Z4)........FF781116 Device Specific.(Z5)........02781174 Device Specific.(Z6)........07731174 Device Specific.(Z7)........0B7C1174 Device Specific.(Z8)........20000000C9AA5388 Device Specific.(Z9)........US1.11X4 Device Specific.(ZA)........U2D1.11X4 Device Specific.(ZB)........U3K1.11X4 Device Specific.(ZC)........000000EF Hardware Location Code......U78A0.001.DNWK129-P1-C1-T1 PLATFORM SPECIFIC Name: fibre-channel Model: 10N9824 Node: fibre-channel@0 Device Type: fcp Physical Location: U78A0.001.DNWK129-P1-C1-T1 |
Update: I also found a great tool called "hbainfo" at http://www.tablespace.net/hbainfo/ I tested it on 6.1 as well as 7.1, and it works great on both. The o/p below is from 6.1 though.
# uname -a AIX sonasisvp1_ora1 1 6 00F61CE14C00 # ./hbainfo Total Adapters: 2 This Adapter Index: 0 Adapter Name: com.ibm-df1000f114108a0-1 Manufacturer: IBM SerialNumber: 1C00908221 Model: df1000f114108a0 Model Description: FC Adapter HBA WWN: 20000000C99D9E4C Node Symbolic Name: Hardware Version: Driver Version: 6.1.4.6 Option ROM Version: 02781174 Firmware Version: 111304 Vendor Specific ID: 0 Number Of Ports: 1 Driver Name: /usr/lib/drivers/pci/efcdd Port Index: 0 Node WWN: 20000000C99D9E4C Port WWN: 10000000C99D9E4C Port Fc Id: 330496 Port Type: Fabric Port State: Operational Port Symbolic Name: OS Device Name: fcs0 Port Supported Speed: Unknown - transceiver incable of reporting Port Speed: Unknown - transceiver incable of reporting Port Max Frame Size: 2112 Fabric Name: 10000005336C6CF9 Number of Discovered Ports: 2 Seconds Since Last Reset: 0 Tx Frames: 159 Tx Words: 9 Rx Frames: 313 Rx Words: 20 LIP Count: 0 NOS Count: 0 Error Frames: 0 Dumped Frames: 0 Link Failure Count: 0 Loss of Sync Count: 5 Loss of Signal Count: 0 Primitive Seq Protocol Err Cnt: 0 Invalid Tx Word Count: 16 Invalid CRC Count: 0 # |
2 comments:
For hbainfo tool i ran main.c file it throwing error to me.. i need to run main.c or any other file.. In makefile
lean:
rm -f *.o *~
clean: lean
rm -f hbainfo what it mean...in which path it will remove ".o" files.
Just do a "make", that should create "hbainfo" for you. The 'lean' and 'clean' are to cleaning, not for creating the executable.
Post a Comment