configuring celerra events and notifications - dell emc · pdf file4 of 138 version 5.6...

1 of 138

ContentsIntroduction to events and notifications . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4Cautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Events and notifications concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5How events and notifications work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Simple Network Management Protocol . . . . . . . . . . . . . . . . . . . . . . .15

System requirements for events and notifications . . . . . . . . . . . . . . . . .17E-Lab Interoperability Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

User interface choices for events and notifications. . . . . . . . . . . . . . . . .18Roadmap for configuring events and notifications . . . . . . . . . . . . . . . . .19Configure DNS on the Control Station. . . . . . . . . . . . . . . . . . . . . . . . . . . .20Check if email is working properly before configuring notifications . . .21Configuring email notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Enable email notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Configure email notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Display an email notifications configuration . . . . . . . . . . . . . . . . . . .25Sample email notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Test an email notification configuration. . . . . . . . . . . . . . . . . . . . . . .26Disable email notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Re-initialize email notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Gathering required information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Determine facilities in a component that generate events . . . . . . . .29Determine events associated with a facility . . . . . . . . . . . . . . . . . . .30Locate more information about an event . . . . . . . . . . . . . . . . . . . . . .31Determine a list of all possible actions . . . . . . . . . . . . . . . . . . . . . . .32Determine which events trigger an action . . . . . . . . . . . . . . . . . . . . .33

Configuring SNMP trap notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Modify the Celerra MIB file for SNMP traps . . . . . . . . . . . . . . . . . . . .34Configure SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Send a test SNMP trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Receive a test SNMP trap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Configure SNMP on Data Movers . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Customizing notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Create a configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Configuring Celerra Events andNotifications

P/N 300-004-167Rev A04

Version 5.6October 2010

Configuring Celerra Events and NotificationsVersion 5.6 2 of 138

Load a configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Verify the configuration file loaded . . . . . . . . . . . . . . . . . . . . . . . . . .43

SNMP traps and email notifications: Examples . . . . . . . . . . . . . . . . . . . .44When file system usage exceeds certain limits. . . . . . . . . . . . . . . . .44When a SnapSure SavVol usage reaches its high water mark. . . . .49When there are Virus Checker events . . . . . . . . . . . . . . . . . . . . . . . .53When a hard or soft quota is exceeded . . . . . . . . . . . . . . . . . . . . . . .57

Change the SNMP port where SNMP traps are sent. . . . . . . . . . . . . . . . .61Event notification actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Where to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Email notifications not received . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Check if sendmail is running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Configure sendmail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Notifications missing or not working . . . . . . . . . . . . . . . . . . . . . . . . .65SNMP security issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Related information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Customer training programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68Appendix A: Specify an email subject line . . . . . . . . . . . . . . . . . . . . . . . .69Appendix B: Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137

3 of 138Version 5.6Configuring Celerra Events and Notifications

Introduction to events and notificationsThe EMC® Celerra® Network Server generates events to record errors, commands, and other information you might need to know. You can configure the Celerra Network Server to perform an action when specified events occur. Actions based on events are called notifications. Notifications the system can perform include, but are not limited to, logging the event in an event log file, sending an email, or generating a Simple Network Management Protocol (SNMP) trap.

This document is part of the Celerra Network Server information set and is intended for system administrators responsible for configuring and maintaining file storage and network retrieval infrastructure. This section includes some terminology and restrictions that you should be familiar with before you configure or modify network settings.

TerminologyThe Celerra Glossary provides a complete list of Celerra terminology.

alert: In Celerra Manager, a system event that requires administrative attention. These events may be severe enough to cause a system error or disrupt user access.

event: System-generated message caused by a command, an error, or some other condition that may require action by an administrator. Events are typically written to an event log, and may trigger an event notification.

event log: File of system-generated messages based on meeting a condition of a particular severity level. There are separate event logs for the Control Station and for each physical and virtual Data Mover in the system.

event notification: Process by which specified events meeting a severity threshold trigger an action or notification. See also notification.

facility: Component of a Celerra system that monitors the system and generates an event when a certain condition is detected.

Management Information Base (MIB): Hierarchical database maintained by an agent that a network management station can query, using a network management protocol such as the SNMP.

network management station (NMS): Systems that execute management applications, such as SNMP commands to monitor and control network elements.

notifications: Actions the Control Station takes in response to particular events. Some possible actions include sending an email message or an SNMP trap. There are two types of notifications: event notifications, which are notifications based on predefined system events, such as a temperature being too high, and resource notifications, which are notifications based on user-specified resource usage limits or thresholds.

Simple Network Management Protocol (SNMP): Method used to communicate management information between the network management stations and the agents in the network elements.

../../mergedprojects/Glossary/index.htm

Configuring Celerra Events and Notifications4 of 138 Version 5.6

SNMP agent: Software module in a managed device, such as a Celerra Network Server or Symmetrix storage system, that maintains local management information and delivers that information to a manager using SNMP.

SNMP community: Name for the SNMP transaction with a remote system. This is used as a password to control access to the SNMP MIB.

SNMP trap: Asynchronous message sent from an SNMP agent to an SNMP management program. Traps are typically used to report errors. A Celerra Network Server can be configured to send SNMP traps when specified events occur. See event notification.

RestrictionsEmail notifications are dependent on external email servers. Some email servers might require you to register the Control Station hostname in DNS.

CautionsIf any of this information is unclear, contact your EMC Customer Support Representative for assistance.

SNMP security is based on community strings. SNMP version 1 (SNMPv1) transmits all information in clear text. Anyone monitoring the network can obtain the SNMP community name from passing traffic. RFC 1157 provides details about SNMPv1 security.


Events and notifications conceptsYou can monitor and manage the Celerra Network Server, including Data Movers and file systems, with events and notifications. The Celerra Network Server generates events as a result of system changes, some of which might be severe enough to cause an error or disrupt user access. By using notifications, you can specify a variety of actions, such as sending an email, triggering an SNMP trap, or running a script in response to these events.


How events and notifications workThe following sections provide background about using events and notifications on the Celerra Network Server.

EventsCelerra Network Servers generate events in response to specific changes in the state of the system caused by a command, an error, or some other condition that might require action by an administrator. For example, an event is generated when any of the following occur:

◆ A Data Mover restarts

◆ A network interface card (NIC) fails

◆ A file system reaches its soft or hard quota limit

◆ A SnapSure™ save volume exceeds its limit and becomes inactive

◆ A virus checker server becomes unavailable

The file /nas/sys/nas_eventlog.cfg specifies default notifications (actions) that occur as a result of events. "Customizing notifications" on page 41 provides information about setting up customized events and notifications.

Note: Do not edit the files /nas/sys/nas_eventlog.cfg and /nas/site/nas_eventlog.cfg. Edits to /nas/sys/nas_eventlog.cfg will be lost during software upgrades. The file /nas/site/nas_eventlog.cfg contains the list of configuration files currently loaded into the event handler. The directory /nas/site contains local event configuration files which are preserved during software upgrades. Create any new customized notification configuration files in this directory.

FacilitiesThe source of an event is called the event facility. The facility is the part of the Celerra system that generated the event. Each facility has a unique facility identifier (facility ID). For example, the UFS facility (facility ID 64) monitors file system quotas. If a quota is reached, an event is generated with a facility value of UFS.

Each event has component and facility IDs associated with it. The component ID specifies the area of the system from which the event was generated. The facility ID specifies a more specific subsystem within that component. Table 1 on page 6 lists IDs, components, and component definitions.

Table 1 IDs and components (page 1 of 2)

ID Component Component definition

1 DART (Data Access in Real Time)

On a Celerra system, the operating system software that runs on the Data Mover. It is a realtime, multithreaded operating system optimized for file access, while providing service for standard protocols.


The facilities that generate events can change from release to release. Table 2 on page 7 lists the facilities that generate events in the 5.6 release.

2 CS_CORE The core software running on the Control Station.

5 XML_API An application programming interface to the Control Station that uses Extensible Markup Language (XML).

6 CS_PLATFORM Scripts and other NAS service software running on the Control Station.

Table 2 Celerra event facilities (page 1 of 5)

Facility name Facility ID Component Description

ACLUPD 101 DART Access control list (ACL) database events.

ADMIN 24 DARTCS_PLATFORM

Miscellaneous administrative and configuration events.

APIQuotaCache 7 XML_API Quota cache events for XML API v2, the public API for Celerra management.

BoxMonitor 131 CS_PLATFORM Hardware events. Monitors status of operating system on each Data Mover or blade. Also monitors enclosure hardware for NSX systems. See also the CHAMII facility.

CAM 26 DART The Common Access Method layer of the Celerra software provides the raw I/O communications to the data storage device. CAM events typically mean there is a failure to communicate correctly with the storage processing components.

Table 1 IDs and components (page 2 of 2)

ID Component Component definition


CEPP 146 DART Celerra Event Publishing and Processing (CEPP) events. CEPP is a mechanism by which applications can register to receive event notification and context from a Data Mover. The events in this facility include only issues with CEPP itself; they do not include the events sent to registered applications.

CFS 27 DARTCS_PLATFORM

Events associated with file system usage such as built-in usage thresholds and file system auto-extension.

CHAMII 86 DART Monitors the hardware events of NS series Data Movers and their enclosures. Formerly known as CHAMIIENCMON.

Checkup 142 CS_PLATFORM NAS checkup events. The nas_checkup utility periodically runs a series of system health checks on the Celerra and reports the problems found and the actions needed to fix them.

CIC 109 CS_CORE Celerra interconnect events. Events associated with the internal communication between Data Movers or Control Stations or both.

CommandService 9 CS_CORE Control Station command service daemon events. The Command Service daemon manages a number of administrative commands.

ConnectHome 133 CS_PLATFORM ConnectHome events. The ConnectHome mechanism calls or emails EMC Customer Service automatically if a problem occurs.

DBMS 122 DARTCS_CORE

Database Management System events for Celerra configuration data.

DNS 118 DART Domain Name System events.

DPSVC 111 DART Data Protection service events for iSCSI Replicator, file systems, and VDM. Used for Replicator V2.




DRIVERS 36 DART Device driver (for example: network ports, fibre ports) events.

EmailUser 144 CS_PLATFORM Email user notification events.

EventLog 130 CS_PLATFORM Control Station event log events.

FCP 102 DART Low-level Fibre Channel SCSI driver events.

FSTOOLS 40 DARTCS_PLATFORM

File system consistency events.

IP 43 DART Internet Protocol events.

JServer 135 CS_PLATFORM Celerra Monitoring Agent (JServer) events. The Celerra Monitoring Agent monitors all storage usage, storage projection, and Data Mover Load notifications, so events triggered by any of these notifications come from this facility.

KERNEL 45 DART Events associated with the operating system of a Data Mover.

LocalHardwareMonitor 139 CS_PLATFORM Control Station hardware events.

LOCK 68 DART File lock manager events. The file lock manager handles file locking for all file access protocols (NFS, CIFS, and so on).

LogCollect 141 CS_PLATFORM Automatic log collection and transfer events.

MasterControl 129 CS_PLATFORM Control Station software events. The Master Control service manages several services on the Control Station.

MGFS 75 DARTCS_PLATFORM

Celerra Data Migration Service (CDMS) migration file system events or FileMover events.

NASDB 137 CS_PLATFORMCS_CORE

NAS database events.

NaviEventMonitor 138 CS_PLATFORM EMC CLARiiON® events.




NDMP 51 DARTCS_PLATFORM

Network Data Management Protocol (backup) events.

NETLIB 73 DART Network Information Service events.

NFS 52 DART Network File System events.

PERFSTATS 144 DART Statistics Network Service (statmonService) events. The Statistics Network Service collects and reports on various system statistics.

RCPD 83 DART Remote Copy Protocol Daemon events for iSCSI Replicator, file systems, and VDM. Used for Replicator V2.

RDFChannel 11 CS_CORE Remote Data Facility (RDF) Service events. The RDF Channel service processes requests coming in from the RDF channel of the Data Mover.

REP 108 DARTCS_CORE

Replication events for iSCSI Replicator, file systems, and VDM. Used for Replicator V2.

SECMAP 115 DART Events associated with the UNIX uid/gid to Windows SID mapping.

SECURITY 54 DARTCS_PLATFORM

Security events.

SMB 56 DART Common Internet File System (CIFS) events. Formerly known as Server Message Block events.

SNAPSURE_SCHED 91 CS_PLATFORM SnapSure scheduling events.

STORAGE 58 DART High-level SCSI driver events.

SVFS 70 DARTCS_PLATFORMCS_CORE

SnapSure events.




Event numbersEach event associated with a facility is assigned a unique number within that facility. As an example, Table 3 on page 11 lists some of the events generated by the UFS facility.

SYR 143 CS_PLATFORM Events associated with the System Reporting (SYR) process used to gather system configuration information.

UFS 64 DART File system consistency events concerning the physical file system, which is dependent on the disk structure. Additionally, quota events are in this facility.

UPSMonitor 140 CS_PLATFORM Uninterruptible Power Supply monitor for NSX systems.

USRMAP 93 DART Usermapper events.

VC 81 DART Virus-checking events.

VMCAST 84 DARTCS_PLATFORM

Volume multicast events associated with a file system copy. Used for Replicator V1.

VRPL 77 DART Volume Replicator events. Used for Replicator V1.

WINS 117 DART Windows Internet Name Service events.

XLT 72 DARTCS_PLATFORM

Translation (XLT) file events. Detects XLT file corruptions, and recovers those files automatically from the Control Station.

Table 3 UFS event numbers (page 1 of 2)

Base ID Severity Brief description

1 ERROR(3) Event ${evt,5,%u} occurred while doing a dircvt

2 ERROR(3) Event ${evt,5,%u} occurred while doing a dircvt

4 WARNING(4) "Block soft quota crossed (fs ${mountPoint,8,%s}, ${idStr,8,%s} %${userId,2,%d})

5 ERROR(3) Block hard quota reached/exceeded (fs ${mountPoint,8,%s}, ${idStr,8,%s} ${userId,5,%u})




For example, if the usage of a file system grows beyond predefined quotas, the system generates UFS events (facility ID 64) with event numbers of 4 or 5.

Event severity levelsEach Celerra event has a severity level, which gives an administrator an indication of the nature of the event and whether it is necessary to take immediate action. Default notifications are defined in the configuration file /nas/sys/nas_eventlog.cfg. Table 4 on page 12 provides a list of event severity levels and shows the relationship between these severity levels and those defined by Celerra Manager.

The lower the severity level number, the greater the severity of the event. A severity of 0 is an emergency, while a severity of 7 is a debug condition.

42 ERROR(3) fsid ${fsid,5,%u}: transaction replay skipped. Missing volume information, fs may be corrupted

Table 4 Event severity levels

Severitylevel Name Description Celerra Manager

designation

0 Emergency An extremely urgent condition exists; immediate action is needed.

Critical

1 Alert Administrator attention is required. Critical

2 Critical A critical error condition is detected. Critical

3 Error A noncritical error condition is detected. Error

4 Warning A nonerror condition occurred that, if ignored, could become an error.

Warning

5 Notice An abnormal condition occurred that does not require an action.

Info

6 Info A normal condition occurred; informational only.

Info

7 Debug A debug-related condition occurred; this should not happen in normal operations.

Debug

Table 3 UFS event numbers (page 2 of 2)

Base ID Severity Brief description


NotificationsA notification is an action the Control Station takes in response to a particular event. For example, the Control Station can send an email message to an administrator when a critical event occurs. Actions the system can take include:

◆ Logging the event in an event log file

◆ Sending an email message for single or multiple system events to a specific email address

◆ Generating an SNMP trap

◆ Calling home to EMC

◆ Running a script

◆ Sending an RPC message to a host

◆ Terminating processing of an event

Event log files The most common action taken when an event occurs is to log the event in an event log file. Celerra Network Server System Operations provides information about displaying log files by using the Celerra command line interface. The default system event log can be viewed and managed by using Celerra Manager. You can find detailed information about Celerra Manager in its online help.

Notification configuration filesThe Celerra Network Server is configured with a set of default notifications that include logging all events to the appropriate log file. The default notifications are defined in the default configuration file /nas/sys/nas_eventlog.cfg.

Note: The checkup facility has its own sample configuration file, /nas/site/checkup_eventlog.cfg, which you can use to set up email notifications. To set up email notifications from scheduled checkups, edit this file with the appropriate email addresses and then load it. For more information on scheduled checkups, see the nas_checkup man page.

You can create notification definitions by creating new configuration files in the /nas/site directory and loading them by using the CLI.

You also can create mail, log, and trap notifications by using Celerra Manager.

By using custom configuration files and the CLI, you can define notifications with one or more of the available actions for any event. For example, you might put all configuration information for email notifications in a file called /nas/site/mail_eventlog.cfg and all configuration information for SNMP notifications in a file called /nas/site/trap_eventlog.cfg. You can then use the CLI to configure Celerra notifications with the customized files. If you create separate configuration files for particular notifications or events, you can load and unload them individually, without affecting configurations specified in other files.

../SystemOperations/index.htm


How to create a notification configuration file The following information describes how to create a notification configuration file. Use the following format for each entry in the notification configuration files:

◆ A line starting with the keyword facilitypolicy and its component ID, followed by the unique facility ID for the facility and an event severity level with the following format:

facilitypolicy <Component_ID>:<facility_ID>, <severity_level>

where:

<Component_ID> = component ID to which the facility belongs

<facility_ID> = facility ID

<severity_level> = maximum severity level for this disposition

For example, facilitypolicy 1:64, 3 specifies an entry for events from the DART UFS facility (component ID 1, facility ID 64) with a severity level of Error (3) or lower (more severe). The notification is triggered by events with severity-level numbers equal to or less than the <severity_level> specified in the <facilitypolicy> line. In the previous example, notifications would be triggered by events with severity levels of Error (3), Critical (2), Alert (1), or Emergency (0).

Note: If a facility is specified in more than one configuration file, the highest severity number (least severe) specified in the files is used. For example, if the UFS entry has a severity level of 7 (Debug) in /nas/sys/nas_eventlog.cfg file and a severity level of 2 (critical) in cwm_notify.cfg, the event log daemon uses the maximum severity number (least severe level) of 7.

◆ A line starting with the keyword disposition, followed by a range of event IDs within the facility, severity level, an optional directive to control unwanted or repetitious events, and the action to take when the facility issues an event in the specified event ID range. The format follows:

disposition [range=<range_start-range_end>][severity=<severity_start-severity_end>] [<directive>], <action>

where:

<range_start-range_end> = optional range of event IDs

<severity_start-severity_end> = optional range of severity levels

<directive> = optional directive that can be one of the following:

• threshold=<n> = number of occurrences of the event before taking the associated action. This directive treats 0 as 1, so threshold=0 is the same as threshold=1 and both values invoke the associated action on the first occurrence of the event.

• rearm=<n> = number of occurrences that must take place to invoke the associated action after the threshold is reached. This directive works in conjunction with threshold and overrides the threshold value for subsequent event occurrences.


• resetafter=<n> = number of seconds after which threshold and rearm counters are reset if no associated event activity occurs.

• <action> = action to take when this event is triggered. This is not optional. Following are the defined actions:

logfile, mail, trap, callhome, exec, udprpc, terminate

The following example specifies that the system should generate the specified SNMP trap (2) for events with event IDs in the range of 3 to 7.

disposition range=3-7, trap "/nas/site/trap.cfg 2"

The range is optional. If no range is specified, the disposition applies to all events issued by that facility. If no severity level is specified, the maximum level is used if the facility is specified in more than one configuration file.

The following example specifies that the system should generate the specified SNMP trap (2) for any event generated by this facility. Note that the comma is still required:

disposition, trap "/nas/site/trap.cfg 2"

◆ An optional line starting with the keyword disposition, followed by a range of severity levels and the action to take when the facility issues an event in the specified severity-level range. The format follows:

disposition [<severity_level_range>], <action>

The following example specifies that any event with severity 1 or 2 results in an email. Specifying a range of severity levels overrides the severity level specified in the <facilitypolicy> line, 7 in this case.

facilitypolicy 1:64, 7disposition severity=1-2, mail "user@domain"

Events can have more than one action. For example, a specific event could have logfile, and trap actions. "Create a configuration file" on page 41 describes the procedure to create and modify a configuration file.

