EMC® Atmos™

Version 1.4.0

Administrator’s Guide

REV A01

EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
 Copyright © 2008 - 2010 EMC Corporation. All rights reserved.

Published October, 2010

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 regulatory document for your product line, go to the Technical Documentation and
Advisories section on EMC Powerlink.

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.

2 EMC Atmos Version 1.4.0 Administrator’s Guide

 Contents

Preface
Introduction ....................................................................................... 18

Chapter 1 Administrative Roles

Roles.................................................................................................... 22
SecurityAdmin ........................................................................... 22
SysAdmin.................................................................................... 22
TenantAdmin ............................................................................. 22
SubtenantAdmin........................................................................ 23
Authentication................................................................................... 23
Logging In .......................................................................................... 24
SecurityAdmin and SysAdmin Login .................................... 24
TenantAdmin and SubtenantAdmin Login........................... 25
Dashboards ........................................................................................ 26
Security Dashboard ................................................................... 26
System Dashboard..................................................................... 27
Tenant Dashboard ..................................................................... 28
Subtenant Dashboard................................................................ 29
SecurityAdmin Tasks ....................................................................... 30
Modifying the SecurityAdmin................................................. 30
Creating a SysAdmin ................................................................ 30
Deleting a SysAdmin ................................................................ 32

Chapter 2 Managing RMGs

Master node ....................................................................................... 34
Viewing Details about an RMG ...................................................... 34
Adding an RMG................................................................................ 35
Adding an Additional IS to an Existing RMG.............................. 35

EMC Atmos Version 1.4.0 Administrator’s Guide 3

Contents

Adding Additional Nodes to an RMG .......................................... 41

Viewing and Managing Details for a Node in an RMG.............. 42

Chapter 3 Configuring System Settings

Modifying a SysAdmin.................................................................... 46
Updating the Software Serial Number .......................................... 46
Configure Segments’ Hardware TLA ............................................ 47
Configuring NTP (Network Time Protocol)................................. 47
Configuring a Federation Target.................................................... 48
Configuring Security System-wide (Enabling/Disabling SSL) . 49
Configuring SSL Certificates System-wide................................... 50
Configuring MDS Remote Replication.......................................... 51

Chapter 4 Managing Tenants

Listing Tenants.................................................................................. 54
Creating a Tenant.............................................................................. 55
Controlling the tenant namespace directory structure ........ 55
Default policy............................................................................. 55
How to create a tenant .............................................................. 56
Configuring an LDAP server for remote authentication..... 58
Configuring OpenLDAP for UID secret storage................... 59
Configuring AD for UID secret storage ................................. 62
Making the shared secret store highly available................... 63
Managing an external shared secret store.............................. 63
Renaming a Tenant........................................................................... 64
Creating a TenantAdmin ................................................................. 65
Modifying a TenantAdmin ............................................................. 68
Deleting a TenantAdmin ................................................................. 69
Adding Nodes to a Tenant .............................................................. 70
Require SSL for Web Service connections.............................. 72
Configuring SSL Certificates for a Tenant ............................. 73

Chapter 5 Managing Subtenants

Listing Subtenants ............................................................................ 76
Creating a Subtenant ........................................................................ 76
Controlling the Subtenant Namespace Directory Structure 76
How to create a subtenant........................................................ 77
Renaming or Modifying a Subtenant............................................. 78
Creating a Unique ID and Assigning it to a Subtenant............... 80
Creating a SubtenantAdmin ........................................................... 80
Deleting a SubtenantAdmin............................................................ 83

4 EMC Atmos Version 1.4.0 Administrator’s Guide

 Contents

Chapter 6 Managing Policies

Overview ............................................................................................ 86
Policy-based Data Storage ............................................................... 86
Default policy..................................................................................... 88
Policy Specifications ......................................................................... 89
Metadata location....................................................................... 89
Replicas........................................................................................ 91
Retention/Deletion.................................................................... 98
Policy Selectors .................................................................................. 99
Assigning a Policy Selector to a Subtenant.................................. 102
Reordering Policies ......................................................................... 103

Chapter 7 System Monitoring, Events, & Reporting

Overview .......................................................................................... 106
Monitoring Atmos with your NMS.............................................. 106
Operational Reporting Framework .............................................. 107
Alerts ................................................................................................. 111
Email alerts....................................................................................... 112
SNMP support ................................................................................. 114
SNMP traps............................................................................... 114
Dell traps ................................................................................... 118
SNMP agent .............................................................................. 120
Configuring SNMP .................................................................. 120
Getting useful data from the MIBs ........................................ 124
System reports ................................................................................. 133
Configuring system reports.................................................... 133
SYR symptom codes ................................................................ 135
Collecting system reports ....................................................... 138
Log files and log collection ............................................................ 139

Chapter 8 Configuring NFS/CIFS Access

Overview .......................................................................................... 142
Configuring NFS ............................................................................. 142
Configuring CIFS ............................................................................ 145
Active Directory ....................................................................... 145
Configuring CIFS Node Properties ....................................... 147
Adding or Editing a CIFS Share............................................. 152

Chapter 9 Getting Performance Data

Overview .......................................................................................... 156

EMC Atmos Version 1.4.0 Administrator’s Guide 5

Contents

Example: Getting the Statistics ..................................................... 157

Request...................................................................................... 157
Response ................................................................................... 157
Browser Output ....................................................................... 158
Output Fields ........................................................................... 158
Example: Resetting the Counters ................................................. 159
Request...................................................................................... 159
Response ................................................................................... 160

Appendix A Atmos MIB

Atmos MIB Version Group ........................................................... 162
atmosMibMajorVersion.......................................................... 162
atmosMibMinorVersion ......................................................... 162
Atmos Software Version Group ................................................... 162
atmosVersion............................................................................ 162
Atmos Capacity Group .................................................................. 162
atmosNodeCapacityStorageCapacity................................... 162
atmosNodeCapacityStorageCapacityUnit........................... 162
atmosNodeCapacityStorageUsed ......................................... 163
atmosNodeCapacityStorageUsedUnit ................................. 163
atmosNodeCapacityStorageAvailable ................................. 163
atmosNodeCapacityStorageAvailableUnit.......................... 163
atmosNodeCapacityStoragePercentUsed ............................ 163
atmosNodeCapacityMetadataCapacity ............................... 163
atmosNodeCapacityMetadataCapacityUnit ....................... 164
atmosNodeCapacityMetadataUsed...................................... 164
atmosNodeCapacityMetadataUsedUnit.............................. 164
atmosNodeCapacityMetadataAvailable .............................. 164
atmosNodeCapacityMetadataAvailableUnit ...................... 164
atmosNodeCapacityMetadataPercentUsed......................... 164
atmosNodeCapacityDataCapacity........................................ 165
atmosNodeCapacityDataCapacityUnit................................ 165
atmosNodeCapacityDataUsed .............................................. 165
atmosNodeCapacityDataUsedUnit ...................................... 165
atmosNodeCapacityDataAvailable ...................................... 165
atmosNodeCapacityDataAvailableUnit .............................. 165
atmosNodeCapacityDataPercentUsed ................................. 166
Atmos Service Status Group ......................................................... 166
atmosServiceActiveEntries..................................................... 166
atmosServiceTable................................................................... 166
Atmos Metadata Service Group ................................................... 167
atmosMDSUpmasterCount.................................................... 167
atmosMDSContainerCount.................................................... 167

6 EMC Atmos Version 1.4.0 Administrator’s Guide

 Contents

atmosMDSReplicaGroupCount ............................................. 167

Atmos Storage Service Group ....................................................... 167
atmosSSDestageStatus............................................................. 168
Atmos Job Service Group............................................................... 168
atmosJSQueueStatus................................................................ 168
atmosJSQueueLength .............................................................. 168
atmosJSRecoverQueueLength................................................ 168
atmosJSRecoverDequeueRate ................................................ 168
atmosJSRecoverByteRate ........................................................ 168
atmosJSReclaimQueueLength................................................ 169
atmosJSReclaimDequeueRate ................................................ 169
atmosJSReclaimByteRate ........................................................ 169
atmosJSReplicateQueueLength.............................................. 169
atmosJSReplicateDequeueRate .............................................. 169
atmosJSReplicateByteRate ...................................................... 169
atmosJSVerifyQueueLength ................................................... 169
atmosJSVerifyDequeueRate ................................................... 170
atmosJSVerifyByteRate ........................................................... 170
Atmos Web Service Group ............................................................ 170
atmosWSReadsPerSec ............................................................. 170
atmosWSWritesPerSec ............................................................ 170
atmosWSDeletesPerSec ........................................................... 170
atmosWSTransPerSec .............................................................. 170
Atmos Notification Group ............................................................. 171
atmosNotificationVariables .................................................... 171
atmosNotificationCpuUsage .................................................. 171
atmosNotificationMemoryUsage .......................................... 172
atmosNotificationSwapUsage................................................ 172
atmosNotificationFilesystemUsage....................................... 172
atmosNotificationServiceMemoryUsage.............................. 172
atmosNotificationServiceStatus ............................................. 172
atmosNotificationInternalCarrierStatus ............................... 172
atmosNotificationExternalCarrierStatus .............................. 173
atmosNotificationNodeStatus................................................ 173
atmosNotificationSegmentStatus .......................................... 173
atmosNotificationRMGStatus ................................................ 173
atmosNotificationPolicySyncFailed ...................................... 173
atmosNotificationUidSyncFailed .......................................... 173
atmosNotificationDAEStatus ................................................. 173
atmosNotificationDAEBackplaneStatus............................... 174
atmosNotificationDAEFanStatus........................................... 174
atmosNotificationDAETempStatus....................................... 174
atmosNotificationDiskStatus.................................................. 174

EMC Atmos Version 1.4.0 Administrator’s Guide 7

Contents

atmosNotificationPolicyResourceStatus .............................. 174

atmosNotificationMgmtDBStatus......................................... 174
atmosNotificationDiskRecovery ........................................... 175
atmosNotificationVIPFailover ............................................... 175
Atmos Group Conformance Information ................................... 175
atmosMibVersionGroup......................................................... 175
atmosSoftwareVersionGroup ................................................ 175
atmosNodeCapacityGroup .................................................... 175
atmosServiceGroup ................................................................. 175
atmosMetadataServiceGroup ................................................ 176
atmosStorageServiceGroup.................................................... 176
atmosJobServiceGroup ........................................................... 176
atmosWebServiceGroup......................................................... 176
atmosNotificationVariableGroup.......................................... 176
atmosNotificationGroup ........................................................ 176
Atmos Conformance Information ................................................ 176
atmosCompliance .................................................................... 176

Appendix B MIB-II (RFC 1213)

MIB II overview .............................................................................. 178
Textual conventions ....................................................................... 178
Objects and types imported .......................................................... 179
System group................................................................................... 179
sysDescr ..................................................................................... 179
sysObjectID................................................................................ 179
sysUpTime................................................................................. 180
sysContact.................................................................................. 180
sysName..................................................................................... 180
sysLocation ................................................................................ 180
sysServices ................................................................................. 180
Interfaces group .............................................................................. 181
ifNumber.................................................................................... 181
ifTable......................................................................................... 181
ifEntry......................................................................................... 181
ifIndex ........................................................................................ 182
ifDescr ........................................................................................ 182
ifType.......................................................................................... 182
ifMtu ........................................................................................... 182
ifSpeed........................................................................................ 182
ifPhysAddress ........................................................................... 183
ifAdminStatus ........................................................................... 183
ifOperStatus............................................................................... 183
ifLastChange ............................................................................. 183

8 EMC Atmos Version 1.4.0 Administrator’s Guide

 Contents

ifInOctets ....................................................................................183
ifInUcastPkts..............................................................................184
ifInNUcastPkts ..........................................................................184
ifInDiscards................................................................................184
ifInErrors ....................................................................................184
ifInUnknownProtos ..................................................................184
ifOutOctets .................................................................................185
ifOutUcastPkts...........................................................................185
ifOutNUcastPkts .......................................................................185
ifOutDiscards.............................................................................185
ifOutErrors .................................................................................185
ifOutQLen ..................................................................................186
ifSpecific .....................................................................................186
AT Group.......................................................................................... 186
atTable ........................................................................................186
atEntry ........................................................................................186
atIfIndex .....................................................................................187
atPhysAddress...........................................................................187
atNetAddress.............................................................................187
IP group ............................................................................................ 187
ipForwarding.............................................................................187
ipDefaultTTL .............................................................................188
ipInReceives ...............................................................................188
ipInHdrErrors............................................................................188
ipInAddrErrors..........................................................................188
ipForwDatagrams .....................................................................189
ipInUnknownProtos .................................................................189
ipInDiscards...............................................................................189
ipInDelivers ...............................................................................189
ipOutRequests ...........................................................................189
ipOutDiscards............................................................................190
ipOutNoRoutes .........................................................................190
ipReasmTimeout .......................................................................190
ipReasmReqds ...........................................................................190
ipReasmOKs ..............................................................................190
ipReasmFails..............................................................................191
ipFragOKs ..................................................................................191
ipFragFails..................................................................................191
ipFragCreates.............................................................................191
ipAddrTable...............................................................................191
ipAddrEntry ..............................................................................192
ipAdEntAddr.............................................................................192
ipAdEntIfIndex..........................................................................192

EMC Atmos Version 1.4.0 Administrator’s Guide 9

Contents

ipAdEntNetMask...................................................................... 192
ipAdEntBcastAddr ................................................................... 192
ipAdEntReasmMaxSize ........................................................... 193
ipRouteTable ............................................................................. 193
ipRouteEntry ............................................................................. 193
ipRouteDest ............................................................................... 193
ipRouteIfIndex .......................................................................... 193
ipRouteMetric1 ......................................................................... 194
ipRouteMetric2 ......................................................................... 194
ipRouteMetric3 ......................................................................... 194
ipRouteMetric4 ......................................................................... 194
ipRouteNextHop ...................................................................... 194
ipRouteType .............................................................................. 195
ipRouteProto ............................................................................. 195
ipRouteAge................................................................................ 195
ipRouteMask ............................................................................. 195
ipRouteMetric5 ......................................................................... 196
ipRouteInfo................................................................................ 196
ipNetToMediaTable ................................................................. 196
ipNetToMediaEntry ................................................................. 197
ipNetToMediaIfIndex .............................................................. 197
ipNetToMediaPhysAddress ................................................... 197
ipNetToMediaNetAddress...................................................... 197
ipNetToMediaType .................................................................. 197
ipRoutingDiscards.................................................................... 198
ICMP group ..................................................................................... 198
icmpInMsgs ............................................................................... 198
icmpInErrors ............................................................................. 198
icmpInDestUnreachs................................................................ 198
icmpInTimeExcds ..................................................................... 198
icmpInParmProbs..................................................................... 199
icmpInSrcQuenchs ................................................................... 199
icmpInRedirects ........................................................................ 199
icmpInEchos .............................................................................. 199
icmpInEchoReps ....................................................................... 199
icmpInTimestamps................................................................... 199
icmpInTimestampReps............................................................ 199
icmpInAddrMasks ................................................................... 200
icmpInAddrMaskReps ............................................................ 200
icmpOutMsgs............................................................................ 200
icmpOutErrors .......................................................................... 200
icmpOutDestUnreachs............................................................. 200
icmpOutTimeExcds.................................................................. 200

10 EMC Atmos Version 1.4.0 Administrator’s Guide

 Contents

icmpOutParmProbs ..................................................................201
icmpOutSrcQuenchs.................................................................201
icmpOutRedirects .....................................................................201
icmpOutEchos ...........................................................................201
icmpOutEchoReps ....................................................................201
icmpOutTimestamps ................................................................201
icmpOutTimestampReps .........................................................201
icmpOutAddrMasks.................................................................202
icmpOutAddrMaskReps..........................................................202
TCP group ........................................................................................ 202
tcpRtoAlgorithm .......................................................................202
tcpRtoMin...................................................................................202
tcpRtoMax ..................................................................................203
tcpMaxConn ..............................................................................203
tcpActiveOpens .........................................................................203
tcpPassiveOpens .......................................................................203
tcpAttemptFails.........................................................................203
tcpEstabResets ...........................................................................204
tcpCurrEstab ..............................................................................204
tcpInSegs ....................................................................................204
tcpOutSegs .................................................................................204
tcpRetransSegs...........................................................................204
TCP Connection Table..............................................................204
tcpConnTable.............................................................................205
tcpConnEntry ............................................................................205
tcpConnState..............................................................................205
tcpConnLocalAddress..............................................................205
tcpConnLocalPort .....................................................................206
tcpConnRemAddress ...............................................................206
tcpConnRemPort.......................................................................206
tcpInErrs .....................................................................................206
tcpOutRsts..................................................................................206
UDP group ....................................................................................... 206
udpInDatagrams .......................................................................206
udpNoPorts................................................................................207
udpInErrors................................................................................207
udpOutDatagrams ....................................................................207
udpTable ....................................................................................207
udpEntry ....................................................................................207
udpLocalAddress......................................................................207
udpLocalPort .............................................................................208
EGP group ........................................................................................ 208
egpInMsgs................................................................................. 208

EMC Atmos Version 1.4.0 Administrator’s Guide 11

Contents

egpInErrors............................................................................... 208
egpOutMsgs ............................................................................. 208
egpOutErrors............................................................................ 208
egpNeighTable......................................................................... 208
egpAs......................................................................................... 211
Transmission group........................................................................ 211
SNMP group.................................................................................... 212
snmpInPkts................................................................................ 212
snmpOutPkts............................................................................. 212
snmpInBadVersions ................................................................. 212
snmpInBadCommunityNames .............................................. 212
snmpInBadCommunityUses................................................... 213
snmpInASNParseErrs .............................................................. 213
snmpInTooBigs ......................................................................... 213
snmpInNoSuchNames............................................................. 213
snmpInBadValues .................................................................... 213
snmpInReadOnlys.................................................................... 214
snmpInGenErrs......................................................................... 214
snmpInTotalReqVars ............................................................... 214
snmpInTotalSetVars................................................................. 214
snmpInGetRequests ................................................................. 214
snmpInGetNexts....................................................................... 215
snmpInSetRequests .................................................................. 215
snmpInGetResponses............................................................... 215
snmpInTraps ............................................................................. 215
snmpOutTooBigs...................................................................... 215
snmpOutNoSuchNames.......................................................... 215
snmpOutBadValues ................................................................. 216
snmpOutGenErrs...................................................................... 216
snmpOutGetRequests .............................................................. 216
snmpOutGetNexts.................................................................... 216
snmpOutSetRequests ............................................................... 216
snmpOutGetResponses ........................................................... 216
snmpOutTraps .......................................................................... 217
snmpEnableAuthenTraps ....................................................... 217

Appendix C Host Resources MIB (RFC 2790)

Host Resources System Group ..................................................... 220
hrSystemUptime...................................................................... 220
hrSystemDate ........................................................................... 220
hrSystemInitialLoadDevice.................................................... 220
hrSystemInitialLoadParameters............................................ 220
hrSystemNumUsers ................................................................ 221

12 EMC Atmos Version 1.4.0 Administrator’s Guide

 Contents

hrSystemProcesses ................................................................... 221

hrSystemMaxProcesses ........................................................... 221
Host Resources Storage Group ..................................................... 221
hrStorageTypes......................................................................... 221
hrMemorySize .......................................................................... 223
hrStorageTable.......................................................................... 223
Host Resources Device Group....................................................... 225
hrDeviceTypes.......................................................................... 225
hrDeviceTable........................................................................... 227
hrProcessorTable...................................................................... 229
hrNetworkTable ....................................................................... 230
hrPrinterTable........................................................................... 230
hrDiskStorageTable ................................................................. 231
hrPartitionTable ....................................................................... 232
hrFSTable................................................................................... 234
hrFSTypes.................................................................................. 235
Host Resources Running Software Group................................... 238
hrSWOSIndex ........................................................................... 239
hrSWRunTable ......................................................................... 239
Host Resources Running Software Performance Group ........... 240
hrSWRunPerfTable .................................................................. 240
Host Resources Installed Software Group................................... 241
hrSWInstalledLastChange ...................................................... 241
hrSWInstalledLastUpdateTime ............................................. 242
hrSWInstalledTable ................................................................. 242
Conformance information.............................................................. 243
hostResourcesMibModule ...................................................... 243
hrMIBCompliances .................................................................. 243
hrMIBGroups............................................................................ 243

Glossary

Index

EMC Atmos Version 1.4.0 Administrator’s Guide 13

Contents

14 EMC Atmos Version 1.4.0 Administrator’s Guide

 Figures

Title Page
1 SecurityAdmin and SysAdmin Login Page ............................................... 24
2 TenantAdmin and SubtenantAdmin Login Page...................................... 25
3 SecurityAdmin Dashboard ........................................................................... 26
4 System Dashboard ......................................................................................... 27
5 Tenant Dashboard .......................................................................................... 28
6 Subtenant Dashboard .................................................................................... 29
7 Update My Information ................................................................................ 30
8 Update My Information ................................................................................ 46
9 Tenant List....................................................................................................... 54
10 Upate My Information................................................................................... 69
11 Subtenant List ................................................................................................. 76
12 Policy Specification Page............................................................................... 89
13 Policy Specification Metadata Location Options ....................................... 90
14 Policy Specification Customize Options ..................................................... 93
15 Policy Specification Enable Stripe Options................................................. 95
16 Policy Specification Erasure Code Options ................................................ 96
17 Erasure Code Fragmentation Distribution ................................................. 97
18 Policy Specification Rentention and Deletion Options............................. 99
19 Policy Selector Page ..................................................................................... 100
20 Alert Information ......................................................................................... 111

EMC Atmos Version 1.4.0 Administrator’s Guide 15

Figures

16 EMC Atmos Version 1.4.0 Administrator’s Guide

 Preface

As part of an effort to improve and enhance the performance and capabilities

of its product lines, EMC periodically releases revisions of its hardware and
software. Therefore, some functions described in this document may not be
supported by all versions of the software or hardware currently in use. For
the most up-to-date information on product features, refer to your product
release notes.
If a product does not function properly or does not function as described in
this document, please contact your EMC representative.

Note: This document was accurate as of the time of publication. However, as

information is added, new versions of this document may be released to the
EMC Powerlink website. Check the Powerlink website to ensure that you are
using the latest version of this document.

Preface 17
Preface

Introduction
Audience This document is part of the Atmos documentation set, and is
intended for use by system administrators who are responsible for
installing, configuring, and maintaining Atmos.

Related The following EMC publications provide additional information:

documentation
◆ EMC Atmos Release Notes
◆ EMC Atmos Conceptual Overview
◆ EMC Atmos Installation Guide
◆ EMC Atmos Administrator’s Guide
◆ EMC Atmos Programmer’s Guide
◆ EMC Atmos System Management API Guide
◆ EMC Atmos Security Configuration Guide
◆ EMC Atmos Non-EMC Software License Agreements
◆ EMC Atmos Hardware Guide
◆ EMC Atmos online help

Conventions used in EMC uses the following conventions for special notices:
this document
Note: A note presents information that is important, but not hazard-related.

! CAUTION
A caution contains information essential to avoid data loss or
damage to the system or equipment.

! IMPORTANT
An important notice contains information essential to software or
hardware operation.

18 EMC Atmos Version 1.4.0 Administrator’s Guide

 Preface

Typographical conventions
EMC uses the following type style conventions in this document.
Normal Used in running (nonprocedural) text for:
• Names of interface elements (such as names of windows,
dialog boxes, buttons, fields, and menus)
• Names of resources, attributes, pools, Boolean expressions,
buttons, DQL statements, keywords, clauses, environment
variables, functions, utilities
• URLs, pathnames, filenames, directory names, computer
names, filenames, links, groups, service keys, file systems,
notifications
Bold Used in running (nonprocedural) text for:
• Names of commands, daemons, options, programs,
processes, services, applications, utilities, kernels,
notifications, system calls, man pages
Used in procedures for:
• Names of interface elements (such as names of windows,
dialog boxes, buttons, fields, and menus)
• What user specifically selects, clicks, presses, or types
Italic Used in all text (including procedures) for:
• Full titles of publications referenced in text
• Emphasis (for example a new term)
• Variables
Courier Used for:
• System output, such as an error message or script
• URLs, complete paths, filenames, prompts, and syntax when
shown outside of running text
Courier bold Used for:
• Specific user input (such as commands)
Courier italic Used in procedures for:
• Variables on command line
• User input variables
<> Angle brackets enclose parameter or variable values supplied by
the user
[] Square brackets enclose optional values
| Vertical bar indicates alternate selections - the bar means “or”
{} Braces indicate content that you must specify (that is, x or y or z)
... Ellipses indicate nonessential information omitted from the
example

Introduction 19
Preface

Where to get help EMC support, product, and licensing information can be obtained as
follows.
Product information — For documentation, release notes, software
updates, or for information about EMC products, licensing, and
service, go to the EMC Powerlink website (registration required) at:
http://Powerlink.EMC.com
Technical support — For technical support, go to Powerlink and
choose Support. On the Support page, you will see several options,
including one for making a service request. Note that to open a
service request, you must have a valid support agreement. Please
contact your EMC sales representative for details about obtaining a
valid support agreement or with questions about your account.

Your comments Your suggestions will help us continue to improve the accuracy,
organization, and overall quality of the user publications. Please send
your opinions of this document to:
[email protected]

20 EMC Atmos Version 1.4.0 Administrator’s Guide

 1

Administrative Roles

This chapter describes the different administrative roles in the EMC®

Atmos™ system, their creation sequence, and how they work
together.
◆ Roles..................................................................................................... 22
◆ Authentication .................................................................................... 23
◆ Logging In ........................................................................................... 24
◆ Dashboards ......................................................................................... 26
◆ SecurityAdmin Tasks ........................................................................ 30

Administrative Roles 21
Administrative Roles

Roles
The system supports four administrative roles: SecurityAdmin,
SysAdmin, TenantAdmin, and SubtenantAdmin.

SecurityAdmin The SecurityAdmin is a built-in super-user responsible for initial

installation and creating SysAdmins.
During the installation process, the SecurityAdmin does the
following:
◆ Resets the default SecurityAdmin password.
◆ Creates a SysAdmin role, which is then used to complete the
installation. This is the only SysAdmin until and unless others are
added.
The system supports only one SecurityAdmin.

SysAdmin The SysAdmin role is responsible for overall management of an

Atmos system, including management of segments, RMGs, and
nodes; changing faulty disks; and adding new hardware. Specified
users may be assigned the SysAdmin role.
SysAdmins also can create new tenants, which are logical
compartmentalizations of data and resources. Associated with a
tenant are specific access nodes, security control, and storage policies.
A tenant is configured with Web-service or file-system access to
specific nodes.
Users who are assigned the SysAdmin role may be authenticated
against either the internal authentication source maintained by the
Atmos system (referred to as local authentication) or an external
authentication source maintained by the customer (referred to as
remote authentication). To use an external authentication source,
additional configuration must be completed.
Multiple users may be assigned the SysAdmin role.

TenantAdmin The TenantAdmin role is responsible for managing subtenants, and

policies for the tenant to which they are assigned. The SysAdmin
assigns specific users the TenantAdmin role within a given tenant.
Policies are assigned by the TenantAdmin to a specific subtenant.
TenantAdmins are unaware of system resources other than those

22 EMC Atmos Version 1.4.0 Administrator’s Guide

 Administrative Roles

defined for their tenant and have no ability to access system resources
except those assigned to their tenant. A TenantAdmin also can do
anything that a SubtenantAdmin can do.
A TenantAdmin registers applications (which involves adding new
applications on the Atmos system by generating a UID/Shared
Secret) and adds policies for the corresponding applications.
A given tenant can have multiple TenantAdmins, but a given
TenantAdmin can be a TenantAdmin for only one tenant.

SubtenantAdmin Subtenants are logical partitions of tenants that group together

selected policies, data access, and reporting capabilities. Each
subtenant has a unique set of users and sees a unique set of data. A
given object can be seen by only one subtenant. When the SysAdmin
creates a tenant, the system automatically creates one corresponding
subtenant (which is identical to the tenant). SysAdmins can choose to
create additional subtenants within each tenant. SubtenantAdmins
assign users to a subtenant.
A SubtenantAdmin can only create a unique ID and assign it to a
subtenant.

Authentication
Authentication may depend on the internal authentication source
maintained by the Atmos system (referred to as local authentication)
or an external authentication source maintained by the customer.
(referred to as remote authentication).
The authentication service comprises multiple authentication servers
(one master and several read-only slaves). If the master
authentication server temporarily is unavailable (for example,
because it is down or there is a network disconnection), a failover
process is triggered. This occurs only rarely. Complete failover takes
some time (roughly 15 minutes, depending on the size and
configuration of your system). While failover is in progress, users can
be authenticated against only those authentication servers which are
up. During the failover window, while the master authentication
server is unavailable, write operations (adding and deleting
system-management users) will fail.

Authentication 23
Administrative Roles

Logging In
Access to the GUI is through a browser. Atmos supports Internet
Explorer. For supported versions of the browser and other software
related to Atmos, see the EMC Atmos Installation Guide.

SecurityAdmin and In an Internet Explorer window, enter the URL

SysAdmin Login https://hostname/mgmt_login. Alternately, if you already are
logged in as a TenantAdmin or SubtenantAdmin, log out, then click
the Switch to SystemAdmin login page link on the
TenantAdmin/SubtenantAdmin login page.
The login page for SecurityAdmin and SysAdmin appears as shown
in Figure 1.

Figure 1 SecurityAdmin and SysAdmin Login Page

24 EMC Atmos Version 1.4.0 Administrator’s Guide

 Administrative Roles

Login credentials are case sensitive. Enter the following fields:

