celerra network server configuring celerra events and notifications · 2020-03-09 · configuring...

1 of 106

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

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

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

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

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

User interface choices for events and notifications. . . . . . . . . . . . . . . . .16Roadmap for events and notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . .17Configuring DNS on the Control Station . . . . . . . . . . . . . . . . . . . . . . . . . .18Checking if email is working properly before configuring notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Gathering required information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Task 1: Determining facilities that generate events . . . . . . . . . . . . .22Task 2: Determining events associated with a facility . . . . . . . . . . .23Task 3: Determining a list of all possible actions . . . . . . . . . . . . . . .24Task 4: Determining which events trigger an action . . . . . . . . . . . .25

Configuring SNMP trap notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Task 1: Modifying the Celerra MIB file for SNMP traps . . . . . . . . . . .26Task 2: Configuring SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Task 3: Sending a test SNMP trap. . . . . . . . . . . . . . . . . . . . . . . . . . . .27Task 4: Receiving a test SNMP trap . . . . . . . . . . . . . . . . . . . . . . . . . .28Task 5: Configuring SNMP on Data Movers . . . . . . . . . . . . . . . . . . . .30Task 6: Verifying an SNMP configuration. . . . . . . . . . . . . . . . . . . . . .30

Customizing notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Task 1: Creating a configuration file. . . . . . . . . . . . . . . . . . . . . . . . . .31Task 2: Loading a configuration file . . . . . . . . . . . . . . . . . . . . . . . . . .32Task 3: Verifying the configuration file loaded . . . . . . . . . . . . . . . .33

SNMP traps and email notifications: Examples . . . . . . . . . . . . . . . . . . . .34When file system usage exceeds certain limits. . . . . . . . . . . . . . . . .34When the SnapSure SavVol usage reaches its high water mark . . .37When there are Virus Checker events . . . . . . . . . . . . . . . . . . . . . . . .42When a hard or soft quota is exceeded . . . . . . . . . . . . . . . . . . . . . . .46When there are ACL updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Configuring Celerra Events andNotifications

P/N 300-002-708Rev A03

Version 5.5March 2007

Configuring Celerra Events and NotificationsVersion 5.5 2 of 106

Event notification actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Troubleshooting events and notifications . . . . . . . . . . . . . . . . . . . . . . . .57

Technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Email notifications not received . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Checking if sendmail is running . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Configuring sendmail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Notifications missing or not working . . . . . . . . . . . . . . . . . . . . . . . . .58SNMP security issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Related information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60Customer training programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Appendix A: Specifying an email subject line . . . . . . . . . . . . . . . . . . . . .61Appendix B: Events and event IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

3 of 106Version 5.5Configuring Celerra Events and Notifications

Introduction to events and notificationsThe EMC® Celerra® Network Server generates events to record errors, commands, and other information you may need to know. You can configure your 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 technical module is part of the Celerra Network Server information set and is intended for the system administrators responsible for configuring and maintaining your file storage and network retrieval infrastructure. This section includes some terminology and restrictions that should be familiar to you before you configure or modify network settings.

TerminologyThis section defines terms important to understanding events and notification capabilities on the Celerra Network Server. The 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. A specialized notification allows the administrator to perform corrective action.

event: A 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: A 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: The process by which specified events exceeding a severity threshold trigger an action or notification. See notification.

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

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

monitor alert: In the context of Celerra Monitor, a message sent to the system log generated as a result of a predefined alert condition. Optionally, monitor alerts can be emailed to specified users and SNMP traps can be sent to specified hosts.

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

notification: An action triggered by an event, such as calling home, sending an email message or SNMP trap, or running a script.

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

Configuring Celerra Events and Notifications4 of 106 Version 5.5

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

SNMP agent: A 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: The name for the SNMP transaction with a remote system. This is used as a password to control access to the SNMP MIB.

SNMP trap: An 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.

CautionsThis section lists the cautions for using this feature on the Celerra Network Server. If any of this information is unclear, contact an EMC Customer Support Representative for assistance.

!CAUTION!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 your 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 may be severe enough to cause an error or disrupt user access. 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 your 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 may require action by an administrator. For example, an event is generated when any of the following occur:

◆ A Data Mover reboots.

◆ 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 contains the default event definitions and also specifies the default notifications (actions) that occur as a result of the events. "Customizing notifications" on page 31 provides information about how you can set up your own customized events and notifications.

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.

The facilities that generate events can change from release to release. Table 1 lists the facilities that generate events in the current release.

Table 1 Celerra event facilities

Facility name Facility ID Description

ACLUPD 101 ACL database events.

ADMIN 24 Data Mover administration/configuration events.

BoxMonitor 131 Hardware events. Monitors status of operating system on each Data Mover/blade and logs Data Mover messages. Also monitors enclosure hardware for NSX systems. See also the CHAMIIENCMON facility (Facility ID 86).


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

CFS 27 Common File System events. Provides common functionality for file systems. Used for file system full.

CHAMIIENCMON 86 Monitors the hardware events of NS series Data Movers and their enclosures.

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

DHSM 96 FileMover events.

DPSVC 111 Data Protection service events for iSCSI Replicator.

DRIVERS 36 Device driver events.

FCP 102 Low-level Fibre Channel SCSI driver events.

FSTOOLS 40 File System tool events.

JServer 135 JServer (Java server) events

LIB 46 Data Mover library events. Used for duplicate events.

LocalHardwareMonitor 139 Local Control Station hardware events.

LogCollect 141 Automatic log collection and transfer events.

MasterControl 129 Control Station software events. Manages several services on the Control Station.

MGFS 75 CDMS migration file system event or FileMover events.

NASDB 137 NAS database events.

NaviEventMonitor 138 CLARiiON® events.

NDMP 51 Network Data Management Protocol events.

Table 1 Celerra event facilities (continued)



Event numbersEach event associated with a facility is assigned a unique number within that facility. As an example, Table 2 lists the events generated by the UFS facility.

NFS 52 Network File System events.

REP 108 Replication events for iSCSI Replicator.

RCPD 83 Remote Copy Protocol Daemon events for iSCSI Replicator.

SECURITY 54 Security events.

SNAPSURE_SCHED 91 SnapSure scheduling events.

STORAGE 58 High-level SCSI driver events.

SVFS 70 SnapSure events.

UFS 64 File system events. The physical file system, which is dependent on the disk structure. Used for quotas.

UPSMonitor 140 Uninterruptible Power Supply monitor for NSX systems.

USRMAP 93 Usermapper events.

VC 81 Virus-checking events.

VMCAST 84 Volume multicast events. Used for Replicator.

VRPL 77 Volume Replicator events.

XLT 72 Translation (XLT) file events. Detects XLT file corruptions, and recovers those files automatically from the Control Station. An event is generated and sent to the Control Station, which in turn records the event in the system log and triggers a call home event.

Table 2 UFS event numbers

Number Description

0 I18N OK

1 I18N - Out of Inodes

2 I18N - Cannot balloc

Table 1 Celerra event facilities (continued)



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 severity levels for events are defined in the configuration file /nas/sys/nas_eventlog.cfg. Table 3 on page 9 provides a list of event severity levels and shows the relationship between these severity levels and those defined by Celerra Manager.

Note: 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.

3 I18N - Recovery failed, file system not mounted

4 Soft quota (warning limit) crossed

5 Hard quota limit reached/exceeded

6 Directory translation cannot progress

7 Skip auto fsck for corrupted file system at mount

8 Gid map file is not present

9 Gid map file is full

10 Directory translate cannot progress

11 Crossed the root filesystem inode threshold

12 Crossed the filesystem inode threshold

13 Dropped below the root filesystem inode threshold

14 Dropped below the filesystem inode threshold

15 Filesystem size incorrect in superblock

Table 3 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

Table 2 UFS event numbers (continued)

Number 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 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 using the Celerra command line interface. Event logs can also be viewed, sorted, and filtered using the Celerra Manager. You can find detailed information about the Celerra Manager in its online help.

Notification configuration filesThe Celerra Network Server is configured with a set of default notifications that includes 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.

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 Event severity levels (continued)

Severitylevel Name Description Celerra Manager

designation

../SystemOperations/index.htm


You can create your own notification definitions by creating new configuration files in the /nas/site directory and loading them using the CLI. You also can create mail, log, and trap notifications using the Celerra Manager. 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 your 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.

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, followed by the unique facility ID for the facility and an event severity level with the following format:facilitypolicy <facility_ID>, <severity_level>

For example, facilitypolicy 64, 3 specifies an entry for events from the UFS facility (facility ID 64) with a severity level of Error (3) or worse. 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 maximum severity level specified in the files is used. For example, if the UFS has a severity level of 7 in /nas/sys/nas_eventlog.cfg file and a severity level of 2 in cwm_notify.cfg, the event log daemon uses the maximum severity level of 7.

◆ A line starting with the keyword disposition, followed by a range of event IDs within the facility, 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_start:range_end>] [<directive>], <action>

Where:

<range_start:range_end> = optional range of event IDs

<directive> = an 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> = logfile, mail, trap, callhome, exec, udprpc, terminate

Examples:

The following event configuration triggers a call home on every tenth event occurrence:disposition range=5-5 threshold=10, callhome immediate

The following event configuration triggers a call home on the first event occurrence and every tenth event following the first occurrence:disposition range=5-5 threshold=1 rearm=10, callhome immediate

The following event configuration triggers a call home on the first event occurrence and every tenth event following the first occurrence. However, if 3600 seconds (one hour) pass without event activity, the threshold and rearm counters are reset and await the next event to trigger a call home.disposition range=5-5 threshold=1 rearm=10 resetafter=3600, callhome immediate

The following example specifies the system should generate the specified SNMP trap (2) for events with event IDs in the range of 3 to 7. SNMP trap numbers are unique for each facility and are specified in the Celerra MIB.

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 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 64, 7disposition severity=1-2, mail "user@domain"

Events can have more than one action. For example, a specific event could have logfile, CallHome, and trap actions.


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

"Creating a configuration file" on page 31 describes the procedure for configuring a notification file.

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/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 reboot, or a network interface card failure. The manager may 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 string The 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 your Celerra Network Server.

Note: Use only alphanumeric characters to specify the community name.

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.

SNMP traps on Celerra Network ServerYou can set up an SNMP trap for any Celerra event. In the default configuration, all events that generate a CallHome action also generate an SNMP trap. The default configuration may change from release to release.


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 notificationsThis section describes the Celerra Network Server software, hardware, network, and storage configurations required for using events and notifications as described in this technical module.

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

Table 4 Events and notifications system requirements

Software Celerra Network Server version 5.5 or later. For management of custom notifications through Celerra Manager, you must have the Celerra Manager - Advanced Edition license. This license is also required if you want to run Celerra Monitor.

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 technical module describes how to configure Celerra events and notifications using the command line interface (CLI). You can also perform many of these tasks using one of the Celerra management applications:

◆ Celerra Manager - Basic Edition

◆ Celerra Manager - Advanced Edition

◆ Celerra Monitor

◆ Microsoft Management Console (MMC) snap-ins

◆ Active Directory Users and Computers (ADUC) extensions

For additional information about managing your Celerra, refer to:

◆ Learning about Celerra

◆ Celerra Manager Online Help

◆ Monitoring Celerra

◆ Application’s online help system on the 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 the Celerra Monitor to configure the following notification actions:

◆ CallHome

◆ Execution of a procedure

◆ Generation of an RPC message

◆ Termination of processing of event

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

../../mergedprojects/Concepts/Celerra_Product_Line.htm

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

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

../InstallationManagement/index.htm


Roadmap for events and notificationsThis section lists the tasks required for configuring events and notifications:

1. "Configuring DNS on the Control Station" on page 18

2. "Checking if email is working properly before configuring notifications" on page 19

3. "Gathering required information" on page 21

4. "Configuring SNMP trap notifications" on page 26

5. "Customizing notifications" on page 31


Configuring DNS on the Control StationUsing DNS services makes it 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.com>search localdomainnameserver <a.b.c.e>nameserver <a.b.c.f>

