Error message

Deprecated function: implode(): Passing glue string after array is deprecated. Swap the parameters in drupal_get_feeds() (line 394 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).

7

emc ecc manual

LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF

File Name:emc ecc manual.pdf
Size: 3403 KB
Type: PDF, ePub, eBook

Category: Book
Uploaded: 16 May 2019, 18:49 PM
Rating: 4.6/5 from 738 votes.

Status: AVAILABLE

Last checked: 3 Minutes ago!

In order to read or download emc ecc manual ebook, you need to create a FREE account.

Download Now!

eBook includes PDF, ePub and Kindle version

✔ Register a free 1 month Trial Account.

✔ Download as many books as you like (Personal use)

✔ Cancel the membership at any time if not satisfied.

✔ Join Over 80000 Happy Readers

emc ecc manualFeatures and Indicators Back-Panel FeaturesIndicator Patterns Power SupplyCodes and Features Related Documentation Controller Modules RAID Controller. Modules RAID Controller. Module Connectors And Features RAID Controller. Module—Additional Features Battery Backup. Unit Storage Array. Thermal Shutdown System Password. Reset Cache FunctionsCache Installing Array. Components Recommended Tools Front Bezel (Optional) Removing the. Front Bezel Installing the. Front Bezel Physical Drives SAFETY Models. AMT E03J and E04J Removing a 2.5. Inch Physical-Drive Blank Installing aInch Physical-Drive Blank Installing aPhysical Drive Installing a. Hot-Swap Physical Drive Removing a Physical. Drive From a Physical-Drive Carrier Installing a. Physical Drive Into a Physical-Drive Carrier RAID Controller. Module Removing a RAID. Controller Module Blank Installing a. RAID Controller Module Blank Removing a RAID. Controller Module Installing a. RAID Controller Module Opening the. RAID Controller Module Closing the. RAID Controller Module RAID Controller Module. Backup Battery Unit Removing the. RAID Controller Module Backup Battery Unit Installing the. RAID Controller Module Backup Battery Unit Power Supply or Cooling. Fan Module Removing a Power. Supply or Cooling Fan Module Installing a. Power Supply or Cooling Fan Module Control Panel Removing the. Control Panel Installing the. Control Panel Backplane Removing the. Backplane Installing the. Backplane Troubleshooting. Your System Troubleshooting. Storage Array Startup Failure Troubleshooting. Loss of Communication Troubleshooting. External Connections Troubleshooting. Power Supply or Cooling Fan Modules Troubleshooting. Array Cooling Problems Troubleshooting. Expansion Enclosure Management Modules If EMM Status. LED is Blinking Amber at Five Times per Sequence If the EMM Status. LED is Solid or Blinking Amber at Two or Four Times per Sequence If the Link. Status LEDs are not Green Troubleshooting. RAID controller modules If the Array.http://www.goldia.cz/data/delonghi-grill-indoor-manual.xml

    Tags:
  • emc ecc manual, emc ecc manual user, emc ecc manual transmission, emc ecc manual pdf, emc ecc manual transmissions.