◆ Auth Type — Local
◆ User Name — SecurityAdmin/SysAdmin name (the default for
SecurityAdmin is SecurityAdmin)
◆ Password — SecurityAdmin/SysAdmin password (the default
for SecurityAdmin is #1Passwd)

TenantAdmin and In an Internet Explorer window, enter the URL https://hostname.

SubtenantAdmin Alternately, if you already are logged in as a SecurityAdmin or
Login SysAdmin, log out, then click the Switch to TenantAdmin login page
link on the SecurityAdmin/SysAdmin login page.
The login page for TenantAdmin and SubtenantAdmin appears as
shown in Figure 2.

Figure 2 TenantAdmin and SubtenantAdmin Login Page

Login credentials are case sensitive. Enter the following fields:

◆ Tenant — Tenant name
◆ Subtenant — Subtenant name
◆ User Name — TenantAdmin/SubtenantAdmin name
◆ Password — TenantAdmin/SubtenantAdmin password

Logging In 25
Administrative Roles

If you forget your password, click the Forgot Password link on the
login page. Your password will be mailed to you, if an email address
is specified for your admin role and an SMTP server is set up.

Dashboards
Since each role has different privileges, each type of admin sees a
different dashboard after logging in.

Security Dashboard When a SecurityAdmin logs into Atmos, the Security Dashboard
appears as shown in Figure 3.

Figure 3 SecurityAdmin Dashboard

26 EMC Atmos Version 1.4.0 Administrator’s Guide

 Administrative Roles

System Dashboard When a SysAdmin logs into Atmos, the System Dashboard appears
as shown in Figure 4.

Figure 4 System Dashboard

Dashboards 27
Administrative Roles

Tenant Dashboard When a TenantAdmin logs into Atmos, the Tenant Dashboard
appears as shown in Figure 5.

Figure 5 Tenant Dashboard

28 EMC Atmos Version 1.4.0 Administrator’s Guide

 Administrative Roles

Subtenant When a SubtenantAdmin logs into Atmos, the Subtenant Dashboard

Dashboard appears as shown in Figure 6.

Figure 6 Subtenant Dashboard

Dashboards 29
Administrative Roles

SecurityAdmin Tasks
This section explains how the SecurityAdmin uses the Atmos
system-management GUI to manage SecurityAdmins and
SysAdmins.

Modifying the To view or modify SecurityAdmin information, login as a

SecurityAdmin SecurityAdmin and click Update My Information in the Navigation
pane. Figure 7 shows the Update My Information page. Use this page
to change passwords and other information about your
SecurityAdmin account.
Required fields are marked with red asterisks on the page.

Figure 7 Update My Information

Creating a To create a SysAdmin—that is, to assign the SysAdmin role to a

SysAdmin user—follow these steps:
1. Login as SecurityAdmin. The Security Dashboard appears.
Click Add. The Assign System Admin Role page appears.

2. Choose an Authentication Source (Local or Remote).

30 EMC Atmos Version 1.4.0 Administrator’s Guide

 Administrative Roles

The system lets you authenticate user accounts locally (internal)

to the platform or remotely (external), using a preconfigured
LDAP server.
• If Local is selected, the authentication source is the Atmos
system; skip to step 5.
• Remote authentication requires additional configuration: if
your site requires external, centralized authentication, you
need to enter the configuration details to enable access. If you
choose remote authentication, an Authentication Address
field appears.
3. The Authentication Source field contains either a drop-down list
(if LDAP servers are already configured) or a message: “No
remote authentication source available.” If there is a drop-down
list, select a remote authentication source; otherwise, you must
configure an LDAP server.

Note: Only LDAP is supported as a remote authentication mechanism

for administrators.

4. Enter a User Name and click Assign. If the user does not already
exist, you are prompted to add it.
When you create a SysAdmin and specify a Local authentication
source, the server checks whether the user you input exists; if not,
it prompts you to add the user. If you specify a Remote
authentication source, the server does not check whether the user
exists.
In this case, because the authentication source is Local and the user
name does not exist in the system, you are asked to add the new
(local) user.

SecurityAdmin Tasks 31
Administrative Roles

Click OK. The Add New User page appears.

5. Enter the required User Name, Password, and Confirm

Password fields and any optional fields.
Although the Email field is optional, it is recommend that you
use it. If the new SysAdmin forgets his password, he can get it
emailed to him—but only if you fill in this field.
Click Add. The user is added as a SysAdmin and now appears on
the Security Dashboard.

Note: For operations that create/modify system-management users, or

assign an administrative role (SysAdmin, TenantAdmin, or
SubtenantAdmin) to a user, there is a slight delay before the effect of the
operation is visible on all Atmos nodes, while the Atmos system is
synchronized.

Deleting a To delete a SysAdmin, follow these steps:

SysAdmin 1. Login as SecurityAdmin. The Security Dashboard appears.
2. In the row for the SysAdmin you want to remove, click Remove
Role.
3. In the pop-up dialog asking you to confirm, click OK.

32 EMC Atmos Version 1.4.0 Administrator’s Guide

 2

Managing RMGs

This chapter describes how to access the functions for managing

RMGs through the System Dashboard.
Throughout this chapter, required fields are marked with red
asterisks on the page.
◆ Master node ........................................................................................ 34
◆ Viewing Details about an RMG ....................................................... 34
◆ Adding an RMG ................................................................................. 35
◆ Adding an Additional IS to an Existing RMG ............................... 35
◆ Adding Additional Nodes to an RMG............................................ 41
◆ Viewing and Managing Details for a Node in an RMG ............... 42

Managing RMGs 33
Managing RMGs

Master node
The master node is the first node installed in each installation segment.
It always has -001 appended to its node name. When a new RMG is
added to the system, it has one installation segment, hence one
master node. If more installation segments are added to that RMG
later, there are more master nodes: an RMG with N installation
segments has N master nodes.
The initial master node is the first node installed in the first installation
segment in the first RMG in the system (during system installation).
This is the node where the SysAdmin must login.

Viewing Details about an RMG

1. Login as SysAdmin. The System Dashboard appears. The RMG
List area of the System Dashboard lists all RMGs in this Atmos
system and the location of each RMG.
2. In the RMG List area, click Detail for a given RMG. The RMG
Summary page for that RMG appears.

The yellow warning triangles in the Name column indicate that

there are new, unacknowledged alerts for the node. For details,
click the node’s Name.

34 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing RMGs

Service Status indicates whether the node is up (green), down

(red), configuring ("Configuring"), or if the node replacement has
failed ("Replacement Failed"). For details, click the node’s Name.

Adding an RMG
An RMG is a collection of segments that share a single domain and
location identifier. There are three main steps to add an RMG:
◆ Step 1: Launch Atmos Installation on the Master Node (VMware
or physical hardware)
◆ Step 2: Install the Atmos Appliance on the Master Node
◆ Step 3: Add the New RMG
For more information on adding a new RMG, see the EMC Atmos
Installation Guide.

Adding an Additional IS to an Existing RMG

Note: For VMware Installations, each installation segment must use its
own switch for the private network. Before adding an installation
segment here, ensure that it will use a different switch for the private
network than any installation segments that are already installed.

To add an installation segment:

1. Login as SysAdmin to the initial master node. The System
Dashboard appears.
2. In the RMG List area, click Detail for the RMG to which you
want to add an installation segment.
3. In the Operations area, click Add Segment. The Target Segment
Configuration page appears.

Adding an RMG 35
Managing RMGs

4. Choose a segment to configure and click Next. The Network

Configuration page appears.

5. Complete the fields as described in the following table.

Field Description

Platform type Select your platform type from the dropdown list:
• Server with DAE (external disk cabinet)
• Server without DAE (internal storage only)
• VMWare (VMWare node, no real disks)

IP Range From/To Specify the public IP addresses for nodes in this

installation segment. Enter the upper IP address for
the network. The number of IP addresses you specify
in this range represents the number of nodes in the
installation segment.

36 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing RMGs

Field Description

Subnet Mask Enter a subnet mask that identifies the local network
addresses defined for the IP Range.

Default Gateway Enter the gateway address. This is critical if you plan
to access Atmos through the public network.

Hostname Prefix Enter the hostname prefix associated with the IS. The
system adds a hyphen after the prefix and before a
three-digit, system-generated serial number.
The following characters are valid for this field:
• The first character must be an alphabetic
character.
• Characters following the first character can be one
or more: alpha (a-z,A-Z), number (0-9), dot (.),
underscore (_), hyphen (-).
• The last character must be an alphabetic
character or a number.

DNS Server Enter the IP address of the name server on the public
interfaces.

Search DNS Suffix Enter a value which will be appended to a domain

name that is not fully qualified. For example, entering
company.com here would cause the name www to be
looked up as www.company.com. As another
example, www.emc.com is fully qualified and would
be looked up as is.

NTP Server An NTP server helps synchronize application servers

and Atmos nodes. EMC strongly recommends that
you use an external NTP.
You can specify one of the following:
Local NTP Server— Select this option when you
want to use the Atmos-supplied NTP server.
Remote NTP Server —Select this option when you
want to specify an external NTP server.

6. Click Next. The Application Configuration page appears. You use

it to set up your storage and metadata servers.

Adding an Additional IS to an Existing RMG 37

Managing RMGs

Use the slider bar to specify whether Atmos will perform more
large-file operations or small-file operations. Since each
object/file has a fixed amount of metadata, large files have less
metadata as a percentage of their size than small files. The ratio
specified here determines the number of drives per node
allocated to metadata versus user data.
Choose one of the following ways to proceed:
• Click Next, and a default, overall configuration pattern is
auto-generated for the system.
• Click Manual Customize to configure each node in the
system. Use the Manual Customize page to define the disk
ratio, placement, and action-type storage requirements for
each node. Your policy specifications must reflect the storage
definitions defined in this setup.
The Manual Customize page is shown below.

38 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing RMGs

The Manual Customize fields are as follows:

Field Description

Disk ratio The initial value in this field reflects your slider bar settings on the
Application Configuration page.
In a valid metadata:data disk ratio, the metadata part of the ratio is less
than or equal to the data part of the ratio.
When you enter a valid ratio, it gets propagated to the grayed-out fields in
the Disk Ratio column.

Placement Specify how the storage service allocates new objects to the physical disks
under its management by selecting one of the following values from the
dropdown:
• OPTIMAL — Round robin: rotate requests equally among all available
storage disks. This is the default.
• GREEN — Only one or a few disks are active; the rest are spun down for
energy conservation. When the active disks fill up, the spun-down disks
are woken up and used.
• BALANCED — Pick the disk with the most available space.

Note: In a VMWare installation, GREEN is not supported.

Adding an Additional IS to an Existing RMG 39

Managing RMGs

Field Description

Action Type This specifies the data-at-rest services applied to Storage Servers:
• None — No services; normal writes and reads. This is the default.
• Checksum — The Storage Server generates a checksum for all data
saved on it. When the data is read, the checksum is verified. When the
data is re-written, the old data also is verified.
• Compression — Data is compressed on write and decompressed on
read. This conserves disk space but introduces processing overhead on
the server, so typically it has a negative impact on performance.
Compression can be used successfully for objects that are written once
and accessed rarely.
• Deduplication — Deduplication: multiple copies of the data are
removed, and only one copy of the data is maintained. This is intended to
conserve storage capacity.
• CompressionDedup — Combination of Compression and
Deduplication.

Note: Checksum, Compression, Deduplication, or CompressionDedup

must be specified here if you want to use any of them later, when creating a
policy specification.

7. Click Next to display the Configuration Summary page.

8. Click Next to install the master node. The Installation of the
Master Node page appears. Depending on your installation, the
page has either a Next button or a Finish button.

When the installation is in the Configuring the machine for

network communication stage, you are prompted by a Security
Alert page for a security certificate — In this case, choose View

40 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing RMGs

Certificate (you will see it is configured with the Atmos master

node name), then Install Certificate (it is added as a Trusted Root
certificate for your browser). Click OK to proceed with the
remaining stages of the installation.
If there is an error during installation of the master node, two
more buttons appear on the page: Restart and Restart from
Failure Point. Click the appropriate button restart the installation
process for the master node from the beginning or from the point
of failure, respectively.
9. Click Finish.

Adding Additional Nodes to an RMG

When you add an RMG, you can choose to install only some of the
nodes you specify for that RMG. Use the procedure below to install
the additional nodes in that RMG later.

Note: Adding or discovering physical nodes is not supported in the Atmos

Virtual Edition.

1. Login as SysAdmin. The System Dashboard appears.

2. In the RMG List area, click Detail for a given RMG. The RMG
Summary page for that RMG appears.
3. In the Operations area, click Add Node. The Add New Node &
View Installation Status page appears, displaying a list of known
nodes in the RMG and their status.

4. Click Discover New Nodes, and the master node in the first
installation segment in the RMG interrogates the RMG for slave
nodes that respond (via IPMI, Intelligent Platform Management

Adding Additional Nodes to an RMG 41

Managing RMGs

Interface) but are not in the list of installed nodes. These are nodes
that are physically connected to the system and to power, but are
not yet installed or powered on.
The list of new nodes is presented. Use Install or Install All
Nodes to install new nodes individually or collectively.

Viewing and Managing Details for a Node in an RMG

1. Login as SysAdmin. The System Dashboard appears.
2. In the RMG List area, click Detail for a given RMG. The RMG
Summary page for that RMG appears.
3. From the Node List area, click the link for the node you want to
view in detail. The node dashboard appears.
The information on the node dashboard differs somewhat,
depending on whether it is for a master node or a slave node. The
dashboard for a slave node is as follows:

42 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing RMGs

Viewing and Managing Details for a Node in an RMG 43

Managing RMGs

The page displays a variety of information for the node. The

Operations area displays the functions you can perform on the
node:
• Power On/Off — Turn the node on or off (not supported in
the Atmos Virtual Edition). Powering off a node that has not
been properly shutdown can result in unexpected results. To
properly shutdown a node, login as root and run the system
shutdown command. The Power Off command should only be
used under the advice of EMC Customer Support or after you
are sure the operating system has been correctly stopped.
• Restart — Reboot the node (not supported in the Atmos
Virtual Edition).
• Collect Log — Collect the system log of the node. (You may be
asked to do this if a log is needed for debugging purposes. In
that case, after the log file is collected, you would be directed
to send it to EMC.)
• Go to Maintenance Mode — Not currently supported.
Maintenance mode stops all Atmos services; you can then
disconnect the node and perform maintenance. Production
mode restores all Atmos services.
• Beacon On, Beacon Off — Turn the node LCD light on or off
(not supported in the Atmos Virtual Edition).
• Replace — Reinstall the node using DHCP to retrieve an IP
address. This applies only to slave nodes (not supported in the
Atmos Virtual Edition).
In addition to Operations, the page has several other areas: Alert
Information, Filesystem Information, Disk Information, Task
Information, and Graphs.

44 EMC Atmos Version 1.4.0 Administrator’s Guide

 3
Configuring System
Settings

This chapter describes how to access and configure system settings.

This chapter describes the following topics:
◆ Modifying a SysAdmin ..................................................................... 46
◆ Updating the Software Serial Number ........................................... 46
◆ Configure Segments’ Hardware TLA ............................................. 47
◆ Configuring NTP (Network Time Protocol) .................................. 47
◆ Configuring a Federation Target ..................................................... 48
◆ Configuring Security System-wide (Enabling/Disabling SSL)... 49
◆ Configuring SSL Certificates System-wide .................................... 50
◆ Configuring MDS Remote Replication ........................................... 51

Configuring System Settings 45

Configuring System Settings

Modifying a SysAdmin
To view or modify SysAdmin information, login as a SysAdmin and
click Update My Information in the Navigation pane. The Update My
Information page appears as shown in Figure 8. Use this page to
change passwords and other information about your SysAdmin
account.
Required fields are marked with red asterisks on the page.

Figure 8 Update My Information

Updating the Software Serial Number

The software serial number is used as an access key when
configuring system reporting of Atmos configuration data. For more
information, see “Configuring MDS Remote Replication” on page 51.
The software serial number must be configured before system
reporting can be configured.
1. Login as SysAdmin. The System Dashboard appears.
2. In the Operations area, click Update Software Serial Number.
The Update Software Serial Number page appears.

3. Enter the software serial number and click Submit.

46 EMC Atmos Version 1.4.0 Administrator’s Guide

 Configuring System Settings

Configure Segments’ Hardware TLA

The Segments’ Hardware TLA (top level assembly) number is used
when sending system reports of Atmos configuration data to EMC.
To configure the Segments’ Hardware TLA:
1. Login as SysAdmin. The System Dashboard appears.
2. Under RMG List, click Detail. The RMG Summary page appears.
3. Under Operations, click Configure Segments’ Hardware TLA.
The Configure Segments’ Hardware TLA page appears.

4. Enter the number and click Submit.

Configuring NTP (Network Time Protocol)

Atmos requires strong time synchronization internally (between
Atmos nodes), and externally between any machines running the
Atmos file system and the Atmos system. The Atmos system
implements internal time synchronization, but EMC recommends
that you augment it with a high-quality external NTP server
(especially for production systems). For more information about
configuring an external NTP server, see the EMC Atmos Installation
Guide.
1. Login as SysAdmin. The System Dashboard appears.
2. In the Operations area, click NTP Configuration. The NTP
Configuration page appears.

Configure Segments’ Hardware TLA 47

Configuring System Settings

3. Select the type of NTP Server, either Remote (the nodes

synchronize to a standard reference) or Local (the nodes
synchronize to each other but not to a standard reference).
4. Specify the NTP Server host name or address. Here, we use
pool.ntp.org, which supplies multiple address from a pool, which
distributed the load and is more reliable. This is a publicly
available resource on the Internet
5. Click Submit.

Configuring a Federation Target

If you configure a federation target, the TenantAdmin can define a
policy with a replica in that targeted location, that is outside this
Atmos system.
Follow these steps:
1. Login as SysAdmin, then click Federation Configuration in the
Navigation pane. The Cloud Federations page appears initially
empty, as shown below.

2. Click Add. The Federation Configuration page appears.

3. Fill out the fields on the page:

• Type — Currently, this always is Atmos onLine.
• Name — Specify a name for this target.

48 EMC Atmos Version 1.4.0 Administrator’s Guide

 Configuring System Settings

• Address — IP address, fully qualified domain name, or

hostname for this target. (If a fully qualified domain name or
hostname is used, it must be resolvable by Atmos nodes.)
• Full Token ID — A combination of subtenant ID and a UID
within that subtenant, both in the Atmos onLine system that is
being targeted. The format is subtenant ID/UID.
• Shared Secret — Shared secret for the UID, in the Atmos
onLine system that is being targeted.
4. Click Submit. You are returned to the Cloud Federations page,
which now shows the target you just configured.

Configuring Security System-wide (Enabling/Disabling SSL)

If the Secure Sockets Layer (SSL) protocol on access nodes using Web
Services is enabled, Atmos SOAP and REST interfaces can be
accessed only by HTTPS. When Web Service SSL is disabled, Atmos
SOAP and REST interfaces can be accessed by HTTP. By default, SSL
is enabled.
SSL should be enabled unless one of the following is true”
◆ You secured the connection between the client and server in
another way.
◆ Performance is more important than privacy protection for the
data passing between the client and server (for example, if you
are passing unimportant test data).
To change the SSL enablement setting for Web-service access on all
nodes, follow the steps below. (To change the SSL enablement setting
on all nodes assigned to a specific tenant, see “Configuring SSL
Certificates for a Tenant” on page 73.)
1. Login as SysAdmin. The System Dashboard appears.

Configuring Security System-wide (Enabling/Disabling SSL) 49

Configuring System Settings

2. In the Operations area, click Security Configuration. The

Security Configuration page appears.

3. Specify the setting using the Enable or Disable button

(whichever is active).
4. Click Back to return to the System Dashboard.

Note: To change the SSL enablement setting for Web-service access

on all nodes assigned to a specific tenant, see “Require SSL for Web
Service connections” on page 72.

Configuring SSL Certificates System-wide

Servers use certificates for creating an SSL while communicating with
each other over networks. By default, Atmos uses a self-signed
certificate for SSL connections. For the best security, we recommend
you replace the default Atmos certificate with one of your own,
signed by your trusted Certificate Authority (CA).
To configure your own SSL certificates for Web-services access on all
nodes, follow the steps below. (To configure SSL certificates on all
nodes assigned to a specific tenant, see “Configuring SSL Certificates
for a Tenant” on page 73.)
1. Login as SysAdmin. The System Dashboard appears.

50 EMC Atmos Version 1.4.0 Administrator’s Guide

 Configuring System Settings

2. In the Operations area, click SSL Configuration. The Update

Management GUI SSL Certificate page appears.

3. Follow the procedure in “Configuring SSL Certificates for a

Tenant” on page 73.

Configuring MDS Remote Replication

When Atmos is installed, there are two MDS instances running on
two different nodes in the same RMG, in a master-slave mode. The
master MDS replicates its data to the slave MDS. If this RMG goes
offline (for example, due to a power or network outage), all objects
owned by this MDS pair are unavailable to the user. The MDS remote
replica feature enables you to configure a secondary RMG location to
replicate metadata. Then, if the primary RMG becomes unavailable,
Atmos can read from the secondary RMG.
1. Login as SysAdmin. The System Dashboard appears.
2. In the Operations area, click MDS remote replica. The MDS
Remote Replica Configuration page appears.

3. Select values for Installation Segment 1 and Installation

Segment 2 from the drop-down lists. (These are installation
segments.)

Configuring MDS Remote Replication 51

Configuring System Settings

The two installation segments must be in different RMGs. The

GUI enforces this requirement: after you select Installation
Segment 1, the drop-down list for Installation Segment 2
changes, so it does not contain any installation segments in the
same RMG as Installation Segment 1.
4. Click Add. The new configuration is listed on the page.

52 EMC Atmos Version 1.4.0 Administrator’s Guide

 4

Managing Tenants

This chapter describes how to access the functions for managing

tenants through the System Dashboard. This chapter describes the
following topics:
◆ Listing Tenants ................................................................................... 54
◆ Creating a Tenant............................................................................... 55
◆ Renaming a Tenant ............................................................................ 64
◆ Creating a TenantAdmin .................................................................. 65
◆ Modifying a TenantAdmin............................................................... 68
◆ Deleting a TenantAdmin................................................................... 69
◆ Adding Nodes to a Tenant ............................................................... 70

Managing Tenants 53
Managing Tenants

Listing Tenants
Login as SysAdmin, then click Tenant List in the Navigation pane.
The Tenant List page appears as shown in Figure 9.

Figure 9 Tenant List

This Tenant List page shows a Tenant Admin named t1admin already
was created. Each Name in the Tenant List is a tenant ID; each tenant
has a unique ID that is required at login. You first create a tenant, then
assign TenantAdmins to the tenant.
In this example, for the tenant named t2, the Tenant Admin column
indicates No Tenant Admin, meaning no TenantAdmin role is
assigned to this tenant. To complete this tenant, you must assign a
TenantAdmin role and one or more nodes to this tenant. For more
information, see “Creating a TenantAdmin” on page 65 and “Adding
Nodes to a Tenant” on page 70.

54 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Tenants

Creating a Tenant
When you create a tenant in the system-management GUI, a default
subtenant automatically is created under it. That default subtenant
has the same name, ID, and Authentication Source as the tenant.
Default subtenants cannot be deleted.

Controlling the Each tenant owns a namespace—comprising files and

tenant namespace directories—that is independent of the namespaces of other tenants.
directory structure At the top of the tenant namespace is a tenant root directory, which
Atmos creates when a new tenant is created. The location of the
tenant root directory is the same as the location (RMG) where the
operation for tenant creation was invoked through the
system-management GUI or CLI. Under the tenant root directory are
subtenant root directories. Under the subtenant root directories are
the files and directories created by user applications.
Atmos distributes the namespace to best utilize system resources.
Efficient management of the namespace is very important for overall
system performance. EMC recommends that you balance the
namespace; for example one directory should not contain all or a
large portion of all files.
Namespace considerations are similar for both Atmos file-system
access and Web services access with namespace addressing.

Default policy Whenever a tenant is created (during Atmos installation or later), a

default policy specification is created for that tenant. The default
policy specification, named “default,” is listed on the Tenant
Dashboard. It is defined to have two synchronous replicas, with no
location or server attribute constraints. It is applied to all objects that
do not match any user-defined policy selector. If required, the
TenantAdmin can modify the default policy specification for a tenant.
The default policy for a tenant applies to all subtenants under that
tenant. An Atmos system can operate only with a default policy.

Creating a Tenant 55
Managing Tenants

How to create a 1. Login as SysAdmin, then click Create Tenant in the Navigation
tenant pane. The Create Tenant page appears.

2. Choose an Authentication Source (Local or Remote).

• Local authentication lets you authenticate tenant accounts
locally (internal) to the platform.
• Remote authentication requires additional configuration: if
your site requires external, centralized authentication, you
need to enter the configuration details to enable access.

Note: This authentication source applies to TenantAdmins created

within this tenant. See “Creating a TenantAdmin” on page 65.

The Authentication Address field contains either a drop-down

list (if LDAP servers are already configured) or a message: “No
remote authentication source available,” as shown below. To
configure an LDAP server, see “Configuring an LDAP server for
remote authentication” on page 58.

3. Enter a Tenant Name, which must be unique and no more than 30

characters.

56 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Tenants

4. Select a UID Shared Secret Store Provider. In order for Atmos to

authenticate REST and SOAP requests, Atmos must securely
store the shared secrets associated with each UID. Atmos has two
methods for storing UID shared secrets:
• LockBox—Atmos internal secret store (keystore). This is an
encrypted file maintained on the Atmos nodes. It is ideal for
small environments or test systems that do not have access to
an external LDAP server. For environments where the number
of UIDs exceed 500, it is recommended that shared secrets are
stored in an external LDAP server.
• LDAP—External LDAP server. Only OpenLDAP 2.4 and AD
are supported. The target LDAP server must be properly
configured with schema extensions before it can be used. Each
tenant must use a unique LDAP server or AD.
5. If LDAP is selected as the authentication source, complete the
fields as described below.

Field Description

LDAP Servers The LDAP servers are where the secrets are stored. The
format is: <ldap node1>:<port>[, <ldap node2>:<port>] ...
Note: There is no default port. The <port> must be specified.

Bind DN The binddn for the LDAP servers.

For AD, the format is:
cn=Administrator,cn=users,<base_dn>
For example:
cn=Administrator,cn=users,DC=MAUI,DC=CIG,DC=COM

Base Directory The base entry where the secrets stored.

For AD the format is:
cn=atmosks, <base_dn>
For example:
cn=atmosks,DC=MAUI,DC=CIG,DC=COM

Bind Password For OpenLDAP: the bindpw is the OpenLDAP administrator’s

password.
For AD: the bindpw is AD administrator's password.

6. Click Submit to create a tenant.

Creating a Tenant 57
Managing Tenants

Configuring an LDAP 1. When creating a tenant, click Add next to the Authentication
server for remote Source field. The Remote LDAP Configuration page appears.
authentication

2. Complete the fields as described below.

Field Description

Auth Name Name of authentication source.

Bind DN Distinguished name to use to connect to the LDAP server.

This field is used to populate the Auth Name field. For
example, if you enter the following for Bind DN:
cn=root,dc=host,dc=example,dc=com then Auth Name is
filled in as follows: host.example.com

Bind Password Password for Bind DN.

58 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Tenants

Field Description

Server Name LDAP server locations or IP addresses, separated by spaces.

LDAP Debug Level Debug level for the server.

Protocol LDAP or LDAPS.

Port Number Port number for communicating with the LDAP server.

LDAP Timeout Timeout interval (in milliseconds) to use when

communicating with the LDAP server.

User Search Path Distinguished name at which to begin user searches on the
LDAP server.

Group Search Path Distinguished name at which to begin group searches on the
LDAP server.

User Object Class Object class that identifies users in the LDAP hierarchy.

User ID Attribute Attribute that identifies a user login ID.

Group Object Class Object class that identifies groups in the LDAP hierarchy.

Group Name Attribute Attribute that identifies a group name.

3. Click Save.

Configuring Before using a new or existing OpenLDAP server as an external store

OpenLDAP for UID for UID shared secrets, it must be configured with new schema
secret storage information. The sections below describe how to download the
schema scripts, configure the OpenLDAP servers, and start and stop
the OpenLDAP servers.

Downloading the You can download the ldapSecretStore.tar from the EMC Powerlink
schema files website:
http://www.powerlink.EMC.com

The ldapSecretStore.tar file contains the atmoskeystore.ldif file that

will need to be available to each OpenLDAP server that is going to be
configured.

Creating a Tenant 59
Managing Tenants

Configuring existing This section describes how to configure existing OpenLDAP servers
OpenLDAP servers with the LDAP keystore (secret store) schema.
Prerequisites:
◆ OpenLDAP 2.4.x is installed as documented by OpenLDAP.
◆ OpenLDAP 2.4.x is configured to run in dynamic configuration
mode. For more information about dynamic configuration mode,
see the OpenLDAP Administrator Guide.
◆ If the existing OpenLDAP servers are deployed in
master/multiple-slaves mode, data syncronization must be
configured.
◆ If there is a network firewall between the OpenLDAP server and
the Atmos nodes, be sure to configure it to allow LDAP traffic to
pass. The default LDAP port is 389.
◆ Download the schema scripts (ldapSecretStore.tar) from EMC
Powerlink website.
◆ Ensure admin rights to the OpenLDAP server.
To integrate the schema scripts into OpenLDAP, follow the steps
below:
1. Stop the existing OpenLDAP servers.
2. Untar the ldapSecretStore.tar file from the EMC Powerlink
website and store the files in the following directories:
• /etc/maui/ldapkeyst/schema24.ldif
• /etc/maui/ldapkeyst/atmoskeystore.ldif
• /usr/local/maui/bin/ldapkeystcfg
3. Import the Atmos keystore schema into each OpenLDAP server
using the following command:
ldapkeystcfg -i schema -d <slapd_conf_dir> -f
<path_of_atmoskeystore.ldif>

For example:
ldapkeystcfg -i schema -d /etc/openldap/slapd.d -f
atmoskeystore.ldif

4. Restart all of the OpenLDAP servers.

60 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Tenants

5. Add the Atmos keystore root entry into the master OpenLDAP
server using the following command:
ldapkeystcfg -i rootentry -r <bind_dn> -b <base_dn> [-p
<ldap_port>]

For example:
ldapkeystcfg -i rootentry -r
cn=admin,ou=atmos,dc=emc,dc=com -b dc=emc,dc=com

Note: the entries derived from <base_dn> should already be

configured to be able to synchronize the OpenLDAP servers.

Configuring new This section describes how to configure new OpenLDAP servers with
OpenLDAP servers the LDAP keystore schema. These steps assume that the OpenLDAP
software is installed.
Prerequisites:
◆ Install OpenLDAP 2.4.x as documented by OpenLDAP. It is
recommended that OpenLDAP 2.4.23 be installed.
◆ If there is a network firewall between the OpenLDAP server and
the Atmos nodes, be sure to configure it to allow LDAP traffic to
pass. The default LDAP port is 389.
◆ Download the schema scripts (ldapSecretStore.tar) from EMC
Powerlink website.
◆ Ensure admin rights to the OpenLDAP server.
To expand the OpenLDAP schema, follow the steps below:
1. Untar the ldapSecretStore.tar file from the EMC Powerlink
website and store the files in the following directories:
• /etc/maui/ldapkeyst/schema24.ldif
• /etc/maui/ldapkeyst/atmoskeystore.ldif
• /usr/local/maui/bin/ldapkeystcfg
2. To configure the master LDAP server, run the following
command as root:
/usr/local/maui/bin/ldapkeystcfg -m

3. To configure each slave LDAP server, run the following command

as root:
/usr/local/maui/bin/ldapkeystcfg -s -l
<master_ldapserver>

Creating a Tenant 61
Managing Tenants

Starting the OpenLDAP To Start the OpenLDAP servers, run the following command:
servers
<path_of_slapd> -F /var/local/maui/ks/conf/slapd.d -h
"ldap:///"

Stopping the To Stop the OpenLDAP servers, run the following command:
OpenLDAP servers
killall slapd

Configuring AD for To use AD as an external shared secret store (keystore), follow the
UID secret storage steps below.
1. download the ADSecretStore.zip file from the EMC Powerlink
website:
http://www.powerlink.EMC.com

The ADSecretStore.zip file contains the

atmoskeystore_ADschema.ldif file that will need to be available
to each AD server that is going to be configured
2. Install the atmos shared secret schema into AD:
As administrator, login to the node running AD, unzip the
ADSecretStore.zip file, and execute the following command:
ldifde -i -f <schema file> -v -c
"cn=Configuration,dc=X" "cn=Configuration,<base dn>"

For example:
ldifde -i -f atmoskeystore_ADschema.ldif -v -c
"cn=Configuration,dc=X"
"cn=Configuration,DC=MAUI,DC=CIG,DC=COM"

Note: the atmoskeystore_ADschema.ldif file is located in the

directory where the ADSecretStore.zip file was extracted.
3. Install the Atmos keystoreroot entry into AD using the following
command:
ldifde -i -f atmoskeystore_ADroot.ldif -v -c
"cn=atmosks,dc=X" "cn=atmosks,<base_dn>

For example:
ldifde -i -f atmoskeystore_ADroot.ldif -v -c
"cn=atmosks,dc=X" "cn=atmosks,DC=MAUI,DC=CIG,DC=COM"

62 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Tenants

Making the shared To ensure that the external shared secret store is always available, the
secret store highly external LDAP or AD server should be configured for HA. Refer to
available the OpenLDAP or AD documentation for more information on
making these products highly available.

Note: If all of the external LDAP servers are stopped within a short period of
time, Atmos will not be accessible via Web Services for the next 1000 requests,
even if the LDAP servers are restarted. This is done to avoid performance
issues if there are many read requests. To restore the LDAP servers sooner,
use the Apache service httpd graceful command on the failed node.

Managing an To modify the external shared secret store or to re-encrypt shared

external shared secrets, follow the steps below.
secret store 1. Login as SysAdmin, then click Tenant List in the Navigation
pane. The Tenant List page appears.
2. Under the Actions column, click Edit next to the tenant you want
to modify. The Tenant Information page appears.

Creating a Tenant 63
Managing Tenants

3. Click Configure External Shared Secret Store. The Configure

External Shared Secret Store page appears.

4. To change the LDAP shared secret store configuration, modify the

fields as needed.
5. To re-encrypt the shared secrets, click Re-encrypt.
Shared secrets should be re-encrypted as part of a regular key
rotation security policy or whenever you suspect that the
encryption key for the shared secrets has been compromised.
Depending on the number of shared secrets that need to be
re-encrypted, this operation could take up to several minutes to
complete.
UID authentication operations will continue uninterrupted
during the re-encryption operation.

Renaming a Tenant
When you rename a tenant, the name of its default subtenant also is
changed.
1. Login as SysAdmin, then click Tenant List in the Navigation
pane. The Tenant List page appears.

64 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Tenants

2. Under the Actions column, click Edit next to the tenant you want
to rename. The Tenant Information page appears.

3. Click Rename. The Rename Tenant page appears.

4. Enter the New Tenant Name, then click Submit.

Creating a TenantAdmin
Once you create a tenant, you must assign the TenantAdmin role
within this tenant to one or more users. A given tenant can have
multiple TenantAdmins, but a given TenantAdmin can be a
TenantAdmin for only one tenant.
Follow these steps:
1. Login as SysAdmin, then click Tenant List in the Navigation
pane. The Tenant List page appears.

Creating a TenantAdmin 65
Managing Tenants

2. Click Edit for the Tenant you need to modify. The Tenant
Information page appears.

3. Click Add Tenant Admin. The Add New Admin page appears.

4. Enter the User Name for this TenantAdmin, and click Save.
When you create a TenantAdmin and the authentication source
associated with the tenant is Local, the server checks whether the
user you input exists; if not, it prompts you to add the user. If the
authentication source for the tenant is Remote, the server does not
check whether the user exists.

66 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Tenants

In this case, because the authentication source is Local and the

user name does not exist in the system, you are asked to add the
new (local) user.

5. Click OK to add the new (local) user to the system. You are
prompted to enter the password and other information about the
account.

6. Enter the required Password and Password Confirm fields and

any optional fields.
Although the Email field is optional, we highly recommend you
use it. If the new TenantAdmin forgets his password, he can get it
emailed to him—but only if you fill in this field.

Creating a TenantAdmin 67
Managing Tenants

Click Save to return to the Tenant Information page. The Tenant

Admins area now shows the new TenantAdmin’s user name.

Note: For operations that create/modify system-management users, or

assign an administrative role (SysAdmin, TenantAdmin, or
SubtenantAdmin) to a user, there is a slight delay before the effect of the
operation is visible on all Atmos nodes, while the Atmos system is
synchronized.

Modifying a TenantAdmin
To view or modify TenantAdmin information, login as a
TenantAdmin and click Update My Information in the Navigation
pane. The Update My Information page appears as shown in
Figure 10. Use this page to change passwords and other information
about your TenantAdmin account.
Required fields are marked with red asterisks on the page.

68 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Tenants

Figure 10 Upate My Information

Deleting a TenantAdmin
1. Login as SysAdmin, then click Tenant List in the Navigation
pane. The Tenant List page appears.
2. Click Edit for the Tenant you need to modify. The Tenant
Information page appears.

3. In the Tenant Admins area, in the row for the TenantAdmin you
want to remove, click Remove Role.
4. In the pop-up dialog asking you to confirm, click OK.

Deleting a TenantAdmin 69
Managing Tenants

Adding Nodes to a Tenant

You can add nodes to a tenant for Web-services or file-system data
access. An access node can belong to only one tenant. A single node
may be assigned as both a Web-services access node and either an
NFS or CIFS access node.
After following the steps in the procedure below, you can either
◆ Export NFS and CIFS directly from Atmos, using the
system-management GUI. To do this, the TenantAdmin adds or
edits mount-point shares of NFS/CIFS on the appropriate nodes.
You can use Active Directory to authenticate CIFS users (UIDs).
◆ Export the Atmos file system as NFS. For a step-by-step
procedure, see the EMC Atmos Installation Guide.
To add nodes to a tenant, follow these steps:
1. Login as SysAdmin, then click Tenant List in the Navigation
pane. The Tenant List page appears.

2. Click Edit for the Tenant you need to modify. The Tenant
Information page appears.

70 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Tenants

3. Under Access Nodes, click Add Access Nodes. The Assign Node
To Tenant page appears.

4. On the left, select the check box(es) for the node(s) you want to
add for this tenant.
5. For each selected node, check Web Service and/or a File System
option, as required.
6. Check Multi Subtenant Access if you want all subtenants under
this tenant to have access to the namespace via the selected
node(s). If you do not check this, only the default subtenant under
this tenant will have access.
7. Click Save. You are returned to the Tenant Information page. The
selected node name now appears in the Access Nodes list for the
tenant you modified.

8. Optionally, proceed below to enable/disable or configure SSL.

Adding Nodes to a Tenant 71

Managing Tenants

Require SSL for Web Use Require SSL for Web Service connections to enable and disable
Service the Secure Sockets Layer (SSL) protocol on access nodes using Web
connections Services. When enabled, Atmos SOAP and REST interfaces can only
be accessed by HTTPS (plain HTTP requests are refused). When
disabled, Atmos SOAP and REST interfaces can be accessed by HTTP
and HTTPS.
SSL should be enabled unless one of the following is true:
◆ You secured the connection between the client and server in
another way.
◆ Performance is more important than privacy protection for the
data passing between the client and server (for example, if you
are passing unimportant test data).
To change the SSL enablement setting for Web-service access on all
nodes assigned to this tenant, follow the steps below. To change the
SSL enablement setting for Web-service access on all nodes, see
“Configuring Security System-wide (Enabling/Disabling SSL)” on
page 49.
1. On the Tenant Information page, click Require SSL for Web
Service connections (in the Operations area). Note: This link
always is active, but if you click it before any node is assigned to
the tenant for Web Service access, you get an error message.
2. Specify the setting using the Enable or Disable button
(whichever is active).
3. Click Back to return to the Tenant Information page.

72 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Tenants

Configuring SSL Servers use certificates for creating an SSL while communicating with
Certificates for a each other over networks. By default, Atmos uses a self-signed
Tenant certificate for SSL connections. For the best security, we recommend
you replace the default Atmos certificate with one of your own,
signed by your trusted Certificate Authority (CA).
To configure your own SSL certificates for Web-service access on all
nodes assigned to this tenant, follow the steps below. To configure
SSL certificates on all nodes, login as SysAdmin. On the System
Dashboard, in the Operations area, click SSL Configuration. Continue
with step 2 below.
1. On the Tenant Information page, click Update Web Service SSL
Certificate (in the Operations area). The Update Web Service SSL
Certificate page appears.

2. Select the type of Server Certificate you want. This selection

applies only to the format of the Server Certificate File.
• PKCS7— server certificate sent to a CA for requesting a
public-key certificate
• PKCS12—server certificate file format commonly used to
store private keys with accompanying public key certificates
and are protected with a password-based symmetric key

Adding Nodes to a Tenant 73

Managing Tenants

3. Depending on the type of Server Certificate selected, different

fields appear on the page. Complete the fields as described below.

PKCS7 Fields Description

Certificate Key File A file which stores the PEM-encoded RSA Private Key.

Certificate Key Password The secret to unencrypt the Certificate Key File. If this
is not provided, the non-encrypted private key is
accepted.

Server Certificate File A PEM-encoded file that contains the server’s certificate.
The Server Certificate File contains just the certificate.

Certificate of Trusted Root CA The public certificate of the trusted root CA certificate.
This is the certificate that Atmos trusts. All clients that
communicate with Atmos must present a certificate
signed by the same CA or signed by a CA that can be
linked back to the trusted CA.

Certificate Chain of CAs A file that contains a set of certificates that allows the
SSL protocol to check and validate the integrity of the
certificate presented to it. The root CA certificate must
be the first certificate in the chain file, followed by one or
more intermediary CA certificates.

PKCS12 Fields Description

Server Certificate File A file which stores the PEM-encoded file that contains
the server’s certificate. The Server Certificate File
contains both the certificate and the private key.

Password A symmetrix key password use to protect the private key

for the PKCS12 certificate.

Certificate of Trusted Root CA The public certificate of the trusted root CA certificate.
This is the certificate that Atmos trusts. All clients that
communicate with Atmos must present a certificate
signed by the same CA or signed by a CA that can be
linked back to the trusted CA.

Certificate Chain of CAs\ A file that contains a set of certificates that allows the
SSL protocol to check and validate the integrity of the
certificate presented to it. The root CA certificate must
be the first certificate in the chain file, followed by one or
more intermediary CA certificates.

4. Click Submit.

74 EMC Atmos Version 1.4.0 Administrator’s Guide

 5
Managing
Subtenants

This chapter describes how the TenantAdmin and SubtenantAdmin

use the system-management GUI to manage subtenants. A
TenantAdmin can do anything that a SubtenantAdmin can do. This
chapter describes the following topics:
◆ Listing Subtenants.............................................................................. 76
◆ Creating a Subtenant ......................................................................... 76
◆ Renaming or Modifying a Subtenant.............................................. 78
◆ Creating a Unique ID and Assigning it to a Subtenant ................ 80
◆ Creating a SubtenantAdmin............................................................. 80
◆ Deleting a SubtenantAdmin ............................................................. 83

Managing Subtenants 75
Managing Subtenants

Listing Subtenants
Login as TenantAdmin. The Tenant Dashboard appears. The Subtenant
List area is shown in Figure 11.

Figure 11 Subtenant List

Creating a Subtenant
When you create a tenant, a default subtenant automatically is
created under it. That default subtenant has the same name, ID, and
Authentication Source as the tenant. Default subtenants cannot be
deleted.

Controlling the Each subtenant owns a namespace—comprising files and

Subtenant directories—that is independent of the namespaces of other
Namespace subtenants in the same tenant.Subtenant namespaces are located
Directory Structure under tenant namespaces.
At the top of subtenant namespace is a subtenant root directory,
which Atmos creates when a new subtenant is created. The location
of the subtenant root directory is the same as the location (RMG)
where the operation for subtenant creation was invoked through the
system-management GUI or CLI. Under the subtenant root
directories are the files and directories created by user applications.
Atmos distributes the namespace to best utilize system resources.
Efficient management of the namespace is very important for overall
system performance. The namespace should be balanced, one
directory should not contain all or a large portion of all files.
By default, the metadata records of new directories and files are
created in the same location (RMG) as the parent directory where the
directories and files (user data) are created. This default behavior can
be overridden by a metadata location policy.

76 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Subtenants

Namespace considerations are similar for both Atmos file-system

access and Web services access with namespace addressing.

How to create a 1. Login as TenantAdmin. The Tenant Dashboard appears.

subtenant 2. In the Subtenant List area, click Add. The Create Subtenant page
appears.

3. Specify an Authentication Source (Local or Remote).

The system lets you authenticate subtenant accounts locally
(internal) to the platform or remotely (external), using a
preconfigured LDAP server.
• If Local is selected, the authentication source is the Atmos
system. Skip to step 5.
• Remote authentication requires additional configuration: if
your site requires external, centralized authentication, you
need to enter the configuration details to enable access. If you
choose remote authentication, an Authentication Address
field appears.

Note: Once a subtenant is created, you cannot modify its authentication

source.

4. The Authentication Address field contains either a drop-down

list (if LDAP servers are already configured) or a message: “No
remote authentication source available” (shown below). If there is
a drop-down list, select a remote Authentication Address.
Otherwise, you must configure an LDAP server. For more
information about configuring an LDAP server, see “Configuring
an LDAP server for remote authentication” on page 58.
5. Specify a Subtenant Name, then click Create. The Tenant
Dashboard appears again, this time showing the new subtenant.

Creating a Subtenant 77
Managing Subtenants

Renaming or Modifying a Subtenant

A tenant's default subtenant cannot be renamed directly. However,
when a tenant is renamed, both its name and its default subtenant’s
name are changed.
1. Login as TenantAdmin. The Tenant Dashboard appears.
2. In the Subtenant List area, click Edit next to the subtenant you
want to modify. The Subtenant Information page appears.

Complete the fields as described below.

Field Description

Subtenant ID UID of the subtenant

Subtenant Name Name assigned to the subtenant

Authentication Source Local or Remote authentication

78 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Subtenants

Field Description

Used Capacity Total disk space used by the subtenant

Default Policy Specification The default policy to be used for this subtenant.

Subtenant Admins Area where you can add/delete SubtenantAdmins for

this subtenant.

UID Information about Web-service UIDs belonging to this

subtenant. A UID can be assigned to only one
subtenant. To add a UID to this subtenant, click Add,
then see “ Creating a Unique ID and Assigning it to a
Subtenant” on page 80.
This area of the page also enables you to regenerate the
secret key (shared secret), disable a UID, and email the
secret key to the email address associated with this UID.
To update the email information for a UID, click the UID.
This page lists both UIDs and SubtenantAdmins. UIDs
read and write data. SubtenantAdmins are for
administration.

Access Nodes for NFS/CIFS Lists nodes with the NFS or CIFS service which can be
accessed by this subtenant.

Policy Selectors Lists the policy selectors that are associated with the
subtenant

3. Use the Rename button or links to modify fields.

Renaming or Modifying a Subtenant 79

Managing Subtenants

Creating a Unique ID and Assigning it to a Subtenant

After a user creates an application, it is registered. This involves
providing a User ID (UID) and then generating a unique key (or
shared secret). After generating this UID and shared secret, it must be
provided to the application developer who will use them both to
authenticate this application for web service requests to the system.
To create a UID:
1. Login as SubtenantAdmin. The Subtenant Dashboard appears.
2. In the UID List area, click Add. The Add UID page appears.

3. Under UID, enter a new ID, which is unique for this subtenant.
4. Optionally, enter an email address. This is used to email the secret
key, if that action is specified on the Subtenant Dashboard.
5. Click Add. The Subtenant Information page appears, listing the
new UID and the Shared Secret that the system generated for it.
Give this information to your application developer for use in
authenticating access to the system for Web-service requests.
The shared secret can be disabled, enabled, or regenerated. When a
shared secret is disabled, the user is no longer able to access the
system through web services. To restore access, enable the shared
secret. A shared secret can also be regenerated. The user will need the
new shared secret in order to access the system. There is no way to
revert to a previous shared secret once a new one has been generated.

Creating a SubtenantAdmin
1. Login as TenantAdmin. The Tenant Dashboard appears.
2. In the Subtenant List area, click Edit for a given subtenant. The
Subtenant Information page appears.

80 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Subtenants

3. In the Subtenant Admins area, click Add. Add New Admin page
appears.

4. Enter the User Name for this SubtenantAdmin, and click Save.
When you create a SubtenantAdmin and the authentication
source associated with the tenant is Local, the server checks
whether the user you input exists. If the user does not exist, it
prompts you to add the user. If the authentication source for the
tenant is Remote, the server does not check whether the user
exists.
In this case, because the authentication source is Local and the
user name does not exist in the system, you are asked to create the
new (local) user.

Creating a SubtenantAdmin 81
Managing Subtenants

5. Click OK to add the new (local) user to the system. You are
prompted to enter the password and other information about the
account.

6. Enter the required Password and Password Confirm fields and

any optional fields.
Although the Email field is optional, we highly recommend you
use it. If the new TenantAdmin forgets his password, he can get it
emailed to him—but only if you fill in this field.
Click Save to return to the Tenant Dashboard. The Subtenant
Admins area now shows the new SubtenantAdmin’s user name.

Note: For operations that create/modify system-management users, or

assign an administrative role (SysAdmin, TenantAdmin, or
SubtenantAdmin) to a user, there is a slight delay before the effect of the
operation is visible on all Atmos nodes, while the Atmos system is
synchronized.

82 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Subtenants

Deleting a SubtenantAdmin
1. Login as TenantAdmin. The Tenant Dashboard appears.
2. In the Subtenant List area, click Edit for a given subtenant. The
Subtenant Information page appears.
3. In the Subtenant Admins area, in the row for the
SubtenantAdmin you want to remove, click Remove Role.
4. In the pop-up dialog asking you to confirm, click OK.

Deleting a SubtenantAdmin 83
Managing Subtenants

84 EMC Atmos Version 1.4.0 Administrator’s Guide

 6

Managing Policies

This chapter describes how the TenantAdmin and SubtenantAdmin

uses the system-management GUI to manage policies. This chapter
describes the following topics:
◆ Overview ............................................................................................. 86
◆ Policy-based Data Storage ................................................................ 86
◆ Default policy ..................................................................................... 88
◆ Policy Specifications .......................................................................... 89
◆ Policy Selectors ................................................................................... 99
◆ Assigning a Policy Selector to a Subtenant .................................. 102
◆ Reordering Policies .......................................................................... 103

Managing Policies 85
Managing Policies

Overview
Policy management involves defining a passive strategy for storing,
retrieving, and managing objects and metadata. In the Atmos system,
objects may include any type of binary content. Atmos relies on the
Policy Manager to process this content, and it enables you to
associate a policy with every object-management event. In addition,
you associate metadata with objects as a way to understand their
organization. As a result, you can achieve passive automation of
object management for a variety of events, according to media type
and related user or system metadata.
The TenantAdmin determines the nature of policies that run on the
system. Policies implemented by a TenantAdmin apply only to the
nodes defined for the tenant into which the TenantAdmin is placed.
The TenantAdmin determines how object data is treated within
Atmos based on a variety of conditions, including object types and
events. Events associated with objects include creation, deletion,
versioning, sorting, and updating. You can define discrete policies
that automatically manage your stored data assets by specifying
storage services, data transformations, placement strategies,
workflows, and lifecycle management, all through the placement and
definition of policies.
Policy definition is complex, so EMC recommends that you design
your policies carefully and thoroughly, before implementing them.
Begin by familiarizing yourself with the information in this chapter to
see which design decisions must be made for each policy.

Policy-based Data Storage

Atmos provides policy-based data storage, which enables an
administrator to define policies that guide how data is stored in the
system. Policies are defined via the system-management GUI.
Policies are triggered by metadata (user metadata or system
metadata).
For example, suppose an administrator sets up three policies: Gold,
Silver, and Bronze. These might correspond to service levels of
different users or of different data objects for the same user. The Gold
policy specifies three synchronous replicas and one asynchronous
replica at specific locations (for example, Boston, New York, and
Shanghai, or perhaps locations close to the users who will access the

86 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Policies

data), with one replica compressed. The Silver policy specifies two
synchronous replicas at specific locations. The Bronze policy is
intended for data that is used only infrequently and for which
inexpensive storage is required. It specifies two synchronous replicas
(to minimize the chance of losing data) and compression, but no
location. It allows the system to determine where the data is located.
Policy definitions have two main components:
◆ Policy Selector—this defines the conditions under which a policy
is triggered. These conditions are specified as expressions using
user or system metadata. For example, the Gold policy might
have a condition that the user ID is “VP.” In this case, any data
requests by a Vice President will be handled subject to the Gold
policy, which is backed up with significant storage resources, so
the Vice President’s data requests are handled very quickly. The
Silver policy might have a condition that there is a metadata tag
of “Finance.” If the user has set a metadata tag indicating that this
data is for the Finance department, the Silver policy applies to it.
The Bronze policy might have a condition that the data is email
that has not been accessed for three months.
◆ Policy Specification—this defines what happens when a policy is
selected for use. Policy specifications include the following:
• Number, type (synchronous or asynchronous), and location of
replicas.
• Transformations applied to replicas, such as compression and
deduplication.
• Striping across servers and/or across disks on a server.
• Server attributes, such as “green” specifies that most disks are
spun down for energy conservation.
• A retention period, during which data cannot be modified.
• A deletion period (also called an expiration period), after
which the data is deleted.
• Location of metadata. This affects the selection of an MDS.
• Whether all the replicas are internal or they are federated.
Federated replicas are distributed across a combination of
internal Atmos systems and external systems (for example,
Atmos onLine).
You can view a policy as an if-then statement: the policy selector is
the “if” clause, and the policy specification is the “then” clause.

Policy-based Data Storage 87

Managing Policies

Each combination of a policy selector and a policy specification is a

separate policy. The administrator can define a variety of policy
specifications, each of which can be used repeatedly (with different
policy selectors) to create multiple policies.
Policies are evaluated in the order in which they are listed in the
system. Users can control this order. The policy that is used is the first
policy encountered with a selector that matches the object data or
metadata.
The use of flexible policies enables the system administrator to better
control storage through a large, distributed system, without having to
delve down to the level of individual directories.
Policy management is handled within the Metadata Service (MDS),
by the Policy Manager (PM). The PM supports the MDS by storing
policies and selecting appropriate policies for objects and
instantiating abstract policies into concrete layout descriptions.
Policy management always is invoked on create requests, sometimes
on metadata updates, and rarely on reads and user-data updates. (It
is invoked on reads or user-data updates if the user sets appropriate
metadata triggers to cause such policy evaluation.)

Default policy
Whenever a tenant is created (during Atmos installation or later), a
default policy specification is created for that tenant. The default
policy specification, named “default,” is listed on the Tenant
Dashboard. It is defined to have two synchronous replicas, with no
location or server attribute constraints. It is applied to all objects that
do not match any user-defined policy selector. The TenantAdmin can
modify the default policy specification for a tenant. The default
policy for a tenant applies to all subtenants under that tenant. An
Atmos system can operate with only the default policy.

88 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Policies

Policy Specifications
The Policy Specification page, shown in Figure 12, is used to define
policy specifications. This page is accessed by logging into Atmos as a
TenantAdmin and clicking Add in the Policy Specifications area.

Figure 12 Policy Specification Page

The Policy Specification page enables you to define:

◆ The policy specification name
◆ Where metadata will be stored
◆ The number and type of replicas
◆ Retention and deletion times

Metadata location Atmos divides objects (or files) into two parts: user data and
metadata. User data is application data, such as Word files, text files,
movies, and MP3 files. User data is managed by the Storage Service
(SS). Metadata is stored on disks managed by the Metadata Service
(MDS). There are two types of metadata:
◆ System metadata—this includes filename, file size, modification
date, creation date, access-control lists, and object ID.
◆ User metadata—this comprises arbitrary, custom, name-value
pairs. Examples of user metadata is artist name (for MP3 data)
and customer type.

Policy Specifications 89
Managing Policies

Every object in Atmos has information associated with it that

includes system and user metadata, describes its layout, and lists any
parents and children (for file-system objects). The interface to the
system is an object interface. While there is support for a namespace,
every file is identified by an object ID.
The Metadata location setting controls the location where the
metadata records of new files and directories are created. There are
two options, sameAs and otherThan. The drop-down list to the right
of this field allows you to select one of these options:
The Metadata location drop-down menus on the Policy Specification
page, shown in Figure 13, enable you to control where file and
directory metadata is stored.

Figure 13 Policy Specification Metadata Location Options

Table 1 lists the available metadata location options.

Table 1 Metadata Location Options

Field Description

sameAs Store the object's metadata information in the same location as the data.

otherThan Store the object's metadata information in a different location from the data.

ANY For the Web-service object interface, this is a location at or close to the
client, for the Web-service namespace interface or file-system interface,
this is the location of the subtenant root directory.

RMG A specific RMG location that you defined when adding RMGs.

$client The location where the data request is received.

Atmos supports dynamic location definitions. $client designates the

location of the client where an operation is executed. A policy using
the $client location descriptor stores the replica on a storage service at
the same location as the client that initiated the request.
$clientCreateLoc designates the location of the client where the object
is or was created. A policy using the $clientCreateLoc location
descriptor stores the replica on a storage service at the same location
as the client where the object is or was created.

90 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Policies

For example, consider an Atmos system with two locations, Boston

and Denver. At each location, there are several Atmos nodes running
the Atmos storage server and client services. If a Boston application
(UID) creates an object whose policy has a replica with location
equals sameAs $client, that replica is stored in Boston. If a Denver
application (UID) creates another object with the same policy, its
$client location-driven replica is stored in Denver. In the case where a
policy is triggered by object creation, $client is interpreted the same
as $clientCreateLoc.

Replicas Two types of replicas may be created and associated with objects:
synchronous and asynchronous. A given object may have both types
of replicas.

Synchronous In general, synchronous replicas are bit-for-bit copies of each other

Replication that are identical at any point in time. When writing the data for an
object, once the sync replicas are accessible, the application will
receive an acknowledgment once the data is committed to all of them
and they are identical copies of them. If one or more sync replicas are
not accessible (possible because of a disk failure), Atmos will
acknowledge the write to the application when the remaining good
sync replicas are committed and temporarily exclude the inaccessible
replica(s) from the list of sync replicas and schedule it for
background repair, which may lead to reallocation of the replica in
question.
At least one sync replica must be successfully written to in order for
Atmos to acknowledge a write.
When an MDS returns metadata to the client, the client can determine
which SSs contain synchronous replicas for the data being updated.
The client is responsible for updating synchronous replicas, so it
needs to talk to those SSs immediately.

Asynchronous Asynchronous replication offers some level of disaster recovery while

Replication not affecting performance as much as synchronous replication.
Asynchronous replication is done on a best-effort basis. The system
tries to keep asynchronous replicas up to date, but while such
updates will be made eventually, there is no guarantee of when they
will occur.
For example, assume we are writing to an object that has two
synchronous and one asynchronous replicas. Whenever an object is
written, the client updates the SSs containing the synchronous

Policy Specifications 91
Managing Policies

replicas. When the client completes the updates, the API returns a
close request, which is sent to the MDS. That close request contains
information about what the client did while they had the object open,
for example, which blocks were written (made “dirty”) and which, if
any, blocks failed. The MDS closes the object and acknowledges that
to the client.
In the background, the MDS creates a new request for the Job Service
(JS). The JS is responsible for all asynchronous data-maintenance
tasks, like asynchronous replication and consistency checking. It runs
on most Atmos nodes and is an application that sits on top of the
client.
Every policy must specify at least one replica, and a policy can
specify an unlimited number of replicas. Any Atmos SS can host a
replica.
When defining replica requirements, be sure that the specified
resources are available in the system. Before a policy is created,
Atmos verifies that the specified Server Attributes are actually
available. The Location specification determines how resources are
checked.
For example, if the location is specified as a constant, such as Boston,
then Atmos checks the nodes in Boston for the specified resources. If
Boston does not have the resources, an error is returned indicating
that the resources were not found. If the location is specified by the
$client variable, and there are three locations in the system: Boston,
Denver, and London, then Atmos checks the nodes at Boston, Denver,
and London for the specified resources. All three locations are
checked because the $client variable can designate either Boston,
Denver, or London as the location. If the resources are not found at all
three locations, an error is returned indicating that the resources were
not found.

92 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Policies

Customize The Customize option enables you to customize where and how
objects are stored, as shown in Figure 14.

Figure 14 Policy Specification Customize Options

The location drop-down menus enable you to control where the

replica is stored. Table 2 lists the available location options:

Table 2 Replica Location Options

Field Description

sameAs Store the replica in the same location as the object.

otherThan Store the replica in a different location from the object. In systems where
there are more than two RMGs, otherThan does not enable you to
specify which other location should be used.

ANY For the Web-service object interface, this is a location at or close to the
client. For the Web-service namespace interface or filesystem interface,
this is the location of the subtenant root directory.

$client Designates the location of the client where an operation is executed. A

policy using the $client location descriptor stores the replica on a SS at
the same location as the client that initiated the request.

$clientCreateLoc Designates the location of the client where the object is/was created. A
policy using the $clientCreateLoc location descriptor stores the replica
on a SS at the same location as the client where the object is/was
created.

Policy Specifications 93
Managing Policies

Server Attributes describe how the SS allocates new objects to the

physical disks under its management. The action attribute specifies
the type of data-at-rest transformations that are applied to the replica
data when stored on the server.
Table 3 lists the available placement strategies.

Table 3 Placement Strategies

Field Description

OPTIMAL Rotate requests equally among all available storage disks (round robin).

GREEN Only one or a few disks are active, the rest are spun down for energy
conservation. When the active disks fill up, the spun-down disks are
woken up and used. This option is not supported in the Atmos Virtual
Edition.

BALANCED Pick the disk with the most available space.

The server can apply data transformations to the object. Table 4 lists
the available data transformations.

Table 4 Data Transformations

Field Description

None No services are performed (normal writes and reads). This is the
default.

Any Pick any storage server regardless of how it is configured (for

example, whether it is configured for compression).

Checksum The storage server generates a checksum for all data saved on it.
When the data is read, the checksum is verified. When the data is
re-written, the old data is also verified.

Compression Data is compressed on write and decompressed on read. This

conserves disk space but introduces processing overhead on the
server, so typically it has a negative impact on performance.
Compression can be used successfully for objects that are written
once and accessed rarely.

Deduplication Multiple copies of the data are removed and only one copy of the
data is maintained. This is intended to conserve storage capacity.
Atmos Virtual Edition does not support Deduplication.

CompressionDedup A combination of Compression and Deduplication.

94 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Policies

Striping Striping enables you to put blocks of data of the same replica on
different nodes. The Enable Stripe options are shown in Figure 15.

Figure 15 Policy Specification Enable Stripe Options

Table 5 lists the striping options.

Table 5 Striping Options

Field Description

Stripe Number Number of nodes to stripe across.

Stripe Size Amount of data written to each node.

Stripe Unit Options are B, KB, MB, GB, and TB.

Erasure Code Erasure Code provides data redundancy without the overhead of
replication. Erasure Code divides an object into rows, each of which
contains m data fragments and k code fragments. Each fragment is
stored on a different disk. Using this method, each row of the object
can be reconstructed from any m of the total set of fragments,
tolerating up to k unavailable fragments.
Atmos supports the following Erasure Code Fragmentation options
as shown in Figure 16.
◆ 9/12 configuration (Data=9, Code=3) — storage overhead 33%
◆ 10/16 configuration (Data=10, Code=6) — storage overhead 60%
◆ 10/12 configuration (Data=10, Code=2) — storage overhead 20%

Policy Specifications 95
Managing Policies

Figure 16 Policy Specification Erasure Code Options

Table 6 lists the Erasure Code options.

Table 6 Erasure Code Options

Field Description

Erasure Code CRS (Cauchy Reed-Solomon) is the default algorithm.

Algorithm: CRS

Fragmentation: Tolerates up to 3 simultaneous drive failures

Data=9, Code=3

Fragmentation: Tolerates up to 6 simultaneous drive failures.

Data=10, Code=6

Fragmentation: Tolerates up to 2 simultaneous drive failures.

Data=10, Code=2

Note: Because Erasure Code has an enhanced data protection mechanism,

concurrent write and read operations of an object may result in an I/O error
until the write operation has completed.

96 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Policies

Table 7 lists the recommended Erasure Code configurations.

Table 7 Erasure Code Configurations

For this configuration EMC recommends...

Single EC replica 9/12 or 10/16 configuration

Single EC replica + single ordinary 9/12 or 10/16 configuration

replica

Two or more EC replicas 9/12, 10/12, or 10/16

configuration

For Atmos Virtual Edition (AVE) configurations, use protected

storage (RAID or Mirroring). For Erasure Code use with AVE, contact
EMC personnel.
The performance of a single Erasure Code replica distributed across
multiple sites is strongly dependent on WAN latency, site count, and
other characteristics. Such a deployment should be designed in
consultation with EMC personnel.

Replica distribution You can select the distribution location for replicas with Erasure
Code. EMC recommends that you select the defined location of the
RMG, as shown in Figure 17.

Figure 17 Erasure Code Fragmentation Distribution

Policy Specifications 97
Managing Policies

Federate Federate is active only if a federation target was defined by the

SysAdmin. If Federate is active, a drop-down list is available which
contains the federation names that were defined by the SysAdmin.
For more information see, “Configuring a Federation Target” on
page 48.
Federated replicas do not work if the clocks of the federation target
servers are not synchronized: the write to the federated replica fails,
and the federated replica is marked as stale. Make sure the clocks of
the federation target servers and the Atmos client server are
synchronized.

Read access Replica selection for read access determines how the Atmos client
chooses a replica when a read operation is performed. Typically, for
protection, availability, and performance purposes, Atmos objects
have multiple replicas. The client can choose any of the replicas in
their current state.
Options for read access are:
◆ geographic—chooses the closest replica in geographic terms.
◆ random—picks a replica at random.

Retention/Deletion Policies can specify retention and deletion periods. Retention is a

period of time that the object cannot be modified or deleted from the
date it was created (Start Delay Window). Once the retention period
has passed, then the user can update the object and a new retention
period can be applied (the clock starts over again). Deletion is the
time after an object was created that it should be deleted. This time
should be longer than the retention time since it is not possible to
delete an object that is being retained. Deletion applies only to files,
not directories. The retention and deletion fields are shown in
Figure 18.

98 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Policies

Figure 18 Policy Specification Rentention and Deletion Options

Policy Selectors
Policy selection is a process where Atmos applies a set of XQuery
expressions to determine which policy is applied to the object. The
policy selection XQuery expressions are defined by a series of policy
selector descriptions. Each selector descriptor specifies the selection
criteria for a different policy, including the object operation, which
triggers the policy. To complete the process, a policy specification
must be selected from a list available to the subtenant.

! IMPORTANT
Some objects may have one policy triggered on object (or metadata)
creation and another triggered on object (or metadata) update. If so,
at least one synchronous replica in the create policy specification
must exactly match a synchronous replica in the update policy
specification, or the update will fail.

Policy Selectors 99
Managing Policies

The Policy Selectors page, shown in Figure 19, is used to define policy
selectors. This page is accessed by logging into Atmos as a
TenantAdmin and clicking Add in the Policy Selectors area.

Figure 19 Policy Selector Page

There are three ways to create a selector:

◆ User metadata—build the policy selector expression from the
menu using user metadata tags
◆ System metedata—build the policy selector expression from the
menu using system metadata tags
◆ Advanced Policy Selector—input the XQuery expression
manually
Table 8 lists the available selector descriptions.

Table 8 Policy Selector Descriptions

Field Description

Specification Policy specifications available to the subtenant, which is used once

the policy is triggered.

100 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Policies

Table 8 Policy Selector Descriptions (continued)

Field Description

Metadata Tag Indicates which metadata field will be used to intercept. The field can
be either system metadata attribute or user metadata attribute
depending on which method of entry is chosen. System metadata
tags include:
• atime—last access time
• mtime—last modified time
• ctime—change time
• itime—create time
• uid— UID from UID List, where you create new applications from
• gid—group ID, N/A to Web Service users; ignore
• size—object size in bytes
The time format for atime, mtime, ctime, itime is as follows:
YYYY-MM-DDTHH:MnMn:SSZ
Where: YYYY = Year, MM = Month, DD = Day, HH = Hour, MnMn =
Minutes, SS = Seconds. Note that there is a T in between DD and
HH, and also a Z at the end.
For example, April 12, 2008 at 3:35 would be displayed as:
2008-04-12T03:45:00Z

Match Operator Indicates which operator will be used in the selector expression. The
following operators are available:
• Equals—matches the defined entry
• Starts With—starts with the defined entry
• Ends With—ends with the defined entry
• Contains—contains the defined entry
• <—less than the defined entry
• =—equals the defined entry
• >—greater than the defined entry
• <=—less than or equal to the defined entry
• >=—greater than or equal to the defined entry

Metadata Value Indicates what value will be intercepted for the Metadata Tag.

XQuery Expression Enter the XQuery expression that will be used to determine which
policy is applied to the object.
For example, a query for all objects of .jpg file type would have the
following expression:
//objname[ends-with(.,'.jpg')]

Policy Selectors 101

Managing Policies

Table 8 Policy Selector Descriptions (continued)

Field Description

On Event Indicates when the action is triggered. The following object events
cause evaluation of policies on existing objects:
• ON_CREATE—this event is triggered when an object matching
this definition is created.
• ON_SMD_UPDATE—this event is triggered when a change in the
system metadata of an object is made. System metadata
includes: atime, mtime, ctime, uid, gid, mode, ACL, DACL,
expiration time, and retention time (ACL, expiration time, and
retention time are extended attributes available in the Atmos
reserved namespace). Policy evaluation is only triggered when
attributes are changed directly through commands, such as
chmod, chown, and truncate. Attribute changes caused by
indirect operations, such as modifying the data, does not trigger
policy evaluation. Note that for write operations through
CIFS/Samba, the Samba server calls the utime subroutine to
change the modification and access times of the file touched,
which will trigger policy evaluation.
• ON_UMD_UPDATE—this event is triggered when a change in the
user metadata of an object is made.

Assigning a Policy Selector to a Subtenant

After you define a policy, you assign it to a subtenant. Up to 16
policies can be assigned to a single subtenant.
1. Login as TenantAdmin. The Tenant Dashboard appears.
2. In the Policy Selectors area, click the Assign link for the policy
selector to assign. The Assign Policy page appears.

3. Select the check box of the subtenant.

4. Click Submit.

102 EMC Atmos Version 1.4.0 Administrator’s Guide

 Managing Policies

Reordering Policies
Atmos evaluates policies in the order in which they appear in the
system. The first one that matches is used.
1. Login as SubtenantAdmin. The Subtenant Dashboard appears.
2. In the Policy Selectors area, click Reorder. The Reorder Policy
page appears.

3. Use the Up and Down buttons to reorder the policies.

4. Click Submit.

Reordering Policies 103

Managing Policies

104 EMC Atmos Version 1.4.0 Administrator’s Guide

 7
System Monitoring,
Events, & Reporting

This chapter describes how to configure and use Atmos system

monitoring (the operational reporting framework), event
notifications, system reporting, and log collection.
This chapter describes the following topics:
◆ Overview ........................................................................................... 106
◆ Monitoring Atmos with your NMS............................................... 106
◆ Operational Reporting Framework ............................................... 107
◆ Alerts.................................................................................................. 111
◆ Email alerts........................................................................................ 112
◆ SNMP support .................................................................................. 114
◆ System reports .................................................................................. 133
◆ Log files and log collection ............................................................. 139

System Monitoring, Events, & Reporting 105

System Monitoring, Events, & Reporting

Overview
Atmos provides various types of notifications and reports that help
you to maintain and troubleshoot your Atmos system.
Atmos provides the following types of notificatons:
◆ alerts—created when situations result in errors and warnings, or
to provide information. Sources may come from either hardware
or software.
◆ email— email notifications can be sent based on severity, which
will trigger the email alerts. Each RMG has its own email alert
configuration.
◆ SNMP—both SNMP trap generation and SNMP standard
(MIB-II) MIB access are supported. For MIB access, the SNMP
agent must be configured.
Atmos also provides log collection and system reports, which are
used by EMC Technical Support when troubleshooting:
◆ log collection—collects logs for debugging purposes. After the
logs are collected, you can save the log package and send them to
EMC Technical Support.
◆ system report—collects data about your Atmos configuration and
sends a report to the EMC System Reports database, through the
System Report (SYR) mechanism. System reports are sent to the
EMC System Reports Database to improve customer service, and
allow EMC to provide timely support for Atmos issues.

Monitoring Atmos with your NMS

Your network management station (NMS) should be the central
monitoring tool for Atmos. The NMS should be configured to receive
the Atmos SNMP traps from the Operational Reporting Framework
and to poll various Atmos and MIB-II MIB objects in order to
properly monitor the Atmos hardware and software.
For complete monitoring, a combination of traps and MIB objects
must be monitored, such as:

106 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

◆ Operational Reporting Framework traps—monitors Atmos

system resources and provides SNMP trap notifications of
unfavorable system conditions. For more information about the
Operational Reporting Framework, see “Operational Reporting
Framework.”
◆ Dell hardware traps—Atmos forwards Dell OpenManage
hardware SNMP traps for all severities (informational, warning,
and critical). These traps provide an indication of the node status.
For more information about the Dell hardware traps, see “Dell
traps” on page 118.
◆ Atmos MIB—provides detailed information on node storage
capacity, DAE storage capacity, Atmos service status, MDS status,
SS status, WS status, JS status, and so on. For more information
about the Atmos MIB, see Appendix A, “Atmos MIB.”
◆ MIB-II MIB—provides detailed information about the network
interfaces. For more information about the MIB-II MIB, see
Appendix B, “MIB-II (RFC 1213).”
◆ Host Resources MIB—provides detailed information about the
number of disks in the Atmos system, the total storage for all
disks, the total storage for a given disk, the total used storage for
all disks, and so on. For more information about the Host
Resources MIB, see Appendix C, “Host Resources MIB (RFC
2790).”

Operational Reporting Framework

The Operational Reporting Framework serves as an early warning
system alerting you to unfavorable system conditions. The feature
allows you to monitor Atmos system resources, which can save you
time and effort when troubleshooting system issues.
To use this feature, you must select monitor targets and threshold values.
The monitor target is the service or resource you want to monitor. The
threshold value triggers the reporting action when that value is either
reached or exceeded. The reporting action sends out notifications to
you and includes alerts, emails, and SNMP traps, depending on what
you configure.

Operational Reporting Framework 107

System Monitoring, Events, & Reporting

To configure the operational reporting framework:

1. Login as SysAdmin. The System Dashboard appears.
2. In the Operations area, click Reporting Framework. The
Operational Reporting Framework page appears.
By default, all of the conditions are configured, as shown below.
Therefore, the Add button will not do anything unless a condition
is first deleted.

3. To modify an existing reporting condition, click Edit (in the

Operation column) on the same line as the condition you want to
modify.
The Operational Reporting Framework Configuration page
appears.

4. Complete the fields on the page.

The Monitor Target is the name of the service or resource being
monitored. Once a target is created, you can edit or delete the
selected target, but you cannot create two conditions with the
same target. There are several valid values as shown below.

108 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

Name Description

CPU Any CPU in the system. This enables the MauiNodeCPU

SNMP trap, if SNMP is configured and/or email if email is
configured.

Memory System memory. This enables the MauiNodeMemory

SNMP trap, if SNMP is configured and/or email if email is
configured. Because Atmos memory utilization is often at
90% or higher, a threshold setting below 90% may result in
many alerts.

Filesystem The database for storage, organization, manipulation, and

retrieval of data. This enables the MauiNodeFileSystem
SNMP trap, if SNMP is configured and/or email if email is
configured.

Swap A portion of the hard disk drive that is used for virtual
memory. This enables the MauiNodeSwap SNMP trap, if
SNMP is configured and/or email if email is configured.

Service Status Status of all system services. This enables the

MauiAppServiceCrash SNMP trap, if SNMP is configured
and/or email if email is configured. The services monitored,
include:
• Atmos Storage Service (mauiss)
• Atmos Resource Management Service (mauirms)
• Atmos Meta-Data Location Service (mauimdls)
• Atmos Job Service (mauijs)
• Atmos Consistency Checker (mauicc)
• Atmos Authentication Service (authsrv)
• Ganglia Monitoring Daemon (gmond)
• AMQP Broker Daemon (qpidd)
• Maui Client As A Service (mauiclaas)
• Spread Toolkit (spread)
• Mongrel Server (mongrel)
• Ganglia Meta Daemon (gmetad)
• Apache Server (httpd)
• Authorization Server Failover (as_failover)

Service Memory Determinies if each service is using too much of its memory
(in GB). This enables the MauiAppServiceMemory SNMP
trap, if SNMP is configured and/or email if email is
configured.

Operational Reporting Framework 109

System Monitoring, Events, & Reporting

Name Description

Sync Policy Propagation of policy changes (creation, deletion, or

modification) to replicas. This enables the
MauiTrapPolicySyncFail SNMP trap, if SNMP is configured
and/or email if email is configured.

RMG Status RMG status or connection. This enables the MauiRmgDown

SNMP trap, if SNMP is configured and/or email if email is
configured.

Segment Status Segment status or connection. This enables the

MauiSegmentDown SNMP trap, if SNMP is configured
and/or email if email is configured.

Node Status Node status or connection. This enables the

MauiNodeDown SNMP trap, if SNMP is configured and/or
email if email is configured.

Service Restart A service was restarted. This enables the

MauiAppServiceRestart SNMP trap, if SNMP is configured
and/or email if email is configured.

Network Adapter Status Network service is shutdown. This enables the

MauiNodeIntfCarrier SNMP trap, if SNMP is configured
and/or email if email is configured.

Node Temperature Node temperature is too high. This enables the

MauiNodeTempThreshold SNMP trap, if SNMP is
configured and/or email if email is configured.

The Threshold Value is the value that triggers a reporting action.

Valid values for Threshold Value depend on the setting for
Monitor Target as shown below.

Monitor Target Threshold Value

CPU, Memory, Filesystem, Swap Usage > 70%... Usage > 95%

Service Status, Network Adapter Status Down

Service Memory Usage > 1 GB... Usage > 5 GB

Sync Policy Failed

Node Status, Segment Status, RMG Status Connection Lost

Service Restart Restart

Node Temperature Over Temperature

110 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

The Reporting Action is the action that is triggered after the

threshold is reached. Valid values are shown below.

Action Description

Alert Add an alert to the database.

Email Send an email. Requires email configuration.

SNMP Trap Send an SNMP trap. Traps (notifications) can be sent to an SNMP
network-management station) to relay hardware failures and other
exceptions. Requires SNMP configuration (see “SNMP support” on
page 114).

