Mac OS X Fibre Channel connectivity to the HP StorageWorks Enterprise Virtual Array storage system configuration guide (5697-0025, August 2009)

Figure 27 Sample ASP output
To view ASP output:
1. Click the Apple icon in the top left corner of the screen.
2. Click More info.
3. Select File > Save as and enter the file name and directory in which to save the file.
ATTOCelerityFCLog utility
The Celerity FC host adapter driver does not use the system log to communicate driver events because
it has limited resources and events are easily lost. Instead, the driver logs events internally; you can
retrieve them using the ATTOCelerityFCLog utility.
It is difficult to predict the number of events, but the driver's internal event log should be large enough
to hold all events from the time the driver is loaded until the time ATTOCelerityFCLog is run. If the
event log becomes full, the driver continues to log events, overwriting the earliest events with the most
recent events. If event data is lost, ATTOCelerityFCLog displays ...Lost X bytes..., where X
is the number of bytes lost.
The ATTOCelerityFCLog utility displays events as they are logged by the driver. You can set the utility
as a startup item to always retrieve events in the background, but this can cause a slight performance
degradation.
When events are retrieved and displayed, they cannot be redisplayed, even if they are not overwritten
by subsequent events. If you want to save events for future reference, save the Terminal output or use
standard redirection when starting ATTOCelerityFCLog to save the output to a file.
Each event begins with a channel identifier, Channel X.Y.Z, where X is the PCI bus number, Y is the
PCI device number, and Z is the PCI function number. Driver initialization messages can be logged
before this information is available.
You can specify the types of events that are logged using the -e System NVRAM option. Each bit
in the mask corresponds to a group of related messages.
Troubleshooting the Celerity FC host adapter54