Status LED is Solid or Blinking Amber If the Link. Physical Disks Troubleshooting. Array and Expansion Enclosure Connections TroubleshootingArray ECC Errors PCI errors Technical Specifications Getting help Locating your. You may also need to provide your support ID if you have not already done so. Storage infrastructures include multivendor arrays such as storage area networks (SANs), network-attached storage (NAS), content-addressed storage (CAS), and switches. You may also need to provide your support ID if you have not already done so. These trademarks are. For a full experience use one of the browsers below Instructions for the following steps are located in the NVIDIA Virtual GPU Software Quick Start Guide. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search. However, results ranking takes case into account and assigns higher scores to case matches. Refer to the NX-series EtherCAT Coupler Unit User’sFor the node addressFor example, the values are as follows when the EtherCATIf you use any of thoseFor information on the communications cycles that you can set, refer toHowever, note that only NX-ECC203 EtherCAT Coupler Units (Ver. 1.5 or later) isIf a Unit does not have the specified version,Refer to the user's manuals for the. Please check your inbox, and if you can’t find it, check your spam folder to make sure it didn't end up there. Please also check your spam folder. Compliant with EMC and LVD. HVAC232 and HVAC402 are compact in size and flexible in application with one free slot for an option board. Easy to operate and commissioning with an embedded wizard. Published December 2010 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.http://mapect.com/upload/fckeditor/delonghi-ec-145-espresso-manual.xml 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 Data Protection Advisor Version 5.7 Administration Guide Contents Preface Chapter 1 Security and Port Settings Ports and protocols. Overview. Server port settings. GUI Client port settings. Illuminator port settings. Collector port settings. Startup process. Security. Encryption. An encryption session. Key Tool. Encryption from a web browser interface. Chapter 2 12 12 14 14 15 16 17 18 19 19 20 21 Configuring Data Monitoring Introduction to DPA data monitoring. Data Collection and Discovery Wizards. Data collection and licensing. Requests. Testing credentials. Gathering historical data. Application Hosts. Prerequisites. Importing hosts from a CSV file. Importing hosts from EMC Ionix ControlCenter. Monitoring a single host. Storage arrays. EMC CLARiiON. EMC Symmetrix. Monitoring storage arrays that use RecoverPoint. Applications. CA BrightStor ARCserve. Adding a label to a Control Panel. Adding an image to a Control Panel. Adding a report to a Control Panel. Adding a button to a Control Panel. Working with Control Panels. Running a Control Panel from the navigation tree. Setting an initial Control Panel. Editing a Control Panel. Deleting a Control Panel. Chapter 6 Configuring Analysis Jobs Rulesets and analyses. Ruleset. Analysis. Generating events from analyses. Assigning an analysis job. Creating an alert. Alert arguments. Creating an analysis job. Editing an analysis job. Chapter 7 122 122 122 122 123 123 126 127 129 Using the Ruleset Editor Ruleset basics. Creating a simple ruleset. Complex rulesets. Testing a ruleset. Chapter 8 114 115 115 116 117 118 118 118 118 119 132 133 141 143 Troubleshooting and Reporter Performance Tuning the Reporter for performance. Reporter worker processes. Log files. Server process log files. Client process log file. Recoverability server log.http://www.diamondsinthemaking.com/content/boss-gt-10b-owners-manual Changing the log level (server). Managing the log files. Viewing log files from the GUI. Sending notifications on warnings and errors. Processes. Stopping and restarting a process. Viewing process status from the GUI. Data collection. Data collection troubleshooting first actions. Data collection troubleshooting second actions. Data collection troubleshooting third actions. Preparing a log file for submission to EMC Support. Client discovery (recoverability analysis). Remote client discovery. Local client discovery. General client discovery. EMC Data Protection Advisor Version 5.7 Administration Guide 146 146 148 148 148 148 149 150 150 151 152 152 152 153 153 153 153 154 155 155 157 158 5 Contents Incorrect Recovery Point times. 159 Report history. 161 System clock synchronization. 162 Appendix A Analysis Job Definitions Capacity planning. 164 Change management. 165 Configuration. 166 Data protection. 168 Licensing. 170 Performance. 171 Provisioning. 172 Resource utilization. 173 Service Level Agreements. 175 Status. 176 Troubleshooting. 178 Appendix B WDS File Importing the WDS file. 183 Exporting the WDS file. 184 Appendix C Command Line Operations Exporting the WDS file. 186 Running reports from the Publisher. 188 Syntax. 188 Classpath. 189 Changing the terminology in the GUI. 191 Loading historical backup job data. 192 Job summary reports. 192 Index 6 EMC Data Protection Advisor Version 5.7 Administration 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 the product release notes. If a product does not function properly or does not function as described in this document, please contact the EMC representative.https://gabrieliassociati.com/images/97-chevy-blazer-owners-manual.pdf Purpose Audience This guide describes the networking environment requirements for Data Protection Advisor and the prerequisites for setting up data monitoring for each supported data protection server or appliance in the environment. The guide also describes the advanced adminstrative functions, including creating custom reports and analysis jobs. This guide is intended for users already familiar with Data Protection Advisor. System administrators should use this guide, along with the EMC Data Protection Advisor Installation Guide, to prepare their environment for data monitoring by DPA. Advanced DPA users should also use this guide to create custom reports and Control Panels, and set up analysis jobs for alerting on environment changes. The chapter also describes the authentication and encryption options available for interprocess communication. Requests are the DPA objects that capture information about how, what, and how often to gather data from monitored components. Credentials contain connection and authentication information and are used by the Collector to access monitored components and gather data. Analysis jobs are a set of user criteria that the Analysis Engine uses to scan the database and alert on changes in conditions. A ruleset is the set of conditions that is contained in an Analysis Job. The chapter also describes how to scale Reporter performance in large environments. Appendix A, ”Analysis Job Definitions,” lists all of the system Analysis Jobs that ship with DPA. Appendix B, ”WDS File,” describes how to import and export configuration data from the DPA server. Appendix C, ”Command Line Operations,” describes a number of command line utilities for use by administrators. Related documentation 8 Related documents include. EMC Data Protection Advisor Compatibility Guide — Provides information on all of the components of a data protection environment supported by DPA, including servers, databases, and operating systems. ? EMC Data Protection Advisor Preinstallation Checklist — Provides a checklist of all of the prerequisite activities that must occur before DPA is installed and data can be gathered for reporting. ? EMC Data Protection Advisor Installation Guide — Describes the minimum system requirements for the DPA Server, Collector and GUI client, and describes how to install or upgrade those components. The guide also describes how to configure the database that will be used to store DPA configuration and datamine data. ? EMC Data Protection Advisor Quick Start Guide — A quick start guide for installing and setting up DPA for experienced users. ? EMC Data Protection Advisor Product Guide — Provides an overview of the DPA architecture and explains how administrator's configure basic operations such as creating users and user roles, and configuring views, nodes and queries. ? EMC Data Protection Advisor Report User Guide — Provides information on how to use the DPA GUI to create, modify, and run reports, as well as perform basic reporting functions. This guide also includes a listing of all the predefined, system reports that come installed with DPA. ? EMC Data Protection Advisor Report Reference Guide — Describes in detail the predefined, system reports by report type that are installed with DPA. ? EMC Data Protection Advisor Data Collection Reference Guide — Discusses each of the DPA data collection modules, describing the information that each module returns and how it obtains that data. ? EMC Data Protection Advisor API Reference — Describes the Application Programming Interface (API) to the DPA Controller and Reporter. ? EMC Data Protection Advisor Release Notes — Provides the latest information about fixed and known defects in the release and also provides information about new product features and changes for the release. ? EMC Data Protection Advisor online help — Provides detailed context-sensitive information about screens of the product to help customers learn and understand how to use DPA. EMC Data Protection Advisor Version 5.7 Administration Guide Preface Conventions used in this document EMC uses the following conventions for special notices. Note: A note presents information that is important, but not hazard-related. Ellipses indicate nonessential information omitted from the example 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 Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact the EMC sales representative for details about obtaining a valid support agreement or to answer any questions about the account. EMC Data Protection Advisor Version 5.7 Administration Guide 9 Preface Your comments Comments and suggestions about our product documentation are always welcome. It includes the following sections. ? ? ? ? Ports and protocols. Startup process. Security. Encryption. Security and Port Settings 12 17 18 19 11 Security and Port Settings Ports and protocols The port and networking requirements for DPA components to communicate with each other are described in this section: Overview ? “Overview” on page 12 ? “Server port settings” on page 14 ? “GUI Client port settings” on page 14 ? “Illuminator port settings” on page 15 ? “Collector port settings” on page 16 DPA uses several predefined TCP ports for communication between DPA processes. This section describes the port requirements for the DPA Server, GUI Client, and Collector components. The ports described in this section are the default values. If necessary, an administrator can change the port on which a process listens from the System Settings dialog. Chapter 4, “Credentials,” describes how to configured the system settings for a process. Server process communications This process: Listens on port: Communicates with: Collector 3741 Controller, Listener Controller 3916 All other processes Listener 4001 Collector, Controller, GUI Reporter 4002 Controller Publisher 4007 Controller, Reporter, GUI Web Server 9002 GUI The default ports for communications between theGUI Client and Server processes are described in Table 2 on page 14. Client communications Client listens on port: Communicates with: 3916 Controller 4002 Reporter 9002 Web Server The user can launch the GUI from a web browser, or chose to install it locally. If they choose to launch from a web browser, the client also needs to be able to connect to port 9002, which is the web server. 4001 Listener In the backup module, the user has the ability to annotate failed backups with the reason the job failed and other information. To use this feature, the GUI needs to connect to port 4001 (Listener) to store data in the database. 4007 Publisher If the user is using scheduled reports, and wishes to test the report from the GUI, the GUI neeeds to connect to port 4007 (Publisher). For almost all functionality, the GUI Client only needs to connect to ports 3916 (Controller) and port 4002 (Reporter). Connection to ports 9002, 4001, and 4007 are only required if the features described in Table 2 on page 14 are required. 14 EMC Data Protection Advisor Version 5.7 Administration Guide Security and Port Settings Illuminator port settings Table 3 The default ports for communication between the recoverability server (the Illuminator process) and the other server processes are described in Table 3 on page 15. Illuminator server communications This process: Listens on port: Communicates with: Illuminator 3916 Controller Controller 3916 Illuminator Reporter 8583 (by RMI) Illuminator Illuminator 8587 (by RMI) Reporter Illuminator 25011 - Always used. 8090 - Opened from the proxy host. Use when the Discovery proxy host is not the DPA server. Collector Collector 3741 Illuminator The default port settings for gathering date remotely from the Illuminator server are described in Table 4 on page 15. Table 4 Remote communications Operating system Direction: Using port: Windows From DPA server RPC port range (Default port 135). To DPA server RPC port Range (Default 1024-65535). Collector only or application host with Collector This scenario refers to a DPA Collector installed remotely on any platform, or a Collector installed on an application host (for exampole, an ECC host). ? Windows proxy Collector This scenario refers to a DPA Collector installed on a Windows platform to perform discovery on Windows hosts. This configuration is required to remotely discover Windows hosts when DPA server is running on Solaris. ? Application host without Collector This scenario refers to discovery performed on an application host without a Collector installed local to the host. Ports and protocols 15 Security and Port Settings If the recoverability discovery process is performed remotely, DPA will attempt on SSH (default port 22). If this fails, DPA will attempt an RPC connection (default port 135). The following must be enabled to ensure communication between the monitored host and the Illuminator process: Collector port settings 16. The Controller must communicate with the Collector on port 3741 to allow the Collector to be informed of changes in the configuration. This information includes the items to monitor along with any options (for example, username and passwords, specific ports, time-out values, polling interval). 4. The Collector immediately starts monitoring the system upon receipt of the configuration. 5. Upon gathering data, the Collector formats the information into an XML packet, and sends the packet to the Listener. 6. The Collector returns to idle, and continues polling each request at the specified interval for that request. 7. The Listener, upon receipt of a packet from the Collector, inserts the data into the database, either as a new row or as an update to data that is already present. In addition, specific Collectors may require other available ports. For example, collecting data through SNMP requires access from the Collector to port 161 on the node being monitored by both TCP and UDP protocols. The full details of the ports required for each module depend on the application being monitored (for example, NetWorker or Symantec NetBackup). Chapter 2, “Configuring Data Monitoring,” describes the configuration prerequisites for all of the data gathering modules of DPA. Startup process 17 Security and Port Settings Security Security for all server processes includes the Reporter, Listener, Analysis engine, and Publisher. If security is enabled, users are not able to connect to any of these processes using the API without being authenticated first. To enable security, modify the controller.xml file on the server. There is an AUTHREQUIRED setting in this file that can be set to one of three values:.Users can connect to Server-side processes using the API without being authenticated. ? compatauth Security is enabled. Users must authenticate when connecting to the Server-side processes. This method should be used with Collectors 2.1 or 2.1.2 in your environment. ? fullauth Security is enabled. Users must authenticate when connecting to server processes. This method should be used if all Collectors in the environment are version 3.0 or later. If upgrading from a previous version that had security enabled, the security setting is automatically changed to the new method of configuration, and the security level is set to compatauth. If Collectors earlier than version 2.1 are in your environment, do not enable server security. The Collectors will not be able to communicate with the Controller and will stop gathering data. 18 EMC Data Protection Advisor Version 5.7 Administration Guide Security and Port Settings Encryption If encryption is enabled, all communications between all processes in the product are encrypted. To enable encryption, modify the controller.xml file on the server by changing the CRYPTREQUIRED variable to one of the following values:.Use this setting if components in the environment are an earlier version of the product and are not capable of encryption. ? enforce All communications are encrypted. If a component is incapable of encrypting data, it will not be able to communicate with other processes. Use this setting if all components are version 3.1 and later. If upgrading from an old version of DPA, set the Collector to allow so that Collectors in the environment that have not been upgraded can continue to communicate with the server. Restart the Controller to apply the changes and enable encryption. An encryption session When encryption is enabled, data is encrypted using the Advanced Encryption Standard (AES). A session key is used to encrypt all data sent across the network. This key is unique to each individual network connection and is used only for the duration of that connection. When a client initiates a network connection, it must negotiate a session key with the server. As part of the negotiation phase, the initiating process sends a private key across the network to the server. The server generates a unique session key and encrypts the key using the private key of the client. The session key is then returned to the client, which then uses that key to encrypt all data sent over the network using AES. The private key used by the client process during the negotiation of the session key is created by default when the process is installed. This key is unique to that host. By default, the client process will generate a 2048 bit RSA key. The following algorithms are supported. RSA (1024 and 2048 bit keys). AES (128 and 256 bit keys) ? 3DES (192 bit keys). DES (56 bit key). The encryption algorithm and key used during the session key negotiation can be modified by a customer if necessary, using the key tool. The key tool binary is used to generate a new encryption key. If the parameter is not specified, the file is created in the same directory in which the command was run, with a file extension that matches the specified algorithm and key length. On UNIX platforms, you must source the dpa.config file before running the key tool. The location of the keys directory depends on the operating system. After creating a key, move the key file into the keys directory on that machine. Multiple keys can be placed in the keys directory. The encryption process uses the key with the longest key length that exists in the keys directory. After putting the key file in the keys directory, all processes must be restarted for the change to take affect. 20 EMC Data Protection Advisor Version 5.7 Administration Guide Security and Port Settings Encryption from a web browser interface To change the encryption method used by a GUI launched from a web browser, the generated keys must be placed inside a jar file. When the product is first installed, Data Protection Advisor automatically starts gathering information about the host on which the DPA server is installed. Data Collection and Discovery Wizards Monitoring devices and applications is automated by the Data Collection Wizard and the Discovery Wizard, which configure DPA using a series of questions about the device or application to monitor. After defining a device or application in a wizard, one or more nodes are automatically added to the Configuration view and data monitoring by the Collector starts. The sections in this chapter describe how to use the wizards to configure all of the components of a data protection environment that DPA monitors. Many devices and applications require configuration tasks to be performed on the DPA server, the Collector proxy host, or the monitored host before using the Data Collection Wizard or Discovery Wizard. These prerequisite tasks are also described. Data collection and licensing The options that are available for configuration in the Data Collection and Discovery wizards depend on the types of licenses that you have installed with DPA. If you do not have the correct license installed, the option to create that device or host is disabled in the wizard. The EMC Data Protection Advisor Installation Guide describes the license types available for DPA. For more information on how to obtain licenses for reporting, please contact an EMC Account Manager or Customer Support Engineer. Requests are assigned to a node automatically after that node is created using the Data Collection or Discovery wizards. You can change data gathering for a node by changing the details of the assigned requests, and the type of requests assigned. Testing credentials For most devices and applications, a credential is required for the Collector to access the device or server. The Data Collection and Discovery Wizards prompt for the credential during the configuration process. A Test button is available in the wizard that tests the validity of the supplied credential by connecting briefly to the device or application. Gathering historical data 24 The Collector can also gather historical backup data from jobs that were run prior to the backup application being configured in Data Protection Advisor. Appendix C, ”Command Line Operations,” contains more information on gathering historical data. EMC Data Protection Advisor Version 5.7 Administration Guide Configuring Data Monitoring Application Hosts DPA can monitor database hosts and Microsoft Exchange Server for recoverability analysis. There are two methods to configure application hosts for monitoring in DPA. To configure multiple hosts, use the Discovery Wizard. Hosts can be imported from a CSV file, or by connecting to an EMC Ionix ControlCenter host and importing the defined clients. ? To configure a single host, use the Data Collection Wizard. Prerequisites To perform an import from a CSV file, the user must select a text file from the local filesystem that is in a comma-separated value format. The format of the file must be: Client,AlternativeName,Timezone,Platform The values for the time zone field and Platform field are optional, but if specified must conform to the following formats. Timezone — A valid Java time zone string, as defined at NormalizedCustomID. Platform — One of: Windows, Solaris, Linux, HP-UX, AIX, ESX. If no time zone is specified, the default time zone is taken from the machine on which the DPA client is running. The credentials used to connect to the storage array host must include the following. Windows — A user with local or domain administrator rights. Application Hosts 25 Configuring Data Monitoring. The SUDO program should support the -p parameter and the -s parameter when the interactive mode is used. The following must be enabled to ensure communication between the monitored host and the recoverability process. The Discovery Wizard appears. 2. Select Servers and click Next to proceed to the Import Source panel. 3. Select File, and enter the full path to the CSV file in the File name field, or click Browse to search for the file. 4. Click Next to proceed to the Select Clients panel. All of the hosts defined in the CSV file are displayed. 5. Select the hosts from the file to be imported. Click Next. The Recoverability panel appears. 6. Select Monitor for Recoverability to enable recoverability analysis for the selected hosts. 7. Select a Credential to use to connect to the hosts to gather recoverability data, or click Edit to modify or create a credential. 8. Select a Schedule for the recoverability data gathering request, or click Edit to modify or create a schedule. Click Next. The Import Location panel appears. 9. Select Assign nodes in Tree to assign the imported host nodes to the selected position in the Configuration view. By default, the created nodes are not added to the Configuration view, but added to the configuration database, and can be edited and assigned from the Node List dialog. 10. Click Next. The Importing panel appears. Click Next to start importing the selected clients. 11. A message indicates if the import process was successful. Select Finish to close the Discovery Wizard, or OK to return to the Wizard if the import failed. 12. If the import was successful, the host nodes are created and the client discovery request is assigned to the nodes with the specified credential and schedule to gather recoverability data. Importing hosts from EMC Ionix ControlCenter 26 You can discover application hosts from EMC Ionix ControlCenter by connecting to the ControlCenter host. EMC Data Protection Advisor Version 5.7 Administration Guide Configuring Data Monitoring Prerequisites The DPA Collector must be able to communicate with the ECC API. The credentials used to connect to hosts for recoverability monitoring must include the following. The Discovery Wizard appears. 2. Select Servers and click Next to proceed to the Import Source panel. 3. Select ECC connection. 4.