You can use comment lines, which start with the number sign (#), to document notification configuration files.

Simple Network Management ProtocolOne type of notification you can configure for certain events is an SNMP notification, or SNMP trap. SNMP is a network protocol based upon a manager or agent model and is used to communicate management information between a network management station (NMS) and agents in the network elements. The manager provides the interface between the human network manager and the management system. The agent provides the interface between the manager and the physical devices in the network.


SNMP messagesThere are three types of SNMP messages:

◆ Get requests from the SNMP manager — Request information from the remote device.

◆ Set requests from the SNMP manager — Modify the configuration of the remote device.

◆ Trap messages from the SNMP agent on the remote device — Provide notification and monitoring of events.

The trap message is the way an agent communicates with the SNMP manager, notifying the manager of an event, such as a crash, a restart, or a network interface card failure. The manager might respond to a trap message by polling agents to get more information.

The Celerra Network Server responds to SNMP get requests and can generate SNMP trap messages for specified events. The values you can set or modify are community, syscontact, and location.

SNMP security and the community stringThe SNMP community string is the basis for security in SNMP. The default community name is the well-known name public. This name should be changed to prevent unwanted access to the Celerra Network Server. Use only alphanumeric characters to specify the community name. You can set up an SNMP trap for any Celerra event.

Using more than one community name can provide multiple levels of security.

Note: SNMP version 1 (SNMPv1) transmits all information in clear text. Anyone monitoring the network can obtain the SNMP community name from passing traffic. RFC 1157 provides details about SNMPv1 security.

Third-party commercial SNMP productsThere are many commercial third-party SNMP management products, including:

◆ Computer Associates Unicenter TNG

◆ Hewlett-Packard OpenView Network Node Manager

◆ Hewlett-Packard OpenView Operations

◆ IBM Tivoli NetView

◆ IBM Tivoli TME10 NetView

◆ IBM Tivoli TME10 Enterprise Console

◆ Micromuse Netcool/OMNIbus


System requirements for events and notificationsTable 5 on page 17 describes the Celerra Network Server software, hardware, network, and storage configurations required for using events and notifications as described in this document.

E-Lab Interoperability Navigator The EMC E-LabTM Interoperability Navigator is a searchable, web-based application that provides access to EMC interoperability support matrices. It is available on the EMC Powerlink® website at http://Powerlink.EMC.com. After logging in to Powerlink, go to Support > Interoperability and Product Lifecycle Information > E-Lab Interoperability Navigator.

Table 5 Events and notifications system requirements

Software Celerra Network Server version 5.6.

Hardware No specific hardware requirements.

Network Depends on the type of action used for notifications. For example, mail service is required for email notification, SNMP applications for traps, DNS for hostname resolution, and modems for call homes.

Storage No specific storage requirements.

http://powerlink.emc.com


User interface choices for events and notificationsThe Celerra Network Server offers flexibility in managing networked storage based on your support environment and interface preferences. This document describes how to configure notifications by using the command line interface (CLI). You can also perform many of these tasks by using one of the Celerra management applications:

◆ Celerra Manager — Basic Edition

◆ Celerra Manager — Advanced Edition

◆ Microsoft Management Console (MMC) snap-ins

◆ Active Directory Users and Computers (ADUC) extensions

For additional information about managing your Celerra, refer to:

◆ The topic, Learning about EMC Celerra, on the EMC Celerra Network Server Documentation CD

◆ Celerra Manager online help

◆ Application’s online help system on the EMC Celerra Network Server Documentation CD

Installing Celerra Management Applications includes instructions on launching Celerra Manager, and on installing the MMC snap-ins and the ADUC extensions.

LimitationsYou cannot use Celerra Manager to configure the following notification actions:

◆ CallHome

◆ Execution of a procedure

◆ Generation of an RPC message

◆ Termination of processing of event

Celerra Network Server Release Notes contain additional, late-breaking information about Celerra management applications.

../../gettingstarted.htm

../../HelpSystems/ManagerHelp/wwhelp/wwhimpl/java/html/wwhelp.htm

../../mergedprojects/MonitoringCelerra/Monitoring_Celerra.htm

../InstallationManagement/index.htm


Roadmap for configuring events and notificationsThe tasks for configuring events and notifications are:

◆ "Configure DNS on the Control Station" on page 20

◆ "Check if email is working properly before configuring notifications" on page 21

◆ "Configuring email notifications" on page 23

◆ "Gathering required information" on page 28

◆ "Configuring SNMP trap notifications" on page 34

◆ "Customizing notifications" on page 41

◆ "Appendix A: Specify an email subject line" on page 69

◆ "Appendix B: Events" on page 70


Configure DNS on the Control StationBy using DNS services, it is easier to administer hostname resolution. Most of the time, DNS configuration is done at the time of Celerra Network Server implementation.

Action

If necessary, use a text editor to add the following lines to /etc/resolv.conf:domain xxx.emc.comsearch localdomainnameserver a.b.c.enameserver a.b.c.f

where:xxx.emc.com = DNS domain namea.b.c.e = IP address of a DNS name server on the networka.b.c.f = IP address of a secondary DNS name server on the networkExample:domain nasdocs.emc.comsearch localdomainnameserver 192.168.152.184nameserver 192.168.152.185


Check if email is working properly before configuring notificationsThis procedure combines the commands echo, mail, and hostname. The results of the echo command are passed to the mail command and the hostname (Control Station name) is sent to the recipient.

Action

To test if email is working properly before configuring notifications, use this command syntax:$ echo test from ‘hostname‘ | mail -v -s ”‘hostname‘ subject” recipient email address

Be sure to enclose hostname in single, backward quotes; otherwise, the command fails. The man pages for echo, mail, and hostname commands provide more information.where:-v = verbose output option of mail command-s = subject option of the message‘hostname‘ = result of hostname command that is passed to the requested commands (echo, and mail)subject = email subjectrecipient email address = recipient’s email addressExample:To send a test email to user1, type:$ echo test from ‘hostname‘ | mail -v -s ”‘hostname‘ test message” [email protected]

Output

The following output provides information about the state of email service on the Control [email protected]... Connecting to eagle.lss.nasdocs.emc.com. via esmtp...220 igw ESMTP Sendmail 8.10.1/8.10.1; Tue, 22 Jun 2004 11:14:19 -0400 (EDT)>>> EHLO manatee6.pag.nasdocs.emc.com250-igw.nasdocs.emc.com Hello [192.168.80.140], pleased to meet you...>>> MAIL From:<[email protected]> SIZE=104250 2.1.0 <[email protected]>... Sender ok>>> RCPT To:<[email protected]>250 2.1.5 <[email protected]>... Recipient ok>>> DATA354 Enter mail, end with "." on a line by itself>>> .250 2.0.0 i5MFEJr00252 Message accepted for [email protected]... Sent (i5MFEJr00252 Message accepted for delivery)Closing connection to eagle.lss.nasdocs.emc.com.>>> QUIT221 2.0.0 igw.nasdocs.emc.com closing connection


You can also test email notifications by using the Test button. For this, create an event notification for email in Celerra Manager. Then, go to Notifications > Events. Click Test on the notification list. "Configuring email notifications" on page 23 provides another means of setting up and testing email notifications.

Note

In the resulting output from the command, the following line 250 2.1.5 <[email protected]>... Recipient ok, indicates that email on the Control Station is working properly.

If the recipient did not receive the email, there might be network problems external to the Control Station. "Troubleshooting" on page 63 provides more information on what to do if email notifications are not working as expected.


Configuring email notificationsEmail notifications allow you to configure email for multiple, serious system events in one place, eliminating the need to configure notifications with the same email recipients. To configure email notifications:

◆ "Enable email notifications" on page 23

◆ "Configure email notifications" on page 24

◆ "Display an email notifications configuration" on page 25

◆ "Test an email notification configuration" on page 26

◆ "Re-initialize email notifications" on page 27

◆ "Disable email notifications" on page 27

Note: Events will continue to be sent as callhomes to EMC support if Connect Home is enabled.

You can continue to configure email notifications for specific events. "Customizing notifications" on page 41 provides more information. You can also configure and test email notifications by using Celerra Manager. In Celerra Manager, go to Support > Email User tab.

Enable email notifications

Action

To enable email notification, use this command syntax:$ nas_emailuser -modify -enabled {yes | no}

where:yes = enabled. Example:To enable email notification, type:$ nas_emailuser -modify -enabled yes

Output

OK


Configure email notificationsUse this procedure to configure an email notification.

Before configuring email notificationsIf DNS is not configured on the Control Station, email notifications will not be delivered. Configuring Celerra Naming Services provides information about configuring DNS.

The mailbox portion of the fully qualified domain name uses the following ASCII characters: a–z, A–Z, 0–9, !, #, $, %, &, *, +, -, /, =, ?, ^, _, `, {, |, }, ., ‘, and ~. Periods cannot be the first or last character in the mailbox. Alphanumeric strings are accepted. Enclose email addresses in single quotes. For example: ’[email protected]’. You can use single quotes within an email address, but you must escape them correctly. The first example shows how to use a single quote on its own in an address, while the second shows how to use a single quote within a single-quoted address:

◆ admin\'[email protected]

◆ 'first'\''[email protected],second'\''[email protected]'

You can customize the subject prefix to meet your specific requirements, such as email filtering.

Action

To configure email notifications, use this command syntax:$ nas_emailuser -modify -to {<email_addr>,...} -cc {<email_addr>,...} -email_server <email_server> -subject_prefix <email_subject> -from <email_addr>

where:<email_addr> = for -to, one or more comma-separated, email addresses, from 3 to 255 characters, in the format ‘mailbox@fully-qualified-domain-name’. Each individual email address can be a maximum of 63 characters. <email_addr> = for -cc, one or more optional, comma-separated, email addresses, from 3 to 255 characters, in the format ‘mailbox@fully-qualified-domain-name’. Each individual email address can be a maximum of 63 characters.<email_addr> = for -from, sender’s optional email address, from 3 to 63 characters, in the format ‘mailbox@fully-qualified-domain-name’. If you do not specify a sender, an address in the format root@<hostname> is used by the system. For example: ’[email protected]’.<email_server> = the optional email server that accepts and routes the email notifications. Specifies an optional IP address or the fully qualified domain name, from 1 to 63 characters, of the email server. The IPv4 addresses 0.0.0.0 and 255.255.255.255 are not allowed.<email_subject> = the optional subject prefix of the email notification, from 1 to 63 printable ASCII characters. The default subject prefix is Celerra Notification.Example:To configure email notifications using email server 10.6.50.122 from administrator to support, while copying engineering and documentation, type:$ nas_emailuser -modify -to ‘[email protected]’,’[email protected]’ -cc ‘[email protected]’,’[email protected]’ -email_server 10.6.50.122 -subject_prefix "Celerra Notification -- May 10, 2008" -from ‘[email protected]’


Display an email notifications configuration

Output

OK

Action

To display the email notifications configuration, type:$ nas_emailuser -info

Output

Service Enabled = YesRecipient Address(es) = [email protected],[email protected] copy Address(es) = [email protected],[email protected] Server = 10.6.50.122Subject Prefix = Celerra Notification -- May 10, 2008Sender Address = [email protected]


Sample email notificationThe following output shows an example of an email notification based on the configuration information you supplied and generated when a BoxMonitor error occurs:

Test an email notification configurationTest an email notification posts a test event, which delivers an email notification to the configured recipients.

Output

From: [email protected]: [email protected],[email protected]: [email protected],[email protected]: Celerra Notification -- May 10, 2008

Event Time: May 10 03:14:07 2038

Brief Description: Slot 2: Enclosure 0 blade 1 I2C PSA bus error.

Full Description:

This is a management switch internal error. The error is logged when the management switch is not able to control or query the status of enclosure components because of a hardware problem that may be caused by a component or connection outside the management switch.

Recommended Action:

Examine the /nas/log/sys_log to locate the cause of the management switch event. This may be caused by bad I2C connections on the motherboard or the enclosure. This can also happen when the two management switches in the enclosure have conflicting views of the system. Replacing the enclosure hardware or one of the management switches may be necessary.

Celerra Name: csdev-45(1.2.3.4)Celerra Model: NS40Celerra Serial #: APM123455445NAS Version: 5.6.38.0

Severity: CRITICALComponent: CS_PLATFORMFacility: BoxMonitorMessage ID: 78928609795

Depending on your service level agreement, you can contact your service provider to resolve the problem or follow the instructions in the recommended actions.

Action

To test email notifications, type:$ nas_emailuser -test

Output

OK


After testing an email notification configurationConfirm with the configured recipients that they received the test email with the correct system identification information.

Disable email notifications

Re-initialize email notificationsIf the configuration file becomes corrupt or is deleted, you can use the -init option to re-initialize the email notification feature; however, you should only use this option if you are directed to run it by a system message.

Action

To disable email notification, use this command syntax:$ nas_emailuser -modify -enabled {yes | no}

where:no = disabled. Example:To disable email notification, type:$ nas_emailuser -modify -enabled no

Output

OK

Action

To re-create the configuration file, type:$ nas_emailuser -init

Output

OK


Gathering required informationTo specify notifications for specific events, you need to gather information about event facilities and the events they generate.

To gather required information:

1. "Determine facilities in a component that generate events" on page 29

2. "Determine events associated with a facility" on page 30

3. "Locate more information about an event" on page 31

4. "Determine a list of all possible actions" on page 32

5. "Determine which events trigger an action" on page 33


Determine facilities in a component that generate events

Step Action

1. To view the list of components, type:$ nas_event -list -component -info

Output:ID Component1 DART2 CS_CORE5 XML_API6 CS_PLATFORM

2. To view a list of all facilities of the component DART that generate events, type:$ nas_event -list -component DART -facility -info

Output:DART(1)

|->Id Facility 24 ADMIN 26 CAM 27 CFS 36 DRIVERS 40 FSTOOLS 43 IP 45 KERNEL 51 NDMP 52 NFS 54 SECURITY 56 SMB 58 STORAGE 64 UFS 68 LOCK 70 SVFS 72 XLT 73 NETLIB 75 MGFS 77 VRPL 81 VC 83 RCPD 84 VMCAST 86 CHAMII 93 USRMAP 101 ACLUPD 102 FCP 108 REP 111 DPSVC 115 SECMAP 117 WINS 118 DNS 122 DBMS 144 PERFSTATS 146 CEPP


Determine events associated with a facility

Action

To view a list of events and event ID numbers associated with a facility, use this command syntax:$ nas_event -list -component DART -facility <facility>

where:<facility> = case-sensitive facility nameA component must be listed with a facility to view the list of events generated by that facility. Example:To list the events associated with the DART facility, type:$ nas_event -list -component DART -facility SVFS

Output

DART(1)|--> SVFS(70)BaseID Severity Brief_Description1 WARNING(4) FSID:${id,5,%u} SavVol:${vol,8,%s} MaxSize:${maxsize,5,%u} MB %Full(hwm=${hwm,2,%d}) reached (t:${ticks,3,%q})2 ERROR(3) FSID:${id,22,%u} SavVol:${vol,76,%s} Inactive3 INFO(6) Restore completed successfully. (PFS_VOLID:${volname,76,%s})4 INFO(6) Restore in progress ${percent,5,%1u} percent done. (PFS_VOLID:${volid,76,%s})5 EMERGENCY(0) FSID:${id,22,%u} SavVol:${vol,76,%s} conversion paused (t:${ticks,6,%llu})6 ERROR(3) FsVol:${FsVolName,76,%s} SavVol:${SaveVolName,76,%s} Inactivate ALL ckpt


Locate more information about an eventTo locate more information about an event, determine the message ID for the event and then use the message ID to display the additional information.

Step Action

1. To view a list of events, and associated message IDs, for a facility, use this command syntax:$ nas_event -list -component DART -facility <facility> -id

where:<facility> = case-sensitive facility nameExample:To list the message IDs for all events of a facility, type:$ nas_event -list -component DART -facility SVFS -id

Output:DART(1)|--> SVFS(70)MessageID BaseID Severity Brief_Description86172368897 1 WARNING(4) FSID:${id,5,%u} SavVol:${vol,8,%s} MaxSize:${maxsize,5,%u} MB %Full(hwm=${hwm,2,%d}) reached (t:${ticks,3,%q})81877401602 2 ERROR(3) FSID:${id,22,%u} SavVol:${vol,76,%s} Inactive94762303491 3 INFO(6) Restore completed successfully. (PFS_VOLID:${volname,76,%s})94762303492 4 INFO(6) Restore in progress ${percent,5,%1u} percent done. (PFS_VOLID:${volid,76,%s})68992499717 5 EMERGENCY(0) FSID:${id,22,%u} SavVol:${vol,76,%s} conversion paused (t:${ticks,6,%llu})81877401606 6 ERROR(3) FsVol:${FsVolName,76,%s} SavVol:${SaveVolName,76,%s} Inactivate ALL ckpt

Note: The number 81877401606 is a message ID.


Determine a list of all possible actions

2. To locate more information about an event, use this command syntax:$ nas_message -info <message_id>where:<message_id> = multi-digit ID numberExample:To obtain additional information about an event by using the message ID, type:$ nas_message -info 81877401606

Output:MessageID = 81877401606BaseID = 6Severity = ERRORComponent = DARTFacility = SVFSType = EVENT

Brief_Description = FsVol:${FsVolName,76,%s} SavVol:${SaveVolName,76,%s} Inactivate ALL ckpt

Full_Description = All checkpoints are inactive due to limited space on the save volume.

Recommended_Action = Check the system configuration to see if more space can be allocated for the save volume.

Action

To view a list of all possible actions you can take, type:$ nas_event -list -action -info

Output

actionmailterminatetrapexeccallhome logfileudprpc

Note

Mail notification is not a default; therefore, it does not appear in the list of possible actions until an event is configured for mail notification.

Step Action


Determine which events trigger an action

Action

To view a list of events that trigger a particular action, use this command syntax:$ nas_event -list -action <action>

where:<action> = name of the action: mail, trap, logfile, callhome, exec, terminate, updrpcExample:To list the events that trigger a trap action to EMC, type:$ nas_event -list -action trap

Output

CS_PLATFORM(6)|--> BoxMonitor(131)BaseID Severity Brief_Description1 CRITICAL(2) EPP failed to initialize.3 CRITICAL(2) Failed to create ${threadname,8,%s} thread.4 CRITICAL(2) SIB Read failure: ${string,8,%s}..CS_PLATFORM(6)|--> SYR(143)BaseID Severity Brief_Description5 INFO(6) The SYR file ${src_file_path,8,%s} with ${dest_extension,8,%s} extension is attached.


Configuring SNMP trap notificationsTo configuring SNMP traps for notifications:

1. "Modify the Celerra MIB file for SNMP traps" on page 34

2. "Configure SNMP traps" on page 34

3. "Send a test SNMP trap" on page 35

4. "Receive a test SNMP trap" on page 37

5. "Configure SNMP on Data Movers" on page 40

Modify the Celerra MIB file for SNMP trapsIf the default SNMP traps do not properly describe the condition you want to trap, you can define additional SNMP traps by modifying the Celerra MIB file.

Configure SNMP trapsAn SNMP trap configuration file informs the Control Station which SNMP managers should receive a message when a trap occurs. Specify which trap configuration file (located in the /nas/site directory) to use when you configure a trap notification. A trap configuration file can contain multiple entries, one per line. Modifications to the file are maintained when the Celerra Network Server is upgraded.

Step Action

1. Modify the Celerra MIB, /nas/sys/emccelerra.mib, to include the following lines:celCFS TRAP-TYPEENTERPRISE emcCelerraVARIABLES {celEvent}DESCRIPTION "description"::=unique-id-number

where:description = description of the trap.unique-id-number = arbitrary, yet, unique trap number for the event you specified in the notification configuration file. Some trap numbers are reserved. Ensure to check the trap definition section of the Celerra MIB, /nas/sys/emccelerra.mib, before assigning a trap number.

Note: Ensure that the trap number in the MIB and in the configuration file you are modifying are the same.The trap number correlates a particular trap in the MIB with events you specify in the configuration file. Save a copy of the modified MIB in another location because it is overwritten when the system is upgraded. On HP OpenView, load the MIB by using Options > Load/Unload MIBs:SNMP.

2. Configure the MIB on the SNMP Manager.


Before configuring SNMP trapsThe Control Station can use /etc/hosts, NIS, or DNS to resolve hostnames and IP addresses. These services must be configured and running. In addition, set up the /etc/nsswitch.conf file to determine the search order the Control Station uses when resolving names. The /etc/hosts file is a text file listing hostnames and their corresponding IP addresses. If you use hostnames in a trap configuration file, be sure to add the hostnames and IP addresses to the /etc/hosts file if you are not using DNS for name resolution. The changes take effect as soon as the file is saved. There is no need to restart the system.

Send a test SNMP trapYou can use nas_snmptrap and snmptrapd -f -Le -Lf on the Control Station to send a test SNMP trap.

Before sending a test SNMP trapFor NS series Control Stations, snmptrapd is already running. The Celerra software starts the daemon on NS20, NS40, NS40G, NS80, NS80G, and NSX systems whether or not UPS is installed. To prevent the generation of two sets of logs when testing an SNMP trap on these systems, as root kill the existing snmptrapd service run by typing:

# killall snmptrapd

To restart snmptrapd services after testing, type:

# /usr/sbin/snmptrapd -c /nas/sys/snmptrapd.conf -p 162 -u /var/run/snmptrapd.pid >/dev/null 2>&1 &

Action

By using a text editor, add the following lines to the file /nas/site/trap.cfg to configure the SNMP Managers:#snmp trap configuration filesnmpmanager hostname ; communityname community

where:snmp trap configuration file = comment linesnmpmanager = keyword hostname = hostname or IP address; = separator character, preceded and followed by a spacecommunityname = keyword community = community name for the SNMP managerExample:#snmp trap configuration filesnmpmanager 128.154.11.20 ; communityname xyz_communitysnmpmanager host1 ; communityname xyz_community


You can create an event notification for a trap in Celerra Manager. To create, go to Notifications > Events. Then, click Test on the notification list.

Step Action

1. Log in to the Control Station as root.

2. Ensure that the Control Station is listed in the trap.cfg file. Example:snmpmanager localhost ; communityname public

3. Start the SNMP trap daemon on the Control Station by typing:# /usr/sbin/snmptrapd -f -Le -Lf /nbsnas/var/log/my_eventlog_messages &

Note: Because snmptrapd is already running on NS series Control Stations, this command returns an informational error message.

Some Celerras do not have the /nbsnas directory. If this is true for your system, use the /nas/var/log directory.

The & starts the daemon in the background and allows you to continue typing commands. Messages are logged to the my_eventlog_messages file.You can enable SNMP on the Control Station through Celerra Manager. Go to Security > Network Services. You can also enable and disable SNMP on Data Movers.

4. From root, send a trap by using this syntax:# /nas/sbin/nas_snmptrap config_file_path -m /nas/sys/emccelerra.mib -r trap_number -f facility_id -i event_id -s severity_level -d "description"

where:config_file_path = path of the trap configuration file/nas/sys/emccelerra.mib = Celerra MIB file trap_number = unique trap number for the eventfacility_id = ID number of the facility generating the eventevent_id = event ID numberseverity_level = severity level of the eventdescription = description of the trap (up to 255 characters)

Example:# /nas/sbin/nas_snmptrap /nas/site/trap.cfg -m /nas/sys/emccelerra.mib -r 1 -f 64 -i 5 -s 7 -d "test SNMP traps"

Output:2003-01-20 17:05:17 eng192152 [192.168.192.152] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public. enterprises.1139.2 Enterprise Specific Trap (1) Uptime: 14 days, 1:39:04.68 enterprises.1139.2.1.1.1 = 64 enterprises.1139.2.1.1.2 = 5 enterprises.1139.2.1.1.3 = 7 enterprises.1139.2.1.1.4 = "test SNMP traps "


Receive a test SNMP trapYou can receive a test SNMP trap by configuring the Control Station as the target.

Step Action

1. Set up the SNMP Manager to receive Virus Checker SNMP traps by adding the following line to the file /nas/site/trap.cfg:snmpmanager a.b.c.d ; communityname public

where:a.b.c.d = IP address of the SNMP Manager that gets the traps.public = community name to use for authentication with the SNMP Manager. Check with the site manager for what to use in place of public.

2. Modify the Celerra MIB, found at /nas/sys/emccelerra.mib, to include the following lines:celVC TRAP-TYPEENTERPRISE emcCelerraVARIABLES {celEvent}DESCRIPTION "Trap message will be sent in the event of a VC service associated notification request."::=11

where: 11 = arbitrary, yet unique, trap number for the event you specified in the my_eventlog.cfg fileSave a copy of the modified MIB in another location because it is overwritten when the system is upgraded. On HP OpenView, load the MIB by using Options > Load/Unload MIBs:SNMP.

3. Configure MIB on the SNMP Manager.

4. Ensure that the Control Station name is in the /etc/hosts file:# Do not remove the following line, or various programs# requiring network functionality will fail.127.0.0.1 localhost.localdomain localhosta.b.c.d example_cs0 example_cs0.nasdocs.emc.com

where: a.b.c.d = IP address of the Control Station.example_cs0 = Control Station name and nasdocs.emc.com is the name of the domain that includes the mail server. Substitute Control Station and domain information for the ones in the example.

5. Create a new notification configuration file named /nas/site/my_eventlog.cfg by copying /nas/sys/nas_eventlog.cfg to my_eventlog.cfg.


6. Use a text editor to add the following statements to my_eventlog.cfg:# Virus Checker Events# email and trap notification for any Virus Checker event# facilitypolicy 1:81,7 disposition range=1-28, mail "[email protected]" disposition range=1-28, trap "/nas/site/trap.cfg 11"

where:facilitypolicy 1:81 = dispositions that need to be applied to events in the VC facility (facility ID 81) of the DART component (component ID 1).7 = severity-level threshold (captures events of severity 7 or lower).disposition range=1-28 = events 1 through 28, which equates to all VC [email protected] = email address that receives email notification. Replace these with one or more email addresses at company.11 = arbitrary, yet unique, trap number you associate with the event in the Celerra MIB (code shown in step 2).

Note: If you are running Celerra Network Server version 5.1 or earlier, you must define the subject line for email notifications when editing event log configuration file. "Appendix A: Specify an email subject line" on page 69 provides an example of doing this.

"Determine events associated with a facility" on page 30 provides information about determining which events are associated with which facilities.

7. Using the full path name, load the new notification configuration file by using the following command: $ nas_event -Load /nas/site/my_eventlog.cfg

Output:EventLog : will load /nas/site/my_eventlog.cfg...done

Note: You must unload the configuration file before making additional changes. You must specify the absolute path of the configuration file to unload.

Step Action


8. Verify the new notifications (email and traps) have been accepted by using the following command:$ nas_event -list -action mail$ nas_event -list -action trap

Note: Mail is not a default action. Until an event is configured for mail notification, the command nas_event -list -action mail returns an error.

The output should at least display:DART(1)|--> VC(81)BaseID Severity Brief_Description1 NOTICE(5) The virus checker is running normally.2 ERROR(3) ${type,8,%s} high water mark reached.3 WARNING(4) ${type,8,%s} low water mark reached.4 ERROR(3) No virus checker server is available.5 ERROR(3) No virus checker server is available. CIFS is stopped.6 ERROR(3) No virus checker server is available. Virus checking is stopped.7 ERROR(3) '${filename,8,%s}' was not checked.8 NOTICE(5) Server ${ipaddr,8,%s} is online. RPC program version ${rpc,2,%d}, ${cava,8,%s}.9 ERROR(3) Error on server ${ipaddr,8,%s}: ${status,8,%s}${winerror,8,%s}, RPC program version ${rpc,2,%d}, ${cava,8,%s}.10 NOTICE(5) The virus checker is started.11 NOTICE(5) Scanning was completed for file system ${fsid,2,%d} mounted on ${mountPath,8,%s}. ${dirs,2,%d} directories were scanned and ${files,2,%d} files were submitted to the scan engine.12 ERROR(3) Scanning was aborted for file system ${fsid,2,%d} mounted on ${mountPath,8,%s} for this reason: ${error,8,%s}. ${dirs,2,%d} directories were scanned and ${files,2,%d} files were submitted to the scan engine.13 ERROR(3) The antivirus (AV) engine deleted ${file,8,%s}, ${user,8,%s}.14 ERROR(3) The antivirus (AV) engine renamed ${file,8,%s}, ${user,8,%s}.15 WARNING(4) The antivirus (AV) engine modified ${file,8,%s}, ${user,8,%s}.16 NOTICE(5) The virus checker is stopped.

9. Generate a test Virus Checker event by using the following command:$ /nas/sbin/postevent -c 1 -f 81 -i 4 -s 3 -T$ /nas/sbin/postevent -c 1 -f 81 -i 16 -s 5 -T

Step Action


The following shows SNMP traps from the Virus Checker facility:

Configure SNMP on Data MoversThe server_snmp command manipulates SNMP configuration values of the server agent for the specified Data Mover.

The values you can set or modify are community, syscontact, and location. Celerra Network Server Command Reference Manual provides more information about this command.

Output

2008-02-06 13:32:42 matisse-cs0.rtp.dg.com [10.6.4.76] (via 127.0.0.1)TRAP, SNMP v1, community publicSNMPv2-SMI::enterprises.1139.2 Enterprise Specific Trap (11)Uptime: 19:44:34.83SNMPv2-SMI::enterprises.1139.2.1.1.1 = INTEGER: 81 SNMPv2-SMI::enterprises.1139.2.1.1.2 = INTEGER: 4 SNMPv2-SMI::enterprises.1139.2.1.1.3 = INTEGER: 3 SNMPv2-SMI::enterprises.1139.2.1.1.4 = STRING: "Feb 6 13:32:42 2008 VC:3:4 Novirus checker server is available. "2008-02-06 13:32:50 matisse-cs0.rtp.dg.com [10.6.4.76] (via 127.0.0.1)TRAP, SNMP v1, community publicSNMPv2-SMI::enterprises.1139.2 Enterprise Specific Trap (11)Uptime: 19:44:42.91SNMPv2-SMI::enterprises.1139.2.1.1.1 = INTEGER: 81 SNMPv2-SMI::enterprises.1139.2.1.1.2 = INTEGER: 16 SNMPv2-SMI::enterprises.1139.2.1.1.3 = INTEGER: 5 SNMPv2-SMI::enterprises.1139.2.1.1.4 = STRING: "Feb 6 13:32:50 2008 VC:5:16The virus checker is stopped. "

Action

To assign a new value of private to a server SNMP agent’s community for a Data Mover, type:$ server_snmp server_2 -community private

Output

server_2 : done


Customizing notificationsTo customize notifications, create the configuration file and load it on the Celerra Network Server. You can also create log, mail, or trap notifications through Celerra Manager. To customize notifications:

1. "Create a configuration file" on page 41

2. "Load a configuration file" on page 42

3. "Verify the configuration file loaded" on page 43

Create, load, and verify tasks can be done through Celerra Manager. To accomplish these tasks, go to Notifications > Events. The actions are limited to email, trap, and logfile. Celerra Manager online help has more details.

Note: In case of CLI, if the nas_emailuser command is used to specify the sender address, custom notifications created in the format "mailuser @domain.com" will use the root user instead of the sender address specified in the command.

In Celerra Manager, you can specify the email address by selecting Support > Email User. However if you create custom notification by using Notifications > Storage Usage, it will use the root user instead of the address specified in the "Sender Email Address".

Create a configuration fileYou can create and modify configuration files to fit your specific Celerra Network Server environment.

Step Action

1. Log in to the Control Station.

2. Change to the /nas/site directory by typing:$ cd /nas/site

3. Copy the /nas/sys/nas_eventlog.cfg file to the current directory, so you can use it as a template. Rename it by using this command syntax:$ cp /nas/sys/nas_eventlog.cfg new_filename

where: new_filename = name of the customized configuration fileExample:$ cp /nas/sys/nas_eventlog.cfg custom_event_config.cfg

Note: Do not use the name nas_eventlog.cfg as the name for the customized configuration file. Do not modify any of the default notification configuration files.

4. Use a text editor to modify new_filename.where: new_filename = name of the customized configuration file



"How to create a notification configuration file" on page 14 provides more information about how to create a notification configuration file. When you set up a new notification, ensure that you test it and that email is reaching the intended recipient.

Load a configuration fileAfter creating the customized configuration file, you must load the file for new notifications to take effect.

5. If you copied /nas/sys/nas_eventlog.cfg as the basis for the customized file, delete everything in the file except those lines related to the facility policies and dispositions you want to change. This will help you avoid unintentionally changing default notifications.

6. Add the following statements to the notification file to associate events with the actions you want:# UFS#facilitypolicy 1:64, 3 disposition range=0-7, logfile "/nas/log/sys_log" disposition range=4-7, mail "[email protected]" disposition range=3-7, trap "/nas/site/trap.cfg 2" where:facilitypolicy 1:64 = dispositions that need to be applied to events in the UFS facility (facility ID 64) of the DART component (component ID 1)3 = severity level of Error (3) or worse. If a facility is specified in more than one configuration file, the maximum severity level specified is usedlogfile = entry added to the /nas/log/sys_log file for events 0 through 7mail = email message sent for events 4 through 7trap = SNMP trap (2) report sent for events 3 through 7. The Control Station consults /nas/site/trap.cfg for information about where to send the trapTable 6 on page 62 provides a complete list of actions. "Configure SNMP traps" on page 34 provides more information on trap configuration files.

7. Save the file and then exit.

Step Action

1. Log in to the Control Station.If you create separate configuration files, the order in which the configuration files are loaded determines the order in which the actions occur. The actions specified in the first file you load occur before the actions specified in subsequent files.

Step Action


Verify the configuration file loaded

2. Load the customized configuration file by using this command syntax:$ nas_event -Load <customized_file>

where:<customized_file> = full pathname of the customized configuration fileExample:$ nas_event -Load /nas/site/custom_event_config.cfg

Output:EventLog : will load /nas/site/custom_event_config.cfg...done

Note: Do not put customized configuration files in the /nas/sys directory or the files will be overwritten when the system is upgraded.

Action

To verify that the customized configuration file is loaded, use this command syntax:$ nas_event -Load -info

Output

The list of loaded configuration files appears:Loaded config. files:1: /nas/sys/nas_eventlog.cfg2: /nas/http/webui/etc/web_client_eventlog.cfg3: /nas/site/custom_event_config.cfg

You might need to modify the configuration of the SNMP management application before it can use these changes. "Configuring SNMP trap notifications" on page 34 provides more information.

Step Action


SNMP traps and email notifications: ExamplesThe following sections provide examples of configuring SNMP traps and email notifications to notify you:

◆ "When file system usage exceeds certain limits" on page 44

◆ "When a SnapSure SavVol usage reaches its high water mark" on page 49

◆ "When there are Virus Checker events" on page 53

◆ "When a hard or soft quota is exceeded" on page 57

When file system usage exceeds certain limitsYou can configure the Celerra Network Server to generate an SNMP trap and an email notification to several file system administrators when the size of a file system exceeds a certain percentage full, based on system tracking of the file system size threshold. The default file system size threshold is 90 percent full. This applies to the global built-in CFS event to check each file system against the fsSizeThreshold parameter.

In Celerra Manager you can create individualized threshold notifications for file systems. For example, you can notify when a particular file system hits 80 percent usage and also notify when a different file system hits 85 percent usage. Celerra Manager terms these notifications as resource notifications and they are independent of any notifications set on the CFS event.

Monitoring the percentage full is useful because file system performance can degrade as its used space approaches100.

Managing Celerra Volumes and File Systems with Automatic Volume Management and Managing Celerra Volumes and File Systems Manually provide information about how to change this threshold to another percentage value. See the description about changing the fsSizeThreshold parameter.

You need root access to the Celerra Network Server.

By default, an event is generated on the Celerra Network Server when the used space in a file system exceeds 90 percent of the total capacity of the file system.

../VolFSManually/index.htm

../AVM/index.htm


Configure Celerra to generate a notification when file system usage exceeds certain limitsIn Celerra Manager you can create individualized threshold notifications for file systems. For example, you can notify when a particular file system hits 80 percent usage and also notify when a different file system hits 85 percent usage. Celerra Manager terms these notifications as resource notifications.

Step Action

1. Configure the Domain Name Server (DNS) to enable email notification. The /etc/resolv.conf file should contain the following lines:domain xxx.emc.comsearch localdomainnameserver a.b.c.enameserver a.b.c.f

Most of the time, DNS configuration is done at the time of Celerra Network Server implementation.where:xxx.emc.com = DNS domain namea.b.c.e = IP address of a DNS name server on the networka.b.c.f = IP address of a secondary DNS name server on the network

Note: Steps 1-3, 8,and 9 can be done in Celerra Manager by choosing Notifications > Storage Usage. The actions are limited to email and trap, and the user must have an Advanced Edition license.



3. Use a text editor to add the following statements to my_eventlog.cfg:# CFS High Water Mark Event Control# notification for the file system size threshold exceeded# facilitypolicy 1:27,7 disposition range=1-1, logfile "/nas/log/sys_log" disposition range=1-1, mail "[email protected]" disposition range=1-1, mail "[email protected]" disposition range=1-1, mail "[email protected]" disposition range=1-1, trap "/nas/site/trap.cfg 12"

where:facilitypolicy 1:27 = dispositions that need to be applied to events in the CFS facility (facility ID 27) of the DART component (component ID 1).7 = severity-level threshold (captures events of severity 7 or lower).disposition range=1-1 = events 1 through 1, which equates to the CFS event "Crossed the fs (file system) size threshold." Event id 1 is the event id of the fs threshold event.logfile = entry added to the /nas/log/sys_log file for events 1 through [email protected], [email protected], and [email protected] = email addresses that receive email notification. Replace these with one or more email addresses at the company.12 = arbitrary, yet unique, trap number you associate with the event in the Celerra MIB (code shown in step 5).

Note: If you are running a Celerra Network Server version 5.1 or earlier, you must define the subject line for email notifications when editing event log configuration file. "Appendix A: Specify an email subject line" on page 69 provides an example of doing this.


4. Set up the SNMP Manager by adding the following line to the file /nas/site/trap.cfg:snmpmanager a.b.c.d ; communityname public


5. Modify the Celerra MIB, found at /nas/sys/emccelerra.mib, to include the following lines:celCFS TRAP-TYPEENTERPRISE emcCelerraVARIABLES {celEvent}DESCRIPTION "Trap message will be sent when a file system exceeds the threshold."::=12

where: 12 = arbitrary, yet unique, trap number for the event you specified in the my_eventlog.cfg file.

Note: Save a copy of the modified MIB in another location because it is overwritten when the system is upgraded. On HP OpenView, load the MIB by using Options > Load/Unload MIBs:SNMP.

Step Action


When the used space in a file system exceeds the threshold, an SNMP trap message and an email notification are sent to the file system administrator. The /usr/sbin/snmptrapd daemon must be started on the Control Station to display SNMP trap messages. "Send a test SNMP trap" on page 35 provides more information.



where: a.b.c.d = IP address of the Control Station.example_cs0 = Control Station name and nasdocs.emc.com is the name of domain that includes the mail server. Substitute Control Station and domain information for the ones in the example.

8. Using the full pathname, load the new notification configuration file by using the following command:$ nas_event -Load /nas/site/my_eventlog.cfg



9. Verify that the new notifications (email and traps) have been accepted by using the following commands:$ nas_event -list -action mail$ nas_event -list -action trap


The output should at least display:DART(1)|--> CFS(27)BaseID Severity Brief_Description1 WARNING(4) filesystem size threshold (${usageHWM,2,%d}%) crossed (fs ${mountPath,55,%s})

Step Action


The trap message on the SNMP Manager looks like this:

The following is an example of email notification:

Note: There might be a delay in email sending due to activity on the Data Mover, network traffic, activity on the Control Station, or other factors onsite.

Output

Feb 6 13:17:43 2008 CFS:4:1 Slot 3: 1191865801: filesystem size threshold (90%) crossed (fs /ufs1)

Note

The 1 in CFS:4:1 indicates the CFS event "Crossed the fs (file system) size threshold" and the Data Mover (Slot 3) and the mount point of the file system (/ufs1) involved are shown.

Output

To: [email protected]: EMCServer matisse-cs0, Component - DART, Facility - CFS, Severity - WARNING

Feb 6 13:17:43 2008 DART:CFS:WARNING:1 Slot 3: 1191865801: filesystem size threshold (90%) crossed (fs /ufs1)


When a SnapSure SavVol usage reaches its high water markYou can configure the Celerra Network Server to generate an SNMP trap and an email notification to several file system administrators when a SnapSure SavVol usage reaches its high water mark.

By default, SnapSure audits SavVols automatically and writes a message to the system log when a user-set (0 percent to 100 percent) or default high water mark (HWM) of 90 percent full is reached. In addition to the log file, you can set up trap and email notification.

Configure Celerra to generate a notification when SnapSure SavVol usage reaches its high water mark

Step Action


Most of the time, DNS configuration is done at the time of the Celerra Network Server implementation.where:xxx.emc.com = DNS domain namea.b.c.e = IP address of a DNS name server on the networka.b.c.f = IP address of a secondary DNS name server on the network



3. Use a text editor to add the following statements to my_eventlog.cfg:# SVFS High Water Mark Event Control# notification for the SavVol high water mark usage reached# facilitypolicy 1:70,7 disposition range=1-1, logfile "/nas/log/sys_log" disposition range=1-1, mail "[email protected]" disposition range=1-1, mail "[email protected]" disposition range=1-1, mail "[email protected]" disposition range=1-1, trap "/nas/site/trap.cfg 14"

where:facilitypolicy 1:70 = dispositions that need to be applied to events in the SVFS facility (facility ID 70) of the DART component (component ID 1). 7 = severity-level threshold (captures events of severity 7 or lower). disposition range=1-1 = events 1 through 1, which equates to the SVFS event “high water mark of SavVol reached.” Event id 1 is the event id of the High Water Mark event.logfile = entry added to the /nas/log/sys_log file for events 1 through [email protected], [email protected], and [email protected] = email addresses that receive email notification Replace these with one or more email addresses at company.14 = arbitrary, yet unique, trap number you associate with the event in the Celerra MIB (code shown in step 5).

Note: If you are running a Celerra Network Server version 5.1 or earlier, you must define the subject line for email notifications when editing event log configuration file. "Appendix A: Specify an email subject line" on page 69 provides an example of doing this.




5. Modify the Celerra MIB, found at /nas/sys/emccelerra.mib, to include the following lines:celSVFS TRAP-TYPEENTERPRISE emcCelerraVARIABLES {celEvent}DESCRIPTION "Trap message will be sent when a SavVol high water mark reached."::=14

where: 14 = arbitrary, yet unique, trap number for the event you specified in the my_eventlog.cfg file


Step Action


When the high water mark is reached for a SavVol, an SNMP trap message and email notification are sent to the file system administrator. The /usr/sbin/snmptrapd daemon must be started on the Control Station to display SNMP trap messages. "Send a test SNMP trap" on page 35 provides more information.




8. Using the full pathname, load the new notification configuration file by using the following command: $ nas_event -Load /nas/site/my_eventlog.cfg



9. Verify that the new notifications (email and traps) have been accepted by using the following commands:$ nas_event -list -action mail$ nas_event -list -action trap


Output:For nas_event -list -action mail, the output should at least display:DART(1)|--> SVFS(70)BaseID Severity Brief_Description1 WARNING(4) FSID:${id,5,%u} SavVol:${vol,8,%s} MaxSize:${maxsize,5,%u} MB %Full(hwm=${hwm,2,%d}) reached (t:${ticks,3,%q})

For nas_event -list -action trap, the output should at least display:DART(1)|--> SVFS(70)BaseID Severity Brief_Description1 WARNING(4) FSID:${id,5,%u} SavVol:${vol,8,%s} MaxSize:${maxsize,5,%u} MB %Full(hwm=${hwm,2,%d}) reached (t:${ticks,3,%q})

Step Action


The trap message on the SNMP Manager looks like this:

The following is an example of email notification:

Note: There might be a delay in email sending due to activity on the Data Mover, network traffic, activity on the Control Station, or other factors onsite.

Output

2008-02-06 13:26:28 matisse-cs0.rtp.dg.com [10.6.4.76] (via 127.0.0.1) TRAP, SNMP v1, community public SNMPv2-SMI::enterprises.1139.2 Enterprise Specific Trap (14) Uptime: 19:38:21.11 SNMPv2-SMI::enterprises.1139.2.1.1.1 = INTEGER: 70 SNMPv2-SMI::enterprises.1139.2.1.1.2 = INTEGER: 1 SNMPv2-SMI::enterprises.1139.2.1.1.3 = INTEGER: 4 SNMPv2-SMI::enterprises.1139.2.1.1.4 = STRING: "Feb 6 13:26:28 2008 SVFS:4:1 Slot 2: 1191866214: FSID:25 SavVol:121 MaxSize:1000 MB %Full(hwm=80) reached (t:1191866214232323) "

Note

The 1 in SVFS:4:1 indicates the SVFS event “High water mark of SavVol reached,” on Data Mover (Slot 2).

Output

To: [email protected]: EMCServer matisse-cs0, Component - DART, Facility - SVFS, Severity - WARNING

Feb 6 13:26:28 2008 DART:SVFS:WARNING:1 Slot 2: 1191866214: FSID:25 SavVol:121 MaxSize:1000 MB %Full(hwm=80) reached (t:1191866214232323)


When there are Virus Checker events You can configure the Celerra Network Server to generate SNMP traps and an email notification to Windows administrators when there are Virus Checker events. You need root access to the Celerra Network Server.

Configure Celerra to generate a notification for Virus Checker events

Step Action




3. Use a text editor to add the following statements to my_eventlog.cfg:# Virus Checker Events# email and trap notification for any Virus Checker event# facilitypolicy 1:81,7 disposition range=1-28, mail "[email protected]" disposition range=1-28, trap "/nas/site/trap.cfg 11"

where:facilitypolicy 1:81 = dispositions that need to be applied to events in the VC facility (facility ID 81) of the DART component (component ID 1).7 = severity-level threshold (captures events of severity 7 or lower).disposition range=1-28 = events 1 through 28, which equates to all VC [email protected] = email address that receives email notification. Replace these with one or more email addresses at company.11 = arbitrary, yet unique, trap number you associate with the event in the Celerra MIB (code shown in step 5).






5. Modify the Celerra MIB, found at /nas/sys/emccelerra.mib, to include the following lines:celVC TRAP-TYPEENTERPRISE emcCelerraVARIABLES {celEvent}DESCRIPTION "Trap message will be sent in the event of a VC service associated notification request."::= 11 where: 11 = arbitrary, yet unique, trap number for the event you specified in the my_eventlog.cfg file





8. Using the full pathname, load the new notification configuration file by using the following command: $ nas_event -Load /nas/site/my_eventlog.cfg



Step Action


When the CAVA service is stopped and started, the Control Station generates SNMP trap messages and email. The /usr/sbin/snmptrapd daemon must be started on the Control Station to display SNMP trap messages. "Send a test SNMP trap" on page 35 provides more information.

9. Verify the new notifications (email and traps) have been accepted by using the following command:$ nas_event -list -action mail$ nas_event -list -action trap


The output should at least display:DART(1)|--> VC(81)BaseID Severity Brief_Description1 NOTICE(5) The virus checker is running normally.2 ERROR(3) ${type,8,%s} high water mark reached.3 WARNING(4) ${type,8,%s} low water mark reached.4 ERROR(3) No virus checker server is available.5 ERROR(3) No virus checker server is available. CIFS is stopped.6 ERROR(3) No virus checker server is available. Virus checking is stopped.7 ERROR(3) '${filename,8,%s}' was not checked.8 NOTICE(5) Server ${ipaddr,8,%s} is online. RPC program version ${rpc,2,%d}, ${cava,8,%s}.9 ERROR(3) Error on server ${ipaddr,8,%s}: ${status,8,%s}${winerror,8,%s}, RPC program version ${rpc,2,%d}, ${cava,8,%s}.10 NOTICE(5) The virus checker is started.11 NOTICE(5) Scanning was completed for file system ${fsid,2,%d} mounted on ${mountPath,8,%s}. ${dirs,2,%d} directories were scanned and ${files,2,%d} files were submitted to the scan engine.12 ERROR(3) Scanning was aborted for file system ${fsid,2,%d} mounted on ${mountPath,8,%s} for this reason: ${error,8,%s}. ${dirs,2,%d} directories were scanned and ${files,2,%d} files were submitted to the scan engine.13 ERROR(3) The antivirus (AV) engine deleted ${file,8,%s}, ${user,8,%s}.14 ERROR(3) The antivirus (AV) engine renamed ${file,8,%s}, ${user,8,%s}.15 WARNING(4) The antivirus (AV) engine modified ${file,8,%s}, ${user,8,%s}.16 NOTICE(5) The virus checker is stopped.

Step Action


Here are some examples of Virus Checker trap messages:

When Virus Checker is started, some of the following trap messages are generated:

Here is an example of a mail notification when Virus Checker is started:

Here is an example of a mail notification when Virus Checker is stopped:

Output

2008-02-06 13:32:42 matisse-cs0.rtp.dg.com [10.6.4.76] (via 127.0.0.1) TRAP, SNMP v1, community public SNMPv2-SMI::enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 19:44:34.83 SNMPv2-SMI::enterprises.1139.2.1.1.1 = INTEGER: 81 SNMPv2-SMI::enterprises.1139.2.1.1.2 = INTEGER: 4 SNMPv2-SMI::enterprises.1139.2.1.1.3 = INTEGER: 3 SNMPv2-SMI::enterprises.1139.2.1.1.4 = STRING: "Feb 6 13:32:42 2008 VC:3:4 No virus checker server is available. "2008-02-06 13:32:50 matisse-cs0.rtp.dg.com [10.6.4.76] (via 127.0.0.1) TRAP, SNMP v1, community public SNMPv2-SMI::enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 19:44:42.91 SNMPv2-SMI::enterprises.1139.2.1.1.1 = INTEGER: 81 SNMPv2-SMI::enterprises.1139.2.1.1.2 = INTEGER: 16 SNMPv2-SMI::enterprises.1139.2.1.1.3 = INTEGER: 5 SNMPv2-SMI::enterprises.1139.2.1.1.4 = STRING: "Feb 6 13:32:50 2008 VC:5:16 The virus checker is stopped. "

Output

SNMPv2-SMI::enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 19:52:45.25 SNMPv2-SMI::enterprises.1139.2.1.1.1 = INTEGER: 81 SNMPv2-SMI::enterprises.1139.2.1.1.2 = INTEGER: 10 SNMPv2-SMI::enterprises.1139.2.1.1.3 = INTEGER: 5 SNMPv2-SMI::enterprises.1139.2.1.1.4 = STRING: "Feb 6 13:40:52 2008 VC:5:10 Slot 2: 1089402969: The virus checker is started. "2008-02-06 13:41:20 matisse-cs0.rtp.dg.com [10.6.4.76] (via 127.0.0.1) TRAP, SNMP v1, community public SNMPv2-SMI::enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 19:53:12.58 SNMPv2-SMI::enterprises.1139.2.1.1.1 = INTEGER: 81 SNMPv2-SMI::enterprises.1139.2.1.1.2 = INTEGER: 10 SNMPv2-SMI::enterprises.1139.2.1.1.3 = INTEGER: 5 SNMPv2-SMI::enterprises.1139.2.1.1.4 = STRING: "Feb 6 13:41:20 2008 VC:5:10 Slot 3: 1089454545: The virus checker is started. "

Output

To: [email protected]: EMCServer matisse-cs0, Component - DART, Facility - VC, Severity - NOTICE

Feb 6 13:41:20 2008 DART:VC:NOTICE:10 Slot 3: 1089454545: The virus checker is started.

Output

To: [email protected]: EMCServer matisse-cs0, Component - DART, Facility - VC, Severity - NOTICE

Feb 6 13:32:50 2008 DART:VC:NOTICE:16 The virus checker is stopped.


When a hard or soft quota is exceededYou can configure the Celerra Network Server to generate SNMP traps and an email notification to several storage administrators whenever a hard or soft quota for users, groups, or trees is exceeded.

Configure Celerra to generate a notification when a quota is exceeded

Step Action




3. Use a text editor to add the following statements to my_eventlog.cfg:# email and trap notification for soft and hard quota exceeded#facilitypolicy 1:64, 7 disposition range=4-5, mail "[email protected]"disposition range=4-5, trap "/nas/site/trap.cfg 20"

where:facilitypolicy 1:64 = dispositions that need to be applied to events in the UFS facility (facility ID 64) of the DART component (component ID 1).7 = severity-level threshold (captures events of severity 7 or lower)[email protected] = email addresses that receive email notification. Replace these with one or more email addresses at company.disposition range=4-5 = events 4 through 5, which equates to the UFS events "Block soft quota crossed" and "Hard limit reached or exceeded."




4. Set up the SNMP Manager by adding the following line to the file: /nas/site/trap.cfg:snmpmanager a.b.c.d ; communityname public


5. Modify the Celerra MIB, found at /nas/sys/emccelerra.mib, to include the following lines:celUFS TRAP-TYPEENTERPRISE emcCelerraVARIABLES {celEvent}DESCRIPTION "Trap message will be sent in the event of a UFS quota exceeded."::=20

where: 20 = arbitrary, yet unique, trap number for the event you specified in the my_eventlog.cfg file.





8. Using the full pathname, load the new notification configuration file by using the following command:$ nas_event -Load /nas/site/my_eventlog.cfg



Step Action


When a hard or soft quota for users, groups, or trees is exceeded, the Control Station generates SNMP trap messages and email. The /usr/sbin/snmptrapd daemon must start on the Control Station to display SNMP trap messages. "Send a test SNMP trap" on page 35 provides more information.

When a hard or soft quota is exceeded, the following trap messages are generated:

9. Verify that the new notifications (email and traps) have been accepted by using the following command:$ nas_event -list -action mail$ nas_event -list -action trap


The output should at least display:DART(1)|--> UFS(64)BaseID Severity Brief_Description4 WARNING(4) Block soft quota crossed (fs ${mountPoint,55,%s}, ${idStr,8,%s} ${quotaId,25,%u})5 ERROR(3) Block hard quota reached/exceeded (fs ${mountPoint,55,%s}, ${idStr,8,%s} ${userId,25,%u})

10. Edit the quota event notification settings for the file systems on a Data Mover with the following command: $ nas_quotas -config -edit -mover server_2

11. You will see the following lines defining quota event notification settings for the file systems on the specified Data Mover:soft quota crossed: (no)hard quota crossed: (no)By default, the fields are set to (no), which disables event notification when the event occurs. To enable event reporting for the desired file systems, change their settings to (yes). Repeat this change of quota event notification settings for each Data Mover.

Output

2008-02-06 13:46:59 matisse-cs0.rtp.dg.com [10.6.4.76] (via 127.0.0.1) TRAP, SNMP v1, community public SNMPv2-SMI::enterprises.1139.2 Enterprise Specific Trap (20) Uptime: 19:58:51.70 SNMPv2-SMI::enterprises.1139.2.1.1.1 = INTEGER: 64 SNMPv2-SMI::enterprises.1139.2.1.1.2 = INTEGER: 4 SNMPv2-SMI::enterprises.1139.2.1.1.3 = INTEGER: 4 SNMPv2-SMI::enterprises.1139.2.1.1.4 = STRING: "Feb 6 13:46:59 2008 UFS:4:4 Slot 2: 1191867432: Block soft quota crossed (fs /root_vdm_1/ufs12, uid 32784). "2008-02-06 13:48:40 matisse-cs0.rtp.dg.com [10.6.4.76] (via 127.0.0.1) TRAP, SNMP v1, community public SNMPv2-SMI::enterprises.1139.2 Enterprise Specific Trap (20) Uptime: 20:00:32.66 SNMPv2-SMI::enterprises.1139.2.1.1.1 = INTEGER: 64 SNMPv2-SMI::enterprises.1139.2.1.1.2 = INTEGER: 5 SNMPv2-SMI::enterprises.1139.2.1.1.3 = INTEGER: 3 SNMPv2-SMI::enterprises.1139.2.1.1.4 = STRING: "Feb 6 13:48:40 2008 UFS:3:5 Slot 2: 1191867444: Block hard quota reached/exceeded (fs /root_vdm_1/ufs12, uid 32784). "

Step Action


When the file system hard or soft quota is exceeded, notifications similar to the following messages are sent:

Output

To: [email protected]: EMCServer matisse-cs0, Component - DART, Facility - UFS, Severity - WARNING

Feb 6 13:46:59 2008 DART:UFS:WARNING:4 Slot 2: 1191867432: Block soft quota crossed (fs /ufs2 , uid 32784).

To: [email protected]: EMCServer matisse-cs0, Component - DART, Facility - UFS, Severity - ERROR

Feb 6 13:48:40 2008 DART:UFS:ERROR:5 Slot 2: 1191867444: Block hard quota reached/exceeded (fs /ufs2, uid 32784).

Note

The 5 in DART:UFS:ERROR:5 indicates the UFS event "Block hard quota reached/exceeded" and 4 in DART:UFS:WARNING:4 indicates the UFS event "Block soft quota crossed.” The Data Mover (Slot 2) and the mount point of the file system (/ufs2) involved are shown. The u in uid indicates a user quota alert, treeid indicates a tree quota alert, and the g in gid indicates a group quota alert.


Change the SNMP port where SNMP traps are sentTo integrate Celerra's SNMP trap notifications mechanism with the EMC ControlCenter® NAS agent or another monitoring application already using the standard SNMP port 162, you can configure the SNMP port to which to send the trap.

Action

By using a text editor, add the following line to the file /nas/site/trap.cfg:snmpmanager <ipaddr>:<port_number>; communityname public

where:<ipaddr> = IP address of the host application<port_number> = port number where the application listens for SNMP trapsExample:snmpmanager 172.24.108.20:163; communityname public


Event notification actionsTable 6 on page 62 summarizes the Celerra Network Server notifications (actions) you can take when an event occurs.

Table 6 Celerra event notification actions

Action Arguments Description

logfile <logfile_pathname> Puts an entry in the Celerra log file specified by <logfile_pathname>.

mail <address> | user <address> – Sends email to the specified email address. Use a separate mail line for each additional email address.user – Sends email using the settings specified by the /nas/bin/nas_emailuser CLI or Support > Email User page.

trap <config_file> <trap_number> Sends SNMP trap number <trap_number> to the SNMP manager as defined in the <config_file> configuration file.SNMP traps are sent on UDP port 162.

callhome binary | immediate Generates a CallHome action to EMC.binary – Sends home a binary file (for EMC use only)immediate – Calls home immediatelyCallHome is configured when the system is installed. This action is for the use of EMC and its authorized service providers only.

exec <procedure_name> <args> Executes the procedure specified by <procedure_name> with the arguments specified by <args>.

udprpc <proc_num>,<prog_num>,<version>@<host>

Sends an RPC message (by using UDP) to a host, where <proc_num> is the RPC procedure number, <prog_num> is the program number, <version> is the version number, and <host> is the hostname. The <proc_num> and <prog_num> arguments are required. If <version> is not supplied, version 1 is the default. If <host> is not supplied, <localhost> is the default.

terminate Immediately terminates processing of the event, providing a way to override already defined actions so that troubleshooting can be performed.


TroubleshootingAs part of an effort to continuously improve and enhance the performance and capabilities of its product lines, EMC periodically releases new versions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.If a product does not function properly or does not function as described in this document, contact your EMC Customer Support Representative.

Where to get helpTo obtain EMC support, product, and licensing information:

Product information – For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support – For technical support, go to EMC Customer Service on Powerlink. After logging in to the EMC Powerlink website, go to Support > Request Support. To open a service request through Powerlink, you must have a valid support agreement. Contact your EMC Customer Support Representative for details about obtaining a valid support agreement or to answer any questions about your account.

Note: Do not request a specific support representative unless one has already been assigned to your particular system problem.

The Problem Resolution Roadmap for Celerra contains additional information about using Powerlink and resolving problems.

TelephoneU.S.: 800.782.4362 (SVC.4EMC)

Canada: 800.543.4782 (543.4SVC)

Worldwide: 508.497.7901

Note: Please do not request a specific support representative unless one has already been assigned to a particular system problem.

The Problem Resolution Roadmap for Celerra contains additional information about using Powerlink and resolving problems.

Email notifications not receivedIf the Control Station is not able to send a notification that specifies an email address as its destination, the Control Station places the message in its root user mailbox. Retrieve the message and check its header to verify the destination

http://Powerlink.EMC.com

../ProblemResolutionRoadmap/index.htm



../ProblemResolutionRoadmap/index.htm



address. You can use the mail log files in the /var/log directory to troubleshoot sendmail problems.

For more information on troubleshooting problems with the sendmail feature on Celerra Control Station refer to the online Support Solutions Knowledgebase available on Powerlink. From the Powerlink, home page, select Support > Knowledgebase Search > Support Solutions Search. Use the text “cannot send email event notifications” and limit the scope of the search to product Celerra by using the Refine by Product option.

Check if sendmail is runningUse this command to check if sendmail is running, as root (su -), type:

Configure sendmailTo configure sendmail on the Control Station perform the following steps:

Step Action

1. Log in to the Control Station as root. If you logged in with your administrative username and password, you can change to root by typing:$ su -

2. At the command prompt, type:# mail

This displays a list of messages addressed to root.

3. To see the list of commands for the mail program, at the mail prompt type:# help

Action

# ps -ef | grep sendmail

Output

If sendmail is running, you will see output similar to the following:root 29698 1 0 Jan07 ? 00:00:00 sendmail: accepting connections

If sendmail is not accepting connections, you must configure it.

Step Action

1. Log in to the Control Station as root. If you logged in with your administrative username and password, you can change to root by typing:$ su -

2. To configure sendmail, type:# /sbin/chkconfig --add sendmail# /sbin/service sendmail start




Notifications missing or not workingIf you believe an event has occurred and the notification you expected did not happen, first check the notification configuration files to see what other actions are defined for the event. For example, most events have a log file action defined. If so, you can check the appropriate log file to see if that action occurred, or if just a single action failed. You need to configure notifications in order to receive notifications once the events are posted.

Use a command similar to the following to view the quota event notification settings for file systems on a Data Mover:

nas_quotas -config -edit -mover server_2

You will see these lines defining quota event notification settings for the file systems on the specified Data Mover:

soft quota crossed: (no)hard quota crossed: (no)

By default, the fields are set to (no), which disables event notification when the event occurs. To enable event reporting for the desired file systems, change their settings to (yes). Repeat this change of quota event notification settings for each Data Mover on which the file systems are mounted.

Probable causes for not receiving email notifications include:

◆ Email exchange rejecting email

◆ Email exchange not being located

To troubleshoot:

◆ Check root's email inbox on the Celerra Control Station.

◆ Look for returned messages and look at the returned message to identify why it was returned.

Possible solutions:

◆ Ensure that the Control Station's hostname is in DNS and is resolvable from your email exchange.

◆ Ensure that your email exchange's IP address can be resolved by DNS from the Control Station.

◆ Ensure that the email exchange is responding.

Other solutions might be warranted as determined by the cause of the rejected email. If you do not see rejected emails, check the email notification configuration and look for email routing or delivery problems within your email system.


SNMP security issuesIf SNMP does not respond and you implemented SNMP security, follow these steps to troubleshoot the issue:

◆ Check the community name. Community names are case-sensitive. It is a general practice to use uppercase letters to begin community names. If you remove all community names, including the default name (public), SNMP does not respond to any community names presented.

◆ Ensure that the host is set to accept SNMP packets from specific hosts.

Verify generation of an SNMP trap as a result of a Celerra Network Server event If you believe an SNMP trap was not issued or was issued incorrectly, first check that the trap.cfg file is correct. "Configure SNMP traps" on page 34 provides more information on trap.cfg.

Use SNMP manager to determine if an SNMP trap is being issued correctly.

SNMP traps not working after Control Station restart or power outageIf the snmptrapd and snmpd daemons are not running, the SNMP trap messages you set up are not sent. After a Control Station restart or a power outage, the snmpd daemon might or might not start on a restart depending on being set up by /sbin/chkconfig to start.The snmptrapd daemon is not set up under the /sbin/chkconfig function, so it does not restart after a restart unless you write a run control script to start it or start it manually.

If you enable or disable SNMP through Celerra Manager > Security > Network Services, the daemon state survives a Control Station restart. It automatically sets up chkconfig.

Note: For NS series Control Stations, snmptrapd is already running.

To manually start the snmptrapd daemon, log in to the Control Station as root and type:

/usr/sbin/snmptrapd -f -Le -Lf /nas/var/log/my_eventlog_messages &

The command starts the snmptrapd daemon as a background process. Some Celerras do not have the /nbsnas directory. If this is true for your system, use the /nas/var/log directory.

The snmptrapd and snmpd daemons manage SNMP trap messages, which are logged to the my_eventlog_messages file.


Error messagesAs of version 5.6, all new event, alert, and status messages provide detailed information and recommended actions to help you troubleshoot the situation. To view message details, use any of these methods:◆ Celerra Manager:

• Right-click an event, alert, or status message and select to view Event Details, Alert Details, or Status Details.

◆ Celerra CLI:

• Type nas_message -info <MessageID>, where MessageID is the message identification number.

◆ Celerra Network Server Error Messages Guide:

• Use this guide to locate information about messages that are in the earlier-release message format.

◆ Powerlink:

• Use the text from the error message’s brief description or the message’s ID to search the Knowledgebase on Powerlink. After logging in to Powerlink, go to Support > Knowledgebase Search > Support Solutions Search.

../ErrorMsgs/index.htm

../ErrorMsgs/index.htm



Related informationFor specific information related to the features and functionality described in this document, refer to:

◆ Celerra Manager online help

◆ Celerra Network Server Command Reference Manual

◆ Celerra Network Server Parameters Guide

◆ Celerra Network Server System Operations

◆ Managing Celerra Volumes and File Systems with Automatic Volume Management

◆ Managing Celerra Volumes and File Systems Manually

◆ Online Celerra man pages

The EMC Celerra Network Server Documentation CD, supplied with the Celerra and also available on Powerlink, provides the complete set of EMC Celerra customer publications. After logging in to Powerlink, go to Support > Technical Documentation and Advisories > Hardware/Platforms Documentation > Celerra Network Server. On this page, click Add to Favorites. The Favorites section on your Powerlink home page provides a link that takes you directly to this page.

SNMP manager documentation has more information on SNMP.

Customer training programsEMC customer training programs are designed to help you learn how EMC storage products work together and integrate within your environment to maximize your entire infrastructure investment. EMC customer training programs feature online and hands-on training in state-of-the-art labs conveniently located throughout the world. EMC customer training programs are developed and delivered by EMC experts. For program information and registration, log in to Powerlink, our customer and partner website and select the Training menu.

../AVM/index.htm



../VolFSManually/index.htm

../CommandReference/index.htm

../Parameters/index.htm

../SystemOperations/index.htm



Appendix A: Specify an email subject lineIf you are running Celerra Network Server version 5.1 or earlier, you must define the subject line for email notifications when editing event log configuration file. Use the -s option as shown in the example to specify the subject for email notification. Join all parts of the subject (no blank spaces between parts). Do not join the recipient’s email address to the subject string.

Action

Add the following statements to my_eventlog.cfg:# CFS High Water Mark Event Control# notification for the file system size threshold exceeded# the -s option sets the subject line for the email notificationfacilitypolicy 1:27,1 disposition range=1-1, mail "-s EMCServer_cs_name,Facility-facility_name, Severity-severity recipient email address"

where:cs_name = name of the Control Station.facility_name = facility.severity = severity level.recipient email address = recipient’s email address.Example:$ mail "-s EMCServer_csA121,Component-DART,Facility-CFS,Severity-4 [email protected]"

Output

The following is an example of the email notification that includes the specified subject line:From: root@<server>Subject: EMCServer_csA121,Component-DART, Facility-CFS,Severity-4Feb 6 13:17:43 2008 DART:CFS:WARNING:1 Slot 3: 1191865801: filesystem size threshold (90%) crossed (fs /ufs1)


Appendix B: EventsThis section illustrates the relationship between components and event facilities and event facilities and particular events.

Table 7 on page 70 lists the event facilities in each component. Some event facilities appear under more than one component.

Table 7 Components and associated event facilities

DART (1) CS_CORE (2) XML_API (5) CS_PLATFORM (6)

ACLUPDADMINCAMCEPPCFSCHAMIIDBMSDNSDPSVCDRIVERSFCPFSTOOLSIPKERNELLOCKMGFSNDMPNETLIBNFSPERFSTATSRCPDREPSECMAPSECURITYSMBSTORAGESVFSUFSUSRMAPVCVMCASTVRPLWINSXLT

CICCommandServiceDBMSNASDBRDFChannelREPSVFS

APIQuotaCache ADMINBoxMonitorCFSCheckupConnectHomeEmailUserEventLogFSTOOLSJServerLocalHardwareMonitorLogCollectMasterControlMGFSNASDBNaviEventMonitorNDMPSECURITYSNAPSURE_SCHEDSVFSSYRUPSMonitorVMCASTXLT


Table 8 provides cross-references to events for each event facility.

Subsequent tables provide a list of base (event) IDs, message IDs, severities, and brief descriptions for each event. You can use the following command on the Control Station to generate the output contained in all the tables:

$ export NAS_DB=/nas ; /nas/bin/nas_event -l -c -i \| awk '/^[ ]*[0-9]+/{print $1}' | xargs -n1 -i bash -c \"export COMP={} ; /nas/bin/nas_event -l -c {} -i | awk '/^[ ]*[0-9]+/{print \$1}'\| xargs -n1 -i /nas/bin/nas_event -l -c \$COMP -f \{\} -id" | fgrep -v 'DEBUG(7)'

Note: Most brief descriptions in the tables use variables preceded by the $ symbol. The Celerra substitutes a value for the variable.

Table 8 Event facility event list cross-reference (page 1 of 3)

Event facility Location

ACLUPD "ACLUPD (101) event facility (DART)" on page 73

ADMIN "ADMIN (24) event facility (DART)" on page 74"ADMIN (24) event facility (CS_PLATFORM)" on page 74

APIQuotaCache "APIQuotaCache (7) event facility (XML API)" on page 75

BoxMonitor "BoxMonitor (131) event facility (CS_PLATFORM)" on page 75

CAM "CAM (26) event facility (DART)" on page 85

CEPP "CEPP (146) event facility (DART)" on page 85

CFS "CFS (27) event facility (DART)" on page 86"CFS (27) event facility (CS_PLATFORM)" on page 86

CHAMII "CHAMII (86) event facility (DART)" on page 88

Checkup "Checkup (142) event facility (CS_PLATFORM)" on page 88

CIC "CIC (109) event facility (CS_CORE)" on page 90

CommandService "CommandService (9) event facility (CS_CORE)" on page 90

ConnectHome "ConnectHome (133) event facility (CS_PLATFORM)" on page 91

DBMS "DBMS (122) event facility (DART)" on page 91"DBMS (122) event facility (CS_CORE)" on page 91

DNS "DNS (118) event facility (DART)" on page 92

DPSVC "DPSVC (111) event facility (DART)" on page 92

DRIVERS "DRIVERS (36) event facility (DART)" on page 93


EmailUser "EmailUser (144) event facility (CS_PLATFORM)" on page 94

EventLog "EventLog (130) event facility (CS_PLATFORM)" on page 94

FCP "FCP (102) event facility (DART)" on page 96

FSTOOLS "FSTOOLS (40) event facility (DART)" on page 98"FSTOOLS (40) event facility (CS_PLATFORM)" on page 98

IP "IP (43) event facility (DART)" on page 99

JServer "JServer (135) event facility (CS_PLATFORM)" on page 99

KERNEL "KERNEL (45) event facility (DART)" on page 102

LocalHardwareMonitor "LocalHardwareMonitor (139) event facility (CS_PLATFORM)" on page 102

LOCK "LOCK (68) event facility (DART)" on page 104

LogCollect "LogCollect (141) event facility (CS_PLATFORM)" on page 104

MasterControl "MasterControl (129) event facility (CS_PLATFORM)" on page 107

MGFS "MGFS (75) event facility (DART)" on page 108"MGFS (75) event facility (CS_PLATFORM)" on page 108

NASDB "NASDB (137) event facility (CS_PLATFORM)" on page 108"NASDB (137) event facility (CS_CORE)" on page 109

NaviEventMonitor "NaviEventMonitor (138) event facility (CS_PLATFORM)" on page 109

NDMP "NDMP (51) event facility (DART)" on page 110"NDMP (51) event facility (CS_PLATFORM)" on page 110

NETLIB "NETLIB (73) event facility (DART)" on page 111

NFS "NFS (52) event facility (DART)" on page 111

PERFSTATS "PERFSTATS (144) event facility (DART)" on page 112

RCPD "RCPD (83) event facility (DART)" on page 112

RDFChannel "RDFChannel (11) event facility (CS_CORE)" on page 112

REP "REP (108) event facility (DART)" on page 112"REP (108) event facility (CS_CORE)" on page 115




SECMAP "SECMAP (115) event facility (DART)" on page 120

SECURITY "SECURITY (54) event facility (DART)" on page 120"SECURITY (54) event facility (CS_PLATFORM)" on page 121

SMB "SMB (56) event facility (DART)" on page 121

SNAPSURE_SCHED "SNAPSURE_SCHED (91) event facility (CS_PLATFORM)" on page 121

STORAGE "STORAGE (58) event facility (DART)" on page 122

SVFS "SVFS (70) event facility (DART)" on page 123"SVFS (70) event facility (CS_PLATFORM)" on page 123"SVFS(70) event facility (CS_CORE)" on page 124

SYR "SYR (143) event facility (CS_PLATFORM)" on page 124

UFS "UFS (64) event facility (DART)" on page 125

UPSMonitor "UPSMonitor (140) event facility (CS_PLATFORM)" on page 127

USRMAP "USRMAP (93) event facility (DART)" on page 130

VC "VC (81) event facility (DART)" on page 130

VMCAST "VMCAST (84) event facility (DART)" on page 132"VMCAST (84) event facility (CS_PLATFORM)" on page 132

VRPL "VRPL (77) event facility (DART)" on page 133

WINS "WINS (117) event facility (DART)" on page 134

XLT "XLT (72) event facility (DART)" on page 134"XLT (72) event facility (CS_PLATFORM)" on page 135



Table 9 ACLUPD (101) event facility (DART) (page 1 of 2)

Base ID Message ID Severity Brief description

1 90469367809 NOTICE(5) The "acl database resetall" command as started on file system ${fileSystem,8,%s}

2 90469367810 NOTICE(5) The "acl database resetall" command ended successfully on the file system ${fileSystem,8,%s}


3 90469367811 NOTICE(5) The "acl database checkall" command has started on file system ${fileSystem,8,%s}

4 90469367812 NOTICE(5) The "acl database checkall" has ended successfully on file system ${fileSystem,8,%s}

5 90469367813 NOTICE(5) The "acl database setsd" command has started on file system ${fileSystem,8,%s}

6 90469367814 NOTICE(5) The "acl database setsd" command has ended on file system ${fileSystem,8,%s}

7 90469367815 NOTICE(5) The "acl database migdom" command has started on file system ${fileSystem,8,%s}

8 90469367816 NOTICE(5) The "acl database migdom" command has ended on file system ${fileSystem,8,%s}

9 90469367817 NOTICE(5) The "acl database historysid" command has started on file system ${fileSystem,8,%s}

10 90469367818 NOTICE(5) The "acl database historysid" command has ended on file system ${fileSystem,8,%s}

11 90469367819 NOTICE(5) The "acl database printstats" command has started on file system ${fileSystem,8,%s}

12 90469367820 NOTICE(5) The "acl database printstats" command has ended successfully on file system ${fileSystem,8,%s}

13 90469367821 NOTICE(5) The "acl database dumpall" command has started on file system ${fileSystem,8,%s}

14 90469367822 NOTICE(5) The "acl database dumpall" command has ended successfully on file system ${fileSystem,8,%s}

15 81879433231 ERROR(3) The command ${command,8,%s} has ended with an error on the file system ${fileSystem,8,%s}

Table 9 ACLUPD (101) event facility (DART) (page 2 of 2)


Table 10 ADMIN (24) event facility (DART)


1 68989485057 EMERGENCY(0) ${command,8,%s}

Table 11 ADMIN (24) event facility (CS_PLATFORM) (page 1 of 2)


15 87511531535 WARNING(4) ${ARG0,8,%s}[${PID,5,%u}]: Already running. Exiting.


16 87511531536 WARNING(4) ${ARG0,8,%s}[${PID,5,%u}]: Do not understand line ${LINE_NUMBER,5,%u} in ${CFG_FILENAME,59,%s}.

17 87511531537 WARNING(4) ${ARG0,8,%s}[${PID,5,%u}]: Couldn't create ${CFG_FILENAME,59,%s}. exiting.

18 87511531538 WARNING(4) ${ARG0,8,%s}[${PID,5,%u}]: FS ${DEV_NAME,8,%s} mounted on ${MOUNT_POINT,55,%s} filling up (at ${PERCENT_USED,18,%d}%, max = ${PERCENT_MAX,18,%d}%).

19 70331662355 EMERGENCY(0) nas_watchdog: ${FAULT_MESSAGE,8,%s}

Table 11 ADMIN (24) event facility (CS_PLATFORM) (page 2 of 2)


Table 12 APIQuotaCache (7) event facility (XML API)


1 82947014657 ERROR(3) Unable to initialize quota cache.

2 82947014658 ERROR(3) Unable to refresh quota cache.

Table 13 BoxMonitor (131) event facility (CS_PLATFORM) (page 1 of 11)


1 78928609281 CRITICAL(2) EPP failed to initialize.

2 78928609282 CRITICAL(2) Failed to create socket for UDP RPC transport handle.

3 78928609283 CRITICAL(2) Failed to create ${threadname,8,%s} thread.

4 78928609284 CRITICAL(2) SIB Read failure: ${string,8,%s}

5 78928609285 CRITICAL(2) SIB Write failure: ${string,8,%s}

6 74633641990 ALERT(1) AC power failure 0x${boxmask,2,%x}.

7 78928609287 CRITICAL(2) Slot ${m_slotID,2,%d}, Fan 0 has failed.

8 78928609288 CRITICAL(2) Slot ${m_slotID,2,%d}, Fan 1 has failed.

9 78928609289 CRITICAL(2) Slot ${m_slotID,2,%d}, both fans have failed.

10 78928609290 CRITICAL(2) Slot ${m_slotID,2,%d}, high temperature warning.

11 78928609291 CRITICAL(2) Slot ${m_slotID,2,%d}, over temperature failure.

12 78928609292 CRITICAL(2) Slot ${m_slotID,2,%d}, 12V DC supply high.

13 78928609293 CRITICAL(2) Slot ${m_slotID,2,%d}, 12V DC supply low.

14 78928609294 CRITICAL(2) Slot ${m_slotID,2,%d}, 5V DC supply high.


15 78928609295 CRITICAL(2) Slot ${m_slotID,2,%d}, 5V DC supply low.

16 78928609296 CRITICAL(2) Slot ${m_slotID,2,%d}, 3.3V DC supply high.

17 78928609297 CRITICAL(2) Slot ${m_slotID,2,%d}, 3.3V DC supply low.

18 78928609298 CRITICAL(2) Slot ${m_slotID,2,%d}, -12V DC supply high.

19 78928609299 CRITICAL(2) Slot ${m_slotID,2,%d}, -12V DC supply low.

20 78928609300 CRITICAL(2) Slot ${m_slotID,2,%d}, -5V DC supply high.

21 78928609301 CRITICAL(2) Slot ${m_slotID,2,%d}, -5V DC supply low.

22 78928609302 CRITICAL(2) Slot ${m_slotID,2,%d}, Service Mode switch enabled.

23 96108478487 INFO(6) Battery backup enabled.

24 78928609304 CRITICAL(2) Battery backup disabled.

25 96108478489 INFO(6) ${name,8,%s} ${m_slotID_1,2,%ld} has been ${string,8,%s}.

26 78928609306 CRITICAL(2) ${name,8,%s} ${m_slotID_1,2,%ld} has been removed.









35 96108478499 INFO(6) Slot ${id,2,%ld} has been detected.

36 78928609316 CRITICAL(2) Slot ${id,2,%ld} has been removed.

37 96108478501 INFO(6) Backplane unit ${unit,2,%ld} detected on Commbd ${id,1,%c}.

38 74633642022 ALERT(1) Commboards report different ${badconfig,8,%s} configurations.

41 96108478505 INFO(6) Slot ${slotID,2,%ld} ${string,8,%s}.

42 96108478506 INFO(6) Slot ${slotID,2,%ld} has rebooted with (${attempts,2,%d}) attempts.

43 78928609323 CRITICAL(2) Slot ${id,2,%ld} failed to respond to ping at server_${slot,2,%d}${string,8,%s}.

45 96108478509 INFO(6) Slot ${id,2,%ld} has rebooted with (${attempts,2,%d}) attempts.

46 96108478510 INFO(6) The BoxMonitor version number is displayed.












55 96108478519 INFO(6) Invalid command line argument: ${errormsg,8,%s}

56 96108478520 INFO(6) Changed a command line argument: ${argchangemsg,8,%s}

58 78928609338 CRITICAL(2) AC power has been lost; powerdown in ${timeout_wait,2,%d} seconds.

59 96108478523 INFO(6) AC power is OK.

61 78928609341 CRITICAL(2) Black power switch is OFF. Cabinet will be powered down.

62 78928609342 CRITICAL(2) EPO Box cable is not connected.

63 78928609343 CRITICAL(2) Battery cable is not connected.

64 78928609344 CRITICAL(2) Main AC line cord is not plugged in.

65 78928609345 CRITICAL(2) Comm Board 12V Backup alarm has occurred.

66 78928609346 CRITICAL(2) Power Supply ${ps,2,%d} failed.

67 78928609347 CRITICAL(2) System fan in tray ${fan,2,%d} failed.

68 78928609348 CRITICAL(2) Mux Board 12V over current.

69 96108478533 INFO(6) Slot ${index,2,%d} parameter ${name,8,%s} set to ${cp,8,%s}.

70 78928609350 CRITICAL(2) Can not open /etc/hosts file.

71 78928609351 CRITICAL(2) Slot ${id,2,%ld} hardware or thermal failure [${oldreason,2,%ld} to ${reason,2,%ld}].

72 78928609352 CRITICAL(2) Slot ${id,2,%ld} sibpost failure.

73 78928609353 CRITICAL(2) Slot ${m_slotID,2,%ld} serial connection failure.

74 78928609354 CRITICAL(2) Control Station Local Network Connection failure.

75 96108478539 INFO(6) Control Station Local Network Connection restored.

76 96108478540 INFO(6) Battery is OK.

77 78928609357 CRITICAL(2) Slot ${m_slotID,2,%d}, RS485 Network A Failure.

78 78928609358 CRITICAL(2) Slot ${m_slotID,2,%d}, RS485 Network B Failure.

79 96108478543 INFO(6) ${name,8,%s} ${m_slotID_1,2,%ld} has been removed.

80 78928609360 CRITICAL(2) Battery backup disabled and batteries not charging.




81 96108478545 INFO(6) Battery backup enabled.

82 78928609362 CRITICAL(2) ${name,8,%s} ${m_slotID_1,2,%ld} has been ${string,8,%s}.










92 74633642076 ALERT(1) ${badconfig,8,%s} Commbd ${Commbd,1,%c}.








100 78928609380 CRITICAL(2) Slot ${m_slotID,2,%ld} reason code of ${reason,2,%ld} is stale.



















116 78928609396 CRITICAL(2) 20 seconds timeout after Red Switch is turned OFF.

117 78928609397 CRITICAL(2) Internal EPO failure.

118 78928609398 CRITICAL(2) EPO switch cable in not connected.

119 78928609399 CRITICAL(2) EPO switched to backup 12V from Comm Board.

120 78928609400 CRITICAL(2) Battery is OFF or not inserted.

121 78928609401 CRITICAL(2) Battery charge low.

122 78928609402 CRITICAL(2) Battery charger ${charger,2,%d} is not inserted.

123 78928609403 CRITICAL(2) Auxiliary AC line cord is not plugged in.

124 78928609404 CRITICAL(2) Main AC has transferred over to auxiliary AC line.

125 78928609405 CRITICAL(2) Comm Board 5V fallen below 4.4V.

126 78928609406 CRITICAL(2) Comm Board 5V reading has gone Over Voltage.

127 78928609407 CRITICAL(2) Power Supply ${ps,2,%d} is off.

128 78928609408 CRITICAL(2) Power Supply ${ps,2,%d} is overheated.

129 78928609409 CRITICAL(2) Mux Board 5V is out of range.

130 78928609410 CRITICAL(2) Mux Board 12V is out of range.

131 78928609411 CRITICAL(2) CD-ROM power is OFF.

132 78928609412 CRITICAL(2) One or more of Lplane three red switches is ON.

133 78928609413 CRITICAL(2) Comm Board service switch (Sw 5) is ON.

134 78928609414 CRITICAL(2) DART power switch (Sw 2) is OFF.




135 78928609415 CRITICAL(2) This is an unsupported diagnostic message from the commboard.

136 78928609416 CRITICAL(2) This is an unsupported diagnostic message from the commboard.

150 78928609430 CRITICAL(2) Failed to bind socket for UDP RPC transport handle.

151 78928609431 CRITICAL(2) Failed to create UDP RPC transport handle.

152 78928609432 CRITICAL(2) Failed to register RPC service on UDP.

200 78928609480 CRITICAL(2) Slot ${m_slotID,2,%ld} Both internal interfaces are down.
















300 78928609580 CRITICAL(2) Slot ${m_slotID,2,%ld} has panicked.



















400 78928609680 CRITICAL(2) Slot ${m_slotID,2,%ld} Cannot get status using the MAC interface.
















440 83223577016 ERROR(3) Slot ${m_slotID,2,%ld} last 5 attempts to set reason code to "contacted" failed.




500 78928609780 CRITICAL(2) Enclosure ${encid,2,%ld} compute blade ${num,1,%c} has been removed.

501 96108478965 INFO(6) Enclosure ${encid,2,%ld} compute blade ${num,1,%c} has been detected.

502 78928609782 CRITICAL(2) Enclosure ${encid,2,%ld} CPU module ${cpu,1,%c} fault.

503 96108478967 INFO(6) Enclosure ${encid,2,%ld} CPU module ${cpu,1,%c} is OK.

504 78928609784 CRITICAL(2) Enclosure ${encid,2,%ld} CPU ${cpu,1,%c} I/O Module 0 fault.

505 96108478969 INFO(6) Enclosure ${encid,2,%ld} CPU ${cpu,1,%c} I/O Module 0 is OK.

506 78928609786 CRITICAL(2) Enclosure ${encid,2,%ld} CPU ${cpu,1,%c} I/O Module 1 fault.

507 96108478971 INFO(6) Enclosure ${encid,2,%ld} CPU ${cpu,1,%c} I/O Module 1 is OK.

508 78928609788 CRITICAL(2) Enclosure ${encid,2,%ld} I/O Annex ${ioannex,1,%c} has been removed.

509 96108478973 INFO(6) Enclosure ${encid,2,%ld} I/O Annex ${ioannex,1,%c} has been detected.

510 78928609790 CRITICAL(2) Enclosure ${encid,2,%ld} I/O Annex ${ioannex,1,%c} fault.

511 96108478975 INFO(6) Enclosure ${encid,2,%ld} I/O Annex ${ioannex,1,%c} is OK.

512 78928609792 CRITICAL(2) Enclosure ${encid,2,%ld} management switch ${num,1,%c} has been removed.

513 96108478977 INFO(6) Enclosure ${encid,2,%ld} management switch ${num,1,%c} has been detected.

514 78928609794 CRITICAL(2) Enclosure ${encid,2,%ld} management switch ${num,1,%c} ${string,8,%s}.

515 78928609795 CRITICAL(2) Enclosure ${encid,2,%ld} blade ${num,1,%c} I2C PS${AorB,1,%c} bus error.

516 96108478980 INFO(6) Enclosure ${encid,2,%ld} management switch ${num,1,%c} ${string,8,%s}.

517 78928609797 CRITICAL(2) Enclosure ${encid,2,%ld} power supply ${num,1,%c} has been removed.

518 96108478982 INFO(6) Enclosure ${encid,2,%ld} power supply ${num,1,%c} has been detected.

519 78928609799 CRITICAL(2) Enclosure ${encid,2,%ld} power supply ${num,1,%c} fault.

520 96108478984 INFO(6) Enclosure ${encid,2,%ld} power supply ${num,1,%c} is OK.

521 78928609801 CRITICAL(2) Enclosure ${encid,2,%ld} blower ${num,1,%c} ${string,8,%s}.

522 96108478986 INFO(6) Enclosure ${encid,2,%ld} blower ${num,1,%c} ${string,8,%s}.

523 78928609803 CRITICAL(2) Enclosure ${encid,2,%ld} multi-fan fault.




524 78928609804 CRITICAL(2) Slot ${id,2,%ld} boot error (Post Code = 0x${pcode,2,%.2x} ; Mid Code = 0x${mcode,2,%.2x} ; Blade Code = 0x${bcode,2,%.2x}).

525 83223577101 ERROR(3) Slot ${id,2,%ld} reason code query failed (error ${estatus,2,%d} : ${string,8,%s})

526 78928609806 CRITICAL(2) Enclosure ${encid,2,%ld} failed to respond to "ping" at management switch ${num,1,%c}.

527 78928609807 CRITICAL(2) Enclosure ${encid,2,%ld} both management switches failed to respond to "ping".

528 96108478992 INFO(6) Enclosure ${encid,2,%ld} management switch ${num,1,%c} port ${port,1,%c} is ${string,8,%s}.

529 96108478993 INFO(6) Enclosure ${encid,2,%ld} management switch ${num,1,%c} port ${port,1,%c} is ${string,8,%s}.

530 87518544402 WARNING(4) Slot ${id,2,%ld} Ignoring ${string,8,%s} request because of management switch problems.

531 96108478995 INFO(6) UPS ${num,2,%d} has been detected.

532 87518544404 WARNING(4) UPS ${num,2,%d} has been removed or cannot be detected.

533 96108478997 INFO(6) Failed to open ${filename,8,%s}.

534 96108478998 INFO(6) UPS ${num,2,%d} is turned off because of AC failure.

535 96108478999 INFO(6) UPS ${num,2,%d} is turned on because of dual AC failure.

536 78928609816 CRITICAL(2) Enclosure ${encid,2,%ld} fault ${temp,1,%c} occurred.

537 96108479001 INFO(6) Enclosure ${encid,2,%ld} is OK ${temp,1,%c}.

538 78928609818 CRITICAL(2) Enclosure ${encid,2,%ld} CPU module ${cpumodule,1,%c} NAS Personality Module fault.

539 96108479003 INFO(6) Enclosure ${encid,2,%ld} CPU module ${cpumodule,1,%c} NAS Personality Module is OK.

540 96108479004 INFO(6) Enclosure ${encid,2,%ld} CPU module ${cpumodule,1,%c} DIMM ${num,1,%d} is OK.

541 78928609821 CRITICAL(2) Enclosure ${encid,2,%ld} CPU module ${cpumodule,1,%c} DIMM ${num,1,%d} fault.

542 78928609822 CRITICAL(2) Enclosure ${encid,2,%ld} Blade ${blade,1,%c} over temperature.

543 96108479007 INFO(6) Enclosure ${encid,2,%ld} Blade ${blade,1,%c} is OK.

544 78928609824 CRITICAL(2) Enclosure ${encid,2,%ld} I/O Annex ${ioannex,1,%c} Fan ${fan,1,%c} is faulted.

545 96108479009 INFO(6) Enclosure ${encid,2,%ld} I/O Annex ${ioannex,1,%c} Fan ${fan,1,%c} is OK.

546 78928609826 CRITICAL(2) Enclosure ${encid,2,%ld} I/O Annex ${annex,1,%c} over temperature.




550 78928609830 CRITICAL(2) Enclosure ${encid,2,%ld} blade ${num,1,%c} I2C PS${AorB,1,%c} arbitration line frozen.

551 78928609831 CRITICAL(2) Enclosure ${encid,2,%ld} management switch ${num,1,%c} error (${fruname,8,%s} ${frunum,1,%c} presence contradiction).

552 78928609832 CRITICAL(2) Enclosure ${encid,2,%ld} management switch ${num,1,%c} RS-232, no peer traffic on ${AorB,1,%c}.

553 78928609833 CRITICAL(2) Enclosure ${encid,2,%ld} blade ${num,1,%c} I2C arbitration line frozen.

554 78928609834 CRITICAL(2) Enclosure ${encid,2,%ld} management switch ${num,1,%c} Midplane ID Read Error.

555 78928609835 CRITICAL(2) Enclosure ${encid,2,%ld} management switch ${num,1,%c} RS-232, no peer traffic.

556 78928609836 CRITICAL(2) Enclosure ${encid,2,%ld} blade ${num,1,%c} I2C MP Bus Error.

557 78928609837 CRITICAL(2) Enclosure ${encid,2,%ld} power supply ${num,1,%c} ambient over temperature.

558 78928609838 CRITICAL(2) Enclosure ${encid,2,%ld} power supply ${num,1,%c} AC Fault.

600 78928609880 CRITICAL(2) Slot ${m_slotID,24,%u} failover failure (pid=${m_processID,24,%u}; fromslot=${m_fromSlotID,24,%u})



















999 96108479463 INFO(6) No message is available.



Table 14 CAM (26) event facility (DART)


1 81874518017 ERROR(3) The SCSI HBA ${hbano,2,%d} is operating normally.

2 81874518018 ERROR(3) Warning: The SCSI HBA ${hbano,2,%d} has failed.

3 81874518019 ERROR(3) Warning: The SCSI HBA ${hbano,2,%d} is inaccessible.

4 81874518020 ERROR(3) I/O Error: c${path_id,5,%u}t${target_id,5,%u}l${target_lun,5,%u} Irp 0x${irp,2,%08x} CamStatus 0x${cam_status,2,%02x} ScsiStatus 0x${scsi_status,2,%02x} Sense 0x${sns_key,2,%02x}/0x${asc,2,%02x}/0x${asq,2,%02x}

Table 15 CEPP (146) event facility (DART)


1 90472316929 NOTICE(5) CEPP server ${ipaddr,8,%s} of pool ${pool,8,%s} is ${status,8,%s}. Vendor ${vendor,8,%s}, ntStatus 0x${ntstatus,2,%x}.

2 81882382338 ERROR(3) Error on CEPP server ${ipaddr,8,%s} of pool ${pool,8,%s}: ${status,8,%s}. Vendor ${vendor,8,%s}, ntStatus 0x${ntstatus,2,%x}.

3 90472316931 NOTICE(5) The CEPP facility is started.

4 90472316932 NOTICE(5) The CEPP facility is stopped.


Table 16 CFS (27) event facility (DART)


1 86169550849 WARNING(4) filesystem size threshold (${usageHWM,2,%d}%) crossed (fs ${mountPath,55,%s})

3 86169550851 WARNING(4) The file system size (fs ${mountPath,8,%s}) dropped below the threshold of (${usageHWM,2,%d}%)

4 86169550852 WARNING(4) File system size threshold (${size,5,%u}%) was crossed for (fs ${fsname,68,%s})

5 86169550853 WARNING(4) The file system size (fs ${mountPath,8,%s}) dropped below the threshold of (${usageHWM,2,%d}%)

6 94759485446 INFO(6) FsId: ${id,5,%lu} MaxSize: ${maxSize,2,%d} MB HWM: ${usage,2,%d}%. ${extSizeStr,8,%s}

Table 17 CFS (27) event facility (CS_PLATFORM) (page 1 of 2)


101 83216760933 ERROR(3) fs auto extension failed:

102 96101662822 INFO(6) fs auto extension start: [${FS_NAME,68,%s}] max_size:${FS_MAX_SIZE,3,%lld} hwm:${HWM,18,%d} (${DM_EVENT_STAMP,8,%s})

103 87511728231 WARNING(4) fs auto extension: ${FS_NAME,68,%s} (size:${FS_SIZE,3,%lld}) has reached its max_size:${FS_MAX_SIZE,3,%lld} and cannot be extended (${DM_EVENT_STAMP,8,%s})

104 83216760936 ERROR(3) fs auto extension failed: unable to determine ${FS_NAME,68,%s} % used (${DM_EVENT_STAMP,8,%s})

105 83216760937 ERROR(3) fs auto extension failed: unable to determine ${FS_NAME,68,%s} file system size (${DM_EVENT_STAMP,8,%s})

106 83216760938 ERROR(3) fs auto extension failed: unable to determine ${FS_NAME,68,%s} file system available space (${DM_EVENT_STAMP,8,%s})

107 83216760939 ERROR(3) fs auto extension failed: ${FS_NAME,68,%s} is not RW mounted (${DM_EVENT_STAMP,8,%s})

108 83216760940 ERROR(3) fs auto extension failed: no space available to extend ${FS_NAME,68,%s} (${DM_EVENT_STAMP,8,%s})

109 83216760941 ERROR(3) fs auto extension failed: unable to determine ${FS_NAME,68,%s} available pool size (${DM_EVENT_STAMP,8,%s})

110 83216760942 ERROR(3) fs auto extension failed: unable to determine ${FS_NAME,68,%s} slice flag (${DM_EVENT_STAMP,8,%s})


111 83216760943 ERROR(3) fs auto extension failed: space available for ${FS_NAME,68,%s} is ${EXT_SIZE,2,%ld}M and minimum extension size is 2M (${DM_EVENT_STAMP,8,%s})

112 83216760944 ERROR(3) fs auto extension failed: unable to retrieve FS_ID from event (${DM_EVENT_STAMP,8,%s})

113 83216760945 ERROR(3) fs auto extension failed: invalid FS_ID: ${FS_ID,22,%u} (${DM_EVENT_STAMP,8,%s})

114 83216760946 ERROR(3) fs auto extension failed: unable to retrieve FS_MAX_SIZE from event, fs id=${FS_ID,22,%u} (${DM_EVENT_STAMP,8,%s})

115 83216760947 ERROR(3) fs auto extension failed: unable to retrieve hwm from event, fs id=${FS_ID,22,%u} (${DM_EVENT_STAMP,8,%s})

116 96101662836 INFO(6) fs auto extension forced ext start: [${FS_NAME,68,%s}] max_size:${FS_MAX_SIZE,3,%lld} hwm:${HWM,18,%d} (${DM_EVENT_STAMP,8,%s})

117 96101662837 INFO(6) fs auto extension end: [${FS_NAME,68,%s}] fs_usage:${USED,3,%lld} hwm:${HWM,18,%d} (${DM_EVENT_STAMP,8,%s})

118 96101662838 INFO(6) fs auto extension end: [${FS_NAME,68,%s}] fs_size:${FS_SIZE,3,%lld} max_size:${FS_MAX_SIZE,3,%lld} (${DM_EVENT_STAMP,8,%s})

119 96101662839 INFO(6) fs auto extension forced ext -no action: space available for ${FS_NAME,68,%s} is ${FS_AVAIL_SIZE,8,%s}, dart requested size is ${DART_REQUEST_SIZE,2,%ld}

120 96101662840 INFO(6) fs auto extension: ${FS_NAME,68,%s} pool available size: ${AVAIL_POOL_SIZE,3,%lld}; calculated extend size: ${EXT_SIZE,2,%ld}. Use pool available size as extend size (${DM_EVENT_STAMP,8,%s})

121 96101662841 INFO(6) fs auto extension: ${FS_NAME,68,%s} extend request ${EXT_SIZE,2,%ld} succeeded (${DM_EVENT_STAMP,8,%s})

122 96101662842 INFO(6) fs auto extension forced ext end: [${FS_NAME,68,%s}] fs_size:${FS_SIZE,3,%lld} max_size:${FS_MAX_SIZE,3,%lld} (${DM_EVENT_STAMP,8,%s})

123 83216760955 ERROR(3) fs auto extension failed: unable to determine ${FS_NAME,68,%s} volume id (${DM_EVENT_STAMP,8,%s})

124 83216760956 ERROR(3) fs auto extension failed: unable to determine ${FS_NAME,68,%s} storage id (${DM_EVENT_STAMP,8,%s})

125 83216760957 ERROR(3) fs auto extension failed: ${FS_NAME,68,%s} is across multiple storage backends, auto-extension is not supported (${DM_EVENT_STAMP,8,%s})

126 83216760958 ERROR(3) The file system auto-extension operation failed for ${FS_NAME,68,%s} (${DM_EVENT_STAMP,8,%s})

Table 17 CFS (27) event facility (CS_PLATFORM) (page 2 of 2)



Table 18 CHAMII (86) event facility (DART)


1 94763352065 INFO(6) Power Supply A was removed.

5 94763352069 INFO(6) Power Supply A is OK.

6 73288515590 ALERT(1) Power Supply A failed: ${details,8,%s}

10 94763352074 INFO(6) Power Supply B was installed.

11 94763352075 INFO(6) Power Supply B was removed.

15 94763352079 INFO(6) Power Supply B is OK.

16 73288515600 ALERT(1) Power Supply B failed:${details,8,%s}

21 73288515605 ALERT(1) One or more fans in Fan Module 1 failed.



26 73288515610 ALERT(1) Multiple fans failed. Critical.

28 94763352092 INFO(6) ALL Fans are OK.

29 94763352093 INFO(6) XPE Enclosure is OK.

31 73288515615 ALERT(1) Power Supply A is going to shutdown.

32 73288515616 ALERT(1) Power Supply B is going to shutdown

33 73288515617 ALERT(1) Both Power Supplies are going to shutdown.

50 94763352114 INFO(6) Power Supply A was installed.

101 86173417573 WARNING(4) Warning: ${dmilogwarning,8,%s}

102 81878450278 ERROR(3) Error: ${dmilogerror,8,%s}

103 94763352167 INFO(6) Info: ${dmiloginfo,8,%s}

Table 19 Checkup (142) event facility (CS_PLATFORM) (page 1 of 2)


10 96109199370 INFO(6) nas_checkup has found no problems.

11 96109199371 INFO(6) nas_checkup has posted the information. See ${logfile,8,%s} for more details.

12 87519264780 WARNING(4) nas_checkup has posted a warning. See ${logfile,8,%s} for more details.

13 83224297485 ERROR(3) nas_checkup has discovered an error. See ${logfile,8,%s} for more details.


19 96109199379 INFO(6) nas_checkup exited before checking system health.

21 96109199381 INFO(6) nas_checkup has posted information. See ${logfile,8,%s} for more details.

22 87519264790 WARNING(4) nas_checkup has posted a warning. See ${logfile,8,%s} for more details.

23 83224297495 ERROR(3) nas_checkup has discovered an error. See ${logfile,8,%s} for more details.

29 87519264797 WARNING(4) nas_checkup exited before checking system health.

110 96109199470 INFO(6) Scheduled nas_checkup has found no problems.

111 96109199471 INFO(6) Scheduled nas_checkup has posted information. See ${logfile,8,%s} for more details.

112 87519264880 WARNING(4) Scheduled nas_checkup has posted a warning. See ${logfile,8,%s} for more details.

113 83224297585 ERROR(3) Scheduled nas_checkup has discovered an error. See ${logfile,8,%s} for more details.

119 96109199479 INFO(6) nas_checkup exited before checking system health.

121 96109199481 INFO(6) Scheduled nas_checkup has posted the information. EMC Customer Service will contact you. See ${logfile,8,%s} for more details.

122 87519264890 WARNING(4) Scheduled nas_checkup has posted a warning. EMC Customer Service will contact you. See ${logfile,8,%s} for more details.

123 83224297595 ERROR(3) Scheduled nas_checkup has discovered an error. EMC Customer Service will contact you. See ${logfile,8,%s} for more details.

129 87519264897 WARNING(4) nas_checkup exited before checking system health.

221 96109199581 INFO(6) Scheduled nas_checkup has posted information. The file ${src_file_path,8,%s} with the extension ${dest_extension,8,%s} is attached.

222 87519264990 WARNING(4) Scheduled nas_checkup has posted a warning. The file ${src_file_path,8,%s} with the extension ${dest_extension,8,%s} is attached.

223 83224297695 ERROR(3) Scheduled nas_checkup has discovered an error. The file ${src_file_path,8,%s} with the extension ${dest_extension,8,%s} is attached.

Table 19 Checkup (142) event facility (CS_PLATFORM) (page 2 of 2)



Table 20 CIC (109) event facility (CS_CORE)


1 82148392961 ERROR(3) IPC failure detected. ${value1,8,%s}.

Table 21 CommandService (9) event facility (CS_CORE)


1 86436806657 WARNING(4) Watchdog detected a check failure. Component=${value1,8,%s}

2 86436806658 WARNING(4) Watchdog error handling callback failed. Component=${value1,8,%s}

3 82141839363 ERROR(3) The Command Service is shutting down.

4 95026741252 INFO(6) The Command Service initialization is complete.

5 95026741253 INFO(6) The Command Service shutdown is complete.

6 82141839366 ERROR(3) The Command Service was forced to shutdown.

7 82141839367 ERROR(3) Failed to open dynamic library ${lib_name,8,%s}: ${dlerror,8,%s}.

8 82141839368 ERROR(3) Failed to unload dynamic library ${lib_name,8,%s}.

9 82141839369 ERROR(3) Failed to read dynamic library ${lib_name,8,%s}.

10 86436806666 WARNING(4) There is a problem accessing the cshosts file.

11 86436806667 WARNING(4) Attempt to recover command failed: ${object,8,%s}/${action,8,%s} factory not found.

12 86436806668 WARNING(4) Attempt to recover command failed: ${object,8,%s}/${action,8,%s}; failure ${factory,8,%s}.

13 82141839373 ERROR(3) Cannot run system management recovery, failed in task database lookup.

14 82141839374 ERROR(3) The Command Service could not service the request. A task ID cannot be generated.

15 82141839375 ERROR(3) The Command Service could not service the request: ${object,8,%s}/${action,8,%s}.

16 82141839376 ERROR(3) The Command Service could not service the request: ${object,8,%s}/${action,8,%s}.

17 82141839377 ERROR(3) Attempt to writeTaskInfo failed for ${task_id,30,%d} with ${db_status,8,%s}.

18 86436806674 WARNING(4) The number of active tasks (${active_tasks,2,%d}) exceeded the limit (${max_tasks,2,%d}).


Table 22 ConnectHome (133) event facility (CS_PLATFORM)


1 91813642241 NOTICE(5) ${num_files,1,%hd} old ConnectHome files deleted

2 83223707650 ERROR(3) Primary Email failed to transfer ConnectHome event file: ${msg,8,%s}

3 83223707651 ERROR(3) Primary FTP failed to transfer ConnectHome event file: ${msg,8,%s}

4 83223707652 ERROR(3) Primary Modem failed to transfer ConnectHome event file: ${msg,8,%s}

25 96108609561 INFO(6) ConnectHome event file(s) successfully transferred

50 96108609586 INFO(6) Connecthome Test of the ${type,8,%s} initiated

51 91813642291 NOTICE(5) Connecthome Test of the ${type,8,%s} succeeded

52 83223707700 ERROR(3) Connecthome Test of the ${type,8,%s} Email failed

53 83223707701 ERROR(3) Connecthome Test of the ${type,8,%s} FTP failed

54 83223707702 ERROR(3) Connecthome Test of the ${type,8,%s} Modem failed

100 96108609636 INFO(6) Test event from /nas/sbin/nas_connecthome -test.

Table 23 DBMS (122) event facility (DART)


1 73290874881 ALERT(1) The environment database of the VDM might be corrupted and a recovery procedure must take place

2 77585842178 CRITICAL(2) Only ${freeblocks,3,%llu} free blocks in the root file system (fsid ${fsid,2,%u}) of the VDM ${vdm,8,%s}.

3 73290874883 ALERT(1) The root file system (fsid ${fsid,2,%u}) of the VDM ${vdm,8,%s} is full. There are only ${freeblocks,3,%llu} free blocks.

Table 24 DBMS (122) event facility (CS_CORE) (page 1 of 2)


1 82149244929 ERROR(3) Db Env: ${db_env,8,%s}: Checkpoint: Failed: ${db_status,8,%s}.

2 86444212226 WARNING(4) Db: Compact${compact_option,8,%s}: ${db_name,8,%s}: Failed: ${db_status,8,%s}.


3 86444212227 WARNING(4) Db Env: ${db_env,8,%s}: Log Remove: Failed: ${db_status,8,%s}.

4 82149244932 ERROR(3) Db Env: ${errpfx,8,%s}: PANIC: Terminating...

5 82149244933 ERROR(3) Db Env: ${errpfx,8,%s}: Write Failed: Terminating...

Table 24 DBMS (122) event facility (CS_CORE) (page 2 of 2)


Table 25 DNS (118) event facility (DART)


1 81880547329 ERROR(3) Unable to connect to name server ${serverAddr,8,%s} : ${reason,8,%s}

Table 26 DPSVC (111) event facility (DART) (page 1 of 2)


1 86175055873 WARNING(4) Secondary=${sessionName,8,%s}(alias=${alias,8,%s}), send ack failed:${status,8,%s}, Primary Retry.

2 94764990466 INFO(6) Secondary=${secondary,8,%s}(alias=${alias,8,%s}), send ack ok. Connection up.

3 81880088579 ERROR(3) RepSessionName=${sessionName,8,%s}(alias=${alias,8,%s}), ${reqType,8,%s} failed, status:${status,8,%s}

4 94764990468 INFO(6) RepSessionName=${sessionName,8,%s}(alias=${alias,8,%s}), ${reqType,8,%s} ok.

5 94764990469 INFO(6) Initial Copy completed for verName:${versionName,8,%s} repName:${policyName,8,%s}

6 94764990470 INFO(6) Group:${rcpGpeName,8,%s} FSID:${fsID,8,%s} Resync Copy failed. Full Copy has to be started. (t:${ticks})

7 81880088583 ERROR(3) RepSessionName=${primaryName,8,%s}(alias=${alias,8,%s}), ${operation,8,%s} failed, status:${status,8,%s}

8 81880088584 ERROR(3) DpTaskManagerCopyReverseInitiator::session:${session,8,%s} failed OutOfSpace

9 81880088585 ERROR(3) DpInit::replicaInit() failed to recover replication session - repName:${repName,8,%s} alias:${alias,8,%s} status:${status,8,%s}

10 86175055882 WARNING(4) checkNameDB_StaleMode: INCONSISTENCY detected, repName:${repName,8,%s}, alias:${alias,8,%s}, vsid:${vsid,8,%s}. Reason: ${reason,8,%s}


11 86175055883 WARNING(4) checkNameDB_CriticalMode: INCONSISTENCY detected, repName:${repName,8,%s}, taskId:${taskId,8,%s}. Reason: ${reason,8,%s}

12 94764990476 INFO(6) Skip Replication Session Recovery:${cookieType,8,%s} recovery skipped for session:${repSessionName,8,%s}.

Table 26 DPSVC (111) event facility (DART) (page 2 of 2)


Table 27 DRIVERS (36) event facility (DART)


2 86170140674 WARNING(4) ${deviceName,45,%s}: link down${additionalInfo,8,%s}

3 86170140675 WARNING(4) ${deviceName,45,%s}: link up${additionalInfo,8,%s}

4 86170140676 WARNING(4) ${deviceName,45,%s}: link down${additionalInfo,8,%s}

5 86170140677 WARNING(4) ${deviceName,45,%s}: link up${additionalInfo,8,%s}

6 81875173382 ERROR(3) SlicNicDevice: TOE ${deviceName,45,%s} panic detected. The TOE core image is being saved to '${filename,8,%s}'.

7 86170140679 WARNING(4) Fiber Port ${port,2,%x} SFP inserted: connector type ${type,8,%s}

8 77580206088 CRITICAL(2) Fibre Port ${port,2,%x} SFP removed: status 0x${status,2,%x} state 0x${state,2,%x} type 0x${type,2,%x}

9 77580206089 CRITICAL(2) Fibre Port ${port,2,%x} SFP type changed from ${changes,8,%s}

10 77580206090 CRITICAL(2) Fiber Port ${port,2,%x} SFP invalid attachment: link speeds 1, 2, and 4 Gbps are not supported by this SFP

11 86170140683 WARNING(4) Fibre Port ${port,2,%x} SFP removed: status 0x${status,2,%x} state 0x${state,2,%x} type 0x${type,2,%x}

12 81875173388 ERROR(3) Fibre Port ${port,2,%x} SFP type changed from ${changes,8,%s}

13 81875173389 ERROR(3) Fiber Port ${port,2,%x} SFP invalid attachment: link speeds 1, 2, and 4 Gbps are not supported by this SFP

14 77580206094 CRITICAL(2) Fiber Port ${port,2,%x} SFP invalid attachment : copper cable of length ${length,2,%d} meters is not supported

15 81875173391 ERROR(3) Fiber Port ${port,2,%x} SFP invalid attachment : copper cable of length ${length,2,%d} meters is not supported

21 81875173397 ERROR(3) PCI-E Device (${busnum,5,%d},${devnum,5,%d},${funnum,5,%d}): ${errdesc,8,%s} over threshold (${trigger,2,%d})


Table 28 EmailUser (144) event facility (CS_PLATFORM)


1 83224428545 ERROR(3) Failed to open the email user configuration file.

2 83224428546 ERROR(3) ${cmd_path,8,%s} returned an error.

3 83224428547 ERROR(3) ${cmd_path,8,%s} does not exist or is not executable.

4 83224428548 ERROR(3) Unable to update email server in the ${file_path,8,%s} configuration file.

5 83224428549 ERROR(3) The file ${file_path,8,%s} is not writable or does not exist.

6 87519395846 WARNING(4) The Email User configuration file might be corrupted because of ${reason,8,%s}.

7 83224428551 ERROR(3) Failed to deliver the email with return code ${ret_value,1,%hd}.

8 83224428552 ERROR(3) Failed to restart the sendmail daemon.

9 87519395849 WARNING(4) Failed to access the ConnectHome configuration file ${file_path,8,%s}.

100 96109330532 INFO(6) Test event for Email User.

Table 29 EventLog (130) event facility (CS_PLATFORM) (page 1 of 3)


1 91813445633 NOTICE(5) Old ReportEvent interface used. Facility =${old_fac,2,%d} , Severity = ${old_sev,2,%d} , Event = ${old_id,2,%d}, Text = '${event_string,8,%s}'.

2 91813445634 NOTICE(5) Old Postevent interface used. Facility = ${old_fac,5,%u} , Severity = ${old_sev,5,%u} , Event = ${old_id,5,%u}, Text = '${event_string,8,%s}'.

3 96108412931 INFO(6) Event from DART. Facility = ${old_fac,2,%d} , Severity = ${old_sev,2,%d} , Event Id = ${old_id,2,%d}, String = '${event_string,8,%s}'.

4 83223511044 ERROR(3) Failed to translate ${ccmd_id,6,%llu} from the ${cat_lvl,8,%s} catalog : Bad Format Pattern.

5 83223511045 ERROR(3) Failed to translate ${ccmd_id,6,%llu} from the ${cat_lvl,8,%s} catalog : Add argument failed.

6 83223511046 ERROR(3) Failed to translate ${ccmd_id,6,%llu} from the ${cat_lvl,8,%s} catalog : Cannot add argument to NULL message.


7 83223511047 ERROR(3) Failed to translate ${ccmd_id,6,%llu} from the ${cat_lvl,8,%s} catalog : Failed to open catalog.

8 83223511048 ERROR(3) Failed to translate ${ccmd_id,6,%llu} from the ${cat_lvl,8,%s} catalog : Invalid catalog component.

9 83223511049 ERROR(3) Failed to translate ${ccmd_id,6,%llu} from the ${cat_lvl,8,%s} catalog : Incorrect catalog level.

10 83223511050 ERROR(3) Failed to translate ${ccmd_id,6,%llu} from the ${cat_lvl,8,%s} catalog : Catalog component mismatch.

11 83223511051 ERROR(3) Failed to translate ${ccmd_id,6,%llu} from the ${cat_lvl,8,%s} catalog : Catalog level mismatch.

12 83223511052 ERROR(3) Failed to translate ${ccmd_id,6,%llu} from the ${cat_lvl,8,%s} catalog : Message not found in catalog.

13 83223511053 ERROR(3) Failed to translate ${ccmd_id,6,%llu} from the ${cat_lvl,8,%s} catalog : Catalog type mismatch.

14 83223511054 ERROR(3) Failed to translate ${ccmd_id,6,%llu} from the ${cat_lvl,8,%s} catalog : Invalid argument name.

15 83223511055 ERROR(3) Failed to translate ${ccmd_id,6,%llu} from the ${cat_lvl,8,%s} catalog : Invalid argument type.

16 83223511056 ERROR(3) Failed to translate ${ccmd_id,6,%llu} from the ${cat_lvl,8,%s} catalog : High.

17 83223511057 ERROR(3) Failed to extract modem phone number : ${str,8,%s}

18 83223511058 ERROR(3) Failed to extract site name : ${str,8,%s}

19 83223511059 ERROR(3) Failed to extract serial number : ${str,8,%s}

20 83223511060 ERROR(3) Binary filename is NULL.

21 83223511061 ERROR(3) Stat failed for binary file '${filename,8,%s}' : ${err_str,8,%s}

22 83223511062 ERROR(3) RSCGenerateFilename() returned error: ${ret_val,2,%d}

23 83223511063 ERROR(3) RSCEventAdd() returned error: ${ret_val,2,%d}

24 83223511064 ERROR(3) RSCTransEventAndRawData() returned error: ${ret_val,2,%d}

25 83223511065 ERROR(3) RSCTransXMLEvent() returned error: ${ret_val,2,%d}

26 83223511066 ERROR(3) RSCEventCleanup() returned error: ${ret_val,2,%d}

27 83223511067 ERROR(3) Error Processing CallHome Event

28 91813445660 NOTICE(5) Event ${ccmd_id,6,%llu} : '${brief_desc,8,%s}' is not valid for callhome binary.

29 87518478365 WARNING(4) Failed to send message to IPC. Error code ${error_code,1,%hd}

30 83223511070 ERROR(3) EventCollector(pid = ${pid,5,%u}) received a corrupt event from slot ${slot_id,17,%d}.




31 83223511071 ERROR(3) EventLogger(pid = ${pid,5,%u}) processed a corrupt pending event.

32 87518478368 WARNING(4) Event indications are blocked until EventLogger is restarted.

50 70338609202 EMERGENCY(0) ${text,8,%s}

51 74633576499 ALERT(1) ${text,8,%s}

52 78928543796 CRITICAL(2) ${text,8,%s}

53 83223511093 ERROR(3) ${text,8,%s}

54 87518478390 WARNING(4) ${text,8,%s}



Table 30 FCP (102) event facility (DART) (page 1 of 3)


1 86174466049 WARNING(4) HBA ${adapter_id,5,%u} Now online.

2 81879498754 ERROR(3) HBA ${adapter_id,2,%01x}: Waiting for FLOGI.

3 81879498755 ERROR(3) HBA ${adapter_id,5,%u} OFFLINE: Link Reset.

4 81879498756 ERROR(3) HBA ${adapter_id,2,%x}: Link Down.

5 81879498757 ERROR(3) HBA ${badHBA,5,%u}: HBA does not exist on chain ${chain,2,%d}

6 81879498758 ERROR(3) WARNING: User has issued a "fcp bind clear" command to Slot ${slot_id,2,%d}

7 81879498759 ERROR(3) Chains ${chain1,2,%d}-${chain2,2,%d} are Stale: Chains rendered unusable

8 81879498760 ERROR(3) Invalid Config: Multiple sys chains (LUN 0) configured: D_ID ${fcDid,2,%06x} WWN ${temp0,2,%08x}${temp1,2,%08x}

9 86174466057 WARNING(4) HBA ${adapter_id,2,%01x}: sys chain ${fcDid,2,%d} N_PORT D_ID ${value1,2,%06x} FA-${value2,5,%02u}${char1,1,%c}${char2,1,%c}: ${temp0,2,%08x}${temp1,2,%08x}

10 86174466058 WARNING(4) HBA ${adapter_id,2,%01x}: sys chain ${path,2,%d} N_PORT D_ID ${fcDid,2,%06x} SP-${char1,1,%c}${value1,5,%01u}: ${temp0,2,%08x}${temp1,2,%08x}

11 86174466059 WARNING(4) HBA ${adapter_id,2,%01x}: sys chain ${path,2,%d} N_PORT D_ID ${fcDid,2,%06x} WWN: ${temp0,2,%08x}${temp1,2,%08x}

12 86174466060 WARNING(4) HBA ${adapter_id,2,%01x}: No sys drive: Binding will not occur.

13 81879498765 ERROR(3) HBA ${adapter_id,2,%01x}: binding table read fail.

14 81879498766 ERROR(3) HBA ${adapter_id,2,%01x}: binding table refresh fail.


15 86174466063 WARNING(4) HBA ${adapter_id,2,%01x}: binding table refresh retry succeeded.

16 86174466064 WARNING(4) HBA ${adapter_id,2,%01x}: binding table cleared.

17 81879498769 ERROR(3) HBA ${adapter_id,2,%01x}: binding table write fail.

18 86174466066 WARNING(4) HBA ${adapter_id,2,%01x}: binding table write retry succeeded.

19 81879498771 ERROR(3) HBA ${adapter_id,2,%u} will bind with Chain ${chain,2,%04d}

20 86174466068 WARNING(4) HBA ${adapter_id,2,%01x}: new N_PORT D_ID ${value1,2,%06x} FA-${value2,5,%02u}${char1,1,%c}${char2,1,%c}: ${temp0,2,%08x}${temp1,2,%08x}

21 86174466069 WARNING(4) HBA {adatper_id}: new N_PORT D_ID ${fcDid,2,%06x} SP-${char1,1,%c}${value1,5,%01u}: ${temp0,2,%08x}${temp1,2,%08x}

22 86174466070 WARNING(4) HBA ${adapter_id,2,%01x}: new N_PORT D_ID ${fcDid,2,%06x} WWN: ${temp0,2,%08x}${temp1,2,%08x}

23 86174466071 WARNING(4) HBA ${adapter_id,1,%01x}: duplicate N_PORT D_ID ${fcDid,2,%06x} WWN: ${temp0,2,%08x}${temp1,2,%08x} duplicate ${dup_wwn,2,%x} total ${tot_wwn

24 81879498776 ERROR(3) Binding online chains ${value1,2,%d}-${value2,2,%d} to HBA ${adapter_id,5,%u}

25 81879498777 ERROR(3) Binding offline chains ${value1,2,%d}-${value2,2,%d} to HBA ${adapter_id,5,%u}

26 86174466074 WARNING(4) HBA ${adapter_id,5,%u}: state change notification

27 81879498779 ERROR(3) HBA ${adapter_id,5,%u}: asynchronous state change

28 86174466076 WARNING(4) State change notification: FA-${value1,5,%02u}${char1,1,%c}${char2,1,%c}: ${temp0,2,%08x}${temp1,2,%08x}

29 86174466077 WARNING(4) State change notification: SP-${char1,1,%c}${value1,5,%01u}: ${temp0,2,%08x}${temp1,2,%08x}

30 86174466078 WARNING(4) State Change Notification: N_PORT: ${temp0,2,%08x}${temp1,2,%08x}

31 86174466079 WARNING(4) SCSI-${chain,5,%4u}: HBA ${adapter_id,2,%01x}: CHAINS ${chain1,5,%4u} - ${chain2,5,%4u} OFFLINE

32 86174466080 WARNING(4) SCSI-${chain,5,%4u}: HBA ${adapter_id,2,%01x}: CHAINS ${chain1,5,%4u} - ${chain2,5,%4u} ONLINE

33 81879498785 ERROR(3) sim_startIO Err: Tid {Tid} Lun ${lun_id,5,%u} max_tid ${max_tid,5,%u}max_lun ${max_lun,5,%u}

34 81879498786 ERROR(3) IORequest bad state 0x${state,2,%02x} in sim_initiateIO()

38 81879498790 ERROR(3) Error: ID ${errid,5,%03x} Error ${err,2,%08x} SUB ${subcode1,2,%08x}, IOSTAT ${subcode2,2,%02x} IOERR ${subcode3,2,%02x}




39 81879498791 ERROR(3) ${deviceName,8,%s} not created - parent device invalid

40 81879498792 ERROR(3) Too many FCP host bus adapters.

41 81879498793 ERROR(3) Cannot allocate HBA memory.

42 81879498794 ERROR(3) Cannot allocate HBA memory for Tachyon.

43 81879498795 ERROR(3) sim_busRESET called

44 86174466092 WARNING(4) HBA ${adapter_id,2,%d}: binding table refresh succeeded



Table 31 FSTOOLS (40) event facility (DART)


1 77580468225 CRITICAL(2) The file system utility, fsck, started on file system id: ${id,22,%u} for type: (${type,8,%s}).

2 94760337410 INFO(6) FsId: ${id,5,%u} Fsck Started (${type,8,%s}).

3 77580468227 CRITICAL(2) FsId: ${id,5,%u} Fsck Succeeded

4 94760337412 INFO(6) FsId: ${id,5,%u} Fsck Succeeded

5 77580468229 CRITICAL(2) FsId: ${fsid,5,%u} Fsck Failed

6 94760337414 INFO(6) FsId: ${fsid,5,%u} Fsck Failed

7 94760337415 INFO(6) FsId: ${fsid,5,%u} Aclchk Started (${type,8,%s}).

8 94760337416 INFO(6) FsId: ${fsid,5,%u} Aclchk Succeeded

9 73285500937 ALERT(1) FsId: ${fsid,5,%u} Aclchk Failed

10 94760337418 INFO(6) MAPBLOCK:: MapBlock Started.

11 94760337419 INFO(6) MAPBLOCK:: MapBlock Succeeded.

12 77580468236 CRITICAL(2) MAPBLOCK:: MapBlock Failed. Reason: ${reason,8,%s}.

13 86170402829 WARNING(4) Fsck Couldn't allocate a block from file system. Release some unused space and run fsck Again

Table 32 FSTOOLS (40) event facility (CS_PLATFORM)


10 78922645514 CRITICAL(2) FsId: ${FS_ID,22,%u} Fsck Started (Auto - Corruption (${FSCK_REASON,8,%s}))


Table 33 IP (43) event facility (DART)


1 81875632129 ERROR(3) Duplicate address: ${ipaddress,52,%s} / ${macaddress,8,%s} detected on IP interface ${ifname,50,%s}.

2 81875632130 ERROR(3) Duplicate address: ${ipaddress,51,%s} / ${macaddress,8,%s} detected on IP interface ${ifname,50,%s}.

Table 34 JServer (135) event facility (CS_PLATFORM) (page 1 of 4)


101 87518806117 WARNING(4) The Jserver failed to start after three tries.

102 87518806118 WARNING(4) ${msg,8,%s}.

103 87518806119 WARNING(4) The Jserver reported nas_cmd errors.

104 87518806120 WARNING(4) ${msg,8,%s}.

201 87518806217 WARNING(4) Alert ${alert_id,40,%s} ${prop_name,8,%s}; File System '${fs_name,68,%s}'; value=${condition,8,%s}; ${notified_on,8,%s}

202 87518806218 WARNING(4) Alert ${alert_id,40,%s}; File System '${fs_name,68,%s}'; ${prop_name,8,%s} limit on ${sdate,8,%s}; ${notified_on,8,%s}

203 87518806219 WARNING(4) Alert ${alert_id,40,%s} (${method_name,8,%s}); Mover '${server_description,8,%s}' ($server_name); value=${mem_value,8,%s}

204 87518806220 WARNING(4) Alert ${alert_id,40,%s}; Storage Pool '${pool_name,75,%s}'; value=${condition,8,%s}; ${notified_on,8,%s}

205 87518806221 WARNING(4) Alert ${alert_id,40,%s}; Storage Pool '${pool_name,75,%s}'; space limit on ${sdate,8,%s}; ${notified_on,8,%s}

210 87518806226 WARNING(4) Alert ${alert_id,40,%s}: File system ${fs_name,68,%s} is using ${condition,8,%s} of its ${cap_setting,8,%s} ${prop_name,8,%s} capacity.

211 87518806227 WARNING(4) Alert ${alert_id,40,%s}: File system ${fs_name,68,%s} has ${condition,8,%s} of its ${cap_setting,8,%s} ${prop_name,8,%s} capacity available.

212 87518806228 WARNING(4) Alert ${alert_id,40,%s}: Storage pool ${pool_name,75,%s} is using ${condition,8,%s} of its ${cap_setting,8,%s} capacity.

213 87518806229 WARNING(4) Alert ${alert_id,40,%s}: Storage pool ${pool_name,75,%s} has ${condition,8,%s} of its ${cap_setting,8,%s} capacity available.

214 87518806230 WARNING(4) Alert ${alert_id,40,%s}: File system ${fs_name,68,%s} is using ${condition,8,%s} of the maximum allowable file system size (16 TB).


215 87518806231 WARNING(4) Alert ${alert_id,40,%s}: File system ${fs_name,68,%s} has ${condition,8,%s} of the maximum allowable file system size (16 TB).

216 87518806232 WARNING(4) Alert ${alert_id,40,%s}: File system ${fs_name,68,%s} is using ${condition,8,%s} of the maximum storage pool capacity available.

217 87518806233 WARNING(4) Alert ${alert_id,40,%s}: File system ${fs_name,68,%s} has ${condition,8,%s} of the maximum storage pool capacity available.

218 87518806234 WARNING(4) Alert ${alert_id,40,%s}: File system ${fs_name,68,%s} will fill its ${cap_setting,8,%s} ${prop_name,8,%s} capacity on ${sdate,8,%s}.

219 87518806235 WARNING(4) Alert ${alert_id,40,%s}: Storage pool ${pool_name,75,%s} will fill its ${cap_setting,8,%s} capacity on ${sdate,8,%s}.

220 87518806236 WARNING(4) Alert ${alert_id,40,%s}: File system ${fs_name,68,%s} will reach the 16 TB file system size limit on ${sdate,8,%s}.

221 87518806237 WARNING(4) Alert ${alert_id,40,%s}: File system ${fs_name,68,%s} will fill its storage pool's maximum capacity on ${sdate,8,%s}.

222 87518806238 WARNING(4) Alert ${alert_id,40,%s}: Data Mover ${server_name,56,%s} (ID ${server_id,17,%d}) is using ${stat_value,8,%s} of its ${stat_name,8,%s} capacity, calculated with the ${method_name,8,%s} method.

801 87518806817 WARNING(4) Unable to read CLARiiON device cache: ${strace,8,%s}

802 8751880681 WARNING(4) Unable to write CLARiiON config cache: ${strace,8,%s}

803 87518806819 WARNING(4) Unable to read CLARiiON disk cache: ${strace,8,%s}

804 87518806820 WARNING(4) Unable to write CLARiiON disk cache: ${strace,8,%s}

805 87518806821 WARNING(4) Unable to read CLARiiON raid group cache: ${strace,8,%s}

806 87518806822 WARNING(4) Unable to read CLARiiON SP cache: ${strace,8,%s}

807 87518806823 WARNING(4) Unable to write CLARiiON SP cache: ${strace,8,%s}

808 87518806824 WARNING(4) CLARiiON ${clar_name,8,%s} polling interval is too short, skipping polls

809 87518806825 WARNING(4) CLARiiON ${sn,65,%s} poller has been shut down.

810 87518806826 WARNING(4) Navicli stats gathering is disabled for CLARiiON ${clar_name,65,%s}

811 87518806827 WARNING(4) The Symm poller is not responding.

812 87518806828 WARNING(4) Could not connect to SymmPoller 5 times. Exiting for process cleanup.

813 87518806829 WARNING(4) CLARiiON poller is not responding. There might be problems with Navisphere®.




814 87518806830 WARNING(4) Could not connect to ClariPoller 5 times. Exiting for process cleanup.

815 87518806831 WARNING(4) The /nas(or /nbsnas) filesystem capacity has dropped below ${space_limit,8,%s}%. Historical data gathered about the Control Station's configuration has been resumed

816 87518806832 WARNING(4) Network addresses ${a_addr,8,%s} and ${b_addr,8,%s} resolved to the same IP address.

817 87518806833 WARNING(4) Attempting to shut down symm agent

818 87518806834 WARNING(4) Attempting to restart symm agent

819 87518806835 WARNING(4) Attempting to shut down Clari agent

820 87518806836 WARNING(4) Attempting to restart Clari agent

821 87518806837 WARNING(4) Polling of the Data Mover in slot ${serverSlot,24,%s} has been shut down.

822 87518806838 WARNING(4) Symmetrix ${sn,8,%s} poller has been shut down.

823 87518806839 WARNING(4) Unable to start up SYMAPI subsystem. Exiting...

824 87518806840 WARNING(4) The fetcher thread failed to start after three tries. Stopping Jserver.

825 87518806841 WARNING(4) Unable to write CLARiiON device cache: ${strace,8,%s}

826 87518806842 WARNING(4) New problem report is in /nas/jserver/${file_name,8,%s}

827 87518806843 WARNING(4) Unable to generate problem report

828 87518806844 WARNING(4) Unable to read Symmetrix device cache: ${strace,8,%s}

829 87518806845 WARNING(4) Unable to write Symmetrix device cache: ${strace,8,%s}

830 87518806846 WARNING(4) Unable to read Symmetrix disk cache: ${strace,8,%s}

831 87518806847 WARNING(4) Unable to write Symmetrix disk cache: ${strace,8,%s}

832 87518806848 WARNING(4) Unable to read Symmetrix config cache: ${strace,8,%s}

833 87518806849 WARNING(4) The command ${command_str,8,%s} timed out.

850 96108741458 INFO(6) CLARiiON ${clar_name,8,%s} - new configuration received

851 96108741459 INFO(6) CLARiiON ${clar_name,8,%s} polling interval has been changed to ${rem,8,%s}

852 96108741460 INFO(6) CLARiiON ${clar_name,8,%s} poller has been restarted.

853 96108741461 INFO(6) Control Station - Server Poller error count is too high (${count,8,%s})

854 96108741462 INFO(6) Control Station - restarting fs capacity fetcher

855 96108741463 INFO(6) Generated debug file ${path,8,%s} from the core dump.${line_two,8,%s}

856 96108741464 INFO(6) Jserver stopped




857 96108741465 INFO(6) Fetcher pipe write timeout for server slot ${slot,8,%s}.

858 96108741466 INFO(6) Polling of data mover in slot ${serverSlot,8,%s} has been restarted.

859 96108741467 INFO(6) Data Mover in slot ${serverSlot,8,%s} polling interval has been changed to ${rem,8,%s}

860 96108741468 INFO(6) Symmetrix ${sym_name,8,%s} poller is on line.

861 96108741469 INFO(6) Symmetrix ${sname,8,%s} polling interval has been changed to ${rem,8,%s}

862 96108741470 INFO(6) Symmetrix ${sname,8,%s} poller has been restarted.

1001 87518807017 WARNING(4) The /nas/jserver(or /nbsnas/jserver) filesystem capacity exceeds ${space_limit,8,%s}%. The system is no longer gathering historical data about the Control Station's configuration.



Table 35 KERNEL (45) event facility (DART)


1 81875763201 ERROR(3) ${featurename,8,%s}: Service:${servicename,8,%s} Pool:${poolname,8,%s} BLOCKED for ${blockedtime,5,%u} seconds.

2 81875763202 ERROR(3) ${featurename,8,%s}: Service:${servicename,8,%s} Pool:${poolname,8,%s} PENDING for ${blockedtime,5,%u} seconds (potential panic in ${panictime,2,%d} seconds).

3 81875763203 ERROR(3) ${featurename,8,%s}: Service:${servicename,8,%s} Pool:${poolname,8,%s} BLOCKED for ${blockedtime,5,%u} seconds: Server operations may be impacted ${criticalstr,8,%s}.

4 81875763204 ERROR(3) ${featurename,8,%s}: Service:${servicename,8,%s} Pool:${poolname,8,%s} PENDING for ${blockedtime,5,%u} seconds.

Table 36 LocalHardwareMonitor (139) event facility (CS_PLATFORM) (page 1 of 3)


1 78929133569 CRITICAL(2) 1.5V too high.

2 83224100866 ERROR(3) 1.5V too low.

3 83224100867 ERROR(3) VCCP1 too high.


4 83224100868 ERROR(3) VCCP1 too low.

5 83224100869 ERROR(3) 3.3V too high.

6 83224100870 ERROR(3) 3.3V too low.

7 83224100871 ERROR(3) 5V too high.

8 83224100872 ERROR(3) 5V too low.

9 83224100873 ERROR(3) 12V too high.

10 83224100874 ERROR(3) 12V too low.

11 83224100875 ERROR(3) VCCP2 too high.

12 83224100876 ERROR(3) VCCP2 too low.

13 83224100877 ERROR(3) Fan1 low.

14 83224100878 ERROR(3) Fan2 low.

15 83224100879 ERROR(3) Temperature too high.

17 83224100881 ERROR(3) VID too high.

18 83224100882 ERROR(3) Chassis Intrusion.

100 83224100964 ERROR(3) VCCP Voltage Alarm.

101 83224100965 ERROR(3) FSB Voltage Alarm.

102 83224100966 ERROR(3) MCH CORE 1.5V Alarm.

103 83224100967 ERROR(3) MEM VTT 0.98V Alarm.

104 83224100968 ERROR(3) MEM CORE 1.8V Alarm.

105 83224100969 ERROR(3) NIC CORE 1.5V Alarm.

106 83224100970 ERROR(3) BB 3.3VSB Alarm.

107 83224100971 ERROR(3) BB 5VSB Alarm.

108 83224100972 ERROR(3) BB 3.3V Alarm.

109 83224100973 ERROR(3) BB 5V Alarm

110 83224100974 ERROR(3) BB 12V Alarm.

111 83224100975 ERROR(3) BB -12V Alarm.

112 83224100976 ERROR(3) Fan 1H Alarm.

113 83224100977 ERROR(3) Fan 2H Alarm.

114 83224100978 ERROR(3) Fan 3H Alarm.

115 83224100979 ERROR(3) Fan 4H Alarm.

116 83224100980 ERROR(3) Fan 5H Alarm.

117 83224100981 ERROR(3) Fan 1L Alarm.




118 83224100982 ERROR(3) Fan 2L Alarm.

119 83224100983 ERROR(3) Fan 3L Alarm.

120 83224100984 ERROR(3) Fan 4L Alarm.

121 83224100985 ERROR(3) Fan 5L Alarm.

122 83224100986 ERROR(3) BB Temp Alarm.

123 83224100987 ERROR(3) Amb Temp Alarm

124 83224100988 ERROR(3) CPU Temp Alarm



Table 37 LOCK (68) event facility (DART)


1 86172237825 WARNING(4) Client ${clientName,8,%s} has reached the max count of entries (${maxEntries,2,%u}) in statd registry

2 86172237826 WARNING(4) ${nodesCount,2,%u}% nodes are consumed by file locks

Table 38 LogCollect (141) event facility (CS_PLATFORM) (page 1 of 4)


1 96109133825 INFO(6) ${SCRIPTNAMEPID,8,%s}: The collection script revision ${SCRIPTVERSION,8,%s} has started.

2 96109133826 INFO(6) ${SCRIPTNAMEPID,8,%s}: The log collection script finished successfully. A support materials file has been created in ${TMPDIR,8,%s}.

3 87519199235 WARNING(4) ${SCRIPTNAMEPID,8,%s}: The log collection script finished with only partial collection. There is not enough disk space in the ${TMPDIR,8,%s} directory.

4 87519199236 WARNING(4) ${SCRIPTNAMEPID,8,%s}: The log collection script failed. It could not create a temporary directory in ${TMPDIR,8,%s} in which to place the file.

5 87519199237 WARNING(4) ${SCRIPTNAMEPID,8,%s}: The log collection script failed. It could not create a temporary directory in / in which to place the file.

7 96109133831 INFO(6) ${SCRIPTNAMEPID,8,%s}: The log collection script failed because only one session can be run at a time.


8 96109133832 INFO(6) ${SCRIPTNAMEPID,8,%s}: You do not have permission to run this feature. You must belong to the nasadmin or root primary group.

9 87519199241 WARNING(4) ${SCRIPTNAMEPID,8,%s}: The maximum file size of ${MAXSIZE,8,%s}MB is exceeded. The log collection file size is ${CURSIZE,8,%s}KB, and ${ESTIMATED_NEWSIZE,8,%s}${UNITFLAG,8,%s}B is needed.

10 87519199242 WARNING(4) ${SCRIPTNAMEPID,8,%s}: The log collection files exceeded the total size limit of ${TOTAL_COLLECT_SIZE,8,%s}KB. Estimated space required: ${ESTIMATED_NEWSIZE,8,%s}${UNITFLAG,8,%s}B.

11 96109133835 INFO(6) ${SCRIPTNAMEPID,8,%s}: Reached the maximum space limit for log collection files (${MAXTOTALSIZE,8,%s}MB). Deleting the oldest collect file (${COLLECTFILE,8,%s}) to free space.

100 96109133924 INFO(6) ${SCRIPTNAMEPID,8,%s}: The transfer script started.

101 87519199333 WARNING(4) ${SCRIPTNAMEPID,8,%s}: The remote FTP server/directory cannot be reached. Verify your configuration in ${CONFIG,8,%s}.

102 87519199334 WARNING(4) ${SCRIPTNAMEPID,8,%s}: The transfer script failed. Data cannot be transferred to ${SERVER,8,%s} or the remote directory. Contact your authorized service provider to verify the remote server has sufficient free disk space (${SPACENEEDED,8,%s}).

103 96109133927 INFO(6) ${SCRIPTNAMEPID,8,%s}: No support materials are available for transfer.

104 87519199336 WARNING(4) ${SCRIPTNAMEPID,8,%s}: The transfer script failed (log collection file). Unable to reach ${SERVER,8,%s} or the remote directory. Verify your configuration in ${CONFIG,8,%s}.

105 96109133929 INFO(6) ${SCRIPTNAMEPID,8,%s}: Instruct your authorized service provider to check ${SERVER,8,%s} for the log saved as ${NEWFILE,8,%s} at ${REMOTENAME,8,%s}.

106 96109133930 INFO(6) ${SCRIPTNAMEPID,8,%s}: Instruct your authorized service provider to check ${SERVER,8,%s} for a dump file saved as ${OUTPUTFILE,8,%s} in ${REMOTENAME,8,%s}.

107 87519199339 WARNING(4) ${SCRIPTNAMEPID,8,%s}: The transfer script failed (DUMP).

108 96109133932 INFO(6) ${SCRIPTNAMEPID,8,%s}: The transfer script finished successfully. The slot ${SLOTNUM,8,%s} Dump is saved to ${FIFOFILE,8,%s}.

109 87519199341 WARNING(4) ${SCRIPTNAMEPID,8,%s}: The transfer script failed (DUMP). Failed to create ${FILENAME,8,%s}.

200 96109134024 INFO(6) Slot 0 dump is ready.



















300 96109134124 INFO(6) ${SCRIPTNAMEPID,8,%s}: The automatic transfer feature is enabled.

301 96109134125 INFO(6) ${SCRIPTNAMEPID,8,%s}: The automatic collection and transfer feature is disabled.

302 96109134126 INFO(6) ${SCRIPTNAMEPID,8,%s}: The automatic collection and transfer feature is enabled.

303 96109134127 INFO(6) ${SCRIPTNAMEPID,8,%s}: The automatic transfer feature is disabled.

304 96109134128 INFO(6) ${SCRIPTNAMEPID,8,%s}: There are too many transfers (${NUMOFTRANSFER,8,%s}) in progress. Transfer will be attempted again in 1 minute.

305 96109134129 INFO(6) ${SCRIPTNAMEPID,8,%s}: The log collection script cannot run because 15 minutes must elapse between collection sessions.

306 87519199538 WARNING(4) ${SCRIPTNAMEPID,8,%s}: There are too many dumps (${TOTALCOPIES,8,%s}) in the dump directory ${DUMPDIR,8,%s}.

307 87519199539 WARNING(4) ${SCRIPTNAMEPID,8,%s}: The automaticcollection.cfg file cannot be created in /nas/site.

308 96109134132 INFO(6) ${SCRIPTNAMEPID,8,%s}: ${NEWFILE,8,%s} cannot be transferred to your authorized service provider because the automatic transfer feature is disabled.

309 96109134133 INFO(6) ${SCRIPTNAMEPID,8,%s}: The automatic log collection and transfer feature is disabled.

310 87519199542 WARNING(4) ${SCRIPTNAMEPID,8,%s}: The output directory ${DIR,8,%s} does not exist.




311 96109134135 INFO(6) ${SCRIPTNAMEPID,8,%s}: Slot ${SLOTNUM,8,%s} does not have a panic dump for retrieval.

312 87519199544 WARNING(4) ${SCRIPTNAMEPID,8,%s}: The configuration file /nas/site/automaticcollection.cfg cannot be upgraded to version ${CURRENTVERSION,8,%s}.



Table 39 MasterControl (129) event facility (CS_PLATFORM) (page 1 of 2)


1 87518412801 WARNING(4) Terminating the Master Control Application.

2 70338543618 EMERGENCY(0) Unable to set IO priority level.

3 70338543619 EMERGENCY(0) Unable to change directory to ${DIR_PATH,59,%s} for daemon ${DAEMON_NAME,8,%s}.

4 70338543620 EMERGENCY(0) Exec of daemon ${DAEMON_NAME,8,%s} failed: (file = ${FILE_NAME,8,%s}; error = ${ERROR_STRING,8,%s}).

5 70338543621 EMERGENCY(0) Fork failed for daemon ${DAEMON_NAME,8,%s}; (error = ${ERROR_STRING,8,%s}).

6 70338543622 EMERGENCY(0) Daemon ${DAEMON_NAME,8,%s} unexpectedly exited (status = ${STATUS,5,%u}); ifexit=${IF_EXIT,5,%u}, exitstatus=${EXIT_STATUS,5,%u}, ifsignal=${IF_SIGNAL,5,%u}, termsig=${TERM_SIG,5,%u}, ifstop=${IF_STOP,5,%u}, stopsig=${STOP_SIG,5,%u}, ifdump=${IF_DUMP,5,%u}.

7 83223445511 ERROR(3) Heartbeat is missing from other Control Station.

8 83223445512 ERROR(3) The "sibpost" command failed: ${slot_id_string,8,%s}.

9 83223445513 ERROR(3) Discovered unknown slot ID ${slot_num_string,8,%s}.

10 83223445514 ERROR(3) ${slot_id_string,8,%s} file system repair found errors.

11 87518412811 WARNING(4) ${ARG0,8,%s} ${ARG1,8,%s} ${ARGs,8,%s}.

12 70338543628 EMERGENCY(0) NBS device(s) are unavailable.

13 87518412813 WARNING(4) IPMI Connection Failure occurred.

14 87518412814 WARNING(4) IPMI Connection is Restored.

15 70338543631 EMERGENCY(0) ${DAEMON_NAME,8,%s} respawning too fast; disabled for ${DISABLED_MINUTES,1,%u} minutes.

16 83223445520 ERROR(3) Slot ${slot_num_string,8,%s} file system repair found errors.

17 83223445521 ERROR(3) Heartbeat is missing from the other Control Station (rebooting).

18 83223445522 ERROR(3) Heartbeat is missing from the other Control Station.


19 83223445523 ERROR(3) Slot ${slot_num_string,8,%s} becomes primary because of timeout.

20 83223445524 ERROR(3) Unable to recover the other Control Station.

Table 39 MasterControl (129) event facility (CS_PLATFORM) (page 2 of 2)


Table 40 MGFS (75) event facility (DART)


1 94762631169 INFO(6) Complete migration of CID: [${cid,2,%d}] on FSPATH: [${fspath,8,%s}] of FSID: [${fsid,5,%u}], state: [${state,8,%s}], recall: [${recall,8,%s}]

Table 41 MGFS (75) event facility (CS_PLATFORM)


10 70335004682 EMERGENCY(0) Recall Migration of FSID[${FS_ID,22,%u}] succeeded: Attempting verification.

11 70335004683 EMERGENCY(0) Recall Migration of FSID[${FS_ID,22,%u}] failed: ${STATE,8,%s}

12 70335004684 EMERGENCY(0) MGFS_hander Fault, Command: ${COMMAND,8,%s}, Error: ${ERROR,8,%s}

13 70335004685 EMERGENCY(0) Error: Void or Null argument

Table 42 NASDB (137) event facility (CS_PLATFORM) (page 1 of 2)


11 83223969803 ERROR(3) Command failed. Command: ${COMMAND,8,%s} Error: ${ERROR_STRING,8,%s}

20 83223969812 ERROR(3) Command failed after ${BIG_MAX_RETRY,1,%hd} lock was retried. Command: ${COMMAND,8,%s} Error: ${ERROR_STRING,8,%s}

202 83223969994 ERROR(3) A Celerra database error was detected.

211 83223970003 ERROR(3) Missed the schedule. ${scheduleName,62,%s}: ${taskDescription,8,%s}

212 83223970004 ERROR(3) Task (${taskId,30,%u}) ${taskDescription,8,%s} of schedule ${scheduleName,62,%s} has failed.


214 87518937302 WARNING(4) The schedule file for the schedule ${scheduleName,62,%s} is quarantined.

300 96108871980 INFO(6) nasdb_backup: NAS_DB checkpoint is in progress.

301 87518937389 WARNING(4) nasdb_backup: deleted nasdb_backup file ${NASDB_BACKUP_FILENAME,8,%s} to free disk space on ${DEST_DIRECTORY,59,%s}.

303 91813904687 NOTICE(5) nasdb_backup: rename ${NEWEST_COPY_FILENAME,8,%s} to ${SAVED_COPY_FILENAME,8,%s}.

304 87518937392 WARNING(4) nasdb_backup: cannot compute the size of ${NAS_DB_PATHNAME,59,%s}.

305 96108871985 INFO(6) nasdb_backup: NAS_DB checkpoint done.

306 96108871986 INFO(6) nasdb_backup: Celerra database backup done.

307 83223970099 ERROR(3) nasdb_backup: cannot find enough space. ${ESTIMATED_KB_NEEDED,2,%d} KB of space is required. Only ${AVAILABLE_KB_CURR,2,%d} KB space left on ${DEST_DIRECTORY,59,%s}.

308 83223970100 ERROR(3) Failed to update server ${SERVER,57,%s} with the Control Station's IP address. ${COMMAND,8,%s} failed.

309 91813904693 NOTICE(5) Control Station is configured with DHCP connection.

310 83223970102 ERROR(3) nasdb_backup: failed to backup BDB dbms files for Data Movers.

Table 42 NASDB (137) event facility (CS_PLATFORM) (page 2 of 2)


Table 43 NASDB (137) event facility (CS_CORE)


1 95035129857 INFO(6) Database file ${file_name,8,%s} has an invalid signature.

2 86445195266 WARNING(4) Restart checkpoint ${CKPT_NAME,69,%s} could not be created during replication failover due to Error ${ERRORCODE,6,%llu}:${ERROR_MESG,8,%s}.

3 95035129859 INFO(6) ${message,8,%s}

Table 44 NaviEventMonitor (138) event facility (CS_PLATFORM) (page 1 of 2)


1 96108937217 INFO(6) CLARiiON event number 0x${navi_event_str,8,%s} ${desc,8,%s}.

2 87519002626 WARNING(4) CLARiiON event number 0x${navi_event_str,8,%s} ${desc,8,%s}.


3 83224035331 ERROR(3) CLARiiON event number 0x${navi_event_str,8,%s} ${desc,8,%s}.

4 78929068036 CRITICAL(2) CLARiiON event number 0x${navi_event_str,8,%s} ${desc,8,%s}.

10 74634100746 ALERT(1) CLARiiON Event Monitor daemon terminated unexpectedly.

100 74634100836 ALERT(1) Disk ${dname,8,%s} has been cache-compromised.

101 78929068133 CRITICAL(2) Disk ${dname,8,%s} has been trespassed.

200 96108937416 INFO(6) Device group ${name,8,%s} on ${BACKEND_NAME,8,%s} is ${condition,8,%s}.

201 83224035529 ERROR(3) ${BACKEND_NAME,8,%s} ${name,8,%s} is ${condition,8,%s}.

202 83224035530 ERROR(3) Device group ${name,8,%s} on ${BACKEND_NAME,8,%s} is ${condition,8,%s}.

203 87519002827 WARNING(4) Device group ${name,8,%s} on ${BACKEND_NAME,8,%s} is ${condition,8,%s}.

Table 44 NaviEventMonitor (138) event facility (CS_PLATFORM) (page 2 of 2)


Table 45 NDMP (51) event facility (DART)


1 86171123713 WARNING(4) source_fsid:${source,2,%d} mount_point:${mount,8,%s}/${key,8,%s}

2 86171123714 WARNING(4) fsid:${fsid,2,%d} mount_point:${parentKey,8,%s}/${removeKey,8,%s}

Table 46 NDMP (51) event facility (CS_PLATFORM) (page 1 of 2)


10 83218333706 ERROR(3) command failed: ${COMMAND,8,%s}

11 83218333707 ERROR(3) illegal number of arguments ${ARGUMENT_COUNT,1,%d}

12 83218333708 ERROR(3) Illegal argument ${ARGUMENTS,8,%s}

13 83218333709 ERROR(3) badly formatted message

14 83218333710 ERROR(3) invalid source fsid specified: ${SOURCE_FS_ID,22,%u}

15 83218333711 ERROR(3) source_fsid not specified

16 83218333712 ERROR(3) cannot retrieve file system identity from mount point ${MOUNT_POINT,59,%s}

17 83218333713 ERROR(3) source_fsid ${SOURCE_FS_ID,22,%u} can not be found


18 83218333714 ERROR(3) source_fsid ${SOURCE_FS_ID,22,%u} not mounted

19 83218333715 ERROR(3) VDM mount_point ${MOUNT_POINT,59,%s} mismatch

20 83218333716 ERROR(3) mount_point ${MOUNT_POINT,59,%s} mismatch (${VDM_ROOT,8,%s}/... expected)

21 83218333717 ERROR(3) fsid ${CKPT_FS_ID,22,%u} not found

22 83218333718 ERROR(3) fsid ${CKPT_FS_ID,22,%u} is not ckpt: ${NAS_FS_QUERY,8,%s}

23 83218333719 ERROR(3) cannot retrieve ckpt name: ${NAS_FS_QUERY,8,%s}

24 83218333720 ERROR(3) ckpt ${CKPT_FS_ID,22,%u} not mounted: ${NAS_FS_QUERY,8,%s}

25 83218333721 ERROR(3) name ${CKPT_NAME,8,%s} not found

26 83218333722 ERROR(3) name ${CKPT_NAME,8,%s} is not ckpt: ${NAS_FS_QUERY,8,%s}

27 83218333723 ERROR(3) cannot retrieve ckpt fsid: ${NAS_FS_QUERY,8,%s}

28 83218333724 ERROR(3) ckpt ${CKPT_NAME,8,%s} not mounted: ${NAS_FS_QUERY,8,%s}

29 83218333725 ERROR(3) command unexpectedly succeeded: ${COMMAND,8,%s}

30 83218333726 ERROR(3) BUG: illegal action ${ACTION,8,%s}

31 96103235615 INFO(6) command succeeded: ${COMMAND,8,%s}

32 83218333728 ERROR(3) invalid fsid specified: ${CKPT_FS_ID,22,%u}

Table 46 NDMP (51) event facility (CS_PLATFORM) (page 2 of 2)


Table 47 NETLIB (73) event facility (DART)


1 81877598209 ERROR(3) Unable to connect to the NIS server ${serverAddr,8,%s} : ${reason,8,%s}

2 90467532802 NOTICE(5) The NIS server ${serverAddr,8,%s} is online.

Table 48 NFS (52) event facility (DART)


1 81876221953 ERROR(3) ERROR: NFS TCP initialization failed.

2 81876221954 ERROR(3) ERROR: NFS TCP portmap registration failed.

3 81876221955 ERROR(3) NFS: Unable to start NFS service due to UDP initialization failure.


Table 49 PERFSTATS (144) event facility (DART)


1 73292316673 ALERT(1) The statistics network service (statmonService) received a request from an unauthorized client: ${addrToString,52,%s}

Table 50 RCPD (83) event facility (DART)


1 81878253569 ERROR(3) Rcpd stopped listening:(OpenStream for TCP failed.)

2 81878253570 ERROR(3) Rcpd stopped listening:(${status,5,%u})

Table 51 RDFChannel (11) event facility (CS_CORE)


1 95026872321 INFO(6) command: ${command_line,8,%s}

Table 52 REP (108) event facility (DART) (page 1 of 4)


1 81879891969 ERROR(3) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), creating DB record failed:${arg2,8,%s}.

2 81879891970 ERROR(3) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), updating DB record failed:${arg2,8,%s}.