Where:<xxx.emc.com > = your DNS domain name<a.b.c.e> = IP address of a DNS name server on your network<a.b.c.f> = IP address of a secondary DNS name server on your networkExample:domain nasdocs.emc.comsearch localdomainnameserver 192.168.152.184nameserver 192.168.152.185


Checking if email is working properly before configuring notificationsThis procedure uses a combination of three 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>

Note: Be sure to enclose hostname in single, backward quotes; otherwise, the command fails. The man pages for the 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 which is passed to the requested commands (echo, and mail)<subject> = email subject<recipient 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


Note

In the resulting output from the command, the following line (bold in above sample output), 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 events and notifications" on page 57 provides more information on what to do if email notifications are not working as expected.


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

1. "Determining facilities that generate events" on page 22

2. "Determining events associated with a facility" on page 23

3. "Determining a list of all possible actions" on page 24

4. "Determining which events trigger an action" on page 25


Task 1: Determining facilities that generate events

Action

To view the current list all of the facilities that generate events, type:$ nas_event -list -f -info

Output

id facility142 Checkup141 LogCollect140 UPSMonitor139 LocalHardwareMonitor138 NaviEventMonitor137 NASDB135 JServer131 BoxMonitor129 MasterControl111 DPSVC108 REP102 FCP101 ACLUPD96 DHSM93 USRMAP91 SNAPSURE_SCHED86 CHAMIIENCMON84 VMCAST83 RCPD81 VC77 VRPL75 MGFS72 XLT70 SVFS64 UFS58 STORAGE54 SECURITY52 NFS51 NDMP46 LIB40 FSTOOLS36 DRIVERS27 CFS26 CAM24 ADMIN


Task 2: Determining events associated with a facilityUse these procedures to list events associated with an event facility.

Listing events associated with an event facility — example 1


Action

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

Where:<facility> = case-sensitive facility nameExample:To list the events associated with the UFS facility, type:$ nas_event -list -f UFS

Output

id description0 I18N OK1 I18N - Out of Inodes2 I18N - Cannot balloc3 I18N - Recovery failed, filesystem not mounted4 Soft quota (warning limit) crossed5 Hard quota limit reached/exceeded6 Directory translate cannot progress7 Skip auto fsck for corrupted filesystem at mount8 Gid map file is not present9 Gid map file is full10 Directory translate cannot progress11 Crossed the root filesystem inode threshold12 Crossed the filesystem inode threshold13 Dropped below the root filesystem inode threshold14 Dropped below the filesystem inode threshold15 Filesystem size incorrect in superblock

Action

To list the events associated with the SVFS facility, type:$ nas_event -list -f SVFS

Output

id description1 High water mark of SavVol reached2 Checkpoint inactive3 Source filesystem restore done4 Restore is in progress5 Checkpoint conversion is paused - savvol is full



Task 3: Determining a list of all possible actions

Action

To list the events associated with the VC facility, type:$ nas_event -list -f VC

Output

id description0 Normal state1 High water mark reached2 Low water mark reached3 No Virus Checker server available4 No Virus Checker server; stop CIFS5 No Virus Checker server; stop virus checking6 File not checked7 Virus Checker server online8 Virus Checker server offline9 Filesystem scan started10 Filesystem scan terminated11 Filesystem scan aborted12 File has been deleted by the Virus Checker engine13 File has been renamed by the Virus Checker engine14 File has been modified (cleaned) by the Virus Checker engine15 Virus Checker stopped16 Virus Checker started

Action

To view a list of all possible actions you can take, use this command syntax:$ nas_event -list -a -info

Output

actionudprpcexecterminatetrapcallhomemaillogfile


Task 4: Determining which events trigger an action

After gathering required informationA CallHome action occurs when an event occurs or a threshold is crossed. When this happens, the Control Station automatically generates a call to EMC. For example, when a Data Mover’s root file system becomes almost full, by default the UFS facility generates the Crossed the root filesystem inode threshold event that triggers a call home to EMC.

Action

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

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

Output

facility id descriptionCAM 7 CAM I/O errorCFS 4 Crossed the root filesystem size thresholdFSTOOLS 0 FSCK StartedMasterControl 6 Unexpected daemon exit . . .UFS 7 Skip auto fsck for corrupted filesystem at mountUFS 11 Crossed the root filesystem inode threshold


Configuring SNMP trap notificationsConfiguring SNMP traps for notifications consists of some or all of the following tasks:

1. "Modifying the Celerra MIB file for SNMP traps" on page 26

2. "Configuring SNMP traps" on page 27

3. "Sending a test SNMP trap" on page 27

4. "Receiving a test SNMP trap" on page 28

5. "Configuring SNMP on Data Movers" on page 30

6. "Verifying an SNMP configuration" on page 30

Task 1: Modifying 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.

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 your notification configuration file. Some trap numbers are reserved, so be sure to check the Trap Definition section of the Celerra MIB, /nas/sys/emccelerra.mib, before assigning a trap number.

Note: Be sure 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 your modified MIB in another location because it is overwritten when the system is upgraded.

On HP OpenView, load the MIB using Options > Load/Unload MIBs:SNMP.

2. Configure the MIB on the SNMP Manager.


Task 2: Configuring 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.

After configuring SNMP trapsModifications to the file are maintained when the Celerra Network Server is upgraded.

Task 3: Sending a test SNMP trapYou can use nas_snmptrap and snmptrapd -P on the Control Station to send a test SNMP trap.

Step Action

1. 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 manager

Note: A trap configuration file can contain multiple entries, one per line.

Example:#snmp trap configuration filesnmpmanager 128.154.11.20 ; communityname xyz_communitysnmpmanager host1 ; communityname xyz_community

Note: The 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 reboot the system.

Step Action

1. Log in to the Control Station.

2. Change to root using the su command.


Task 4: Receiving a test SNMP trapYou can receive a test SNMP trap by configuring the Control Station as the target.

3. Make sure the Control Station is listed in your trap.cfg file. Example:snmpmanager localhost ; communityname public

4. Start the SNMP trap daemon on the Control Station by typing:# /usr/sbin/snmptrapd -P -o /nas/site/my_eventlog_messages &

The & starts the daemon in the background and allows you to continue entering commands. Messages are logged to the my_eventlog_messages file.

5. From root, send a trap using the following command 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>"

Note: Up to 255 characters are supported in <description> length.

Where:<config_file_path> = path of the trap configuration file/nas/sys/emccelerra.mib = Celerra MIB file <trap_number> = unique trap number for the event<facility_id> = ID number of the facility generating the event<event_id> = event ID number<severity_level> = severity level of the event<description> = description of the trapExample:# /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 "

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 your site manager for what to use in place of public.

Step Action (continued)


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 file

Note: Save a copy of your modified MIB in another location because it is overwritten when the system is upgraded.


3. Configure MIB on the SNMP Manager.

Output

The following shows the output from the Virus Checker facility when CAVA service goes offline

2004-07-09 15:58:07 LNSGC224 [192.168.101.224] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 7 days, 12:27:17.86enterprises.1139.2.1.1.1 = 81enterprises.1139.2.1.1.2 = 8enterprises.1139.2.1.1.3 = 3enterprises.1139.2.1.1.4 = "Jul 9 15:58:07 2004 VC:3:8 Slot 3: 1089402897: Server 192.168.101.107 version 0 is OFFLINE "2004-07-09 15:58:07 LNSGC224 [192.168.101.224] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 7 days, 12:27:17.90enterprises.1139.2.1.1.1 = 81enterprises.1139.2.1.1.2 = 3enterprises.1139.2.1.1.3 = 3enterprises.1139.2.1.1.4 = "Jul 9 15:58:07 2004 VC:3:3 Slot 3: 1089402897: No Virus Checker Server available "2004-07-09 15:58:17 LNSGC224 [192.168.101.224] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 7 days, 12:27:27.78enterprises.1139.2.1.1.1 = 81enterprises.1139.2.1.1.2 = 8enterprises.1139.2.1.1.3 = 3enterprises.1139.2.1.1.4 = "Jul 9 15:58:17 2004 VC:3:8 Slot 2: 1089402908: Server 192.168.101.107 version 0 is OFFLINE "2004-07-09 15:58:17 LNSGC224 [192.168.101.224] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 7 days, 12:27:27.81enterprises.1139.2.1.1.1 = 81enterprises.1139.2.1.1.2 = 3enterprises.1139.2.1.1.3 = 3enterprises.1139.2.1.1.4 = "Jul 9 15:58:17 2004 VC:3:3 Slot 2: 1089402908: No Virus Checker Server available "

Step Action


Task 5: Configuring SNMP on Data MoversThe server_snmp command manipulates SNMP configuration values of the server agent for the specified Data Mover.

Task 6: Verifying an SNMP configuration

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

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

Output

server_2 : done

Action

To verify if a system <hostname> has been configured with the community name of <community>, use the following syntax: $ snmpwalk -Cc <hostname> <community>

Note: Use the Linux snmpwalk command to read all values from the SNMP agent specified by a hostname or IP address. The man page for the snmpwalk command on the Control Station provides more information.

Example:To verify if server_2 has been configured with a community name xyz_community, type:$ snmpwalk -Cc server_2 xyz_community

Output

The following is the initial part of the output from running the snmpwalk command:system.sysDescr.0 = Product: EMC Celerra File Server Project: SNAS Version:T5.5.9.2003system.sysObjectID.0 = OID: enterprises.1139system.sysUpTime.0 = Timeticks: (95400) 0:15:54.00system.sysContact.0 = nasadminsystem.sysName.0 = server_2system.sysLocation.0 = heresystem.sysServices.0 = 72interfaces.ifNumber.0 = 7interfaces.ifTable.ifEntry.ifIndex.1 = 1interfaces.ifTable.ifEntry.ifIndex.2 = 2 . . .

../CommandReference/index.htm


Customizing notificationsTo customize notifications for your needs, create the configuration file and load it on the Celerra Network Server. Customizing consists of the following tasks.

1. "Creating a configuration file" on page 31

2. "Loading a configuration file" on page 32

3. "Verifying the configuration file loaded" on page 33

Task 1: Creating a configuration fileYou can create and modify configuration files to fit your specific Celerra Network Server environment.

Step Action


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 you want for your 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 your 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 your customized configuration file

5. If you copied /nas/sys/nas_eventlog.cfg as the basis for your 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.


After creating a configuration fileWhen you set up a new notification, make sure that you test it and that email is reaching the intended recipient.

Task 2: Loading a configuration fileAfter creating your customized configuration file, you must load the file for the new notifications to take effect.

6. Add the following statements to the notification file to associate events with the actions you want.# UFS#facilitypolicy 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" disposition range=4-5 threshold=1 rearm=10, callhome immediate

Where:facilitypolicy 64 = events from the UFS facility (facility ID 64).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 used.logfile = entry added to the /nas/log/sys_log file for events 0 through 7.mail = email message sent for events 4 through 7. trap = 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 trap. threshold=1 and rearm=10 = call home generated on the first event occurrence and every tenth event following the first occurrence.callhome = immediate call home for events 4 through 5.Table 5 on page 55 provides a complete list of actions. "Configuring SNMP traps" on page 27 provides more information on trap configuration files.

7. Save the file, and then exit.

Note: "How to create a notification configuration file" on page 11 provides more information about how to create a notification configuration file.

Step Action


Note: 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


Task 3: Verifying the configuration file loaded

After verifying the configuration file loadedYou might need to modify the configuration of your SNMP management application before it can use these changes. "Configuring SNMP trap notifications" on page 26 provides more information.

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

Where:<customized_file> = full pathname of your 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 your customized configuration files in the /nas/sys directory or they will be overwritten when the system is upgraded.

Action

To verify that your customized configuration file is loaded, type:$ 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

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 34

◆ "When the SnapSure SavVol usage reaches its high water mark" on page 37

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

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

◆ "When there are ACL updates" on page 51

When file system usage exceeds certain limitsYou can configure your 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.

