
Driver for Linux -Troubleshooting Section Page 112
elx_mes0215: RSCN received
DESCRIPTION: An RSCN ELS command was received from a fabric and processed.
DATA: (1) fc_flag (2) cnt (3) fc_rscn_id_cnt (4) fc_ffstate
SEVERITY: Information
LOG: LOG_DISCOVERY verbose
ACTION:No action needed, informational.
elx_mes0216: Assign scandown scsi id <sid> to NPort <nlp_DID>
DESCRIPTION: A scsi id is assigned due to BIND_ALPA.
DATA: ((1) nlp_bind_type (2) nlp_flag (3) nlp_state (4) nlp_rpi
SEVERITY: Information
LOG: LOG_DISCOVERY | LOG_FCP verbose
ACTION: No action needed, informational.
elx_mes0217: Unknown Identifier in RSCN payload
DESCRIPTION: Typically the identifier in the RSCN payload specifies a domain, area or a specific
NportID. If neither of these are specified, a warning will be recorded.
DATA: (1) didp->un.word
SEVERITY: Error
LOG: Always
ACTION: Potential problem with Fabric. Check with Fabric vendor.
elx_mes0218: FDMI Request
DESCRIPTION: The driver is sending an FDMI request to the fabric.
DATA: (1) fc_flag (2) hba_state (3) cmdcode
SEVERITY: Information
LOG: LOG_DISCOVERY verbose
ACTION: No action needed, informational.
elx_mes0219: Issue FDMI request failed
DESCRIPTION: Cannot issue FDMI request to HBA.
DATA: (1) cmdcode
SEVERITY: Information
LOG: LOG_DISCOVERY verbose
ACTION: No action needed, informational.
elx_mes0220: FDMI rsp failed
DESCRIPTION: An error response was received to FDMI request.
DATA:(1) SWAP_DATA16(fdmi_cmd)
SEVERITY: Information
LOG: LOG_DISCOVERY verbose
ACTION: The fabric does not support FDMI, check fabric configuration.
Comentarios a estos manuales