FW V06.XX/HAFM SW V08.02.00 HP StorageWorks Director Element Manager User Guide (AA-RTDUC-TE, July 2004)
Table Of Contents
- Contents
- About this Guide
- Overview
- Feature Keys
- Managing the Director
- Element Manager Description
- Using the Element Manager
- Backing Up and Restoring Element Manager Data
- Monitoring and managing the Director
- Hardware View
- Port Card View
- Port List View
- Node List View
- Performance View
- FRU List View
- Port Operational States
- Link Incident Alerts
- Threshold Alerts
- Configuring the Director
- Configuring Identification
- Configuring Management Style
- Configuring Operating Parameters
- Configuring a Preferred Path
- Configuring Switch Binding
- Configuring Ports
- Configuring Port Addresses (FICON Management Style)
- Configuring an SNMP Agent
- Configuring Open Systems Management Server
- Configuring FICON Management Server
- Configuring Feature Key
- Configuring Date and Time
- Configuring Threshold Alerts
- Creating New Alerts
- Figure 49: Configure Threshold Alert(s) dialog box
- Figure 50: New Threshold Alerts dialog box - first screen
- Figure 51: New Threshold Alerts dialog box - second screen
- Figure 52: New Threshold Alerts dialog box - third screen
- Figure 53: New Threshold Alerts dialog box - summary screen
- Figure 54: Configure Threshold Alerts dialog box - alert activated
- Modifying Alerts
- Activating or Deactivating Alerts
- Deleting Alerts
- Creating New Alerts
- Configuring Open Trunking
- Exporting the Configuration Report
- Enabling Embedded Web Server
- Enabling Telnet
- Backing Up and Restoring Configuration Data
- Using Logs
- Using Maintenance Features
- Optional Features
- Information and Error Messages
- Index

Monitoring and managing the Director
103Director Element Manager User Guide
Error Statistics
Port errors indicate that a port is not operating correctly. Use this data to isolate
problems with port and link operations. Error statistics include:
■ Link failures—A link failure was recorded in response to a not operational
sequence (NOS), protocol timeout, or port failure. At the Port Card View, a
yellow triangle displays to indicate a link incident, or a blinking red and
yellow diamond displays to indicate a port failure.
■ Sync losses—A loss of synchronization was detected because the attached
device was reset or disconnected from the port. At the Port Card View, a
yellow triangle displays to indicate a link incident.
■ Signal losses—A loss of signal was detected because the attached device was
reset or disconnected from the port. At the Port Card View, a yellow triangle
displays to indicate a link incident.
■ Primitive sequence errors—An incorrect primitive sequence was received
from the attached device, indicating a Fibre Channel link-level protocol
violation. At the Port Card View, a yellow triangle displays to indicate a link
incident.
■ Discarded frames—A received frame could not be routed and was discarded
because the frame timed out (insufficient buffer-to-buffer credit) or the
destination device was not logged into the director.
■ Invalid transmission words—The number of times that the director detected
invalid transmission words from the attached device. This indicates that a
frame or primitive sequence arrived at the director’s port corrupted. This
corruption can be due to the attached device performing a reset, plugging or
unplugging the link, bad optics at either end of the cable, bad cable, or a dirty
or poor connection. Moving the connection around or replacing cables can
isolate the problem.
Some number of invalid transmission words are expected and acceptable.
Invalid transmission words within a frame are used to produce the bit-error
threshold link incident. If one or more invalid transmission words are detected
in 12 separate 1.5-second samples within 5 minutes, a bit-error threshold link
incident is generated.
■ CRC errors—A received frame failed a cyclic redundancy check (CRC)
validation, indicating the frame arrived at the director’s port corrupted. Frame
corruption may be caused by device disconnection, an optical transceiver
failure at the device, a bad fiber-optic cable, or a poor cable connection.