3 81879891971 ERROR(3) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), deleting DB record failed:${arg2,8,%s}.

4 81879891972 ERROR(3) Secondary=${arg0,8,%s}(alias=${arg1,8,%s}), creating DB record failed:${arg2,8,%s}.

5 81879891973 ERROR(3) Secondary=${arg0,8,%s}(alias=${arg1,8,%s}), updating DB record failed:${arg2,8,%s}.

6 81879891974 ERROR(3) Secondary=${arg0,8,%s}(alias=${arg1,8,%s}), deleting DB record failed:${arg2,8,%s}.

7 81879891975 ERROR(3) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), secondary restoring version failed:${arg2,8,%s}. No retry.

8 81879891976 ERROR(3) Secondary=${arg0,8,%s}(alias=${arg1,8,%s}), restoring version failed:${arg2,8,%s}. No retry.


9 81879891977 ERROR(3) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), recovering failed:${arg2,8,%s}. Session inactive.

10 81879891978 ERROR(3) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), starting secondary failed:${arg2,8,%s}. Session inactive.

11 81879891979 ERROR(3) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), getting sig list failed:${arg2,8,%s}. Session inactive.

12 81879891980 ERROR(3) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), doing pre-event failed:${arg2,8,%s}. Session inactive.

13 81879891981 ERROR(3) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), transfer failed:${arg2,8,%s}. Session inactive.