The Total Number of Reports applies only if Monitor Target is set

to CPU, Filesystem, Memory, Swap, or Service. This is the
maximum number of times a report is generated during a given
reporting period (from when the threshold is exceeded until the
threshold is no longer exceeded).
The Frequency of Reports drop-down menu appears when you
choose a Total Number of Reports greater than 1. This
drop-down enables you to choose how often the report should be
sent. For example, if you choose Every 6 Minutes, the event will
be reported every six minutes until the Total Number of Reports
has been meet.
5. Click Submit. You return to the Operational Reporting
Framework page.

Alerts
The Alert Information area, which is displayed on the Node
Information page, contains a list of alerts relative to the node, as
shown in Figure 20. Alerts are created when situations result in errors
and warnings, or to provide information. Sources may come from
either hardware or software.

Figure 20 Alert Information

Alerts 111
System Monitoring, Events, & Reporting

The Alert Information that can be displayed includes:

◆ Severity—there are four levels of severity, each represented by a
color:
• Critical—red warning sign
• Error—red warning sign
• Warning—yellow warning sign
• Informational—orange warning sign
◆ Status—the state can be either New or Confirmed
◆ Received Time—time when the system receives the alert
◆ Description—a brief message about the alert
To confirm or delete an alert:
1. Click the navigation buttons to move between pages.
2. Click the row of the alert.
3. Click Confirm or Delete.

