This document will describe how to identify a KGPSA-CA or a KGPSA-BC located in an Alpha Server. Visual identification: Locate, on your server, where your adapters are connected to the external cables. If your KGPSA-xx HBA has a cable attached, it is a SC Type Optical connector (usually orange with blue or tan connectors). Looking at the HBA sheet metal you will see the optical connector module, holes for 3 LEDs, and the following silk screen (TX, RX, and LP). If the server is powered on and connected to a hub or switch the LED pattern is blinking yellow and two solid green. Under OpenVMS you can identify if you have a KGPSA-CA or KGPSA-BC For getting KGPSA-CA or KGPSA-BC or firmware revision in VMS: vms>> sho dev fg FGA0 (an entry for each KGPSA, a for 1 adapter) FGB0 (b for 2 adapters) .. .... .. .... FGX0 (X for y adapters) vms>> analyze/system SDA>> fc show dev fga0 operational firmware revision is dd3.381a4 (dd prefix for lp8000/kgpsa-ca) or operational firmware revision is sf3.20x7 (sf prefix for lp7000) SDA>> fc show dev fgb0 (do for all FGX0 from vms command "sho dev fg") operational firmware revision is .... .. SDA>> fc show dev fgx0 operational firmware revision is ..... For getting KGPSA-CA or KGPSA-BC firmware revisions in UNIX: unix>> hwmgr -get attribute -cat fibrechannel_adapter name = emx0 category = fibrechannel_adapter registration_time = Thu Sep 21 10:40:48 2000 (approx boot time) user_name = (null) (settable) location = (null) (settable) software_module = (null) state = available state_previous = unknown state_change_time = none event_count = 0 last_event_time = none sim_vendor_id = COMPAQ hba_vendor_id = KGPSA-CA (-CA for LP8000, -BC for LP7000) . . . name = emx99 registration_time = Thu Sep 21 10:40:48 2000 (approx boot time) user_name = (null) (settable) location = (null) (settable) software_module = (null) state = available state_previous = unknown state_change_time = none event_count = 0 last_event_time = none sim_vendor_id = COMPAQ hba_vendor_id = KGPSA-Ca (-CA for LP8000, -BC for LP7000)) for emx# entries do the following for getting firmware revisions. Either: unix>> more /var/adm/messages Search for emx# (emx0...emx9999) by hitting "/" key and typing in "emx" you will see an entry like this: Sep 21 10:41:17 clpr10 vmunix: emx0 at pci1 slot 3 Sep 21 10:41:17 clpr10 vmunix: KGPSA-CA : Driver Rev 1.25a : F/W Rev 3.81a4(1.11) : wwn 1000-0000-c922-4ad4 Sep 21 10:41:17 clpr10 vmunix: emx0: Using console topology setting of : Fabric Sep 21 10:41:17 clpr10 vmunix: scsi1 at emx0 slot 0 rad 0 entering "/" after this, will step you through the file going to each subsequent "emx" entry. Below each emx entry there will be a fw revision and driver revision that is loaded into that KGPSA adapter. (please note boot times and make sure you are looking at the latest boot time that corresponds to the registration time from the hwmgr command, NOTE THE APPROX TIMES IN THIS EXAMPLE) or unix>> uerf -r 300 |more Search for emx# (emx0...emx9999) by hitting "/" key and typing in "emx" you will see an entry like this: Sep 21 10:41:17 clpr10 vmunix: emx0 at pci1 slot 3 Sep 21 10:41:17 clpr10 vmunix: KGPSA-BC : Driver Rev 1.25a : F/W Rev 3.20x7(1.40A0) : wwn 1000-0000-c922-4ad4 Sep 21 10:41:17 clpr10 vmunix: emx0: Using console topology setting of : Fabric Sep 21 10:41:17 clpr10 vmunix: scsi1 at emx0 slot 0 rad 0 entering "/" after this, will step you through the file going to each subsequent "emx" entry. Below each emx entry there will be a fw revision and driver revision that is loaded into that KGPSA adapter. (please note boot times and make sure you are looking at the latest boot time that corresponds to the registration time from the hwmgr command, NOTE THE APPROX TIMES IN THIS EXAMPLE)