14 81879891982 ERROR(3) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), accessing db failed:${arg2,8,%s}. Session inactive.

15 81879891983 ERROR(3) Secondary=${arg0,8,%s}(alias=${arg1,8,%s}), accessing db failed:${arg2,8,%s}. Session inactive.

16 81879891984 ERROR(3) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), stopping secondary failed:${arg2,8,%s}. Session inactive.

17 81879891985 ERROR(3) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), searching comm base failed:${arg2,8,%s}. Session inactive.

18 81879891986 ERROR(3) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), doing post-event failed:${arg2,8,%s}. Session inactive.

19 81879891987 ERROR(3) Primary=%${arg0,8,%s}(alias=${arg1,8,%s}), sending stop secondary failed:${arg2,8,%s}. Sesssion inactive.

20 94764793876 INFO(6) Primary=${primaryName,8,%s}(alias=${alias,8,%s}), starting secondary. Control connection down.

21 94764793877 INFO(6) Primary=${primaryName,8,%s}(alias=${alias,8,%s}), abort secondary failed. Session inactive.

22 86174859286 WARNING(4) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), transferring. Data connection down. Retry.

23 94764793879 INFO(6) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), searching comm base. Secondary no space. Retry.

24 86174859288 WARNING(4) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), doing pre-event. Secondary no space. Retry.

