
Driver for Linux -Troubleshooting Section Page 144
elx_mes0932: FIND node did <did> NOT FOUND
DESCRIPTION: The driver was searching for a node table entry based on the DID and the entry was not
found.
DATA: (1) order
SEVERITY: Information
LOG: LOG_NODE verbose
ACTION: None required.
FCP Target Mode Events (1100 - 1199)
1100 TMi message: LUN <lunNum> RDY blk <blkCnt> byt <byteCnt>
DESCRIPTION: Display TGTM LUN Ready status followed by the number of '512-byte' blocks and the
total number of bytes.
DATA: none
SEVERITY: information
LOG: LOG_TGTM verbose
MODULE: fctarget.c
ACTION: None required.
1101 TMi message: Line <num> HBA <num> has <num> LUNs cfg'd
DESCRIPTION: The number of LUNs that were successfully configured by configuration line <num> on
HBA <num>.
DATA: none
SEVERITY: information
LOG: LOG_TGTM verbose
MODULE: fc<LINUX>fcp.c
ACTION: None required.
1102 TMi message: No LUNs configuration'd by line <num> on HBA <num>
DESCRIPTION: No LUNs were configured by the specified configuration line.
DATA: none
SEVERITY: information
LOG: LOG_TGTM verbose
MODULE: fc<LINUX>fcp.c
ACTION: If this configuartion is not intended, check the LUN configuration on the specified configuration
line.
1103 TMc message: Config line <num> starting LUN number <num> should be odd
DESCRIPTION: The starting LUN number on the specified configuration line is not odd.
DATA: none
SEVERITY: error config
LOG: always
MODULE: fc<LINUX>fcp.c
ACTION: Check the LUN configuration on the specified configuration line. The LUN sequence mode is
odd, therefore the starting LUN number must be odd.
Comentarios a estos manuales