HP StorageWorks XPath OS 7.4.X Administrator Guide (AA-RVHDD-TE, February 2006)

XPath OS 7.4.x administrator guide 15
PID mode requirements
Either core port identifier (PID) mode or extended-edge PID mode must be enabled to successfully execute
the XPath OS. In its default configuration, XPath OS has core PID mode enabled.
All switches within a fabric must have the same PID mode enabled. For more information on configuring a
fabric PID mode, see ”Verifying the PID mode” on page 20.
For information on configuring the PID mode in Fabric OS, see the HP StorageWorks Fabric OS 5.x
administrator guide.
NOTE: The PID mode for the MP Router need not match that of the attached fabrics; however, the PID
mode set on the EX_Port must match. To set the PID mode, see ”Setting the PID mode” on page 20.
Feature compatibility
XPath OS does not support the following Fabric OS features:
• The interopMode command. The MP Router segments from a fabric that has interopMode enabled.
See the interopMode command in the HP StorageWorks XPath OS 7.4.x command reference guide
for more information.
• Fabric Watch
• Functionality equivalent to the Open E_Port feature of Fabric OS. The Open E_Port feature permits
Fabric OS to support certain Fibre Channel E_Port extension devices.
In addition, the following differences exist between Fabric OS and XPath OS:
• XPath OS allows longer connections than the native 10 km distance specified by the Fibre Channel
standard. Long-distance connections are configured using the portCfgLongDistance command.
For details, see ”Configuring a long-distance connection” on page 22.
• XPath OS does not maintain an alias server, but the FC-FC routing service makes use of aliases
managed by attached Fabric OS fabrics.
• XPath OS requires that ports be disabled before changing their properties. Ports are disabled by
default. If ports have been enabled, actions that return a port to default settings—such as the
configDefault and portCfgDefault commands—disable the port. Before configuring an
enabled port for multi-protocol routing services, the port must be stopped. See the portDisable and
portStop commands in the HP StorageWorks XPath OS 7.4.x command reference guide for more
information.
Daemon overseer service
Many of the applications running on the MP Router are controlled by daemons. An overseer daemon
monitors the status of the system daemons.
NOTE: The Full Fabric License, which is shipped as standard with the MP Router, is required to bring up
the daemons.
This overseer daemon checks the heartbeat of all the daemons running in the MP Router. If the overseer
fails to receive three consecutive heartbeats, it then informs all the daemons who are interested in the
failure notification.
Once it receives a response from the appropriate daemon, it takes the action specified: either rebooting
the switch or restarting the daemon.
If the notified daemon does not respond within 30 seconds, the overseer then initiates the default action
shown.
The overseer daemon monitors the daemons listed in Table 3.