25 86174859289 WARNING(4) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), doing post-event. Secondary no space. Retry.

26 94764793882 INFO(6) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), sending start secondary failed:${arg2,8,%s}. Retry.

27 94764793883 INFO(6) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), sending search comm base failed:${arg2,8,%s}. Retry.

28 86174859292 WARNING(4) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), Network communications failed:${arg2,8,%s}. Retry.




29 86174859293 WARNING(4) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), Network communications failed:${arg2,8,%s}.

30 94764793886 INFO(6) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), sending stop secondary failed:${arg2,8,%s}. Retry.

31 94764793887 INFO(6) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), transferring. Data connection up.

32 94764793888 INFO(6) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), starting secondary. Control connection up.

33 94764793889 INFO(6) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), searching comm base. Control connection up.

34 94764793890 INFO(6) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), searching comm base. Secondary space ok.

35 94764793891 INFO(6) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), doing pre-event. Control connection up.

36 94764793892 INFO(6) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), doing pre-event. Secondary space ok.

37 94764793893 INFO(6) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), doing post-event. Control connection up.

38 94764793894 INFO(6) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), Space on the destination is available.

39 94764793895 INFO(6) Primary=${arg0,8,%s}(alias=${arg1,8,%s}), Network connection is now available; stopping the secondary.

