HP NetServer AA 4000 HP NetServer AA 6200 Solution Release 3.0 Messages - Page 19
Message Summary, Table 1-4HP NetServer AA Message Summary
View all HP NetServer AA 4000 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 19 highlights
Chapter 1 Introduction Variable logDevName MICx offendingValue phyDevName provName sourceIOP Tuplex x y Table 1-3Message Variables (Continued) Description A logical device name. A logical device name is an abstract representation of the mirrored drives that comprise a mirrored disk set. For example, for two physical disks that comprise a mirror set at physical SCSI settings 0-0-1-0 (IOP1 disk at SCSI settings (0-0-1-0) and IOP2 disk at SCSI settings (0-0-1-0)), the logical device name is Disk0; the next mirror set would have a logical device name of Disk1. A Marathon Interface Card (MIC) identifier. The offending value. This field displays the invalid value that was detected. See the message description for details. A physical device name. A physical device comprises one half of a mirror set. A mirror set requires two SCSI devices, one on each IOP. An example of a physical device name is: Disk (0-0-1-0). The provider name. A provider is a software entity that provides some service. For example, a SCSI provider provides access to SCSI devices, and an Ethernet provider provides access to Ethernet devices. The source IOP. The IOP that is the source of a mirror set copy. Either IOP1 or IOP2. A tuple identifier. Either Tuple 1 or Tuple 2. See Variable description for details. See Variable description for details. Message Summary Table 1-4 and Table 1-5 list all HP NetServer AA messages in alphabetical order. The unprefixed messages appear in Table 1-4, and the prefixed messages appear in Table 1-5. Use the hot links to jump to the message documentation, with complete information about a message. Table 1-4HP NetServer AA Message Summary - Unprefixed Messages Message A critical error occurred initializing the Keyboard Pointer Redirector. A datatype entry in the MTCSMAPI.DLL contains incorrect data. Page page 160 page 373 9