HP StorageWorks Fabric OS 5.0.0 Features Overview (AA-RW1NA-TE, May 2005)

15Fabric OS 5.0 features overview
Routing policies
All HP StorageWorks models support port-based routing, in which the routing path chosen for
an incoming frame is based only on the incoming port and the destination domain. To
optimize port-based routing, you can enable the Dynamic Load Sharing feature (DLS) to
balance the load across the available output ports within a domain.
The SAN Switch 4/32 model allows you to tune routing performance with these additional
routing policies:
• Device-based routing, in which the choice of routing path is based on the Fibre Channel
addresses of the source device (S_ID) and the destination device (D_ID), improving path
utilization for better performance
• Exchange-based routing, in which the choice of routing path is based on the S_ID, D_ID,
and Fibre Channel originator exchange ID (OXID), optimizing path utilization for the best
performance
Device-based and exchange-based routing require DLS; when these policies are in effect, you
cannot disable the DLS feature.
Using port-based routing, you can assign a static route, in which the path chosen for traffic
never changes. In contrast, device-based and exchange-based routing policies always employ
dynamic path selection.
Message logging
Standard features allow you to display system, port, and specific hardware messages. You
can set up system logging mapping (syslogd), and you can specify that the system
automatically offload diagnostic messages to a server.
The HP StorageWorks Core Switch 2/64 and SAN Director 2/128 models provide a unique
error log on each CP.
Fabric OS also maintains a separate, internal port log of all port activity. You can use this log
to troubleshoot device connections.
Fabric OS CLI
The Fabric OS CLI lets you monitor and manage entire fabrics, individual switches, and ports
from a standard workstation. Using the CLI, you can access the entire suite of Fabric OS
features and capabilities across an entire fabric from a single access point.
A switch-level password for each account controls access (see ”Configurable accounts” on
page 9 for more information). You can perform all configuration and management tasks using
the admin or user role. CLI commands are based on the account role and activated license
keys.