NOTE: The June 2001 Release replaced event numbers 0-19 with numbers 200-219 respectively. For the new numbers, add 200 to the original number.
Event 0 (Replaced by 200 in June 2001)
- Severity: Critical
- Event Class: I/O
- Event Summary:Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description: SCSI Card 0 failed.
- Probable Cause / Recommended Action:
Failed hardware or improper installation. Check seating of SCSI Card and check SCSI cable for loose connection and termination. If the problem persists, replace the SCSI card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:05 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:05 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 200 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: SCSI Card 0 failed. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of SCSI Card and check SCSI cable for loose connection and termination. If the problem persists, replace the SCSI card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1d00000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#200 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 00 FF E4 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 00 FE F4 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 1 (Replaced by 201 in June 2001)
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description: SCSI Card 1 did not pass selftest.
- Probable Cause / Recommended Action:
Failed hardware or improper installation. Check if SCSI Card is not seated properly and if SCSI cable is loose. If problem persists, then replace SCSI card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:06 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:05 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 201 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: SCSI Card 1 failed. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of SCSI Card and check SCSI cable for loose connection and termination. If the problem persists, replace the SCSI card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1d00000002 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#201 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 01 00 20 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 01 00 48 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 2 (Replaced by 202 in June 2001)
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description: SCSI Card 2 did not pass selftest.
- Probable Cause / Recommended Action:
Failed hardware or improper installation. Check if SCSI Card is not seated properly and if SCSI cable is loose. If problem persists, then replace SCSI card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:06 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:06 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 202 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: SCSI Card 2 failed. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of SCSI Card and check SCSI cable for loose connection and termination. If the problem persists, replace the SCSI card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1e00000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#202 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 01 00 C0 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 01 00 84 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 3 (Replaced by 203 in June 2001)
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description: SCSI Card 3 did not pass selftest.
- Probable Cause / Recommended Action:
Failed hardware or improper installation. Check if SCSI Card is not seated properly and if SCSI cable is loose. If problem persists, then replace SCSI card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:06 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:06 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 203 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: SCSI Card 3 failed. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of SCSI Card and check SCSI cable for loose connection and termination. If the problem persists, replace the SCSI card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1e00000002 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#203 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 01 00 34 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 01 00 D4 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 4 (Replaced by 204 in June 2001)
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description: FC SCSI MUX failed selftest. PCI Failed
- Probable Cause / Recommended Action:
Failed hardware or improper installation. Check the seating of all the SCSI, FC, and memory cards. Check all the SCSI cables for proper connection including the connector screws. If problem still persists, contact HP for replacement of the motherboard.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:06 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:06 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 204 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: Mother Board Failed Selftest. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of all SCSI, FC, and memory cards. Check all of the SCSI cables for proper connection and termination and check the connector screws. If the problem still persists, contact HP for replacement of the motherboard. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1e00000004 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#204 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 00 FE E0 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 00 FF 08 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 6 (Replaced by 206 in June 2001)
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description: FC SCSI MUX failed selftest. Mother Board Failed
- Probable Cause / Recommended Action: Failed hardware or improper installation. Check the seating of all the SCSI, FC, and memory cards. Check all the SCSI cables for proper connection including the connector screws. If problem still persists, contact HP for replacement of the motherboard.
- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:07 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:06 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 206 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: Mother Board Failed Selftest. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of all SCSI, FC, and memory cards. Check all of the SCSI cables for proper connection and termination and check the connector screws. If the problem still persists, contact HP for replacement of the motherboard. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1e00000006 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#206 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 00 FE B8 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 00 FF A8 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 7 (Replaced by 207 in June 2001)
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description:
FC SCSI MUX failed selftest. Memory Board Failed- Probable Cause / Recommended Action:
Failed hardware or improper installation. Seat the card properly and if the problem persists then contact HP for the replacement of the memory card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:07 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:07 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 207 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: Memory Board Failed Selftest. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of memory board card. If the problem persists, then contact HP for replacement of the memory board. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1f00000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#207 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 00 FF 94 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 00 FF 44 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 8 (Replaced by 208 in June 2001)
- Severity: Minor Warning
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description:
FC SCSI MUX failed selftest. LCD Failed- Probable Cause / Recommended Action:
MUX has been set to offline by front panel controls. Failed hardware or improper installation. If the problem persists then contact HP for the replacement of the LCD.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 17:51:48 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is MINORWARNING(2). Event data from monitor: Event Time..........: Wed Mar 21 17:51:48 2001 Severity............: MINORWARNING Monitor.............: dm_fc_scsi_mux Event #.............: 208 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: LCD Failed Probable Cause / Recommended Action: The MUX has entered the offline condition due to commands from the front panel or failed hardware or improper installation. Use the front panel controls to put the MUX online. Check for improper installation of all cards and the front panel assembly. If the problem persists, then contact HP for replacement of the front panel assembly. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95ab400000004 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#208 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 9 minute Each path, for which this event gets generated, will have this same duplicate event number : 1 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 5F 73 63 73 69 5F 6D 75 78 00 9D 00 00 00 20 0x0020: 00 05 00 00 00 00 00 02 00 00 00 0B 00 00 00 00 0x0030: 00 00 00 0F 00 00 00 09 00 00 00 3C 00 00 00 00 0x0040: 40 01 4E D4 00 00 01 61 00 00 00 00 2F 76 61 72 0x0050: 2F 73 74 6D 2F 63 6F 6E 66 69 67 2F 74 6F 6F 6C 0x0060: 73 2F 6D 6F 6E 69 74 6F 72 2F 64 65 66 61 75 6C 0x0070: 74 5F 64 6D 5F 66 63 5F 73 63 73 69 5F 6D 75 78 0x0080: 2E 63 6C 63 66 67 00 00 00 00 00 00 00 00 00 00 0x0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x00A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >---------- End Event Monitoring Service Event Notification ----------<Event 9 (Replaced by 209 in June 2001)
- Severity: Major Warning
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 10/12.8.0.255.0.4.0 : Hardware warning.
- Description:
FC SCSI MUX does not respond to host Fibre Channel requests.- Probable Cause / Recommended Action:
MUX has been set to offline by front panel controls. MUX has reset itself due to network event. MUX and I/O operations will recover automatically from reset. Problem in Fibre Channel network. Failed hardware or improper installation. Determine if FC SCSI MUX resumes responding. If problem recurs or persists, then check condition of Fibre Channel network. The FC SCSI MUX front panel or serial port user interface may provide additional information.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 12:38:21 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/10_12.8.0.255.0.4.0 is >= 1. Its current value is MAJORWARNING(3). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 12:38:20 2001 Severity............: MAJORWARNING Monitor.............: dm_fc_scsi_mux Event #.............: 209 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 10/12.8.0.255.0.4.0 : Hardware warning. Description of Error: FC SCSI MUX not responding. Probable Cause / Recommended Action: The MUX has entered the offline condition due to one of many possible causes. Commands from the front panel or failed hardware or improper installation may have caused the MUX to go offline. The MUX may have reset itself due to network event. A problem may exist in the Fibre Channel network. Normally the MUX and I/O operations will recover automatically from reset. Determine if the MUX resumes responding. No action needed if the MUX resumes responding. Use the front panel controls to put the MUX online. Check for improper installation of all cards. If the FC adapter on the host or a device attached to the MUX also reports errors, the fiber cable may be defective or not attached. Check the fiber cabling between the MUX and the host. The MUX front panel or serial port user interface may provide additional information. If the problem persists, then check the Fibre Channel network connected to the MUX. The MUX will not respond if it does not have the correct firmware. Firmware with date code 3810 or earlier does not support the polling done by this monitor. If the MUX has 3810 or earlier firmware, then download the latest firmware. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab9113c00000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#209 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: Firmware Revision (Not Available): Each path, for which this event gets generated, will have this same duplicate event number : 329 Manager-Specific Information: Raw Manager Data: 0x0000: 00 02 0x0000: 00 00 00 01 >---------- End Event Monitoring Service Event Notification ----------<Event 10 (Replaced by 210 in June 2001)
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description:
FC SCSI MUX failed selftest. FC port A failed.- Probable Cause / Recommended Action:
Failed hardware or improper installation. Check the FC card for proper seating. If problem persists, contact HP for replacement FC card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:50 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 00:32:50 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 210 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: FC port A failed. Probable Cause / Recommended Action: The FC port of the MUX failed selftest due to failed hardware or improper installation. Check the FC card for proper seating. If the problem persists, then contact HP for replacement of the FC card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673200000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#210 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 581 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0A 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 07 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 E9 A8 40 01 DD A0 76 00 33 61 0x0060: 40 00 FE 24 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 ED C8 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 00 FE 60 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 11 (Replaced by 211 in June 2001)
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description:
FC SCSI MUX failed selftest. FC port B failed- Probable Cause / Recommended Action:
The FC port of the MUX failed selftest due to failed hardware or improper installation. Check the FC card for proper seating. If the problem persists, then contact HP for replacement of the FC card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:52 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 00:32:51 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 211 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: FC port B failed. Probable Cause / Recommended Action: The FC port of the MUX failed selftest due to failed hardware or improper installation. Check the FC card for proper seating. If the problem persists, then contact HP for replacement of the FC card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673300000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#211 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 582 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0B 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 08 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 E9 A8 40 01 DD A0 76 00 33 61 0x0060: 40 01 00 2C 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 ED C8 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 01 00 40 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 12 (Replaced by 212 in June 2001)
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description: FC SCSI MUX failed selftest. Mother Board (Processor)
- Probable Cause / Recommended Action:
The MUX failed selftest. Check seating of all SCSI, FC, and memory cards. Check all of the SCSI cables for proper connection and termination and check the connector screws. If the problem still persists, contact HP for replacement of the motherboard.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:53 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 00:32:53 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 212 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: Mother board processor failed. Probable Cause / Recommended Action: The MUX failed selftest. Check seating of all SCSI, FC, and memory cards. Check all of the SCSI cables for proper connection and termination and check the connector screws. If the problem still persists, contact HP for replacement of the motherboard. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673500000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#212 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 583 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0C 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 09 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 E9 A8 40 01 DD A0 76 00 33 61 0x0060: 40 00 FF A0 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 ED C8 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 00 FF F0 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 13 (Replaced by 213 in June 2001)
- Severity: Information
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Information.
- Description:
FC SCSI MUX detected an unexpected condition during normal operation.- Probable Cause / Recommended Action:
May happen if FC SCSI MUX gets used in a new and untested environment or an unusual condition occurs. No corrective action needed if this event does not recur.
FC SCSI MUX should reset itself and then continue functioning. Report the event with its associated data to HP.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:54 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is MINORWARNING(2). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 00:32:54 2001 Severity............: MINORWARNING Monitor.............: dm_fc_scsi_mux Event #.............: 213 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Information. Description of Error: Code assertion occurred. Probable Cause / Recommended Action: The firmware or processor on the MUX has detected a firmware or hardware failure and was in an inconsistent state. The MUX has reset itself. This event does not require a corrective action if it does not reoccur. If this event does reoccur, report this event with its associated data to HP. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673600000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#213 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 584 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0D 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 0A Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 E9 A8 40 01 DD A0 76 00 33 61 0x0060: 40 01 00 2C 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 ED B0 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 00 FF DC 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 14 (Replaced by 214 in June 2001)
- Severity: Major Warning
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware warning.
- Description:
FC SCSI MUX failed selftest. Unknown FRU- Probable Cause / Recommended Action:
Failed hardware or improper installation but the MUX could not determine the exact cause. May occur if a fan fails twice. If preceded by Fan Module failure, then quite possibly another fan failure has occurred. However, another component may also cause this failure. The FC SCSI MUX will continue to operate as long as the remaining fan provides sufficient cooling.
Check the fan cables and connectors.
Check if both fans run and trouble shoot to find the exact cause. Replace fan assembly if found defective.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:55 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is INFORMATION(1). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 00:32:55 2001 Severity............: INFORMATION Monitor.............: dm_fc_scsi_mux Event #.............: 214 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware warning. Description of Error: Unknown hardware failure. Probable Cause / Recommended Action: The MUX failed selftest but could not determine the exact cause. This event could occur if a fan failure was previously reported, but the fan was not replaced, and another fan failed. Check the fan cables and connectors, and check to see that both fans are operational. Replace the fan assembly if it is found to be defective. If the fan is not defective, the cause may be another MUX component. Report this event with its associated data to HP. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673700000002 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#214 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 585 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 10 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 E9 A8 40 01 DD A0 76 00 33 61 0x0060: 40 00 FF C8 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 ED C8 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 01 00 40 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 15 (Replaced by 215 in June 2001)
- Severity: Major Warning
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware warning.
- Description: One of the two FC SCSI MUX fans failed.
- Probable Cause / Recommended Action:
One of the two MUX cooling fans has failed. The fan may have something blocking it such as the fan cable. The fan may have an improperly installed or disconnected cable. The MUX will continue to operate as long as the remaining fan provides sufficient cooling. Check the fan cables and connectors. Check if both fans run and trouble shoot to find the exact cause. Replace the fan assembly if it is found to be defective.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 01:33:00 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is MAJORWARNING(3). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 01:32:59 2001 Severity............: MAJORWARNING Monitor.............: dm_fc_scsi_mux Event #.............: 215 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware warning. Description of Error: Fan module failed. Probable Cause / Recommended Action: One of the two MUX cooling fans has failed. The fan may have something blocking it such as the fan cable. The fan may have an improperly installed or disconnected cable. The MUX will continue to operate as long as the remaining fan provides sufficient cooling. Check the fan cables and connectors. Check if both fans run and trouble shoot to find the exact cause. Replace the fan assembly if it is found to be defective. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8754b00000004 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#215 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 5 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 658 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0F 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 02 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 E9 A8 40 01 DD A0 76 00 33 61 0x0060: 40 00 FE 74 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 ED C8 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 00 FF B4 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 16 (Replaced by 216 in June 2001)
- Severity: Information
- Event Class: I/O
- Event Summary:Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : FC external loopback test did not pass.
- Description:
FC SCSI MUX failed loopback selftest. FC port A failed.- Probable Cause / Recommended Action:
Failed hardware or improper installation. Check for proper installation of loopback cable.
Check the FC card for proper seating. Confirm the connection by unplugging and reconnecting the cable and performing an External Loop Test. If problem persists, contact HP for replacement FC card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:49 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Mar 21 00:32:48 2001 Severity............: INFORMATION Monitor.............: dm_fc_scsi_mux Event #.............: 216 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : FC external loopback test did not pass. Description of Error: FC port A external loopback test Failed. Probable Cause / Recommended Action: The FC loopback test has failed. Check for proper installation of the loopback cable. Check to make sure that the FC port cover connector was not used during the test instead of the loopback cable (the FC port cover does not provide loopback capability). Check the FC card for proper seating. Disconnect and reconnect the FC cable and perform the external loopback test again. If the problem persists, contact HP for replacement of the FC card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673000000002 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#216 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 577 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0A 00 00 16 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 03 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 EC 08 40 01 DD A0 76 00 33 61 0x0060: 40 00 FE 10 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 EE 00 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 01 00 68 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 17 (Replaced by 217 in June 2001)
- Severity: Information
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : FC external loopback test did not pass.
- Description:
FC SCSI MUX failed loopback selftest. FC port B failed- Probable Cause / Recommended Action:
The FC loopback test has failed. Check for proper installation of the loopback cable. Check to make sure that the FC port cover connector was not used during the test instead of the loopback cable (the FC port cover does not provide loopback capability). Check the FC card for proper seating. Disconnect and reconnect the FC cable and perform the external loopback test again. If the problem persists, contact HP for replacement of the FC card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:49 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is INFORMATION(1). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 00:32:49 2001 Severity............: INFORMATION Monitor.............: dm_fc_scsi_mux Event #.............: 217 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : FC external loopback test did not pass. Description of Error: FC port B external loopback test Failed. Probable Cause / Recommended Action: The FC loopback test has failed. Check for proper installation of the loopback cable. Check to make sure that the FC port cover connector was not used during the test instead of the loopback cable (the FC port cover does not provide loopback capability). Check the FC card for proper seating. Disconnect and reconnect the FC cable and perform the external loopback test again. If the problem persists, contact HP for replacement of the FC card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673100000002 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#217 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 579 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0B 00 00 16 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 05 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 EC 08 40 01 DD A0 76 00 33 61 0x0060: 40 00 FE 10 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 EE 00 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 00 FD D4 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 19 (Replaced by 219 in June 2001)
- Severity: Major Warning
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 10/12.8.0.255.0.4.0 : Hardware warning.
- Description:
FC SCSI MUX has started responding.- Probable Cause / Recommended Action:
The MUX has entered the online condition due one of many possible causes. The MUX may have powered up. The MUX may have been connected or re-connected to the Fibre Channel network. The MUX may have reset itself due to a network event. A problem may have existed in the Fibre Channel network and now does not exits. The MUX may have had firmware with date code 3810 or earlier, replaced by newer firmware. After download with newer firmware, the MUX has the capability to handle polling by this monitor. Normally the MUX and I/O operations will recover automatically from reset. No action needed if the MUX resumes responding.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 13:24:52 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/10_12.8.0.255.0.4.0 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Mar 21 13:24:52 2001 Severity............: INFORMATION Monitor.............: dm_fc_scsi_mux Event #.............: 219 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 10/12.8.0.255.0.4.0 : Hardware warning. Description of Error: FC SCSI MUX has started responding. Probable Cause / Recommended Action: The MUX has entered the online condition due one of many possible causes. The MUX may have powered up. The MUX may have been connected or re-connected to the Fibre Channel network. The MUX may have reset itself due to a network event. A problem may have existed in the Fibre Channel network and now does not exist. The MUX may have had firmware with date code 3810 or earlier, replaced by newer firmware. After download with newer firmware, the MUX has the capability to handle polling by this monitor. Normally the MUX and I/O operations will recover automatically from reset. No action is required. This event has the same severity as MUX not responding event so that when one event appears, so can the other. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab91c2400000002 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#219 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: Firmware Revision (Not Available): Each path, for which this event gets generated, will have this same duplicate event number : 988 Manager-Specific Information: Raw Manager Data: 0x0000: 00 02 0x0000: 00 00 00 02 >---------- End Event Monitoring Service Event Notification ----------<Event 100
- Severity: Information
- Event Class: I/O
- Event Summary: Device added to monitoring
- Problem Description:
The a device has been added and is being monitored by this monitor.- Probable Cause / Recommended Action
No action required.<RESOURCE_NAME>- Automated Recovery: None
- Event Generation Threshold: 1 occurrence <RESOURCE_NAME>
Event 101
- Severity: Critical
- Event Class: I/O
- Event Summary: Device removed from monitoring
- Problem Description:
A divice has been removed from the list of items being monitored by this monitor.- Probable Cause / Recommended Action:
A device was removed from the system, has stopped responding to the system or it has been replaced with a device that is not supported by this monitor.
Run ioscan to determine the state and type of the device.
Check the /var/stm/data/os_decode_xref for the information indicating which devices are supported by this monitor.
Check other monitors to determine if they are now monitoring the device by running /etc/opt/resmon/lbin monconfig and the using the "Check monitoring" command.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 103
- Severity: Informational
- Event Class: I/O
- Description: This is a test message from the monitor to test the communication path from the monitor to the notification mechanism.
- Probable Cause / Recommended Action:
User requested test event. No action is required.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Feb 21 10:29:21 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/10_12.8.0.255.0.4.0 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Feb 21 10:29:21 2001 Severity............: INFORMATION Monitor.............: dm_fc_scsi_mux Event #.............: 103 System..............: hprdstl6.rose.hp.com Summary: Disk at hardware path 10/12.8.0.255.0.4.0 : Test event Description of Error: This is a test message from the monitor to test the communication path from the monitor to the notification mechanism. Probable Cause / Recommended Action: No action required. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3a94090100000002 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.24.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#103 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1: 8/12.8.0.255.0.5 FC Path 2: 10/8.0.255.0.5.0 World Wide Name: 0x20000060-0xB02AE242 Product Number..............: HP A3308 >---------- End Event Monitoring Service Event Notification ----------<Event 200
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description: SCSI Card 0 did not pass selftest.
- Probable Cause / Recommended Action:
Failed hardware or improper installation. Check seating of SCSI Card and check SCSI cable for loose connection and termination. If the problem persists, replace the SCSI card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:05 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:05 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 200 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: SCSI Card 0 failed. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of SCSI Card and check SCSI cable for loose connection and termination. If the problem persists, replace the SCSI card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1d00000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#200 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 00 FF E4 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 00 FE F4 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 201
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description:
SCSI Card 1 did not pass selftest.- Probable Cause / Recommended Action:
Failed hardware or improper installation. Check seating of SCSI Card and check SCSI cable for loose connection and termination. If the problem persists, replace the SCSI card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:06 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:05 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 201 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: SCSI Card 1 failed. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of SCSI Card and check SCSI cable for loose connection and termination. If the problem persists, replace the SCSI card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1d00000002 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#201 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 01 00 20 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 01 00 48 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 202
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description:
SCSI Card 2 did not pass selftest.- Probable Cause / Recommended Action:
Failed hardware or improper installation. Check seating of SCSI Card and check SCSI cable for loose connection and termination. If the problem persists, replace the SCSI card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:06 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:06 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 202 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: SCSI Card 2 failed. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of SCSI Card and check SCSI cable for loose connection and termination. If the problem persists, replace the SCSI card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1e00000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#202 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 01 00 C0 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 01 00 84 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 203
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description:
SCSI Card 3 did not pass selftest.- Probable Cause / Recommended Action:
Failed hardware or improper installation. Check if SCSI Card is not seated properly and if SCSI cable is loose. If problem persists, then replace SCSI card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:06 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:06 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 203 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: SCSI Card 3 failed. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of SCSI Card and check SCSI cable for loose connection and termination. If the problem persists, replace the SCSI card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1e00000002 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#203 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 01 00 34 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 01 00 D4 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 204
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description: FC SCSI MUX failed selftest. PCI Failed
- Probable Cause / Recommended Action:
Failed hardware or improper installation. Check seating of all SCSI, FC, and memory cards. Check all of the SCSI cables for proper connection and termination and check the connector screws. If the problem still persists, contact HP for replacement of the motherboard.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:06 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:06 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 204 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: Mother Board Failed Selftest. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of all SCSI, FC, and memory cards. Check all of the SCSI cables for proper connection and termination and check the connector screws. If the problem still persists, contact HP for replacement of the motherboard. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1e00000004 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#204 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 00 FE E0 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 00 FF 08 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 206
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description: FC SCSI MUX failed selftest. Mother Board Failed
- Probable Cause / Recommended Action:
Failed hardware or improper installation. Check the seating of all the SCSI, FC, and memory cards. Check all the SCSI cables for proper connection including the connector screws. If problem still persists, contact HP for replacement of the motherboard.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:07 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:06 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 206 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: Mother Board Failed Selftest. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of all SCSI, FC, and memory cards. Check all of the SCSI cables for proper connection and termination and check the connector screws. If the problem still persists, contact HP for replacement of the motherboard. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1e00000006 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#206 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 00 FE B8 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 00 FF A8 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 207
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description: FC SCSI MUX failed selftest. Memory Board Failed
- Probable Cause / Recommended Action: Failed hardware or improper installation. Seat the card properly and if the problem persists then contact HP for the replacement of the memory card.
- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 18:02:07 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). Event data from monitor: Event Time..........: Wed Mar 21 18:02:07 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 207 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: Memory Board Failed Selftest. Probable Cause / Recommended Action: Failed hardware or improper installation. Check seating of memory board card. If the problem persists, then contact HP for replacement of the memory board. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95d1f00000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#207 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 19 minute Each path, for which this event gets generated, will have this same duplicate event number : 165 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 4D 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 D5 4D 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 F1 D8 40 01 D5 B8 76 00 33 61 0x0060: 40 00 FF 94 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 F6 60 40 01 E9 08 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 D5 D5 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 D6 00 0x00A0: 40 01 D6 48 73 69 5F 6D 40 00 FF 44 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 208
- Severity: Minor Warning
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description: FC SCSI MUX failed selftest. LCD Failed
- Probable Cause / Recommended Action:
The MUX has entered the offline condition due to commands from the front panel or failed hardware or improper installation. Use the front panel controls to put the MUX online. Check for improper installation of all cards and the front panel assembly. If the problem persists, then contact HP for replacement of the front panel assembly.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 17:51:48 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is MINORWARNING(2). Event data from monitor: Event Time..........: Wed Mar 21 17:51:48 2001 Severity............: MINORWARNING Monitor.............: dm_fc_scsi_mux Event #.............: 208 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: LCD Failed Probable Cause / Recommended Action: The MUX has entered the offline condition due to commands from the front panel or failed hardware or improper installation. Use the front panel controls to put the MUX online. Check for improper installation of all cards and the front panel assembly. If the problem persists, then contact HP for replacement of the front panel assembly. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab95ab400000004 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#208 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 13 day; 9 hour; 9 minute Each path, for which this event gets generated, will have this same duplicate event number : 1 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 01 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 5F 73 63 73 69 5F 6D 75 78 00 9D 00 00 00 20 0x0020: 00 05 00 00 00 00 00 02 00 00 00 0B 00 00 00 00 0x0030: 00 00 00 0F 00 00 00 09 00 00 00 3C 00 00 00 00 0x0040: 40 01 4E D4 00 00 01 61 00 00 00 00 2F 76 61 72 0x0050: 2F 73 74 6D 2F 63 6F 6E 66 69 67 2F 74 6F 6F 6C 0x0060: 73 2F 6D 6F 6E 69 74 6F 72 2F 64 65 66 61 75 6C 0x0070: 74 5F 64 6D 5F 66 63 5F 73 63 73 69 5F 6D 75 78 0x0080: 2E 63 6C 63 66 67 00 00 00 00 00 00 00 00 00 00 0x0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x00A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >---------- End Event Monitoring Service Event Notification ----------<Event 209
- Severity: Major Warning
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 10/12.8.0.255.0.4.0 : Hardware warning.
- Description: FC SCSI MUX does not respond to host Fibre Channel requests.
- Probable Cause / Recommended Action:
The MUX has entered the offline condition due to one of many possible causes. Commands from the front panel or failed hardware or improper installation may have caused the MUX to go offline. The MUX may have reset itself due to network event. A problem may exist in the Fibre Channel network. Normally the MUX and I/O operations will recover automatically from reset. Determine if the MUX resumes responding. No action needed if the MUX resumes responding. Use the front panel controls to put the MUX online. Check for improper installation of all cards. If the FC adapter on the host or a device attached to the MUX also reports errors, the fiber cable may be defective or not attached. Check the fiber cabling between the MUX and the host. The MUX front panel or serial port user interface may provide additional information. If the problem persists, then check the Fibre Channel network connected to the MUX. The MUX will not respond if it does not have the correct firmware. Firmware with date code 3810 or earlier does not support the polling done by this monitor. If the MUX has 3810 or earlier firmware, then download the latest firmware.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< otification Time: Wed Mar 21 12:38:21 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/10_12.8.0.255.0.4.0 is >= 1. ts current value is MAJORWARNING(3). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 12:38:20 2001 everity............: MAJORWARNING onitor.............: dm_fc_scsi_mux vent #.............: 209 ystem..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 10/12.8.0.255.0.4.0 : Hardware warning. escription of Error: FC SCSI MUX not responding. Probable Cause / Recommended Action: The MUX has entered the offline condition due to one of many possible causes. Commands from the front panel or failed hardware or improper installation may have caused the MUX to go offline. The MUX may have reset itself due to network event. A problem may exist in the Fibre Channel network. Normally the MUX and I/O operations will recover automatically from reset. Determine if the MUX resumes responding. No action needed if the MUX resumes responding. Use the front panel controls to put the MUX online. Check for improper installation of all cards. If the FC adapter on the host or a device attached to the MUX also reports errors, the fiber cable may be defective or not attached. Check the fiber cabling between the MUX and the host. The MUX front panel or serial port user interface may provide additional information. If the problem persists, then check the Fibre Channel network connected to the MUX. The MUX will not respond if it does not have the correct firmware. Firmware with date code 3810 or earlier does not support the polling done by this monitor. If the MUX has 3810 or earlier firmware, then download the latest firmware. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab9113c00000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#209 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: Firmware Revision (Not Available): Each path, for which this event gets generated, will have this same duplicate event number : 329 Manager-Specific Information: Raw Manager Data: 0x0000: 00 02 0x0000: 00 00 00 01 ---------- End Event Monitoring Service Event Notification ----------<Event 210
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description: FC SCSI MUX failed selftest. FC port A failed.
- Probable Cause / Recommended Action:
The FC port of the MUX failed selftest due to failed hardware or improper installation. Check the FC card for proper seating. If the problem persists, then contact HP for replacement of the FC card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:50 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 00:32:50 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 210 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: FC port A failed. Probable Cause / Recommended Action: The FC port of the MUX failed selftest due to failed hardware or improper installation. Check the FC card for proper seating. If the problem persists, then contact HP for replacement of the FC card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673200000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#210 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 581 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0A 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 07 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 E9 A8 40 01 DD A0 76 00 33 61 0x0060: 40 00 FE 24 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 ED C8 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 00 FE 60 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 211
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description:
FC SCSI MUX failed selftest. FC port B failed- Probable Cause / Recommended Action:
The FC port of the MUX failed selftest due to failed hardware or improper installation. Check the FC card for proper seating. If the problem persists, then contact HP for replacement of the FC card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:52 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 00:32:51 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 211 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: FC port B failed. Probable Cause / Recommended Action: The FC port of the MUX failed selftest due to failed hardware or improper installation. Check the FC card for proper seating. If the problem persists, then contact HP for replacement of the FC card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673300000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#211 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 582 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0B 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 08 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 E9 A8 40 01 DD A0 76 00 33 61 0x0060: 40 01 00 2C 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 ED C8 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 01 00 40 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 212
- Severity: Critical
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem.
- Description:
FC SCSI MUX failed selftest. Mother Board (Processor)- Probable Cause / Recommended Action:
The MUX failed selftest. Check seating of all SCSI, FC, and memory cards. Check all of the SCSI cables for proper connection and termination and check the connector screws. If the problem still persists, contact HP for replacement of the motherboard.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:53 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is CRITICAL(5). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 00:32:53 2001 Severity............: CRITICAL Monitor.............: dm_fc_scsi_mux Event #.............: 212 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware problem. Description of Error: Mother board processor failed. Probable Cause / Recommended Action: The MUX failed selftest. Check seating of all SCSI, FC, and memory cards. Check all of the SCSI cables for proper connection and termination and check the connector screws. If the problem still persists, contact HP for replacement of the motherboard. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673500000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#212 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 583 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0C 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 09 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 E9 A8 40 01 DD A0 76 00 33 61 0x0060: 40 00 FF A0 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 ED C8 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 00 FF F0 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 213
- Severity: Information
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Information
- Description:
Code assertion occurred.- Probable Cause / Recommended Action:
The firmware or processor on the MUX has detected a firmware or hardware failure and was in an inconsistent state. The MUX has reset itself. This event does not require a corrective action if it does not reoccur. If this event does reoccur, report this event with its associated data to HP.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:54 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is MINORWARNING(2). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 00:32:54 2001 Severity............: MINORWARNING Monitor.............: dm_fc_scsi_mux Event #.............: 213 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Information Description of Error: Code assertion occurred. Probable Cause / Recommended Action: The firmware or processor on the MUX has detected a firmware or hardware failure and was in an inconsistent state. The MUX has reset itself. This event does not require a corrective action if it does not reoccur. If this event does reoccur, report this event with its associated data to HP. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673600000000 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#213 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 584 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0D 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 0A Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 E9 A8 40 01 DD A0 76 00 33 61 0x0060: 40 01 00 2C 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 ED B0 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 00 FF DC 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 214
- Severity: Major Warning
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware warning.
- Description:
FC SCSI MUX failed selftest. Unknown FRU- Probable Cause / Recommended Action:
The MUX failed selftest but could not determine the exact cause. This event could occur if a fan failure was previously reported, but the fan was not replaced, and another fan failed. Check the fan cables and connectors, and check to see that both fans are operational. Replace the fan assembly if it is found to be defective. If the fan is not defective, the cause may be another MUX component. Report this event with its associated data to HP.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:55 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is INFORMATION(1). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 00:32:55 2001 Severity............: INFORMATION Monitor.............: dm_fc_scsi_mux Event #.............: 214 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware warning. Description of Error: Unknown hardware failure. Probable Cause / Recommended Action: The MUX failed selftest but could not determine the exact cause. This event could occur if a fan failure was previously reported, but the fan was not replaced, and another fan failed. Check the fan cables and connectors, and check to see that both fans are operational. Replace the fan assembly if it is found to be defective. If the fan is not defective, the cause may be another MUX component. Report this event with its associated data to HP. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673700000002 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#214 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 585 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0E 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 10 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 E9 A8 40 01 DD A0 76 00 33 61 0x0060: 40 00 FF C8 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 ED C8 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 01 00 40 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 215
- Severity: Major Warning
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware warning.
- Description:
One of the two FC SCSI MUX fans failed.- Probable Cause / Recommended Action: The fan may have worn out or something may have prevented it from turning or the something may have disconnected one of the fan cables. The FC SCSI MUX will continue to operate as long as the remaining fan provides sufficient cooling. Check the fan cables and connectors. Repair or replace the fan module as soon as possible. A second fan failure may get reported as Unknown FRU event.
- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 01:33:00 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is MAJORWARNING(3). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 01:32:59 2001 Severity............: MAJORWARNING Monitor.............: dm_fc_scsi_mux Event #.............: 215 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : Hardware warning. Description of Error: Fan module failed. Probable Cause / Recommended Action: One of the two MUX cooling fans has failed. The fan may have something blocking it such as the fan cable. The fan may have an improperly installed or disconnected cable. The MUX will continue to operate as long as the remaining fan provides sufficient cooling. Check the fan cables and connectors. Check if both fans run and trouble shoot to find the exact cause. Replace the fan assembly if it is found to be defective. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8754b00000004 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#215 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 5 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 658 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0F 00 00 00 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 02 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 E9 A8 40 01 DD A0 76 00 33 61 0x0060: 40 00 FE 74 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 ED C8 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 00 FF B4 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 216
- Severity: Information
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : FC external loopback test did not pass.
- Description:
FC port A external loopback test Failed.- Probable Cause / Recommended Action:
The FC loopback test has failed. Check for proper installation of the loopback cable. Check to make sure that the FC port cover connector was not used during the test instead of the loopback cable (the FC port cover does not provide loopback capability). Check the FC card for proper seating. Disconnect and reconnect the FC cable and perform the external loopback test again. If the problem persists, contact HP for replacement of the FC card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:49 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Mar 21 00:32:48 2001 Severity............: INFORMATION Monitor.............: dm_fc_scsi_mux Event #.............: 216 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : FC external loopback test did not pass. Description of Error: FC port A external loopback test Failed. Probable Cause / Recommended Action: The FC loopback test has failed. Check for proper installation of the loopback cable. Check to make sure that the FC port cover connector was not used during the test instead of the loopback cable (the FC port cover does not provide loopback capability). Check the FC card for proper seating. Disconnect and reconnect the FC cable and perform the external loopback test again. If the problem persists, contact HP for replacement of the FC card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673000000002 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#216 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 577 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0A 00 00 16 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 03 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 EC 08 40 01 DD A0 76 00 33 61 0x0060: 40 00 FE 10 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 EE 00 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 01 00 68 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 217
- Severity: Information
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : FC external loopback test did not pass.
- Description: FC SCSI MUX failed loopback selftest. FC port B failed
- Probable Cause / Recommended Action:
The FC loopback test has failed. Check for proper installation of the loopback cable. Check to make sure that the FC port cover connector was not used during the test instead of the loopback cable (the FC port cover does not provide loopback capability). Check the FC card for proper seating. Disconnect and reconnect the FC cable and perform the external loopback test again. If the problem persists, contact HP for replacement of the FC card.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 00:32:49 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/8_12.8.0.255.0.5.0 is >= 1. Its current value is INFORMATION(1). User Comments: Test 1/23/01 Event data from monitor: Event Time..........: Wed Mar 21 00:32:49 2001 Severity............: INFORMATION Monitor.............: dm_fc_scsi_mux Event #.............: 217 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 8/12.8.0.255.0.5.0 : FC external loopback test did not pass. Description of Error: FC port B external loopback test Failed. Probable Cause / Recommended Action: The FC loopback test has failed. Check for proper installation of the loopback cable. Check to make sure that the FC port cover connector was not used during the test instead of the loopback cable (the FC port cover does not provide loopback capability). Check the FC card for proper seating. Disconnect and reconnect the FC cable and perform the external loopback test again. If the problem persists, contact HP for replacement of the FC card. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab8673100000002 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#217 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: WWN:20000060b02ae242 Firmware Revision: 4jas Power ons since this event happened: 0 Time since this event happened: 9 day; 4 hour; 34 minute Each path, for which this event gets generated, will have this same duplicate event number : 579 Manager-Specific Information: Raw Manager Data: 0x0000: 00 01 0x0000: 00 00 0B 00 00 16 5D 44 00 04 EE EE 00 00 00 00 0x0010: 00 00 00 00 00 00 00 05 Raw Inquiry Data: 0x0000: 00 00 00 1B 41 2E 30 31 2E 30 30 00 64 6D 5F 66 0x0010: 63 6D 6F 6E 00 69 5F 6D 75 78 00 35 00 00 00 28 0x0020: 2F 76 61 72 2F 74 6D 70 2F 64 6D 5F 66 63 5F 73 0x0030: 00 00 00 3C 00 00 00 02 00 00 00 3C 00 00 00 01 0x0040: 40 01 DD 35 00 00 00 21 00 05 00 00 00 00 00 02 0x0050: 00 00 00 0B 40 01 EC 08 40 01 DD A0 76 00 33 61 0x0060: 40 00 FE 10 00 00 00 21 00 05 00 00 00 00 00 02 0x0070: 00 00 00 0B 40 01 EE 00 40 01 E3 E8 00 00 00 47 0x0080: 00 00 00 00 00 00 00 08 40 01 DD BD 00 00 00 21 0x0090: 00 05 00 00 00 00 00 02 00 00 00 0B 40 01 DD E8 0x00A0: 40 01 DE 30 73 69 5F 6D 40 00 FD D4 00 00 00 49 >---------- End Event Monitoring Service Event Notification ----------<Event 219
- Severity: Major Warning
- Event Class: I/O
- Event Summary: Multiplexor (MUX) at hardware path 10/12.8.0.255.0.4.0 : Hardware warning.
- Description: FC SCSI MUX has started responding.
- Probable Cause / Recommended Action:
The MUX has entered the online condition due one of many possible causes. The MUX may have powered up. The MUX may have been connected or re-connected to the Fibre Channel network. The MUX may have reset itself due to a network event. A problem may have existed in the Fibre Channel network and now does not exist. The MUX may have had firmware with date code 3810 or earlier, replaced by newer firmware. After download with newer firmware, the MUX has the capability to handle polling by this monitor. Normally the MUX and I/O operations will recover automatically from reset. No action is required. This event has the same severity as MUX not responding event so that when one event appears, so can the other.- Event Generation Threshold: 1 occurrence
Event Details:
>------------ Event Monitoring Service Event Notification ------------< Notification Time: Wed Mar 21 13:24:52 2001 hprdstl6 sent Event Monitor notification information: /connectivity/events/multiplexors/FC_SCSI_mux/10_12.8.0.255.0.4.0 is >= 1. Its current value is INFORMATION(1). Event data from monitor: Event Time..........: Wed Mar 21 13:24:52 2001 Severity............: INFORMATION Monitor.............: dm_fc_scsi_mux Event #.............: 219 System..............: hprdstl6.rose.hp.com Summary: Multiplexor (MUX) at hardware path 10/12.8.0.255.0.4.0 : Hardware warning. Description of Error: FC SCSI MUX has started responding. Probable Cause / Recommended Action: The MUX has entered the online condition due one of many possible causes. The MUX may have powered up. The MUX may have been connected or re-connected to the Fibre Channel network. The MUX may have reset itself due to a network event. A problem may have existed in the Fibre Channel network and now does not exist. The MUX may have had firmware with date code 3810 or earlier, replaced by newer firmware. After download with newer firmware, the MUX has the capability to handle polling by this monitor. Normally the MUX and I/O operations will recover automatically from reset. No action is required. This event has the same severity as MUX not responding event so that when one event appears, so can the other. Additional Event Data: System IP Address...: 15.8.135.196 Event Id............: 0x3ab91c2400000002 Monitor Version.....: B.01.01 Event Class.........: I/O Client Configuration File...........: /var/stm/config/tools/monitor/default_dm_fc_scsi_mux.clcfg Client Configuration File Version...: A.01.00 Qualification criteria met. Number of events..: 1 Associated OS error log entry id(s): None Additional System Data: System Model Number.............: 9000/831 EMS Version.....................: A.03.20 STM Version.....................: A.26.00 Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_fc_scsi_mux.htm#219 v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v Component Data: FC Path 1...................: 8/12.8.0.255.0.5.0 FC Path 2...................: 10/12.8.0.255.0.4.0 World Wide Name.............: 0x20000060b02ae242 Product Number..............: HP A3308 Product/Device Information: World Wide Name: 0x20000060-0xB02AE242 MUX Location: Firmware Revision (Not Available): Each path, for which this event gets generated, will have this same duplicate event number : 988 Manager-Specific Information: Raw Manager Data: 0x0000: 00 02 0x0000: 00 00 00 02 >---------- End Event Monitoring Service Event Notification ----------<