HP StorageWorks 2000 Modular Smart Array Reference Guide (481599-003, August 2008)

Chapter 7 Troubleshooting Using SMU 225
■ No Debug Tracing – Collects no debug data.
■ Custom Debug Tracing – Shows that specific events are selected for inclusion in
the log. This is the default. If no events are selected, this option is not displayed.
3. Click Change Debug Logging Setup.
4. If instructed by service personnel, click Advanced Debug Logging Setup Options
and select one or more additional types of events.
Under normal conditions, you should not select any of these options because they
have a slight impact on read/write performance.
Correcting Enclosure IDs
When installing a system with drive enclosures attached, the enclosure IDs might
differ from the physical cabling order. This is because the controller might have
been previously attached to some of the same enclosures and it attempts to preserve
the previous enclosure IDs if possible. To correct this condition, you can perform a
rescan; see “Scanning for Device Changes” on page 184.
Problems After Power-On or Restart
After powering on the storage system or restarting the MC or SC, the processors
take about 45 seconds to boot up, and the system takes an additional minute or more
to become fully functional and able to process commands from SMU or the CLI.
The time to become fully functional depends on many factors such as the number of
enclosures, the number of disk drives, the number of virtual disks, and the amount
of I/O running at the time of the restart. During this time, some SMU or CLI
commands might fail and some SMU pages may not be available. If this occurs,
wait a few minutes and try again.