Email alerts
The Email Configuration page is used to set email alert options for
the RMG. Each RMG has its own email alert configuration. Enabling
Email Configuration also enables DAE and Dell hardware traps, by
default.

Note: The SNMP daemon sends shutdown and coldstart alerts each time the
SNMP daemon is shut down or restarted. To receive these email alerts, SMTP
must be configured and an email address must be provided on the Update
My Information page. When SNMP or SMTP is enabled, each node in the
RMG may send multiple alerts.

1. Login as SysAdmin. The System Dashboard appears.

2. In the RMG List area, click Detail for a given RMG. The RMG
Summary page for that RMG appears.

112 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

3. In the Operations area, click Configure Email. The Email

Configuration page appears.

4. Complete the fields as described below.

Field Description

Enable Alert Email Service Enable by selecting the check box and filing out the fields.
This is required to receive email alerts.
Important: Email alerts must be configured for at least one
RMG, for password-reminder emails to work.

Mail Sending Server IP address of the SMTP server that will deliver alert
messages and password-reminder emails.

User Account The user name of the mail-sending server, which is the
email address authenticated by the SMTP server. If the
mail server does not require a user account, you do need
to enter a user account name.

Password Account password. If the mail server does not require a

password, you do not need to enter a password.

Alert Severity For Mailing Severity which will trigger the email alerts: Critical, Error,
Warning, or Informational.

Alert Email Account The email account to receive the alerts.

5. Click Submit.

Email alerts 113

System Monitoring, Events, & Reporting

SNMP support
Atmos supports both SNMP trap generation and SNMP standard
(MIB-II) MIB access. For MIB access, the SNMP agent must be
configured. SNMP traps and the SNMP agent can be configured at
the same time or separately. For security reasons, it is recommended
that a SNMP agent community name other than public or private be
used as these are well-known default community names.
You can configure SNMP system-wide or for a specific RMG.

SNMP traps Traps (notifications) can be sent to an SNMP network-management

station (NMS) to relay hardware failures and other exceptions. The
feature is selectively enabled via the management user interface. You
need to configure the address and port of the network-management
station and the SNMP community name.
Traps require a network-management station to receive the traps,
hardware to generate true hardware-related events, and the
management interface to configure SNMP notifications. Specific
events are described in the event table, corresponding to hardware
failures. Each particular failure should generate an SNMP trap that is
received on the configured network-management station.
With Atmos 1.4.0, the Atmos MIB is now located at SNMP OID tree
area .1.3.6.1.4.1.1139.16.3.x as listed in Table 9.

Table 9 SNMP Traps

Component Trap Name/Identifier Monitor Target Value Description/Recovery

Node atmosNotificationCpuUsage CPU This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.101 the CPU usage status change on
the system.

Node atmosNotificationMemoryUsage Memory This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.102 the physical memory usage status
change on the system.

Node atmosNotificationSwapUsage Swap This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.103 the swap usage status change on
the system.

Node atmosNotificationFilesystemUsage Filesystem This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.104 the file system disk space usage
status change.

114 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

Table 9 SNMP Traps (continued)

Component Trap Name/Identifier Monitor Target Value Description/Recovery

Application atmosNotificationServiceMemoryUsage Service Memory This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.105 the Atmos service memory usage
status change on the system.

Application atmosNotificationServiceStatus Service Status This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.106 the Atmos service status change.

Node atmosNotificationInternalCarrierStatus Network Adapter This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.107 Status the internal carrier status change,
e.g., eth0 is disconnected.

Node atmosNotificationExternalCarrierStatus Network Adapter This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.108 Status the external carrier status change,
e.g., eth1 is disconnected.

Node atmosNotificationNodeStatus Node Status This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.109 the Atmos node status change.

Segment atmosNotificationSegmentStatus Segment Status This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.110 the Atmos segment status change.

RMG atmosNotificationRMGStatus RMG Status This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.111 the Atmos RMG status change.

Cluster atmosNotificationPolicySyncFailed Sync Policy This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.112 the policy distribution failure.

Cluster atmosNotificationUidSyncFailed Sync UID This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.113 the UID distribution failure.

DAE atmosNotificationDAEStatus — This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.114 the DAE status change of the
system.

DAE atmosNotificationDAEBackplaneStatus — This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.115 the DAE backplane status change
of the system.

DAE atmosNotificationDAEFanStatus — This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.116 the DAE fan status change of the
system.

DAE atmosNotificationDAETempStatus — This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.117 the DAE temperature status change
of the system.

Internal Server Disk atmosNotificationDiskStatus — This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.118 the disk status change of the
system.

SNMP support 115

System Monitoring, Events, & Reporting

Table 9 SNMP Traps (continued)

Component Trap Name/Identifier Monitor Target Value Description/Recovery

Cluster atmosNotificationPolicyResourceStatus — This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.119 the policy resource status of the
system.

Management DB atmosNotificationMgmtDBStatus pgreplicate/postgresql This notification is used to report

1.3.6.1.4.1.1139.16.3.1000.120 service status the policy resource failure of the
system.

Cluster atmosNotificationDiskRecovery Filesystem This notification is used to report a

1.3.6.1.4.1.1139.16.3.1000.121 file system's critical state, trigger
recovery.

Cluster atmosNotificationVIPFailover — This notification is used to report a

1.3.6.1.4.1.1139.16.3.1000.122 VIP failover event.

Atmos also supports the legacy SNMP traps provided prior to

Atmos 1.4.0 as listed in Table 10.

Table 10 Legacy SNMP Traps

Component Trap Name/Identifier Monitor Target Value Description/Recovery

Cluster MauiTrapGeneric / — This is a generic trap used to test

.1.3.6.1.4.1.1139.16.1.1 and verify connectivity.

Node MauiNodeDown/ Node Status Node has lost power or

.1.3.6.1.4.1.1139.16.1.2 connectivity.
Check the power or the network
adapter.

Node MauiNodeTempThreshold / Node Temperature Node temperature is too high.

.1.3.6.1.4.1.1139.16.1.3 Power down the node and fix the
temperature problem.

Node MauiNodeIntfCarrier / Network Adapter Status The external network interface is

.1.3.6.1.4.1.1139.16.1.4 disconnected.
Plug in the network cable.

Disk array enclosure (DAE) MauiDAEDiskFailure — A DAE disk failed.

.1.3.6.1.4.1.1139.16.1.5 Replace the drive.

DAE MauiDAEFanOperation / — A DAE fan is not reporting back

.1.3.6.1.4.1.1139.16.1.6 correctly.
Replace the fan unit.

DAE MauiDAEBackplane / — (Not supported on current

.1.3.6.1.4.1.1139.16.1.7 hardware.)

116 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

Table 10 Legacy SNMP Traps (continued)

Component Trap Name/Identifier Monitor Target Value Description/Recovery

DAE MauiDAEEnclosureFail / — DAE controller failure.

.1.3.6.1.4.1.1139.16.1.8 Replace the DAE enclosure
controller.

DAE MauiDAETempThreshold / — DAE temperature is too high.

.1.3.6.1.4.1.1139.16.1.9 Correct the heat problem.

Application MauiAppServiceRestart / Service Restart mmon reports that it restarted an

.1.3.6.1.4.1.1139.16.1.10 application.

Node MauiNodeCPU / CPU There is high CPU use at a node.

.1.3.6.1.4.1.1139.16.1.13 Restart the service that consumes
too much CPU.

Node MauiNodeMemory / Memory There is high memory use at a

.1.3.6.1.4.1.1139.16.1.14 node.
Restart the service that consumes
too much memory.

Node MauiNodeFileSystem / Filesystem There is high file-system use at a

.1.3.6.1.4.1.1139.16.1.15 node.
Add more disks or nodes, or free up
unused space

Node MauiNodeSwap / Swap There is high swap-space use at a

.1.3.6.1.4.1.1139.16.1.16 node.
Restart the service that consumes
too much memory.

Application MauiAppServiceCrash / Service Status An Atmos service crashed.

.1.3.6.1.4.1.1139.16.1.17 Restart the service.

Application MauiAppServiceMemory / Service Memory An Atmos process uses too much

.1.3.6.1.4.1.1139.16.1.18 memory.
Restart the service if necessary.

Cluster MauiTrapUidSyncFail Sync UID UID synchronization failed.

1.3.6.1.4.1.1139.16.1.19 Repeat the UID synchronization
procedure.

Cluster MauiTrapPolicySyncFail / Sync Policy Policy synchronization failed.

.1.3.6.1.4.1.1139.16.1.20 Repeat the policy synchronization
procedure.

RMG MauiRmgDown RMG Status RMG has lost power or connectivity.

.1.3.6.1.4.1.1139.16.1.21 Check the power or the network
adapter.

SNMP support 117

System Monitoring, Events, & Reporting

Table 10 Legacy SNMP Traps (continued)

Component Trap Name/Identifier Monitor Target Value Description/Recovery

Segment MauiSegmentDown / Segment Status Segment has lost power or

.1.3.6.1.4.1.1139.16.1.22 connectivity.
Check the power or the network
adapter.

Node MauiNodeDiskError — The node’s internal disk has an

1.3.6.1.4.1.1139.16.1.23 error.

Management DB MAUI_MGMTDB_OID pgreplicate/postgresql A mangement database service

.1.3.6.1.4.1.1139.16.1.28 service status has stopped.
Manually start the stopped service.

DAE MauiDAECriticalEvent — DAE has a critical failure. Check the

.1.3.6.1.4.1.1139.16.1.29 power supply for a failure.

Cluster RECOVER_DISK_OID Filesystem An SS disk has potentially failed.

.1.3.6.1.4.1.1139.16.1.98 Manually verify that the disk has
truly failed.

Cluster NUM_EXCEPTION_RECS_OID Filesystem Number of exceptional objects to

.1.3.6.1.4.1.1139.16.1.99 be recovered on the node. The
system is polled for exceptional
objects every 12 hours. Exceptional
objects will be recovered
automatically by Atmos every 24
hours.

The severity of a trap depends on the number of traps received

during a given period of time. For example, if you receive a
MauiAppServiceCrash trap every minute, that indicates a high
severity; whereas, receiving the MauiAppServiceCrash trap once
every 24 hours is a low severity.

Dell traps Atmos forwards Dell OpenManage hardware traps (10892.mib and
dcstorag.mib) to either your NMS or email. All Dell system traps for
all severities (informational, warning, and critical) are forwarded. To
receive these traps as email alerts, SMTP must be configured and an
email address must be provided on the Update My Information page.
When SNMP or SMTP is enabled, each node in the RMG may send
multiple alerts. Atmos Virtual Edition does not support forwarding
Dell OpenManage hardware traps, even if the ESX server is a Dell
system.

118 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

A sample of the most severe Dell traps are listed in Table 11.

Table 11 Sample of Dell Traps

Component Trap Name/Identifier Description/Recovery Severity

Node MIB-Dell-10892::alertMemoryDeviceFailure Memory device status is critical. High

.1.3.6.1.4.674.10892.1.0.1404

Node MIB-Dell-10892::alertMemoryDeviceNonRecoverable Memory device status is High

.1.3.6.1.4.674.10892.1.0.1405 non-recoverable.

Node StorageManagement-MIB::alertControllerWarning Alert message ID: %s, Controller Medium

.1.3.6.1.4.674.10893.1.20.200.0.753 warning. %s, %s, %s

Node StorageManagement-MIB::alertArrayDiskWarning Alert message ID: %s, Array disk Medium

.1.3.6.1.4.674.10893.1.20.200.0.903 warning. %s, %s, %S

Node StorageManagement-MIB::alertArrayDiskFailure Alert message ID: %s, Array disk High

.1.3.6.1.4.674.10893.1.20.200.0.904 failure. %s, %s, %s

Node StorageManagement-MIB::alertArrayDiskNonRecoverable Alert message ID: %s, Array disk is High

.1.3.6.1.4.674.10893.1.20.200.0.905 non-recoverable. %s, %s, %s

Node StorageManagement-MIB::alertEMMWarning Alert message ID: %s, EMM Medium

.1.3.6.1.4.674.10893.1.20.200.0.953 warning. %s, %s, %s

Node StorageManagement-MIB::alertEMMFailure Alert message ID: %s, EMM failure. High

.1.3.6.1.4.674.10893.1.20.200.0.954 %s, %s, %s

Node StorageManagement-MIB::alertEMMNonRecoverable Alert message ID: %s, EMM is High

.1.3.6.1.4.674.10893.1.20.200.0.955 non-recoverable. %s, %s, %s

Node StorageManagement-MIB::alertVirtualDiskWarning Alert message ID: %s, Virtual disk Medium

.1.3.6.1.4.674.10893.1.20.200.0.1203 warning. %s, %s, %s

Node StorageManagement-MIB::alertVirtualDiskFailure Alert message ID: %s, Virtual disk High

.1.3.6.1.4.674.10893.1.20.200.0.1204 failure. %s, %s, %s

Node StorageManagement-MIB::alertVirtualDiskNonRecoverable Alert message ID: %s, Virtual disk High

.1.3.6.1.4.674.10893.1.20.200.0.1205 is non-recoverable. %s, %s, %s

Node StorageManagement-MIB::alertRedundancyDegraded Alert message ID: %s, Redundancy Medium

.1.3.6.1.4.674.10893.1.20.200.0.1305 has been degraded. %s, %s, %s

Node StorageManagement-MIB::alertRedundancyLost Alert message ID: %s, Redundancy High

.1.3.6.1.4.674.10893.1.20.200.0.1306 has been lost. %s, %s, %s

SNMP support 119

System Monitoring, Events, & Reporting

For a complete description of the instrumentation traps that can be

forwarded by Atmos, see the Dell OpenManage SNMP Reference Guide.

SNMP agent The SNMP agent is the SNMP daemon that runs on Atmos and
listens on the SNMPD port for SNMP requests from an NMS.
Whereas SNMP traps are sent from Atmos to an NMS, SNMP
requests are sent from NMS to Atmos.
The following SNMP standard MIBs are available for query through
SNMP:
◆ system {mib-2 1}
◆ interfaces {mib-2 2}
◆ at {mib-2 3}
◆ ip {mib-2 4}
◆ icmp {mib-2 5}
◆ tcp {mib-2 6}
◆ udp {mib-2 7}
◆ snmp {mib-2 11}
◆ host resources {mib-2 25}
◆ snmpv2 {internet 6}

For more information about the MIB-II MIB, see Appendix B, “MIB-II
(RFC 1213).” For more information about the Host Resources MIB,
see Appendix C, “Host Resources MIB (RFC 2790).”

Configuring SNMP There are two SNMP configuration pages: System SNMP
Configuration and RMG SNMP Configuration. The System SNMP
Configuration page is used to configure SNMP system-wide, whereas
the RMG SNMP Configuration page is used to configure SNMP for
one RMG. Both configuration pages are configured in the same way.
To configure SNMP:
1. Login as SysAdmin. The System Dashboard appears.
2. Do one of the following:
• To configure SNMP system-wide: In the Operations area, click
SNMP Configuration. The System SNMP Configuration page
appears.
• To configure SNMP for one RMG: In the RMG List area, click
Detail for a given RMG. The RMG Summary page for that
RMG appears. In the Operations area, click Configure SNMP.
The RMG SNMP Configuration page appears.

120 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

Both the System SNMP Configuration and RMG SNMP

Configuration pages are shown below.

3. (RMG configuration only) To use system-level SNMP settings for

this RMG, select the Use system SNMP configuration check box.
If you select Use system SNMP configuration, all other fields are
grayed out.

SNMP support 121

System Monitoring, Events, & Reporting

To configure SNMP for just the specified RMG, de-select Use

system SNMP configuration and continue below.

Note: If you previously specified system-level SNMP settings, Use

system SNMP configuration is selected. By deselecting it and
entering different information in the RMG SNMP Configuration
page, you can change the settings for just the specified RMG.

4. Fill out the fields in the NMS Configuration area:

• NMS Host Address — Enter the IP address or host name.
• NMS Host Port — Enter the port number. The default is 162.
• NMS Community Name — Enter the SNMP community
name for the NMS.
5. Fill out the fields in the SNMP Trap Configuration area:
• Enable SNMP Traps — Select this check box to enable the
configuration; this means SNMP trap messages are sent. If this
box is not checked, the configuration is saved but the “enable”
flag is not set, so SNMP trap messages are not sent.
• Select MIB Version — With Atmos 1.4.0, the Atmos MIB is
now located at SNMP OID tree area .1.3.6.1.4.1.1139.16.3.x as
listed in Table 9 on page 114. Atmos also supports the legacy
SNMP traps provided prior to Atmos 1.4.0 as listed in Table 10
on page 116.

Note: The setting for Enable SNMP applies to the entire system or
RMG (depending on whether you are using the System SNMP
Configuration or RMG SNMP Configuration page).

6. When the NMS Host Address, NMS Host Port, and Community
Name fields are filled in, the Test button is enabled. Click this to
test the connection to the NMS server. A “busy” icon is displayed
while the test is ongoing. The result message (the popup) will be
prompted after the test finishes.
• If the NMS server test is unsuccessful, one of several error
messages appears, depending on the circumstances. Retry the
test or contact EMC Customer Support.
• If the NMS server test is successful, a success message
appears; click OK to proceed. On the SNMP Configuration
page, the Add button is now enabled. Click Add; the NMS
server is added to the Atmos database, and information about

122 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

the server is listed on the SNMP Configuration page, as shown

below. For each server that you add, links are provided to Test
(to retest a server that was added previously) and Delete the
server.

7. (Optional) To add additional SNMP servers: specify additional

values for NMS Host Address, NMS Host Port, and NMS
Community Name. Click Test and wait for the test to complete,
then click Add. If multiple servers are configured, they are listed
on the SNMP Configuration page in the order in which they are
added, and they are tried by Atmos in that same order.
8. If needed, configure the trap(s) of interest as reporting conditions.
While some SNMP traps are enabled by default, some traps also
must be configured as reporting conditions to be enabled. These
traps are the ones listed in “SNMP traps” on page 114” that have
entries in the Monitor Target Value column. The Monitor Target
must be specified when configuring these traps as reporting
conditions.
9. Select the Enable SNMP Agent for MIB Access checkbox and fill
out the fields in the SNMP Agent Configuration area:

SNMP support 123

System Monitoring, Events, & Reporting

• SNMP Agent Community Name — Enter an agent

community name. This name will be compared with the NMS
Community Name used in the SNMP query. The two names
must match for the SNMP daemon to respond to the SNMP
query/request. For security reasons, it is recommended that a
SNMP agent community name other than public or private be
used as these are well-known default community names.
• SNMP Agent Contact Email — Optionally, enter an email
address of the system contact for SNMP information. This
field is populated in the “system” MIB, in the sysContact OID.
10. Click Submit.

Getting useful data The following commands can be used from a Linux command line
from the MIBs (which has snmpd available) to poll the MIB-II MIBs in the Atmos
system to retrieve useful information. The OIDs and MIB element
names can be used from any NMS to do polling as well. For more
information about the MIB-II MIB, see Appendix B, “MIB-II (RFC
1213).” For more information about the HOST-RESOURCES MIB, see
Appendix C, “Host Resources MIB (RFC 2790).”

Walking all of the MIB-II MIBs

To walk all of the MIB-II MIBs in one walk:
# snmpwalk -v2c -c community_string host-ip-addr .1.3.6.1

Walking the entire HOST-RESOURCES MIB

To walk the entire HOST-RESOURCES-MIB:
# snmpwalk -v2c -c community_string host-ip-addr
.1.3.6.1.2.1.25

Checking diskspace on an Atmos system

To find the number of disks on the system, use the following
command:
# snmpwalk -v2c -c community_string host-ip-addr
HOST-RESOURCES-MIB::hrStorageIndex

This command returns a table of hrStorageIndex items, each

representing a disk. The disk is referenced by the index number. For
example:
HOST-RESOURCES-MIB::hrStorageIndex.1 = INTEGER: 1
HOST-RESOURCES-MIB::hrStorageIndex.3 = INTEGER: 3
HOST-RESOURCES-MIB::hrStorageIndex.6 = INTEGER: 6

124 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

HOST-RESOURCES-MIB::hrStorageIndex.7 = INTEGER: 7
HOST-RESOURCES-MIB::hrStorageIndex.8 = INTEGER: 8
HOST-RESOURCES-MIB::hrStorageIndex.10 = INTEGER: 10
HOST-RESOURCES-MIB::hrStorageIndex.31 = INTEGER: 31
HOST-RESOURCES-MIB::hrStorageIndex.32 = INTEGER: 32
HOST-RESOURCES-MIB::hrStorageIndex.33 = INTEGER: 33
HOST-RESOURCES-MIB::hrStorageIndex.34 = INTEGER: 34
HOST-RESOURCES-MIB::hrStorageIndex.35 = INTEGER: 35
...
HOST-RESOURCES-MIB::hrStorageIndex.87 = INTEGER: 87
HOST-RESOURCES-MIB::hrStorageIndex.88 = INTEGER: 88
HOST-RESOURCES-MIB::hrStorageIndex.89 = INTEGER: 89

Finding disks
To find which disk is which, use the following command:
# snmpwalk -v2c -c community_string node-ip-addr
HOST-RESOURCES-MIB::hrStorageDescr

This command lists the name of each disk, indexed by same index
number as shown above. For example:
HOST-RESOURCES-MIB::hrStorageDescr.1 = STRING: Physical
memory
HOST-RESOURCES-MIB::hrStorageDescr.3 = STRING: Virtual
memory
HOST-RESOURCES-MIB::hrStorageDescr.6 = STRING: Memory
buffers
HOST-RESOURCES-MIB::hrStorageDescr.7 = STRING: Cached
memory
HOST-RESOURCES-MIB::hrStorageDescr.8 = STRING: Shared
memory
HOST-RESOURCES-MIB::hrStorageDescr.10 = STRING: Swap
space
HOST-RESOURCES-MIB::hrStorageDescr.31 = STRING: /
HOST-RESOURCES-MIB::hrStorageDescr.32 = STRING: /boot
HOST-RESOURCES-MIB::hrStorageDescr.33 = STRING:
/mauimds-db/mds-b2abb3f4-2584-437e-ac9c-03eecbd09b0e
HOST-RESOURCES-MIB::hrStorageDescr.34 = STRING:
/mauimds-db/mds-a80a27a5-7e8f-4627-8a1f-c6780f0971a3
HOST-RESOURCES-MIB::hrStorageDescr.35 = STRING:
/mauimds-db/mds-125c7b2a-6425-4003-9e12-7b929742fb4e
...
HOST-RESOURCES-MIB::hrStorageDescr.87 = STRING:
/mauiss-disks/ss-cc722b09-441b-4823-bc55-5e0aa4073e61
HOST-RESOURCES-MIB::hrStorageDescr.88 = STRING:
/mauiss-disks/ss-18ae1f82-3186-4504-8b25-f681f8174520
HOST-RESOURCES-MIB::hrStorageDescr.89 = STRING:
/mnt/mauifs

SNMP support 125

System Monitoring, Events, & Reporting

Accessing individual disks

To access an individual disk by index, use the following command:
# snmpget -v2c -c community_string node-ip-addr
HOST-RESOURCES-MIB::hrStorageDescr.node_index

This command returns the individual disk. For example:

HOST-RESOURCES-MIB::hrStorageDescr.89 = STRING:
/mnt/mauifs

Getting the total storage for all disks

To get the total storage for all the disks, use the following command:
# snmpwalk -v2c -c community_string node-ip-addr
HOST-RESOURCES-MIB::hrStorageSize

This command lists the total storage. For example:

HOST-RESOURCES-MIB::hrStorageSize.1 = INTEGER: 4057276
HOST-RESOURCES-MIB::hrStorageSize.3 = INTEGER: 10258356
HOST-RESOURCES-MIB::hrStorageSize.6 = INTEGER: 981856
HOST-RESOURCES-MIB::hrStorageSize.7 = INTEGER: 1804152
HOST-RESOURCES-MIB::hrStorageSize.8 = INTEGER: 0
HOST-RESOURCES-MIB::hrStorageSize.10 = INTEGER: 6201080
HOST-RESOURCES-MIB::hrStorageSize.31 = INTEGER: 55508749
HOST-RESOURCES-MIB::hrStorageSize.32 = INTEGER: 101086
HOST-RESOURCES-MIB::hrStorageSize.33 = INTEGER: 240358018
HOST-RESOURCES-MIB::hrStorageSize.34 = INTEGER: 240358018
HOST-RESOURCES-MIB::hrStorageSize.35 = INTEGER: 240358018
...
HOST-RESOURCES-MIB::hrStorageSize.87 = INTEGER: 240358018
HOST-RESOURCES-MIB::hrStorageSize.88 = INTEGER: 240358018
HOST-RESOURCES-MIB::hrStorageSize.89 = INTEGER: 962861504

Getting the total storage for a given disk

To get the total storage for a given disk, use the following command:
# snmpget -v2c -c community_string node-ip-addr
HOST-RESOURCES-MIB::hrStorageSize.node_index

This command returns the total storage for a given disk. For example:
HOST-RESOURCES-MIB::hrStorageSize.88 = INTEGER: 240358018

Getting the total used storage for all disks

To get the used storage for all the disks:, use the following command:
# snmpwalk -v2c -c community_string node-ip-addr
HOST-RESOURCES-MIB::hrStorageUsed

126 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

This command lists the total used storage for all disks. For example:
HOST-RESOURCES-MIB::hrStorageUsed.1 = INTEGER: 3708308
HOST-RESOURCES-MIB::hrStorageUsed.3 = INTEGER: 3708308
HOST-RESOURCES-MIB::hrStorageUsed.10 = INTEGER: 0
HOST-RESOURCES-MIB::hrStorageUsed.31 = INTEGER: 1219717
HOST-RESOURCES-MIB::hrStorageUsed.32 = INTEGER: 16091
HOST-RESOURCES-MIB::hrStorageUsed.33 = INTEGER: 56790
HOST-RESOURCES-MIB::hrStorageUsed.34 = INTEGER: 56592
HOST-RESOURCES-MIB::hrStorageUsed.35 = INTEGER: 56592
...
HOST-RESOURCES-MIB::hrStorageUsed.87 = INTEGER: 53718
HOST-RESOURCES-MIB::hrStorageUsed.88 = INTEGER: 53718
HOST-RESOURCES-MIB::hrStorageUsed.89 = INTEGER: 1251136

Getting the used storage for a given disk

To get the used storage for just one disk, use the following command:
# snmpget -v2c -c community_string node-ip-addr
HOST-RESOURCES-MIB::hrStorageUsed.node_index

This command returns the used storage for a given disk. For
example:
HOST-RESOURCES-MIB::hrStorageUsed.88 = 53718

Calculating the total free disk space

To calculate the total free disk space, subtract hrStorageUsed from
hrStorageSize.

Getting the system uptime

To get the amount of time since this host was last initialized, use the
following command:
# snmpget -v2c -c community_string node-ip-addr
HOST-RESOURCES-MIB::hrSystemUptime.node_index

This command returns the system uptime. For example:

HOST-RESOURCES-MIB::hrSystemUptime.0 = Timeticks:
(196243987) 22 days, 17:07:19.87

Getting the number of system users

To get the number of user sessions for which this host is storing state
information, use the following command:
# snmpget -v2c -c community_string node-ip-addr
HOST-RESOURCES-MIB::hrSystemNumUsers.node_index

SNMP support 127

System Monitoring, Events, & Reporting

This command returns the number of users. For example:

HOST-RESOURCES-MIB::hrSystemNumUsers.0 = Gauge32: 2

Getting the number of system processes

To get the number of processes currently running on a system, use the
following command:
# snmpget -v2c -c community_string node-ip-addr
HOST-RESOURCES-MIB::hrSystemProcesses.node_index

This command returns the number of processes. For example:

HOST-RESOURCES-MIB::hrSystemProcesses.0 = Gauge32: 318

Getting the maximum number of system processes

To get the maximum number of processes the system can support,
use the following command:
# snmpget -v2c -c community_string node-ip-addr
HOST-RESOURCES-MIB::hrSystemMaxProcesses.node_index

This command returns the maximum number of processes that the

system can support. A value of zero represents that there is no fixed
maximum value. For example:
HOST-RESOURCES-MIB::hrSystemMaxProcesses.0 = INTEGER: 0

Getting the memory size

To get the size of the memory, use the following command:
# snmpget -v2c -c community_string node-ip-addr
HOST-RESOURCES-MIB::hrMemorySize.node_index

This command returns the memory size. For example:

HOST-RESOURCES-MIB::hrMemorySize.0 = INTEGER: 4057276
KBytes

Getting the unique value for each device

To get the unique value for each device contained by the host, use the
following command:
# snmpwalk -v2c -c community-string node-ip-addr
HOST-RESOURCES-MIB::hrDeviceIndex

This command returns the unique value for each device. For
example:
HOST-RESOURCES-MIB::hrDeviceIndex.768 = INTEGER: 768
HOST-RESOURCES-MIB::hrDeviceIndex.769 = INTEGER: 769

128 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

HOST-RESOURCES-MIB::hrDeviceIndex.770 = INTEGER: 770

HOST-RESOURCES-MIB::hrDeviceIndex.771 = INTEGER: 771
HOST-RESOURCES-MIB::hrDeviceIndex.1025 = INTEGER: 1025
HOST-RESOURCES-MIB::hrDeviceIndex.1026 = INTEGER: 1026
HOST-RESOURCES-MIB::hrDeviceIndex.1027 = INTEGER: 1027
HOST-RESOURCES-MIB::hrDeviceIndex.1028 = INTEGER: 1028
HOST-RESOURCES-MIB::hrDeviceIndex.1552 = INTEGER: 1552
HOST-RESOURCES-MIB::hrDeviceIndex.1553 = INTEGER: 1553
HOST-RESOURCES-MIB::hrDeviceIndex.1554 = INTEGER: 1554
HOST-RESOURCES-MIB::hrDeviceIndex.1555 = INTEGER: 1555

Getting the device type

To get an indication of the type of device, use the following
command:
# snmpwalk -v2c -c community-string node-ip-addr
HOST-RESOURCES-MIB::hrDeviceType

This command returns the device type. For example:

HOST-RESOURCES-MIB::hrDeviceType.768 = OID:
HOST-RESOURCES-TYPES::hrDeviceProcessor
HOST-RESOURCES-MIB::hrDeviceType.769 = OID:
HOST-RESOURCES-TYPES::hrDeviceProcessor
HOST-RESOURCES-MIB::hrDeviceType.770 = OID:
HOST-RESOURCES-TYPES::hrDeviceProcessor
HOST-RESOURCES-MIB::hrDeviceType.771 = OID:
HOST-RESOURCES-TYPES::hrDeviceProcessor
HOST-RESOURCES-MIB::hrDeviceType.1025 = OID:
HOST-RESOURCES-TYPES::hrDeviceNetwork
HOST-RESOURCES-MIB::hrDeviceType.1026 = OID:
HOST-RESOURCES-TYPES::hrDeviceNetwork
HOST-RESOURCES-MIB::hrDeviceType.1027 = OID:
HOST-RESOURCES-TYPES::hrDeviceNetwork
HOST-RESOURCES-MIB::hrDeviceType.1028 = OID:
HOST-RESOURCES-TYPES::hrDeviceNetwork
HOST-RESOURCES-MIB::hrDeviceType.1552 = OID:
HOST-RESOURCES-TYPES::hrDeviceDiskStorage
HOST-RESOURCES-MIB::hrDeviceType.1553 = OID:
HOST-RESOURCES-TYPES::hrDeviceDiskStorage
HOST-RESOURCES-MIB::hrDeviceType.1554 = OID:
HOST-RESOURCES-TYPES::hrDeviceDiskStorage
HOST-RESOURCES-MIB::hrDeviceType.1555 = OID:
HOST-RESOURCES-TYPES::hrDeviceDiskStorage

Getting a description of the device

To get a textual description of a device, including the device’s
manufacturer, use the following command:
# snmpwalk -v2c -c community-string node-ip-addr
HOST-RESOURCES-MIB::hrDeviceDescr

SNMP support 129

System Monitoring, Events, & Reporting

This command returns a description of the device. For example:

HOST-RESOURCES-MIB::hrDeviceDescr.768 = STRING:
GenuineIntel: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
HOST-RESOURCES-MIB::hrDeviceDescr.769 = STRING:
GenuineIntel: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
HOST-RESOURCES-MIB::hrDeviceDescr.770 = STRING:
GenuineIntel: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
HOST-RESOURCES-MIB::hrDeviceDescr.771 = STRING:
GenuineIntel: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
HOST-RESOURCES-MIB::hrDeviceDescr.1025 = STRING: network
interface lo
HOST-RESOURCES-MIB::hrDeviceDescr.1026 = STRING: network
interface eth0
HOST-RESOURCES-MIB::hrDeviceDescr.1027 = STRING: network
interface eth1
HOST-RESOURCES-MIB::hrDeviceDescr.1028 = STRING: network
interface sit0
HOST-RESOURCES-MIB::hrDeviceDescr.1552 = STRING: SCSI
disk (/dev/sda)
HOST-RESOURCES-MIB::hrDeviceDescr.1553 = STRING: SCSI
disk (/dev/sdb)
HOST-RESOURCES-MIB::hrDeviceDescr.1554 = STRING: SCSI
disk (/dev/sdc)
HOST-RESOURCES-MIB::hrDeviceDescr.1555 = STRING: SCSI
disk (/dev/sdd)

Getting the average processor load

To get the average load (over the last minute) for each processor, use
the following command:
# snmpwalk -v2c -c community-string node-ip-addr
HOST-RESOURCES-MIB::hrProcessorLoad

This command returns the processor loads. For example:

HOST-RESOURCES-MIB::hrProcessorLoad.768 = INTEGER: 11
HOST-RESOURCES-MIB::hrProcessorLoad.769 = INTEGER: 13
HOST-RESOURCES-MIB::hrProcessorLoad.770 = INTEGER: 19
HOST-RESOURCES-MIB::hrProcessorLoad.771 = INTEGER: 15

Walking all of the Interfaces MIB

To walk all of the interfaces MIB in one walk, use the following
command:
# snmpwalk -v2c -c community_string node-ip-addr
.1.3.6.1.2.1.2.2.1

130 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

Getting the unique value for each network interface

To get the unique value for each interface, use the following
command:
# snmpwalk -v2c community_string node-ip-addr
IF-MIB::ifIndex

This command returns the unique values for each interface. For
example:
IF-MIB::ifIndex.1 = INTEGER: 1
IF-MIB::ifIndex.2 = INTEGER: 2
IF-MIB::ifIndex.3 = INTEGER: 3
IF-MIB::ifIndex.4 = INTEGER: 4

Getting information about an interface

To get a textual string containing information about the interface, use
the following command:
# snmpwalk -v2c community_string node-ip-addr
IF-MIB::ifDescr

This command returns information about the interface. For example:

IF-MIB::ifDescr.1 = STRING: lo
IF-MIB::ifDescr.2 = STRING: eth0
IF-MIB::ifDescr.3 = STRING: eth1
IF-MIB::ifDescr.4 = STRING: sit0