40 81879892008 ERROR(3) Primary Scheduler=${arg0,8,%s}, creating DB record failed:${arg1,8,%s}.

41 81879892009 ERROR(3) Primary Scheduler=${arg0,8,%s}, Updating a record from the root file system on the primary failed:${arg1,8,%s}.

42 81879892010 ERROR(3) Primary Scheduler=${arg0,8,%s}, deleting DB record failed:${arg1,8,%s}.

43 81879892011 ERROR(3) Secondary Scheduler=${arg0,8,%s}, creating DB record failed:${arg1,8,%s}.

44 81879892012 ERROR(3) Secondary Scheduler=${arg0,8,%s}, updating DB record failed:${arg1,8,%s}.

45 81879892013 ERROR(3) Secondary Scheduler=${arg0,8,%s}, deleting DB record failed:${arg1,8,%s}.

46 94764793902 INFO(6) Scheduler=${arg0,8,%s}, becomes in sync.

47 94764793903 INFO(6) Scheduler=${arg0,8,%s}, becomes out of sync.

48 81879892016 ERROR(3) Primary Scheduler=${arg0,8,%s}, recovering failed:${arg1,8,%s}. Inactive.

49 81879892017 ERROR(3) Primary Scheduler=${arg0,8,%s}, refreshing snapshot failed:${arg1,8,%s}. Inactive.




