Can anyone explain to me why TCP/IP protocols provide an abundance of
management information (e.g. MIB-II) whereas fiber channel interfaces
provide hardly any information, which often seems to be of a rather
dubious nature?
I had to hunt and peck for how to see if my fiber channel was working
properly. The incantations were so obscure that I put them in a shell
script so that they are available when needed.
Is this all that is available or am I missing something?
=== Channel A ===
HBA Port WWN: 10000000c967c830
OS Device Name: /dev/cfg/c2
Manufacturer: Emulex
Model: LPe11002-M4
Firmware Version: 2.72a2 (Z3F2.72A2)
FCode/BIOS Version: none
Type: L-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 20000000c967c830
Link Error Statistics:
Link Failure Count: 1
Loss of Sync Count: 111
Loss of Signal Count: 2
Primitive Seq Protocol Error Count: 0
Invalid Tx Word Count: 199
Invalid CRC Count: 0
Remote Port WWN: 200400a0b83a8a0c
Active FC4 Types:
SCSI Target: yes
Node WWN: 200400a0b83a8a0b
Link Error Statistics:
Link Failure Count: 61
Loss of Sync Count: 238160
Loss of Signal Count: 2985
Primitive Seq Protocol Error Count: 0
Invalid Tx Word Count: 0
Invalid CRC Count: 0
Thanks,
Bob
======================================
Bob Friesenhahn
[EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