Getting the size of the largest datagram for the interface

To get the size of the largest datagram which can be sent/received on
the interface, use the following command:
# snmpwalk -v2c community_string node-ip-addr
IF-MIB::ifMtu

This command returns the size of the largest datagram. For example:
IF-MIB::ifMtu.1 = INTEGER: 16436
IF-MIB::ifMtu.2 = INTEGER: 1500
IF-MIB::ifMtu.3 = INTEGER: 1500
IF-MIB::ifMtu.4 = INTEGER: 1480

Getting the total number of octets received on an interface

To get the total number of octets received on the interface, use the
following command:
# snmpwalk -v2c community_string node-ip-addr
IF-MIB::ifInOctets

SNMP support 131

System Monitoring, Events, & Reporting

This command returns the total number of octets received. For

example:
IF-MIB::ifInOctets.1 = Counter32: 1952500246
IF-MIB::ifInOctets.2 = Counter32: 136256578
IF-MIB::ifInOctets.3 = Counter32: 1150405726
IF-MIB::ifInOctets.4 = Counter32: 0

Getting the number of subnetwork-unicast packets delivered

To get the number of subnetwork-unicast packets delivered to a
higher-layer protocol, use the following command:
# snmpwalk -v2c community_string node-ip-addr
IF-MIB::ifInUcastPkts

This command returns the number of subnetwork-unicast packets

delivered. For example:
IF-MIB::ifInUcastPkts.1 = Counter32: 71555905
IF-MIB::ifInUcastPkts.2 = Counter32: 1399123
IF-MIB::ifInUcastPkts.3 = Counter32: 46051539
IF-MIB::ifInUcastPkts.4 = Counter32: 0

Getting the total number of octets transmitted out of the interface

To get the total number of octets transmitted out of the interface,
including framing characters, use the following command:
# snmpwalk -v2c community_string node-ip-addr
IF-MIB::ifOutOctets

This command returns the total number of octets transmitted out of

the interface. For example:
IF-MIB::ifOutOctets.1 = Counter32: 1952500246
IF-MIB::ifOutOctets.2 = Counter32: 2953296189
IF-MIB::ifOutOctets.3 = Counter32: 16463471
IF-MIB::ifOutOctets.4 = Counter32: 0

Getting the total number of packets requested

To get the total number of packets that were requested, by
higher-level protocols, use the following command:
# snmpwalk -v2c community_string node-ip-addr
IF-MIB::ifOutUcastPkts

This command returns the total number of packets that were

requested. For example:

132 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

IF-MIB::ifOutUcastPkts.1 = Counter32: 71555905

IF-MIB::ifOutUcastPkts.2 = Counter32: 2025319
IF-MIB::ifOutUcastPkts.3 = Counter32: 22655375
IF-MIB::ifOutUcastPkts.4 = Counter32: 0

Getting the state of a node’s network interfaces using snmpnetstat

To get the state of a node’s network interface, use the following Linux
command:
# snmpnetstat -v2c -c community_string -i node-ip-addr

This command returns the state of the network interfaces.

System reports
Atmos can collect system configuration data and send a report to the
EMC System Reports database, through the System Report (SYR)
mechanism. System reports are sent to the EMC System Reports
Database to improve customer service, and allow EMC to provide
timely support for Atmos issues.

Configuring system The System Report Configuration page is used to configure Atmos to
reports be able to securely send Atmos configuration information to EMC
support personnel. This enables EMC to receive detailed information
about your Atmos environment, including: system information, RMG
information, and tenant information. An SMTP connection is used to
send the configuration information. Once the configuration
information is received, it is analyzed by a service automation tool
called SYR. SYR serves as a repository for configuration data and is
used to provide faster problem resolution.
The procedure in this section configures Atmos for system reporting.
To actually collect the data, see “Collecting system reports” on
page 138.
Before using system report configuration, a software serial number
must be provided and email service must be configured.
To configure system reports:
1. Login as SysAdmin. The System Dashboard appears.
2. In the Operations area, click System Report Configuration. The
System Report Configuration page appears.

System reports 133

System Monitoring, Events, & Reporting

If you have not already configured the software serial number

and an SMTP server, a warning message appears on the page and
you cannot configure system reporting.

3. To enable system reporting, select the Enable system report

service check box, and fill in the other fields on the page:
• Send email notification to customer upon successful
call-home—Select this checkbox to receive a copy of the
successful call-home XML event file.
• Send email notification to customer upon failed
call-home—Select this checkbox to receive a copy of the failed
call-home XML event file.
• Customer Name—The name of a contact person at the
customer site.
• Site ID—A value that uniquely identifies the site location.
• Customer Contact Email—An email address to which a
message is sent, indicating whether the report collection was
successful. If it was successful, a complete copy of the
collected data also is sent to this address.
• Customer Contact Name—Optional. Name of the customer
contact.
4. To disable system reporting that was already set up, deselect the
check box and click Save.
5. Click Save.

134 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

SYR symptom codes Atmos sends symptom codes of detected problems to the EMC
System Reports database through the System Report (SYR)
mechanism. Table 12 lists the symptom codes that are provided to
SYR.

Table 12 SYR Symptom Codes

Error Name Code Description

CRITICAL_NETWORK_RMG_LOST 0x00310001 Lost connection with RMG, and connection hasn’t been restored
for ~8 attempts.

CRITICAL_NETWORK_SEGMENT_LOST 0x00310002 Lost connection with Segment and connection hasn’t been
restored for ~8 attempts.

CRITICAL_SERVICE_APP_MEMORY 0x00410002 Service X’s memory usage exceeds threshold.

CRITICAL_SERVICE_MAUISS_CRASH 0x00410003 Atmos Storage Service crashed (or was killed) on node.

CRITICAL_SERVICE_MAUIRMS_CRASH 0x00410004 Atmos RMS Service crashed (or was killed) on node.

CRITICAL_SERVICE_MAUIMDLS_CRASH 0x00410005 Atmos MDLS Service crashed (or was killed) on node.

CRITICAL_SERVICE_MAUIMDS_CRASH 0x00410006 Atmos MDS Service crashed (or was killed) on node.

CRITICAL_SERVICE_HTTPD_CRASH 0x00410007 HTTPD Service crashed (or was killed) on node.

ERROR_SERVICE_APP_CRASH 0x00420009 Service X crashed (or was killed) on node.

ERROR_TENANT_POLICY_SYNC_FAIL 0x00620002 “mauicm_mauipmsync” failed. This means that a policy push did
not get done on all nodes. Some nodes will not have been
properly updated, which needs to be addressed.

ERROR_SYS_UID_SYNC_FAIL 0x00720003 “mauicm_synclb” failed. This means that the addition of a new
userID through Web Services failed. This causes a problem with
web access because the secret keys are not authorized/user is
not authorized so user cannot access the system through the
web.

CRITICAL_NODE_DISK_ERROR 0x00810001 A critical internal server (node) disk error has occurred. Do not
use the node. It must be replaced.

CRITICAL_NODE_DISK_REMOVED 0x00810002 An internal server (node) disk has been removed from node.

ERROR_NODE_DOWN 0x00820001 Connection to given node is down and has not been restored
after X attempts.

ERROR_NODE_TEMP_THRESHOLD 0x00820002 Temperature Threshold reached on Node

CRITICAL_DAE_DISK_FAIL 0x00910001 Critical DAE Disk failure.

CRITICAL_DAE_DISK_ERROR 0x00910002 Error on DAE disk.

CRITICAL_DAE_POWER_SUPPLY_ERROR 0x00910003 A power supply error occurred on the DAE.

System reports 135

System Monitoring, Events, & Reporting

Table 12 SYR Symptom Codes (continued)

Error Name Code Description

CRITICAL_DAE_EVENT 0x00910004 A critical event occurred on the DAE. (message from SCSI
enclosure Service).

ERROR_DAE_FAN_FAIL 0x00920001 Fan Failure on DAE.

ERROR_DAE_ENC_DOWN 0x00920002 Connection to DAE Enclosure was lost/DAE is down.

ERROR_DAE_TEMP_THRESHOLD 0x00920003 DAE Temperature threshold has been hit.

ERROR_DAE_DISK_ERROR 0x00920005 A non-critical error occurred on the DAE disk.

ERROR_DAE_RUN_DISK_REMOVED 0x00920006 A running disk was removed from the DAE enclosure.

CRITICAL_DELL_HW_STOR_MGMT_FAILURE 0x00A10001 StorageManagement-MIB::alertStorageManagementFailure

CRITICAL_DELL_HW_STOR_MGMT_NON_RECOVER 0x00A10002 StorageManagement-MIB::alertStorageManagementNonRecove

rable

CRITICAL_DELL_HW_CTRLR_FAILURE 0x00A10003 StorageManagement-MIB::alertControllerFailure

CRITICAL_DELL_HW_CTRLR_NON_RECOVER 0x00A10004 StorageManagement-MIB::alertControllerNonRecoverable

CRITICAL_DELL_HW_CHAN_FAILURE 0x00A10005 StorageManagement-MIB::alertChannelFailure

CRITICAL_DELL_HW_CHAN_NON_RECOVER 0x00A10006 StorageManagement-MIB::alertChannelNonRecoverable

CRITICAL_DELL_HW_ENCL_FAILURE 0x00A10007 StorageManagement-MIB::alertEnclosureFailure

CRITICAL_DELL_HW_ENCL_NON_RECOVER 0x00A10008 StorageManagement-MIB::alertEnclosureNonRecoverable

CRITICAL_DELL_HW_ARR_DISK_FAILURE 0x00A10009 StorageManagement-MIB::alertArrayDiskFailure

CRITICAL_DELL_HW_ARR_DISK_NON_RECOVER 0x00A1000A StorageManagement-MIB::alertArrayDiskNonRecoverable

CRITICAL_DELL_HW_EMM_FAILURE 0x00A1000B StorageManagement-MIB::alertEMMFailure

CRITICAL_DELL_HW_EMM_NON_RECOVER 0x00A1000C StorageManagement-MIB::alertEMMNonrecoverable

CRITICAL_DELL_HW_PS_FAILURE 0x00A1000D StorageManagement-MIB::alertPowerSupplyFailure

CRITICAL_DELL_HW_PS_NON_RECOVER 0x00A1000E StorageManagement-MIB::alertPowerSupplyNonRecoverable

CRITICAL_DELL_HW_TEMP_PROBE_FAILURE 0x00A1000F StorageManagement-MIB::alertTemperatureProbeFailure

CRITICAL_DELL_HW_TEMP_PROBE_NON_RECOVER 0x00A10010 StorageManagement-MIB::alertTemperatureProbeNonRecovera

ble

CRITICAL_DELL_HW_FAN_FAILURE 0x00A10011 StorageManagement-MIB::alertFanFailure

CRITICAL_DELL_HW_FAN_NON_RECOVER 0x00A10012 StorageManagement-MIB::alertFanNonRecoverable

CRITICAL_DELL_HW_BATTERY_FAILURE 0x00A10013 StorageManagement-MIB::alertBatteryFailure

136 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

Table 12 SYR Symptom Codes (continued)

Error Name Code Description

CRITICAL_DELL_HW_BATTERY_NON_RECOVER 0x00A10014 StorageManagement-MIB::alertBatteryNonRecoverable

CRITICAL_DELL_HW_VDISK_FAILURE 0x00A10015 StorageManagement-MIB::alertVirtualDiskFailure

CRITICAL_DELL_HW_VDISK_NON_RECOVER 0x00A10016 StorageManagement-MIB::alertVirtualDiskNonRecoverable

CRITICAL_DELL_HW_REDUNDANCY_LOST 0x00A10017 StorageManagement-MIB::alertRedundancyLost

WARNING_DELL_HW_STOR_MGMT_ERROR 0x00A30001 StorageManagement-MIB::alertStorageManagementWarning

WARNING_DELL_HW_CTRLR_ERROR 0x00A30002 StorageManagement-MIB::alertControllerWarning

WARNING_DELL_HW_CHAN_ERROR 0x00A30003 StorageManagement-MIB::alertChannelWarning

WARNING_DELL_HW_ENCL_ERROR 0x00A30004 StorageManagement-MIB::alertEnclosureWarning

WARNING_DELL_HW_ARR_DISK_ERROR 0x00A30005 StorageManagement-MIB::alertArrayDiskWarning

WARNING_DELL_HW_EMM_ERROR 0x00A30006 StorageManagement-MIB::alertEMMWarning

WARNING_DELL_HW_PS_ERROR 0x00A30007 StorageManagement-MIB::alertPowerSupplyWarning

WARNING_DELL_HW_TEMP_PROBE_ERROR 0x00A30008 StorageManagement-MIB::alertTemperatureProbeWarning

WARNING_DELL_HW_FAN_ERROR 0x00A30009 StorageManagement-MIB::alertFanWarning

WARNING_DELL_HW_BATTERY_ERROR 0x00A3000A StorageManagement-MIB::alertBatteryWarning

WARNING_DELL_HW_VDISK_ERROR 0x00A3000B StorageManagement-MIB::alertVirtualDiskWarning

WARNING_DELL_HW_REDUNDANDY_DEGRADED 0x00A3000C StorageManagement-MIB::alertRedundanncyDegraded

System reports 137

System Monitoring, Events, & Reporting

Collecting system The Collect System Report page is used to collect and then send
reports Atmos configuration information to EMC support personnel. This
feature is enabled and configured using the System Report
Configuration page. Once the configuration information is collected,
it is sent to a service automation tool called SYR, which serves as a
repository for configuration data and is used to provide faster
problem resolution.
Before you can collect system reports, you must configure system
reporting (see “Configuring system reports” on page 133).
EMC recommends that you collect a system report after installation
or upgrade, and both before and after making configuration changes.
This provides EMC with a record of the current configuration of a
customer's system, which can be helpful in resolving issues.
To collect system reports:
1. Login as SysAdmin. The System Dashboard appears.
2. In the Operations area, click Collect System Report. The Collect
System Report page appears, first indicating that system-report
information collection is in process, then indicating that the
information collection has completed and will be sent to SYR
(EMC’s internal name for its System Reporting group).

If you navigate away from the Collect System Report page before
the information collection completes, the information continues
to be collected and, if it succeeds, the report is sent. Regardless of
whether it succeeds, you do not receive any status information.

138 EMC Atmos Version 1.4.0 Administrator’s Guide

 System Monitoring, Events, & Reporting

Log files and log collection

Each Atmos node has numerous logs. The MDS and SS, for example,
maintain many log files that are used by Atmos to improve system
performance.
A portion of the available disk space is consumed by log files. For
example, the MDS maintains 1000 log files by default, which
consumes about 10 GB of disk space (once MDS has claimed this disk
space, it is reserved even if the objects that were written are deleted).
The SS also maintains many log files, which are removed every 12
hours by default. Logging defaults can be changed. For more
information, contact EMC Technical Support.
EMC Technical Support may ask you to collect logs for debugging
purposes.
To collect the logs:
1. Login as SysAdmin. The System Dashboard appears.
2. Under Operations, click Collect Logs. A warning notice appears:
log collection takes several minutes, impacts system performance,
and prevents you from doing anything else with the
system-management GUI.
3. To proceed, click OK. The Log Collection page appears.

Log files and log collection 139

System Monitoring, Events, & Reporting

4. To view the log, click Download the log package. (A log package is
a collection of logs from multiple nodes.) The log package
downloads, and you are prompted whether to open or save it.

5. Click Open, Save, or Cancel.

140 EMC Atmos Version 1.4.0 Administrator’s Guide

 8
Configuring NFS/CIFS
Access

This chapter describes how to export NFS and CIFS directly from
Atmos, using the system-management GUI.
This chapter describes the following topics:
◆ Overview ........................................................................................... 142
◆ Configuring NFS .............................................................................. 142
◆ Configuring CIFS ............................................................................. 145

Configuring NFS/CIFS Access 141

Configuring NFS/CIFS Access

Overview
This chapter describes how to export NFS and CIFS directly from
Atmos, using the system-management GUI.
To enable NFS or CIFS access to Atmos nodes:
◆ The SysAdmin adds Atmos nodes to a tenant, so that tenant (and
its subtenants) can be accessed via the NFS/CIFS service of those
nodes. For more information, see “Adding Nodes to a Tenant” on
page 70.
◆ Then the TenantAdmin or SubtenantAdmin adds or edits
mount-point shares of NFS/CIFS on the appropriate nodes, for a
specific subtenant. For more information, see “Configuring NFS”
on page 142 or “Configuring CIFS” on page 145.