50 81879892018 ERROR(3) Primary Scheduler=${arg0,8,%s}, copying snapshot failed:${arg1,8,%s}. Inactive.

51 81879892019 ERROR(3) Primary Scheduler=${arg0,8,%s}, cancelling copying snapshot failed:${arg1,8,%s}. Inactive.

52 81879892020 ERROR(3) Primary Scheduler=${arg0,8,%s}, aborting secondary failed:${arg1,8,%s}. Inactive.

53 81879892021 ERROR(3) Secondary Scheduler=${arg0,8,%s}, recovering failed:${arg1,8,%s}. Inactive.

54 81879892022 ERROR(3) Secondary Scheduler=${arg0,8,%s}, refreshing snapshot failed:${arg1,8,%s}. Inactive.

55 77584924727 CRITICAL(2) Recovery for the Task with id=${taskId,8,%s} FAILED with Error Message id=${msgId,35,%llu}

56 73289957432 ALERT(1) TaskID ${taskId,8,%s} networkAddress ${srcAddr,8,%s} TargetNetworkAddress ${dstAddr,8,%s} connection down with status ${status,8,%s} on node ${node,5,%u}. Retry.

57 73289957433 ALERT(1) TaskId ${taskId,8,%s} BerkelyDb database error ${status,8,%s} is detected on node ${node,5,%u}, retry.

58 73289957434 ALERT(1) TaskID ${taskId,8,%s} encounter an unknown error ${status,8,%s} on node ${node,5,%u}.

59 94764793915 INFO(6) repSessionName=${repSessionName,8,%s} (alias=${alias,8,%s}), retry sending abort to secondary. Secondary has returned DpRequest_AbortInProgress.

60 81879892028 ERROR(3) Queuing recovery failed with status: ${status,8,%s} for repSessionName: ${repSessionName,8,%s} repType: ${repType,8,%s} taskId: ${taskId,8,%s}.



Table 53 REP (108) event facility (CS_CORE) (page 1 of 6)


1 95033229313 INFO(6) Task id=${task_id,30,%u} failed; No roll back needed.

2 82148327426 ERROR(3) ${state,8,%s} failed in task id=${task_id,30,%u} during rollback. But the error is missing for some reason.

3 82148327427 ERROR(3) ${state,8,%s} failed in task id=${task_id,30,%u} during rollback. The error is ${err_msg,8,%s}

4 82148327428 ERROR(3) The copy service create task id=${task_id,30,%u} failed and cannot roll back. In order to clean up the system, please delete the newly created destination filesystem id=${destinationFsId,22,%u}.


5 82148327429 ERROR(3) The copy service create task id=${task_id,30,%u} failed and cannot roll back. In order to clean up the system, please do the following: 1. umount the newly created destination filesystem id=${destinationFsId,22,%u} from ${serverName,56,%s}. 2. delete the newly created mountpoint ${fsMountpt,55,%s} from ${serverName,56,%s}. 3. delete the destination filesystem id=${destinationFsId,22,%u}.

6 82148327430 ERROR(3) The copy service create task id=${task_id,30,%u} failed and cannot roll back. In order to clean up the system, please do the following: 1. delete the newly created destination checkpoint id=${destinationSnapId,70,%u}. 2. umount the newly created destination filesystem id=${destinationFsId,22,%u} from ${serverName,56,%s}. 3. delete the newly created mountpoint ${fsMountpt,55,%s} from ${serverName,56,%s}. 4. delete the destination filesystem id=${destinationFsId,22,%u}.

7 82148327431 ERROR(3) The copy service create task id=${task_id,30,%u} failed and cannot roll back. In order to clean up the system, please delete the newly created destination checkpoint id=${destinationSnapId,70,%u}.

8 82148327432 ERROR(3) The copy service create task id=${task_id,30,%u} failed and cannot roll back. In order to clean up the system, please do the following: 1. umount the newly created destination checkpoint id=${destinationSnapId,70,%u} from ${serverName,56,%s}. 2. delete the newly created checkpoint mountpoint ${destinationSnapMntpt,55,%s} from ${serverName,56,%s}. 3. delete the destination checkpoint id=${destinationSnapId,70,%u}. 4. umount the newly created destination filesystem id=${destinationFsId,22,%u} from ${serverName,56,%s}. 5. delete the newly created mountpoint ${fsMountpt,55,%s} from ${serverName,56,%s}. 6. delete the destination filesystem id=${destinationFsId,22,%u}.

9 82148327433 ERROR(3) The copy service create task id=${task_id,30,%u} failed and cannot roll back. In order to clean up the system, please do the following: 1.umount the newly created destination checkpoint id=${destinationSnapId,70,%u} from ${serverName,56,%s}. 2. delete the newly created checkpoint mountpoint ${destinationSnapMntpt,55,%s} from ${serverName,56,%s}. 3. delete the destination checkpoint id=${destinationSnapId,70,%u}.

10 82148327434 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for filesystem with id=${fsId,22,%u}. In order to clean up the system, please do the following: 1. delete the second internal checkpoint id=${ckpt2Id,70,%u}. 2. umount the first internal checkpoint id=${ckpt1Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt1Mntpt,55,%s}. 3. delete the mountpoint for the first internal checkpoint path=${ckpt1Mntpt,55,%s}. 4. delete the first internal checkpoint id=${ckpt1Id,70,%u}.




11 82148327435 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for filesystem with id=${fsId,22,%u}. In order to clean up the system, please do the following: 1. umount the first internal checkpoint id=${ckpt1Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt1Mntpt,55,%s}. 2. delete the mountpoint for the first internal checkpoint path=${ckpt1Mntpt,55,%s}. 3. delete the first internal checkpoint id=${ckpt1Id,70,%u}.

12 82148327436 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for filesystem with id=${fsId,22,%u}. In order to clean up the system, please do the following: 1. delete the first internal checkpoint id=${ckpt1Id,70,%u}.

13 82148327437 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for filesystem with id=${fsId,22,%u}. In order to clean up the system, please do the following: 1. delete the second internal checkpoint id=${ckpt2Id,70,%u}. 2. umount the first internal checkpoint id=${ckpt1Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt1Mntpt,55,%s}. 3. delete the mountpoint for the first internal checkpoint path=${ckpt1Mntpt,55,%s}. 4. delete the first internal checkpoint id=${ckpt1Id,70,%u}. 5. umount the first destination fs with id=${fsId,22,%u} from ${serverName,56,%s} mounted at path=${fsMntpt,55,%s}. 6. delete the mountpoint for destination fs with path=${fsMntpt,55,%s}. 7. delete the newly created destination fs with id=${fsId,22,%u}.

14 82148327438 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for filesystem with id=${fsId,22,%u}. In order to clean up the system, please do the following: 1. umount the first internal checkpoint id=${ckpt1Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt1Mntpt,55,%s}. 2. delete the mountpoint for the first internal checkpoint path=${ckpt1Mntpt,55,%s}. 3. delete the first internal checkpoint id=${ckpt1Id,70,%u}. 4. umount the first destination fs with id=${fsId,22,%u} from ${serverName,56,%s} mounted at path=${fsMntpt,55,%s}. 5. delete the mountpoint for destination fs with path=${fsMntpt,55,%s}. 6. delete the newly created destination fs with id=${fsId,22,%u}.

15 82148327439 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for filesystem with id=${fsId,22,%u}. In order to clean up the system, please do the following: 1. delete the first internal checkpoint id=${ckpt1Id,70,%u}. 2. umount the first destination fs with id=${fsId,22,%u} from ${serverName,56,%s} mounted at path=${fsMntpt,55,%s}. 3. delete the mountpoint for destination fs with path=${fsMntpt,55,%s}. 4. delete the newly created destination fs with id=${fsId,22,%u}.




16 82148327440 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for filesystem with id=${fsId,22,%u}. In order to clean up the system, please do the following: 1. umount the first destination fs with id=${fsId,22,%u} from ${serverName,56,%s} mounted at path=${fsMntpt,55,%s}. 2. delete the mountpoint for destination fs with path=${fsMntpt,55,%s}. 3. delete the newly created destination fs with id=${fsId,22,%u}.

17 82148327441 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for filesystem with id=${fsId,22,%u}. In order to clean up the system, please do the following: 1. delete the newly created destination fs with id=${fsId,22,%u}.

18 82148327442 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for vdm $vdmName. In order to clean up the system, please do the following: 1. delete the second internal checkpoint id=${ckpt2Id,70,%u}. 2. umount the first internal checkpoint id=${ckpt1Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt1Mntpt,55,%s}. 3. delete the mountpoint for the first internal checkpoint path=${ckpt1Mntpt,55,%s}. 4. delete the first internal checkpoint id=${ckpt1Id,70,%u}. 5. delete the newly created destination vdm ${vdmName,56,%s}.

19 82148327443 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for vdm $vdmName. In order to clean up the system, please do the following: 1. umount the first internal checkpoint id=${ckpt1Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt1Mntpt,55,%s}. 2. delete the mountpoint for the first internal checkpoint path=${ckpt1Mntpt,55,%s}. 3. delete the first internal checkpoint id=${ckpt1Id,70,%u}. 4. delete the newly created destination vdm ${vdmName,56,%s}.

20 82148327444 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for vdm $vdmName. In order to clean up the system, please do the following: 1. delete the first internal checkpoint id=${ckpt1Id,70,%u}. 2. delete the newly created destination vdm ${vdmName,56,%s}.

21 82148327445 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for vdm $vdmName. In order to clean up the system, please do the following: 1. delete the newly created destination vdm ${vdmName,56,%s}.

22 82148327446 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for vdm $(vdmName}. In order to clean up the system, please do the following: 1. delete the second internal checkpoint id=${ckpt2Id,70,%u}. 2. umount the first internal checkpoint id=${ckpt1Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt1Mntpt,55,%s}. 3. delete the mountpoint for the first internal checkpoint path=${ckpt1Mntpt,55,%s}. 4. delete the first internal checkpoint id=${ckpt1Id,70,%u}.




23 82148327447 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for vdm $(vdmName}. In order to clean up the system, please do the following: 1. umount the first internal checkpoint id=${ckpt1Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt1Mntpt,55,%s}. 2. delete the mountpoint for the first internal checkpoint path=${ckpt1Mntpt,55,%s}. 3. delete the first internal checkpoint id=${ckpt1Id,70,%u}.

24 82148327448 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for vdm $(vdmName}. In order to clean up the system, please do the following: 1. delete the first internal checkpoint id=${ckpt1Id,70,%u}.

25 82148327449 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for filesystem with id=${fsId,22,%u}. In order to clean up the system, please do the following: 1. umount the second internal checkpoint id=${ckpt2Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt2Mntpt,55,%s}. 2. delete the mountpoint for the second internal checkpoint path=${ckpt2Mntpt,55,%s}. 3. delete the second internal checkpoint id=${ckpt2Id,70,%u}. 4. umount the first internal checkpoint id=${ckpt1Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt1Mntpt,55,%s}. 5. delete the mountpoint for the first internal checkpoint path=${ckpt1Mntpt,55,%s}. 6. delete the first internal checkpoint id=${ckpt1Id,70,%u}.

26 82148327450 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for filesystem with id=${fsId,22,%u}. In order to clean up the system, please do the following: 1. umount the first internal checkpoint id=${ckpt2Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt2Mntpt,55,%s}. 2. delete the mountpoint for the first internal checkpoint path=${ckpt2Mntpt,55,%s}. 3. delete the first internal checkpoint id=${ckpt2Id,70,%u}. 4. umount the first internal checkpoint id=${ckpt1Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt1Mntpt,55,%s}. 5. delete the mountpoint for the first internal checkpoint path=${ckpt1Mntpt,55,%s}. 6. delete the first internal checkpoint id=${ckpt1Id,70,%u}. 7. umount the first destination fs with id=${fsId,22,%u} from ${serverName,56,%s} mounted at path=${fsMntpt,55,%s}. 8. delete the mountpoint for destination fs with path=${fsMntpt,55,%s}. 9. delete the newly created destination fs with id=${fsId,22,%u}.




27 82148327451 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for vdm $vdmName. In order to clean up the system, please do the following: 1. umount the first internal checkpoint id=${ckpt2Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt2Mntpt,55,%s}. 2. delete the mountpoint for the first internal checkpoint path=${ckpt2Mntpt,55,%s}. 3. delete the first internal checkpoint id=${ckpt2Id,70,%u}. 4. umount the first internal checkpoint id=${ckpt1Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt1Mntpt,55,%s}. 5. delete the mountpoint for the first internal checkpoint path=${ckpt1Mntpt,55,%s}. 6. delete the first internal checkpoint id=${ckpt1Id,70,%u}. 7. delete the newly created destination vdm ${vdmName,56,%s}.

28 82148327452 ERROR(3) The replication service create task id=${task_id,30,%u} failed and cannot roll back for vdm $(vdmName}. In order to clean up the system, please do the following: 1. umount the first internal checkpoint id=${ckpt2Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt2Mntpt,55,%s}. 2. delete the mountpoint for the first internal checkpoint path=${ckpt2Mntpt,55,%s}. 3. delete the first internal checkpoint id=${ckpt2Id,70,%u}. 4. umount the first internal checkpoint id=${ckpt1Id,70,%u} from ${serverName,56,%s} mounted at path=${ckpt1Mntpt,55,%s}. 5. delete the mountpoint for the first internal checkpoint path=${ckpt1Mntpt,55,%s}. 6. delete the first internal checkpoint id=${ckpt1Id,70,%u}.



Table 54 SECMAP (115) event facility (DART)


1 94765252609 INFO(6) The migration of the secmap database to the Celerra Network Server version 5.6 format has started.

2 94765252610 INFO(6) The secmap database has been successfully migrated.

3 86175318019 WARNING(4) The secmap database was successfully migrated, but some minor errors were encountered.

4 73290416132 ALERT(1) The migration of the secmap database has failed. Secmap is not available.

Table 55 SECURITY (54) event facility (DART) (page 1 of 2)


1 81876353025 ERROR(3) Empty line in group file


2 81876353026 ERROR(3) Line too long in group file: ${line,8,%.64s}...

3 81876353027 ERROR(3) Bad line in group file: ${line,8,%.64s}...

4 73286418436 ALERT(1) Expired public key certificate retrieved for Persona ${PersonaName,8,%s}

Table 55 SECURITY (54) event facility (DART) (page 2 of 2)


Table 56 SECURITY (54) event facility (CS_PLATFORM)


10 96103432202 INFO(6) Network service ${sname,8,%s} has been started on node ${snode,8,%s} (Data Mover reboot not required) by UID ${uid,8,%s}.

11 96103432203 INFO(6) Network service ${sname,8,%s} has been stopped on node ${snode,8,%s} (Data Mover reboot not required) by UID ${uid,8,%s}.

12 96103432204 INFO(6) Network service ${sname,8,%s} has been started on node ${snode,8,%s} (pending a Data Mover reboot) by UID ${uid,8,%s}.

13 96103432205 INFO(6) Network service ${sname,8,%s} has been stopped on node ${snode,8,%s} (pending a Data Mover reboot) by UID ${uid,8,%s}.

Table 57 SMB (56) event facility (DART)


1 86171451393 WARNING(4) Local xid enforcement disabled

2 86171451394 WARNING(4) Local xid 16bit enforcement enabled

Table 58 SNAPSURE_SCHED (91) event facility (CS_PLATFORM)


1 83220955137 ERROR(3) Scheduled SnapSure creation failed, command: ${COMMAND,8,%s}

2 83220955138 ERROR(3) Scheduled snapsure refresh failed, command: ${COMMAND,8,%s}


Table 59 STORAGE (58) event facility (DART)


1 86171582465 WARNING(4) Volume ${volname,8,%s} moved from ${sp1,8,%s} to ${sp2,8,%s}.

2 86171582466 WARNING(4) LUN ${lunid,2,%d} was trespassed to ${sp,8,%s}.

3 81876615171 ERROR(3) Volume ${volname,8,%s}, ${devname,8,%s}, disk id ${mark_id,6,%lu}, disk mark has changed.

4 81876615172 ERROR(3) Incorrect reference on volume ${volname,8,%s}.

5 86171582469 WARNING(4) Incorrect reference on volume ${volname,8,%s}.

7 86171582471 WARNING(4) NDU mode initiated.

8 86171582472 WARNING(4) NDU mode exited.

9 81876615177 ERROR(3) NDU mode is already on.

10 81876615178 ERROR(3) NDU mode is already off.

11 81876615179 ERROR(3) NDU mode has been on for ${m,2,%d} minutes.

12 86171582476 WARNING(4) NDU mode is ${status,8,%s}.

13 81876615181 ERROR(3) Media error affected Please start Revectoring using "revector start vol=${volName,8,%s}"

14 81876615182 ERROR(3) VolCopy: RepThread:${threadName,8,%s} - Couldn't allocate Pages

15 81876615183 ERROR(3) volcopy - Vol:${volName,8,%s} failed to repair block:${blkNum,6,%llu} size:${size,5,%u}

16 81876615184 ERROR(3) volcopy - Vol:${volName,8,%s} failed to read the repaired block:${blockNum,6,%llu} size:${size,5,%u}

17 81876615185 ERROR(3) volcopy - Vol:${volName,8,%s} failed to verify block:${blockNum,6,%llu} size:${size,5,%u}

18 81876615186 ERROR(3) Vol ${volName,8,%s}: Revectoring will report the bad blocks in server_log

19 81876615187 ERROR(3) BasicVol:${volName,8,%s}, ${blksRep,6,%llu} blks repaired, ${restartAddr,6,%llu} RestartAddress, ${blksPend,6,%llu} nBlks pending for VolCopy at Abort

20 81876615188 ERROR(3) Revector Completed:BasicVol:${volName,8,%s}, ${blksRep,6,%llu} blks repaired, total ${numBlks,6,%llu} nBlks covered

21 94761517077 INFO(6) For vol:${volName,8,%s} Need to abort replication, delete the filesystem as corrupted

22 81876615190 ERROR(3) Volume:${volName,8,%s} not affected, NO need for Revectoring


Table 60 SVFS (70) event facility (DART)


1 86172368897 WARNING(4) FSID:${id,5,%u} SavVol:${vol,8,%s} MaxSize:${maxsize,5,%u} MB %Full(hwm=${hwm,2,%d}) reached (t:${ticks,3,%q})

2 81877401602 ERROR(3) FSID:${id,22,%u} SavVol:${vol,76,%s} Inactive

3 94762303491 INFO(6) Restore completed successfully. (PFS_VOLID:${volname,76,%s})

4 94762303492 INFO(6) Restore in progress ${percent,5,%1u} percent done. (PFS_VOLID:${volid,76,%s})

5 68992499717 EMERGENCY(0) FSID:${id,22,%u} SavVol:${vol,76,%s} conversion paused (t:${ticks,6,%llu})

6 81877401606 ERROR(3) FsVol:${FsVolName,76,%s} SavVol:${SaveVolName,76,%s} Inactivate ALL ckpt

Table 61 SVFS (70) event facility (CS_PLATFORM) (page 1 of 2)


10 83219578890 ERROR(3) ${DM_EVENT_STAMP,8,%s} autoextension failed: cannot find clients for SavVol ID ${VOL_ID,32,%u}.

11 83219578891 ERROR(3) ${DM_EVENT_STAMP,8,%s} autoextension failed: no checkpoint with ${CLIENT,68,%s} exists.

12 83219578892 ERROR(3) ${DM_EVENT_STAMP,8,%s} ${CKPT_NAME,69,%s} autoextension failed: unable to determine checkpoint percent used.

13 96104480781 INFO(6) ${DM_EVENT_STAMP,8,%s} checkpoint ${FS_ID,22,%u} not found: checking the most recent checkpoint on SavVol ${VOL_ID,32,%u}.

