Duplicate Port World Wide Name; High Availability Of Daemon Processes; Table 1 Daemons That Are Automatically Restarted - HP SN3000B Administrator's Manual

Duplicate Port World Wide Name

According to Fibre Channel standards, the Port World Wide Name (PWWN) of a device cannot
overlap with that of another device, thus having duplicate PWWNs within the same fabric is an
illegal configuration.
If a PWWN conflict occurs with two devices attached to the same domain, Fabric OS handles device
login in such a way that only one device may be logged in to the fabric at a time. For more
information, refer to
If a PWWN conflict occurs and two duplicate devices are attached to the fabric through different
domains, the devices are removed from the Name Server database and a RASlog is generated.
Device Recovery
To recover devices that have been removed from the Name Server database due to duplicate
PWWNs, the devices must re-login to the fabric. This is true for any device—for example, a device on
an F_Port, NPIV devices, or devices attached to a switch in Access Gateway mode.

High availability of daemon processes

Starting non-critical daemons is automatic; you cannot configure the startup process. The following
sequence of events occurs when a non-critical daemon fails:
1. A RASlog and AUDIT event message are logged.
2. The daemon is automatically started again.
3. If the restart is successful, then another message is sent to RASlog and AUDIT reporting the
4. If the restart fails, another message is sent to RASlog and no further attempts are made to
Schedule downtime and reboot the switch at your convenience.
considered non-critical and are automatically restarted on failure.
TABLE 1
Daemon
arrd
cald
raslogd
rpcd
snmpd
traced
trafd
Fabric OS Administrator's Guide
53-1002446-01
"Configuring FLOGI-time handling of duplicate PWWN"
successful restart status.
restart the daemon.
Daemons that are automatically restarted
Description
Asynchronous Response Router, which is used to send management data to hosts when the switch is
accessed through the APIs (FA API or SMI-S).
Common Access Layer daemon, which is used by manageability applications.
Reliability, Availability, and Supportability daemon logs error detection, reporting, handling, and
presentation of data into a format readable by you and management tools.
Remote Procedure Call daemon, which is used by the API (Fabric Access API and SMI-S).
Simple Network Management Protocol daemon.
Trace daemon provides trace entry date and time translation to Trace Device at startup and when
date/time changed by command. Maintains the trace dump trigger parameters in a Trace Device.
Performs the trace Background Dump, trace automatic FTP, and FTP "aliveness check" if auto-FTP is
enabled.
Traffic daemon implements Bottleneck detection.

High availability of daemon processes

Table 1 lists the daemons that are
1
on page 60.
13