emlxs_messages.h revision 93c20f2609342fd05f6625f16dfcb9348e7977f2
/*
* CDDL HEADER START
*
* The contents of this file are subject to the terms of the
* Common Development and Distribution License (the "License").
* You may not use this file except in compliance with the License.
*
* You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
* See the License for the specific language governing permissions
* and limitations under the License.
*
* When distributing Covered Code, include this CDDL HEADER in each
* file and include the License file at usr/src/OPENSOLARIS.LICENSE.
* If applicable, add the following below this CDDL HEADER, with the
* fields enclosed by brackets "[]" replaced with your own identifying
* information: Portions Copyright [yyyy] [name of copyright owner]
*
* CDDL HEADER END
*/
/*
* Copyright 2008 Emulex. All rights reserved.
* Use is subject to License terms.
*/
#ifndef _EMLXS_MESSAGES_H
#define _EMLXS_MESSAGES_H
#ifdef __cplusplus
extern "C" {
#endif
#ifdef DEF_MSG_REPORT
#else /* DEF_MSG_REPORT */
#ifdef DEF_MSG_STRUCT
#else
extern emlxs_msg_t _name;
#endif /* DEF_MSG_STRUCT */
#endif /* DEF_MSG_REPORT */
/*
*
* LOG Message Types Numbering Sequence
*
* Message Group From
*
* MISC 000
* DRIVER 100 -Driver Attach and Detach events
* INIT 200 -HBA initialization events
* MEM 300
* SLI 400
* MBOX 500
* NODE 600
* LINK 700
* ELS 800
* PKT 900
* FCP 1000
* FCT (FCP Target) 1100
* IP 1200
* SFS 1300
* IOCTL 1400
* FIRMWARE 1500
* CT 1600
* FCSP 1700
* EVENTS 2000
*
*/
#ifdef DEF_MSG_REPORT
typedef struct emlxs_msg_group {
char desc[80];
{
{0, 99, "Miscellaneous Events"},
{100, 199, "Driver Events"},
{200, 299, "HBA Initialization Events"},
{300, 399, "Memory Management Events"},
{400, 499, "Service level Interface (SLI) Events"},
{500, 599, "Mailbox Events"},
{600, 699, "Node Events"},
{700, 799, "Link Events"},
{800, 899, "ELS Events"},
{900, 999, "General I/O Packet Events"},
{1000, 1099, "FCP Traffic Events"},
{1100, 1199, "FCT Traffic Events"},
{1200, 1299, "IP Traffic Events"},
{1300, 1399, "Solaris SFS Events"},
{1400, 1499, "IOCTL Events"},
{1500, 1599, "Firmware Download Events"},
{1600, 1699, "Common Transport Events"},
{1700, 1799, "Fibre Channel Security Protocol (FCSP) Events"},
};
#endif /* DEF_MSG_REPORT */
/* Verbose flags */
#define MSG_RESV18 0x00040000
#define MSG_RESV19 0x00080000
#define MSG_RESV20 0x00100000
#define MSG_RESV21 0x00200000
/* download events (very verbose) */
/* (very verbose) */
/* (very verbose) */
/* (very verbose) */
/* DFC Events */
/* Msg Levels */
#define EMLXS_DEBUG 1
#define EMLXS_NOTICE 2
#define EMLXS_WARNING 3
#define EMLXS_ERROR 4
#define EMLXS_PANIC 5
#define EMLXS_EVENT 6
typedef struct emlxs_msg {
#ifdef DEF_MSG_REPORT
char desc[512];
char action[512];
#endif /* DEF_MSG_REPORT */
} emlxs_msg_t;
/* ACTION defines (common) */
#define ACTION_NONE "No action needed, informational."
#define ACTION_NONE_REP "No action needed, informational." \
" However, if the problem persists," \
" report these errors to your customer" \
" service representative."
#define ACTION_NONE_ADM "No action needed, informational." \
" However, if the problem persists, report" \
" these errors to your system administrator."
#define ACTION_CHK_HSCFG "Check your hardware and software" \
" configuration. If the problem persists," \
" report these errors to your customer" \
" service representative."
#define ACTION_CHK_HCFG "Check your hardware configuration." \
" If the problem persists, report these" \
" errors to your customer service" \
" representative."
#define ACTION_CHK_CONN "Check your network connections." \
" If the problem persists, report these" \
" errors to your system administrator."
#define ACTION_REP "Contact your customer service" \
" representative."
#define ACTION_IMG_REP "Obtain the proper image file." \
" If the problem persists, report these" \
" errors to your customer service" \
" representative."
/* MESSAGE defines */
#ifdef DEF_MSG_REPORT
{
#endif /* DEF_MSG_REPORT */
/*
* GROUP: MISC 000 - 099
*/
DEFINE_MSG(1, \
"", \
EMLXS_DEBUG, \
MSG_MISC, \
"This is a general purpose informational message.", \
DEFINE_MSG(2, \
"", \
EMLXS_NOTICE, \
MSG_MISC, \
"This is a general purpose informational message.", \
DEFINE_MSG(3, \
"", \
MSG_MISC, \
"This is a general purpose warning message.", \
DEFINE_MSG(4, \
"", \
EMLXS_ERROR, \
MSG_MISC, \
"This is a general purpose error message.", \
DEFINE_MSG(5, \
"", \
EMLXS_PANIC, \
MSG_MISC, \
"This is a general purpose panic message.", \
DEFINE_MSG(6, \
"", \
EMLXS_EVENT, \
MSG_MISC, \
"This is a general purpose event message.", \
/*
* GROUP: DRIVER 100 - 199
*/
DEFINE_MSG(100, \
"Driver attach.", \
EMLXS_NOTICE, \
MSG_DRIVER, \
"This indicates that the driver is performing an attach"
" operation.", \
DEFINE_MSG(101, \
"Driver attach failed.", \
EMLXS_ERROR, \
MSG_DRIVER, \
"This indicates that the driver was unable to attach due"
" to some issue.", \
DEFINE_MSG(102, \
"Driver attach.", \
EMLXS_DEBUG, \
MSG_DRIVER, \
"This indicates that the driver is performing a attach"
" operation.", \
DEFINE_MSG(110, \
"Driver detach.", \
EMLXS_NOTICE, \
MSG_DRIVER, \
"This indicates that the driver is performing a detach"
" operation.", \
DEFINE_MSG(111, \
"Driver detach failed.", \
EMLXS_ERROR, \
MSG_DRIVER, \
"This indicates that the driver was unable to detach due"
" to some issue.", \
DEFINE_MSG(112, \
"Driver detach.", \
EMLXS_DEBUG, \
MSG_DRIVER, \
"This indicates that the driver is performing a detach"
" operation.", \
DEFINE_MSG(120, \
"Driver suspend.", \
EMLXS_DEBUG, \
MSG_DRIVER, \
"This indicates that the driver is performing a suspend"
" operation.", \
DEFINE_MSG(121, \
"Driver suspend failed.", \
EMLXS_ERROR, \
MSG_DRIVER, \
"This indicates that the driver was unable to suspend due"
" to some issue.", \
DEFINE_MSG(130, \
"Driver resume.", \
EMLXS_DEBUG, \
MSG_DRIVER, \
"This indicates that the driver is performing a resume"
" operation.", \
DEFINE_MSG(131, \
"Driver resume failed.", \
EMLXS_ERROR, \
MSG_DRIVER, \
"This indicates that the driver was unable to resume due"
" to some issue.", \
/*
* GROUP: INIT 200 - 299
*/
DEFINE_MSG(200, \
"Adapter initialization.", \
EMLXS_NOTICE, \
MSG_INIT, \
"This indicates that the adapter is initializing.", \
DEFINE_MSG(201, \
"Adapter initialization failed.", \
EMLXS_ERROR, \
MSG_INIT, \
"This indicates that an attempt to initialize the adapter"
" has failed.", \
DEFINE_MSG(202, \
"Adapter initialization.", \
EMLXS_DEBUG, \
MSG_INIT, \
"This indicates that the adapter is initializing.", \
DEFINE_MSG(210, \
"Adapter transition.", \
EMLXS_DEBUG, \
MSG_INIT, \
"This indicates that the adapter is changing states.", \
DEFINE_MSG(220, \
"Adapter online.", \
EMLXS_DEBUG, \
MSG_INIT, \
"This indicates that the adapter is online and ready to"
" communicate.", \
DEFINE_MSG(230, \
"Adapter offline.", \
EMLXS_DEBUG, \
MSG_INIT, \
"This indicates that the adapter is offline and unable to"
" communicate.", \
DEFINE_MSG(231, \
"Adapter shutdown.", \
MSG_INIT, \
"This indicates that the adapter has been shutdown and"
" will require a reboot to reinitialize.", \
DEFINE_MSG(240, \
"Adapter reset failed.", \
EMLXS_ERROR, \
MSG_INIT, \
"This indicates that an attempt to reset the adapter has"
" failed.", \
/*
* GROUP: MEM 300 - 399
*/
DEFINE_MSG(300, \
"Memory alloc.", \
EMLXS_DEBUG, \
MSG_MEM, \
"This indicates that the driver allocated system"
" memory.", \
DEFINE_MSG(301, \
"Memory alloc failed.", \
EMLXS_ERROR, \
MSG_MEM, \
"This indicates that the driver was unable to allocate"
" system memory. The system is low on memory"
" resources.", \
DEFINE_MSG(310, \
"Memory pool error.", \
EMLXS_ERROR, \
MSG_MEM, \
"This indicates that a problem has occurred with the"
" memory buffer pool management.", \
DEFINE_MSG(311, \
"Memory pool alloc failed.", \
EMLXS_DEBUG, \
MSG_MEM, \
"This indicates that the driver was unable to allocate"
" memory from one of its own memory pools.", \
"If the problem occurs frequently you may be able to"
" configure more resources for that pool. If this"
" does not solve the problem, report these errors to"
" customer service.")
DEFINE_MSG(320, \
"No unsolicited buffer available.", \
EMLXS_NOTICE, \
MSG_MEM, \
"This indicates that the driver's unsolicited buffer pool"
" is exhausted. The I/O will be dropped and most"
" likely retried by the remote device.", \
"If the problem occurs frequently you may be able to"
" configure more resources for that pool. If this"
" does not solve the problem, report these errors to"
" customer service.")
/*
* GROUP: SLI 400 - 499
*/
DEFINE_MSG(400, \
"Vital Product Data.", \
EMLXS_DEBUG, \
MSG_SLI, \
"This provides vendor specific information about the"
" adapter.", \
DEFINE_MSG(410, \
"Link atten.", \
EMLXS_DEBUG, \
MSG_SLI, \
"This indicates that the adapter has triggered a link"
" attention interrupt.", \
DEFINE_MSG(411, \
"State change.", \
EMLXS_DEBUG, \
MSG_SLI, \
"This indicates that the adapter has changed state.", \
DEFINE_MSG(420, \
"Adapter hardware error.", \
EMLXS_ERROR, \
MSG_SLI, \
"This indicates that an interrupt has occurred and the"
" status register indicates a nonrecoverable hardware"
" error.", \
"This error usually indicates a hardware problem with the"
" adapter. Try running adapter diagnostics. Report"
" these errors to customer service.")
DEFINE_MSG(421, \
"Adapter temperature.", \
EMLXS_NOTICE, \
MSG_SLI, \
"This indicates that the adapter has provided general"
" information about the adapter's temperature.", \
DEFINE_MSG(422, \
"Adapter temperature.", \
MSG_SLI, \
"This indicates that adapter's temperature is too hot.", \
"Check hardware ventilation. Reduce adapter usage."
" Shutdown host system.")
DEFINE_MSG(423, \
"Adapter notice.", \
EMLXS_NOTICE, \
MSG_SLI, \
"This indicates that the adapter has provided general"
" information about the adapter's condition.", \
DEFINE_MSG(424, \
"Adapter warning.", \
MSG_SLI, \
"This indicates that an interrupt has occurred indicating"
" a recoverable adapter error.", \
"This error usually indicates a hardware or firmware"
" firmware levels. Report these errors to customer"
" service.")
DEFINE_MSG(425, \
"Adapter error.", \
EMLXS_ERROR, \
MSG_SLI, \
"This indicates that a recoverable adapter error has"
" occurred.", \
"This error usually indicates a hardware or firmware"
" firmware levels. Report these errors to customer"
" service.")
DEFINE_MSG(430, \
"Ring event.", \
EMLXS_DEBUG, \
MSG_SLI, \
"This indicates that an SLI ring event has occurred.", \
DEFINE_MSG(431, \
"Ring error.", \
EMLXS_DEBUG, \
MSG_SLI, \
"This indicates an SLI ring error is being reported by"
" the adapter", \
DEFINE_MSG(432, \
"Ring reset.", \
EMLXS_DEBUG, \
MSG_SLI, \
"This indicates an SLI ring is being reset.", \
DEFINE_MSG(440, \
"Adapter msg.", \
EMLXS_DEBUG, \
MSG_SLI, \
"This indicates that a message was sent to the driver"
" from the adapter.", \
DEFINE_MSG(450, \
"IOCB invalid.", \
EMLXS_ERROR, \
MSG_SLI, \
"This indicates that an IOCB was received from the adapter"
" with an illegal value. This error could indicate a"
" driver or firmware problem.", \
DEFINE_MSG(451, \
"IOCB queue full.", \
EMLXS_DEBUG, \
MSG_SLI, \
"This indicates that the IOCB queue is full. This will"
" occur during normal operation.", \
DEFINE_MSG(452, \
"IOCB event.", \
EMLXS_DEBUG, \
MSG_SLI, \
"This indicates an IOCB local error event is being"
" reported by the adapter", \
DEFINE_MSG(453, \
"IOCB stale.", \
EMLXS_DEBUG, \
MSG_SLI, \
"This indicates an IOCB completed after its associated"
" packet completed.", \
DEFINE_MSG(460, \
"SLI detail.", \
EMLXS_DEBUG, \
"This provides detailed information about an SLI event.", \
/*
* GROUP: MBOX 500 - 599
*/
DEFINE_MSG(500, \
"Mailbox event.", \
EMLXS_DEBUG, \
MSG_MBOX, \
"This indicates that a mailbox event has occurred.", \
DEFINE_MSG(501, \
"Mailbox detail.", \
EMLXS_DEBUG, \
"This provides detailed information about a mailbox"
" event.", \
DEFINE_MSG(510, \
"Stray mailbox interrupt.", \
EMLXS_DEBUG, \
MSG_MBOX, \
"This indicates that a mailbox command completion"
" interrupt was received and the mailbox is not valid."
" This error could indicate a driver or firmware"
" problem.", \
DEFINE_MSG(520, \
"Mailbox error.", \
EMLXS_DEBUG, \
MSG_MBOX, \
"This indicates that an unsupported or illegal mailbox"
" command was completed. This error could indicate a"
" driver or firmware problem.", \
/*
* GROUP: NODE 600 - 699
*/
DEFINE_MSG(600, \
"Node create.", \
EMLXS_DEBUG, \
MSG_NODE, \
"This indicates that a node has been created for a remote"
" device.", \
DEFINE_MSG(601, \
"Node opened.", \
EMLXS_DEBUG, \
"This indicates that a node has been opened for IO"
" transport.", \
DEFINE_MSG(602, \
"Node create failed.", \
EMLXS_NOTICE, \
MSG_NODE, \
"This indicates that a node create request for a remote"
" device has failed.", \
DEFINE_MSG(603, \
"Node updated.", \
EMLXS_DEBUG, \
MSG_NODE, \
"This indicates that a node has been updated for a remote"
" device.", \
DEFINE_MSG(610, \
"Node destroy.", \
EMLXS_DEBUG, \
MSG_NODE, \
"This indicates that a node has been destroyed for a remote"
" device.", \
DEFINE_MSG(611, \
"Node closed.", \
EMLXS_DEBUG, \
"This indicates that a node has been temporarily closed"
" for IO transport.", \
DEFINE_MSG(612, \
"Node missing.", \
EMLXS_NOTICE, \
MSG_NODE, \
"This indicates that a FCP2 device node has been found"
" missing.", \
DEFINE_MSG(620, \
"Node not found.", \
EMLXS_DEBUG, \
MSG_NODE, \
"This indicates that there was an attempt to send an I/O"
" pkt to an unknown device node. The driver maintains"
" a node table entry for every device it needs to"
" communicate with on the FC network.", \
/*
* GROUP: LINK 700 - 799
*/
DEFINE_MSG(700, \
"Link event.", \
EMLXS_DEBUG, \
"This indicates that a link event has occurred.", \
DEFINE_MSG(710, \
"Link down.", \
EMLXS_NOTICE, \
MSG_LINK, \
"This indicates that the fibre channel link is down to"
" the adapter.", \
DEFINE_MSG(720, \
"Link up.", \
EMLXS_NOTICE, \
MSG_LINK, \
"This indicates that the fibre channel link is up.", \
DEFINE_MSG(721, \
"NPIV Link up.", \
EMLXS_NOTICE, \
MSG_LINK, \
"This indicates that the fibre channel link is up for all"
" virtual ports.", \
DEFINE_MSG(730, \
"Link reset.", \
EMLXS_NOTICE, \
"This indicates that an issue has forced the fibre channel"
" link to be reset.", \
DEFINE_MSG(731, \
"Link reset failed.", \
EMLXS_ERROR, \
"This indicates that an attempt to reset the fibre channel"
" link has failed.", \
/*
* GROUP: ELS 800 - 899
*/
DEFINE_MSG(800, \
"ELS sent. ", \
EMLXS_DEBUG, \
MSG_ELS, \
"This indicates that an ELS command is being sent.", \
DEFINE_MSG(801, \
"ELS comp. ", \
EMLXS_DEBUG, \
MSG_ELS, \
"This indicates that an ELS command completed normally.", \
DEFINE_MSG(810, \
"Stray ELS completion.", \
EMLXS_ERROR, \
MSG_ELS, \
"This indicates that the an ELS command completion was"
" received without issuing a corresponding ELS"
" command. This error could indicate a driver or"
" firmware problem. ", \
DEFINE_MSG(811, \
"Abnormal ELS completion.", \
EMLXS_DEBUG, \
MSG_ELS, \
"This indicates that an ELS command completed with a"
" status error in the IOCB. It could mean the Fibre"
" Channel device on the network is not responding or"
" the Fibre Channel device is not an FCP target. The"
" driver will automatically retry this ELS command if"
" needed.", \
"If the command is a PLOGI or PRLI, and the destination"
" PortID is not an FCP Target, no action is needed."
" Otherwise, check physical connections to Fibre"
" Channel network and the state the remote PortID"
" is in.")
DEFINE_MSG(820, \
"ELS rcvd. ", \
EMLXS_DEBUG, \
MSG_ELS, \
"This indicates that an unsolicited ELS command was"
" received.", \
DEFINE_MSG(821, \
"Unsolicited ELS dropped.", \
EMLXS_DEBUG, \
MSG_ELS, \
"This indicates that an unsolicited ELS command was"
" received and then dropped for some reason.", \
DEFINE_MSG(822, \
"ELS reply.", \
EMLXS_DEBUG, \
MSG_ELS, \
"This indicates that a reply is being sent for an"
" unsolicited ELS command.", \
DEFINE_MSG(830, \
"Invalid ELS command found.", \
EMLXS_ERROR, \
MSG_ELS, \
"This indicates that an ELS command was found with an"
" invalid command code.", \
/*
* GROUP: PKT 900 - 999
*/
DEFINE_MSG(900, \
"Packet abort.", \
EMLXS_NOTICE, \
MSG_PKT, \
"This indicates that an I/O packet is being aborted.", \
DEFINE_MSG(901, \
"Packet abort failed.", \
MSG_PKT, \
"This indicates that an attempt to abort an I/O packet"
" has failed.", \
DEFINE_MSG(910, \
"Packet timeout.", \
EMLXS_DEBUG, \
MSG_PKT, \
"This indicates that an I/O packet has timed out and is"
" being aborted.", \
DEFINE_MSG(911, \
"Ring watchdog.", \
EMLXS_DEBUG, \
MSG_PKT, \
"This indicates that IO(s) are getting stale waiting on a"
" ring tx queue.", \
DEFINE_MSG(912, \
"TXQ watchdog.", \
EMLXS_DEBUG, \
MSG_PKT, \
"This indicates that an IO was found missing from the"
" transmit queue.", \
DEFINE_MSG(920, \
"Packet flush.", \
EMLXS_DEBUG, \
MSG_PKT, \
"This indicates that an I/O packet is being flushed.", \
DEFINE_MSG(921, \
"Packet flushed.", \
EMLXS_DEBUG, \
MSG_PKT, \
"This indicates that an I/O packet has been flushed.", \
DEFINE_MSG(922, \
"Packet flush timeout.", \
EMLXS_NOTICE, \
MSG_PKT, \
"This indicates that an I/O packet flush request has"
" timed out with some I/O packets's still not"
" completed. The driver will attempt to recover by"
" itself.", \
DEFINE_MSG(930, \
"Packet transport failed.", \
EMLXS_NOTICE, \
MSG_PKT, \
"This indicates that an attempt to send an I/O packet"
" failed. The I/O packet will be retried by the upper"
" layer.", \
DEFINE_MSG(931, \
"Packet transport error.", \
EMLXS_ERROR, \
MSG_PKT, \
"This indicates that an error occurred while attempting"
" to send an I/O packet. The I/O packet will likely"
" be failed back to the user application.", \
DEFINE_MSG(932, \
"Packet transport.", \
EMLXS_DEBUG, \
MSG_PKT, \
"This provides additional information about a packet"
" being sent.", \
DEFINE_MSG(940, \
"Packet completion error.", \
EMLXS_DEBUG, \
MSG_PKT, \
"This indicates that an I/O packet was completed with an"
" error status. This can occur during normal"
" operation.", \
/*
* GROUP: FCP 1000 - 1099
*/
DEFINE_MSG(1000, \
"Stray FCP completion.", \
EMLXS_DEBUG, \
MSG_FCP, \
"This indicates that an FCP command completion was"
" received without issuing a corresponding FCP"
" Command. This error could indicate a driver or"
" firmware problem.", \
DEFINE_MSG(1001, \
"FCP completion error.", \
EMLXS_DEBUG, \
MSG_FCP, \
"This indicates that an FCP command completed with an"
" error status. These errors can occur during normal"
" operation.", \
/*
* GROUP: FCT 1100 - 1199
*/
#ifdef SFCT_SUPPORT
DEFINE_MSG(1100, \
"FCT detail.", \
EMLXS_DEBUG, \
"This provides detailed information about the driver's"
" FCT interface.", \
DEFINE_MSG(1110, \
"FCT debug.", \
EMLXS_DEBUG, \
MSG_FCT, \
"This provides general information about the driver's"
" FCT interface.", \
DEFINE_MSG(1120, \
"FCT error.", \
EMLXS_DEBUG, \
MSG_FCT, \
"This indicates a general error has occurred in the"
" driver's FCT interface.", \
DEFINE_MSG(1130, \
"FCT API.", \
EMLXS_DEBUG, \
MSG_FCT_API, \
"This provides an API trace with the driver's FCT"
" interface.", \
#endif /* SFCT_SUPPORT */
/*
* GROUP: IP 1200 - 1299
*/
DEFINE_MSG(1200, \
"IP detail. ", \
EMLXS_DEBUG, \
"This provides detailed information about the driver's"
" IP interface.", \
DEFINE_MSG(1210, \
"Stray IP completion.", \
EMLXS_ERROR, \
MSG_IP, \
"This indicates that the an IP sequence completion was"
" received without issuing a corresponding IP"
" sequence. This error could indicate a driver or"
" firmware problem. ", \
DEFINE_MSG(1211, \
"Abnormal IP completion.", \
EMLXS_DEBUG, \
MSG_IP, \
"This indicates that an IP sequence completed with a"
" status error in the IOCB. It could mean the Fibre"
" Channel device on the network is not responding.", \
DEFINE_MSG(1220, \
"Unsolicited IP dropped.", \
EMLXS_DEBUG, \
MSG_IP, \
"This indicates that an unsolicited IP sequence was"
" received, but was dropped for some reason.", \
DEFINE_MSG(1221, \
"IP recvd.", \
EMLXS_DEBUG, \
MSG_IP, \
"This indicates that an unsolicited IP sequence was"
" received.", \
DEFINE_MSG(1230, \
"Invalid IP sequence found.", \
EMLXS_ERROR, \
MSG_IP, \
"This indicates that an IP sequence was found with an"
" invalid code.", \
/*
* GROUP: SFS 1300 - 1399
*/
DEFINE_MSG(1300, \
"SFS.", \
EMLXS_DEBUG, \
MSG_SFS, \
"This provides general information about the driver's SFS"
" interface.", \
DEFINE_MSG(1301, \
"SFS detail.", \
EMLXS_DEBUG, \
"This provides detailed information about the driver's SFS"
" interface.", \
DEFINE_MSG(1310, \
"Diagnostic error.", \
MSG_SFS, \
"This indicates that a diagnostic request did not complete"
" because of some issue.", \
DEFINE_MSG(1311, \
"ECHO diagnostic completed.", \
EMLXS_DEBUG, \
MSG_SFS, \
"This indicates that an ECHO diagnostic has completed.", \
DEFINE_MSG(1312, \
"ECHO diagnostic failed.", \
MSG_SFS, \
"This indicates that an ECHO diagnostic has failed to"
" return a positive result. This could indicate a"
" connectivity problem with your FC network.", \
DEFINE_MSG(1313, \
"BIU diagnostic completed.", \
EMLXS_DEBUG, \
MSG_SFS, \
"This indicates that an BIU diagnostic has completed.", \
DEFINE_MSG(1314, \
"BIU diagnostic failed.", \
EMLXS_ERROR, \
MSG_SFS, \
"This indicates that an BIU diagnostic has failed to"
" return a positive result. This usually caused by an"
" adapter hardware problem.", \
DEFINE_MSG(1315, \
"POST diagnostic completed.", \
EMLXS_DEBUG, \
MSG_SFS, \
"This indicates that an POST diagnostic has completed.", \
DEFINE_MSG(1316, \
"POST diagnostic failed.", \
EMLXS_ERROR, \
MSG_SFS, \
"This indicates that an POST diagnostic has failed to"
" return a positive result. This is usually caused by"
" an adapter hardware problem.", \
/*
* GROUP: IOCTL 1400 - 1499
*/
DEFINE_MSG(1400, \
"IOCTL.", \
EMLXS_DEBUG, \
MSG_IOCTL, \
"This provides general information about the driver's"
" IOCTL interface.", \
DEFINE_MSG(1401, \
"IOCTL detail.", \
EMLXS_DEBUG, \
"This provides detailed information about the driver's"
" IOCTL interface.", \
DEFINE_MSG(1410, \
"DFC", \
EMLXS_DEBUG, \
MSG_IOCTL, \
"This provides general information about the driver's"
" DFC interface.", \
DEFINE_MSG(1411, \
"DFC detail.", \
EMLXS_DEBUG, \
"This provides detailed information about the driver's"
" DFC interface.", \
DEFINE_MSG(1420, \
"DFC Error.", \
EMLXS_DEBUG, \
MSG_IOCTL, \
"This indicates that an error was found while processing a"
" DFC request.", \
/*
* GROUP: FIRMWARE 1500 - 1599
*/
DEFINE_MSG(1500, \
"Firmware image.", \
EMLXS_DEBUG, \
MSG_FIRMWARE, \
"This provides information about the firmware image.", \
DEFINE_MSG(1501, \
"Firmware detail.", \
EMLXS_DEBUG, \
"This provides detailed information about the firmware"
" image.", \
DEFINE_MSG(1502, \
"Firmware Library", \
EMLXS_NOTICE, \
MSG_DRIVER, \
"This shows the versions of firmware contained in the"
" driver's library.", \
DEFINE_MSG(1510, \
"Bad firmware image.", \
EMLXS_ERROR, \
MSG_FIRMWARE, \
"This indicates that a bad firmware image was provided"
" to the download function.", \
DEFINE_MSG(1511, \
"Firmware image not compatible.", \
EMLXS_ERROR, \
MSG_FIRMWARE, \
"This indicates that the firmware image provided was not"
" compatible with the existing hardware.", \
DEFINE_MSG(1520, \
"Firmware download.", \
EMLXS_NOTICE, \
MSG_FIRMWARE, \
"This indicates that an attempt to download a firmware"
" image has occurred.", \
DEFINE_MSG(1521, \
"Firmware download complete.", \
EMLXS_NOTICE, \
MSG_FIRMWARE, \
"This indicates that an attempt to download a firmware"
" image was successful.", \
DEFINE_MSG(1522, \
"Firmware download failed.", \
EMLXS_ERROR, \
MSG_FIRMWARE, \
"This indicates that an attempt to download a firmware"
" image was failed.", \
/*
* GROUP: CT 1600 - 1699
*/
DEFINE_MSG(1600, \
"CT sent. ", \
EMLXS_DEBUG, \
MSG_CT, \
"This indicates that an CT command is being sent.", \
DEFINE_MSG(1601, \
"CT comp. ", \
EMLXS_DEBUG, \
MSG_CT, \
"This indicates that an CT command completed normally.", \
DEFINE_MSG(1610, \
"Stray CT completion.", \
EMLXS_ERROR, \
MSG_CT, \
"This indicates that the an CT command completion was"
" received without issuing a corresponding CT command."
" This error could indicate a driver or"
" firmware problem. ", \
DEFINE_MSG(1611, \
"Abnormal CT completion.", \
EMLXS_DEBUG, \
MSG_CT, \
"This indicates that an CT command completed with a status"
" error in the IOCB. It could mean the Fibre Channel"
" device on the network is not responding. The"
" driver will automatically retry this CT command"
" if needed.", \
"Check physical connections to Fibre Channel network "
" and the state the remote PortID is in.")
DEFINE_MSG(1620, \
"CT rcvd. ", \
EMLXS_DEBUG, \
MSG_CT, \
"This indicates that an unsolicited CT command was"
" received.", \
DEFINE_MSG(1621, \
"Unsolicited CT dropped.", \
EMLXS_DEBUG, \
MSG_CT, \
"This indicates that an unsolicited CT command was"
" received and then dropped for some reason.", \
DEFINE_MSG(1622, \
"CT reply.", \
EMLXS_DEBUG, \
MSG_CT, \
"This indicates that a reply is being sent for an"
" unsolicited CT command.", \
DEFINE_MSG(1630, \
"Invalid CT command found.", \
EMLXS_ERROR, \
MSG_CT, \
"This indicates that an CT command was found with an"
" invalid command code.", \
/*
* GROUP: FC-SP (DHCHAP) 1700 - 1799
*/
#ifdef DHCHAP_SUPPORT
DEFINE_MSG(1700, \
"FCSP", \
EMLXS_DEBUG, \
MSG_FCSP, \
"This provides general information about the driver's FCSP"
" interface.", \
DEFINE_MSG(1701, \
"FCSP detail.", \
EMLXS_DEBUG, \
"This provides detailed information about the driver's"
" FCSP interface.", \
DEFINE_MSG(1702, \
"FCSP error.", \
EMLXS_DEBUG, \
MSG_FCSP, \
"This indicates that an error was found while processing"
" a DFC request.", \
DEFINE_MSG(1705, \
"FCSP state.", \
EMLXS_DEBUG, \
MSG_FCSP, \
"This indicates that an authentication state is"
" changing.", \
DEFINE_MSG(1706, \
"FCSP event", \
EMLXS_DEBUG, \
MSG_FCSP, \
"This indicates that an authentication event has"
" occurred.", \
DEFINE_MSG(1707, \
"FCSP status.", \
EMLXS_DEBUG, \
MSG_FCSP, \
"This indicates that an authentication status is being"
" updated.", \
DEFINE_MSG(1710, \
"FCSP start.", \
EMLXS_DEBUG, \
MSG_FCSP, \
"This indicates that authentication is being started to a"
" specific node.", \
DEFINE_MSG(1720, \
"FCSP comp. ", \
EMLXS_DEBUG, \
MSG_FCSP, \
"This indicates that authentication is being stopped or"
" completed to a specific node.", \
#endif /* DHCHAP_SUPPORT */
/*
* GROUP: EVENT 2000 - 2099
*/
DEFINE_MSG(2000, \
"Link.", \
EMLXS_EVENT, \
EVT_LINK, \
"This indicates that a link event has occurred.", \
DEFINE_MSG(2010, \
"RSCN.", \
EMLXS_EVENT, \
EVT_RSCN, \
"This indicates that an unsolicited RSCN command was"
" received.", \
DEFINE_MSG(2020, \
"CT.", \
EMLXS_EVENT, \
EVT_CT, \
"This indicates that an unsolicited CT command was"
" received.", \
DEFINE_MSG(2030, \
"DUMP", \
EMLXS_EVENT, \
EVT_DUMP, \
"This indicates that an HBA core dump has occurred.", \
DEFINE_MSG(2040, \
"TEMP", \
EMLXS_EVENT, \
EVT_TEMP, \
"This indicates that an adapter temperature event has"
" occurred.", \
DEFINE_MSG(2050, \
"FCOE", \
EMLXS_EVENT, \
EVT_FCOE, \
"This indicates that an adapter FCOE event has"
" occurred.", \
#ifdef DEF_MSG_REPORT
}; /* emlxs_message[] */
#endif /* DEF_MSG_REPORT */
#ifdef __cplusplus
}
#endif
#endif /* _EMLXS_MESSAGES_H */