14 83219578894 ERROR(3) ${DM_EVENT_STAMP,8,%s} autoextension failed: no checkpoint using savVol ${VOL_ID,32,%u} exists.

15 96104480783 INFO(6) ${DM_EVENT_STAMP,8,%s} extending checkpoint ${CKPT_NAME,69,%s}.

16 83219578896 ERROR(3) ${DM_EVENT_STAMP,8,%s} autoextension failed: unable to find checkpoint using volume ID ${VOL_ID,32,%u}.

17 83219578897 ERROR(3) (${DM_EVENT_STAMP,8,%s}) ${CKPT_NAME,69,%s} autoextension failed: unable to get checkpoint HWM.

18 96104480786 INFO(6) ${DM_EVENT_STAMP,8,%s} ${CKPT_NAME,69,%s} autoextension skipped: checkpoint HWM is ${HWM,18,%d}.

19 96104480787 INFO(6) ${DM_EVENT_STAMP,8,%s} ${CKPT_NAME,69,%s} autoextension skipped: used ${USED,18,%d}, HWM ${HWM,18,%d}%.

20 96104480788 INFO(6) ${DM_EVENT_STAMP,8,%s} ${CKPT_NAME,69,%s} autoextension succeeded.


21 83219578901 ERROR(3) ${DM_EVENT_STAMP,8,%s} ${COMMAND,8,%s} ${ERROR_TEXT,8,%s}.

29 83219578909 ERROR(3) ${ARG0,8,%s} failed to unmount inactive checkpoint ${CKPT_NAME,69,%s}.

33 87514546209 WARNING(4) Only one scheduled replication restart checkpoint exists for ${SRC_FS_NAME,68,%s} to restart replication.

35 87514546211 WARNING(4) Scheduled replication restart checkpoint ${OLDER_CKPT_NAME,69,%s} refresh failed.

36 87514546212 WARNING(4) Checkpoint refresh query failed. ${ERROR_TEXT,8,%s}.

39 83219578919 ERROR(3) TimeStamp ${DM_EVENT_STAMP,8,%s}: checkpoint: ${CKPT_NAME,69,%s} with SavVol ID: ${SAVVOLID,32,%u} Extend failed as Size:${CKPTSIZE,8,%s} exceeded Maximum size:${MAX_SIZE,8,%s}.

40 83219578920 ERROR(3) Checkpoint autoextension failed for ${DM_EVENT_STAMP,8,%s} ${CKPT_NAME,69,%s}.

41 83219578921 ERROR(3) Checkpoint extension failed: ${DM_EVENT_STAMP,8,%s} command failed to complete.

42 83219578922 ERROR(3) Checkpoint autoextension failed for checkpoint: ${DM_EVENT_STAMP,8,%s}, ${CKPT_NAME,69,%s} with SavVol ID: ${SAVVOLID,32,%u}. Maximum size exceeded: ${MAX_SIZE,8,%s}.

Table 61 SVFS (70) event facility (CS_PLATFORM) (page 2 of 2)


Table 62 SVFS(70) event facility (CS_CORE)


1 86440804353 WARNING(4) ${moverName,56,%s}: The checkpoint ${checkPointName,69,%s} mount failed on failover.

2 95030738946 INFO(6) On ${hostname,8,%s}, the memory quota high water mark has been reached.

3 95030738947 INFO(6) The checkpoint volume allocation high water mark has been reached.

4 95030738948 INFO(6) The checkpoint volume allocation quota has been exceeded.

Table 63 SYR (143) event facility (CS_PLATFORM)


5 96109264901 INFO(6) The SYR file ${src_file_path,8,%s} with ${dest_extension,8,%s} extension is attached.


Table 64 UFS (64) event facility (DART) (page 1 of 3)


1 81877008385 ERROR(3) Event ${evt,5,%u} occurred while doing a dircvt

2 81877008386 ERROR(3) Event ${evt,5,%u} occurred while doing a dircvt

4 86171975684 WARNING(4) Block soft quota crossed (fs ${mountPoint,55,%s}, ${idStr,8,%s} ${quotaId,25,%u})

5 81877008389 ERROR(3) Block hard quota reached/exceeded (fs ${mountPoint,55,%s}, ${idStr,8,%s} ${userId,25,%u})

6 81877008390 ERROR(3) Translation already scheduled on FS ${fsid,5,%u}. Please turn off translation before setting dirType

7 86171975687 WARNING(4) File system ${fsid,22,%u} ${worm,8,%s} is corrupted and will remain unmounted.

8 86171975688 WARNING(4) filesystem ${fsid,22,%u} will remain un-mounted due to GID Map corruption

9 86171975689 WARNING(4) filesystem ${fsname,22,%u} has reached the maximum unique GID's. GID Table needs to be rebuilt

10 81877008394 ERROR(3) MPDTranslate of ${fs,8,%s}: Directory corruption in inode ${ino,5,%u}: ${msg,8,%s}

11 86171975691 WARNING(4) Inodes used has crossed the threshold (${thresh,2,%d}%) for file system ${fsname,68,%s}

12 86171975692 WARNING(4) Inodes used has crossed the threshold (${thresh,2,%d}%) for fs ${fsname,8,%s}

13 86171975693 WARNING(4) Inodes used has dropped below the threshold (${thresh,2,%d}%) for fs ${fsname,8,%s}

14 86171975694 WARNING(4) Inodes used has dropped below the threshold (${thresh,2,%d}%) for fs ${fsname,8,%s}

15 81877008399 ERROR(3) File system id: ${fsid,22,%u} has inaccurate filesize in superblock. Superblock file system size = ${fssize,6,%llu}, Volume size = ${volsize,6,%llu}

16 81877008400 ERROR(3) Quota usage for file system ${mountPoint,55,%s}, userid ${userId,25,%u} has exceeded 4TB and it can result in inconsistent quota reporting or system behavior

17 86171975697 WARNING(4) UFS log replay: incomplete transactions skipped

18 90466942994 NOTICE(5) MPDTranslate of ${fs,8,%s}: Early termination, incomplete translation of ${idone,5,%u} of ${itotal,5,%u} dir inodes traversed. See log for errors. status = ${errmsg,8,%s}

19 90466942995 NOTICE(5) MPDTranslate of ${fs,8,%s}: completed translation of ${idone,5,%u} of ${itotal,5,%u} dir inodes without 100 percent success. See log for errors. status = ${errmsg,8,%s}

20 90466942996 NOTICE(5) MPDTranslate of ${fs,8,%s}: Successfully completed translation of ${itotal,5,%u} dir inodes.


21 90466942997 NOTICE(5) MPDTranslate of ${fs,8,%s}: ${what,8,%s} after incomplete translation of ${idone,5,%u} of ${itotal,5,%u} dir inodes ${why,8,%s}

22 90466942998 NOTICE(5) MPDTranslate of ${fs,8,%s}: shadow getAllNames of ${fname,8,%s} failed in upgrade of ino ${ino,5,%u}. Ignoring this shadow.

23 81877008407 ERROR(3) MPDTranslate of ${fs,8,%s}: shadow getAllNames of ${fname,8,%s} failed in upgrade of ino ${ino,5,%u} : ${errmsg}

24 81877008408 ERROR(3) MPDTranslate of ${fs,8,%s}: Cannot progress: tree quota for treeid ${id,5,%u} exceeded

25 81877008409 ERROR(3) MPDTranslate of ${fs,8,%s}: aborting after incomplete translation of ${idone,5,%u} of ${itotal,5,%u} dir inodes due to errors in quota tree: status = ${errmsg,8,%s}

26 81877008410 ERROR(3) MPDTranslate of ${fs,8,%s}: flush of shadow failed: status = ${errmsg,8,%s}

27 81877008411 ERROR(3) MPDTranslate of ${fs,8,%s}: direnter of ${fname,8,%s} failed for dir ino ${ino,5,%u} due to name-too-long

28 81877008412 ERROR(3) MPDTranslate of ${fs,8,%s}: failure on dir inode ${ino,5,%u} : status = ${errmsg,8,%s}

29 81877008413 ERROR(3) MPDTranslate of ${fs,8,%s}: Suspending because of low ${why,8,%s}

30 81877008414 ERROR(3) MPDTranslate of ${fs,8,%s}: skipping dir node ${ino,5,%u}: out of ${why,8,%s} quota for id ${id,5,%u}

31 81877008415 ERROR(3) MPDTranslate of ${fs,8,%s}: Running I18N name conversion via uc_config will possibly resolve the above invalid-argument errors from shadow getAllNames

32 81877008416 ERROR(3) MPDTranslate of ${fs,8,%s}: direnter of ${fname,8,%s} failed for dir ino ${ino,5,%u} : status = ${errmsg,8,%s}

33 81877008417 ERROR(3) MPDTranslate of ${fs,8,%s}: NameTooLong errors in log will likely be cured by rebuilding shadows of affected directories

34 81877008418 ERROR(3) MPDTranslate of ${fs,8,%s}: Base of Quota tree not a dir on inode ${ino,5,%u} treeid ${id,5,%u}

35 81877008419 ERROR(3) MPDTranslate of ${fs,8,%s}: ${what,8,%s} failure on dir inode ${ino,5,%u} : status = ${errmsg,8,%s}

36 81877008420 ERROR(3) MPDTranslate of ${fs,8,%s}: shadow getAllNames of ${fname,8,%s} failed in upgrade of ino ${ino,5,%u} : ${errmsg,8,%s}

37 81877008421 ERROR(3) MPDTranslate of ${fs,8,%s}: update of superblock failed with ${errmsg,8,%s}. Directory layout may not be committed to disk




38 81877008422 ERROR(3) MPDTranslate of ${fs,8,%s}: Possible FS corruption: skipping inode ${ino,5,%u} found to have linkcount of ${nlink,5,%u} and does not appear to be under deferred delete

39 81877008423 ERROR(3) MPDTranslate of ${fs,8,%s}: Skipping dir inode ${ino,5,%u} due to multiple shadow rebuilds

40 81877008424 ERROR(3) MPDTranslate of ${fs,8,%s}: shadow createEntry of ${fname,8,%s} failed for dir ino ${ino,5,%u} : status = ${errmsg,8,%s}

41 77582041129 CRITICAL(2) File system ${tag,8,%s}, fsnum ${fsnum,22,%u} detected a possible PBR count inconsistency.

42 81877008426 ERROR(3) fsid ${fsid,5,%u}: transaction replay skipped. Missing volume information, fs may be corrupted



Table 65 UPSMonitor (140) event facility (CS_PLATFORM) (page 1 of 4)


1 87519133697 WARNING(4) Communication lost between the agent and the UPS.

2 87519133698 WARNING(4) The UPS has sensed a load greater than 100 percent of its rated capacity.

3 78929199107 CRITICAL(2) The UPS has failed its internal self-test.

4 87519133700 WARNING(4) The UPS batteries are discharged.

5 87519133701 WARNING(4) The UPS has switched to battery backup power.

6 87519133702 WARNING(4) The UPS has enabled SmartBoost(TM); low incoming line voltage.

7 87519133703 WARNING(4) The UPS system's batteries are low and will soon be exhausted.

8 96109068296 INFO(6) UPS communication has been established.

9 96109068297 INFO(6) Returned from battery backup power; utility power restored.

10 96109068298 INFO(6) The UPS passed internal self-test.

11 96109068299 INFO(6) The UPS has returned from a Low Battery condition.

12 78929199116 CRITICAL(2) The UPS has been switched off by a management station.

13 87519133709 WARNING(4) The UPS entered sleep mode. Power to the load will be cut off.

14 96109068302 INFO(6) The UPS has returned from sleep mode. Power to the load has been restored.

15 87519133711 WARNING(4) The UPS has started its reboot sequence.

16 87519133712 WARNING(4) The DIP switch settings on the UPS have been changed.


17 78929199121 CRITICAL(2) The UPS batteries require immediate replacement.

18 78929199122 CRITICAL(2) An Environment contact closure has faulted.

19 96109068307 INFO(6) An Environment contact closure has returned to its default state.

20 78929199124 CRITICAL(2) The UPS is on bypass because of an internal fault.

21 87519133717 WARNING(4) UPS put on bypass by user via software or front UPS panel.

22 87519133718 WARNING(4) UPS put on bypass by user.

23 96109068311 INFO(6) The UPS has returned from bypass mode.

24 78929199128 CRITICAL(2) The base module bypass power supply needs repair.

25 78929199129 CRITICAL(2) The base module fan needs repair.

26 87519133722 WARNING(4) Communication lost with external battery packs; check battery signal cable.

27 96109068315 INFO(6) Communication established with external battery packs.

28 96109068316 INFO(6) A battery run-time calibration test has been initiated.

29 96109068317 INFO(6) Agent restarting as commanded by manager.

30 96109068318 INFO(6) A UPS is turned on.

31 87519133727 WARNING(4) The UPS has enabled SmartTrim(TM) voltage reduction.

32 96109068320 INFO(6) Authentication on agent code image is done.

33 96109068321 INFO(6) The overload condition has been cleared.

34 96109068322 INFO(6) The UPS has returned from SmartBoos(TM).

35 96109068323 INFO(6) The UPS has returned from SmartTrim(TM) voltage reduction.

36 96109068324 INFO(6) The UPS has returned from a bad battery fault.

37 96109068325 INFO(6) The UPS has finished calibrating.

38 96109068326 INFO(6) The UPS discharge condition has been cleared.

39 96109068327 INFO(6) A graceful shutdown has been initiated.

41 87519133737 WARNING(4) Outlet has been turned on.

42 87519133738 WARNING(4) Outlet has turned off.

43 87519133739 WARNING(4) Outlet has rebooted.

44 87519133740 WARNING(4) The SNMP configuration has been changed.

45 87519133741 WARNING(4) The Outlet configuration has been changed.

46 87519133742 WARNING(4) Three unsuccessful logins have been attempted using the console.

47 87519133743 WARNING(4) An unsuccessful login has been attempted using HTTP.




48 87519133744 WARNING(4) Someone has changed the password on the device.

49 87519133745 WARNING(4) The output voltage is not within an acceptable range.

50 96109068338 INFO(6) The output voltage has returned to an acceptable level.

51 78929199155 CRITICAL(2) The battery charger has failed.

52 96109068340 INFO(6) The battery charger failure condition has been cleared.

53 78929199157 CRITICAL(2) The battery temperature threshold has been violated.

54 96109068342 INFO(6) The battery over temperature has been cleared.

55 87519133751 WARNING(4) SmartBoost(TM) or SmartTrim(TM) relay fault.

56 96109068344 INFO(6) SmartBoost(TM) or SmartTrim(TM) relay fault has been cleared.

57 87519133753 WARNING(4) A humidity threshold has been violated on probe 1.

58 96109068346 INFO(6) A humidity threshold violation has been cleared on probe 1.

59 87519133755 WARNING(4) A temperature threshold has been violated on probe 1.

60 96109068348 INFO(6) A temperature threshold violation has been cleared on probe 1.

61 87519133757 WARNING(4) A humidity threshold has been violated on probe 2.

62 96109068350 INFO(6) A humidity threshold violation has been cleared on probe 2.

63 87519133759 WARNING(4) A temperature threshold has been violated on probe 2.

64 96109068352 INFO(6) A temperature threshold violation has been cleared on probe 2.

65 96109068353 INFO(6) Communication has been established between the agent and the Environmental Monitor.

66 87519133762 WARNING(4) Communication has been lost between the agent and the Environmental Monitor.

67 96109068355 INFO(6) The number of batteries has increased.

68 96109068356 INFO(6) The number of batteries has decreased.

69 96109068357 INFO(6) The number of power modules has increased.

70 96109068358 INFO(6) The number of power modules has decreased.

71 96109068359 INFO(6) An intelligence module has been inserted.

72 96109068360 INFO(6) An intelligence module has been removed.

73 96109068361 INFO(6) A redundant intelligence module has been inserted.

74 96109068362 INFO(6) A redundant intelligence module has been removed.

75 96109068363 INFO(6) An external battery frame has been added.

76 96109068364 INFO(6) An external battery frame has been removed.




77 78929199181 CRITICAL(2) An abnormal condition has been detected.

78 96109068366 INFO(6) An abnormal condition has been cleared.

79 96109068367 INFO(6) The status of the device being monitored has changed.

80 87519133776 WARNING(4) The UPS has no batteries attached.

81 96109068369 INFO(6) The UPS's batteries have been attached.

82 96109068370 INFO(6) A new user has been added.

83 96109068371 INFO(6) A user has been deleted.

84 96109068372 INFO(6) A user has been modified.



Table 66 USRMAP (93) event facility (DART)


1 94763810817 INFO(6) The Usermapper database has been created.

2 94763810818 INFO(6) Usermapper service has been enabled.

3 94763810819 INFO(6) The Usermapper service has been disabled.

4 94763810820 INFO(6) The Usermapper database has been destroyed.

5 94763810821 INFO(6) The Usermapper server is available at ${interface,8,%s} for the client.

6 86173876230 WARNING(4) The Usermapper server is no more available at ${interface,8,%s} for the Usermapper client.

8 94763810824 INFO(6) The migration of the Usermapper database to the Celerra Network Server version 5.6 format has started.

9 94763810825 INFO(6) The Usermapper database has been successfully migrated.

10 86173876234 WARNING(4) The Usermapper database was successfully migrated, but some minor errors were encountered.

11 73288974347 ALERT(1) The migration of the Usermapper database failed. Only the following tables has been migrated: ${table,8,%s}. Usermapper is not available.

Table 67 VC (81) event facility (DART) (page 1 of 3)


1 90468057089 NOTICE(5) The virus checker is running normally.


2 81878122498 ERROR(3) ${type,8,%s} high water mark reached.

3 86173089795 WARNING(4) ${type,8,%s} low water mark reached.

4 81878122500 ERROR(3) No virus checker server is available.

5 81878122501 ERROR(3) No virus checker server is available. CIFS is stopped.

6 81878122502 ERROR(3) No virus checker server is available. Virus checking is stopped.

7 81878122503 ERROR(3) '${filename,8,%s}' was not checked.

8 90468057096 NOTICE(5) Server ${ipaddr,8,%s} is online. RPC program version ${rpc,2,%d}, ${cava,8,%s}.

9 81878122505 ERROR(3) Error on server ${ipaddr,8,%s}: ${status,8,%s}${winerror,8,%s}, RPC program version ${rpc,2,%d}, ${cava,8,%s}.

10 90468057098 NOTICE(5) The virus checker is started.

11 90468057099 NOTICE(5) Scanning was completed for file system ${fsid,2,%d} mounted on ${mountPath,8,%s}. ${dirs,2,%d} directories were scanned and ${files,2,%d} files were submitted to the scan engine.

12 81878122508 ERROR(3) Scanning was aborted for file system ${fsid,2,%d} mounted on ${mountPath,8,%s} for this reason: ${error,8,%s}. ${dirs,2,%d} directories were scanned and ${files,2,%d} files were submitted to the scan engine.

13 81878122509 ERROR(3) The antivirus (AV) engine deleted ${file,8,%s}, ${user,8,%s}.

14 81878122510 ERROR(3) The antivirus (AV) engine renamed ${file,8,%s}, ${user,8,%s}.

15 86173089807 WARNING(4) The antivirus (AV) engine modified ${file,8,%s}, ${user,8,%s}.

16 90468057104 NOTICE(5) The virus checker is stopped.

17 90468057105 NOTICE(5) The virus checker is started.

18 90468057106 NOTICE(5) The VC server ${ipaddr,8,%s} updated the reference time, reference=${reference,8,%s}.

19 86173089811 WARNING(4) A number of files (${count,2,%d}) were not checked for the file system ${fsid,2,%d}.

20 86173089812 WARNING(4) The virus checker is already running. The new number of threads is ignored.

21 86173089813 WARNING(4) The maxThreadWaiting parameter is set to ${maxThreadWaiting,2,%d}.

22 86173089814 WARNING(4) The waitTimeout parameter is set to ${waitTimeout,2,%d} seconds.

23 86173089815 WARNING(4) The specified RPC retry timeout is invalid. It is reset to ${RPCRetryTimeout,2,%d} milliseconds.




24 86173089816 WARNING(4) The specified RPC request time is invalid. It is reset to ${RPCRequestTimeout,2,%d} milliseconds.

25 86173089817 WARNING(4) The specified survey time is invalid. It is reset to ${surveyTime,2,%d} seconds.

26 86173089818 WARNING(4) The specified high water mark value is invalid. It is reset to ${highWaterMark,2,%d}.

27 86173089819 WARNING(4) The specified low water mark value is invalid. It is reset to ${lowWaterMark,2,%d}.

28 86173089820 WARNING(4) The shutdown=cifs option cannot be used with a single server.



Table 68 VMCAST (84) event facility (DART)


1 94763220993 INFO(6) Group:${rcpGpeName,8,%s} FSID:${fsID,2,%d} ${convert,8,%s} Copy done (t:${ticks,6,%q})

2 81878319106 ERROR(3) Group:${rcpGpeName,8,%s} FSID:${fsID,2,%d} Copy Failed restartad:0x%${addr,6,%llx} (t:${ticks,6,%q})

5 94763220997 INFO(6) Group:${group,8,%s} FSID:${fsId,2,%d} Copy Interrupted(because of unmount) restartAddress:0x${restartAddr,6,%llx} (t:${ticks,3,%q})

6 94763220998 INFO(6) pfscopy: g:${rcpGpeName,8,%s} targetIP:${targetIP,8,%s} WARNING Network or Receiver down (t:${ticks,3,%q})

7 94763220999 INFO(6) ipfscopy: g:${rcpGpeName,8,%s} targetIP:${targetIP,8,%s} Network or Receiver up (t:${ticks,3,%q})

9 86173286409 WARNING(4) Group:${rcpGpeName,8,%s} FSID:${fsID,2,%d} Resync Copy failed. Full Copy is started automatically. (t:${ticks,3,%q})

10 81878319114 ERROR(3) VMCastReceiver: Bad CRC gpe:${MCastNode,8,%s} vol:${volName,8,%s} expected:0x${expected,5,%x} computed:0x${computed,5,%x}

11 81878319115 ERROR(3) Group:${rcpGpeName,8,%s} FSID:${fsID,2,%d} Resync Copy failed. Full Copy has to be started. (t:${ticks,6,%llu})

Table 69 VMCAST (84) event facility (CS_PLATFORM) (page 1 of 2)


7 83220496391 ERROR(3) FS Copy convert failed: ${COMMAND,8,%s}


8 83220496392 ERROR(3) FS Copy cleanup failed on ${SRC_FS_NAME,8,%s}: ${COMMAND,8,%s}

Table 69 VMCAST (84) event facility (CS_PLATFORM) (page 2 of 2)


Table 70 VRPL (77) event facility (DART) (page 1 of 2)


1 81877860353 ERROR(3) srcvol:${arg0,77,%s} Replication inactive for reason:${arg1,8,%s}

2 68992958466 EMERGENCY(0) srcvolsec:${srcVolName,77,%s} Resync is requested.

6 86172827654 WARNING(4) IPRepSender: g:${rcpGroupName,8,%s} localIP:${localIP,51,%s} targetIP:${targetIP,51,%s} WARNING Network or Receiver down (t:${ticks,6,%q})

7 86172827655 WARNING(4) IPRepSender: g:${rcpGroupName,8,%s} localIP:${localIP,51,%s} targetIP:${targeIP,51,%s} Network or Receiver up (t:${ticks,6,%q})

8 81877860360 ERROR(3) CheckSuperBlock on vol=${volName,76,%s} failed. Replication is waiting on Abort.

9 94762762249 INFO(6) Replica: srcvol:${saveVolName,8,%s} resume Flow (t:${ticks,6,%llu})

10 86172827658 WARNING(4) Replica: PFS:${fsID,22,%u} Frozen srcvol:${srcVolName,77,%s} (t:${ticks,6,%llu})

11 86172827659 WARNING(4) Replica: PFS:${fsID,22,%u} Thaw not required. PFS unmounted. srcvol:{$srcVolName} (no deltaset switch) (t:${ticks,6,%llu})

14 86172827662 WARNING(4) Replica: PFS:${fsID,22,%u} mounted ro srcvol:${srcVolName,77,%s} (t:${ticks,6,%q})

15 86172827663 WARNING(4) Replica: PFS:${fsID,22,%u} mounted rw srcvol:${srcVolName,77,%s} (t:${ticks,6,%q})

17 81877860369 ERROR(3) RepControl failed. Wait for stop to come.

18 81877860370 ERROR(3) IPRepSender stop failed on gpe:${gpeName,8,%s} vol:${volName,76,%s}.

19 94762762259 INFO(6) IPRepSender stop succeeded on gpe:${gpeName,8,%s} vol:${volName,76,%s}.

20 94762762260 INFO(6) IPRepSender is shutdown on gpe:${gpeName,8,%s} vol:${volName,76,%s}.

21 94762762261 INFO(6) Manual IPRepTransfer failed vol:${volName,76,%s} add:${transferAdd,6,%llu}.

22 81877860374 ERROR(3) srcvolsec:${srcVolName,76,%s} Playback failed.


23 86172827671 WARNING(4) Replica: srcvol:${srcVolName,77,%s} Flow on Hold (no deltaset switch). Check SaveVolume space, network, playback side. (t:${ticks,6,%llu})

24 94762762264 INFO(6) IPRepSender::Manual IPRepTransfer succeeded vol:${volName,76,%s} add:${transferAdd,6,%llu}.

25 86172827673 WARNING(4) Replica: PFS:${pfsId,22,%u} Thaw srcvol:${srcVolName,77,%s} (no deltaset switch) (t:${ticks,3,%q})

26 86172827674 WARNING(4) Replica: Thaw not required. PFS unmounted. srcvol:${srcvol,77,%s} (no deltaset switch) (t:${ticks,6,%q})

27 81877860379 ERROR(3) ${who,8,%s} Capacity mode is switched to low, vol:${OrigFsVolName,76,%s}

28 94762762268 INFO(6) srcVol:${OrigFsVolName,76,%s} iosize:${ioSize,5,%u} lesser than 8KB

29 94762762269 INFO(6) VolID:${VolName,76,%s} Last DeltaSet Replayed:${DeltaSetGenCount,2,%d} created on Primary at:${ReplayTime,9,%m/%d/%Y %H:%M:%S}

30 68992958494 EMERGENCY(0) RedoBuf should be extended or Config Vol to slow for vol:${volName,76,%s}

Table 70 VRPL (77) event facility (DART) (page 2 of 2)


Table 71 WINS (117) event facility (DART)


1 81880481793 ERROR(3) Unable to connect to the WINS server ${serverAddr,8,%s}

2 90470416386 NOTICE(5) The WINS server ${serverAddr,8,%s} is online.

Table 72 XLT (72) event facility (DART)


1 77582565377 CRITICAL(2) Corruption in XLT files was detected; a dial home was triggered

2 77582565378 CRITICAL(2) corruption in XLT files is detected, recovery is triggered


Table 73 XLT (72) event facility (CS_PLATFORM)


100 83219710052 ERROR(3) Translation directory does not exist yet.

101 83219710053 ERROR(3) uc_config update failed

102 96104611942 INFO(6) uc_config update succeeded


Index

Aactions, that events trigger 33

CCheckup facility 13community name, security 4

Eemail

notifications 21, 23configuration file corrupted or deleted 27

specifying a subject line 69troubleshooting 64

eventdefinition 3examples 6facility 6facility names 7ID, determining 30log 13notification 13number 11severity level 12throttling 14

rearm 14resetafter 15threshold 14

event, controlling repetition of 14

Ffacility, See event, facilityfile system, size threshold exceeded

email notification 44SNMP trap 44

fsSizeThreshold parameter 44

MMIB, modify for SNMP 34

Nnas_eventlog.cfg 13notification

configuration file 13custom configuration files 13customizing 14default 13definition 3, 13email configuration 21loading configuration files 42verifying loaded configuration files 43

Pparameter, fsSizeThreshold 44

Ssecurity with SNMPv1 4SnapSure SavVol high water mark reached

email notification 49SNMP trap 49

SNMPchanging the port 61community name 4configuring traps 34message types 16modify MIB 34security 16, 66traps 15

Ttelephone, EMC Customer Service contact 63trap, SNMP 15trap.cfg 35

VVirus Checker events, email notification 53

About this technical moduleAs part of its effort to continuously improve and enhance the performance and capabilities of the Celerra Network Server product line, EMC periodically releases new versions of Celerra hardware and software. Therefore, some functions described in this document may not be supported by all versions of Celerra software or hardware presently in use. For the most up-to-date information on product features, see your product release notes. If your Celerra system does not offer a function described in this document, contact your EMC Customer Support Representative for a hardware upgrade or software update.

Comments and suggestions about documentationYour suggestions will help us improve the accuracy, organization, and overall quality of the user documentation. Send a message to [email protected] with your opinions of this document.

Copyright © 1998-2010 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

Version 5.6 138 of 138

configuring celerra events and notifications - dell emc · pdf file4 of 138 version 5.6...

Documents