Note: Before you configure NFS or CIFS access to Atmos, you should
synchronize your external servers’ times with your Atmos NTP server time
(see “Configuring NTP (Network Time Protocol)” on page 47.

Configuring NFS
1. Do one of the following:
• Login as SubtenantAdmin. The Subtenant Dashboard appears.
• Login as a TenantAdmin. On the Tenant Dashboard, in the
Subtenant List area, click Edit next to a subtenant. The
Subtenant Information page appears.
On either page (Subtenant Dashboard or Subtenant Information),
the area called Access Nodes for NFS/CIFS shows a list of nodes
with the NFS or CIFS service which can be accessed.

142 EMC Atmos Version 1.4.0 Administrator’s Guide

 Configuring NFS/CIFS Access

2. Under Service Type, click the appropriate NFS link. The Node
NFS Information page appears.

3. To get details about a share, move your mouse anywhere over the
table row for that share, and a popup window appears. To add a
new NFS share, click Add. To edit or delete a current share, click
Edit or Delete for that share. If you click Add or Edit, the NFS
Configuration page appears.

4. Add or edit the fields on the NFS Configuration page. Parameters

with red asterisks are required.

Field Description

Share Path If you are editing an existing share, this field is populated and
cannot be changed. This is a directory to which the user of the
service is to be given access. This should be the full path name
of the directory from the root of the tenant namespace.

Configuring NFS 143

Configuring NFS/CIFS Access

Field Description

Allow Host The hosts that access the share. Valid values are:
Single machine—A fully qualified domain name (which can be
resolved by the server), hostname (which can be resolved by the
server), or IP address.
Series of machines specified with wildcards—Use the * or ?
character to specify a string match. Wildcards are not to be used
with IP addresses; however, they may work accidentally if
reverse DNS lookups fail. When specifying wildcards in fully
qualified domain names, dots (.) are not included in the wildcard.
For example, *.example.com includes one.example.com but
does not include one.two.example.com.
IP networks—Use a.b.c.d/z, where a.b.c.d is the network and z is
the number of bits in the netmask (for example, 192.168.0.0/24).
Another acceptable format is a.b.c.d/netmask, where a.b.c.d is
the network and netmask is the netmask (for example,
192.168.100.8/255.255.255.0).
Netgroups—Use the format @group-name, where group-name
is the NIS netgroup name.

Permission Specifies whether the directory is read-only or has read/write

permissions The default is Read/Write.

Authorization User access. Valid values are:

all_squash—Treat all client users as anonymous users.
root_squash—Do not treat a remote root user as local root.
no_root_squash—Treat a remote root user as local root. This is
the default.

Sync Write If Yes, the server cannot reply to requests until the changes
made by the request are written to the disk. The default value is
Yes.
For advanced parameters, click the Advanced check box and
specify the advanced parameters. The advanced parameters are
used to define and map user and group IDs to anonymous
accounts. Advanced parameters are optional.

Secure If Yes, requires that all requests originate from a port lower than
1024. If No, requests from any port number are accepted. The
default is Yes.

Anonymous UID Sets the user ID of the anonymous account, to map all requests
to one user.

Anonymous GID Sets the group ID of the anonymous account, to map all requests
to one user.

Squash UIDs A list of user IDs that are subject to anonymous mapping; for
example: 0-15,20,25-50.

144 EMC Atmos Version 1.4.0 Administrator’s Guide

 Configuring NFS/CIFS Access

Field Description

Squash GIDs A list of group IDs that are subject to anonymous mapping; for
example, 0-15,20,25-50.

Configuring CIFS
All CIFS configuration should be done through the
system-management GUI. Do not modify the Samba/CIFS
configuration file manually.
Atmos does not support two different CIFS shares with the same
share path on different nodes, unless the nodes have been configured
for high availability. For more information on how to configure
highly available CIFS shares in an Atmos environment, see the EMC
Atmos CIFS Failover using Microsoft Distributed File System white
paper.

Active Directory Active Directory is supported for authenticating only CIFS users
(UIDs), not Atmos administrators.
The Atmos CIFS server can be a member of Microsoft Active
Directory. In this mode, clients can be authenticated centrally by an
Active Directory server. We recommend you use Active Directory
when most clients belong to a Windows domain.

Note: If you intend to configure Active Directory for CIFS authentication,

then before configuring CIFS node properties in the following procedure,
be sure to synchronize your Active Directory server time with your
Atmos NTP server time. For more information about configuring an
external NTP server, see the EMC Atmos Installation Guide.

1. Login as a TenantAdmin. On the Tenant Dashboard, in the

Subtenant List area, click Edit next to a subtenant. The Subtenant
Information page appears.
The area called Access Nodes for NFS/CIFS shows a list of nodes
with the NFS or CIFS service which can be accessed.

Configuring CIFS 145

Configuring NFS/CIFS Access

2. Under Service Type, click the appropriate CIFS link. The Node
CIFS Information page appears.

3. Do one of the following:

• To get details about a share, move your mouse anywhere over
the table row for that share, and a popup window appears.
• To delete a share, click Delete for that share. The Node CIFS
Information page gets updated by removing the share you
deleted.
• To prepare to add your first CIFS share, click Node
Configuration. The CIFS Node Configuration page appears.
Continue with “Configuring CIFS Node Properties” on
page 147. You should do node configuration before adding the
first share.
• To add a new CIFS share (after doing a CIFS Node
configuration), click Add. The CIFS Share Configuration page
appears. Continue with “Adding or Editing a CIFS Share” on
page 152.
• To edit an existing CIFS share, click Edit for that share. The
CIFS Share Configuration page appears. Continue with
“Adding or Editing a CIFS Share” on page 152.

146 EMC Atmos Version 1.4.0 Administrator’s Guide

 Configuring NFS/CIFS Access

Configuring CIFS 1. Start with the CIFS Node Configuration page.

Node Properties

2. Edit the fields on this page. If the Shared security option is

selected, you must provide a Netbios Name. If the ADS security
option is selected, you must provide the RID Range, Active
Directory Domain, Active Directory Administrator, Active
Directory Password, and Active Directory DNS parameters.

Field Description

Node Name The name of the node.

Workgroup The workgroup your server will appear to be in when queried by

clients. The default is WORKGROUP. When Security is set to
ADS, Workgroup is the short name of the domain. If you define
the wrong value, the server will not be able to join the ADS
domain.

Server String The string that will appear in the browse lists next to the machine
name. The default is EMC_Atmos.

Netbios Name The NetBIOS name by which a server is known. By default, this
is the same as the first component of the host's DNS name.

Configuring CIFS 147

Configuring NFS/CIFS Access

Field Description

Allowed Hosts A set of hosts which are permitted to access a service. Settings
apply to all services, regardless of whether the individual service
has a different setting. You can specify the hosts by name or IP
number. You also can specify hosts by network/netmask pairs
and by netgroup names if your system supports netgroups. The
default is no entry, meaning all hosts are allowed. Here are
several examples.
Example 1: Allow all IPs in 150.203.*.*; except one:
150.203. EXCEPT 150.203.6.66
Example 2: Allow hosts that match the given network/netmask:
150.203.15.0/255.255.255.0
Example 3: Allow two specific hosts:
lalans, calomb

Preferred Master Controls the election of a master node in the CIFS domain and
whether nmbd is a preferred master browser for its workgroup.
(nmbd is a daemon service involved in the CIFS server. It
queries the domain or share names in the domain.)
Valid values are Yes, No, and Auto. If Yes, nmbd has a slight
advantage in winning the election. If No, nmdb cannot win the
election. If Auto, the election is random. The default is No.

Encrypt Passwords Specifies whether to encrypt CIFS user passwords. By default,

Windows NT 4.0 SP3 and above and Windows 98 expect
encrypted passwords. The default is Yes.

Winbind Use Default Specifies whether the winbindd daemon operates on users
Domain without a domain component in their usernames. Users without a
domain component are treated as part of the winbindd server's
own domain. The default is No.

Inherit Permissions When the inherit permissions option is set to yes, the create
mask, directory mask, force create mode, and force directory
mode are ignored. The normal behavior of setting the
permissions on newly created files is overridden such that the
new files and directories take on permissions from their parent
directory. New directories will have exactly the same permissions
as the parent, and new files will inherit the read and write bits
from the parent directory, while the execute bits are determined
as usual by the values of the map archive, map hidden, and map
system parameters. If this option is set to yes, permissions on
new files and directories are inherited from parent directory. The
default value is no.

148 EMC Atmos Version 1.4.0 Administrator’s Guide

 Configuring NFS/CIFS Access

Field Description

Inherit ACLs CLs: This parameter can be used to ensure that if default ACLs
exist on parent directories, they are always honored when
creating a new file or subdirectory in these parent directories.
The default behavior is to use the UNIX mode specified when
creating the directory. Enabling this option sets the UNIX mode
to 0777, thus guaranteeing that default directory acls are
propagated. The default value is yes.

IDmap UID The range of user IDs that are allocated for the purpose of
mapping UNIX users to NT user SIDs. This range of user IDs
should not contain any existing local or NIS users; that is, it
should be beyond the maximum UID value of the local system, to
avoid overlapping.

IDmap GID The range of group IDs that are allocated for the purpose of
mapping UNIX groups to NT group SIDs. This range of group IDs
should not contain any existing local or NIS groups; that is, it
should be beyond the maximum GID value of the local system, to
avoid overlapping.

Configuring CIFS 149

Configuring NFS/CIFS Access

Field Description

Security Affects how clients respond to the server. There are two options,
Share and ADS. There are two security modes Atmos does not
support: User (because Atmos does not support internal CIFS
user management) and Domain.
* Share—The client authenticates itself separately for each
share. With each connection request, a client sends a password,
but not a user name (although modern CIFS client do send a
user name; for example, Windows XP sends the current login
name). The client expects a password to be associated with
each share, independent of the user. The CIFS server must
determine what user name the client wants to use.

Note: Share mode should only be used for testing purposes.

Atmos CIFS does not support user configuration, so with Share

security mode, the only use model is configuring a CIFS share
as an anonymous read-only server.
There are several techniques to determine the correct UNIX user
to use on behalf of the client:
1. If the Guest Only parameter is set, the user is immediately
granted access to the share with the rights of the user
“nobody,” no password checking is performed, and all new
files will belong to the user “nobody.”
2. If a username is sent with the share-connection request, that
username is added as a potential username.
3. If the client did a previous logon request (the SessionSetup
SMB call), the username sent in this SMB is added as a
potential username.
4. The name of the service the client requested is added as a
potential username.
5. The NetBIOS name of the client is added to the list as a
potential username.
6. Any users on the user list are added as potential usernames.
Active Directory:
* ADS—The Atmos CIFS server can be a member of Microsoft
Active Directory. In this mode, clients can be authenticated
centrally by an Active Directory server. We recommend you use
Active Directory when most clients belong to a Windows domain.
If ADS is selected, the CIFS Node Configuration page expands
to display the additional ADS settings (all fields listed below,
which appear below Security on the image above).

User Name Mapping By default, Atmos currently uses Active Directory Relative ID
(RID) user mapping schema. This schema maps the RID of an
object AD Security ID to a range specified in the CIFS
configuration to provide a unique ID for a user/group. This
schema is only valid for a Single Domain.

150 EMC Atmos Version 1.4.0 Administrator’s Guide

 Configuring NFS/CIFS Access

Field Description

RID Range Specifies the range of user/group IDs that are allocated for the
purpose of mapping UNIX users to NT user RIDs. This range of
user IDs should not contain any existing local or NIS users or
groups; that is, it should be beyond the maximum UID value of
the local system to avoid overlapping. A sample range is 20001 -
30000.

Active Directory The fully qualified domain name of the database server. The
Domain Active Directory domain is used as the Active Directory service
equivalent of the NT4 domain. This must be specified in
all-capital letters.

Active Directory A directory service used to store information about the network
Server resources. The Active Directory server is either an IP address or
a simple host name.

Active Directory The user name of the Active Directory administrator.

Administrator

Active Directory The password of the Active Directory administrator.

Password

Active Directory DNS The IP address or simple host name of the Active Directory DNS
server.

3. Click Submit.
As mentioned above, this configuration will fail unless your
external servers’ times are synchronized with the Atmos NTP
server time (see “Configuring NTP (Network Time Protocol)” on
page 47. To ensure this, a dialog box appears with the following
notice:
Is your Active Directory server time synchronized with
your Atmos NTP server time? If not, DO NOT PROCEED. See
the Atmos documentation for details.

If your Active Directory server times are synchronized, click OK

on the dialog, to return to the Node CIFS Information page.
Otherwise, click Cancel on the dialog, to return to the CIFS Node
Configuration page.

Configuring CIFS 151

Configuring NFS/CIFS Access

Adding or Editing a 1. Start with the CIFS Share Configuration page.

CIFS Share

2. Edit the fields on the CIFS Share Configuration page. Parameters

with red asterisks are required.

Field Description

Node Name The name of the node.

Tenant The tenant in which the node is a member.

Subtenant The subtenant in which the node is a member.

Share Name The name of the directory to be shared.

Share Path A directory to which the user of the service is to be given access.

Public If Yes, no password is required to connect to the service;

privileges are those of the guest account. The default is Yes.

Browseable Controls whether this share is seen in the list of available shares
in a net view and in the browse list. The default is Yes.

Read Only If Yes, users of the service cannot create or modify files in the
service's directory. The default is No.

Comments This text field is seen next to a share when a client queries the
server, either via the network neighborhood or via net view to list
what shares are available.

152 EMC Atmos Version 1.4.0 Administrator’s Guide

 Configuring NFS/CIFS Access

Field Description

Guest Only If Yes, only guest connections to the service are permitted. This
parameter has no effect unless Public is set for the service. The
default is Yes.

Valid Users A list of groups/users who are allowed to login to this service. If
this is empty (the default), any user can login. Groups are
specified using the @ symbol. To specify a group named
Group1, you would enter @Group1. To specify a user named
user1, you would enter user1. To specify both Group1 and
User1, you would enter: @Group1, User1

Create Mask When a file is created, the necessary permissions are calculated
according to the mapping from DOS modes to UNIX
permissions, and the resulting UNIX mode is bit-wise AND-ed
with this parameter. This parameter may be thought of as a
bit-wise mask for a file’s UNIX access modes. Any bit not set
here is removed from the modes set on a file when it is created.
The default value of this parameter removes the “group” and
“other” write and execute bits from the UNIX modes.

Directory Mask The octal modes used when converting DOS modes to UNIX
modes when creating UNIX directories. When a directory is
created, the necessary permissions are calculated according to
the mapping from DOS modes to UNIX permissions, and the
resulting UNIX mode is bit-wise AND-ed with this parameter.
This parameter may be thought of as a bit-wise mask for a
directory’s UNIX access modes. Any bit not set here is removed
from the modes set on a directory when it is created. The default
value of this parameter removes the “group” and “other” write bits
from the UNIX mode, allowing only the user who owns the
directory to modify it.

Write Cache Size his option allows Samba to improve performance on systems
where the disk subsystem is a bottleneck. The value of this
option is specified in bytes, and a size of 262,144 represent a
256k cache size per file. The default Write Cache Size is
8,388,608 bytes.

Force Unknown ACL The ACLs that result on a Samba server will most probably not
User match the originating ACLs. Windows supports the possibility of
files that are owned only by a group. Group-alone file ownership
is not possible under UNIX/Linux. Errors in migrating
group-owned files can be avoided by using the Force Unknown
ACL User = yes parameter. This option will automatically convert
group-owned files into correctly user-owned files on the Samba
server.

Configuring CIFS 153

Configuring NFS/CIFS Access

Field Description

Write List A list of groups/users who have read-write access to a service

(comma separated). This option overrides the Read Only
parameter. To specify a group named Group1, you would enter
@Group1. To specify a user named user1, you would enter
user1. To specify both Group1 and User1, you would enter:
@Group1, User1

3. Click Submit. You return to the Node CIFS Information page.

154 EMC Atmos Version 1.4.0 Administrator’s Guide

 9
Getting Performance
Data

This chapter explains how to obtain performance data from any

workstation that can access an Atmos server. This chapter describes
the following topics:
◆ Overview ........................................................................................... 156
◆ Example: Getting the Statistics....................................................... 157
◆ Example: Resetting the Counters................................................... 159

Getting Performance Data 155

Getting Performance Data

Overview
The /wsstats Web page presents basic Web-services performance
data. Performance data can be obtained by anyone with network
access to the HTTP servers that run on Atmos nodes. There are two
ways to get the performance data. From any workstation that can
access an Atmos server running httpd (the HTTP daemon), do one of
the following:
◆ Point your browser to http://node-name/wsstats on the master
node of an installation segment. The performance data for that
server is displayed.
◆ Run a program to do a GET of http://node-name/wsstats on the
master node of an installation segment. A simple XML document
is returned for reading or machine consumption. An example is
shown below; the items you input are in bold.
Above, node-name is the Atmos node name or IP address of an Atmos
server running httpd. For many installations, this is an IP address. If
the node on which the Apache Web server is installed has a Fully
Qualified Domain Name (FQDN), however, a hostname is returned
(as shown in “Example: Getting the Statistics” on page 157).
Each node has a separate instance of the Web server and, hence, a
separate instance of wsstats to be collected. If there is a load balancer
in front of Atmos at your installation (a common occurrence),
node-name is not the concentrator, but the Atmos nodes to which the
concentrator points.

156 EMC Atmos Version 1.4.0 Administrator’s Guide

 Getting Performance Data

Example: Getting the Statistics

The example requests use REST request syntax.
In the examples, curl is a command utility that allows one to do
HTTP transactions from the command line, instead of interactively
using a browser.

Request [root@deuce /]# curl -v http://10.5.113.242/wsstats

* About to connect() to 10.5.113.242 port 80 (#0)
* Trying 10.5.113.242... connected
* Connected to 10.5.113.242 (10.5.113.242) port 80 (#0)
> GET /wsstats HTTP/1.1
> User-Agent: curl/7.16.4 (x86_64-redhat-linux-gnu)
libcurl/7.16.4 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.8
> Host: 10.5.113.242
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 27 May 2009 21:03:39 GMT
< Server: Apache
< Content-Length: 559
< Connection: close
< Content-Type: text/xml;charset=ascii

Response <WSStat>
<Node name="10.5.113.242"/>
<ReadsPerSec>675.80</ReadsPerSec>
<WritesPerSec>1102.43</WritesPerSec>
<DeletesPerSec>171.57</DeletesPerSec>
<TransPerSec>1949.80</TransPerSec>
<MeanReadLatencyMS>4.557</MeanReadLatencyMS>
<MeanWriteLatencyMS>153.282</MeanWriteLatencyMS>
<MeanLatencyMS>89.206</MeanLatencyMS>
<Reads>31087</Reads>
<Writes>50712</Writes>
<Deletes>7892</Deletes>
<Total>89691</Total>
<ReadLatencyMS>141660</ReadLatencyMS>
<WriteLatencyMS>7773233</WriteLatencyMS>
<DeleteLatencyMS>86112</DeleteLatencyMS>
<UptimeMS>46711</UptimeMS>
</WSStat>
* Closing connection #0
[root@deuce /]#

Example: Getting the Statistics 157

Getting Performance Data

Browser Output

Output Fields The output is interpreted as follows:

◆ Node name is the server name in the node-name field of the
request for the /wsstats page, as defined by the Apache Web
server when it logs.
◆ Reads, Writes, and Deletes are defined in Table 13.

Table 13 Reads, Writes, and Deletes

REST SOAP

Reads GET and HEAD transactions List, Get, and Read transactions

Writes PUT and POST transactions Create, Set, Update, and Version Transactions

Deletes DELETE transactions Delete transactions

◆ Total is the sum of reads, writes, and deletes.

◆ The per-second (PerSec) rate for each of the three transaction
types is calculated as the count divided by the total uptime since
the last server restart.
◆ Mean latency is the sum of the individual latencies reported at
logging time, divided by the total number of transactions. There
also are latencies calculated by operation type in a similar
manner.

158 EMC Atmos Version 1.4.0 Administrator’s Guide

 Getting Performance Data

◆ Separately, the total accumulated latency is reported for each

operation (ReadLatencyMS, WriteLatencyMS, and
DeleteLatencyMS) and for the uptime (UptimeLatencyMS), in
milliseconds. This allows you to sample at any required
frequency and calculate latencies for that interval.

Example: Resetting the Counters

To reset all the counters, add the query string ?reset:

Request [romanm2@deuce ~]$ curl -v

http://deuce.lss.emc.com/wsstats?reset
* About to connect() to deuce.lss.emc.com port 80 (#0)
* Trying 168.159.116.103... connected
* Connected to deuce.lss.emc.com (168.159.116.103) port
80 (#0)
> GET /wsstats?reset HTTP/1.1
> User-Agent: curl/7.16.4 (x86_64-redhat-linux-gnu)
libcurl/7.16.4 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.8
> Host: deuce.lss.emc.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 30 Jul 2008 18:27:03 GMT
< Server: Apache/2.2.8 (Fedora)
< Content-Length: 276
< Connection: close
< Content-Type: text/xml;charset=ascii

Example: Resetting the Counters 159

Getting Performance Data

Response <WSStat>
<Node name="deuce.lss.emc.com"/>
<ReadsPerSec>0.00</ReadsPerSec>
<WritesPerSec>0.00</WritesPerSec>
<DeletesPerSec>0.00</DeletesPerSec>
<TransPerSec>0.00</TransPerSec>
<MeanReadLatencyMS>0.000</MeanReadLatencyMS>
<MeanWriteLatencyMS>0.000</MeanWriteLatencyMS>
<MeanLatencyMS>0.000</MeanLatencyMS>
<Reads>0</Reads>
<Writes>0</Writes>
<Deletes>0</Deletes>
<Total>0</Total>
<ReadLatencyMS>0</ReadLatencyMS>
<WriteLatencyMS>0</WriteLatencyMS>
<DeleteLatencyMS>0</DeleteLatencyMS>
<UptimeMS>0</UptimeMS>
</WSStat>
* Closing connection #0

160 EMC Atmos Version 1.4.0 Administrator’s Guide

 A

Atmos MIB

This appendix provides descriptions and other information specific

to the Atmos MIB, and includes the following sections:
◆ Atmos MIB Version Group............................................................. 162
◆ Atmos Software Version Group..................................................... 162
◆ Atmos Capacity Group ................................................................... 162
◆ Atmos Service Status Group........................................................... 166
◆ Atmos Metadata Service Group..................................................... 167
◆ Atmos Storage Service Group ........................................................ 167
◆ Atmos Job Service Group................................................................ 168
◆ Atmos Web Service Group ............................................................. 170
◆ Atmos Notification Group.............................................................. 171
◆ Atmos Group Conformance Information..................................... 175
◆ Atmos Conformance Information ................................................. 176

Atmos MIB 161

Atmos MIB

Atmos MIB Version Group

atmosMibMajorVersion
OID: 1.3.6.1.4.1.1139.16.3.1.1
The major version of the MIB this SNMP agent implemented.

atmosMibMinorVersion
OID: 1.3.6.1.4.1.1139.16.3.1.2
The minor version of the MIB this SNMP agent implemented.

Atmos Software Version Group

atmosVersion
OID: 1.3.6.1.4.1.1139.16.3.10.1
Atmos software version currently installed, e.g., '1.3.0-b48080'.

Atmos Capacity Group

atmosNodeCapacityStorageCapacity
OID: 1.3.6.1.4.1.1139.16.3.80.1
The scalar value of the storage capacity on the current node which is
capable for the client.

atmosNodeCapacityStorageCapacityUnit
OID: 1.3.6.1.4.1.1139.16.3.80.2
The data unit for the scalar value of the storage capacity on the
current node which is capable for the client.

162 EMC Atmos Version 1.4.0 Administrator’s Guide

 Atmos MIB

atmosNodeCapacityStorageUsed
OID: 1.3.6.1.4.1.1139.16.3.80.3
The scalar value of the occupied storage space by the client on the
current node, including both Metadata and Data.

atmosNodeCapacityStorageUsedUnit
OID: 1.3.6.1.4.1.1139.16.3.80.4
The data unit for the scalar value of the occupied storage space by the
client on the current node, including both Metadata and Data.

atmosNodeCapacityStorageAvailable
OID: 1.3.6.1.4.1.1139.16.3.80.5
The scalar value of the available storage space on the current node for
the client.

atmosNodeCapacityStorageAvailableUnit
OID: 1.3.6.1.4.1.1139.16.3.80.6
The data unit for the scalar value of the available storage space on the
current node for the client.

atmosNodeCapacityStoragePercentUsed
OID: 1.3.6.1.4.1.1139.16.3.80.7
The occupied storage space by the client in percentage on the current
node, including both Metadata and Data.

atmosNodeCapacityMetadataCapacity
OID: 1.3.6.1.4.1.1139.16.3.80.8
The scalar value of the storage capacity for Metadata on the current
node.

Atmos Capacity Group 163

Atmos MIB

atmosNodeCapacityMetadataCapacityUnit
OID: 1.3.6.1.4.1.1139.16.3.80.9
The data unit for the scalar value of the storage capacity for Metadata
on the current node.

atmosNodeCapacityMetadataUsed
OID: 1.3.6.1.4.1.1139.16.3.80.10
The scalar value of the occupied storage space by Metadata on the
current node.

atmosNodeCapacityMetadataUsedUnit
OID: 1.3.6.1.4.1.1139.16.3.80.11
The data unit for the scalar value of the occupied storage space by
Metadata on the current node.

atmosNodeCapacityMetadataAvailable
OID: 1.3.6.1.4.1.1139.16.3.80.12
The scalar value of the available storage space for Metadata on the
current node.

atmosNodeCapacityMetadataAvailableUnit
OID: 1.3.6.1.4.1.1139.16.3.80.13
The data unit for the scalar value of the available storage space for
Metadata on the current node.

atmosNodeCapacityMetadataPercentUsed
OID: 1.3.6.1.4.1.1139.16.3.80.14
The occupied storage space by Metadata in percentage on the current
node.

164 EMC Atmos Version 1.4.0 Administrator’s Guide

 Atmos MIB

atmosNodeCapacityDataCapacity
OID: 1.3.6.1.4.1.1139.16.3.80.15
The scalar value of the storage capacity for Data on current node.

atmosNodeCapacityDataCapacityUnit
OID: 1.3.6.1.4.1.1139.16.3.80.16
The data unit for the scalar value of the storage capacity for Data on
current node.

atmosNodeCapacityDataUsed
OID: 1.3.6.1.4.1.1139.16.3.80.17
The scalar value of the occupied storage space by Data on the current
node.

atmosNodeCapacityDataUsedUnit
OID: 1.3.6.1.4.1.1139.16.3.80.18
The data unit for the scalar value of the occupied storage space by
Data on the current node.

atmosNodeCapacityDataAvailable
OID: 1.3.6.1.4.1.1139.16.3.80.19
The scalar value of the available storage space for Data on the current
node.

atmosNodeCapacityDataAvailableUnit
OID: 1.3.6.1.4.1.1139.16.3.80.20
The data unit for the scalar value of the available storage space for
Data on current node.

Atmos Capacity Group 165

Atmos MIB

atmosNodeCapacityDataPercentUsed
OID: 1.3.6.1.4.1.1139.16.3.80.21
The occupied storage space by Data in percentage on the current
node.

Atmos Service Status Group

atmosServiceActiveEntries
OID: 1.3.6.1.4.1.1139.16.3.90.1
The number of available Atmos services in the system.

atmosServiceTable
OID: 1.3.6.1.4.1.1139.16.3.90.2
A table defining each Atmos service's detail status entry.

atmosServiceEntry
OID: 1.3.6.1.4.1.1139.16.3.90.2.1
An entry describing a given Atmos service's detail status information.

atmosServiceIndex
OID: 1.3.6.1.4.1.1139.16.3.90.2.1.1
The index for a given Service status instance.

atmosServiceName
OID: 1.3.6.1.4.1.1139.16.3.90.2.1.2
The name of the Atmos service.

atmosServiceStatus
OID: 1.3.6.1.4.1.1139.16.3.90.2.1.3
The current status of the Atmos service.

atmosServiceLatency
OID: 1.3.6.1.4.1.1139.16.3.90.2.1.4
The latency of the Atmos service in microseconds.

166 EMC Atmos Version 1.4.0 Administrator’s Guide

 Atmos MIB

atmosServiceOid
OID: 1.3.6.1.4.1.1139.16.3.90.2.1.5
The corresponding OID of the Atmos service, which can be queried to
get more details about the service. If not applicable, should set as .0.

atmosServiceMemoryUsed
OID: 1.3.6.1.4.1.1139.16.3.90.2.1.6
The memory used by the Atmos service.

atmosServiceMemoryUsedUnit
OID: 1.3.6.1.4.1.1139.16.3.90.2.1.7
The data unit for the memory used by the Atmos service.

Atmos Metadata Service Group

atmosMDSUpmasterCount
OID: 1.3.6.1.4.1.1139.16.3.100.1
The number of masters for replication.

atmosMDSContainerCount
OID: 1.3.6.1.4.1.1139.16.3.100.2
The number of containers.

atmosMDSReplicaGroupCount
OID: 1.3.6.1.4.1.1139.16.3.100.3
The number of replication groups.

Atmos Storage Service Group

Atmos storage service destage status.

Atmos Metadata Service Group 167

Atmos MIB

atmosSSDestageStatus
OID: 1.3.6.1.4.1.1139.16.3.110.1
Currently destage status of the Atmos Storage Service.

Atmos Job Service Group

Atmos Job queue status type.

atmosJSQueueStatus
OID: 1.3.6.1.4.1.1139.16.3.120.1
Current status of the Job Service queue.

atmosJSQueueLength
OID: 1.3.6.1.4.1.1139.16.3.120.2
The length of the Job Service queue.

atmosJSRecoverQueueLength
OID: 1.3.6.1.4.1.1139.16.3.120.3
The number of jobs on the Job Service recover queue.

atmosJSRecoverDequeueRate
OID: 1.3.6.1.4.1.1139.16.3.120.5
The rate of jobs being dequeued from the Job Service recover queue,
in jobs per second.

atmosJSRecoverByteRate
OID: 1.3.6.1.4.1.1139.16.3.120.6
The rate of Job Service recovery data transferred.

168 EMC Atmos Version 1.4.0 Administrator’s Guide

 Atmos MIB

atmosJSReclaimQueueLength
OID: 1.3.6.1.4.1.1139.16.3.120.7
The number of jobs on the Job Service reclaim queue.

atmosJSReclaimDequeueRate
OID: 1.3.6.1.4.1.1139.16.3.120.9
The rate of jobs being dequeued from the Job Service reclaim queue,
in jobs per second.

atmosJSReclaimByteRate
OID: 1.3.6.1.4.1.1139.16.3.120.10
The rate of Job Service reclamation data transferred.

atmosJSReplicateQueueLength
OID: 1.3.6.1.4.1.1139.16.3.120.11
The number of jobs on the Job Service replicate queue.

atmosJSReplicateDequeueRate
OID: 1.3.6.1.4.1.1139.16.3.120.13
The rate of jobs being dequeued from the Job Service replicate queue,
in jobs per second.

atmosJSReplicateByteRate
OID: 1.3.6.1.4.1.1139.16.3.120.14
The rate of Job Service replication data transferred.

atmosJSVerifyQueueLength
OID: 1.3.6.1.4.1.1139.16.3.120.18
The number of jobs on the Job Service verify queue.

Atmos Job Service Group 169

Atmos MIB

atmosJSVerifyDequeueRate
OID: 1.3.6.1.4.1.1139.16.3.120.20
The rate of jobs being dequeued from the Job Service verify queue, in
jobs per second.

atmosJSVerifyByteRate
OID: 1.3.6.1.4.1.1139.16.3.120.21
The rate of Job Service verification data transferred.

Atmos Web Service Group

atmosWSReadsPerSec
OID: 1.3.6.1.4.1.1139.16.3.140.1
The number of reads per second from the web service interface for
the current node.

atmosWSWritesPerSec
OID: 1.3.6.1.4.1.1139.16.3.140.2
The number of writes per second from the web service interface for
the current node.

atmosWSDeletesPerSec
OID: 1.3.6.1.4.1.1139.16.3.140.3
The number of deletes per second from the web service interface for
the current node.

atmosWSTransPerSec
OID: 1.3.6.1.4.1.1139.16.3.140.4
The number of transactions per second from the web service interface
for the current node.

170 EMC Atmos Version 1.4.0 Administrator’s Guide

 Atmos MIB

Atmos Notification Group

atmosNotificationVariables
OID: 1.3.6.1.4.1.1139.16.3.1000.1

atmosNotificationNode
OID: 1.3.6.1.4.1.1139.16.3.1000.1.1
The name of the Atmos node that generated the notification.

atmosNotificationNodeUUID
OID: 1.3.6.1.4.1.1139.16.3.1000.1.2
The UUID of the Atmos node that generated the notification.

atmosNotificationOID
OID: 1.3.6.1.4.1.1139.16.3.1000.1.3
The OID that was used to identity the object which caused this
notification. If not applicable, should set as .0.

atmosNotificationCurrentStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.1.4
The current status of the object which caused this notification.

atmosNotificationPreviousStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.1.5
The previous status of the object which caused this notification.

atmosNotificationMessage
OID: 1.3.6.1.4.1.1139.16.3.1000.1.6
Detail message for this notification.

atmosNotificationCpuUsage
OID: 1.3.6.1.4.1.1139.16.3.1000.101
This notification is used to report the CPU usage status change on the
system.

Atmos Notification Group 171

Atmos MIB

atmosNotificationMemoryUsage
OID: 1.3.6.1.4.1.1139.16.3.1000.102
This notification is used to report the physical memory usage status
change on the system.

atmosNotificationSwapUsage
OID: 1.3.6.1.4.1.1139.16.3.1000.103
This notification is used to report the swap usage status change on
the system.

atmosNotificationFilesystemUsage
OID: 1.3.6.1.4.1.1139.16.3.1000.104
This notification is used to report the file system disk space usage
status change.

atmosNotificationServiceMemoryUsage
OID: 1.3.6.1.4.1.1139.16.3.1000.105
This notification is used to report the Atmos service memory usage
status change on the system.

atmosNotificationServiceStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.106
This notification is used to report the Atmos service status change.

atmosNotificationInternalCarrierStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.107
This notification is used to report the internal carrier status change,
e.g., eth0 is disconnected.

172 EMC Atmos Version 1.4.0 Administrator’s Guide

 Atmos MIB

atmosNotificationExternalCarrierStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.108
This notification is used to report the external carrier status change,
e.g., eth1 is disconnected.

atmosNotificationNodeStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.109
This notification is used to report the Atmos node status change.

atmosNotificationSegmentStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.110
This notification is used to report the Atmos segment status change.

atmosNotificationRMGStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.111
This notification is used to report the Atmos RMG status change.

atmosNotificationPolicySyncFailed
OID: 1.3.6.1.4.1.1139.16.3.1000.112
This notification is used to report the policy distribution failure.

atmosNotificationUidSyncFailed
OID: 1.3.6.1.4.1.1139.16.3.1000.113
This notification is used to report the UID distribution failure.

atmosNotificationDAEStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.114
This notification is used to report the DAE status change of the
system.

Atmos Notification Group 173

Atmos MIB

atmosNotificationDAEBackplaneStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.115
This notification is used to report the DAE backplane status change of
the system.

atmosNotificationDAEFanStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.116
This notification is used to report the DAE fan status change of the
system.

atmosNotificationDAETempStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.117
This notification is used to report the DAE temperature status change
of the system.

atmosNotificationDiskStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.118
This notification is used to report the disk status change of the
system.

atmosNotificationPolicyResourceStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.119
This notification is used to report the policy resource status of the
system.

atmosNotificationMgmtDBStatus
OID: 1.3.6.1.4.1.1139.16.3.1000.120
This notification is used to report the policy resource failure of the
system.

174 EMC Atmos Version 1.4.0 Administrator’s Guide

 Atmos MIB

atmosNotificationDiskRecovery
OID: 1.3.6.1.4.1.1139.16.3.1000.121
This notification is used to report a file system's critical state, trigger
recovery.

atmosNotificationVIPFailover
OID: 1.3.6.1.4.1.1139.16.3.1000.122
This notification is used to report a VIP failover event.

Atmos Group Conformance Information

atmosMibVersionGroup
OID: 1.3.6.1.4.1.1139.16.3.2000.1
Atmos MIB version group.

atmosSoftwareVersionGroup
OID: 1.3.6.1.4.1.1139.16.3.2000.2
Atmos software version group.

atmosNodeCapacityGroup
OID: 1.3.6.1.4.1.1139.16.3.2000.9
Atmos node capacity group.

atmosServiceGroup
OID: 1.3.6.1.4.1.1139.16.3.2000.10
Atmos service group.

Atmos Group Conformance Information 175

Atmos MIB

atmosMetadataServiceGroup
OID: 1.3.6.1.4.1.1139.16.3.2000.11
Atmos metadata service group.

atmosStorageServiceGroup
OID: 1.3.6.1.4.1.1139.16.3.2000.12
Atmos storage service group.

atmosJobServiceGroup
OID: 1.3.6.1.4.1.1139.16.3.2000.13
Atmos job service group.

atmosWebServiceGroup
OID: 1.3.6.1.4.1.1139.16.3.2000.15
Atmos web service group.

atmosNotificationVariableGroup
OID: 1.3.6.1.4.1.1139.16.3.2000.19
Atmos notification variables group.

atmosNotificationGroup
OID: 1.3.6.1.4.1.1139.16.3.2000.20
Atmos notification group.

Atmos Conformance Information

atmosCompliance
OID: 1.3.6.1.4.1.1139.16.3.2010.1

176 EMC Atmos Version 1.4.0 Administrator’s Guide

 B

MIB-II (RFC 1213)

This appendix provides descriptions and other information specific

to MIB-II, and includes the following sections:
◆ MIB II overview................................................................................ 178
◆ Textual conventions......................................................................... 178
◆ Objects and types imported............................................................ 179
◆ System group .................................................................................... 179
◆ Interfaces group................................................................................ 181
◆ AT Group .......................................................................................... 186
◆ IP group ............................................................................................. 187
◆ ICMP group ...................................................................................... 198
◆ TCP group ......................................................................................... 202
◆ UDP group ........................................................................................ 206
◆ EGP group......................................................................................... 208
◆ Transmission group ......................................................................... 211
◆ SNMP group ..................................................................................... 212

MIB-II (RFC 1213) 177

MIB-II (RFC 1213)

MIB II overview
The descriptions of each of the MIB variables in this chapter come
directly from the MIB-II itself.

Textual conventions
Table 14 lists the textual conventions used for MIB-II.

Table 14 MIB-II textual conventions

Type definition Value

DisplayString Octet String of size 0 to 255

PhysAddress Octet String

178 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

Objects and types imported

The following objects and types are imported from RFC1155-SMI:
◆ mgmt
◆ NetworkAddress
◆ IpAddress
◆ Counter
◆ Gauge
◆ TimeTicks

System group
All systems must implement the System group. If an agent is not
configured to have a value for any of the System group variables, a
string of length 0 is returned.

sysDescr
OID: 1.3.6.1.2.1.1.1
A textual description of the entity. This value should include the full
name and version identification of the system's hardware type,
software operating-system, and networking software. It is mandatory
that this only contain printable ASCII characters.

sysObjectID
OID: 1.3.6.1.2.1.1.2
The vendor's authoritative identification of the network management
subsystem contained in the entity. This value is allocated within the
SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and
unambiguous means for determining `what kind of box' is being
managed. For example, if vendor `Flintstones, Inc.' was assigned the
subtree 1.3.6.1.4.1.4242, it could assign the identifier
1.3.6.1.4.1.4242.1.1 to its `Fred Router'.

Objects and types imported 179

MIB-II (RFC 1213)

sysUpTime
OID: 1.3.6.1.2.1.1.3
The time (in hundredths of a second) since the network management
portion of the system was last reinitialized.

sysContact
OID: 1.3.6.1.2.1.1.4
The textual identification of the contact person for this managed
node, together with information on how to contact this person.

sysName
OID: 1.3.6.1.2.1.1.5
An administratively-assigned name for this managed node. By
convention, this is the node’s fully qualified domain name.

sysLocation
OID: 1.3.6.1.2.1.1.6
The physical location of this node (for example, telephone closet, 3rd
floor).

sysServices
OID: 1.3.6.1.2.1.1.7
A value which indicates the set of services that this entity primarily
offers. The value is a sum. This sum initially takes the value zero.
Then, for each layer, L, in the range 1 through 7, that this node
performs transactions for, 2 raised to (L - 1) is added to the sum. For
example, a node which primarily performs routing functions has a
value of 4 (23-1). In contrast, a node that is a host and offers
application services has a value of 72 (24-1 + 27-1).
Note that in the context of the Internet suite of protocols, values
should be calculated accordingly:

180 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

Layer functionality
1 = physical (for example, repeaters)
2 = datalink/subnetwork (for example, bridges)
3 = internet (for example, IP gateways)
4 = end-to-end (for example, IP hosts)
7 = applications (for example, mail relays)
For systems including OSI protocols, layers 5 and 6 also can be
counted.

Interfaces group
Implementation of the Interfaces group is mandatory for all systems.

ifNumber
OID: 1.3.6.1.2.1.2.1
The number of network interfaces (regardless of their current state)
present on this system.

ifTable
OID: 1.3.6.1.2.1.2.2
A list of interface entries. The number of entries is given by the value
of ifNumber.

ifEntry
OID: 1.3.6.1.2.1.2.2.1
An interface entry containing objects at the subnetwork layer and
below for a particular interface.

Interfaces group 181

MIB-II (RFC 1213)

ifIndex
OID: 1.3.6.1.2.1.2.2.1.1
A unique value for each interface. Its value ranges between 1 and the
value of ifNumber. The value for each interface must remain constant
at least from one re-initialization of the entity's network management
system to the next re- initialization.

ifDescr
OID: 1.3.6.1.2.1.2.2.1.2
A textual string containing information about the interface. This
string should include the name of the manufacturer, the product
name and the version of the hardware interface.

ifType
OID: 1.3.6.1.2.1.2.2.1.3
The type of interface, distinguished according to the physical/link
protocol(s) immediately `below' the network layer in the protocol
stack.

ifMtu
OID: 1.3.6.1.2.1.2.2.1.4
The size of the largest datagram which can be sent/received on the
interface, specified in octets. For interfaces that are used for
transmitting network datagrams, this is the size of the largest
network datagram that can be sent on the interface.

ifSpeed
OID: 1.3.6.1.2.1.2.2.1.5
An estimate of the interface's current bandwidth in bits per second.
For interfaces which do not vary in bandwidth or for those where no
accurate estimation can be made, this object should contain the
nominal bandwidth.

182 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

ifPhysAddress
OID: 1.3.6.1.2.1.2.2.1.6
The interface's address at the protocol layer immediately `below' the
network layer in the protocol stack. For interfaces which do not have
such an address (e.g., a serial line), this object should contain an octet
string of zero length.

ifAdminStatus
OID: 1.3.6.1.2.1.2.2.1.7
The desired state of the interface. The testing (3) state indicates that
no operational packets can be passed.

ifOperStatus
OID: 1.3.6.1.2.1.2.2.1.8
The current operational state of the interface. The testing (3) state
indicates that no operational packets can be passed.

ifLastChange
OID: 1.3.6.1.2.1.2.2.1.9
The value of sysUpTime at the time the interface entered its current
operational state. If the current state was entered prior to the last
re-initialization of the local network management subsystem, then
this object contains a zero value.

ifInOctets
OID: 1.3.6.1.2.1.2.2.1.10
The total number of octets received on the interface, including
framing characters.

Interfaces group 183

MIB-II (RFC 1213)

ifInUcastPkts
OID: 1.3.6.1.2.1.2.2.1.11
The number of subnetwork-unicast packets delivered to a
higher-layer protocol.

ifInNUcastPkts
OID: 1.3.6.1.2.1.2.2.1.12
The number of nonunicast packets (for example,
subnetwork-broadcast or subnetwork-multicast) delivered to a
higher-layer protocol.

ifInDiscards
OID: 1.3.6.1.2.1.2.2.1.13
The number of inbound packets which were chosen to be discarded
even though no errors had been detected to prevent their being
deliverable to a higher-layer protocol. One possible reason for
discarding such a packet could be to free up buffer space.

ifInErrors
OID: 1.3.6.1.2.1.2.2.1.14
The number of inbound packets that contained errors preventing
them from being deliverable to a higher-layer protocol.

ifInUnknownProtos
OID: 1.3.6.1.2.1.2.2.1.15
The number of packets received via the interface which were
discarded because of an unknown or unsupported protocol.

184 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

ifOutOctets
OID: 1.3.6.1.2.1.2.2.1.16
The total number of octets transmitted out of the interface, including
framing characters.

ifOutUcastPkts
OID: 1.3.6.1.2.1.2.2.1.17
The total number of packets that were requested, by higher-level
protocols, to be transmitted to a subnetwork-unicast address,
including those that were discarded or not sent.

ifOutNUcastPkts
OID: 1.3.6.1.2.1.2.2.1.18
he total number of packets that higher-level protocols requested be
transmitted to a non- unicast (i.e., a subnetwork-broadcast or
subnetwork-multicast) address, including those that were discarded
or not sent.

ifOutDiscards
OID: 1.3.6.1.2.1.2.2.1.19
The number of outbound packets which were chosen to be discarded
even though no errors had been detected to prevent their being
transmitted. One possible reason for discarding such a packet could
be to free up buffer space.

ifOutErrors
OID: 1.3.6.1.2.1.2.2.1.20
The number of outbound packets that could not be transmitted
because of errors.

Interfaces group 185

MIB-II (RFC 1213)

ifOutQLen
OID: 1.3.6.1.2.1.2.2.1.21
The length of the output packet queue (in packets).

ifSpecific
OID: 1.3.6.1.2.1.2.2.1.22
A reference to MIB definitions specific to the particular media being
used to realize the interface. For example, if the interface is realized
by an ethernet, then the value of this object refers to a document
defining objects specific to ethernet. If this information is not present,
its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a
syntatically valid object identifier, and any conformant
implementation of ASN.1 and BER must be able to generate and
recognize this value.

AT Group
Implementation of the Address Translation group is mandatory for
all systems. Note, however, that this group is deprecated by MIB-II.
From MIB-II onward, each network protocol group contains its own
address translation tables.

atTable
OID: 1.3.6.1.2.1.3.1
The Address Translation tables contain the NetworkAddress to
`physical' address equivalences. Some interfaces do not use
translation tables for determining address equivalences (e.g.,
DDN-X.25 has an algorithmic method); if all interfaces are of this
type, then the Address Translation table is empty, i.e., has zero
entries.

atEntry
OID: 1.3.6.1.2.1.3.1.1
Each entry contains one network address to physical address
equivalence.

186 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

atIfIndex
OID: 1.3.6.1.2.1.3.1.1.1
The interface on which this entry's equivalence is effective. The
interface identified by a particular value of this index is the same
interface as identified by the same value of ifIndex.

atPhysAddress
OID: 1.3.6.1.2.1.3.1.1.2
The media-dependent `physical' address. Setting this object to a null
string (one of zero length) has the effect of invaliding the
corresponding entry in the atTable object. That is, it effectively
dissasociates the interface identified with said entry from the
mapping identified with said entry. It is an implementation-specific
matter as to whether the agent removes an invalidated entry from the
table. Accordingly, management stations must be prepared to receive
tabular information from agents that corresponds to entries not
currently in use. Proper interpretation of such entries requires
examination of the relevant atPhysAddress object.

atNetAddress
OID: 1.3.6.1.2.1.3.1.1.3
The NetworkAddress (e.g., the IP address) corresponding to the
media-dependent `physical' address.

IP group
Implementation of the IP group is mandatory for all systems.

ipForwarding
OID: 1.3.6.1.2.1.4.1
The indication of whether this entity is acting as an IP gateway in
respect to the forwarding of datagrams received by, but not
addressed to, this entity. IP gateways forward datagrams. IP hosts do
not (except those source-routed via the host). Note that for some
managed nodes, this object may take on only a subset of the values

IP group 187
MIB-II (RFC 1213)

possible. Accordingly, it is appropriate for an agent to return a

`badValue' response if a management station attempts to change this
object to an inappropriate value.

ipDefaultTTL
OID: 1.3.6.1.2.1.4.2
The default value inserted into the Time-To-Live field of the IP header
of datagrams originated at this entity, whenever a TTL value is not
supplied by the transport layer protocol.

ipInReceives
OID: 1.3.6.1.2.1.4.3
The total number of input datagrams received from interfaces,
including those received in error.

ipInHdrErrors
OID: 1.3.6.1.2.1.4.4
The number of input datagrams discarded due to errors in their IP
headers, including bad checksums, version number mismatch, other
format errors, time-to-live exceeded, errors discovered in processing
their IP options, etc.

ipInAddrErrors
OID: 1.3.6.1.2.1.4.5
The number of input datagrams discarded because the IP address in
their IP header's destination field was not a valid address to be
received at this entity. This count includes invalid addresses (e.g.,
0.0.0.0) and addresses of unsupported Classes (e.g., Class E). For
entities which are not IP Gateways and therefore do not forward
datagrams, this counter includes datagrams discarded because the
destination address was not a local address.

188 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

ipForwDatagrams
OID: 1.3.6.1.2.1.4.6
The number of input datagrams for which this entity was not their
final IP destination, as a result of which an attempt was made to find
a route to forward them to that final destination. In entities which do
not act as IP Gateways, this counter will include only those packets
which were Source-Routed via this entity, and the Source- Route
option processing was successful.

ipInUnknownProtos
OID: 1.3.6.1.2.1.4.7
The number of locally-addressed datagrams received successfully but
discarded because of an unknown or unsupported protocol.

ipInDiscards
OID: 1.3.6.1.2.1.4.8
The number of input IP datagrams for which no problems were
encountered to prevent their continued processing, but which were
discarded (e.g., for lack of buffer space). Note that this counter does
not include any datagrams discarded while awaiting re-assembly.

ipInDelivers
OID: 1.3.6.1.2.1.4.9
The total number of input datagrams successfully delivered to IP
user-protocols (including ICMP).

ipOutRequests
OID: 1.3.6.1.2.1.4.10
The total number of IP datagrams which local IP user-protocols
(including ICMP) supplied to IP in requests for transmission. Note
that this counter does not include any datagrams counted in
ipForwDatagrams.

IP group 189
MIB-II (RFC 1213)

ipOutDiscards
OID: 1.3.6.1.2.1.4.11
The number of output IP datagrams for which no problem was
encountered to prevent their transmission to their destination, but
which were discarded (e.g., for lack of buffer space). Note that this
counter would include datagrams counted in ipForwDatagrams if
any such packets met this (discretionary) discard criterion.

ipOutNoRoutes
OID: 1.3.6.1.2.1.4.12
The number of IP datagrams discarded because no route could be
found to transmit them to their destination. Note that this counter
includes any packets counted in ipForwDatagrams which meet this
`no-route' criterion. Note that this includes any datagarms which a
host cannot route because all of its default gateways are down..

ipReasmTimeout
OID: 1.3.6.1.2.1.4.13
The maximum number of seconds which received fragments are held
while they are awaiting reassembly at this entity.

ipReasmReqds
OID: 1.3.6.1.2.1.4.14
The number of IP fragments received which needed to be
reassembled at this entity.

ipReasmOKs
OID: 1.3.6.1.2.1.4.15
The number of IP datagrams successfully re- assembled.

190 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

ipReasmFails
OID: 1.3.6.1.2.1.4.16
The number of failures detected by the IP re- assembly algorithm (for
whatever reason: timed out, errors, etc). Note that this is not
necessarily a count of discarded IP fragments since some algorithms
(notably the algorithm in RFC 815) can lose track of the number of
fragments by combining them as they are received.

ipFragOKs
OID: 1.3.6.1.2.1.4.17
The number of IP datagrams that have been successfully fragmented
at this entity.

ipFragFails
OID: 1.3.6.1.2.1.4.18
The number of IP datagrams that have been discarded because they
needed to be fragmented at this entity but could not be, e.g., because
their Don't Fragment flag was set.

ipFragCreates
OID: 1.3.6.1.2.1.4.19
The number of IP datagram fragments that have been generated as a
result of fragmentation at this entity.

ipAddrTable
OID: 1.3.6.1.2.1.4.20
The table of addressing information relevant to this entity's IP
addresses.

IP group 191
MIB-II (RFC 1213)

ipAddrEntry
OID: 1.3.6.1.2.1.4.20.1
The addressing information for one of this entity's IP addresses.

ipAdEntAddr
OID: 1.3.6.1.2.1.4.20.1.1
The IP address to which this entry's addressing information pertains.

ipAdEntIfIndex
OID: 1.3.6.1.2.1.4.20.1.2
The index value which uniquely identifies the interface to which this
entry is applicable. The interface identified by a particular value of
this index is the same interface as identified by the same value of
ifIndex.

ipAdEntNetMask
OID: 1.3.6.1.2.1.4.20.1.3
The subnet mask associated with the IP address of this entry. The
value of the mask is an IP address with all the network bits set to 1
and all the hosts bits set to 0.

ipAdEntBcastAddr
OID: 1.3.6.1.2.1.4.20.1.4
The value of the least-significant bit in the IP broadcast address used
for sending datagrams on the (logical) interface associated with the IP
address of this entry. For example, when the Internet standard
all-ones broadcast address is used, the value will be 1. This value
applies to both the subnet and network broadcasts addresses used by
the entity on this (logical) interface.

192 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

ipAdEntReasmMaxSize
OID: 1.3.6.1.2.1.4.20.1.5
The size of the largest IP datagram which this entity can re-assemble
from incoming IP fragmented datagrams received on this interface.

ipRouteTable
OID: 1.3.6.1.2.1.4.21
This entity's IP Routing table.

ipRouteEntry
OID: 1.3.6.1.2.1.4.21.1
A route to a particular destination.

ipRouteDest
OID: 1.3.6.1.2.1.4.21.1.1
The destination IP address of this route. An entry with a value of
0.0.0.0 is considered a default route. Multiple routes to a single
destination can appear in the table, but access to such multiple entries
is dependent on the table- access mechanisms defined by the network
management protocol in use.

ipRouteIfIndex
OID: 1.3.6.1.2.1.4.21.1.2
The index value which uniquely identifies the local interface through
which the next hop of this route should be reached. The interface
identified by a particular value of this index is the same interface as
identified by the same value of ifIndex.

IP group 193
MIB-II (RFC 1213)

ipRouteMetric1
OID: 1.3.6.1.2.1.4.21.1.3
The primary routing metric for this route. The semantics of this
metric are determined by the routing-protocol specified in the route's
ipRouteProto value. If this metric is not used, its value should be set
to -1.

ipRouteMetric2
OID: 1.3.6.1.2.1.4.21.1.4
An alternate routing metric for this route. The semantics of this
metric are determined by the routing-protocol specified in the route's
ipRouteProto value. If this metric is not used, its value should be set
to -1.

ipRouteMetric3
OID: 1.3.6.1.2.1.4.21.1.5
An alternate routing metric for this route. The semantics of this
metric are determined by the routing-protocol specified in the route's
ipRouteProto value. If this metric is not used, its value should be set
to -1.

ipRouteMetric4
OID: 1.3.6.1.2.1.4.21.1.6
An alternate routing metric for this route. The semantics of this
metric are determined by the routing-protocol specified in the route's
ipRouteProto value. If this metric is not used, its value should be set
to -1.

ipRouteNextHop
OID: 1.3.6.1.2.1.4.21.1.7
The IP address of the next hop of this route. (In the case of a route
bound to an interface which is realized via a broadcast media, the
value of this field is the agent's IP address on that interface.)

194 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

ipRouteType
OID: 1.3.6.1.2.1.4.21.1.8
The type of route. Note that the values direct(3) and indirect(4) refer
to the notion of direct and indirect routing in the IP architecture.
Setting this object to the value invalid(2) has the effect of invalidating
the corresponding entry in the ipRouteTable object. That is, it
effectively dissasociates the destination identified with said entry
from the route identified with said entry. It is an
implementation-specific matter as to whether the agent removes an
invalidated entry from the table. Accordingly, management stations
must be prepared to receive tabular information from agents that
corresponds to entries not currently in use. Proper interpretation of
such entries requires examination of the relevant ipRouteType object.

ipRouteProto
OID: 1.3.6.1.2.1.4.21.1.9
The routing mechanism via which this route was learned. Inclusion
of values for gateway routing protocols is not intended to imply that
hosts should support those protocols.

ipRouteAge
OID: 1.3.6.1.2.1.4.21.1.10
The number of seconds since this route was last updated or otherwise
determined to be correct. Note that no semantics of `too old' can be
implied except through knowledge of the routing protocol by which
the route was learned.

ipRouteMask
OID: 1.3.6.1.2.1.4.21.1.11
The mask to be logical-ANDed with the destination address before
being compared to the value in the ipRouteDest field. For those
systems that do not support arbitrary subnet masks, an agent
constructs the value of the ipRouteMask by determining whether the

IP group 195
MIB-II (RFC 1213)

value of the correspondent ipRouteDest field belong to a class-A, B,

or C network, and then using one of the following:
mask network
255.0.0.0 class-A
255.255.0.0 class-B
255.255.255.0 class-C

If the value of the ipRouteDest is 0.0.0.0 (a default route), then the

mask value is also 0.0.0.0. It should be noted that all IP routing
subsystems implicitly use this mechanism.

ipRouteMetric5
OID: 1.3.6.1.2.1.4.21.1.12
An alternate routing metric for this route. The semantics of this
metric are determined by the routing-protocol specified in the route's
ipRouteProto value. If this metric is not used, its value should be set
to -1.

ipRouteInfo
OID: 1.3.6.1.2.1.4.21.1.13
A reference to MIB definitions specific to the particular routing
protocol which is responsible for this route, as determined by the
value specified in the route's ipRouteProto value. If this information
is not present, its value should be set to the OBJECT IDENTIFIER { 0 0
}, which is a syntatically valid object identifier, and any conformant
implementation of ASN.1 and BER must be able to generate and
recognize this value.

ipNetToMediaTable
OID: 1.3.6.1.2.1.4.22
The IP Address Translation table used for mapping from IP addresses
to physical addresses.

196 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

ipNetToMediaEntry
OID: 1.3.6.1.2.1.4.22.1
Each entry contains one IP address to physical address equivalence.

ipNetToMediaIfIndex
OID: 1.3.6.1.2.1.4.22.1.1
The interface on which this entry's equivalence is effective. The
interface identified by a particular value of this index is the same
interface as identified by the same value of ifIndex.

ipNetToMediaPhysAddress
OID: 1.3.6.1.2.1.4.22.1.2
The media-dependent physical address.

ipNetToMediaNetAddress
OID: 1.3.6.1.2.1.4.22.1.3
The IpAddress corresponding to the media-dependent physical
address.

ipNetToMediaType
OID: 1.3.6.1.2.1.4.22.1.4
The type of mapping.
Setting this object to the value invalid(2) has the effect of invalidating
the corresponding entry in the ipNetToMediaTable. That is, it
effectively dissasociates the interface identified with said entry from
the mapping identified with said entry. It is an
implementation-specific matter as to whether the agent removes an
invalidated entry from the table. Accordingly, management stations
must be prepared to receive tabular information from agents that
corresponds to entries not currently in use. Proper interpretation of
such entries requires examination of the relevant ipNetToMediaType
object.

IP group 197
MIB-II (RFC 1213)

ipRoutingDiscards
OID: 1.3.6.1.2.1.4.23
The number of routing entries which were chosen to be discarded
even though they are valid. One possible reason for discarding such
an entry could be to free-up buffer space for other routing entries.

ICMP group
Implementation of the ICMP group is mandatory for all systems.

icmpInMsgs
OID: 1.3.6.1.2.1.5.1
The total number of ICMP messages which the entity received. Note
that this counter includes all those counted by icmpInErrors.

icmpInErrors
OID: 1.3.6.1.2.1.5.2
The number of ICMP messages which the entity received but
determined as having ICMP-specific errors (bad ICMP checksums,
bad length, etc.).

icmpInDestUnreachs
OID: 1.3.6.1.2.1.5.3
The number of ICMP Destination Unreachable messages received.

icmpInTimeExcds
OID: 1.3.6.1.2.1.5.4
The number of ICMP Time Exceeded messages received.

198 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

icmpInParmProbs
OID: 1.3.6.1.2.1.5.5
The number of ICMP Parameter Problem messages received.

icmpInSrcQuenchs
OID: 1.3.6.1.2.1.5.6
The number of ICMP Source Quench messages received.

icmpInRedirects
OID: 1.3.6.1.2.1.5.7
The number of ICMP Redirect messages received.

icmpInEchos
OID: 1.3.6.1.2.1.5.8
The number of ICMP Echo (request) messages received.

icmpInEchoReps
OID: 1.3.6.1.2.1.5.9
The number of ICMP Echo Reply messages received.

icmpInTimestamps
OID: 1.3.6.1.2.1.5.10
The number of ICMP Timestamp (request) messages received.

icmpInTimestampReps
OID: 1.3.6.1.2.1.5.11
The number of ICMP Timestamp Reply messages received.

ICMP group 199

MIB-II (RFC 1213)

icmpInAddrMasks
OID: 1.3.6.1.2.1.5.12
The number of ICMP Address Mask Request messages received.

icmpInAddrMaskReps
OID: 1.3.6.1.2.1.5.13
The number of ICMP Address Mask Reply messages received.

icmpOutMsgs
OID: 1.3.6.1.2.1.5.14
The total number of ICMP messages which this entity attempted to
send. Note that this counter includes all those counted by
icmpOutErrors.

icmpOutErrors
OID: 1.3.6.1.2.1.5.15
The number of ICMP messages that this entity did not send due to
problems discovered within ICMP such as a lack of buffers. This
value should not include errors discovered outside the ICMP layer
such as the inability of IP to route the resultant datagram. In some
implementations there might be no types of error that contribute to
this counter's value.

icmpOutDestUnreachs
OID: 1.3.6.1.2.1.5.16
The number of ICMP Destination Unreachable messages sent.

icmpOutTimeExcds
OID: 1.3.6.1.2.1.5.17
The number of ICMP Time Exceeded messages sent.

200 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

icmpOutParmProbs
OID: 1.3.6.1.2.1.5.18
The number of ICMP Parameter Problem messages sent.

icmpOutSrcQuenchs
OID: 1.3.6.1.2.1.5.19
The number of ICMP Source Quench messages sent.

icmpOutRedirects
OID: 1.3.6.1.2.1.5.20
The number of ICMP Redirect messages sent. For a host, this object is
always zero, since hosts do not send redirects.

icmpOutEchos
OID: 1.3.6.1.2.1.5.21
The number of ICMP Echo (request) messages sent.

icmpOutEchoReps
OID: 1.3.6.1.2.1.5.22
The number of ICMP Echo Reply messages sent.

icmpOutTimestamps
OID: 1.3.6.1.2.1.5.23
The number of ICMP Timestamp (request) messages sent.

icmpOutTimestampReps
OID: 1.3.6.1.2.1.5.24
The number of ICMP Timestamp Reply messages sent.

ICMP group 201

MIB-II (RFC 1213)

icmpOutAddrMasks
OID: 1.3.6.1.2.1.5.25
The number of ICMP Address Mask Request messages sent.

icmpOutAddrMaskReps
OID: 1.3.6.1.2.1.5.26
The number of ICMP Address Mask Reply messages sent.

TCP group
Implementation of the TCP group is mandatory for all systems that
implement the TCP.
Instances of object types that represent information about a particular
TCP connection are transient; they persist only as long as the
connection in question.

tcpRtoAlgorithm
OID: 1.3.6.1.2.1.6.1
The algorithm used to determine the time-out value used for
retransmitting unacknowledged octets.

tcpRtoMin
OID: 1.3.6.1.2.1.6.2
The minimum value permitted by a TCP implementation for the
retransmission time-out, measured in milliseconds. More refined
semantics for objects of this type depend upon the algorithm used to
determine the retransmission time-out. In particular, when the
time-out algorithm is 3 (rsre), an object of this type has the semantics
of the LBOUND quantity described in RFC 793.

202 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

tcpRtoMax
OID: 1.3.6.1.2.1.6.3
The maximum value permitted by a TCP implementation for the
retransmission time-out, measured in milliseconds. More refined
semantics for objects of this type depend upon the algorithm used to
determine the retransmission time-out. In particular, when the
time-out algorithm is 3 (rsre), an object of this type has the semantics
of the UBOUND quantity described in RFC 793.

tcpMaxConn
OID: 1.3.6.1.2.1.6.4
The limit on the total number of TCP connections the entity can
support. In entities where the maximum number of connections is
dynamic, this object should contain the value -1.

tcpActiveOpens
OID: 1.3.6.1.2.1.6.5
The number of times TCP connections have made a direct transition
to the SYN-SENT state from the CLOSED state.

tcpPassiveOpens
OID: 1.3.6.1.2.1.6.6
The number of times TCP connections have made a direct transition
to the SYN-RCVD state from the LISTEN state.

tcpAttemptFails
OID: 1.3.6.1.2.1.6.7
The number of times TCP connections have made a direct transition
to the CLOSED state from either the SYN-SENT state or the
SYN-RCVD state, plus the number of times TCP connections have
made a direct transition to the LISTEN state from the SYN-RCVD
state.

TCP group 203

MIB-II (RFC 1213)

tcpEstabResets
OID: 1.3.6.1.2.1.6.8
The number of times TCP connections have made a direct transition
to the CLOSED state from either the ESTABLISHED state or the
CLOSE-WAIT state.

tcpCurrEstab
OID: 1.3.6.1.2.1.6.9
The number of TCP connections for which the current state is either
ESTABLISHED or CLOSE-WAIT.

tcpInSegs
OID: 1.3.6.1.2.1.6.10
The total number of segments received, including those received in
error. This count includes segments received on currently established
connections.

tcpOutSegs
OID: 1.3.6.1.2.1.6.11
The total number of segments sent, including those on current
connections but excluding those containing only retransmitted octets.

tcpRetransSegs
1.3.6.1.2.1.6.12
The total number of segments retransmitted; that is, the number of
TCP segments transmitted containing one or more previously
transmitted octets.

TCP Connection Table

The TCP connection table contains information about this entity's
existing TCP connections.

204 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

tcpConnTable
OID: 1.3.6.1.2.1.6.13
A table containing TCP connection-specific information.

tcpConnEntry
OID: 1.3.6.1.2.1.6.13.1
Information about a particular current TCP connection. An object of
this type is transient, in that it ceases to exist when (or soon after) the
connection makes the transition to the CLOSED state.

tcpConnState
OID: 1.3.6.1.2.1.6.13.1.1
The state of this TCP connection.
The only value that might be set by a management station is
deleteTCB (12). Accordingly, it is appropriate for an agent to return a
badValue response if a management station attempts to set this object
to any other value.
If a management station sets this object to the value delete12 (TCB),
then this has the effect of deleting the TCB (as defined in RFC 793) of
the corresponding connection on the managed node, resulting in
immediate termination of the connection.
As an implementation-specific option, a RST segment might be sent
from the managed node to the other TCP endpoint (note, however,
that RST segments are not sent reliably).

tcpConnLocalAddress
OID: 1.3.6.1.2.1.6.13.1.2
The local IP address for this TCP connection. In the case of a
connection in the listen state that is willing to accept connections for
any IP interface associated with the node, the value 0.0.0.0 is used.

TCP group 205

MIB-II (RFC 1213)

tcpConnLocalPort
OID: 1.3.6.1.2.1.6.13.1.3
The local port number for this TCP connection.

tcpConnRemAddress
OID: 1.3.6.1.2.1.6.13.1.4
The remote IP address for this TCP connection.

tcpConnRemPort
OID: 1.3.6.1.2.1.6.13.1.5
The remote port number for this TCP connection.

tcpInErrs
OID: 1.3.6.1.2.1.6.14
The total number of segments received in error (for example, bad
TCP checksums).

tcpOutRsts
OID: 1.3.6.1.2.1.6.15
The number of TCP segments sent containing the RST flag.

UDP group
Implementation of the UDP group is mandatory for all systems that
implement the UDP.

udpInDatagrams
OID: 1.3.6.1.2.1.7.1
The total number of UDP datagrams delivered to UDP users.

206 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

udpNoPorts
OID: 1.3.6.1.2.1.7.2
The total number of received UDP datagrams for which there was no
application at the destination port.

udpInErrors
OID: 1.3.6.1.2.1.7.3
The number of received UDP datagrams that could not be delivered
for reasons other than the lack of an application at the destination
port.

udpOutDatagrams
OID: 1.3.6.1.2.1.7.4
The total number of UDP datagrams sent from this entity.

udpTable
OID: 1.3.6.1.2.1.7.5
A table containing UDP listener information.

udpEntry
OID: 1.3.6.1.2.1.7.5.1
Information about a particular current UDP listener.

udpLocalAddress
OID: 1.3.6.1.2.1.7.5.1.1
The local IP address for this UDP listener. In the case of a UDP
listener that is willing to accept datagrams for any IP interface
associated with the node, the value 0.0.0.0 is used.

UDP group 207

MIB-II (RFC 1213)

udpLocalPort
OID: 1.3.6.1.2.1.7.5.1.2
The local port number for this UDP listener.

EGP group
Implementation of the EGP group is mandatory for all systems which
implement the EGP.

egpInMsgs
OID: 1.3.6.1.2.1.8.1
The number of EGP messages received without error.

egpInErrors
OID: 1.3.6.1.2.1.8.2
The number of EGP messages received that proved to be in error.

egpOutMsgs
OID: 1.3.6.1.2.1.8.3
The total number of locally generated EGP messages.

egpOutErrors
OID: 1.3.6.1.2.1.8.4
The number of locally generated EGP messages not sent due to
resource limitations within an EGP entity.

egpNeighTable
OID: 1.3.6.1.2.1.8.5
The EGP neighbor table.

208 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

egpNeighEntry
OID: 1.3.6.1.2.1.8.5.1
Information about this entity's relationship with a particular EGP
neighbor.

egpNeighState
OID: 1.3.6.1.2.1.8.5.1.1
The EGP state of the local system with respect to this entry's EGP
neighbor. Each EGP state is represented by a value that is one greater
than the numerical value associated with said state in RFC 904.

egpNeighAddr
OID: 1.3.6.1.2.1.8.5.1.2
The IP address of this entry's EGP neighbor.

egpNeighAs
OID: 1.3.6.1.2.1.8.5.1.3
The autonomous system of this EGP peer. Zero should be specified if
the autonomous system number of the neighbor is not yet known.

egpNeighInMsgs
OID: 1.3.6.1.2.1.8.5.1.4
The number of EGP messages received without error from this EGP
peer.

egpNeighInErrs
OID: 1.3.6.1.2.1.8.5.1.5
The number of EGP messages received from this EGP peer that
proved to be in error (e.g., bad EGP checksum).

egpNeighOutMsgs
OID: 1.3.6.1.2.1.8.5.1.6
The number of locally generated EGP messages to this EGP peer.

egpNeighOutErrs
OID: 1.3.6.1.2.1.8.5.1.7
The number of locally generated EGP messages not sent to this EGP
peer due to resource limitations within an EGP entity.

EGP group 209

MIB-II (RFC 1213)

egpNeighInErrMsgs
OID: 1.3.6.1.2.1.8.5.1.8
The number of EGP-defined error messages received from this EGP
peer.

egpNeighOutErrMsgs
OID: 1.3.6.1.2.1.8.5.1.9
The number of EGP-defined error messages sent to this EGP peer.

egpNeighStateUps
OID: 1.3.6.1.2.1.8.5.1.10
The number of EGP state transitions to the UP state with this EGP
peer.

egpNeighStateDowns
OID: 1.3.6.1.2.1.8.5.1.11
The number of EGP state transitions from the UP state to any other
state with this EGP peer.

egpNeighIntervalHello
OID: 1.3.6.1.2.1.8.5.1.12
The interval between EGP Hello command retransmissions (in
hundredths of a second). This represents the t1 timer as defined in
RFC 904.

egpNeighIntervalPoll
OID: 1.3.6.1.2.1.8.5.1.13
The interval between EGP poll command retransmissions (in
hundredths of a second). This represents the t3 timer as defined in
RFC 904.

egpNeighMode
OID: 1.3.6.1.2.1.8.5.1.14
The polling mode of this EGP entity, either passive or active.

egpNeighEventTrigger
OID: 1.3.6.1.2.1.8.5.1.15
A control variable used to trigger operator- initiated Start and Stop
events. When read, this variable always returns the most recent value
that egpNeighEventTrigger was set to. If it has not been set since the
last initialization of the network management subsystem on the node,
it returns a value of `stop'. When set, this variable causes a Start or

210 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

Stop event on the specified neighbor, as specified on pages 8-10 of

RFC 904. Briefly, a Start event causes an Idle peer to begin neighbor
acquisition and a non-Idle peer to reinitiate neighbor acquisition. A
stop event causes a non-Idle peer to return to the Idle state until a
Start event occurs, either via egpNeighEventTrigger or otherwise.

egpAs
OID: 1.3.6.1.2.1.8.6
The autonomous system number of this EGP entity.

Transmission group
Based on the transmission media underlying each interface on a
system, the corresponding portion of the Transmission group is
mandatory for that system.
When Internet-standard definitions for managing transmission
media are defined, the transmission group is used to provide a prefix
for the names of those objects.
Typically, such definitions reside in the experimental portion of the
MIB until they are "proven", then as a part of the Internet
standardization process, the definitions are accordingly elevated and
a new object identifier, under the transmission group is defined. By
convention, the name assigned is:
type OBJECT IDENTIFIER ::= { transmission number }
where "type" is the symbolic value used for the media in the ifType
column of the ifTable object, and "number" is the actual integer value
corresponding to the symbol.

Transmission group 211

MIB-II (RFC 1213)

SNMP group
Implementation of the SNMP group is mandatory for all systems that
support an SNMP protocol entity. Some of the objects defined next
are zero-valued in those SNMP implementations that are optimized
to support only those functions specific to either a management agent
or a management station. All of the objects that follow refer to an
SNMP entity, and there might be several SNMP entities residing on a
managed node (for example, if the node is acting as a management
station).

snmpInPkts
OID: 1.3.6.1.2.1.11.1
The total number of messages delivered to the SNMP entity from the
transport service.

snmpOutPkts
OID: 1.3.6.1.2.1.11.2
The total number of SNMP messages that were passed from the
SNMP protocol entity to the transport service.

snmpInBadVersions
OID: 1.3.6.1.2.1.11.3
The total number of SNMP messages that were delivered to the
SNMP protocol entity and were for an unsupported SNMP version.

snmpInBadCommunityNames
OID: 1.3.6.1.2.1.11.4
The total number of SNMP messages delivered to the SNMP protocol
entity that used a SNMP community name not known to said entity.

212 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

snmpInBadCommunityUses
OID: 1.3.6.1.2.1.11.5
The total number of SNMP messages delivered to the SNMP protocol
entity that represented an SNMP operation that was not allowed by
the SNMP community named in the message.

snmpInASNParseErrs
OID: 1.3.6.1.2.1.11.6
The total number of ASN.1 or BER errors encountered by the SNMP
protocol entity when decoding received SNMP messages.

snmpInTooBigs
OID: 1.3.6.1.2.1.11.8
The total number of SNMP PDUs that were delivered to the SNMP
protocol entity and for which the value of the error-status field is
“tooBig.”

snmpInNoSuchNames
OID: 1.3.6.1.2.1.11.9
The total number of SNMP PDUs that were delivered to the SNMP
protocol entity and for which the value of the error-status field is
“noSuchName.”

snmpInBadValues
OID: 1.3.6.1.2.1.11.10
The total number of SNMP PDUs that were delivered to the SNMP
protocol entity and for which the value of the error-status field is
“badValue.”

SNMP group 213

MIB-II (RFC 1213)

snmpInReadOnlys
OID: 1.3.6.1.2.1.11.11
The total number valid SNMP PDUs that were delivered to the
SNMP protocol entity and for which the value of the error-status field
is “readOnly.”
It is a protocol error to generate an SNMP PDU that contains the
value “readOnly” in the error-status field; as such, this object is
provided as a means of detecting incorrect implementations of the
SNMP.

snmpInGenErrs
OID: 1.3.6.1.2.1.11.12
The total number of SNMP PDUs that were delivered to the SNMP
protocol entity and for which the value of the error-status field is
“genErr.”

snmpInTotalReqVars
OID: 1.3.6.1.2.1.11.13
The total number of MIB objects that have been retrieved successfully
by the SNMP protocol entity as the result of receiving valid SNMP
Get-Request and Get-Next PDUs.

snmpInTotalSetVars
OID: 1.3.6.1.2.1.11.14
The total number of MIB objects that have been altered successfully
by the SNMP protocol entity as the result of receiving valid SNMP
Set-Request PDUs.

snmpInGetRequests
OID: 1.3.6.1.2.1.11.15
The total number of SNMP Get-Request PDUs that have been
accepted and processed by the SNMP protocol entity.

214 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

snmpInGetNexts
OID: 1.3.6.1.2.1.11.16
The total number of SNMP Get-Next PDUs that have been accepted
and processed by the SNMP protocol entity.

snmpInSetRequests
OID: 1.3.6.1.2.1.11.17
The total number of SNMP Set-Request PDUs that have been
accepted and processed by the SNMP protocol entity.

snmpInGetResponses
OID: 1.3.6.1.2.1.11.18
The total number of SNMP Get-Response PDUs that have been
accepted and processed by the SNMP protocol entity.

snmpInTraps
OID: 1.3.6.1.2.1.11.19
The total number of SNMP Trap PDUs that have been accepted and
processed by the SNMP protocol entity.

snmpOutTooBigs
OID: 1.3.6.1.2.1.11.20
The total number of SNMP PDUs that were generated by the SNMP
protocol entity and for which the value of the error-status field is
“tooBig.”

snmpOutNoSuchNames
OID: 1.3.6.1.2.1.11.21
The total number of SNMP PDUs that were generated by the SNMP
protocol entity and for which the value of the error-status field is
“noSuchName.”

SNMP group 215

MIB-II (RFC 1213)

snmpOutBadValues
OID: 1.3.6.1.2.1.11.22
The total number of SNMP PDUs that were generated by the SNMP
protocol entity and for which the value of the error-status field is
“badValue.”

snmpOutGenErrs
OID: 1.3.6.1.2.1.11.24
The total number of SNMP PDUs that were generated by the SNMP
protocol entity and for which the value of the error-status field is
“genErr.”

snmpOutGetRequests
OID: 1.3.6.1.2.1.11.25
The total number of SNMP Get-Request PDUs that have been
generated by the SNMP protocol entity.

snmpOutGetNexts
OID: 1.3.6.1.2.1.11.26
The total number of SNMP Get-Next PDUs that have been generated
by the SNMP protocol entity.

snmpOutSetRequests
OID: 1.3.6.1.2.1.11.27
The total number of SNMP Set-Request PDUs that have been
generated by the SNMP protocol entity.

snmpOutGetResponses
OID: 1.3.6.1.2.1.11.28
The total number of SNMP Get-Response PDUs that have been
generated by the SNMP protocol entity.

216 EMC Atmos Version 1.4.0 Administrator’s Guide

 MIB-II (RFC 1213)

snmpOutTraps
OID: 1.3.6.1.2.1.11.29
The total number of SNMP Trap PDUs that have been generated by
the SNMP protocol entity.

snmpEnableAuthenTraps
OID: 1.3.6.1.2.1.11.30
Indicates whether the SNMP agent process is permitted to generate
authentication-failure traps. The value of this object overrides any
configuration information; as such, it provides a means whereby all
authentication-failure traps may be disabled.
Note that it is strongly recommended that this object be stored in
non-volatile memory so that it remains constant between
re-initializations of the network management system.

SNMP group 217

MIB-II (RFC 1213)

218 EMC Atmos Version 1.4.0 Administrator’s Guide

 C
Host Resources MIB
(RFC 2790)

This appendix provides descriptions and other information specific

to the Host Resources MIB, and includes the following sections:
◆ Host Resources System Group....................................................... 220
◆ Host Resources Storage Group ...................................................... 221
◆ Host Resources Device Group ....................................................... 225
◆ Host Resources Running Software Group ................................... 238
◆ Host Resources Running Software Performance Group............ 240
◆ Host Resources Installed Software Group ................................... 241
◆ Conformance information .............................................................. 243

Host Resources MIB (RFC 2790) 219

Host Resources MIB (RFC 2790)

Host Resources System Group

hrSystemUptime
OID: 1.3.6.1.2.1.25.1.1
The amount of time since this host was last initialized. Note that this
is different from sysUpTime in the SNMPv2-MIB [RFC1907] because
sysUpTime is the uptime of the network management portion of the
system.

hrSystemDate
OID: 1.3.6.1.2.1.25.1.2
The host's notion of the local date and time of day.

hrSystemInitialLoadDevice
OID: 1.3.6.1.2.1.25.1.3
The index of the hrDeviceEntry for the device from which this host is
configured to load its initial operating system configuration (i.e.,
which operating system code and/or boot parameters).
Note that writing to this object just changes the configuration that
will be used the next time the operating system is loaded and does
not actually cause the reload to occur.

hrSystemInitialLoadParameters
OID: 1.3.6.1.2.1.25.1.4
This object contains the parameters (e.g. a pathname and parameter)
supplied to the load device when requesting the initial operating
system configuration from that device.
Note that writing to this object just changes the configuration that
will be used the next time the operating system is loaded and does
not actually cause the reload to occur.

220 EMC Atmos Version 1.4.0 Administrator’s Guide

 Host Resources MIB (RFC 2790)

hrSystemNumUsers
OID: 1.3.6.1.2.1.25.1.5
The number of user sessions for which this host is storing state
information. A session is a collection of processes requiring a single
act of user authentication and possibly subject to collective job
control.

hrSystemProcesses
OID: 1.3.6.1.2.1.25.1.6
The number of process contexts currently loaded or running on this
system.

hrSystemMaxProcesses
OID: 1.3.6.1.2.1.25.1.7
The maximum number of process contexts this system can support.
If there is no fixed maximum, the value should be zero. On systems
that have a fixed maximum, this object can help diagnose failures that
occur when this maximum is reached.

Host Resources Storage Group

Registration point for storage types, for use with hrStorageType.
These are defined in the HOST-RESOURCES-TYPES module.

hrStorageTypes
OID: 1.3.6.1.2.1.25.2.1
Registrations for some storage types, for use with hrStorageType.

hrStorageOther
OID: 1.3.6.1.2.1.25.2.1.1
The storage type identifier used when no other defined type is
appropriate.

Host Resources Storage Group 221

Host Resources MIB (RFC 2790)

hrStorageRam
OID: 1.3.6.1.2.1.25.2.1.2
The storage type identifier used for RAM.

hrStorageVirtualMemory
OID: 1.3.6.1.2.1.25.2.1.3
The storage type identifier used for virtual memory, temporary
storage of swapped or paged memory.

hrStorageFixedDisk
OID: 1.3.6.1.2.1.25.2.1.4
The storage type identifier used for non-removable rigid rotating
magnetic storage devices.

hrStorageRemovableDisk
OID: 1.3.6.1.2.1.25.2.1.5
The storage type identifier used for removable rigid rotating
magnetic storage devices.

hrStorageFloppyDisk
OID: 1.3.6.1.2.1.25.2.1.6
The storage type identifier used for non-rigid rotating magnetic
storage devices.

hrStorageCompactDisc
OID: 1.3.6.1.2.1.25.2.1.7
The storage type identifier used for read-only rotating optical storage
devices.

hrStorageRamDisk
OID: 1.3.6.1.2.1.25.2.1.8
The storage type identifier used for a file system that is stored in
RAM.

hrStorageFlashMemory
OID: 1.3.6.1.2.1.25.2.1.9
The storage type identifier used for flash memory.

222 EMC Atmos Version 1.4.0 Administrator’s Guide

 Host Resources MIB (RFC 2790)

hrStorageNetworkDisk
OID: 1.3.6.1.2.1.25.2.1.10
The storage type identifier used for a networked file system.

hrMemorySize
OID: 1.3.6.1.2.1.25.2.2
The amount of physical read-write main memory, typically RAM,
contained by the host.

hrStorageTable
OID: 1.3.6.1.2.1.25.2.3
The (conceptual) table of logical storage areas on the host.
An entry shall be placed in the storage table for each logical area of
storage that is allocated and has fixed resource limits. The amount of
storage represented in an entity is the amount actually usable by the
requesting entity, and excludes loss due to formatting or file system
reference information.
These entries are associated with logical storage areas, as might be
seen by an application, rather than physical storage entities which are
typically seen by an operating system. Storage such as tapes and
floppies without file systems on them are typically not allocated in
chunks by the operating system to requesting applications, and
therefore shouldn't appear in this table. Examples of valid storage for
this table include disk partitions, file systems, ram (for some
architectures this is further segmented into regular memory,
extended memory, and so on), backing store for virtual memory
(`swap space').
This table is intended to be a useful diagnostic for `out of memory'
and `out of buffers' types of failures. In addition, it can be a useful
performance monitoring tool for tracking memory, disk, or buffer
usage.

Host Resources Storage Group 223

Host Resources MIB (RFC 2790)

hrStorageEntry
OID: 1.3.6.1.2.1.25.2.3.1
A (conceptual) entry for one logical storage area on the host. As an
example, an instance of the hrStorageType object might be named
hrStorageType.3.

hrStorageIndex
OID: 1.3.6.1.2.1.25.2.3.1.1
A unique value for each logical storage area contained by the host.

hrStorageType
OID: 1.3.6.1.2.1.25.2.3.1.2
The type of storage represented by this entry.

hrStorageDescr
OID: 1.3.6.1.2.1.25.2.3.1.3
A description of the type and instance of the storage described by this
entry.

hrStorageAllocationUnits
OID: 1.3.6.1.2.1.25.2.3.1.4
The size, in bytes, of the data objects allocated from this pool. If this
entry is monitoring sectors, blocks, buffers, or packets, for example,
this number will commonly be greater than one. Otherwise this
number will typically be one.

hrStorageSize
OID: 1.3.6.1.2.1.25.2.3.1.5
The size of the storage represented by this entry, in units of
hrStorageAllocationUnits. This object is writable to allow remote
configuration of the size of the storage area in those cases where such
an operation makes sense and is possible on the underlying system.
For example, the amount of main memory allocated to a buffer pool
might be modified or the amount of disk space allocated to virtual
memory might be modified.

hrStorageUsed
OID: 1.3.6.1.2.1.25.2.3.1.6
The amount of the storage represented by this entry that is allocated,
in units of hrStorageAllocationUnits.

224 EMC Atmos Version 1.4.0 Administrator’s Guide

 Host Resources MIB (RFC 2790)

hrStorageAllocationFailures
OID: 1.3.6.1.2.1.25.2.3.1.7
The number of requests for storage represented by this entry that
could not be honored due to not enough storage. It should be noted
that as this object has a SYNTAX of Counter32, that it does not have a
defined initial value. However, it is recommended that this object be
initialized to zero, even though management stations must not
depend on such an initialization.

Host Resources Device Group

The device group is useful for identifying and diagnosing the devices
on a system. The hrDeviceTable contains common information for
any type of device. In addition, some devices have device-specific
tables for more detailed information. More such tables may be
defined in the future for other device types.
Registration point for device types, for use with hrDeviceType.
These are defined in the HOST-RESOURCES-TYPES module.

hrDeviceTypes
OID: 1.3.6.1.2.1.25.3.1

hrDeviceOther
OID: 1.3.6.1.2.1.25.3.1.1
The device type identifier used when no other defined type is
appropriate.

hrDeviceUnknown
OID: 1.3.6.1.2.1.25.3.1.2
The device type identifier used when the device type is unknown.

hrDeviceProcessor
OID: 1.3.6.1.2.1.25.3.1.3
The device type identifier used for a CPU.

Host Resources Device Group 225

Host Resources MIB (RFC 2790)

hrDeviceNetwork
OID: 1.3.6.1.2.1.25.3.1.4
The device type identifier used for a network interface.

hrDevicePrinter
OID: 1.3.6.1.2.1.25.3.1.5
The device type identifier used for a printer.

hrDeviceDiskStorage
OID: 1.3.6.1.2.1.25.3.1.6
The device type identifier used for a disk drive.

hrDeviceVideo
OID: 1.3.6.1.2.1.25.3.1.10
The device type identifier used for a video device.

hrDeviceAudio
OID: 1.3.6.1.2.1.25.3.1.11
The device type identifier used for an audio device.

hrDeviceCoprocessor
OID: 1.3.6.1.2.1.25.3.1.12
The device type identifier used for a co-processor.

hrDeviceKeyboard
OID: 1.3.6.1.2.1.25.3.1.13
The device type identifier used for a keyboard device.

hrDeviceModem
OID: 1.3.6.1.2.1.25.3.1.14
The device type identifier used for a modem.

hrDeviceParallelPort
OID: 1.3.6.1.2.1.25.3.1.15
The device type identifier used for a parallel port.

226 EMC Atmos Version 1.4.0 Administrator’s Guide

 Host Resources MIB (RFC 2790)

hrDevicePointing
OID: 1.3.6.1.2.1.25.3.1.16
The device type identifier used for a pointing device (e.g., a mouse).

hrDeviceSerialPort
OID: 1.3.6.1.2.1.25.3.1.17
The device type identifier used for a serial port.

hrDeviceTape
OID: 1.3.6.1.2.1.25.3.1.18
The device type identifier used for a tape storage device.

hrDeviceClock
OID: 1.3.6.1.2.1.25.3.1.19
The device type identifier used for a clock device.

hrDeviceVolatileMemory
OID: 1.3.6.1.2.1.25.3.1.20
The device type identifier used for a volatile memory storage device.

hrDeviceNonVolatileMemory
OID: 1.3.6.1.2.1.25.3.1.21
The device type identifier used for a non-volatile memory storage
device.

hrDeviceTable
OID: 1.3.6.1.2.1.25.3.2
The (conceptual) table of devices contained by the host.

hrDeviceEntry
OID: 1.3.6.1.2.1.25.3.2.1
A (conceptual) entry for one device contained by the host. As an
example, an instance of the hrDeviceType object might be named
hrDeviceType.3.

Host Resources Device Group 227

Host Resources MIB (RFC 2790)

hrDeviceIndex
OID: 1.3.6.1.2.1.25.3.2.1.1
A unique value for each device contained by the host. The value for
each device must remain constant at least from one re-initialization of
the agent to the next re-initialization.

hrDeviceType
OID: 1.3.6.1.2.1.25.3.2.1.2
An indication of the type of device.
If this value is `hrDeviceProcessor { hrDeviceTypes 3 }' then an entry
exists in the hrProcessorTable which corresponds to this device.
If this value is `hrDeviceNetwork { hrDeviceTypes 4 }', then an entry
exists in the hrNetworkTable which corresponds to this device.
If this value is `hrDevicePrinter { hrDeviceTypes 5 }', then an entry
exists in the hrPrinterTable which corresponds to this device.
If this value is `hrDeviceDiskStorage { hrDeviceTypes 6 }', then an
entry exists in the hrDiskStorageTable which corresponds to this
device.

hrDeviceDescr
OID: 1.3.6.1.2.1.25.3.2.1.3
A textual description of this device, including the device's
manufacturer and revision, and optionally, its serial number.

hrDeviceID
OID: 1.3.6.1.2.1.25.3.2.1.4
The product ID for this device.

hrDeviceStatus
OID: 1.3.6.1.2.1.25.3.2.1.5
The current operational state of the device described by this row of
the table. A value unknown(1) indicates that the current state of the
device is unknown. running(2) indicates that the device is up and
running and that no unusual error conditions are known. The
warning(3) state indicates that agent has been informed of an
unusual error condition by the operational software (e.g., a disk
device driver) but that the device is still 'operational'. An example
would be a high number of soft errors on a disk. A value of

228 EMC Atmos Version 1.4.0 Administrator’s Guide

 Host Resources MIB (RFC 2790)

testing(4), indicates that the device is not available for use because it
is in the testing state. The state of down(5) is used only when the
agent has been informed that the device is not available for any use.

hrDeviceErrors
OID: 1.3.6.1.2.1.25.3.2.1.6
The number of errors detected on this device. It should be noted that
as this object has a SYNTAX of Counter32, that it does not have a
defined initial value. However, it is recommended that this object be
initialized to zero, even though management stations must not
depend on such an initialization.

hrProcessorTable
OID: 1.3.6.1.2.1.25.3.3
The (conceptual) table of processors contained by the host.
Note that this table is potentially sparse: a (conceptual) entry exists
only if the correspondent value of the hrDeviceType object is
`hrDeviceProcessor'.

hrProcessorEntry
OID: 1.3.6.1.2.1.25.3.3.1
A (conceptual) entry for one processor contained by the host. The
hrDeviceIndex in the index represents the entry in the hrDeviceTable
that corresponds to the hrProcessorEntry.
As an example of how objects in this table are named, an instance of
the hrProcessorFrwID object might be named hrProcessorFrwID.3.

hrProcessorFrwID
OID: 1.3.6.1.2.1.25.3.3.1.1
The product ID of the firmware associated with the processor.

hrProcessorLoad
OID: 1.3.6.1.2.1.25.3.3.1.2
The average, over the last minute, of the percentage of time that this
processor was not idle. Implementations may approximate this one
minute smoothing period if necessary.

Host Resources Device Group 229

Host Resources MIB (RFC 2790)

hrNetworkTable
OID: 1.3.6.1.2.1.25.3.4
The (conceptual) table of network devices contained by the host.
Note that this table is potentially sparse: a (conceptual) entry exists
only if the correspondent value of the hrDeviceType object is
`hrDeviceNetwork'.

hrNetworkEntry
OID: 1.3.6.1.2.1.25.3.4.1
A (conceptual) entry for one network device contained by the host.
The hrDeviceIndex in the index represents the entry in the
hrDeviceTable that corresponds to the hrNetworkEntry.
As an example of how objects in this table are named, an instance of
the hrNetworkIfIndex object might be named hrNetworkIfIndex.3.

hrNetworkIfIndex
OID: 1.3.6.1.2.1.25.3.4.1.1
The value of ifIndex which corresponds to this network device. If this
device is not represented in the ifTable, then this value shall be zero.

hrPrinterTable
OID: 1.3.6.1.2.1.25.3.5
The (conceptual) table of printers local to the host.
Note that this table is potentially sparse: a (conceptual) entry exists
only if the correspondent value of the hrDeviceType object is
`hrDevicePrinter'.

hrPrinterEntry
OID: 1.3.6.1.2.1.25.3.5.1
A (conceptual) entry for one printer local to the host. The
hrDeviceIndex in the index represents the entry in the hrDeviceTable
that corresponds to the hrPrinterEntry.
As an example of how objects in this table are named, an instance of
the hrPrinterStatus object might be named hrPrinterStatus.3.

230 EMC Atmos Version 1.4.0 Administrator’s Guide

 Host Resources MIB (RFC 2790)

hrPrinterStatus
OID: 1.3.6.1.2.1.25.3.5.1.1
The current status of this printer device.

hrPrinterDetectedErrorState
OID: 1.3.6.1.2.1.25.3.5.1.2
This object represents any error conditions detected by the printer.
The error conditions are encoded as bits in an octet string, with the
following definitions:
Condition Bit #
lowPaper 0
noPaper 1
lowToner 2
noToner 3
doorOpen 4
jammed 5
offline 6
serviceRequested 7
inputTrayMissing 8
outputTrayMissing 9
markerSupplyMissing 10
outputNearFull 11
outputFull 12
inputTrayEmpty 13
overduePreventMaint 14
Bits are numbered starting with the most significant bit of the first
byte being bit 0, the least significant bit of the first byte being bit 7, the
most significant bit of the second byte being bit 8, and so on. A one
bit encodes that the condition was detected, while a zero bit encodes
that the condition was not detected.
This object is useful for alerting an operator to specific warning or
error conditions that may occur, especially those requiring human
intervention.

hrDiskStorageTable
OID: 1.3.6.1.2.1.25.3.6
The (conceptual) table of long-term storage devices contained by the
host. In particular, disk devices accessed remotely over a network are
not included here.

Host Resources Device Group 231

Host Resources MIB (RFC 2790)

Note that this table is potentially sparse: a (conceptual) entry exists

only if the correspondent value of the hrDeviceType object is
`hrDeviceDiskStorage'.

hrDiskStorageEntry
OID: 1.3.6.1.2.1.25.3.6.1
A (conceptual) entry for one long-term storage device contained by
the host. The hrDeviceIndex in the index represents the entry in the
hrDeviceTable that corresponds to the hrDiskStorageEntry. As an
example, an instance of the hrDiskStorageCapacity object might be
named hrDiskStorageCapacity.3.

hrDiskStorageAccess
OID: 1.3.6.1.2.1.25.3.6.1.1
An indication if this long-term storage device is readable and
writable or only readable. This should reflect the media type, any
write-protect mechanism, and any device configuration that affects
the entire device.

hrDiskStorageMedia
OID: 1.3.6.1.2.1.25.3.6.1.2
An indication of the type of media used in this long- term storage
device.

hrDiskStorageRemoveble
OID: 1.3.6.1.2.1.25.3.6.1.3
Denotes whether or not the disk media may be removed from the
drive.

hrDiskStorageCapacity
OID: 1.3.6.1.2.1.25.3.6.1.4
The total size for this long-term storage device. If the media is
removable and is currently removed, this value should be zero.

hrPartitionTable
OID: 1.3.6.1.2.1.25.3.7
The (conceptual) table of partitions for long-term storage devices
contained by the host. In particular, partitions accessed remotely
over a network are not included here.

232 EMC Atmos Version 1.4.0 Administrator’s Guide

 Host Resources MIB (RFC 2790)

hrPartitionEntry
OID: 1.3.6.1.2.1.25.3.7.1
A (conceptual) entry for one partition. The hrDeviceIndex in the
index represents the entry in the hrDeviceTable that corresponds to
the hrPartitionEntry.
As an example of how objects in this table are named, an instance of
the hrPartitionSize object might be named hrPartitionSize.3.1.

hrPartitionIndex
OID: 1.3.6.1.2.1.25.3.7.1.1
A unique value for each partition on this long-term storage device.
The value for each long-term storage device must remain constant at
least from one re- initialization of the agent to the next re-
initialization.

hrPartitionLabel
OID: 1.3.6.1.2.1.25.3.7.1.2
A textual description of this partition.

hrPartitionID
OID: 1.3.6.1.2.1.25.3.7.1.3
A descriptor which uniquely represents this partition to the
responsible operating system. On some systems, this might take on a
binary representation.

hrPartitionSize
OID: 1.3.6.1.2.1.25.3.7.1.4
The size of this partition.

hrPartitionFSIndex
OID: 1.3.6.1.2.1.25.3.7.1.5
The index of the file system mounted on this partition. If no file
system is mounted on this partition, then this value shall be zero.
Note that multiple partitions may point to one file system, denoting
that that file system resides on those partitions. Multiple file systems
may not reside on one partition.

Host Resources Device Group 233

Host Resources MIB (RFC 2790)

hrFSTable
OID: 1.3.6.1.2.1.25.3.8
The (conceptual) table of file systems local to this host or remotely
mounted from a file server. File systems that are in only one user's
environment on a multi-user system will not be included in this table.

hrFSEntry
OID: 1.3.6.1.2.1.25.3.8.1
A (conceptual) entry for one file system local to this host or remotely
mounted from a file server. File systems that are in only one user's
environment on a multi-user system will not be included in this table.
As an example of how objects in this table are named, an instance of
the hrFSMountPoint object might be named hrFSMountPoint.3.

hrFSIndex
OID: 1.3.6.1.2.1.25.3.8.1.1
A unique value for each file system local to this host. The value for
each file system must remain constant at least from one
re-initialization of the agent to the next re-initialization.

hrFSMountPoint
OID: 1.3.6.1.2.1.25.3.8.1.2
The path name of the root of this file system.

hrFSRemoteMountPoint
OID: 1.3.6.1.2.1.25.3.8.1.3
A description of the name and/or address of the server that this file
system is mounted from. This may also include parameters such as
the mount point on the remote file system. If this is not a remote file
system, this string should have a length of zero.

hrFSType
OID: 1.3.6.1.2.1.25.3.8.1.4
The value of this object identifies the type of this file system.

hrFSAccess
OID: 1.3.6.1.2.1.25.3.8.1.5

234 EMC Atmos Version 1.4.0 Administrator’s Guide

 Host Resources MIB (RFC 2790)

An indication if this file system is logically configured by the

operating system to be readable and writable or only readable. This
does not represent any local access-control policy, except one that is
applied to the file system as a whole.

hrFSBootable
OID: 1.3.6.1.2.1.25.3.8.1.6
A flag indicating whether this file system is bootable.

hrFSStorageIndex
OID: 1.3.6.1.2.1.25.3.8.1.7
The index of the hrStorageEntry that represents information about
this file system. If there is no such information available, then this
value shall be zero. The relevant storage entry will be useful in
tracking the percent usage of this file system and diagnosing errors
that may occur when it runs out of space.

hrFSLastFullBackupDate
OID: 1.3.6.1.2.1.25.3.8.1.8
The last date at which this complete file system was copied to another
storage device for backup. This information is useful for ensuring
that backups are being performed regularly.
If this information is not known, then this variable shall have the
value corresponding to January 1, year 0000, 00:00:00.0, which is
encoded as (hex)'00 00 01 01 00 00 00 00'.

hrFSLastPartialBackupDate
OID: 1.3.6.1.2.1.25.3.8.1.9
The last date at which a portion of this file system was copied to
another storage device for backup. This information is useful for
ensuring that backups are being performed regularly.
If this information is not known, then this variable shall have the
value corresponding to January 1, year 0000, 00:00:00.0, which is
encoded as (hex)'00 00 01 01 00 00 00 00'.

hrFSTypes
OID: 1.3.6.1.2.1.25.3.9
Registrations for some popular File System types, for use with
hrFSType.

Host Resources Device Group 235

Host Resources MIB (RFC 2790)

hrFSOther
OID: 1.3.6.1.2.1.25.3.9.1
The file system type identifier used when no other defined type is
appropriate.

hrFSUnknown
OID: 1.3.6.1.2.1.25.3.9.2
The file system type identifier used when the type of file system is
unknown.

hrFSBerkeleyFFS
OID: 1.3.6.1.2.1.25.3.9.3
The file system type identifier used for the Berkeley Fast File System.

hrFSSys5FS
OID: 1.3.6.1.2.1.25.3.9.4
The file system type identifier used for the System V File System.

hrFSFat
OID: 1.3.6.1.2.1.25.3.9.5
The file system type identifier used for DOS's FAT file system.

hrFSHPFS
OID: 1.3.6.1.2.1.25.3.9.6
The file system type identifier used for OS/2's High Performance File
System.

hrFSHFS
OID: 1.3.6.1.2.1.25.3.9.7
The file system type identifier used for the Macintosh Hierarchical
File System.

hrFSMFS
OID: 1.3.6.1.2.1.25.3.9.8
The file system type identifier used for the Macintosh File System.

236 EMC Atmos Version 1.4.0 Administrator’s Guide

 Host Resources MIB (RFC 2790)

hrFSNTFS
OID: 1.3.6.1.2.1.25.3.9.9
The file system type identifier used for the Windows NT File System.

hrFSVNode
OID: 1.3.6.1.2.1.25.3.9.10
The file system type identifier used for the VNode File System.

hrFSJournaled
OID: 1.3.6.1.2.1.25.3.9.11
The file system type identifier used for the Journaled File System.

hrFSiso9660
OID: 1.3.6.1.2.1.25.3.9.12
The file system type identifier used for the ISO 9660 File System for
CD's.

hrFSRockRidge
OID: 1.3.6.1.2.1.25.3.9.13
The file system type identifier used for the RockRidge File System for
CD's.

hrFSNFS
OID: 1.3.6.1.2.1.25.3.9.14
The file system type identifier used for the NFS File System.

hrFSNetware
OID: 1.3.6.1.2.1.25.3.9.15
The file system type identifier used for the Netware File System.

hrFSAFS
OID: 1.3.6.1.2.1.25.3.9.16
The file system type identifier used for the Andrew File System.

hrFSDFS
OID: 1.3.6.1.2.1.25.3.9.17
The file system type identifier used for the OSF DCE Distributed File
System.

Host Resources Device Group 237

Host Resources MIB (RFC 2790)

hrFSAppleshare
OID: 1.3.6.1.2.1.25.3.9.18
The file system type identifier used for the AppleShare File System.

hrFSRFS
OID: 1.3.6.1.2.1.25.3.9.19
The file system type identifier used for the RFS File System.

hrFSDGCFS
OID: 1.3.6.1.2.1.25.3.9.20
The file system type identifier used for the Data General DGCFS.

hrFSBFS
OID: 1.3.6.1.2.1.25.3.9.21
The file system type identifier used for the SVR4 Boot File System.

hrFSFAT32
OID: 1.3.6.1.2.1.25.3.9.22
The file system type identifier used for the Windows FAT32 File
System.

hrFSLinuxExt2
OID: 1.3.6.1.2.1.25.3.9.23
The file system type identifier used for the Linux EXT2 File System.

Host Resources Running Software Group

The hrSWRunTable contains an entry for each distinct piece of
software that is running or loaded into physical or virtual memory in
preparation for running. This includes the host's operating system,
device drivers, and applications.

238 EMC Atmos Version 1.4.0 Administrator’s Guide

 Host Resources MIB (RFC 2790)

hrSWOSIndex
OID: 1.3.6.1.2.1.25.4.1
The value of the hrSWRunIndex for the hrSWRunEntry that
represents the primary operating system running on this host. This
object is useful for quickly and uniquely identifying that primary
operating system.

hrSWRunTable
OID: 1.3.6.1.2.1.25.4.2
The (conceptual) table of software running on the host.

hrSWRunEntry
OID: 1.3.6.1.2.1.25.4.2.1
A (conceptual) entry for one piece of software running on the host.
Note that because the installed software table only contains
information for software stored locally on this host, not every piece of
running software will be found in the installed software table. This is
true of software that was loaded and run from a non-local source,
such as a network-mounted file system.
As an example of how objects in this table are named, an instance of
the hrSWRunName object might be named hrSWRunName.1287.
hrSWRunIndex
OID: 1.3.6.1.2.1.25.4.2.1.1
A unique value for each piece of software running on the host.
Wherever possible, this should be the system's native, unique
identification number.

hrSWRunName
OID: 1.3.6.1.2.1.25.4.2.1.2
A textual description of this running piece of software, including the
manufacturer, revision, and the name by which it is commonly
known. If this software was installed locally, this should be the same
string as used in the corresponding hrSWInstalledName.

hrSWRunID
OID: 1.3.6.1.2.1.25.4.2.1.3
The product ID of this running piece of software.

Host Resources Running Software Group 239

Host Resources MIB (RFC 2790)

hrSWRunPath
OID: 1.3.6.1.2.1.25.4.2.1.4
A description of the location on long-term storage (e.g. a disk drive)
from which this software was loaded.

hrSWRunParameters
OID: 1.3.6.1.2.1.25.4.2.1.5
A description of the parameters supplied to this software when it was
initially loaded.

hrSWRunType
OID: 1.3.6.1.2.1.25.4.2.1.6
The type of this software.

hrSWRunStatus
OID: 1.3.6.1.2.1.25.4.2.1.7
The status of this running piece of software. Setting this value to
invalid(4) shall cause this software to stop running and to be
unloaded. Sets to other values are not valid.

Host Resources Running Software Performance Group

The hrSWRunPerfTable contains an entry corresponding to each
entry in the hrSWRunTable.

hrSWRunPerfTable
OID: 1.3.6.1.2.1.25.5.1
The (conceptual) table of running software performance metrics.

hrSWRunPerfEntry
OID: 1.3.6.1.2.1.25.5.1.1
A (conceptual) entry containing software performance metrics. As an
example, an instance of the hrSWRunPerfCPU object might be named
hrSWRunPerfCPU.1287.

240 EMC Atmos Version 1.4.0 Administrator’s Guide

 Host Resources MIB (RFC 2790)

hrSWRunPerfCPU
OID: 1.3.6.1.2.1.25.5.1.1.1
The number of centi-seconds of the total system's CPU resources
consumed by this process. Note that on a multi-processor system,
this value may increment by more than one centi-second in one
centi-second of real (wall clock) time.

hrSWRunPerfMem
OID: 1.3.6.1.2.1.25.5.1.1.2
The total amount of real system memory allocated to this process.

Host Resources Installed Software Group

The hrSWInstalledTable contains an entry for each piece of software
installed in long-term storage (e.g. a disk drive) locally on this host.
Note that this does not include software loadable remotely from a
network server.
Different implementations may track software in varying ways. For
example, while some implementations may track executable files as
distinct pieces of software, other implementations may use other
strategies such as keeping track of software "packages" (e.g., related
groups of files) or keeping track of system or application "patches".
This table is useful for identifying and inventorying software on a
host and for diagnosing incompatibility and version mismatch
problems between various pieces of hardware and software.

hrSWInstalledLastChange
OID: 1.3.6.1.2.1.25.6.1
The value of sysUpTime when an entry in the hrSWInstalledTable
was last added, renamed, or deleted. Because this table is likely to
contain many entries, polling of this object allows a management
station to determine when re-downloading of the table might be
useful.

Host Resources Installed Software Group 241

Host Resources MIB (RFC 2790)

hrSWInstalledLastUpdateTime
OID: 1.3.6.1.2.1.25.6.2
The value of sysUpTime when the hrSWInstalledTable was last
completely updated. Because caching of this data will be a popular
implementation strategy, retrieval of this object allows a management
station to obtain a guarantee that no data in this table is older than the
indicated time.

hrSWInstalledTable
OID: 1.3.6.1.2.1.25.6.3
The (conceptual) table of software installed on this host.

hrSWInstalledEntry
OID: 1.3.6.1.2.1.25.6.3.1
A (conceptual) entry for a piece of software installed on this host.
As an example of how objects in this table are named, an instance of
the hrSWInstalledName object might be named
hrSWInstalledName.96

hrSWInstalledIndex
OID: 1.3.6.1.2.1.25.6.3.1.1
A unique value for each piece of software installed on the host. This
value shall be in the range from 1 to the number of pieces of software
installed on the host.

hrSWInstalledName
OID: 1.3.6.1.2.1.25.6.3.1.2
A textual description of this installed piece of software, including the
manufacturer, revision, the name by which it is commonly known,
and optionally, its serial number.

hrSWInstalledID
OID: 1.3.6.1.2.1.25.6.3.1.3
The product ID of this installed piece of software.

hrSWInstalledType
OID: 1.3.6.1.2.1.25.6.3.1.4
The type of this software.

242 EMC Atmos Version 1.4.0 Administrator’s Guide

 Host Resources MIB (RFC 2790)

hrSWInstalledDate
OID: 1.3.6.1.2.1.25.6.3.1.5
The last-modification date of this application as it would appear in a
directory listing.
If this information is not known, then this variable shall have the
value corresponding to January 1, year 0000, 00:00:00.0, which is
encoded as (hex)'00 00 01 01 00 00 00 00'.

Conformance information

hostResourcesMibModule
OID: 1.3.6.1.2.1.25.7.1

hrMIBCompliances
OID: 1.3.6.1.2.1.25.7.2

hrMIBCompliance
OID: 1.3.6.1.2.1.25.7.2.1

hrMIBGroups
OID: 1.3.6.1.2.1.25.7.3

hrSystemGroup
OID: 1.3.6.1.2.1.25.7.3.1
The Host Resources System Group.

hrStorageGroup
OID: 1.3.6.1.2.1.25.7.3.2
The Host Resources Storage Group.

hrDeviceGroup
OID: 1.3.6.1.2.1.25.7.3.3
The Host Resources Device Group.

Conformance information 243

Host Resources MIB (RFC 2790)

hrSWRunGroup
OID: 1.3.6.1.2.1.25.7.3.4
The Host Resources Running Software Group.

hrSWRunPerfGroup
OID: 1.3.6.1.2.1.25.7.3.5
The Host Resources Running Software Performance Group.

hrSWInstalledGroup
OID: 1.3.6.1.2.1.25.7.3.6
The Host Resources Installed Software Group.

244 EMC Atmos Version 1.4.0 Administrator’s Guide

 Glossary

This glossary contains terms related to the Atmos system. Many of

these terms are used in this manual.

A
access node An internal Atmos node that acts as an entry point for requests
generated by clients who do not reside within the Atmos system. An
access node can be assigned to one tenant.

Atmos API Atmos provides an API for object access and management (REST and
SOAP), and for system management tasks.

Atmos Installable File Atmos software packaged as an rpm and installed on a RHEL5
System system running FUSE. IFS enables access to the Atmos storage cloud
from traditional file system applications.

Atmos services Atmos services include client service (CS), job service (JS), metadata
location service (MDLS), metadata service (MDS), resource
management service (RMS), storage service (SS), web service (WS).
All Atmos services (except the MDLS) run on every node in the
system. The MDLS runs on first two nodes of first RMG, and the first
node of subsequent RMGs.

Atmos Virtual Edition The Atmos software that can be installed in a virtual environment.

EMC Atmos Version 1.4.0 Administrator’s Guide 245

Glossary

C
client service CS. An Atmos service that manages requests that come in via Web
Service, IFS, and CIFS/NFS. The client service is installed on every
Atmos node.

consistency checker CC. An Atmos service that runs for each tenant. It checks all objects of
the tenant and initiates recovery if it fails to access a replica or
determines that a replica is not consistent. It runs at a low priority in
the background.

D
default policy The policy that the Atmos policy manager applies when no other
policy is assigned by the user, or no other policy matches. The default
policy is named default and defines two synchronous replicas
without location or server attribute constraints.

deletion period A policy specification that defines a time period after which Atmos
automatically deletes an object.

E
erasure code An Atmos feature that provides data redundancy without the
overhead of replication.

exceptional objects An Atmos object that is known or suspected to be out of conformance

with its placement policy specification due to the failure of one or
more of its replicas. When Atmos discovers a replica that might be in
an invalid state, it records the object on a list of exceptional objects.
These exceptional objects are automatically checked for consistency
once a day, by default.

F
federation An Atmos replica definition. When defining policies, replicas can be
federated. Federated replicas are distributed across a combination of
internal Atmos systems and external Atmos-based systems. Atmos
supports access to federated data via file-system and Web-services
access mechanisms.

246 EMC Atmos Version 1.4.0 Administrator’s Guide

 Glossary

file-system client File-system access is provided via NFS (Network File System), CIFS
(Common Internet File System), or installable file systems for specific
operating systems.

FUSE File System in User Space. Software required by the Atmos installable
file system.

G
GeoProtect An Atmos feature that provides better protection optimized for the
cloud. GeoProtect increases the availability of your content, reduces
storage overhead, and improves access to content.

I
initial master node The first node of the first installation segment in the first RMG that is
installed in the system becomes the initial master node. Each Atmos
system has only one initial master node. You use the IP address of this
node to initiate the system.

installation segment A set of nodes that share the same “private,” management subnet.

J
job service JS. The Atmos service responsible for all asynchronous
data-maintenance tasks, like asynchronous replication and
consistency checking. It runs on most Atmos nodes and is an
application that sits on top of the client.

L
location Identifies the physical location of the RMG. The RMG’s location is
specified during system installation.

M
management network The private network (eth0) that handles internal management and
installation. It is assigned a private IP address.

master node The first node installed in each installation segment. It always has
-001 appended to its node name. When a new RMG is added to the
system, it has one installation segment, hence one master node. If
more installation segments are added to that RMG later, there are

EMC Atmos Version 1.4.0 Administrator’s Guide 247

Glossary

more master nodes: an RMG with N installation segments has N

master nodes. The very first master node in an Atmos system is the
initial master node.

mauicc The Atmos service that performs consistency checking.

mauifs The Atmos service that runs on the Atmos installable file system.

mauiverify A command-line tool used to check the Atmos system’s status. It is

typically used to verify that there are no issues that will prevent a
successful upgrade. It reports system alerts, and the status of Atmos
services and nodes.

metadata disk ratio A setting applied by the user when installing Atmos. It defines the
amount of disks to use for metadata storage and the amount to use
for data storage. The ratio selected depends on what kind of data the
system is expected to handle.

metadata service MDS. The Atmos service that maintains the physical location and
layout of objects. Responsible for a range of object identifiers (OIDs)
and their metadata. It tells the client service where to store a piece of
metadata. Installed on every node.

metadata location MDLS. The Atmos service that maintains the location of MDS objects.
service An index responsible for tracking the metadata database locations,
and the MDS that owns it. It is installed on the first two nodes of a
system, and on the master node of every subsequent RMG.

metadata One of two components of an object, along with user data. Metadata
is divided into system metadata and user metadata.

N
namespace Data access provided by a file-system client occurs in the context of a
namespace.

namespace interface Atmos web services support an object interface and a namespace
interface for interacting with objects. The namespace interface allows
an application to interact with objects using file and directory paths.

node A device where Atmos software is installed and that runs the set of
Atmos services that store, retrieve, categorize, and manage the data
in the system. Nodes are either master or slave.

248 EMC Atmos Version 1.4.0 Administrator’s Guide

 Glossary

network time protocol The protocol used to synchronize the computer clock with a network
time source. Atmos requires that time be synchronized across all
nodes and clients within 5 minutes. It is recommended that an
external NTP server be used for this purpose.

O
object interface Atmos web services support an object interface and a namespace
interface for interacting with objects. The object interface allows an
application to interact with objects using the object identifier.

P
policy manager PM. An Atmos service that stores policies and selects the appropriate
service policies for objects.

policy A set of rules used to guide Atmos about how, when, and where to
replicate, and store objects. It is a combination of a policy selector and
a policy specification.

policy selector The conditions under which a policy is triggered. If you view a policy
as an if-then statement: the selector is the “if” clause.

policy specification A description of what happens when a policy is selected for use, such
as information about replicas, striping, and server attributes. If you
view a policy as an if-then statement: the specification is the “then”
clause.

private network The Atmos network interface (eth0) used for internal management
traffic, such as Installing Atmos (PXE, DHCP, and IPMI), intra-node
communications (within an IS), upgrading to a new Atmos version,
and replacing nodes.

public network The Atmos network interface (eth1 and above) used for data,
replication and system management traffic. This interface is assigned
an externally facing IP addresses.

EMC Atmos Version 1.4.0 Administrator’s Guide 249

Glossary

R
resource RMG. A collection of installation segments that share a single
management group domain. In almost all cases, this is equivalent to a subnet on the
“public,” customer network. You can create multiple RMGs on the
same subnet, as long as each RMG has a unique address. RMGs are
responsible for monitoring and discovering nodes within the subnet.

resource manager RMS. The Atmos service that tracks the availability, status, and
service location of storage services, and the specific features available with
those storage services (for example, compression).

retention An Atmos service that can be applied via policy to data-at-rest. If

enabled, it defines a time period during which an object cannot be
modified. Objects that have a retention period enabled cannot be
modified or deleted. Once the retention period expires, the object can
be modified or deleted.

rolling upgrade The upgrade process where Atmos remains accessible and responsive
while the software is upgraded.

S
SS Storage Server. A physical server on which user data is stored.

subtenant A logical subset of a tenant that groups together selected policies,

data access (that is, file-system or Web-service namespaces), and
reporting capabilities. When the SysAdmin creates a tenant, the
system automatically creates one corresponding subtenant (which is
identical to the tenant). SysAdmins can choose to create additional
subtenants within each tenant.

system management The application used to configure, manage, and monitor the Atmos
GUI system.

system metadata Atmos objects include the following system metadata: atime—last
access time, mtime—last modified time, ctime—change time,
itime—create time, uid— UID from UID List, where you create new
applications from, gid—group ID, N/A to Web Service users; ignore,
size—object size in bytes.

250 EMC Atmos Version 1.4.0 Administrator’s Guide

 Glossary

T
tenant A conceptual subset of the storage resources within an Atmos system.
Associated with a tenant are specific storage resources, security
control, storage policies, and access to the data stored on that tenant's
resources. Each tenant has a name that is unique system-wide.

Tenant Admin A role within a specific tenant, assigned to one or more users.
TenantAdmins control the storage resources, security and storage
policies, and data usage of the tenant to which they are assigned. A
given user can be a TenantAdmin for multiple tenants.
TenantAdmins are unaware of system resources other than those
defined for their tenant, nor any ability to access those resources.

U
user data Atmos objects are comprised of user data and metadata.

user meta data Metadata assigned to an object by the user. It is arbitrary key/value
pairs. Examples of user metadata are artist name (for example, for
MP3 data) and customer type.

W
web services client A flexible Web-services client interface allows direct access to the
object API over SOAP or REST. This enables customers to implement
a solution without needing to understand the underlying
implementation. Using the Atmos Web-services interface allows
customers to quickly integrate Atmos with existing applications that,
like Atmos, have a service-oriented architecture.

EMC Atmos Version 1.4.0 Administrator’s Guide 251

Glossary

252 EMC Atmos Version 1.4.0 Administrator’s Guide

 Index

Numerics community name 114

10892.mib 118 compression 94
CompressionDedup 94
Consistency Checker 109
A
access nodes 70, 142
Active Directory 70, 145 D
address translation group 186 dashboard
ADS 150 security 26
alerts 34, 112 subtenant 29
AMQP Broker Daemon 109 system 27
Apache Server 109 tenant 28
Atmos file system 70, 142 data transformations 94
authentication dcstorag.mib 118
adding and deleting users 23 deduplication 94
external 22 default policy specification 88
failover 23 default policy, tenant 55
internal 22 deletion period 98
servers 23 Dell OpenManage 118
source 30
Authentication Service 109 E
Authorization Server Failover 109 EGP group 208
email
B configuring alerts for an RMG 112
BALANCED object storage 94 OpenManage hardware traps 118
beacon on/off 44 SysAdmin 32
Erasure Code 95
exceptional objects 118
C external authentication 22
Certificate Authority 50, 73
certificates 50
checksum 94 F
CIFS 70, 142 failover, authentication 23
Cloud Federations 49 federation 48, 49, 98

EMC Atmos Version 1.4.0 Administrator’s Guide 253

Index

file system 70, 142 location 90

overview 86
system 100
G user 100
Ganglia Meta Daemon 109
Meta-Data Location Service 109
Ganglia Monitoring Daemon 109
MIB access 114
GeoProtect 247
MIB-II object hierarchy 178
GREEN object storage 94
MIB-II overview 178
Mongrel Server 109
H Monitor Target 108
HTTP daemon 156
N
I namespace 55, 76
ICMP group 198 network management station 114
initial master node 34 NFS 70, 142
installation segment 34, 41 nodes
interfaces group 181 access node 70
interfaces table 181 CIFS access 142
internal authentication 22 discovering new nodes 41
Internet Explorer 24 information 42
IP group 187 installing 42
IPMI 41 master 41
NFS access 142
Node List 42
J reinstall 44
Job Service 109 restarting 44
slave 41, 42
L tenants 70
LDAP notifications 114
server 31 NTP server 47, 142
legacy MIB 122
LockBox 57 O
logs object storage
collect system log 44 BALANCED 94
collecting logs 139 GREEN 94
disk space consumption 139 OPTIMAL 94
log package 140 objects and types imported 179
ON_CREATE 102
M ON_SMD_UPDATE 102
maintenance mode 44 ON_UMD_UPDATE 102
managing policies 86 OpenLDAP 57
master node 34
Maui Client As A Service 109 P
MDS remote replication 51 performance data 155
metadata PKCS12 73

254 EMC Atmos Version 1.4.0 Administrator’s Guide

 Index

PKCS7 73 S
placement strategies 94 Samba 145
policy Secure Sockets Layer 49
default policy specification 88 security dashboard 26
defining policies 87 SecurityAdmin
defining policy selector 100 login credentials 25
definition 86 login page 25
deletion period 98 password 30
Erasure Code 95 segment 34
federate 98 Segments’ Hardware TLA 47
management 86 server attributes 94
Manager 86 service status 35
match operators 101 Shared Secret 63, 80
metadata 89 shutdown command 44
overview 86 slave node 42, 44
reordering 103 SMTP 112
replicas 92 SNMP
retention period 98 agent 114
selector 87 community name 114
specification 87 configure for RMG 114
striping 95 configure system-wide 114
triggers 102 daemon 112, 120
XQuery expressions 101 email contact 124
private network 35 enabling traps 122
public-key certificate 73 standard MIBs 120
traps 114, 116, 122
R SNMP group 212
remote replication (MDS) 51 SOAP interface 49, 72
Replacement Failed error 35 software serial number 46, 134
replicas 92 Spread Toolkit 109
Reporting Framework 108 SSL certificates 50, 73
reports 138 statistics 157
Resource Management Service 109 Storage Service 109
REST interface 49, 72 striping 95
restarting nodes 44 SubtenantAdmin 23
retention period 98 email address 82
RMG login credentials 25
adding nodes 41 login page 25
definition 35 password 82
new 34 subtenants
roles authentication source 76
SecurityAdmin 22 creating 76
SubtenantAdmin 22 dashboard 29
SysAdmin 22 definition 23
TenantAdmin 22 list 76
namespace 76

EMC Atmos Version 1.4.0 Administrator’s Guide 255

Index

renaming 78 traps
root directory 76 atmosNotificationCpuUsage 114
SubtenantAdmin role 80 atmosNotificationDAEBackplaneStatus 115
SYR, see system reporting 106, 133, 135 atmosNotificationDAEFanStatus 115
SysAdmin 22 atmosNotificationDAEStatus 115
deleting a TenantAdmin 69 atmosNotificationDAETempStatus 115
login credentials 25 atmosNotificationDiskRecovery 116
login page 25 atmosNotificationDiskStatus 115
password 25 atmosNotificationExternalCarrierStatus 115
system dashboard 27 atmosNotificationFilesystemUsage 114
system group 179 atmosNotificationInternalCarrierStatus 115
system log 44 atmosNotificationMemoryUsage 114
system reporting atmosNotificationMgmtDBStatus 116
Atmos configuration 46 atmosNotificationNodeStatus 115
configuring 133 atmosNotificationPolicyResourceStatus 116
database 106, 133, 135 atmosNotificationPolicySyncFailed 115
reports 138 atmosNotificationRMGStatus 115
atmosNotificationSegmentStatus 115
atmosNotificationServiceMemoryUsage 115
T atmosNotificationServiceStatus 115
TCP connection table 204
atmosNotificationSwapUsage 114
TCP group 202
atmosNotificationUidSyncFailed 115
tenant dashboard 28
atmosNotificationVIPFailover 116
TenantAdmin
Dell OpenManage 118
creating a SubtenantAdmin 80
MAUI_MGMTDB_OID 118
deleting a SubtenantAdmin 83
MauiAppServiceCrash 117
email address 67
MauiAppServiceMemory 117
login credentials 25
MauiAppServiceRestart 117
login page 25
MauiDAEBackplane 116
password 67
MauiDAECriticalEvent 118
role 22
MauiDAEDiskFailure 116
Update My Information 68
MauiDAEEnclosureFail 117
tenants
MauiDAEFanOperation 116
authentication source 56
MauiDAETempThreshold 117
creating 55
MauiNodeCPU 117
default policy 55
MauiNodeDiskError 118
default policy specification 88
MauiNodeDown 116
default subtenant 78
MauiNodeFileSystem 117
LDAP configuration 58
MauiNodeIntfCarrier 116
list 54
MauiNodeMemory 117
namespace 55
MauiNodeSwap 117
nodes 70
MauiNodeTempThreshold 116
renaming 64
MauiRmgDown 117
root directory 55
MauiSegmentDown 118
TenantAdmin role 65
MauiTrapGeneric 116
textual conventions 178
MauiTrapPolicySyncFail 117
transmission group 211
MauiTrapUidSyncFail 117

256 EMC Atmos Version 1.4.0 Administrator’s Guide

 Index

NUM_EXCEPTION_RECS_OID 118 V
overview 114 VMware 35
RECOVER_DISK_OID 118

X
U XQuery expressions 101
UDP group 206
UID 80

EMC Atmos Version 1.4.0 Administrator’s Guide 257

Index

258 EMC Atmos Version 1.4.0 Administrator’s Guide