Before configuring Celerra to generate a notification when file system usage exceeds certain limits Monitoring the percentage full is useful because file system performance can degrade as its used space approaches 100.

(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.

Note: 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


Configuring Celerra to generate a notification when file system usage exceeds certain limits

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.com>search localdomainnameserver <a.b.c.e>nameserver <a.b.c.f>

Note: Most of the time, DNS configuration is done at the time of Celerra Network Server implementation.

Where:<xxx.emc.com> = your DNS domain name<a.b.c.e> = IP address of a DNS name server on your network<a.b.c.f> = IP address of a secondary DNS name server on your network

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

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 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 10"

Where:facilitypolicy 27 = CFS facility.7 = severity-level threshold (captures events of 7 or lower).disposition range=1-1 = events 1 through 1, which equates to the CFS event "Crossed the fs (file system) size threshold."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 your company.10 = arbitrary, yet unique, trap number you associate with the event in the Celerra MIB (code shown in a later step).

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

Task 2: "Determining events associated with a facility" on page 23 provides information about determining which events are associated with which facilities.


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>

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 your site manager for what to use in place of 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."::=10

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




7. Make sure 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 localhost<a.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 your domain that includes the mail server. Substitute your Control Station and domain information for the ones in the example.

8. Load the new notification configuration file using the following command.

Note: Be sure to use the full path name of the configuration file in the -Load 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


After configuring Celerra to generate a notification when file system usage exceeds certain limitsNow, 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.

Note: The /usr/sbin/snmptrapd daemon must be started on the Control Station to display SNMP trap messages. "Sending a test SNMP trap" on page 27 provides more information.

The trap message on the SNMP Manager looks like this.

The following is an example of the email notification.

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

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

9. Verify the new notifications (email and traps) have been accepted using the following commands:$ nas_event -l -a mail$ nas_event -l -a trap

Where:-l = list-a = actionOutput:facility id descriptionCFS 1 Crossed the fs size threshold

Output

Jun 18 15:42:50 2003 CFS:4:1 Slot 3: 1009511393: 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

From: root@<server>Subject: EMCServer csA121, Facility - CFS, Severity - 4Jun 18 15:42:50 2003 CFS:4:1 Slot 3: 1009511393: filesystem size threshold (90%) crossed (fs /ufs1)

Step Action


Before configuring Celerra to generate a notification when SnapSure SavVol usage reaches its high water markBy default, SnapSure audits the SavVol automatically and writes a message to the system log when a user-set (0% to 100%) 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.

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

Step Action






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 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 70 = SVFS facility.7 = severity-level threshold (captures events of 7 or lower). disposition range=1-1 = events 1 through 1, which equates to the SVFS event “high water mark of SavVol reached.”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 your company.14 = arbitrary, yet unique, trap number you associate with the event in the Celerra MIB (code shown in a later step).




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 your site manager for what to use in place of public.

Step Action


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







8. Load the new notification configuration file using the following command:





Step Action


After configuring Celerra to generate a notification when SnapSure SavVol usage reaches its high water markNow, 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 trap message on the SNMP Manager looks like this.

The following is an example of the email notification.

9. Verify the new notifications (email and traps) have been accepted using the following commands:$ nas_event -l -a mail$ nas_event -l -a trap

Where:-l = list-a = actionOutput:For nas_event -l -a mail, you see the following in the display:facility id descriptionSVFS 1 high water mark of SavVol reached

For nas_event -l -a trap, you see the following in the display:facility id descriptionSVFS 1 high water mark of SavVol reached

Output

2004-06-24 15:17:34 eng168102 [192.168.168.102] TRAP, SNMP v1, community public. enterprises.1139.2 Enterprise Specific Trap (14) Uptime: 3 days, 2:21:10.04 enterprises.1139.2.1.1.1 = 70 enterprises.1139.2.1.1.2 = 1 enterprises.1139.2.1.1.3 = 0 enterprises.1139.2.1.1.4 = "Jun 24 15:17:34 2004 SVFS:0:1 Slot 2: 1088147805: FSID:25 SavVol:121 Full(hwm) reached (t:806574158145328) "

Note

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

Output

From: root <[email protected]>To: [email protected]: Server eng168102, Facility - SVFS, Severity - 0Jun 24 15:17:34 2004 SVFS:0:1 Slot 2: 1088147805: FSID:25 SavVol:121 Full(hwm) reached (t:806574158145328)

Step Action


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

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


Configuring 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 81,15 disposition range=0-16, mail "[email protected]" disposition range=0-16, trap "/nas/site/trap.cfg 11"

Where:facilitypolicy 81 = VC facility.15 = severity-level threshold (captures events of 15 or lower).disposition range=0-16 = events 0 through 16, which equates to all VC [email protected] = email address that receives email notification. Replace these with one or more email addresses at your company.11 = arbitrary, yet unique, trap number you associate with the event in the Celerra MIB (code shown in a later step).

Note: If you are running a Celerra Network Server version 5.1 or earlier, you must define the subject line for your email notifications when editing your event log configuration file. "Appendix A: Specifying an email subject line" on page 61 provides an example about how to do this.



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 your site manager for what to use in place of public.

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.




Step Action


After configuring Celerra to generate a notification for Virus Checker eventsNow, when the CAVA service is stopped and started, the Control Station generates SNMP trap messages and email.








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

Where:-l = list-a = actionOutput:facility id descriptionVC 0 Normal stateVC 1 High water mark reachedVC 2 Low water mark reachedVC 3 No Virus Checker server availableVC 4 No Virus Checker server; stop CIFSVC 5 No Virus Checker server; stop virus checkingVC 6 File not checkedVC 7 Virus Checker server onlineVC 8 Virus Checker server offlineVC 9 Filesystem scan startedVC 10 Filesystem scan terminatedVC 11 Filesystem scan abortedVC 12 File has been deleted by the Virus Checker engineVC 13 File has been renamed by the Virus Checker engineVC 14 File has been modified (cleaned) by the Virus Checker engineVC 15 Virus Checker stoppedVC 16 Virus Checker started

Step Action



When the Virus Checker server is unavailable, the following trap messages are generated.

When CAVA service is started on the Virus Checker server, the following trap messages are generated.

Output

2004-07-09 15:58:07 LNSGC224 [192.168.101.224] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 7 days, 12:27:17.86enterprises.1139.2.1.1.1 = 81enterprises.1139.2.1.1.2 = 8enterprises.1139.2.1.1.3 = 3enterprises.1139.2.1.1.4 = "Jul 9 15:58:07 2004 VC:3:8 Slot 3: 1089402897: Server 192.168.101.107 version 0 is OFFLINE "2004-07-09 15:58:07 LNSGC224 [192.168.101.224] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 7 days, 12:27:17.90enterprises.1139.2.1.1.1 = 81enterprises.1139.2.1.1.2 = 3enterprises.1139.2.1.1.3 = 3enterprises.1139.2.1.1.4 = "Jul 9 15:58:07 2004 VC:3:3 Slot 3: 1089402897: No Virus Checker Server available "2004-07-09 15:58:17 LNSGC224 [192.168.101.224] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 7 days, 12:27:27.78enterprises.1139.2.1.1.1 = 81enterprises.1139.2.1.1.2 = 8enterprises.1139.2.1.1.3 = 3enterprises.1139.2.1.1.4 = "Jul 9 15:58:17 2004 VC:3:8 Slot 2: 1089402908: Server 192.168.101.107 version 0 is OFFLINE "2004-07-09 15:58:17 LNSGC224 [192.168.101.224] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 7 days, 12:27:27.81enterprises.1139.2.1.1.1 = 81enterprises.1139.2.1.1.2 = 3enterprises.1139.2.1.1.3 = 3enterprises.1139.2.1.1.4 = "Jul 9 15:58:17 2004 VC:3:3 Slot 2: 1089402908: No Virus Checker Server available "

Output

2004-07-09 15:59:17 LNSGC224 [192.168.101.224] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 7 days, 12:28:27.59enterprises.1139.2.1.1.1 = 81enterprises.1139.2.1.1.2 = 7enterprises.1139.2.1.1.3 = 4enterprises.1139.2.1.1.4 = "Jul 9 15:59:17 2004 VC:4:7 Slot 2: 1089402969: Server 192.168.101.107 version 2 is ONLINE "2004-07-09 16:00:07 LNSGC224 [192.168.101.224] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (11) Uptime: 7 days, 12:29:17.82enterprises.1139.2.1.1.1 = 81enterprises.1139.2.1.1.2 = 7enterprises.1139.2.1.1.3 = 4enterprises.1139.2.1.1.4 = "Jul 9 16:00:07 2004 VC:4:7 Slot 3: 1089403017: Server 192.168.101.107 version 2 is ONLINE "


Here’s an example of an email notification when there is no Virus Checker server available.

Here’s an example of an email notification after CAVA service is started on the Virus Checker server.

When a hard or soft quota is exceededYou can configure your 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.

Configuring Celerra to generate a notification when a quota is exceeded

Output

Jul 9 15:58:17 2004 VC:3:8 Slot 2: 1089402908: Server 192.168.101.107 version 0 is OFFLINE

Output

Jul 9 15:59:17 2004 VC:4:7 Slot 2: 1089402969: Server 192.168.101.107 version 2 is ONLINE

Step Action






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

Where:facilitypolicy 64 = UFS facility.7 = severity-level threshold (captures events of 7 or lower).disposition range=4-4 = events 4 through 4, which equates to the UFS event "Soft quota (warning limit) crossed."[email protected] = email addresses that receive email notification. Replace these with one or more email addresses at your company.20 = arbitrary, yet unique, trap number you associate with the event in the Celerra MIB (code shown in a later step).disposition range=5-5 = events 5 through 5, which equates to the UFS event "Hard limit reached/exceeded."





Step Action


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







8. Load the new notification configuration file using the following command.





Step Action


After configuring Celerra to generate a notification when a quota is exceededWhen a hard or soft quota for users, groups, or trees is exceeded, the Control Station generates SNMP trap messages and email.


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

Where:-l = list-a = actionOutput:facility id descriptionUFS 4 Soft quota (warning limit) crossedUFS 5 Hard limit reached/exceeded

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.

Step Action


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

Now, when the file system hard or soft quota is exceeded, notifications similar to the following messages are sent.

Output

[root@lnsga140 nasadmin]# 2004-07-15 14:38:28 lnsga140.pag.emc.com [172.24.100.140] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (20) Uptime: 13 days, 11:30:24.14enterprises.1139.2.1.1.1 = 64 enterprises.1139.2.1.1.2 = 4 enterprises.1139.2.1.1.3 = 4 enterprises.1139.2.1.1.4 = "Jul 15 14:38:28 2004 UFS:4:4 Slot 2: 1089917399: [vdm2-1] Block soft quota crossed (fs /root_vdm_1/ufs12, uid 32783) "2004-07-15 14:38:38 lnsga140.pag.emc.com [172.24.100.140] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (20) Uptime: 13 days, 11:30:34.14enterprises.1139.2.1.1.1 = 64 enterprises.1139.2.1.1.2 = 5 enterprises.1139.2.1.1.3 = 3 enterprises.1139.2.1.1.4 = "Jul 15 14:38:38 2004 UFS:3:5 Slot 2: 1089917404: [vdm2-1] Block hard quota reached/exceeded (fs /root_vdm_1/ufs12, uid 32783) "

Output

From: root@<server>Subject: EMCServer csA121, Facility - UFS, Severity - 3

Jun 11 18:04:16 2003 UFS:3:5 Slot 2: 1055369048: Block hard quota reached/exceeded (fs /ufs2, uid 101)

From: root@<server>Subject: EMCServer csA121, Facility - UFS, Severity - 4

Aug 24 09:15:55 2005 UFS:4:4 Slot 4: 1122896509: Block soft quota crossed (fs /ufs2, uid 201)

Aug 24 09:15:55 2005 UFS:4:4 Slot 4: 1122896509: Block soft quota crossed (fs /ufs2, treeid 1)

Aug 24 09:15:55 2005 UFS:4:4 Slot 4: 1122896509: Block hard quota reached/exceeded (fs /ufs2, gid 201

Note

The 5 in UFS:3:5 indicates the UFS event "Block hard quota reached/exceeded" and 4 in UFS:4: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.


When there are ACL updatesYou can configure your Celerra Network Server to generate SNMP traps and an email notification to a Windows or UNIX administrator when there are ACL updates.


Configuring Celerra to generate a notification for ACL updates

Step Action





3. Use a text editor to add the following statements to my_eventlog.cfg:# ACL Update Events# email and trap notification for any ACL update event# facilitypolicy 101,15 disposition range=0-15, mail "[email protected]" disposition range=0-15, trap "/nas/site/trap.cfg 21"

Where:facilitypolicy 101 = ACLUPD facility.15 = severity-level threshold (captures events of 15 or lower). disposition range=0-15 = events 0 through 15, which equates to all ACLUPD [email protected] = email address that receive email notification. Replace this with one or more email addresses at your company.21 = arbitrary, yet unique, trap number you associate with the event in the Celerra MIB (code shown in a later step).






5. Modify the Celerra MIB, found at /nas/sys/emccelerra.mib, to include the following lines:celACLUPD TRAP-TYPEENTERPRISE emcCelerraVARIABLES {celEvent}DESCRIPTION "Trap message will be sent in the event of an ACLUPD update."::=21






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






Step Action


After configuring Celerra to generate a notification for ACL updatesWhen ACLs are updated on the file system, the Control Station generates SNMP trap messages and email.


When ACLs are updated, the following trap messages are generated.

9. Verify the new notification email has been accepted using the following command:$ nas_event -l -a mail$ nas_event -l -a trap

Where:-l = list-a = actionOutput:facility id descriptionACLUPD 0 ACLUPD OKACLUPD 1 ResetAll command startACLUPD 2 ResetAll command endACLUPD 3 CheckAll command startACLUPD 4 CheckAll command endACLUPD 5 SetSd command startACLUPD 6 SetSd command endACLUPD 7 MigDom command startACLUPD 8 MigDom command endACLUPD 9 HistorySid command startACLUPD 10 HistorySid command endACLUPD 11 PrintStats command startACLUPD 12 PrintStats command endACLUPD 13 DumpAll command startACLUPD 14 DumpAll command endACLUPD 15 Error occurred during a command

Output

2004-07-15 14:51:02 lnsga140.pag.emc.com [172.24.100.140] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (21) Uptime: 13 days, 11:42:58.30enterprises.1139.2.1.1.1 = 101 enterprises.1139.2.1.1.2 = 7 enterprises.1139.2.1.1.3 = 4 enterprises.1139.2.1.1.4 = "Jul 15 14:51:02 2004 ACLUPD:4:7 Slot 2: 1089918152: aclupd thread 1 with command acl database migdom on 260 launched "2004-07-15 14:51:02 lnsga140.pag.emc.com [172.24.100.140] (via localhost.localdomain [127.0.0.1]) TRAP, SNMP v1, community public.enterprises.1139.2 Enterprise Specific Trap (21) Uptime: 13 days, 11:42:58.34enterprises.1139.2.1.1.1 = 101 enterprises.1139.2.1.1.2 = 7 enterprises.1139.2.1.1.3 = 4 enterprises.1139.2.1.1.4 = "Jul 15 14:51:02 2004 ACLUPD:4:7 Slot 2: 1089918152: acl database migdom on 260 ended successfully "

Step Action


Now, when ACLs are updated on the file system with a command as follows, email messages are generated:

$ server_cifs server_2 -Migrate ufs5 -acl NT-DOMAIN:if=ana0 migration:if=ana0

The following is an example of the email notification at the start of the ACL update.

The following is an example of the email notification at the completion of the ACL update.

Output

Jun 17 13:40:21 2004 ACLUPD:4:7 Slot 2: 1087494061: aclupd thread 4 with command acl database migdom on 246 launched

Output

Jun 17 14:15:14 2004 ACLUPD:4:7 Slot 2: 1087496159: acl database migdom on 246 ended successfully


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

Table 5 Celerra event notification actions

Action Arguments Description

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

mail <address> Sends email to the specified email address.Use a separate mail line for each additional email address.

Note: You can configure email using the Linux tool netconf on the Control Station. The Linux man pages provide more information.

trap <config_file> <trap_number> Sends SNMP trap number <trap_number> to the SNMP manager as defined in the <config_file> configuration file.

Note: 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 immediately

Note: CallHome is configured when your system is installed. You can update the configuration using the Celerra Manager.

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 (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 host name. 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 troubleshooting can be performed.

Table 5 Celerra event notification actions (continued)

Action Arguments Description


Troubleshooting events and notificationsAs 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 revisions 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, please contact your EMC representative.

Technical supportFor technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC Sales Representative for details about obtaining a valid support agreement or to answer any questions about your account.

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 your 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 address. You can use the mail log files in the /var/log directory to troubleshoot Sendmail problems.

Step Action

1. Log in to the Control Station as root. If you are already logged in as nasadmin, you can change to user root by typing:$ su -

2. At the command prompt, type:# mail

This displays a list of messages addressed to root.


../ProblemResolutionRoadmap/index.htm



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

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

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.

Also check the quota event notification settings to make sure that notification is enabled for the event. 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:

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 are already logged in as nasadmin, you can change to user root by typing:$ su -

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

Step Action


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.

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.

◆ Make sure the host is set to accept SNMP packets from specific hosts.

Verifying 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. "Configuring SNMP traps" on page 27 provide more information on trap.cfg.

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

SNMP traps not working after Control Station reboot 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 reboot or a power outage, the snmpd daemon may or may not start on a reboot depending on if it is setup by /sbin/chkconfig to start. The snmptrapd daemon is not set up under the /sbin/chkconfig function, so it does not restart after a reboot unless you write a run control script to start it or start it manually.

Note: For NSX 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 -P -o my_eventlog_messages &

The command starts the snmptrapd daemon as background process.

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


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

◆ Managing Celerra Volumes and File Systems with Automatic Volume Management

◆ Managing Celerra Volumes and File Systems Manually

◆ Celerra Network Server Command Reference Manual

◆ Celerra Network Server Parameters Guide

◆ Celerra Network Server System Operations

◆ Online Celerra man pages

The Celerra Network Server Documentation CD, supplied with your Celerra Network Server and also available on Powerlink, provides general information on other EMC Celerra publications.

For more information on SNMP, refer to your SNMP manager documentation.

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, refer to Powerlink, our customer and partner website.

../CommandReference/index.htm

../Parameters/index.htm

../AVM/index.htm


../SystemOperations/index.htm




Appendix A: Specifying an email subject lineIf you are running Celerra Network Server version 5.1 or earlier, you must define the subject line for your email notifications when editing your event log configuration file. Use the -s option as shown in the following example to specify the subject for your email notification.

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 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 Stationfacility_name = facilityseverity = severity level<recipient email address> = recipient’s email address

Note: Be sure to join all parts of the subject (no blank spaces between parts). Do not join the recipient’s email address to the subject string.

Example:$ mail "-s EMCServer_csA121,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,Facility-CFS,Severity-4Jun 18 15:42:50 2003 CFS:4:1 Slot 3: 1009511393: filesystem size threshold (90%) crossed (fs /ufs1)


Appendix B: Events and event IDsThe following tables provide a list of event IDs, events, and descriptions. Table 6 provides a cross-reference to the list of events for each event facility.

Table 6 Event facility event list cross-reference

Event facility Location

ACLUPD Table 7 on page 64

ADMIN Table 8 on page 65

BoxMonitor Table 9 on page 65

CAM Table 10 on page 74

CFS Table 11 on page 75

CHAMIIENCMON Table 12 on page 75

Checkup Table 13 on page 76

DHSM Table 14 on page 78

DPSVC Table 15 on page 78

DRIVERS Table 16 on page 78

FCP Table 17 on page 80

FSTOOLS Table 18 on page 80

JServer Table 19 on page 81

LIB Table 20 on page 81

LocalHardwareMonitor Table 21 on page 82

LogCollect Table 22 on page 84

MasterControl Table 23 on page 88

MGFS Table 24 on page 88

NASDB Table 25 on page 89

NaviEventMonitor Table 26 on page 89

NDMP Table 27 on page 90

NFS Table 28 on page 91


RCPD Table 29 on page 91

REP Table 30 on page 91

SECURITY Table 31 on page 91

SNAPSURE_SCHED Table 32 on page 92

STORAGE Table 33 on page 93

SVFS Table 34 on page 93

UFS Table 35 on page 94

UPSMonitor Table 36 on page 95

USRMAP Table 37 on page 99

VC Table 38 on page 99

VMCAST Table 39 on page 100

VRPL Table 40 on page 101

XLT Table 41 on page 102

Table 6 Event facility event list cross-reference (continued)

Event facility Location


Table 7 ACLUPD (101) events

Event ID Event Event description/corrective action

0 ACLUPD OK Not used.

1 ResetAll command start Start of a command to change all ACLs in the database of a given file system. This is a debug command only.

2 ResetAll command end End of a command to change all ACLs in the database of a given file system. This is a debug command only.

3 CheckAll command start Start of a command to check the ACL database of a given ACL for logical corruption. This is a debug command only.

4 CheckAll command end End of a command to check the ACL database of a given ACL for logical corruption. This is a debug command only.

5 SetSd command start Start of a command to remap all SID to UID/GID in the ACL database of a file system. This is a debug command only.

6 SetSd command end End of a command to remap all SID to UID/GID in the ACL database of a file system. This is a debug command only.

7 MigDom command start Start of the Control Station command server_cifs –migrate.

8 MigDom command end End of the Control Station command server_cifs –migrate.

9 HistorySid command start Start of the Control Station command server_cifs –replace.

10 HistorySid command end End of the Control Station command server_cifs –replace.

11 PrintStats command start Start of a command to output the statistics of the ACL database of a given file system. This is a debug command only.

12 PrintStats command end End of a command to output the statistics of the ACL database of a given file system. This is a debug command only.

13 DumpAll command start Start of a command to dump all ACL stored on a file system. This is a debug command only.

14 DumpAll command end End of a command to dump all ACL stored on a file system. This is a debug command only.

15 Error occurred during a command Critical errors occurred, such as Cannot create a new thread. The Data Mover will probably panic before being able to send this message.


Table 8 ADMIN (24) event facility


0 Log crash The event log buffer overflowed; some events were lost. No action required.

Table 9 BoxMonitor (131) event facility


1 EPP did not initialize A call home event has been generated. Logged in sys_log.

2 RPC services failed to start A call home event has been generated. Logged in sys_log.

3 Mandatory thread create failed A call home event has been generated. Logged in sys_log.

4 SIB read failure A call home event has been generated. Logged in sys_log.

5 SIB write failure A call home event has been generated. Logged in sys_log.

6 AC power failure A call home event has been generated. Logged in sys_log.

7 Fan 0 has failed A call home event has been generated. Logged in sys_log.

8 Fan 1 has failed A call home event has been generated. Logged in sys_log.

9 Both fans have failed A call home event has been generated. Logged in sys_log.

10 High temperature warning A call home event has been generated. Logged in sys_log.

11 High temperature failure A call home event has been generated. Logged in sys_log.

12 12V DC supply high A call home event has been generated. Logged in sys_log.

13 12V DC supply low A call home event has been generated. Logged in sys_log.

14 5V DC supply high A call home event has been generated. Logged in sys_log.

15 5V DC supply low A call home event has been generated. Logged in sys_log.

16 3.3V DC supply high A call home event has been generated. Logged in sys_log.

17 3.3V DC supply low A call home event has been generated. Logged in sys_log.

18 -12V DC supply high A call home event has been generated. Logged in sys_log.


19 -12V DC supply low A call home event has been generated. Logged in sys_log.

20 -5V DC supply high A call home event has been generated. Logged in sys_log.

21 -5V DC supply low A call home event has been generated. Logged in sys_log.

22 Service Mode switch enabled A call home event has been generated. Logged in sys_log.

23 Battery backup enabled A call home event has been generated. Logged in sys_log.

24 Battery backup disabled A call home event has been generated. Logged in sys_log.

25 EPO unit has been inserted A call home event has been generated. Logged in sys_log.

26 EPO unit has been removed A call home event has been generated. Logged in sys_log.

27 Battery box has been inserted A call home event has been generated. Logged in sys_log.

28 Battery box has been removed A call home event has been generated. Logged in sys_log.

29 Power supply has been inserted A call home event has been generated. Logged in sys_log.

30 Power supply has been removed A call home event has been generated. Logged in sys_log.

31 Charger has been inserted A call home event has been generated. Logged in sys_log.

32 Charger has been removed A call home event has been generated. Logged in sys_log.

33 Commbd has been inserted A call home event has been generated. Logged in sys_log.

34 Commbd has been removed A call home event has been generated. Logged in sys_log.

35 ShoeBox has been inserted A call home event has been generated. Logged in sys_log. BoxMonitor will attempt to renegotiate in 60 seconds.

36 ShoeBox has been removed Logged in sys_log.

37 Hardware presence detected A call home event has been generated. Logged in sys_log.

38 Invalid hardware configuration A call home event has been generated. Logged in sys_log.

39 ShoeBox boot failed A call home event has been generated. Logged in sys_log.

40 Unexpected reason code A call home event has been generated. Logged in sys_log.

41 State change requested A call home event has been generated. Logged in sys_log.

42 Shoebox reboot requested A call home event has been generated. Logged in sys_log.

Table 9 BoxMonitor (131) event facility (continued)



43 Shoebox ping failed to respond A call home event has been generated. Logged in sys_log.

45 Shoebox has rebooted - RC_DART_READY A call home event has been generated. Logged in sys_log.

46 BoxMonitor version number A call home event has been generated. Logged in sys_log.

47 Sense cable has been inserted A call home event has been generated. Logged in sys_log.

48 Sense cable has been removed A call home event has been generated. Logged in sys_log.

49 Terminator has been inserted A call home event has been generated. Logged in sys_log.

50 Terminator has been removed A call home event has been generated. Logged in sys_log.

51 Terminator has been inserted A call home event has been generated. Logged in sys_log.

52 Terminator has been removed A call home event has been generated. Logged in sys_log.

53 CDROM has been inserted A call home event has been generated. Logged in sys_log.

54 CDROM has been removed A call home event has been generated. Logged in sys_log.

55 Invalid command-line argument A call home event has been generated. Logged in sys_log.

56 Changed a command-line argument A call home event has been generated. Logged in sys_log.

57 Battery power is low Logged in sys_log.

58 Lost AC Power A call home event has been generated. Logged in sys_log on powerup.

59 AC Power is OK Logged in sys_log on powerup.

60 AC Power time-out has been exceeded Logged in sys_log on powerup.

61 Switch-related alarms Logged in sys_log.

62 EPO failure alarms A call home event has been generated. Logged in sys_log.

63 Battery-related alarms A call home event has been generated. Logged in sys_log.

64 AC input power alarms A call home event has been generated. Logged in sys_log.

65 DC internal power alarms A call home event has been generated. Logged in sys_log.

66 Power supply failure alarms A call home event has been generated. Logged in sys_log.

67 Fan failure alarms A call home event has been generated. Logged in sys_log.




68 Noncritical alarms to be logged only Logged in sys_log.

69 Log value of shoebox parameter Logged in sys_log.

70 /etc/hosts file error A call home event has been generated. Logged in sys_log.

71 Shoebox thermal failure Logged in sys_log.

72 Shoebox sibpost failure A call home event has been generated. Logged in sys_log.

73 Serial connection to the Data Mover has failed

A call home event has been generated. Logged in sys_log.

76 Battery is OK A call home event has been generated. Logged in sys_log.

100 Slot 00 reason code is stale A call home event has been generated. Logged in sys_log.



















200 Slot 00 ping failed on both ifaces A call home event has been generated. Slot 0 ping failed on both interfaces. Logged in sys_log.



















300 Slot 00 panicked A call home event has been generated. Logged in sys_log.The Celerra software running on the Data Mover in slot 0 encountered an abnormal condition and called a routine to force the Data Mover to shut down and dump and save its memory for analysis by EMC.



















400 Slot 00 no status Logged in sys_log.



















440 Slot Set Contacted Failed An NSX event.

500 CPU blade is removed A call home event has been generated due to an NSX blade (Data Mover) hardware fault. Logged in sys_log.

501 CPU blade is inserted An NSX event. Logged in sys_log.

502 CPU blade fault A call home event has been generated due to an NSX blade (Data Mover) hardware fault. Logged in sys_log.

503 CPU is OK An NSX event. Logged in sys_log. No action required.

504 CPU IO Module 0 fault A call home event has been generated due to an NSX blade (Data Mover) hardware fault. Logged in sys_log.

505 CPU IO Module 0 is OK An NSX event. Logged in sys_log. No action required.

506 CPU IO Module 1 fault A call home event has been generated due to an NSX blade (Data Mover) hardware fault. Logged in sys_log.

507 CPU IO Module 1 is OK An NSX event. Logged in sys_log. No action required.

508 I/O Annex is removed A call home event has been generated. An NSX event. Logged in sys_log.

509 I/O Annex is inserted An NSX event. Logged in sys_log.

510 I/O Annex fault A call home event has been generated. An NSX event. Logged in sys_log.




511 I/O Annex is OK An NSX event. Logged in sys_log. No action required.

512 Management Switch is removed A call home event has been generated due to an NSX management switch fault. Logged in sys_log.

513 Management Switch is inserted An NSX event. Logged in sys_log.

514 Management Switch fault A call home event has been generated due to an NSX management switch fault. Logged in sys_log.

515 Management Switch internal error A call home event has been generated due to an NSX management switch fault. Logged in sys_log.

516 Management Switch is OK An NSX event. Logged in sys_log. No action required.

517 Power Supply is removed A call home event has been generated due to an NSX power supply fault. Logged in sys_log.

518 Power Supply is inserted An NSX event. Logged in sys_log.

519 Power Supply fault A call home event has been generated due to an NSX power supply fault. Logged in sys_log.

520 Power Supply is OK An NSX event. Logged in sys_log.

521 Fan fault A call home event has been generated due to an NSX fan fault. Logged in sys_log.

522 Fan is OK An NSX event. Logged in sys_log.

523 Multiple Fan error A call home event has been generated due to an NSX fan fault. Logged in sys_log.

524 Slot boot error A call home event has been generated. Logged in sys_log.Indicates that POST or BIOS running on a Data Mover detected an error during the boot process. An error code is set and the process stopped.

525 Slot Management Switch Reason Code Error

An NSX event. Logged in sys_log.

526 Management Switch Ping Failure An NSX event. Logged in sys_log.

527 Both Management Switches Ping Failure

A call home event has been generated due to an NSX management switch fault. Logged in sys_log.

528 Management Switch Network Port is Up An NSX event. Logged in sys_log.

529 Management Switch Network Port is Down

An NSX event. Logged in sys_log.




530 State change request is ignored An NSX event.



Table 10 CAM (26) event facility


0 CAM OK Normal, no action required.

1 CAM I/O path has failed The backend returned an error.

2 CAM I/O path is inaccessible A path to the backend is no longer available.

3 CAM command timeout No response received from the backend.

4 CAM hung I/O No response received from the backend. When the request was aborted, the backend still did not respond.

5 CAM internal error or bad request This is probably the result of a software fault.

6 CAM I/O path is again normal The path to the backend is up and running.

7 CAM I/O error A call home event has been generated. Indicates an I/O failure has occurred in the CAM software layer of the Data Mover. The I/O operation was most likely targeted for a physical disk on a storage backend subsystem, which did not complete successfully.


Table 11 CFS (27) event facility


1 Crossed the filesystem size threshold

The amount of space used in the file system exceeds the specified percent full threshold. The default is 90% space in use. File system performance may degrade when a file system is almost full.

2 Persistent blocks greater than free blocks

Free block corruption. An fsck is required.

3 Dropped below the filesystem size threshold

The file system has enough free blocks. No action required.

4 Crossed the root filesystem size threshold

A call home event has been generated. Indicates the blocks used percentage has crossed the threshold limit set for the root file system; the root file system is close to becoming full.

5 Dropped below the root filesystem size threshold

The file system has enough free blocks. No action required.

Managing Celerra Volumes and File Systems Manually and Managing Celerra Volumes and File Systems with Automatic Volume Management provide information about file systems.

Table 12 CHAMIIENCMON (86) event facility (NS series systems)


0 Power Supply A installed A new Power Supply A has been installed. No action required.

1 Power Supply A removed Power Supply A has been removed. No action required.

5 Power Supply A OK Normal, no action required.

6 Power Supply A failed A call home event has been generated. Power Supply A failed because of an AC failure, over temperature, or other faults.

10 Power Supply B installed A new Power Supply B has been installed. No action required.

11 Power Supply B removed Power Supply B has been removed. No action required.

15 Power Supply B OK Normal, no action required.

16 Power Supply B failed A call home event has been generated. Power Supply B failed because of an AC failure, over temperature, or other faults.

21 One or more fans in Fan Module 1 failed

A call home event has been generated. Fan Module 1 faulted.May need to replace Fan Module 1.


../AVM/index.htm

../AVM/index.htm



A call home event has been generated. Fan Module 2 faulted. May need to replace Fan Module 2.


A call home event has been generated. Fan Module 3 faulted. May need to replace Fan Module 3.

26 Multiple fans failed. Critical A call home event has been generated. More than one fan faulted.The power supplies to the enclosure are shut down if the faults persist for over 2 minutes.

28 ALL Fans OK Normal, no action required.

29 XPE Enclosure OK Normal, no action required.

31 Power Supply A is going to shut down A call home event has been generated. If Power Supply A is over temperature for over 2 minutes, it shuts down.

32 Power Supply B is going to shut down A call home event has been generated. If Power Supply B is over temperature for over 2 minutes, it shuts down.

33 Both power supplies are going to shut down

A call home event has been generated. If there is a multiple fan failure or if both power supplies are over temperature for more than 2 minutes, both power supplies to the enclosure shut down.

101 DMI Log Error or Warning The DMI issued a log error or warning.

Table 12 CHAMIIENCMON (86) event facility (NS series systems) (continued)


Table 13 Checkup (142) event facility


10 nas_checkup found no problems. Checkup found no problems.

11 nas_checkup posted information. See /nas/log/nas_checkup-run.*.log.

Checkup posted information. See the nas_checkup-run log.

12 nas_checkup posted a warning. See /nas/log/nas_checkup-run.*.log.

Checkup posted a warning. See the nas_checkup-run log.

13 nas_checkup discovered an error. See /nas/log/nas_checkup-run.*.log.

Checkup discovered an error. See the nas_checkup-run log.

19 nas_checkup had to exit before performing any checks.

Checkup exited before performing any checks.

21 nas_checkup posted information. Contact EMC Customer Service and refer to EMC Knowledgebase emc146016.

Checkup posted information. Contact EMC Customer Service, and refer to EMC Knowledgebase emc146016.


22 nas_checkup posted a warning. Contact EMC Customer Service and refer to EMC Knowledgebase emc146016.

Checkup posted a warning. Contact EMC Customer Service, and refer to EMC Knowledgebase emc146016.

23 nas_checkup discovered an error. Contact EMC Customer Service and refer to EMC Knowledgebase emc146016.

Checkup discovered an error. Contact EMC Customer Service, and refer to EMC Knowledgebase emc146016.

110 Scheduled nas_checkup found no problems.

Scheduled Checkup found no problems.

111 Scheduled nas_checkup posted information. See /nas/log/nas_checkup.*.log.

Scheduled Checkup posted information. See the nas_checkup log.

112 Scheduled nas_checkup posted a warning. See /nas/log/nas_checkup.*.log.

Scheduled Checkup posted a warning. See the nas_checkup log.

113 Scheduled nas_checkup discovered errors. See /nas/log/nas_checkup.*.log.

Scheduled Checkup discovered errors. See the nas_checkup log.

119 Scheduled nas_checkup had to exit before performing any checks.

Scheduled Checkup exited before performing any checks.

121 Scheduled nas_checkup posted information. EMC Customer Service will contact you. See nas_checkup log.

Scheduled Checkup posted information. EMC Customer Service will contact you. See the nas_checkup log.

122 Scheduled nas_checkup posted a warning. EMC Customer Service will contact you. See nas_checkup log.

Scheduled Checkup posted a warning. EMC Customer Service will contact you. See the nas_checkup log.

123 Scheduled nas_checkup discovered an error. EMC Customer Service will contact you. See nas_checkup log.

Scheduled Checkup discovered an error. EMC Customer Service will contact you. See the nas_checkup log.

221 Scheduled nas_checkup posted information. EMC Customer Service has been contacted. See nas_checkup log.

Scheduled Checkup posted information. EMC Customer Service has been contacted. See nas_checkup log.

222 Scheduled nas_checkup posted a warning. EMC Customer Service has been contacted. See nas_checkup log.

A call home has been generated. Scheduled Checkup posted a warning. See the nas_checkup log.

223 Scheduled nas_checkup discovered an error. EMC Customer Service has been contacted. See nas_checkup log.

A call home has been generated. Scheduled Checkup discovered an error. See the nas_checkup log.

Table 13 Checkup (142) event facility (continued)



Table 14 DHSM (96) event facility


0 DHSM log is full There is no corrective action needed for this event; it is information only. It notifies external policy engines or other applications that the DHSM log file has rolled over.

Using Celerra FileMover provides more information about the conditions that cause the DHSM events.

Table 15 DPSVC (111) event facility


6 DPPolicy has become inactive A call home event has been generated. The policy has become inactive because a fatal error was detected. Replication has to be aborted and restarted, starting automatically from a common base.

7 Database Error during insert A call home event has been generated. The root file system needs to be fixed. Replication has to be aborted and restarted, starting automatically from a common base.

Table 16 DRIVERS (36) event facility


0 OK Normal, no action required.

1 Device initialization failure This is probably an adapter failure.

2 Link down Link was up and is now down.

3 Link up Link was down and is now up.

4 Partial link down This applies to high-availability devices. One or more links in the virtual device are down. The remaining links in the device continue to operate.

5 Partial link up This applies to high-availability devices.

../FileMover/index.htm


6 NIC device panic A call home event is generated. Indicates a TCP Offload Engine (TOE) network interface card (NIC) faulted and created a software panic dump. The TOE card is used only on Celerra systems with 514T type Data Movers. When the card faults, any TCP client connections using that interface are reset. When the card resets itself, it disables TOE and the card functions as a normal NIC interface.

Configuring and Managing Celerra Networking provides information about network devices. Configuring and Managing Celerra Network High Availability provides information about high availability devices.

Table 16 DRIVERS (36) event facility (continued)


../Network/index.htm

../NetworkHighAvailability/index.htm

../NetworkHighAvailability/index.htm


Table 17 FCP (102) event facility


0 Fibre channel OK A call home event has been generated. This information is logged in sys_log.

1 Fiber channel link is now up A call home event has been generated. This information is logged in sys_log.

2 Previously active fibre channel link is down

A call home event has been generated. This information is logged in sys_log.

3 Fibre channel I/O error A call home event has been generated. This information is logged in sys_log.

4 Fibre channel binding is running A call home event has been generated. This information is logged in sys_log.

5 Fibre channel state change notification detected


6 Fibre channel driver detected a bad state or starting I/O failed


7 Fibre channel internal error A call home event has been generated. This information is logged in sys_log.

8 Fibre channel initialization failed A call home event has been generated. This information is logged in sys_log.

9 Fibre channel aborted A call home event has been generated. This information is logged in sys_log.

10 Disk mark needed A call home event has been generated. This information is logged in sys_log.

11 LUN zero I/O error A call home event has been generated. This information is logged in sys_log.

Table 18 FSTOOLS (40) event facility


0 FSCK Started Normal, no action required.

1 FSCK Succeeded The file system check (fsck) succeeded. No action required.


2 FSCK Failed Possible volume database corruption. Manual file system check (fsck) required.

3 ACLCHK Started ACL check stared. No action required.

4 ACLCHK Succeeded ACL check succeeded. No action required.

5 ACLCHK Failed Possible volume database corruption. Manual ACL check required.

Table 18 FSTOOLS (40) event facility (continued)


Table 19 JServer (135) event facility


0 Log Errors/Warnings into /nas/jserver/logs/system_log.x

Errors and warnings are logged to /nas/jserver/logs/system_log.x.

101 Call Home - JServer failed to come up after 3 retries

A call home event has been generated. The JServer did not start after three attempts.

102 Call Home - Generated debug file xxx from the core dump

A call home event has been generated. The JServer created a debug file xxx from the core dump.

103 Call Home - JServer reports nas_cmd errors

A call home event has been generated. The JServer has reported NAS command errors.

104 Call Home - JServer generated problem report zip file /nas/jserver/x.zip

A call home event has been generated. The JServer created a problem report and placed it in a zip file in the following location: /nas/jserver/x.zip.

105 Call Home - API Server failed to come up after 3 retries

A call home event has been generated. The API server did not start after three attempts.

1001 Crossed the JServer file system usage threshold

The JServer has crossed the usage threshold of the file system.

1002 Dropped below the JServer file system usage threshold

The JServer has dropped back below the file system usage threshold.

Table 20 LIB (46) event facility


0 Log crash The event log buffer overflowed; some events were lost. No action required.


Table 21 LocalHardwareMonitor (139) event facility


1 1.5V too high A voltage level is out of range.

2 1.5V too low A voltage level is out of range.

3 Vccp1 too high A voltage level is out of range.

4 Vccp1 too low A voltage level is out of range.

5 3.3V too high A voltage level is out of range.

6 3.3V too low A voltage level is out of range.

7 5V too high A voltage level is out of range.

8 5V too low A voltage level is out of range.

9 12V too high A voltage level is out of range.

10 12V too low A voltage level is out of range.

11 Vccp2 too high A voltage level is out of range.

12 Vccp2 too low A voltage level is out of range.

13 Fan1 low A fan fault.

14 Fan2 low A fan fault.

15 Temperature too high A temperature fault.

17 Vid too high Vid too high.

18 Chassis Intrusion A chassis Intrusion.

100 VCCP Voltage Alarm A call home event has been generated due to an out-of-range NSX voltage level.

101 FSB Voltage Alarm A call home event has been generated due to an out-of-range NSX voltage level.

102 MCH CORE 1.5V Alarm A call home event has been generated due to an out-of-range NSX voltage level.

103 MEM VTT 0.98V Alarm A call home event has been generated due to an out-of-range NSX voltage level.


104 MEM CORE 1.8V Alarm A call home event has been generated due to an out-of-range NSX voltage level.

105 NIC CORE 1.5V Alarm A call home event has been generated. Indicates an NSX voltage level.

106 BB 3.3VSB Alarm A call home event has been generated due to an out-of-range NSX voltage level.

107 BB 5VSB Alarm A call home event has been generated due to an out-of-range NSX voltage level.

108 BB 3.3V Alarm A call home event has been generated due to an out-of-range NSX voltage level.

109 BB 5V Alarm A call home event has been generated due to an out-of-range NSX voltage level.

110 BB 12V Alarm A call home event has been generated due to an out-of-range NSX voltage level.

111 BB -12V Alarm A call home event has been generated due to an out-of-range NSX voltage level.

112 Fan 1H Alarm A call home event has been generated due to an NSX fan fault.





117 Fan 1L Alarm A call home event has been generated. due to an NSX fan fault.

118 Fan 2L Alarm A call home event has been generated due to an NSX fan fault.




122 BB Temp Alarm A call home event has been generated due to an NSX temperature alarm.

123 Amb Temp Alarm A call home event has been generated due to an NSX temperature alarm.

Table 21 LocalHardwareMonitor (139) event facility (continued)



124 CPU Temp Alarm A call home event has been generated due to an NSX temperature alarm.

Table 21 LocalHardwareMonitor (139) event facility (continued)


Table 22 LogCollect (141) event facility


1 Collection script has started The collection script has started.

2 Collection script has finished successfully

The collection script has successfully gathered all materials and placed them in the /nas/var/log directory.

3 Collection script has finished with partial collection

The collection script only partially finished, usually because of insufficient disk space to continue log collection. Ensure that the /nas/var partition is at least 15% free.

4 Collection script cannot create temporary directory X

The collection script was unable to create a temporary directory in which to place the file, usually because of insufficient disk space. Ensure that the parent directory has permission 775 and has enough disk space (at least 15% free).

5 Collection script cannot create temporary directory Y in /

The collection script was unable to create a temporary directory in which to place the file, usually because of incorrect permissions or insufficient disk space. Ensure the disk partition of / has at least 10% of free disk space.

7 Collection script cannot run because another instance is running

The collection script cannot run when another session is already running. If another session has been running for more than 2 hours, it may be hung on a command. Manually terminate the session that is running.

8 Collection script cannot run by non-nasadmin or root user

The collection script could not run because a user without nasadmin or root permission attempted to run it. Make sure you are either a NAS administrator or root user before you try to invoke this script.

100 Transfer script has started The transfer script has started transferring collected materials.

101 Transfer script cannot reach remote FTP server/directory

The transfer script is unable to transfer the collected materials to the remote FTP server or directory. Check your configuration in /nas/site/automaticcollection.cfg, and check network connectivity.


102 Transfer script has failed, possibly not enough disk space on the remote server.

The transfer script failed, perhaps because there is insufficient space available in the remote FTP directory.• If this server is owned by your service provider, contact them to

rectify the problem.• If the server is owned by your company, check the space available

on your FTP server.

103 Transfer script has failed, no material is available for transfer

No recent material for transfer has been collected in the /nas/var/log directory. If you expected material to have been collected, check the system log (sys_log) to ensure there were no errors during log collection.

104 Transfer script has failed, possibly cannot reach remote FTP server/directory

The transfer script failed. It may not have been able to connect to the remote directory. Ensure the following conditions are met:• The configuration file

(/nas/site/automaticcollection.cfg) contains the right hostname/IP address of the server and the correct username/password.

• The user has write access to the remote directory. • The Control Station can resolve the name to an IP address if a

hostname is used.• The ends of these lines contain no spaces, since the FTP program

used by the tool misinterprets spaces at the end of the line.

105 Transfer script has finished successfully for log

Your authorized service provider should check the FTP server for the log saved in the remote directory as specified in the configuration file (/nas/site/ automaticcollection.cfg).

106 Transfer script has finished successfully for dump

Your authorized service provider should check the FTP server for the dump and dump header files saved in the remote directory as specified in the configuration file (/nas/site/ automaticcollection.cfg).

107 Transfer script has failed, possibly not enough disk space in the dump directory

The transfer script failed, possibly because of insufficient disk space to create the file. Make sure the /nas/var partition has permission 775 and has enough disk space (1.6 GB) to accommodate this collection.

108 Transfer script has saved the dump to a local directory

The transfer script logged the dump successfully in the /nas/var/ dump directory. Provide the dump to your authorized service provider upon request.

109 Transfer script has failed because it cannot create FIFO in a local directory

The transfer script failed because the FIFO (program pipes) that assists in the dump creation could not be created. Typically, this is caused by permission problems rather than by a lack of disk space. Ensure the permission of the parent directory is 775.

200 slot 0 dump is ready The dump for slot 0 is ready to be retrieved.



Table 22 LogCollect (141) event facility (continued)
















300 The automatic transfer feature has been enabled

The automatic transfer feature is enabled.

301 The automatic collection and transfer feature has been disabled

The automatic collection and transfer feature is disabled.

302 The automatic collection and transfer feature has been enabled

The automatic collection and transfer feature is enabled.

303 The automatic transfer feature has been disabled

The automatic transfer feature is disabled.

304 There are too many transfer sessions in progress

Too many transfers are running to attempt another transfer. A transfer session could be hung, or the MaxTransfer variable in the configuration file may be too small. To fix the problem:• Type ps -wlef | grep transfer_support_materials to

see how many sessions are in progress, and also check if the system is continuing to log messages in /nas/log/sys_log.

• Use a text editor to increase the MaxTransfer variable in the configuration file (/nas/site/automaticcollection.cfg).




305 Elapse time of 15 minutes is required between collection runs

To limit resources used by this script, the collection script can run only once every 15 minutes. However, when there is a panic, the script is executed regardless of the time limit.If materials need to be collected and the 15-minute time limit has not passed, the NAS administrator can manually invoke the collect_support_materials script from the CLI.• If the /nas/var partition has space for more dumps, increase the MaxCopyDump variable in the configuration file /nas/site/automaticcollection.cfg.

Do not remove dumps from the /nas/var/dump directory unless you are sure they have already been processed by your service provider. Contact your authorized service provider to ensure this is the case.

306 There are too many dumps in the dump directory

Because of disk space limitations, you can save only two dumps in the /nas/var/dump directory.

307 Cannot create the configuration file The configuration file could not be created, usually because of incorrect permissions. Ensure that the /nas/site directory has permission 775 and has enough disk space to accommodate a 2 KB file.

308 Cannot do transfer because the transfer feature is disabled

The transfer feature is disabled.

309 The feature is disabled The LogCollect feature is disabled.




Table 23 MasterControl (129) event facility


1 Terminating master control app Master control process is terminated. This message is usually generated when NAS services stops.

2 No privilege to set IO priority Insufficient privilege to set I/O priority.

3 Unable to chdir Unable to change directory.

4 Unable to exec daemon Unable to start a subdaemon.

5 Unable to fork Unable to fork a process.

6 Unexpected daemon exit A call home event has been generated. The master control daemon is running and has noticed that a subdaemon has exited.

7 Control Station heartbeat missing A call home event has been generated. This pertains to a peer Control Station in dual Control Station environment.

8 Sibpost failed A call home event has been generated. Power on self-test failed.

9 Unknown slot ID A call home event has been generated. Unknown slot ID.

10 File system error A call home event has been generated. This information is logged in sys_log.

11 Notification A call home event has been generated. This information is logged in sys_log.

12 NBS Device Error A call home event has been generated. There has been an error on one of the Network Block Storage devices.

13 IPMI connection failure A call home event has been generated. There has been an Internet Protocol Management Interface connection failure.

14 IPMI connection restored Internet Protocol Management Interface connection restored. No action required.

Table 24 MGFS (75) event facility


0 Connection Delete operation is complete

Normal, no action required.

Celerra CDMS Version 2.0 for NFS and CIFS provides more information about the conditions that cause the MGFS events.

../CDMS/index.htm


Table 25 NASDB (137) event facility


10 Checkpoint Auto Extension Failed The system space quota for SavVols is exceeded. Using SnapSure on Celerra provides more information about the conditions that cause this event.

11 Command Execution Failed Logged in sys_log. Meaning varies depending on the facility generating the event.

12 Inactive Checkpoint Umount Logged in sys_log. Meaning varies depending on the facility generating the event.

13 Scheduled Replication Restart Checkpoint Refresh

Logged in sys_log.

201 Invalid Database Signature Logged in sys_log. Meaning varies depending on the facility generating the event.

202 NAS database error detected Logged in sys_log. Meaning varies depending on the facility generating the event.

211 Scheduled Task Missed Logged in sys_log. Meaning varies depending on the facility generating the event.

212 Scheduled Task Failed Logged in sys_log. Meaning varies depending on the facility generating the event.

1001 Command Log Into nas_log.al.replication

Logged in nas_log.al.replication.

Table 26 NaviEventMonitor (138) event facility


1 Navi Event with severity INFORMATION was received

This is a grouping of Navisphere® events. Unable to determine course of action required, if any.

2 Navi Event with severity WARNING was received

This is a grouping of Navisphere events. Unable to determine course of action required, if any.

3 Navi Event with severity ERROR was received

This is a grouping of Navisphere events. Unable to determine course of action required, if any.

4 Navi Event with severity CRITICAL was received

A call home event has been generated.

5 Unknown Navi Event was received This is a grouping of Navisphere events. Unable to determine course of action required, if any.

../SnapSure/index.htm



10 Navi Event Monitor has terminated Process monitoring from the backend has terminated. To restart this process, you have to stop and start NAS services using the following commands after logging into the Control Station as root:[root@csdev-3 root]# service nas stop

[root@csdev-3 root]# service nas start

After NAS services have started, check that this process is active by issuing the following command:[root@csdev-3 root]# ps -e | grep navilog_mon

25793 ? 00:00:00 navilog_mon

100 A control lun has been cache compromised

Use the following command to update the storage information to the latest state:nas_storage –sync –all Verify that the disk identified has no current owner using this command syntax:nas_disk –info <disk> -o all

If the current owner is blank, the CLARiiON LUN may be cache-compromised and CLARiiON support should be engaged.This event may be the result of a transient condition. If the current owner is “A” or “B,” there is no error and the event can be dismissed.Contact EMC Customer Service if you need more information.

101 A control lun has been trespassed Run the following command for the storage system that owns the device.

Note: This may make the disk temporarily unavailable as it is trespassed back to the SP that owns it.

nas_storage –failback { <name> | id=<storage_id> }

Contact EMC Customer Service if you need more information.

Table 26 NaviEventMonitor (138) event facility (continued)


Table 27 NDMP (51) event facility


1 Create a checkpoint for the backup filesystem and mount it

The Control Station created a new checkpoint for the file system and mounted it.

2 Unmount the checkpoint for the backup filesystem and delete it

The Control Station unmounted the specified checkpoint and deleted it.


Table 28 NFS (52) event facility


0 Failed to start NFS A call home event has been generated. NFS failed to start.

Table 29 RCPD (83) event facility


0 RCPD Server stopped listening A call home event has been generated. The Data Mover needs to be rebooted to continue. There is a bug. Force a panic to generate a dump and then collect the logs.

Table 30 REP (108) event facility


1 DB record creation failed A call home event has been generated. The creation, deletion, or update of a database record on the root file system failed because the root file system is inaccessible, full, or corrupted, or it contains a duplicate record. Fix root file system issue. If replication becomes inactive, it needs to be aborted and restarted. It starts automatically from a common base. The reason for a duplicate record is either a bug or a database that was manually updated.

2 Recovery failed. Session inactive A call home event has been generated. Pre-event, post-event, and recovery failed because of a fatal error. The database update on the root file system failed. To fix the error, replication has to be aborted and restarted. It starts automatically from a common base.

Table 31 SECURITY (54) event facility


0 No error Normal, no action required.

1 No terminator in line A group record in the /.etc/group file is corrupted. Check the group file.

2 Line too long, truncated The group record is larger than 998 bytes, and the record has been truncated. Correct the /.etc/group file.


3 Cannot interpret group string Malformed group record in /.etc/group or the file is corrupted. Check the group file.

4 End of file encountered The /.etc/group file ends in the middle of a group record.

5 Empty line This event is not generated.

Table 31 SECURITY (54) event facility (continued)


Table 32 SNAPSURE_SCHED (91) event facility


1 Scheduled SnapSure creation failed Scheduled SnapSure checkpoint creation failed.

2 Scheduled SnapSure refresh failed Scheduled SnapSure checkpoint refresh failed.

Using SnapSure on Celerra provides more information about the conditions that cause the SnapSure events.



Table 33 STORAGE (58) event facility


0 Storage OK Normal, no action required.

1 Disk mark does not match A call home event has been generated. The diskmark does not match the diskmark on this particular path.

2 I/O path invalidated due to bad disk mark

The diskmark does not match; the path is not used.

3 I/O request failed The backend returned an error.

4 Failover succeeded Normal, no action required.

5 CLARiiON lun has been trespassed A LUN is trespassed if it is not owned by its default storage processor (SP).

6 Incorrect Volume reference/dereference

A call home event has been generated. There was an attempt to use the same part of the used volume or an incorrect part of the volume was released.

Table 34 SVFS (70) event facility


1 High water mark of SavVol reached High water mark of SnapSure SavVol reached.

2 Checkpoint inactive The checkpoint is not readable or accurate due to insufficient resources needed to store point-in-time information.

3 Source filesystem restore done Checkpoint restore (restoring a source file system to a point-in-time state from a checkpoint) has successfully finished. In this case, no action required from the user.

4 Restore is in progress This event indicates that checkpoint restore is progressing and has not yet completed. Normal, no action required.

5 Checkpoint conversion is paused - savvol is full

Checkpoint conversion is paused due to a full SavVol.

Using SnapSure on Celerra provides more information about the conditions that cause the SVFS events.



Table 35 UFS (64) event facility


0 I18N OK I18N conversion succeeded (no event generated).

1 I18N - Out of Inodes I18N conversion could not allocate an inode. Manual file deletions or file system extensions are required (applies to compat directories only).

2 I18N - Cannot balloc I18N conversion could not read a block, or allocate a block. Manual file deletions or file system extensions are required.

3 I18N - Recovery failed, file system not mounted

I18N conversion could not recover a partially converted directory. Retry the operation (only applies to compat directories).

4 Soft quota (warning limit) crossed Indicates the soft quota limit for the file system has been crossed and that the file system is approaching the hard limit. Manual file deletions or file system extensions are required soon.

5 Hard limit reached/exceeded Indicates the hard limit has been reached. Additional files are not saved. Existing files can be read. Remove data.

6 Directory translate status message Manual file deletions or file system extensions are required.

7 Skip auto fsck for corrupted file system at mount

A call home event has been generated. Manual file system check (fsck) needed before file system can be mounted.

8 Gid map file is not present Group ID file is not available. It must be manually recovered before file system can be mounted.

9 Gid map file is full Group ID map file is full and must be rebuilt to reclaim space.

10 Directory translate major error Manual file deletions or file system extensions are required.

11 Crossed the root filesystem inode threshold

A call home event has been generated. The root file system is filling up; you need to free space before it is completely full.

12 Crossed the filesystem inode threshold

Indicates the inode used percentage has crossed the threshold limit set for the file system. The file system is exhausting its inode limit.

13 Dropped below the root filesystem inode threshold

The file system has enough free inodes. No action required.

14 Dropped below the filesystem inode threshold

The file system has enough free inodes. No action required.

15 Filesystem size incorrect in superblock

A call home event has been generated.

Managing Celerra Volumes and File Systems Manually and Managing Celerra Volumes and File Systems with Automatic Volume Management provide more information about the conditions that cause the UFS events.


../AVM/index.htm

../AVM/index.htm


Table 36 UPSMonitor (140) event facility (NSX series systems)


1 communicationLost Communication between the agent and the UPS has been lost.

2 upsOverload The UPS has sensed a load greater than 100 percent of its rated capacity.

3 upsDiagnosticsFailed A call home event has been generated. The UPS failed its internal diagnostic self-test.

4 upsDischarged The UPS batteries are discharged; if utility power fails, an immediate low-battery condition exists. Sufficient runtime for necessary action cannot be guaranteed.

5 upsOnBattery The UPS has switched to battery backup power.

6 smartBoostOn The UPS has enabled SmartBoost; low incoming line voltage.

7 lowBattery The UPS batteries are low and will soon be exhausted. If utility power is not restored, the UPS puts itself to sleep and immediately cuts power to the load.

8 communicationEstablished Communication with the UPS has been established.

9 powerRestored Returned from battery backup power; utility power restored.

10 upsDiagnosticsPassed The UPS passed its internal self-test.

11 returnFromLowBattery The UPS has returned from a low-battery condition.

12 upsTurnedOff A call home event has been generated. The UPS has been turned off by the management station.

13 upsSleeping The UPS is entering sleep mode. Power to the load will be cut off.

14 upsWokeUp The UPS has returned from sleep mode. Power to the load has been restored.

15 upsRebootStarted The UPS has started its reboot sequence.

16 upsDipSwitchChanged The dip switch settings on the UPS have been changed, possibly altering UPS performance.

17 upsBatteryNeedsReplacement A call home event has been generated. The UPS batteries require immediate replacement.

18 contactFault A call home event has been generated. One of the contacts on the environmental monitor has faulted.


19 contactFaultResolved A fault on one of the environmental monitor contacts has been resolved.

20 hardwareFailureBypass A call home event has been generated. The UPS is on bypass because of an internal fault.

21 softwareBypass A user has put the UPS on bypass by means of software or UPS front panel.

22 switchedBypass The UPS was put on bypass by the user.

23 returnFromBypass The UPS has returned from bypass.

24 bypassPowerSupplyFailure A call home event has been generated. The base module bypass power supply needs to be repaired.

25 baseFanFailure A call home event has been generated. The base module fan needs to be repaired.

26 batteryPackCommLost Communication has been lost with external battery packs; check the battery signal cable.

27 batteryPackCommEstablished Communication established with the external battery packs.

28 calibrationStart A battery run time calibration test has been initiated on the UPS.

29 restartAgent Agent restarting as commanded by manager.

30 upsTurnedOn A UPS is turned on.

31 smartAvrReducing The UPS is reducing the line voltage by means of SmartTrim.

32 codeAuthenticationDone Authentication on agent code image is done.

33 upsOverloadCleared The overload condition has been cleared.

34 smartBoostOff The UPS has returned from SmartBoost.

35 smartAvrReducingOff The UPS has returned from SmartTrim voltage reduction.

36 upsBatteryReplaced A bad battery fault has been cleared. The bad battery has been replaced.

37 calibrationEnd The UPS has finished calibrating.

38 dischargeCleared A UPS discharge condition has been cleared.

39 gracefullShutdown A graceful shutdown has been initiated.

Table 36 UPSMonitor (140) event facility (NSX series systems) (continued)



41 outletOn Outlet has turned on.

42 outletOff Outlet has turned off.

43 outletReboot Outlet has rebooted.

44 configChangeSNMP The SNMP configuration has been changed.

45 configChangeOutlet Outlet configuration has been changed.

46 accessViolationConsole There has been an access violation by means of the console. Three unsuccessful logins have been attempted by means of the console.

47 accessViolationHTTP There has been an access violation by means of HTTP. Someone has attempted to log in by means of HTTP with the incorrect password.

48 passwordChange The password for the device has been changed.

49 badVoltage Bad output voltage. The output voltage is not within acceptable range.

50 badVoltageCleared The bad voltage output condition has been cleared. The output voltage has returned to an acceptable level.

51 chargerFailure A call home event has been generated. The battery charger has failed.

52 chargerFailureCleared The battery charger failure condition has been cleared.

53 batteryOverTemperature A call home event has been generated. The battery temperature threshold has been exceeded.

54 batteryOverTemperatureCleared The battery overtemperature condition has been cleared.

55 smartRelayFault There has been a SmartBoost or SmartTrim relay fault.

56 smartRelayFaultCleared The SmartBoost or SmartTrim relay fault has been cleared.

57 humidityThresholdViolation1 A humidity threshold has been violated on probe 1.

58 humidityThresholdViolationCleared1 A humidity threshold violation has been cleared on probe 1.

59 temperatureThresholdViolation1 A temperature threshold has been violated on probe 1.

60 temperatureThresholdViolationCleared1

A temperature threshold violation has been cleared on probe 1.

61 humidityThresholdViolation2 A humidity threshold has been violated on probe 2.

62 humidityThresholdViolationCleared2 A humidity threshold violation has been cleared on probe 2.




63 temperatureThresholdViolation2 A temperature threshold has been violated on probe 2.

64 temperatureThresholdViolationCleared2

A temperature threshold violation has been cleared on probe 2.

65 mupsCommunicationEstablished Communication has been established between the agent and the environmental monitor.

66 mupsCommunicationLost Communication to the environmental monitor has been lost.

67 batteryIncrease The number of batteries has increased.

68 batteryDecrease The number of batteries has decreased.

69 powerModuleIncrease The number of power modules has increased.

70 powerModuleDecrease The number of power modules has decreased.

71 intelligenceModuleInserted An intelligence module has been inserted.

72 intelligenceModuleRemoved An intelligence module has been removed.

73 rintelligenceModuleInserted A redundant intelligence module has been inserted.

74 rintelligenceModuleRemoved A redundant intelligence module has been removed.

75 extBatteryFrameIncease An external battery frame has been added.

76 extBatteryFrameDecrease An external battery frame has been removed.

77 abnormalCondition A call home event has been generated. The UPSMonitor has detected or received an abnormal condition or code from the UPS.

78 abnormalConditionCleared An abnormal condition has been cleared.

79 deviceStatusChange The status of the device being monitored has changed.

80 noBatteries The UPS has no batteries attached.

81 noBatteriesCleared The UPS batteries have been attached.

82 userAdded A new user has been added.

83 userDeleted A user has been deleted.

84 userModified A user has been modified.




Table 37 USRMAP (93) event facility


0 Usermapper OK Normal, no action required.

1 Usermapper database created Normal, no action required.

2 Usermapper service enabled Normal, no action required.

3 Usermapper service stopped The user stopped the Usermapper service. No action required.

4 Usermapper database destroyed The user purposely destroyed a Usermapper database. No action required.

5 Usermapper available Normal, no action required.

6 Usermapper unreachable Check Usermapper configuration and reachability of all external Usermappers.

7 Usermapper filesystem quota exceeded Extend root file system (or file system where the Usermapper database is located).

Table 38 VC (81) event facility


0 Normal state Resync is issued automatically from full copy.

1 High water mark reached Check Virus Checker statistics to verify checkers are able to perform checking on time.

2 Low water mark reached None.

3 No Virus Checker server available Verify state of external checkers and network, etc.

4 No Virus Checker server; stop CIFS The customer has configured CIFS to stop when no external checker is available. Verify checker's availability.

5 No Virus Checker server; stop virus checking

The customer has configured the Virus Checker to stop when no external checker is available. Verify checker's availability.

6 File not checked The checker was stopped; a file couldn't be checked.

7 Virus Checker server online None.

8 Virus Checker server offline Check external Virus Checker service.


9 Filesystem scan started None.

10 Filesystem scan terminated None.

11 Filesystem scan aborted None.

12 File has been deleted by the Virus Checker engine

A virus has been detected, and corrective action has been taken by the external checker.

13 File has been renamed by the Virus Checker engine


14 File has been modified (cleaned) by the Virus Checker engine


15 Virus Checker stopped None.

16 Virus Checker started None.

Using Celerra AntiVirus Agent provides more information about the conditions that cause the VC events.

Table 38 VC (81) event facility (continued)


Table 39 VMCAST (84) event facility


1 Filesystem Copy over IP done Normal, no action required.

2 Filesystem Copy over IP failed File system copy operation failed. Abort the fs_copy command, fix the error reported, and start fs_copy again.

3 Volume Copy over IP done Normal, no action required.

4 Volume Copy over IP failed Volume copy is not supported.

5 Filesystem Copy over IP interrupted, unmount

A umount of the checkpoint was issued. Mount checkpoint to continue from interrupted fs_copy.

6 Filesystem Copy clean up done Normal, no action required.

7 Filesystem Copy convert failed File system on destination side was not converted to uxfs. Fix the error reported and do manual convert.

8 Filesystem Copy clean up failed The fs_copy command cannot clean up objects on the Control Station or Data Mover. Fix the error reported and issue the command fs_copy -abort.

../CAVA/index.htm


9 Resync Copy failed. Full Copy started

Resync cannot be issued from partial copy. Resync DeltaSet is not found on source side.

Table 39 VMCAST (84) event facility (continued)


Table 40 VRPL (77) event facility


0 Replication ok Normal, no action required.

1 Replication on Source Filesystem Inactive

A call home event has been generated. Replication service is inactive and not synchronized with the primary file system.

2 Resync asked by (previous) Destination Filesystem

A call home event has been generated. Request for a resynchronization of a replication relationship after a failover. This occurs every time an fs_replicate -Resync is issued.

3 Source Filesystem Switch Delta on H Not in use.

4 Destination Filesystem in Error A call home event has been generated. Playback service is inactive or an unknown failure has occurred.

5 IP Rep Svc failed - Transport IPRepSender was stopped.

6 IP Rep Svc NetWork or Receiver Down A source or destination IP network is down.

7 IP Rep Svc Network or Receiver Up A source or destination IP network is up.

8 Rep Svc Source Filesystem Flow on Hold

No source SavVol space is available.

9 Rep Svc Source Filesystem Flow Resumed

Source SavVol space is available.

10 Source Filesystem Frozen The result of specifying the autofreeze option or parameter.

11 Source Filesystem Thawed Release of autofreeze option or parameter.

12 Last Delta Replayed on Destination Filesystem

Issued at the end of a failover and reverse.

13 Redo Buffer close to overflow event In write-intensive environments sometimes the redo buffers are not flushed fast enough.

14 Source mounted RO Result of specifying the autoro option or parameter.

15 Source mounted RW Release of autoro option or parameter.


16 Replication in error Replication service is inactive or an internal error occurred.

Using Celerra Replicator provides more information about the conditions that cause the VRPL events.

Table 40 VRPL (77) event facility


Table 41 XLT (72) event facility


1 Detected corrupted XLT files A call home event has been generated. One or more XLT files are corrupted. EMC Customer Service will resolve this issue.

2 Recovering corrupted XLT files Some XLT files are corrupted. The XLT files will be updated automatically from the Control Station.

100 Translation directory does not exist yet

Run the uc_config -setup script to create translation directory, and then run the uc_config –update script.

101 uc_config update failed The update failed. Contact EMC Customer Service.

102 uc_config update succeeded The update succeeded.

../Replicator/index.htm


Index

AACL updates, email notification 51actions, that events trigger 25

CCallHome, when root file system nearly full 25Checkup faciliy 10community name, security 4

Eemail

notifications 19specifying a subject line 61troubleshooting 57

eventdefinition 3examples 6facility 6facility names 6ID, determining 23list of

ACLUPD 64ADMIN 65BoxMonitor 65CFS 75CHAMIIENCMON 75Checkup 76DPSVC 78DRIVERS 78FCP 80FSTOOLS 80JServer 81LIB 81LocalHardwareMonitor 82LOGCOLLECT 84MasterControl 88NASDB 89NaviEventMonitor 89RCPD 91REP 91SECURITY 91SNAPSURE_SCHED 92STORAGE 93SVFS 93UFS 94UPSMonitor 95USRMAP 99VC 99VMCAST 100VRPL 101XLT 102

log 10notification 10number 8severity level 9

throttling 11rearm 12resetafter 12threshold 11

event, controlling repetition of 11

Ffacility, See event, facilityfile system

size threshold exceededemail notification 34SNMP trap 34

fsSizeThreshold parameter 34

MMIB, modify for SNMP 26

Nnas_eventlog.cfg 10notification

configuration file 10custom configuration files 11customizing 11default 10definition 3, 10email

check if sendmail running 19configuring 19

loading configuration files 32verifying loaded configuration files 33

Pparameter, fsSizeThreshold 34

Rroot file system nearly full

CallHome generated 25

Ssecurity with SNMPv1 4sendmail, check if running 19server_snmp 30SnapSure SavVol high water mark reached

email notification 38SNMP trap 38

SNMPcommunity name 4configuring traps 27message types 13modify MIB 26security 13, 59traps 13verifying configuration 30

snmpwalk 30


Ttelephone

using to contact EMC Customer Service 57trap, SNMP 13trap.cfg 27troubleshooting 57

VVirus Checker events

email notification 42


Notes

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 from time to time releases new revisions of Celerra hardware and software. Therefore, some functions described in this document may not be supported by all revisions 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-2007 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.5 106 of 106

celerra network server configuring celerra events and notifications · 2020-03-09 · configuring...

Documents