Table 162 Known Device Issues (continued)
Device | Software | Description |
|
|
|
SGI IRIX host | CXFS file | The management server can only monitor CXFS file systems |
| systems | from the host generating the input/output. For example, |
|
| assume the elements are part of a CXFS file system. When you |
|
| generate input/output into the metadata server into /folder, |
|
| only the metadata server is able to monitor the file system. For |
|
| example, assume the metadata server generates 100 KB write, |
|
| the management server displays 0 KB write for /folder on |
|
| the metadata client. |
|
| |
|
| more information. |
|
|
|
Solaris host | Sun SAN | The bindings page reports a SCSI number that comes from the |
| Foundation | HBAAPI. This number cannot be seen by the user. For example |
| Suite driver | SCSI target 267008 does not correlate to anything. |
| (Leadville |
|
| driver) |
|
|
|
|
Solaris host | HDLM | If you sync the Solaris host by itself without the switches and |
|
| storage, the storage volume page reports all drive types as |
|
| local. |
|
| Once you discover the host with the switches and storage, it |
|
| reports its drives as being external. It reports the same result |
|
| with |
|
|
|
Solaris host | HDLM | Solaris HDLM disks cannot be monitored. If you try monitoring |
|
| them, the management server displays a message saying |
|
| “data is late or an error occurred.” |
|
|
|
Solaris host | HDLM | If you do a Discovery Data Collection for the host by itself, on |
|
| the bindings page, the controller number begins with |
|
| example, |
|
| Perform Discovery Data Collection on the host with storage and |
|
| switches. The controller numbers are displayed correctly. |
|
|
|
724 Troubleshooting