OnCommand Insight 6.4

Transcription

1 OnCommand Insight 6.4 Installation and Administration Guide NetApp, Inc. 495 East Java Drive Sunnyvale, CA U.S. Telephone: +1(408) Fax: +1(408) Support telephone: +1(888) 4-NETAPP Web: Feedback: Part number: _A0 March 2013

2

3 Table of Contents 3 Contents Welcome to OnCommand Insight OnCommand Insight features OnCommand Insight product portfolio Where to find more information about OnCommand Insight Videos for OnCommand Insight Accessing OnCommand Insight online help OnCommand Insight on the web OnCommand Insight product documentation Planning the deployment OnCommand Insight architecture Example of a common OnCommand Insight implementation OnCommand Insight Server requirements Remote Acquisition Unit server requirements OnCommand Insight Client requirements Data Warehouse and Reporting server requirements OnCommand Insight browser requirements Data Source Support Matrix Device identification and data source planning Network traffic generated by OnCommand Insight OnCommand Insight upgrade prerequisites OnCommand Insight installation and upgrade instructions Downloading the OnCommand Insight installer Installing OnCommand Insight Server Installing the OnCommand Insight Server Verifying new OnCommand Insight services Uninstalling the OnCommand Insight services Logging into the OnCommand Insight Administration portal Installing your OnCommand Insight licenses Directly importing OnCommand Insight licenses Replacing expired licenses OnCommand Insight licenses Restarting the OnCommand Insight Server using a command window... 37

4 4 OnCommand Insight Installation and Administration Guide Restarting the OnCommand Insight Server using the Control Panel Installing the OnCommand Insight Data Warehouse and Reporting Locating IBM Cognos documentation Verifying the Data Warehouse and Reporting installation Uninstalling Data Warehouse and Reporting Installing the vcenter Server plug-in for OnCommand Insight Installing the vcenter Server plug-in Configuring VM reports Adding VM reports Removing the vcenter plug-in registration Upgrading OnCommand Insight reports Backing up custom reports and reporting artifacts Restoring and upgrading reports after upgrading from OnCommand Insight versions before Restoring the portal tabs Upgrading SQL-based reports Troubleshooting installations Missing licenses Disabling User Account Control (UAC) in Windows Backend storage connectivity disruption during upgrades Accessing storage data in the OnCommand Insight Client Accessing the OnCommand Insight Client Accessing the OnCommand Insight Client using Windows Start Accessing the OnCommand Insight Client using a web browser Determining your OnCommand Insight license information Identifying OnCommand Insight license information Types of switch ports counted in OnCommand Insight Identifying the number of licensed switch ports Maintaining OnCommand Insight Checking for OnCommand Insight updates OnCommand Insight logs Creating a Support report for troubleshooting assistance Data source setup and device identification How OnCommand Insight identifies devices Managing acquisition unit communication with storage devices Acquisition units and data sources... 60

5 Table of Contents 5 Unsupported device configurations Installing a Remote Acquisition Unit (RAU) Verifying the remote acquisition unit service Validating the remote acquisition unit installation Reviewing acquisition information Removing an acquisition unit Removing a remote acquisition unit using Microsoft Windows Control Panel Acquisition Units reference Setting up data sources for data acquisition Preparing to add a data source Importing data sources from a spreadsheet Adding a data source Adding an Array Performance data source Forcing acquisition manually Managing data sources Troubleshooting data source activity Data sources reference Vendor-specific data source reference PAR (CLI) data source Brocade data source selection Brocade (CLI) data source Brocade (MPR - Multi Protocol Router) data source Cisco data source (All Models Using SNMP) data source EMC Atmos data source EMC Celerra SSH EMC CLARiiON (CLI) data source EMC Connectrix 7 data source EMC Connectrix 8.1, 8.6, 8.7, 8,8, 8.9, 9.0, 9.1, 9.5, 9.6, 9.7 data source EMC ECC StorageScope Host Resolver data source EMC Solutions Enabler (CLI) with CLI Performance EMC Solutions Enabler (CLI) with SMI-S Performance data source EMC VNX data source EMC VPLEX data source Engenio Arrays data source Fujitsu Eternus

6 6 OnCommand Insight Installation and Administration Guide Generic file system level utilization (FSLU) data source (Beta) HDS HiCommand Device Manager data source HDS HiCommand Device Manager Lite data source HP CommandView AE data source HP CommandView AE Lite data source HP (EVA) HP (XP) data source IBM DS (CLI) data source IBM ESS (CLI) data source IBM FAStT data source IBM PowerVM data source (Beta) IBM SVC (CLI) data source IBM Tivoli Monitoring data source IBM TotalStorage DS4000 data source IBM XIV (CLI) data source McData (EFCM) Manager (8.1, 8.6, 8.7, 8.8, 8.9, 9.0,9.1, 9.5, 9.6, 9.7) data source McData EFCM 7 data source McData Sphereon SNMP data source NetApp Clustered Data ONTAP data source NetApp Data ONTAP operating in 7-Mode (ONTAPI) data source QLogic SANsurfer (SNMP) data source VMware Identifying hosts and tapes automatically with Auto Resolution (AR) Automatic host and tape resolution overview Setting host and tape Auto Resolution schedule and preferences Enabling or disabling Auto Resolution by using the Identify views Setting Auto Resolution methods Selecting Auto Resolution storage and tape vendors Re-identifying generic devices with automatic resolution Auditing automatic host and tape resolution Settings for Auto Resolution Identifying and managing FC generic devices Generic devices overview How OnCommand Insight displays generic devices Viewing a list of generic devices

7 Table of Contents 7 Identifying FC-based generic devices manually Making manual identifications with auto resolution rules Deleting FC-based device identification Ensuring that a device is inactive Deleting inactive devices from OnCommand Insight inventory Auditing automatic host and tape resolution Identifying and managing iscsi sessions and NAS shares How OnCommand Insight displays NAS shares How iscsi initiators appear Identifying iscsi sessions and NAS shares manually Identifying a subnet to a mock host Deleting IP-based identification information OnCommand Insight configuration and administration tasks Starting and stopping the OnCommand Insight services Starting the OnCommand Insight Server Starting the OnCommand Insight Client in Windows Starting the OnCommand Insight Client in a browser Stopping the OnCommand Insight Server and acquisition Configuring your configuration prerequisites Configuring your for OnCommand Insight Managing user accounts Setting up user accounts Configuring user definitions using LDAP Changing user passwords Editing a user definition Deleting a user account Configuring SNMP notifications Verifying the SNMP configuration Enabling the syslog facility OnCommand Insight syslog contents OnCommand Insight administrative tasks Performing administrative tasks Configuring servers and passwords Consolidating host data from multiple servers Auditing system and user activities

8 8 OnCommand Insight Installation and Administration Guide Audit view Using the Admin Tools toolkit Opening the Admin Tools portal Showing OnCommand Insight logs Browsing the SAN to locate devices Calculating the Recovery Point Objective (RPO) Running a paths and violations query Triggering VM NAS job Customizing the Help menu Managing Data Warehouse and Reporting user accounts Accessing the Data Warehouse and Reporting Reporting user roles Adding a Reporting user Managing user accounts Configuring Reporting LDAP Setting up and running OnCommand Insight backups Restoring the OnCommand Insight database Backing up the Data Warehouse database Backing up custom reports and reporting artifacts Restoring the Data Warehouse database Troubleshooting and OnCommand Insight ASUP Enabling or disabling automatic disk model updates Adding a missing disk model Downloading extended logs Restarting the OnCommand Insight Server or acquisition unit Configuring the number of hours to ignore dynamic data Sending data to NetApp Customer Support automatically Scrubbing data for transfer to support Generating logs for Customer Support Displaying system information Listing installed OnCommand Insight packages Calculating the number of database objects Moving MySQL data using the migrate option Forcing annotation updates Configuring Client settings Checking a tier upgrade

9 Table of Contents 9 Checking the status of server resources Finding ghost data sources Copyright information Trademark information How to send your comments Index

10 10 OnCommand Insight Installation and Administration Guide Welcome to OnCommand Insight The OnCommand Insight product suite provides visibility into the services delivered by your global storage infrastructure, including host-to-storage access paths, storage availability, and system changes. OnCommand Insight presents a single view of your storage infrastructure and supports Fibre Channel, iscsi, NFS, and CIFS protocols. OnCommand Insight features OnCommand Insight provides near real-time data center visibility for servers, applications, and pathways among heterogeneous devices and components. OnCommand Insight also offers visibility into the storage services delivered by a storage infrastructure. OnCommand Insight does the following: Operates as agent-less software that runs on Microsoft Windows. Discovers the entire heterogeneous SAN environment within hours. Correlates thousands of physical and logical components into storage service paths. Operates with vendor APIs to discover and obtain updated information on data source device configurations. Periodically monitors the environment, logs changes in the environment, and assesses the impact of those changes. Provides executive summary and detailed reports. OnCommand Insight product portfolio OnCommand Insight is a suite of products that boost the quality and efficiency of your storage environment by providing near real-time visibility, multi-vendor and multi-protocol support, and end-to-end service-level views of your application storage path. The OnCommand Insight portfolio provides the tools for you to manage your environment. You can do the following: Optimize the assets that you have on the floor, according to space, performance, and usage criteria. Optimize the business activities, such as application or storage service, on your assets. The OnCommand Insight portfolio includes the following products:

11 Welcome to OnCommand Insight 11 OnCommand Insight Assure OnCommand Insight Perform OnCommand Insight Plan Helps administrators focus on maintaining storage service on their storage resources. Lets administrators establish global, application, host, or path-based service policies and manage the effects of change, risk, and service-level violations of those policies on availability and performance. Helps administrators focus on their storage resources. Collects and maintains service performance information to help administrators reclaim under-utilized storage resources, manage tiers, analyze storage virtualization efficiency, improve load balancing, troubleshoot congestion and contention, and improve resource utilization to optimize services. Helps administrators focus on both storage resources and the services on those assets. Provides administrators with an end-to-end view of resource order, the storage allocation process, and trend usage so that they can manage resource reservations and forecast consumption and resource needs. Administrators can report on costs for storage services by business entity or tier and use this information for chargebacks on storage usage. Business level roll-up reporting helps storage administrators improve capacity planning and optimize consumption by application and tier. OnCommand Insight Assure, OnCommand Insight Perform, and OnCommand Insight Plan use the same integrated discovery component. This discovery component provides visibility into storage availability, resource inventory, and host-to-storage access paths. Administrators can also gain visibility into the path from virtual machines to arrays for organizations deploying VMware ESX technology combined with VMware vcenter (VirtualCenter) technology. The Inventory features are the foundation features for the OnCommand Insight suite and are used in OnCommand Insight Assure, OnCommand Insight Perform, and OnCommand Insight Plan. OnCommand Insight Assure, OnCommand Insight Perform, and OnCommand Insight Plan also use the same report authoring tools and the same Data Warehouse platform.

12 12 OnCommand Insight Installation and Administration Guide Where to find more information about OnCommand Insight You can find more information about OnCommand Insight on the NetApp Support Site and in other OnCommand Insight documentation. Videos for OnCommand Insight You can access how-to videos that show you how to perform some actions in OnCommand Insight. The videos are located on the OnCommand Insight Customer Community, a forum for customers. Many individual topics in the OnCommand Insight documentation include links to specific videos. Note: To see OnCommand Insight videos, use your web browser to access the Customer Community at the following link: products_and_solutions/storage_management_software/oncommand-insight/oncommand-insightvideos/content You need a user name and password for some features of this community. To obtain them, click the Join Now link. The following video topics and more are included in the Community: How to tell OnCommand Insight about your tiering How to identify over utilized disks in OnCommand Insight How to view orphaned storage How to set thresholds for storage efficiency How to identify candidates for tiering How to identify candidates for host virtualization How to group violations How to set business entity annotations Accessing OnCommand Insight online help OnCommand Insight includes quick access to how-to information, descriptions of fields, vendorspecific data source information, explanations of reports, and a glossary of terms in its online help. Within the online help, you can search for information by using the index or searching for specific text. About this task You can access the following types of online information: All product documentation is available in the online help. Context-specific help: Displays information about the view or dialog box that you are viewing. Vendor-specific data source help: While you are adding or editing data sources, after you select the vendor.

13 Welcome to OnCommand Insight 13 Step 1. Do one of the following: Option To display the OnCommand Insight documentation as online help Description Select Help > Help Topics. To display a description of your current view or a dialog box (context-specific information) Do one of the following: Click the help icon (question mark) in the view's title bar. Click the Help button that is available on some dialog boxes. Select Help > More info for... The OnCommand Insight online help opens to a topic that relates to the current view. Press F1 to get help on the current view or dialog. To display vendor-specific data source help Do the following: a. From the Client, select Administration > Data Sources. b. Add or edit a data source. c. As soon as you select a vendor, the next page in the wizard is displayed. On that page, click Help. The Help explains how to enter data source information for that vendor. OnCommand Insight on the web For comprehensive, up-to-date information about OnCommand Insight, use these NetApp web site resources. OnCommand Insight product web site at The NetApp Support Site at: support.netapp.com The OnCommand Insight data source Interoperability Matrix at support.netapp.com/now/ products/interoperability. OnCommand Insight product documentation The OnCommand Insight products are accompanied by a set of guides. You can access the following documents from the NetApp Support Site at support.netapp.com/ documentation/productsatoz/index.html. OnCommand Insight Getting Started Guide Helps new OnCommand Insight users set up and customize their installed system and begin using it for improved efficiency.

14 14 OnCommand Insight Installation and Administration Guide OnCommand Report Installation and Administration Guide OnCommand Insight Inventory User Guide OnCommand Insight Assurance User Guide OnCommand Insight Performance User Guide OnCommand Insight Planning User Guide Note: Information about OnCommand Insight is available from the OnCommand Insight Client Help menu and from the OnCommand Insight Administration portal. Provides an overview of suite architecture with instructions to get the system up and running, discover the logical and physical storage resources in your storage environment, and perform administrative tasks. Describes the configuration parameters and some installation procedures for data sources used by OnCommand Insight. Provides recommended methods of discovering your storage environment for the OnCommand Insight deployment. Provides information about the tools and features to help you gain visibility into your SAN or NAS inventory environment. The Inventory features are the foundation used by all other products in the OnCommand Insight suite. After looking at the OnCommand Insight Getting Started Guide, use this guide to learn about basic features common across all OnCommand Insight modules. Provides an overview of how to use OnCommand Insight to analyze and validate your storage network environment and to automate monitoring of operations, as well as procedures for making safe changes without disrupting availability. Provides an overview of how to use OnCommand Insight to reclaim underutilized resources, manage tiers, identify multipath risks, and troubleshoot ongoing performance bottlenecks. Provides an overview of how to use OnCommand Insight to enable educated capacity management decisions by managing the end-to-end resource order and allocation process. Describes how system administrators can communicate storage capacity requirements to SAN managers using OnCommand Insight Connect Applications web access instead of the full OnCommand Insight feature set. OnCommand Reporting Guide Describes reports from the centralized reports portal that support viewing critical inventory and capacity-related information from the data warehouse. Describes the metadata model upon which OnCommand Insight reports are based. Information in this guide is also available from the OnCommand Insight Data Warehouse portal and in the OnCommand Insight Reporting Connection.

15 Welcome to OnCommand Insight 15 OnCommand Insight Data Warehouse Administration Guide OnCommand Insight Connect API Reference Note: This guide differs from the OnCommand Report User Guide, which describes how to use OnCommand Report. Describes a data warehouse repository that consolidates multiple OnCommand Insight operational databases in an easy-to-query format. Provides an overview of how to use the API interface to enable integration with other applications, such as reporting and monitoring systems. Helps customers and Independent Software Vendors (ISVs) to develop applications using the OnCommand Insight API interface.

16 16 OnCommand Insight Installation and Administration Guide Planning the deployment To ensure a successful deployment, you need to perform several steps before you can install OnCommand Insight. About this task Planning your deployment involves reviewing the following OnCommand Insight items: Architectural information Server requirements Acquisition Unit server requirements Client requirements Data Warehouse and Reporting server requirements Web browser requirements OnCommand Insight architecture The OnCommand Insight Server is the main repository and analysis component. You access and manage OnCommand Insight using the Client and generate reports from the Reporting portal. The OnCommand Insight architecture is shown in this illustration and comprised of the following main components.

17 Planning the deployment 17 OnCommand Insight Server OnCommand Insight Acquisition Unit OnCommand Insight Administration portal OnCommand Insight Client OnCommand Insight Data Warehouse and Reporting The OnCommand Insight main repository and analysis component. The Server provides access to the storage information and policies and provides impact analysis and simulation capabilities. The Server receives regular updates regarding environment changes from the Local and Remote Acquisition Units that are installed. These updates are passed through a secure communications channel and stored in the database. The OnCommand Insight acquisition component, which communicates with devices and provides device information to the OnCommand Insight Server. There are two types of Acquisition units: Local Acquisition Unit (LAU) is installed with the OnCommand Insight Server. Remote Acquisition Unit (RAU) can be optionally installed on one or more remote servers, as required. The web-based interface that you can use to manage licenses, manage user accounts, perform backups, and connect to the OnCommand Insight Client. The OnCommand Insight Java-based user interface, which provides access to the various OnCommand Insight features through a graphical user interface. The OnCommand Insight Client runs on a PC that is compatible with the Client hardware and software requirements. The repository and report engine used to write custom reports utilizing available OnCommand Insight data. This component is installed on a separate PC that is compatible with the OnCommand Insight hardware and software requirements. IBM supplies the Query Studio, Report Studio, and Business Insight reporting utilities that are distributed with OnCommand Insight. Note: Data Warehouse and Reporting should not be installed on the same computer as the OnCommand Insight Server. Example of a common OnCommand Insight implementation This example of a common OnCommand Insight implementation shows four data centers being managed centrally. The illustration shows the OnCommand Insight Server communication with other components: Local Acquisition Unit communicates with the main data center and two local data centers. Remote Acquisition Unit communicates with a remote data center. While communication flows in both directions, the arrows indicate the direction in which communication is initiated.

18 18 OnCommand Insight Installation and Administration Guide Main Data Center HTTPS Remote Acquisition Unit Remote Data Center C OnCommand Insight HTTPS Local Acquisition Unit Client GUI Direct Acquisition Direct Acquisition Local Data Center A Local Data Center B OnCommand Insight Server requirements The Server, a computer running Microsoft Windows, requires a specific operating system, minimum amounts of memory, minimum CPU cores, and minimum disk space. Best Practice: A dedicated server is recommended. Do not install OnCommand Insight on a server with other applications using MySQL. Both physical and virtual servers are supported, provided the product requirements are met. You must have local administrator permissions to install the OnCommand Insight Server software. The dedicated OnCommand Insight Server must meet your company's security standards and include these components: The SQL database that stores information about your SAN configuration The impact analysis and simulation engine The Local Acquisition Unit

19 Planning the deployment 19 Sizing for OnCommand Insight has multiple dependencies, such as data source type and data source size. Consequently, all sizing recommendations should be discussed and validated with a NetApp representative. Component Minimum requirement Recommended practice Operating System Virtual Machine (VM) Memory and CPU Computer running Microsoft Windows Server 2003, 2008 R1, or 2008 R2 with the latest service pack. This component can also be run on a Virtual Machine provided your environment allows for RAM reservations. Recommendations are based on number of ports: For 500 3,000 ports, a minimum of 4 GB of RAM is recommended with 2 CPU cores without OnCommand Insight Perform or 4 CPU cores with OnCommand Insight Perform. For more than 3,000 ports, a minimum of 8 GB of RAM with 4 CPU cores without OnCommand Insight Perform or 8 CPU cores with OnCommand Insight Perform and array performance enabled. A dedicated server is recommended. Run on a dedicated server with no other management utilities other than those required for your Windows environment. These are general guidelines. For specific guidance for your environment, contact your Sales Engineer. For 500 to 3,000 ports, 8 GB of RAM is recommended with 2 CPU cores or 4 CPU cores with OnCommand Insight Perform. For > 3,000 ports and < 7,500 ports, 16 GB of RAM is recommended with 4 CPU cores or 8 CPU cores with OnCommand Insight Perform and array performance enabled. For >7,500 and < 10,000 ports, 16 GB RAM is recommended with 8 CPU cores or 16 CPU cores with OnCommand Insight Perform and array performance enabled. For >10,000 ports, contact your Sales Engineer.

20 20 OnCommand Insight Installation and Administration Guide Component Minimum requirement Recommended practice Available Disk Space Network Based on the available free space: 40 GB free space on the destination drive for OnCommand Insight without OnCommand Insight Perform array performance data or 80 GB with array performance data. 20 GB (additional) free space on the C: (or separate logical) system drive, if different from destination drive. Before installing OnCommand Insight, clear appropriate space on the system drive to accommodate this requirement. Ethernet connection and ports: 100 Mbps / 1 Gbps Ethernet connection with dedicated (static) IP address and IP connectivity to all components in the SAN, including FC devices and Remote Acquisition Units. Port requirements for the OnCommand Insight Server Process are 80, 443, , 3873, 8083, , 5445, 5455, , 5500, 5501 Port requirements for the Acquisition Process: and 5679 Port requirement for MySQL is 3306 The OnCommand Insight software and the operating system should be installed on separate physical disks. 40 GB free space on the destination drive for OnCommand Insight without OnCommand Insight Perform array performance data or 80 GB with array performance data. 20 GB (additional) free space on the C: (or separate logical) system drive, if different from destination drive. Before installing OnCommand Insight, clear appropriate space on the system drive to accommodate this requirement.

21 Planning the deployment 21 Component Minimum requirement Recommended practice Permissions Remote Connectivity Accessibility Virus Scan Local Administrator permissions are required on the OnCommand Insight Server. Internet connectivity to allow Webex access and/or a remote desktop connection to facilitate installation and postinstallation support. HTTP, HTTPS or FTP access to the internet is highly recommended. The entire OnCommand Insight directory should be excluded from any virus scan applications. Related tasks Installing the OnCommand Insight Server on page 28 Remote Acquisition Unit server requirements Installation of a Remote Acquisition Unit (RAU) is required to acquire information from SAN devices that are behind a firewall, at a remote site, on a private network, or in different network segments. The RAU has operating system, CPU, memory, and disk space requirements. Component Minimum requirement Recommended practice Operating System Computer running Microsoft Windows 2003, 2008 R1, or 2008 R2 with the latest service pack. A dedicated server is recommended. CPU 2 CPU cores 2 CPU cores Memory 4 GB RAM 8 GB RAM Available Disk Space 20 GB This server should be secured using your company's security standards and technology before performing the OnCommand Insight installation.

22 22 OnCommand Insight Installation and Administration Guide Component Minimum requirement Recommended practice Network Permissions Virus Scan 100 Mbps /1 Gbps Ethernet connection, static IP address, IP connectivity to all FC devices, and a required port to the OnCommand Insight server (80 or 443). Local Administrator permissions are required on the RAU server. The entire OnCommand Insight directory should be excluded from any virus scan applications. Related tasks Installing a Remote Acquisition Unit (RAU) on page 61 OnCommand Insight Client requirements The OnCommand Insight Client operates in a Java run-time environment on your computer. The Client requires a specific operating system, CPU, and memory. When you access the OnCommand Insight Client, if the Java run-time environment (JRE) is not installed on your computer, the portal displays a message indicating that you need to install it. The Client provides a Java link that directs you to a Windows JRE installation. If you are running a different operating system, refer to the Java download site at manual.jsp. If you are running an earlier version of the JRE, NetApp recommends that you upgrade to Java 6.0. The Client offers a link for the Windows JRE version. Component Operating System CPU Memory Requirement Any Java 6 enabled machine. The Java-based OnCommand Insight Client supports Windows, Unix, and Macintosh platforms. Microsoft Windows is recommended. 1.8 GHz or faster. 1 GB or more is recommended. Related tasks Accessing the OnCommand Insight Client on page 51

23 Planning the deployment 23 Data Warehouse and Reporting server requirements The Data Warehouse and the Reporting server must run on a computer that is compatible with established hardware and software requirements. Ensure that Apache web server or reporting software is not already installed on this machine. Data Warehouse is supported only on the Internet Explorer browser. Component Minimum requirement Recommended practice Operating System Virtual Machine (VM) Computer running Microsoft Windows 2003, 2008 R1, or 2008 R2 with the latest service pack. This must be a dedicated server. This component can also be run on a Virtual Machine. Run on a dedicated server. CPU For < 3,000 ports, use 2 CPU core For > 3,000 ports, use 4 CPU core Memory For < 3,000 ports, use 8 GB RAM For > 3,000 ports, use 16 GB RAM Available Disk Space 50 Gb Installation requires 20 GB free on the C: drive. 100 GB Installation requires 20 GB free on the C: drive. Network 100 Mbps or 1 Gbps Ethernet connection Static IP address For the OnCommand Insight DWH server process, the ports are 80, 443, 1098, 1099, 3873, 8083, and For the reporting engine, the ports are 8080, 1527, 9362, 9300, and For MySQL, the port is Virus Scan The entire OnCommand Insight directory should be excluded from any virus scan applications. Related tasks Installing the OnCommand Insight Data Warehouse and Reporting on page 37

24 24 OnCommand Insight Installation and Administration Guide OnCommand Insight browser requirements OnCommand Insight can operate on different browsers. Component Requirement OnCommand Insight Administration portal Mozilla Firefox 3.6 Microsoft Internet Explorer 8 OnCommand Insight Data Warehouse Mozilla Firefox 3.6 Microsoft Internet Explorer 8 OnCommand Insight Reporting Connection Microsoft Internet Explorer 6.0, 6.0 (SP1, SP2), 7.0 Data Source Support Matrix As part of your deployment planning, you should see if devices in your environment can be monitored by OnCommand Insight. To do so, look at the OnCommand Insight Data Support Matrix, which provides details about specific devices and protocols. To see the Data Support Matrix, look at support.netapp.com/now/products/interoperability. Compare your environment with details in the matrix. Device identification and data source planning As part of your deployment planning, you should collect information about the devices in your environment. You need the following software, connectivity, and information about each device in your environment: IP address Login name and password (read-only) Type of access to the device, for example, controller and management station. This should be read-only access. Port connectivity to the device depending on data source port requirements For switches, SNMP read-only community string Vendor access software Any third-party software required on the device, for example, Solutions Enabler. See vendorspecific data source information in the OnCommand Insight Installation and Administration Guide.

25 Planning the deployment 25 Related references Vendor-specific data source reference on page 86 Network traffic generated by OnCommand Insight The network traffic that OnCommand Insight generates, the amount of processed data traversing the network, and the load that OnCommand Insight places on devices differ based on many factors. The traffic, data, and load differ across environments based on the following factors: The raw data Configuration of devices Deployment topology of OnCommand Insight Different inventory and performance data source polling intervals, which can be reduced to allow for slow devices to be discovered or bandwidth to be conserved The raw configuration data that OnCommand Insight collects can vary a lot. The following example illustrates how the configuration data can vary. For example, you might have two arrays each having 1,000 disks: Array 1: Has 1,000 SATA disks all 1 TB in size. All 1,000 disks are in one storage pool, and there are 1,000 LUNs, all presented (mapped and masked) to the same 32 nodes in an ESX cluster. Array 2: Has TB data disks, GB FC disks, and 40 SSD. There are 3 storage pools, but 320 of the FC disks are used in traditional RAID groups. The LUNs carved on the RAID groups use a traditional masking type (symmaskdb), while the thin provisioned, pool-based LUNs use a newer masking type (symaccess). There are 600 LUNs presented to 150 different hosts. There are 200 BCVs, full block replica volumes of 200 of the 600 LUNs. There are also 200 R2 volumes, remote replica volumes of volumes that exist on an array in a different site. These arrays each have 1,000 disks and 1,000 logical volumes. They might be physically identical in the amount of rack space they consume in the data center, and they might even be running the same firmware, but the second array is much more complex in its configuration than the first array. The example illustrates that traffic, data, and load are affected by many configuration factors. OnCommand Insight upgrade prerequisites If you are manually upgrading your deployment to a new OnCommand Insight version, you must first back up OnCommand Insight. If you are upgrading from a 6.2.X version to 6.4 or greater, you must also uninstall your existing version before performing the upgrade. If you are upgrading OnCommand Insight, ensure that you have performed the following tasks: Backed up OnCommand Insight Backed up the Data Warehouse database

26 26 OnCommand Insight Installation and Administration Guide Backed up custom reports and reporting artifacts If you are upgrading from an OnCommand Insight 6.2.X version to 6.4 or greater, you must also uninstall your existing version before performing the upgrade. However, if you are upgrading a 6.3.X version to 6.4, the OnCommand Insight 6.4 upgrade now handles the upgrade process automatically. Related tasks Setting up and running OnCommand Insight backups on page 229 Backing up custom reports and reporting artifacts on page 44 Backing up the Data Warehouse database on page 232 Uninstalling the OnCommand Insight services on page 31 Checking for OnCommand Insight updates on page 55

27 27 OnCommand Insight installation and upgrade instructions Installation requires installing several OnCommand Insight components, including Client and Data Warehouse and Reporting services. The installation includes the following major tasks, each described in this OnCommand Insight Installation and Administration Guide: Downloading the OnCommand Insight installer. Installing OnCommand Insight services. OnCommand Insight services are installed as the OnCommand Insight Server and Data Warehouse (DWH) and Reporting services. The Server and DWH are installed on separate servers. Installing licenses. Optionally, installing DWH. Optionally, installing the vcenter Server plug-in to monitor your virtual machines inside VMware. Optionally, installing a Remote Acquisition Unit (RAU), which acquires information from SAN devices that reside behind a firewall, are located at a remote site, or are on a private network. For upgrades, upgrading OnCommand Insight reports. Configuring OnCommand Insight to acquire information about your environment includes the following major tasks, each described in this OnCommand Insight Installation and Administration Guide: Setting up the acquisition unit communication between OnCommand Insight and storage devices in your environment. Setting up data sources for data acquisition. Monitoring automatic host resolution (AHR). Identifying specific devices. Related concepts Installing OnCommand Insight Server on page 28 Setting up data sources for data acquisition on page 66 Related tasks Installing your OnCommand Insight licenses on page 32 Installing the OnCommand Insight Data Warehouse and Reporting on page 37 Installing the vcenter Server plug-in for OnCommand Insight on page 41 Upgrading OnCommand Insight reports on page 44

28 28 OnCommand Insight Installation and Administration Guide Accessing the OnCommand Insight Client on page 51 Identifying hosts and tapes automatically with Auto Resolution (AR) on page 142 Identifying and managing FC generic devices on page 172 Identifying and managing iscsi sessions and NAS shares on page 190 Downloading the OnCommand Insight installer Download the OnCommand Insight installer from the NetApp Support Site. Before you begin You must have a login to the NetApp Support Site at support.netapp.com. Steps 1. Log in to the server where you want to install OnCommand Insight. 2. Download the installation file from the NetApp Support Site at support.netapp.com. Installing OnCommand Insight Server The OnCommand Insight Server installation is self-contained and runs in a wizard. However, two of the typical OnCommand Insight elements used to operate OnCommand Insight need to be installed separately: OnCommand Insight Remote Acquisition Unit (RAU) OnCommand Insight Server You can install any number of additional RAUs to add remote data centers and private networks to the SAN devices that are managed by OnCommand Insight. Installing the OnCommand Insight Server The OnCommand Insight Server installation runs in a wizard. Before you begin You must have completed all of the installation prerequisites. Steps 1. Log into Windows using an account with administrator privileges. 2. Open Windows Explorer and navigate to the directory where the installation files are located. 3. Double-click the.msi file that you downloaded. 4. Click Next from the first window to continue.

29 5. Read the License Agreement, and click the Accept checkbox and then click Next. 6. In the OnCommand Insight Server option for the installation, expand the list of options for the Server to select one of the following: Will be installed on local hard drive. Entire feature will be installed on local hard drive. Feature will be installed when required. Entire feature will be unavailable. 7. Click on the specific method you want to use to install the OnCommand Insight Server. After you do this, the window closes, and your selection is added to the system. Note: You can click Reset to return values to their default settings. If there is not enough space, OnCommand Insight lists the volumes and tries to determine which drives in your system have the capacity required to install the software. The highlighted volumes do not have enough disk space for the selected OnCommand Insight features. During the installation, there is a 5 GB temporary space requirement on the C: drive. 8. Click OK and Next to continue. OnCommand Insight installation and upgrade instructions Enter Customer Name and Site Name on the Customer Information window. Click Next. Best Practice: Use the customer name as a prefix for the site, for example, NetApp. 10. In the Customer Information: Configure automated support (ASUP) window, select the Database containing the data that you want to upload to ASUP: No database backup Backup without Performance data Backup with Performance data A backup is not sent to ASUP. A backup is made and sent to ASUP, but does not include performance data. A backup includes performance data, but this could generate a huge *.gz file. 11. In Logs, select whether you want no logs, base logs, or extended logs, which contains a data source recording. 12. For the automated support, select which Send Method you want to upload data to ASUP (FTP, HTTP, HTTPS, or ). HTTP is the default. Note: If you select " ," you must configure the server from the OnCommand Insight Administration web portal using the Mail option. To change to HTTP or HTTPS and a proxy, configure the ASUP settings in the OnCommand Insight Administration web portal. 13. In the Configure Server window, select or set the appropriate configuration parameters to configure the OnCommand Insight Server:

30 30 OnCommand Insight Installation and Administration Guide OnCommand Insight Port (HTTP) OnCommand Insight Secured Remote Acquisition Port (HTTPS) Internal Database Port (SQL) Port used by the OnCommand Insight Server to support user Web services, including a portal to launch the client and to perform administration tasks. Change this to an unused port if port 80 is already in use; otherwise leave the default. Port used by Remote Acquisition Units to send SAN change information to the OnCommand Insight Server through a secure channel. Change this setting if a port conflict occurs; otherwise leave the default. You will specify this same port number when configuring RAUs. Port used internally by the PC where the OnCommand Insight Server is running, to serve as an access point to the database. Change this setting if a port conflict occurs; otherwise leave the default. 14. Click Next to open the second Configure OnCommand Insight Reporting window. The default values are displayed in these Data Warehouse and Reporting fields: Reporting HTTP Server Port Reporting Engine Port 8080 is the default is the default. If that port is in use, an error message appears and you can select another port. 15. Click Next. 16. Click Install to proceed. The installation should take approximately 20 minutes, depending on the applications installed. 17. Click Finish to end the installation. Related references OnCommand Insight Server requirements on page 18 Verifying new OnCommand Insight services After a successful installation, you should check for the installed components in the Microsoft Windows services. Steps 1. Navigate to the Microsoft Windows Services window using this path: Start > Control Panel > Performance and Maintenance > Administrative Tools > Services. Alternatively, open the command window ( Start > Run > "cmd") and enter the net start command to obtain a list of services. 2. Check for these OnCommand Insight services: SANscreen Server

31 SANscreen Acq (the acquisition process) MySql (OnCommand Insight SQL database) If these services are not listed, contact technical support. OnCommand Insight installation and upgrade instructions 31 Uninstalling the OnCommand Insight services If you are upgrading a 6.2.X version of OnCommand Insight to the 6.4 version, you must uninstall the older version before installing 6.4. Before you begin If you are performing this operation to upgrade your 6.2.X version to 6.4 or greater, you must first have backed up your current version of the OnCommand Insight database to preserve your OnCommand Insight data. See the backup instructions. Steps 1. Close all OnCommand Insight windows. 2. Stop the OnCommand Insight server by doing one of the following: Select Microsoft Windows Start > All Programs > NetApp OnCommand > Stop OnCommand Insight Server. Open the command window (Start > Run > "cmd") and enter: net stop "SANscreen Server" 3. Open the Windows Control Panel and select Add or Remove Programs. Note: For Windows Server 2008, this is Programs and Features. 4. Select the Remove a Program task. 5. Select the OnCommand Insight <version number> and click Remove to uninstall the server and application. 6. Also in the Add or Remove Programs (or Programs and Features) view, select OnCommand Insight Client and click Remove to delete the OnCommand Insight Client. Logging into the OnCommand Insight Administration portal You can access the OnCommand Insight Administration portal using a web browser. About this task The following table lists the default user name and password. Best Practice: Change these defaults as soon as possible after installation.

32 32 OnCommand Insight Installation and Administration Guide Data Default user name Default password Value admin admin123 If you do not initiate any activity within a time specified in Settings, then five minutes before the end of that interval, a message appears warning that you will be logged out in five minutes if no activity occurs. Steps 1. Do one of the following: If you are accessing the system from the OnCommand Insight Server, enter: If you are accessing the system from any location, enter the following URL: <OnCommand_Insight_Server_hostname>:<OnCommand_Insight_Server_port> The port number is either 80 or 8080, as configured when the Server was installed. It defaults to 80 if you do not specify it in the URL. 2. In the OnCommand Insight Administration portal, click one of the menu options. 3. In the Login window, enter your user name and password and click OK. Installing your OnCommand Insight licenses After you receive the license file from NetApp, use the License Portal to install the licenses. You can import a group of OnCommand Insight product licenses in the license file. Steps 1. In a browser, open the OnCommand Insight administration portal ( index.do or and log into an account that has Administrator privileges. 2. At the bottom of the Main Menu, click the License Portal link.

33 OnCommand Insight installation and upgrade instructions Click the Launch OnCommand Insight License Manager link to open the License Manager window. 4. Click Import. 5. Browse to locate the license file and click OK. 6. Click Done to save and exit this window.

34 34 OnCommand Insight Installation and Administration Guide When you return to the OnCommand Insight Client, you see the licensed products displayed and available for access in the OnCommand Insight launch menu. After you finish After installing the licenses, you should perform these tasks: Configure data sources. Create OnCommand Insight user accounts. Related concepts OnCommand Insight licenses on page 36 Missing licenses on page 49 Related tasks Accessing the OnCommand Insight Client on page 51 Directly importing OnCommand Insight licenses on page 34 Replacing expired licenses on page 35 Directly importing OnCommand Insight licenses The superuser administrator can directly import the OnCommand Insight licenses. After receiving the license file from NetApp, use the License Portal to install the licenses. Steps 1. Navigate to the OnCommand Insight administration portal ( or and log in using the superuser administrator (oadmin) privileges. 2. Click the License Portal link at the bottom of the Main Menu. The Directly import license file option is only available to the superuser administrator.

35 OnCommand Insight installation and upgrade instructions To import a group of licenses stored in a.txt or.lcn file, click Browse and select the license file to display in the Directly import license file field. 4. Click Import. Replacing expired licenses If your OnCommand Insight license has expired, you can add one or more replacement licenses. Steps 1. Navigate to the OnCommand Insight administration portal ( or and log in using the Administrator privileges. 2. Click the License Portal link at the bottom of the Main Menu. 3. Click the Launch OnCommand Insight License Manager link. 4. Click Add and type the new license key for the product with the expired license. Click OK. 5. Click Commit Changes. You can add another license key. 6. Click Done to close the License Portal.

36 36 OnCommand Insight Installation and Administration Guide OnCommand Insight licenses OnCommand Insight operates with licenses that enable specific features on the OnCommand Insight Server. The OnCommand Insight licenses support different functionality. Assure Perform Plan Reporting Supports Inventory and Assurance (policies and violations) functionality. Supports Performance management. Supports the Planning functions. Supports report generation. Licenses are based on the following issues: By terabyte of managed capacity By time (or perpetual) By product (Assure, Perform, and Plan), which can be purchased separately. Note: To learn more about licensing, watch a video on the NetApp Customer Community: communities.netapp.com/community/products_and_solutions/storage_management_software/ oncommand-insight/oncommand-insight-videos/content You need a user name and password for some features of this community. To obtain them, click the Join Now link. License keys are a set of unique strings that are generated for each customer. Obtain them from your OnCommand Insight representative. There are two versions of the license manager, one that serves as the Java web-start application and one that serves as an interactive web interface. The display of menu options depends on installed licenses: License Assurance menu Planning menu Perform only Changes Switch Port Performance Alerts Port Balance Violations Disk Utilization Violations Does not appear Plan only Reservation Violations Requests Pending Tasks

37 OnCommand Insight installation and upgrade instructions 37 Related tasks Installing your OnCommand Insight licenses on page 32 Directly importing OnCommand Insight licenses on page 34 Restarting the OnCommand Insight Server using a command window After updating components, you must restart the OnCommand Insight Server. You do this by starting the SANscreen Server service. You can do this by using the command window or the Control Panel. Steps 1. To open the command window, select Start > Run > "cmd". 2. To obtain a list of services, enter net start 3. To start the service, enter: net start sanscreen server Restarting the OnCommand Insight Server using the Control Panel After updating components, you must restart the OnCommand Insight Server. You do this by starting the SANscreen Server service. You can do this by using the command window or the Control Panel. Steps 1. Navigate to the Microsoft Windows Services window using this path: Start > Control Panel > Performance and Maintenance > Administrative Tools > Services. 2. Restart the OnCommand Insight Server by restarting this service (which starts the SANscreen acquisition process as well): SANscreen Server. Installing the OnCommand Insight Data Warehouse and Reporting The installation is self-contained and includes the elements required to run and operate OnCommand Insight Data Warehouse (DWH) and the Reporting utilities supplied by IBM. Before you begin Before installing the OnCommand Insight Data Warehouse and Reporting, you need the Data Warehouse and Reporting installation file, the required hardware and software environment, and a

38 38 OnCommand Insight Installation and Administration Guide deployment plan for the hardware, network, and OnCommand Insight Data Warehouse and Reporting configurations. If you are upgrading, you should have backed up all of your OnCommand Insight reports. About this task To find details about the Reporting portal features, such as how to configure SMTP services, refer to the IBM Cognos documentation at Steps 1. Log into Windows using an account with administrator privileges. 2. Open Windows Explorer; then open the directory where the installation files are located. 3. Double-click SANscreenDWH{arch} <version><build>.msi. 4. Click Next. 5. In the next window, check the Accept License Agreement checkbox. 6. Click Next. 7. Select OnCommand Insight Reporting option. By default, it is installed on the local hard drive. To change this default, click the icon next to OnCommand Insight Reporting and select one of the following options: Will be installed on local hard drive. Entire feature will be installed on local hard drive. Feature will be installed when required. Entire feature will be unavailable. 8. Click on the specific method you want to use to install the OnCommand Insight Data Warehouse and Reporting. After you do this, the window closes, and your selection is added to the system. 9. To test your system, click Disk Usage. OnCommand Insight Data Warehouse and the Reporting utilities together require 1,104 MB for installation. OnCommand Insight tries to determine which drives in your system have the capacity required to install the software. The highlighted volumes do not have enough disk space for the OnCommand Insight Data Warehouse and Reporting. Click OK if you want to return to the previous window. The default location for installation is shown in the previous window as C: \Program Files\SANscreen. 10. Click Next. 11. In the Customer Information window, enter a Customer Name and a Site Name. Best Practice: Use the customer name (for example, "NetApp") as a prefix for the site. 12. Click Next.

39 OnCommand Insight installation and upgrade instructions In the Configure Data Warehouse and Reporting window, select or set the appropriate configuration parameters. Protocol OnCommand Insight DWH Portal Port (HTTP) Internal Database Port (SQL) Database Size (MB) Configures Port used by the OnCommand Insight Data Warehouse (DWH) to support user Web services including a portal to launch the Reporting engine and to perform administration tasks. Change this to 8080 if port 80 is already in use or 8181 if port 8080 is also in use. Otherwise, leave the default. Port used internally by the PC where the OnCommand Insight DWH is running, to serve as an access point to the database. Change this setting if a port conflict occurs; otherwise leave the default. Initial size of the OnCommand Insight SQL database. The default size (2,000 MB) can hold a 200-host SAN for more than ten years. The database allocates additional space dynamically, as needed. 14. Click Next to open the second Configure OnCommand Insight Data Warehouse window. The default values are displayed in these data warehouse and reporting fields: Reporting HTTP Server Port is the default. Reporting Engine Port is the default. If that port is in use, an error message displays, and you can select another port. MySQL Memory Allocation 15. Click Next. 16. Click Install to proceed with the installation of the OnCommand Insight Data Warehouse and Reporting. The installation should take approximately 40 minutes, depending on the selections made. 17. Click Finish to finish the installation. Related references Data Warehouse and Reporting server requirements on page 23 Locating IBM Cognos documentation For basic information such as how to start and stop the Reporting portal software, see the IBM Cognos documentation installed with the product. You can search in a web browser for information about any of the IBM Cognos reporting products, such as Query Studio, Report Studio, Business

40 40 OnCommand Insight Installation and Administration Guide Insight, or Business Insight Advanced on the IBM website in the Information Centers for those software products. Steps 1. To locate the IBM Cognos documentation installed with OnCommand Insight, navigate to this directory. <install_dir>\cognos\c10_64\webcontent\documentation\help_docs.html 2. You can also display topics describing individual IBM Cognos windows used in the OnCommand Insight Reporting Portal. Click the? icon on the window toolbar. Verifying the Data Warehouse and Reporting installation After a successful OnCommand Insight Data Warehouse installation, check to be certain that all of the DWH and Reporting services are available in your Microsoft Windows services. Steps 1. From the Windows Start menu, open this utility: Control Panel > Performance and Maintenance > Administrative Tools > Services 2. Check the list of services for these entries: SANscreen Server - The OnCommand Insight DWH server MySQL - OnCommand Insight's SQL database IBM Cognos 8 IBM Cognos Content Database Apache 2.2 Uninstalling Data Warehouse and Reporting You can uninstall Data Warehouse and Reporting if needed or if you are upgrading. Before you begin If you made changes to reports you want to keep, it is critical that you have created a backup before you uninstall OnCommand Insight. About this task Uninstalling the OnCommand Insight Data Warehouse and Reporting permanently deletes all previously collected data and will remove all reports including any newly created or edited reports. Steps 1. Back up the current version of the OnCommand Insight Data Warehouse (DWH) database. 2. Close all of the OnCommand Insight windows.

41 3. Stop the OnCommand Insight DWH. From a command prompt, type: net stop "IBM Cognos 8" net stop "IBM Cognos Content Database" net stop "MySQL" 4. Open the Add or Remove Programs feature from the Control Panel. Select the OnCommand Insight application for removal. 5. Click Remove. OnCommand Insight installation and upgrade instructions 41 Installing the vcenter Server plug-in for OnCommand Insight OnCommand Insight provides the vcenter Server (formerly VMware VirtualCenter) plug-in to monitor your VM environment. Register this OnCommand Insight plug-in within the vcenter Server and install the necessary OnCommand Insight licenses to supply the monitoring data. Before you begin To install the vcenter Server plug-in, you must register it in the vcenter Server. Without registration, the vcenter Plug-in will not work on vcenter Infrastructure Clients (VI Clients). The vcenter plug-in can be registered in vcenter (not the ESX) version 2.5 and up. Operation of the vcenter Server plug-in requires the OnCommand Insight license. You also need the following OnCommand Insight licenses to provide additional data in the OnCommand Insight tab in the vcenter Infrastructure Client: The OnCommand Insight Assure license enables violations to be displayed. The OnCommand Insight Perform license enables the performance section to be displayed in the Path details view. About this task One OnCommand Insight server can register a plug-in within several vcenter Server systems. The Virtual Infrastructure Client of each vcenter displays the relevant data from OnCommand Insight through the OnCommand Insight plug-in tab and in the Reports link. Installing the vcenter Server plug-in Register the vcenter Server plug-in using your administrator credentials through the previously installed OnCommand Insight Client. Steps 1. Open the OnCommand Insight Client. 2. From the Main Menu, click the Insight Connect Applications link.

42 42 OnCommand Insight Installation and Administration Guide 3. Select vcenter Server Plug-in Registration. The login view opens if you are not already logged in. 4. Enter your username and password. You must use your OnCommand Insight Administrator credentials. 5. In the Register OnCommand Insight plugin with vcenter window, enter the vcenter Host address. This can be either the IP address or the host name that can be resolved from the OnCommand Insight machine. If the vcenter is on a different domain, enter in the fully qualified name of the server when registering the vcenter plug-in. Note: Make sure that vcenter version 2.5 or above is installed on the host specified in the first field. 6. Enter the User Name and Password into the appropriate fields. The user should have "Extension.Register" or "Extension.Update" privileges. 7. Click Register. The vcenter Server plug-in is registered or updated (if it is already registered) in the vcenter. Result After the vcenter Server plug-in is successfully registered, you are notified, and the vcenter then creates the OnCommand Insight tab on the Virtual Infrastructure Client. Related tasks Accessing the OnCommand Insight Client on page 51 Configuring VM reports You must configure the reports to access the VM data from the VMware vcenter. Before you begin The OnCommand Insight reporting feature must be installed before it can be configured to produce the VM reports. Steps 1. Open the OnCommand Insight Client. 2. From the Main Menu, click the Insight Connect Applications link. 3. Click the vcenter Server Plug-in Reports Configuration link. 4. The login view opens if you are not already logged in. Enter your username and password. You must use your OnCommand Insight Administrator credentials.

43 A summary of each type of report that has been configured displays. The Reporting Engine Address is "Not Configured," and the default VM Storage Utilization report is listed as the only report, indicating that the OnCommand Insight reporting feature has been installed. 5. Click the Edit link to begin the configuration process. OnCommand Insight installation and upgrade instructions Enter the IP address of the OnCommand Insight Reporting Engine, for example, Enter the HTTP server port of the OnCommand Insight Reporting Engine (usually 8080). 8. Click Save. The VM reports are configured and the address and port information appears in the report URLs. Adding VM reports After configuring the vcenter Server VM reports, you might want to add more reports. Steps 1. Open the OnCommand Insight Client. 2. From the Main Menu, click the Insight Connect Applications link. 3. Click the VirtualCenter Server Plug-in Reports Configuration link. You might be asked to log in if you are not already logged in. 4. Click New. 5. In the Edit Report view, enter the Name of the report you want, and the Path of the report (in the OnCommand Insight reporting). Also provide a description of the report functionality. 6. Click Save. The report appears in the Configuration view.

44 44 OnCommand Insight Installation and Administration Guide Removing the vcenter plug-in registration If you want to remove the OnCommand Insight vcenter plug-in, use the unregister process. In this context, unregistering is the functional equivalent of removal and uninstallation. Steps 1. Open the OnCommand Insight Client. 2. From the Main Menu, click the Insight Connect Applications link. 3. Click vcenter Server Plug-in Registration. 4. Click Unregister to uninstall the OnCommand Insight vcenter plug-in from the vcenter Server. Upgrading OnCommand Insight reports Upgrading OnCommand Insight reports in the Reporting portal requires the following general steps. Before you begin To determine the schema changes that affect custom reports, you should review the Release Notes. Steps 1. Backup the report artifacts. 2. Install the new OnCommand Insight version. 3. Restore your report artifacts. 4. Restore your report tabs to the pre-upgrade version. 5. Upgrade pre-upgrade reports with embedded SQL for 6.x (if necessary). 6. Stop and restart OnCommand Insight reporting. Backing up custom reports and reporting artifacts If you created custom reports or you made changes to the reports in your current version of the Reporting Connection and you want to upgrade to a newer version, you need to back up your reports and reporting artifacts and restore them after the upgrade installation. About this task If you made changes to the predesigned reports, the best practice is to create your own copy in a separate folder from the predesigned ones. That way, when you update the predesigned artifacts, you will not overwrite your changes. Two folders exist under each package:

45 CustomerDashboards - Use this to store your dashboards. CustomerReports - Use this to store your reports. OnCommand Insight installation and upgrade instructions 45 If you have reports in the My Folders area, you should copy them to the CustomerReports folders so that they are not lost. In addition to a manual backup that you can perform at any time, Data Warehouse creates a daily backup (generated each day to a file called DailyBackup.zip) that includes the report definitions. The daily backup includes the top folders, CustomerReports folders, and packages that were shipped with the product. The My Folders directory and directories that you create outside the product's top folders are not included in the Cognos backup. Restoring and upgrading reports after upgrading from OnCommand Insight versions before 6.3 After performing the backup procedure in your OnCommand Insight version prior to 6.3, install the new version and then execute the following steps to restore your reporting artifacts. Steps 1. To start to restore old Reporting artifacts, copy the Export Backup.zip file you created when you executed the steps in the "Backing up report artifacts" to the <install>\cognos \c10_64\deployment directory. 2. Open a browser and go to for the server and port you used during installation, for example 3. Log in using the user name admin and the password admin123. Click Home. 4. On the Home portal page, a Launch link appears in the toolbar in the header. Click Launch > Reporting Administration. 5. Click the Configuration tab. Due to changes in the data model, the reports in the old packages may not run and need to be upgraded. 6. Click Content Administration. 7. Click the New Import button. 8. Make sure that archive you copied to the deployment directory is selected (for example, backup6.0.zip ) and click Next. 9. If you entered a password to protect the archive, enter the password and click OK. 10. Change the name Export... to Import Backup and click Next. 11. Click on the pencil icon next to each package name and enter a new target name if necessary. For example, add a _original suffix to the existing name. Then click OK. 12. After you rename the target package names for all packages, select all blue folders and click Next to continue.

46 46 OnCommand Insight Installation and Administration Guide 13. Accept all default values until you reach the Finish button. 14. Click Finish. Click Run. 15. Check the View the details of this import after closing this dialog checkbox. Click OK. 16. Click the Refresh link in the top right of the page until the Status text indicates that the job is complete. 17. Click Close. When completed, two sets of packages appear in the Public Folders tab. For example, one with a 6.x suffix (for the newer version) and one with a _original (or whatever you entered during the backup/restore procedure) suffix which will contain your old reports. Due to changes in the data model, the reports in the old packages may not run and will have to be upgraded. Your portal tabs now point to the 6.x version of the portal pages. Restoring the portal tabs To restore the reporting portal tabs to the previous version, you can remove the existing tabs and then add the 6.x portal tabs. Steps 1. Because the old and new tab names are the same, remove the existing tabs first to avoid confusion. 2. Open My Preferences in the drop-down on the toolbar on the right. 3. Click Portal Tabs. 4. Check the check boxes next to the existing portal tabs that you want to replace. 5. Click the Remove link to remove the portal tabs. 6. Click the Add link. 7. Click on the links on the left side, beginning with Public Folders until you arrive at the portal pages you want to add, for example, Public Folders > Inventory 6.x > Dashboards. 8. Check the dashboards that you want to add. 9. Click the green right arrow in the middle of the page to add those portal pages to the right side. Click OK. 10. Repeat Steps 6 9 and navigate to the Dashboards folder of the other packages to add their dashboards as well. 11. Click OK to add the portal tabs to your user interface. Upgrading SQL-based reports In OnCommand Insight 6.x versions, the IBM reporting engine was upgraded to better support MySQL and improve reporting performance. If you created customized reports with embedded SQL

47 OnCommand Insight installation and upgrade instructions 47 in an earlier OnCommand Insight version, you need to upgrade those reports manually using this procedure. About this task You must follow these steps in order to make the necessary changes. Steps 1. Open the customized report in Report Studio. 2. Move the pointer over the "Query Explorer" icon in the center of the editor. 3. Click Queries. "Queries" opens. If any of the Query Subjects have SQL nodes, convert those reports to support the upgraded reporting software version. 4. To copy the existing SQL, follow these steps and refer to the illustration below: a) Click the SQL node. b) In the Properties pane, note the "Name" of the SQL node. "Report SQL" is the Name in this example. c) Note the "Data Source" in the Properties. In the example, the Data Source is "dwh_inventory." d) Double-click the SQL node to open a dialog box showing the SQL and copy the entire SQL statement to the clipboard. Click Cancel. 1 2 In this illustration: #1 = Take note of the Name. #2 = Take note of the Data Source value. 5. With the SQL node selected, press Delete to remove the node from the report.

48 48 OnCommand Insight Installation and Administration Guide 6. To create a new SQL node for this report, drag and drop "SQL" from the Insertable Objects pane to the right of the Query Subject, in this example "Report Query." Be sure to release the mouse button when the "I" beam is to the right of the Query Subject. Your new SQL node should resemble this example. 7. Click the new SQL node. 8. In the Properties pane, enter the name you noted in step 4b in the "Name" property. 9. Enter the data source value you noted in step 4c in the Data Source property. 10. Double-click on the SQL node and paste the SQL syntax you copied to the clipboard in step 4d. Important: If the SQL syntax contains a trailing semi-colon, remove it. 11. Click OK. 12. Double-click the Query Subject next to the SQL node. See the illustration in step Double-click each Data Item. 14. Edit the Data Item Expression to remove any table prefixes or leading periods in the expression In this illustration: #1 = Double-click each Data Item here and edit the expression as described in #3.

49 #2 = If there are any filters here, double-click them and remove the table prefixes or leading periods. #3 = Remove any table prefixes or leading periods for any column references in the expression. (There could be more than one.) In this example, the "Host Name" expression [Report SQL].[host.host_name] was changed to [Report SQL].[host_name]. Important: If the expression did not contain a table name but did have a leading period, remove the leading period. For example, if the expression was [Report SQL].[.host_name], change it to [Report SQL].[host_name]. 15. Double-click each filter. 16. Remove table prefixes or leading periods from the filters. 17. Repeat the above steps for each SQL node in the Queries view. OnCommand Insight installation and upgrade instructions When you complete the changes for all of the SQL nodes, run each changed report to verify it. If there is an error, you receive an exception message indicating a non-existent column or syntax error in your SQL. 19. When each report runs without errors, save it for use with OnCommand Insight version 6.x. Troubleshooting installations OnCommand Insight installations are generally managed through the installation wizards. However, customers might experience problems during upgrades or with conflicts due to computer environments. You should also be certain that you install all of the necessary OnCommand Insight licenses for installing the software. Missing licenses Different licenses are required for different OnCommand Insight functionality. What you see displayed in OnCommand Insight is controlled by your installed licenses. If the OnCommand Insight Assure license is not installed, no violations will appear. If the OnCommand Insight Perform license is not installed, the performance section will not appear in the Path Details View when you open the OnCommand Insight tab in the vcenter client. Related concepts OnCommand Insight licenses on page 36 Related tasks Installing your OnCommand Insight licenses on page 32 Replacing expired licenses on page 35

50 50 OnCommand Insight Installation and Administration Guide Disabling User Account Control (UAC) in Windows 2008 The UAC can impact the installation on Microsoft Windows Disabling it resolves the issue. About this task If you do not disable it, the OnCommand Insight installation in Windows 2008 can fail and show the following message: "There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected." Note: This problem might relate to the installation of the OnCommand Insight Scrub utilities into your environment. See the "Scrubbing data for transfer to support" for more information about this feature. Steps 1. Navigate to the Microsoft Windows Control Panel > User Accounts. 2. Turn "User Account Control" on or off. 3. Uncheck "Use user account control (UAC) to help protect your computer." 4. Reboot your computer. 5. Install OnCommand Insight. 6. After the installation is complete, enable UAC again. Related tasks Scrubbing data for transfer to support on page 242 Backend storage connectivity disruption during upgrades During an upgrade from 5.x to 6.x, frontend to backend storage connectivity is lost temporarily. After the first data source acquisition, frontend storage is reconnected to the backend storage. Until that first data source acquisition, you do not see this connectivity data in the OnCommand Insight Client.

51 51 Accessing storage data in the OnCommand Insight Client The OnCommand Insight Client displays the data about your environment. You can log into the OnCommand Insight Client in different ways. About this task You use the OnCommand Insight Client to display all the data in your environment based on the OnCommand Insight licenses you installed. You can do the following with the OnCommand Insight Client: Work with the different types of views. Identify devices within your environment. View inventory in your environment. View changes in your environment and view their impact on other resources. View paths between hosts and end points in your environment. View the network in topology maps. Generate reports about your environment using pre-defined report templates. Customize the layout of the OnCommand Insight Client. Accessing the OnCommand Insight Client You can access the OnCommand Insight Client using either the Windows Start menu or from a web browser. About this task Use one of the following methods to access the OnCommand Insight Client: If you are using the host where the OnCommand Insight Server is installed, you can use the Windows Start menu to launch the OnCommand Insight Client. If you are accessing OnCommand Insight from a remote machine, you can use your web browser to launch the OnCommand Insight Client. If you are accessing OnCommand Insight from a remote machine using HTTP communication, but a firewall separates the Client from the OnCommand Insight Server, you can use a web browser. The following table lists the default user name and password. Best Practice: Change these defaults as soon as possible after installation.

52 52 OnCommand Insight Installation and Administration Guide Data Default user name Default password Value admin admin123 If you do not initiate any activity within a time as specified in Settings (Tools > Settings), five minutes prior to the expiration of that interval, a message appears warning you that you will be logged out in five minutes if you do not initiate any activity. Related references OnCommand Insight Client requirements on page 22 Accessing the OnCommand Insight Client using Windows Start Launch the OnCommand Insight Client from the same host where the OnCommand Insight Server is installed. Steps 1. From the Windows Start menu, select NetApp OnCommand > OnCommand Insight Client. 2. In the Login window, enter your user name and password and click OK. The OnCommand Insight Client main view appears. Accessing the OnCommand Insight Client using a web browser Use a web browser to launch the OnCommand Insight Client. You can launch the Client from the OnCommand Insight Server or from another location. Before you begin You should use the Java Run-Time Environment (JRE) version 6.0 or greater. The OnCommand Insight Administration portal provides a link to the Windows JRE version. About this task You can access the OnCommand Insight Client using different methods. This procedure explains only one method. Steps 1. Do one of the following: If you are accessing the Client from the OnCommand Insight Server, enter: If you are accessing the Client from any location, enter the following URL:

53 <OnCommand_Insight_Server_hostname>:<OnCommand_Insight_Server_port> The port number is either 80 or 8080, as configured when the Server was installed. It defaults to 80 if you do not specify it in the URL. 2. In the OnCommand Insight main portal, at the top of the Main Menu, click the Client link. 3. Click either the image of the Client or the here link. If the Java Run-Time Environment (JRE) is not installed on your PC, a message appears indicating that you have to install it. The Java link directs you to a Windows JRE installation. If you are running a different operating system, refer to the Java download site at: In Internet Explorer, if the Java security window appears, click Always to open this application when requested. 5. In the Login window, enter your user name and password and click OK. The OnCommand Insight Client main view appears. Accessing storage data in the OnCommand Insight Client 53 Determining your OnCommand Insight license information You can quickly determine the OnCommand Insight licenses that you have installed, identify the unit measured for the license, and identify the number of licensed switch ports that you have towards the OnCommand Insight license. Identifying OnCommand Insight license information You can determine the licenses that you have installed and specific details relating to your licenses using the About OnCommand Insight option on the OnCommand Insight Client Help menu. The About dialog box lists the installed licenses. This information is often needed when contacting NetApp Support for assistance. Steps 1. From the OnCommand Insight Client, select Help > About. 2. Click the License tab. Types of switch ports counted in OnCommand Insight OnCommand Insight counts the several types of ports. OnCommand Insight counts the following types of ports on most Brocade switches: Physical ports Virtual (NPIV) ports (created to support storage virtualizers implemented as software running on the switch and virtual ports created to support NPIV) Inter-Chassis Link (ICL) non-physical ports

54 54 OnCommand Insight Installation and Administration Guide The port count for OnCommand Insight as a complete product is the sum of the number of physical ports, NPIV ports, and ICL ports (as reported by the Brocade CLI). Note: It is possible for Brocade switches to have banks of 16 ICL ports, which are disabled due to Brocade licensing. In these cases, the Brocade CLI reports each unlicensed bank as a single ICL port. These ports are also included in the port count because they are reported by the Brocade CLI. However, if only OnCommand Insight Plan is used, only physical and ICL ports are counted because OnCommand Insight Plan does not count NPIV ports. Identifying the number of licensed switch ports You can quickly identify the number of licensed switch ports that you have from the OnCommand Insight Dashboard or from the navigation pane. There is a distinction between OnCommand Insight and OnCommand Insight Plan in how they display port counts. About this task Both the Dashboard and the navigation pane show the same information about licensed switched ports: Daily SAN Path Violations (0/235) Daily Changes Switch Ports (830) Generic Device Paths Data Sources (1/2) Steps 1. From the OnCommand Insight Client menu, do one of the following: To view the Dashboard as a pop-up window, select View > Show Dashboard. To view the Dashboard in the navigation pane, select Tools > Settings. Select General Preferences. Check Use Navigation pane. 2. Review information on the Dashboard and click any of the links to see more information. Maintaining OnCommand Insight If you are new to OnCommand Insight and have a new system to set up or your system has been operating for some time, you need to take steps to maintain smooth operation of the system. The key maintenance concept is that changes in your environment usually need to be accommodated in the OnCommand Insight system, or data collection might stop or be impaired. Use this checklist to be certain you are maintaining OnCommand Insight in your environment: Check the Last Report Time column in the Storage Arrays main view, Hosts main view, Switches main view, or NPV Switches view. If the last reported data for any device is 72 hours or

55 Accessing storage data in the OnCommand Insight Client 55 older, the data source health for that device is worth investigating. It may have stopped or failed and requires your attention. If you remove a device from your environment, you must also delete the inactive device from OnCommand Insight. This device may be rediscovered and reintroduced into OnCommand Insight unless it has been removed from the management software. If you have upgraded infrastructure software, such as HP CommandView EVA or EMC Solutions Enabler, you might have introduced version mismatches because OnCommand Insight data sources might use CLI client tools from these vendors to speak to these server tools, resulting in a data source failure. Ensure that the appropriate versions of the client tools are installed on the acquisition unit. If data source failures persist, you need to check the NetApp download pages for an OnCommand Insight service pack. Your OnCommand Insight acquisition units need to maintain software version synchronization. If you have Remote Acquisition Units in addition to the local acquisition unit, all units need to run the same OnCommand Insight version. Whenever domain names change or are added, you must reconfigure the Auto Resolution (AR) methods. Related tasks Managing acquisition unit communication with storage devices on page 60 Setting Auto Resolution methods on page 147 Removing an acquisition unit on page 64 Identifying OnCommand Insight license information on page 53 Checking for OnCommand Insight updates OnCommand Insight automatically checks for updates after you log in to the Client; however, you can also check for updates to the OnCommand Insight Client software. Steps 1. To check for updates manually, from the OnCommand Insight Client, select Help > Check for updates. 2. Optional: To disable automatic update checking upon startup, uncheck the option to check for updates during client startup. If no updates are found, a message appears indicating this. However, if updates are detected, the message provides a link to the download. 3. If a newer update is detected and a message appears, click the download here link. 4. In the Download page, click the download. 5. Complete the upgrade.

56 56 OnCommand Insight Installation and Administration Guide Related concepts OnCommand Insight upgrade prerequisites on page 25 OnCommand Insight logs OnCommand Insight supplies many log files to assist the administrator with research and troubleshooting. The available logs are listed in the log directory. You might want to use a log monitoring tool, such as BareTail, to display all of the logs at one time. The log files are located in the c:\<install directory>\sanscreen\jboss\server\onaro\log directory. Creating a Support report for troubleshooting assistance If you encounter an error in any main view, you can have OnCommand Insight create a Support report that collects your data and log files and then places them in a WinZip file, which you can then send to NetApp Support. About this task This feature creates an archive file that contains the following: Your description of the problem Details of the data that you selected All OnCommand Insight log files An OnCommand Insight screen capture

57 Accessing storage data in the OnCommand Insight Client 57 Steps 1. From any main view, right click and select Create Support Report. 2. In the Create Support Report dialog box, enter the subject of the error. 3. In the Description box, enter what you were doing and what data you were accessing. For example, you might want to enter the data in the rows or cells that should display or enter steps needed to reproduce the error. 4. Click Create Report. OnCommand Insight creates a WinZip file (ASUP_<db_name>_<unique_number>.zip) and stores it in the OnCommand Insight download folder and displays it in the default web browser. 5. In your web browser, depending upon your browser's default settings on actions with zip files, choose to save or open the file. After you finish Send the Support archive file to NetApp Support. Related tasks Configuring ASUP on page 240

58 58 OnCommand Insight Installation and Administration Guide Data source setup and device identification OnCommand Insight acquires configuration information from data sources that continuously communicate with devices in your SAN or NAS environment. OnCommand Insight discovers those devices, but must then identify the type of device. Setup involves the following processes: Managing acquisition units for communication to devices Setting up data sources for acquiring device data Setting up automatic host resolution (AHR) Managing identification of devices manually when necessary How OnCommand Insight identifies devices OnCommand Insight acquires configuration information from data sources that continuously communicate with devices in your SAN or NAS environment. OnCommand Insight discovers those devices, but must then identify the type of device. The following summarizes how OnCommand Insight acquires and identifies device information: After installation, you add data sources to OnCommand Insight. A data source is a logical OnCommand Insight component that continuously communicates with one or more devices and provides SAN or NAS configuration information to the OnCommand Insight server. Using the data sources, OnCommand Insight acquires device and configuration information. OnCommand Insight tries to identify the devices as hosts using the assignment process of automatic host resolution (AHR), if it is enabled. Some devices have enough information available for OnCommand Insight to determine the type of device. You might want to use AHR first to identify as many devices as possible automatically, reducing the number that you need to identify manually. Or, you might decide that you prefer to identify devices manually because of your unique environment. OnCommand Insight provides both the automatic and manual identification options. OnCommand Insight acquires information about devices differently depending on the environment: For devices using a Fibre Channel (FC) protocol, OnCommand Insight obtains information from switch devices, which in turn, know about the devices connected to them through their ports. For iscsi and NFS, OnCommand Insight discovers IP addresses from the devices accessing the storage. OnCommand Insight associates the IP with a host. OnCommand Insight can also identify hosts that access NFS shares. Note: You can manually or automatically identify to non-virtual machine hosts. If the virtual machine (VM) is not known to OnCommand Insight it appears as an identified host.

59 However, after the VM data source provides data, OnCommand Insight overrides the identification and creates the VM with the IP. You cannot add an IP to an existing VM. You can identify a share only to a VM that exists in OnCommand Insight. You can manually identify devices that were missed or identified incorrectly. You manually identify devices differently depending on the protocol used: FC: FC-based devices that are not yet identified are referred to as generic devices. You can identify them by using the FC Identify view, selecting a generic device icon in the Topology view, selecting a device in the Generic Devices main view, or by importing a file that contains device information. iscsi and NFS: IP-based devices that cannot be identified are referred to as unknown devices and are identified using the IP Identify view. Even after a device is identified, you still might want to fix other identification issues manually. OnCommand Insight continually tries to resolve any unidentified devices (if AHR is configured to run on every environment change) each time an event such as the following occurs: A new device is reported by the acquisition process. A zone is taken up or down. A member is added to, or removed from, a zone. A host resolution rule is changed. A policy is changed. An annotation is set. You can also schedule OnCommand Insight to run AHR. Data source setup and device identification 59 Related concepts Setting up data sources for data acquisition on page 66 Related tasks Identifying and managing FC generic devices on page 172 Identifying and managing iscsi sessions and NAS shares on page 190 Related references Vendor-specific data source reference on page 86

60 60 OnCommand Insight Installation and Administration Guide Managing acquisition unit communication with storage devices Acquisition units are the OnCommand Insight components that communicate with the storage devices and provide information on the OnCommand Insight Server. About this task Use the acquisition units to monitor the status of your storage environment. There are two types of acquisition units: A Local Acquisition Unit (LAU) communicates with devices, provides device information, and should always be on the same machine as the server. A Remote Acquisition Unit (RAU) acquires information from devices that reside behind a firewall, are located at a remote site, or on a private network. You can install any number of additional RAUs to add remote data centers and private networks to the devices that are managed by OnCommand Insight. Acquisition units and data sources A data source is a logical OnCommand Insight component that continuously communicates with one or more devices or device-management applications providing topology and configuration information to the OnCommand Insight server. Each data source runs within a specific acquisition unit. Depending on the management agent, each data source is capable of reporting on one or more devices, as follows: If the management agent is installed on a device, the data source reports on the device itself, and possibly on its sibling devices (for example, all devices of the same type on the same fabric). If the management agent is installed on separate hardware, such as a management station, the data source reports on all devices managed by that station. There are many different types of data sources, representing the various devices supported by OnCommand Insight. OnCommand Insight uses IP-based communication to gather the data from SAN devices for both: Event driven mode - Used to update the system automatically when device information changes (based on SNMP trap messages). Polling mode - Used to periodically gather data from a device at a user-configured interval. Unsupported device configurations OnCommand Insight does not report changes related to the following device configurations: Arrays with no volumes

61 Arrays with no ports Switch devices with no ports Although a data source might acquire status information from such devices, the information fails the integrity checking done by the acquisition unit and is not forwarded to the OnCommand Insight Server. Installing a Remote Acquisition Unit (RAU) Install one or more RAUs in your OnCommand Insight environment. Data source setup and device identification 61 Before you begin The OnCommand Insight Server must be installed on a separate server before installing a RAU. Before installing, check to be certain that the RAU server has full network access to the devices with which it needs to communicate to acquire the data that it must forward to the server. At least one port needs to be open and available between the RAU server and the OnCommand Insight Server in order to forward change information to the server. If you are unsure about this, validate it by opening a Web browser on the RAU computer and directing it to the OnCommand Insight server: OnCommand Insight Server hostname >:< acquisition_port > The acquisition port defaults to 443, but it may have been changed during the server installation. If the connection is successful, you see a OnCommand Insight response page indicating an open and available port between the RAU and the OnCommand Insight server. Steps 1. Log in to Microsoft Windows using an account with administrator privileges. 2. Open Windows Explorer and navigate to the directory where the RAU installation file is located. 3. Double-click RAU-x{arch}-{version}-{build}.msi to start the installation. 4. Click Next to continue to the window that shows the License Agreement. Read this and accept the terms of the License Agreement and click Next. 5. Select to install the RAU on a local hard drive or the entire feature on a local hard drive. (You can check the Disk Usage link to ensure you have enough space - 116MB is required.) Click Next. 6. In the Configure window, set these parameters that are specific to your site: OnCommand Insight Server Name or Address - hostname or IP address to identify the OnCommand Insight Server. The RAU uses this name/ip to open a communications link with the server. If you specify a hostname, make sure it can be resolved through DNS. Acquisition Unit Name - unique name that identifies the RAU. OnCommand Insight Secured Remote Acquisition Port (HTTPS) - Port used by Remote Acquisition Units to send environment change information to the OnCommand Insight server.

62 62 OnCommand Insight Installation and Administration Guide This setting should match the value entered when installing the OnCommand Insight server and must be the same on all RAUs. 7. Review your selections. Click Back to go back and make changes. Click Next. 8. Click Install to start the installation. Wait for the installation to complete. This should take approximately 5 to 10 minutes. After you finish When the installation is complete, a final window appears. Click the Start Remote Acquisition Service box to start the RAU, and click Finish to end this operation. Related references Remote Acquisition Unit server requirements on page 21 Verifying the remote acquisition unit service After a successful remote acquisition unit (RAU) installation, the OnCommand Insight RAU service should be available in the Microsoft Windows services environment. Steps 1. To verify that the RAU was added to the Windows services, open the Windows Start menu and select the Control Panel > Administrative Tools > Services. 2. Locate the OnCommand Insight Acq - OnCommand Insight's Remote Acquisition Unit (RAU) in the list. Validating the remote acquisition unit installation To validate proper installation of the Remote Acquisition Unit (RAU), use the Acquisition Units main view. Steps 1. Open the OnCommand Insight Client. 2. Select Configuration > Acquisition Units. 3. Verify that the new RAU was registered correctly and that it has an OK status. If it does not, contact the NetApp support team. 4. Define the appropriate data sources to run from the newly installed RAU.

63 Data source setup and device identification 63 Reviewing acquisition information Use the Acquisition Units main view to display a list of the local and remote acquisition units installed in your environment and obtain data on an individual unit's errors, devices, and data sources. Steps 1. Log into OnCommand Insight and open the Client. 2. To review the acquisition data in your environment, select Configuration > Acquisition Units. The main view lists the Local Acquisition Unit, which is installed by default with the OnCommand Insight Server, and any Remote Acquisition Units installed in you environment. 3. Click on an acquisition unit and click the Devices detail view icon in the icon bar at the bottom. 4. In the Devices detail view, look at the "Connected" status of the storage devices. (Green checks in the "Connected" column indicate that the devices are connected to the data sources.) 5. Right-click the acquisition unit in the main view to perform any of these operations: Add another data source to the selected acquisition unit. Clear the data source from the Event Log detail view. Remove an acquisition unit. 6. Select an acquisition unit from the list and click one of these detail view icons to display additional information: Event Log detail view lists any errors that occurred during the latest attempt to run the selected Acquisition Unit. Look at the error message to understand the cause, or contact the NetApp support team for assistance. Data Sources detail view lists the data sources that are assigned to (that is, that run within) the selected Acquisition Unit. The fields listed in the detail pane are the same as those in the Data Sources main view. Result

64 64 OnCommand Insight Installation and Administration Guide Related references Acquisition Units view on page 65 Removing an acquisition unit You can remove the acquisition unit and all data sources assigned to it. However, you need to exercise caution and only remove an acquisition unit after the device corresponding to the data sources is no longer used in the SAN. The Local Acquisition Unit (LAU) should always be on the same machine as the server. If you delete the LAU and then restart the acquisition process, a new LAU entry appears in the acquisition units main view, and you can add data sources to that LAU. About this task You can remove an acquisition unit by using the Acquisition Units main view or by using the Microsoft Windows Control Panel. This procedure describes the former. Steps 1. From the Open menu, select Configuration > Acquisition Units. 2. In the Acquisition Units main view, right-click on the acquisition unit you want to remove. 3. Select Remove Acquisition Unit. 4. In the confirmation box, select Yes to confirm the removal. 5. As necessary, right-click on a device in one of the inventory views and select Delete Inactive Device to remove devices permanently. Result After completing this operation, the following occurs: OnCommand Insight presents any data that was first acquired by the removed data sources as non-current. You will no longer see paths that were created based on the information acquired from the removed data sources. Removing a remote acquisition unit using Microsoft Windows Control Panel To uninstall a remote acquisition unit (RAU), you can use the Microsoft Windows Add or Remove Programs utility. Steps 1. To remove a OnCommand Insight RAU, open the Microsoft Windows Control Panel and select Add or Remove Programs. 2. Select the OnCommand Insight RAU in the list.

65 Data source setup and device identification Click Remove. Acquisition Units reference Acquisition Units have main views of the information with icons to display details about selected items in the main view. Acquisition Units view Acquisition Units view lists the local and remote acquisition units installed in your environment and provides data on devices and data sources and on the errors for individual units. Navigation You can access this main view in one of the following ways: From the OnCommand Insight Open menu, select Configuration > Acquisition Units. Column descriptions If other modules are installed, additional columns might appear. Name IP Status Name assigned to the acquisition unit when it was created. IP address of the acquisition unit. No error messages being received from components indicates that the status is OK. Related tasks Reviewing acquisition information on page 63 Event Log detail view for acquisition units The event log for the acquisition units lists any errors associated with the selected unit. Navigation Open the Acquisition Units view, highlight an acquisition unit, and click the Event Log icon below the view to display the errors for the selected acquisition unit. Column descriptions Each row is an acquisition error for the selected acquisition unit. blank Time Error Error message When the error occurred. Error associated with the unit.

66 66 OnCommand Insight Installation and Administration Guide Setting up data sources for data acquisition Data sources discover SAN information that is used for analysis and validation. In general, most environments require more than one Remote Acquisition Unit (RAU) installed for complete discovery and coverage of all SAN components. Data sources are the most critical component when trying to maintain a OnCommand Insight environment. As the primary source of information for OnCommand Insight, it is imperative to make sure data sources are maintained in a running state. In addition, it is important to know when to add new data sources to the OnCommand Insight environment and at what point you may need to consider expanding your OnCommand Insight environment as it grows. Finally, adding or removing SAN devices for your environment may require data source modification as well. For each data source, the specific requirements to define that data source depend on the vendor and model of the corresponding SAN devices. Before starting the installation, you need network addresses, account information, and passwords for all devices including these: SAN switches Device management stations Storage systems that have IP connectivity (NAS) Storage management stations Host servers running management software for storage devices that do not have IP connectivity (FCAL) To find out vendor-specific data source requirements, see the Data Sources wizard reference in the OnCommand Insight Online Help. Related references Vendor-specific data source reference on page 86 Preparing to add a data source In order to add a data source to OnCommand Insight, you need the device-specific information to facilitate communication among the management agents and the utilities in various SAN devices. You might also need to install the management agents required for communication. Steps 1. For a list of possible data source jar files with the file timestamps, select Help > About in the OnCommand Insight Client, and click the Data Sources tab.

67 Data source setup and device identification 67 Click OK to close this Data Sources window. 2. Make sure that you have the information required to connect to the device (for example, IP address, login user name, login password). 3. Based on the required information, check your environment to be certain you are ready to add the data source. 4. If required for your data source, install the management agent through which the data source communicates with its device(s). 5. Verify that the Local Acquisition Unit and all RAUs are shown in the Acquisition Units main view and that they have an OK status. 6. Refer to the OnCommand Insight documentation for lists of required information for your specific data source. While adding a data source into OnCommand Insight, click Help to display information required in that specific window. After you finish Add your data source. Related references Vendor-specific data source reference on page 86 Importing data sources from a spreadsheet You can import multiple data sources into OnCommand Insight from a spreadsheet. This might be helpful if you already maintain your discovery devices in a spreadsheet. This process adds new data sources, but cannot be used to update existing data sources. About this task OnCommand Insight includes a spreadsheet to help you create data sources. This spreadsheet has the following attributes:

68 68 OnCommand Insight Installation and Administration Guide The spreadsheet can be used with Microsoft Excel 2003 or later. Each tab holds one data source type, for example, Brocade SSH/CLI. Each row represents an instance of a new data source to be created. The spreadsheet includes a macro that creates a new data source in OnCommand Insight. Steps 1. Locate the spreadsheet in the <install_directory>/sanscreen/acq/bin/acqcli/ SiteSurvey_DataSourceImporter_w_Macro.zip. 2. In the spreadsheet, enter data source information in the cells with color. 3. Delete empty rows. 4. From the spreadsheet, run the CreateDataSources macro to create the data sources. 5. When prompted for credentials, enter the OnCommand Insight Server administration user name and password. The results are logged in the acquisition log. 6. A prompt asks if the machine currently running the macro has OnCommand Insight installed. Select one of the following: No: If not, a batch file will be created that must be run on the OnCommand Insight machine. Run this batch file from the install directory. Yes: If OnCommand Insight is installed, no additional steps are required to generate the data source information. 7. To verify the addition of the data sources, from the OnCommand Insight Open menu, select Configuration > Data Sources and review the data sources on the Data Sources view. 8. To troubleshoot the addition of the data sources, check the acquisition (acq.log) log file. Adding a data source When a new switch, storage device, or SAN management tool is added to the SAN environment, you need to add a data source to make its information available for analysis in OnCommand Insight. If the new device will be reported by an existing data source, edit the existing data source. Before you begin Before adding a new data source, read the instructions for preparing to add a data source and the accompanying vendor information. Steps 1. Select Action > Add Data Source to open the wizard that guides you through the process of adding a new data source.

69 2. Enter a Name for the data source that is unique across all Acquisition Units. Choose a name that is easily identified as this data source. The name is comprised of alphanumeric characters (a-z, A-Z, 0-9) and the underscore character ("_"). Note: The field changes to red if the name is not correct. Data source setup and device identification Choose the Acquisition Unit where the data source will run (local specifies the Local Acquisition Unit on the OnCommand Insight server). 4. Choose the Vendor of the device where the management agent is installed. This is the agent from which the data source acquires SAN information. It might be the SAN device itself, or separate hardware, such as a management station. 5. Choose the Model of the device where the management agent is installed. 6. Click Next to open the Information to Collect dialog box. Select the license packages (in this example, Array Performance) the you want to activate for the data source. Each data source has different packages from which it is capable of collecting related information. Each license package that you enable for the data source displays an associated configuration dialog box.

70 70 OnCommand Insight Installation and Administration Guide Note: If Inventory is the only option (there is no Performance option), the Information to Collect dialog box does not appear. 7. Click Next to open the data source Inventory window. Enter the specific information for your OnCommand Insight license package (enabled previously) and the specified type of device. 8. Fill in the inventory information. Note: Invalid field values are highlighted, including required fields that are not yet specified. 9. If you checked Performance license in the Information to Collect window, follow the special instructions for performance information. An additional dialog box might open with performance parameters if you have elected to see that data in the license package. The recommended setting for the virtual machines, storage, application, and switch polling intervals is 300 seconds. 10. Click Finish to activate the data source in your environment. OnCommand Insight activates the Finish button after all required fields are completed correctly. Note: The Import button should be used only under the direction of the NetApp support team. After you complete the configuration, a new row displays in the Data Sources main view. 11. To verify the new data source, allow a reasonable amount of time for the acquisition to complete. Several seconds is generally enough, but some devices may be slow or highly populated and may take several minutes to acquire. 12. Examine either the Data Sources main view or the acquisition event log for successful acquisitions. If the Status field is Acquiring Devices, the acquisition has not yet finished. As necessary, press <F5> to refresh the display. Adding an Array Performance data source Information is required to add HDS and certain EMC data sources for array performance. About this task Your OnCommand Insight license must include Perform. Use these instructions if you want to add data sources for the following equipment: EMC CLARiiON EMC Symmetrix Solutions Enabler (CLI) HDS USP - HiCommand Device Manager Steps 1. Read the instructions for preparing to add and adding data sources and gather the information required for your data source.

71 2. Select Action > Add Data Source. 3. Enter a Name for the HDS or EMC data source that is unique across all Acquisition Units. Choose a name that is easily identified as this data source. The name is comprised of alphanumeric characters (a-z, A-Z, 0-9) and the underscore character ("_"). Note: The field changes to red if the name is not correct. Data source setup and device identification Choose the Acquisition Unit where the EMC or HDS data source will run (local specifies the Local Acquisition Unit on the OnCommand Insight server). 5. Choose the Vendor of the EMC or HDS device where the management agent is installed. This is the agent from which the data source will acquire SAN information. It might be the SAN device itself, or separate hardware, such as a management station. Click Next. 6. Choose the Model of the EMC or HDS device where the management agent is installed. 7. In the Information to Collect window, be certain to check the Array Performance checkbox for the EMC or HDS data sources along with any other licenses that you want to support. Click Next. If you selected another license type, you need to enter inventory information in the next dialog box and click Next.

72 72 OnCommand Insight Installation and Administration Guide Note: This example shows the array performance window for an HDS data source. EMC has a different set of required information. 8. Enter the required Array Performance information for your EMC or HDS data source. Click Finish. After you finish If you have licensed Perform and selected it for collection, allow at least two cycles of data collection to compile the performance data. Configuring the data source for EMC (CLI) or CLARiiON Install the SMI-S provider on each EMC Solutions Enabler host for each data source on which you would like to collect array performance statistics. The EMC Solutions Enabler with SMI-S software must be installed on the acquiring OnCommand Insight host. About this task Best Practice: The acquiring OnCommand Insight host and data source both need the same major and minor versions of the EMC (CLI) software. Steps 1. In the Information to Collect window, be certain to check the Array Performance checkbox when adding an EMC data source. Click Next. 2. If you checked both boxes, the Fibre Channel dialog box displays. Enter the required information and click Next. 3. Enter the required Array Performance information for your EMC (CLI) or CLARiiON data source. OnCommand Insight communicates with the Symmetrix device using the EMC (CLI). 4. Click Finish. Configuring the data source for HDS performance The HDS data source communicates directly with storage arrays. The HDS data source supports the HiCommand Device Manager server, and OnCommand Insight communicates with the HiCommand Device Manager server using the standard HiCommand API. Steps 1. To add the HDS data source, select Action > Add Data Source. If it has been added but not configured, right click the HDS data source in the Data Sources main view and select Action > Edit Data Source to add the required HDS configuration information.

73 2. In the Information to Collect window, check Array Performance for the HDS data source along with any other licenses that you want to support. Click Next. If you selected another license type, you need to enter inventory information in the next dialog box and click Next. 3. Enter the Performance polling interval (in seconds). Data source setup and device identification For the Devices USP/R600 Storage, click Add to display the property group dialog. 5. Enter the first array on which to collect performance data and then repeat for all other arrays. When adding the arrays, it is important that the proper directory is chosen for the location of the.jar files. 6. Click OK for each array. 7. For the SNM2Devices WMS/SMS/AMS Storage, click Add to enter Data Source Property Group information. Click OK. 8. Click Finish. Collecting HDS performance data The HDS (Hitachi Data Systems) Performance Monitor uses the Hitachi Export tool for collecting performance statistics. After collecting the statistics, the data is parsed and processed to fill the Volume Counters and the Disk Counters that are sent to the Server. Before you begin The HDS Performance Monitor License must exist for each array and monitoring must be enabled. This can be done using the Storage Navigator for each array. In addition, the HDS Export Tool must be installed on the acquiring OnCommand Insight host.

74 74 OnCommand Insight Installation and Administration Guide Note: The Export Tool is typically located on a CD that comes packaged with the Service Processor on the HDS USP Array. The Export Tool can also be obtained by contacting HDS support. Steps 1. Install the Hitachi Export Utility on the OnCommand Insight server/acquisition Unit for which the HDS data source is acquiring, and configure the data source to use the Export folder containing the microcode to USP arrays accordingly. Best Practice: When you have many arrays with different microcode versions, install each microcode version in a separate directory named for that version. 2. Check to be certain that the HDS Storage Navigator has a license for HDS Performance Monitor. 3. Enable performance monitoring. Forcing acquisition manually OnCommand Insight automatically forces acquisition when you add or edit a data source. Discovery includes the detection of changes in network topology including the addition or deletion of nodes or interfaces. To force this discovery process manually, you can use this procedure. If the data source is already in an acquisition process, OnCommand Insight ignores the Force Acquisition command. Steps 1. Open the Data Sources main view and check to be certain that the data source is started (status is Running). 2. Right-click the data source in the Data Sources main view. 3. Select Force Acquisition. 4. Click Yes to confirm the operation. Result After forcing acquisition: The event log displays the Acquiring Devices status. Allow a reasonable period of time for an acquisition to complete, and then examine the event log for a successful acquisition. Managing data sources After adding data sources, you might want to start, stop, or edit them. About this task You can do the following tasks related to data sources: Edit a data source.

75 Data source setup and device identification 75 Start a data source. Stop a data source. Remove a data source. Clear the data source event log. Restore a data source. Editing data source parameters The Edit Data Source option lets you examine and modify the parameters for one or more selected data sources. You might do this to correct an error in the original definition or due to a SAN device configuration change (for example, an updated password). However, you cannot modify the device name, vendor, or model. Steps 1. In the Data Sources main view, right-click the data source(s) to edit. 2. Select Edit Data Source. 3. Change the information that was originally entered to define the data source and click Next. 4. Update any parameters as required. If you selected multiple data sources, OnCommand Insight allows you to modify the common attributes. 5. Click Finish. If the data source was Running, it will restart to run with the new parameters. If it is Stopped, it remains inactive. 6. To verify the changes, start the data source if it is not already Running and allow a reasonable period of time for the acquisition to complete. 7. Examine the event log for a successful acquisition. Result Complete data collection takes two cycles of the data collection process. Starting a data source Starting a data source changes its status from Stopped to Running (with the transitional Starting state in between). Steps 1. Right-click the data source in the Data Sources main view. 2. Select Start Data Source. 3. Click Yes to confirm the operation.

76 76 OnCommand Insight Installation and Administration Guide 4. After several seconds the status should change to Running. As necessary, press <F5> to refresh the display. Note: Data sources are in Standby when starting the data source and begin acquiring automatically, based on poll interval. 5. Allow a reasonable period of time for an acquisition to complete and examine the event log for a successful acquisition. After you finish If you want to force acquisition manually on a data source, select the data source, right-click on the data source and select Force Acquisition, and click Yes on the Force Acquisition prompt. Stopping a data source Stopping a data source changes its status from Running to Stopped with the transitional Stopping state. Steps 1. Right-click the data source in the Data Sources main view. 2. Select Stop Data Source. 3. Click Yes to confirm the operation. 4. After several seconds, verify that the status has changed to Stopped. As necessary, press <F5> to refresh the display. Removing a data source This operation removes the data source and all entities it reported on during the most recent acquisition including volumes, zones and connectivity. For this reason, you should use this operation with caution and only after all devices corresponding to the data source are no longer used in the SAN. Before you begin As a rule, if a second data source reports on one or more of the same entities, they are not removed. About this task However, one exception to this rule is that the devices on which the data source reported. That data source is not removed, but are grayed out in the topology view and tables, marking them as inactive. Use the Delete Inactive Device option to remove them, as necessary. Steps 1. Right-click the target data source in the Data Sources main view.

77 2. Stop the data source. 3. Select Remove Data Source from the Action or right-click menu. Data source setup and device identification Click Yes in the confirmation box to confirm removal of the data source. After you confirm the removal, the row corresponding to the data source is dropped from the main view. 5. As necessary, use the Delete Inactive Device feature to remove a device permanently. This feature is available from the appropriate Inventory list such as host inventory and switch inventory. Result OnCommand Insight presents any data that was acquired by the removed data source as non-current. This means that all connectivity, ports, volumes, masking, and zones that were discovered solely by the removed data source will disappear, and the data source Changes detail pane indicates their removal. The corresponding device itself still appears in OnCommand Insight views and in the topology pane, but is grayed out. Clearing the data source event log The data source Event Log shows what acquisitions succeeded and failed. After a few weeks, this information typically has no value. About this task Follow these steps to clear the event log for a selected data source: Steps 1. Right-click the data source in the main view. 2. Select Clear Event Log. OnCommand Insight verifies the request. 3. Click OK. After completing this process, the event log contains only the most recent two entries for the selected data source. Restoring a data source When restoring a database backup, the restored data sources are in a Stopped state allowing the administrator to determine the next action. Before you begin A backup was created for the OnCommand Insight Server when all of the data sources were in a Running state.

78 78 OnCommand Insight Installation and Administration Guide Steps 1. Restore the OnCommand Insight Server backup. 2. From the OnCommand Insight Open menu, select Admin > Data Sources. 3. Check the Recent Status column in the Data Sources main view. The OnCommand Insight Server is stopped and the remaining data sources show that acquisition is not running. After you finish The administrator determines whether to start the server at this point or perform some other operation. Enabling or disabling data collection You can enable or disable data collection for performance and disaster recovery. For example, you might want to temporarily disable the collection of performance statistics that display in OnCommand Insight Perform. You might do this to enhance OnCommand Insight responsiveness and reduce data storage needs, if you do not need this type of data. About this task Temporarily disabling data collection does not impact device identification. Devices are still identified; data collection on those devices is halted for specific types of data collected for performance or disaster recovery data, as you specify. Steps 1. From the Client, select Tools > Settings and select the Data Sources option. 2. To enable data collection, select one or more of the following: the Acquire Inventory data option must be checked. It is checked by default. Acquire Inventory data: You cannot change this. Inventory data is always collected. Acquire Performance data: Check this to collect performance data in addition to inventory data. Data will appear in the views from the Performance menu and the Analyze and Analyze Contention options in the Client. The data is also used in Performance views (available if you have a Perform license). Acquire Disaster Recovery data: Check this to collect disaster recovery data in addition to inventory data. Data will appear in these views: Inventory> Disaster Recovery Paths, Inventory > Replications Dashboard, Assurance > DR Rules, and Assurance > Disaster Recovery Violations. Disaster Recovery is available only if you have a Replication Assurance license. 3. Click OK.

79 Data source setup and device identification 79 Troubleshooting data source activity When troubleshooting failed data source operations, you need to check to be certain that the service is running and that the person performing the operation has administrative privileges. Gathering more data source information You might want to check the NetApp Knowledgebase for additional information about a data source problem. About this task You received an error message when performing a data source operation. Steps 1. Open the Data Sources main view and click the Events icon. 2. In the Events log, click the Package dependency link on the line describing the data source error. 3. In the next dialog box, click the Knowledgebase link. 4. Log into the NetApp Support Site. 5. Examine the Knowledgebase articles listed on the Support page to see if the summary of the solution relates to your data source error.

80 80 OnCommand Insight Installation and Administration Guide 6. Click the link to the article for the solution information. Correcting a failure due to an unauthorized operation You must have administrative privileges to perform data source configuration operations. Steps 1. When you click Finish at the end of a data source operation, you receive an "Unauthorized" error message. 2. Click Login in the error message dialog box. 3. Log in as a user who has administrative privileges. 4. Perform the data source operation again. Researching an acquisition failure If you receive an acquisition unit error message stating that acquisition failed to identify a data source, the OnCommand Insight server might be shut down. Steps 1. To see if the acquisition unit is running, open the Data Sources view and check to be certain that the data source state is Running and the acquisition unit status is OK. If the data source is not running, you need to see if the service is running. 2. To verify that OnCommand Insight service is running, open the Services window on the server where the Acquisition Unit was installed on the OnCommand Insight server for a Local Acquisition Unit. In Windows, open the Start menu and select Control Panel > Administrative Tools > Services.

81 Data source setup and device identification Look for the "SANscreen Acq" service in the list and check the Status to see if it is Started, as in this example. 4. If the "SANscreen Acq" service is not started, click the Restart link. 5. Open the OnCommand Insight Data Sources view and check to be certain that the data source state is Running and the acquisition unit status is OK. Troubleshooting SAN device access and connectivity problems If a data source acquisition fails, it might be a problem with connectivity or access to its SAN devices. Steps 1. If the error message describes connectivity problem, check the SAN device for the following conditions: The device is operational and, therefore, not in maintenance. The device is reachable. Try to ping the device or use the Edit Data Source operation to verify that the connectivity parameters are correct such as the IP address. The device is manageable, for example, by Telnet. 2. If the error message is related to device access such as "Failed to log in to fabric," use the Edit Data Source operation to verify that the user name and password are correct. Data sources reference Data Sources have main views of the information with icons to display details about a selected item in the main view. Data Sources detail view Use this view to identify data sources that provide information about a selected device. Navigation This detail view is available after clicking a device in one of the following views: Switches main view

82 82 OnCommand Insight Installation and Administration Guide Hosts main view Storage Arrays main view Tapes main view Generic Devices main view Zones main view You can access this detail view in one of the following ways. From the OnCommand Insight Client menu, select View > Detail Views > Data Sources. At the bottom of OnCommand Insight Client view, click the Data Sources detail view icon. Column descriptions The Data Sources detail view displays the following information. Data Source Originator Device FC Connected Type Identifier Originator Access Time Originator Update Time Additional Data Sources The data source for the selected resource in the main view. The ID that appears in this field depends on the type of data source originator. For example, if the originator is a switch, the IP of that switch is displayed in this field. A data source can have multiple originators of information and can be of different types. Error messages include the originator information that can be useful when you are examining data source errors. The name of the device. Information about how the data source is connected. If the device has FC ports, this column shows connectivity information. If the device is a NAS device, this column displays an X. The type of device, for example, storage or hosts. The identifier information of the data source. The last time that the data source successfully logged into the device and queried the originator. If the Originator Access time is older than 3 months, the data in the row appears in red. The last time that the server was notified of changes to the originator. The acquisition does not update the server if the data did not change. Additional data sources that report on the same device, if any. Data Sources view Use this view to see a list of all data sources. From this view, you can edit existing data sources or add new ones. Navigation You can access this view:

83 Data source setup and device identification 83 From the OnCommand Insight Open menu, select Configuration > Data Sources. Column descriptions For details about data source setup, device identification and data acquisition, see the OnCommand Insight Installation and Administration Guide. Name IP Poll Interval Vendor Model State Recent Status Acquisition Unit Name assigned to the data source when it was created. IP address where the corresponding management agent is installed. This is the IP address of a SAN device or a device-management station. Interval (in minutes) at which the data source polls its corresponding management agent with these results: Receipt of an SNMP trap restarts the interval counter. The information received is only as current as the polling interval for the management agent with which the data source communicates. Vendor for the device(s) reported by the data source. Model of the device(s). Current state of the data source: Running - The data source is active and running at the configured polling interval. Acquisition not running - The entire acquisition service is down, including all data sources running on the Acquisition Unit. Stopped - The data source has been stopped. Starting - The data source is initializing. This is a temporary state between Stopped and Running. Stopping - The data source is shutting down. This is a temporary state between Running and Stopped. Status of the latest attempt to acquire information from the devices that are polled by this data source: Success - The attempt is complete and was successful. Acquiring devices - The acquisition is in process. Sending data to server - The acquisition results are being forwarded to the server. If 3 out of 5 devices finished successfully, the data source successfully reported only a subset of the components it queried. Name of the Acquisition Unit where this data source is running.

84 84 OnCommand Insight Installation and Administration Guide Acquisition Unit Status Current status of the parent Acquisition Unit: OK - The Acquisition Unit is up and running. error message - There is a problem with the Acquisition Unit, as stated. Event Log detail view for data sources Each row in this view represents one or more acquisition attempts that are grouped according to their status. Event log information changes after a new event. Navigation Open the Data Sources main view, highlight a data source, and click the Event Log icon below the view to display the acquisition history for the selected data source. Column descriptions If the result of the event is the same as the previous events, the Times column is used as a counter and is incremented and the To column is updated with the time of the last completed event. A new event is added when the results of an event do not match the previous result. For example, a successful event after multiple failures creates a new row. For details about data source setup, device identification and data acquisition, see the OnCommand Insight Installation and Administration Guide. Package Name of the OnCommand Insight system component generating the acquisition attempt such as Perform. You can group the events by the Packages. From To Times Status Devices detail view Starting time of the acquisition(s), in mm/ dd/ yy hh: mm format. If the line represents more than one acquisition attempt, this is the starting time of the earliest attempt. Ending time of the acquisition(s), formatted as described above. If the line represents more than one acquisition attempt, this is the ending time of the last attempt. Number of data source acquisitions reported on this line, that is, the number of acquisitions that have the same status. Status of the acquisition is reported on this line with a reference such as Stand-by, Success, or Failed. Error conditions might display a Package dependency link to a possible solution in the NetApp Knowledge Base. Use this view to identify the devices that receive information from a selected data source. Navigation Open the Data Sources main view or the Acquisition Units main view, highlight an item in the main view, and do one of the following:

85 From the OnCommand Insight Client menu, select View > Detail Views > Devices. At the bottom of OnCommand Insight Client view, click the Data Sources detail view icon. This detail view is available only after clicking a resource in a main view. Column descriptions The Devices detail view displays the following information. Data source setup and device identification 85 For details about data source setup, device identification and data acquisition, see the OnCommand Insight Installation and Administration Guide. blank Device Connected Type Originator Identifier Originator Access Time Originator Update Time Additional Data Sources Column that organizes the data according to the selected grouping format. Applicable with any presentation order other than No Grouping. Name of the data source device. Indication of whether any other devices are connected to this device. Green indicates other devices are connected to this device. For example, if OnCommand Insight is collecting data on an array, but not collecting on the switch to which that array is attached, the Connected column shows a red X. The type of device, for example, storage, switch or fabric/vsan. Information about an attribute of a data source that helps in troubleshooting the data source. A data source can have multiple originators of information and can be of different types. The ID that appears in this field depends on the type of data source originator. For example, if the originator is a switch, the IP of that switch appears in this field. This might be helpful when you review data source error messages. The error includes the originator information. The identifier information of the data source. The last time that the data source successfully logged into the device and queried the originator. If the Originator Access time is older than three months, the data in the row appears in red. The last time that the server was notified of changes to the originator. The acquisition does not update the server if the data did not change. Additional data sources that report on the same device, if any. This field appears only if accessing this view from the Acquisition Units main view. Information to Collect data source window When adding a data source, you might identify the specific types of information that the data source is going to collect. Data sources are capable of collecting different types of information if you have a Perform license that allows you to collect performance information. The Information to Collect dialog box only opens

86 86 OnCommand Insight Installation and Administration Guide if your license permits you to collect performance data. In the Information to Collect dialog box, you have the opportunity to enable performance data collection in addition to Inventory collection: Inventory describes the basic data source capabilities. Array Performance describes the polling interval and other performance details related to your specific data source. Switch Performance describes polling interval, SNMP information, and other performance details related to your specific data source. A data source might have Array Performance or Switch Performance capabilities, but not both. After enabling the features in this dialog box and clicking Next, you enter additional information defining the enabled capabilities. Vendor-specific data source reference For each data source, the specific requirements to define that data source depend on the vendor and model of the corresponding SAN devices. Related tasks Preparing to add a data source on page 66 3PAR (CLI) data source Configuring the data source for this vendor requires specific information. Inventory fields Field Port requirement Cluster IP(s) User name Password Poll Interval (min.) Exclude devices Description 22. This is not configurable. Network address for the clusters, specified as an IP (nnn.nnn.nnn.nnn format), or as a host name that can be resolved through DNS. Multiple IPs can be specified and should be separated by a comma. Name used to log in to the 3PAR device. Password used to log in to the 3PAR device. Interval, in minutes, at which the data source should poll the device. Comma-separated list of 3PAR devices, identified by IP address, that will not be discovered by this data source.

87 Data source setup and device identification 87 Field SSH timeout (sec) Description Time in seconds waiting for command to finish. If not completed when timeout expires, the run fails. Requirements An IP address or comma-separated list of IP addresses in the cluster of the 3PAR Management Server Read-only username and password to the InServ Server Validate access: Verify by using telnet to port 22. Note: No third-party software is required. Commands showsys -csvtable showversion -a showlicense showport -csvtable showport -par -csvtable showld -csvtable showpd -i -csvtable showpd -csvtable showvv -r -csvtable showvvpd <> -csvtable showvv -cpgalloc -csvtable showvv -csvtable showvlun -a -csvtable showhost -d -csvtable showcpg -r -csvtable showrcopy -csvtable Performance fields Field SMI-S Provider Host IP Address: Description Host name or IP address of 3PAR SMI-S provider host, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS.

88 88 OnCommand Insight Installation and Administration Guide Field SMI-S port: Protocol used: SMI-S namespace: User name: Password: Perform poll interval (seconds) Description Number of the server port through which the data source acquires information. The default is 5988, or 5989 if using HTTPS. HTTP (if unsecured access) or HTTPS (if secured access). The default is HTTP. SMI-S namespace used to query the data. The default is root/pg_interop. Name used for authentication by the SMI-S host for performance data. Password used for authentication by the SMI-S host for performance data. The recommended setting and default for the poll interval is 300 seconds. Brocade data source selection If you are using a Brocade data source, you can choose which data source to use based on a preferred order. The preferred order for selecting a Brocade data source is as follows. Try to choose the first type of Brocade data source. If you cannot choose that one, choose the second one. CLI (SSH) - Use this, if possible, for all Brocade data sources. SNMP HTTP Note: The HTTP and SNMP data sources are available for backward compatibility and are not actively maintained. The Brocade CLI and HTTP and are fabric aware, while the SNMP data sources are not fabric aware. Brocade (CLI) data source Configuring the data source for this vendor requires specific information. This data source provides Access Gateway support. Inventory fields Field Port requirement Description 22 open

89 Data source setup and device identification 89 Field Switch IP Fabric name User name Password Exclude devices Poll interval (minutes) Timeout (seconds) Time needed to wait for the banner output to finish after login Set to true if admin domains are active in the fabric Retrieve MPR data Enable trapping Minimum time between traps (seconds) Discover all switches in the fabric Description Network address for the switch device, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. IP address of at least one switch in every fabric. Fabric name to be reported by this data source (blank to report the fabric WWN). Name used to log in to the Brocade device. (admin=default) Password used to log in to the Brocade storage device. Comma-separated list of Brocade devices, identified by IP address, that will not be discovered by this data source. Interval, in minutes, at which the data source should poll the device. 15=default The period of time that data source will wait for before it declares that connection has failed (timed out). The default is 30. In seconds. 5 is the default. Mark the check box to set to true. Check box used to trigger Multi Protocol Router (MPR) data. Check box used to trigger acquisition upon receiving an SNMP trap from the device. If you mark this box, you must also activate SNMP notifications. Minimum elapsed time between acquisition attempts triggered by traps, in seconds. 10 is the default. Check box used to trigger identification of all of the switches on this fabric. Performance fields Field Perform poll interval (seconds) SNMP version Description The recommended setting and default for the poll interval is 300 seconds. V1 is the default.

90 90 OnCommand Insight Installation and Administration Guide Field SNMP community SNMP User Name SNMP Password SNMP Auth Protocol SNMP Privacy Protocol SNMP Privacy Password Description SNMP read-only community string used to access the device. The SNMP version protocol user name. This applies only to SNMP V3. The SNMP version protocol password. This applies only to SNMP V3. Encryption type for SNMP V3 configurations. MD5 is the default. Selections include: NONE, AES, DES, or TRIPLEDES. Provide a password for SNMP V3 encryption usage. Requirements An IP address of at least one switch in every fabric. The same account is needed globally across all switches in the fabric. Use PuTTY (open source terminal emulator) to confirm access. If the Perform product is installed, ports 161 and 162 must be open to all switches in the fabric for SNMP performance polling. Note: No third-party software is required. Commands alishow fabricshow fosconfig - -show ipaddrshow nbrstateshow nsshow -t sfpshow snmpconfig - -show accesscontrol snmpconfig - -show mibcapability snmpconfig - -show snmpv3 switchshow switchstatusshow trunkshow version wwn -sn

91 Data source setup and device identification 91 Brocade (MPR - Multi Protocol Router) data source Configuring the data source for this vendor requires specific information. Field Brocade switch User name Password Switches to exclude Poll interval (minutes) Command execution timeout Description Network address for the switch device, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Name used to log in to the Brocade device. (admin=default) Password used to log in to the Brocade storage device. Comma-separated list of Brocade devices, identified by IP address, that will not be discovered by this data source. Interval, in minutes, at which the data source should poll the device. The default is 15 minutes. The period of time that data source will wait for the command to execute before it declares that command execution has failed (timed out). The command is a CLI command that the data source issues to the NSP administrating server (console). The default is 60 seconds. Cisco data source (All Models Using SNMP) data source Configuring the data source for this vendor requires specific information. This data source provides N-port virtualization support. Inventory fields Field Port requirement 161 Cisco switch Poll interval (minutes) Description Network address for the switch, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Interval, in minutes, at which the data source should poll the device. Default = 40. SNMP version V2 is the default. V3 is supported in 6.0. SNMP community SNMP read-only community string used to access the device. Community strings are not applicable for SNMP V3 configurations.

92 92 OnCommand Insight Installation and Administration Guide Field User name Password SNMP Auth Protocol SNMP Privacy Protocol SNMP Privacy Password Enable trapping Minimum time between traps (seconds) Support chassis discovery Exclude devices Check device type Primary Alias Type Description Name used to log in to the switch. Used for SNMP V3 configurations only. Password used to log in to the switch. Used for SNMP V3 configurations only. Encryption type for SNMP V3 configurations. MD5 is the default. Selections include: NONE, AES, DES, and TRIPLEDES Provide a password for SNMP V3 encryption usage. Check box used to trigger acquisition upon receiving an SNMP trap from the device. If you mark this box, you must also activate SNMP notifications. Minimum elapsed time between acquisition attempts triggered by traps, in seconds. 10 is the default. If this checkbox is enabled, the data source will attempt to discover not only the switch configured in the data source, but also all other Cisco switches in the VSANs and fabrics of which this switch is a member. Comma-separated list of devices, identified by Switch IP address, that will not be discovered by this data source. For this data source, an example would be: If set, the data source will accept only those devices that explicitly advertise themselves as Cisco devices. Select the first preference for resolution of the alias from these options: Device Alias - a user-friendly name for a port WWN (pwwn) that can be used in all configuration commands as required. All switches in the Cisco MDS 9000 Family support Distributed Device Alias Services (device aliases). None - do not report any Alias. Port Description - a description to help identify the port in a list of ports. Zone Alias (all) - a user-friendly name for port that can be used only for zoning configuration. Zone Alias (only active) - a user-friendly name for port that can be used only for the active configuration. This is the default.

93 Data source setup and device identification 93 Field Secondary Alias Type Tertiary Alias Type Enable SANTap Proxy Mode Support Description Provide second preference for resolution of the alias using the same options as the Primary Alias Type. Provide third preference for resolution of the alias using the same options as the Primary Alias Type. Check this if your Cisco switch is using SANTap in proxy mode. Note: If you are using EMC RecoverPoint, then you are probably using SANTap. Performance fields Field Perform poll interval (seconds) Description The recommended setting and default for the poll interval is 300 seconds. Requirements The following items are required: An IP address of one switch in the fabric or individual switches. Chassis discovery must be on for fabric discovery. If using SNMP V2, read-only community string Access validation: Run the snmpwalk utility to the switch (see <install_path>\bin\) Note: No third-party software is required. SNMP MIBs CISCO-CDP-MIB CISCO-DM-MIB CISCO-DYNAMIC-PORT-VSAN-MIB CISCO-ENTITY-DISPLAY-MIB CISCO-FC-DEVICE-ALIAS-MIB CISCO-FC-FE-MIB CISCO-FCS-MIB CISCO-FDMI-MIB CISCO-IVR-MIB CISCO-LICENSE-MGR-MIB CISCO-NS-MIB CISCO-PSM-MIB

94 94 OnCommand Insight Installation and Administration Guide CISCO-SMI CISCO-ST-TC CISCO-TC CISCO-VSAN-MIB CISCO-VTP-MIB CISCO-ZS-MIB ENTITY-MIB IANAifType-MIB IF-MIB INET-ADDRESS-MIB SNMP-FRAMEWORK-MIB SNMPv2-CONF SNMPv2-MIB SNMPv2-SMI SNMPv2-TC EMC Atmos data source Configuring the data source for this vendor requires specific information. Implementation considerations The EMC Atmos data source provides support to the EMC cloud offering, which includes a single pool of storage. This data source is implemented in the following ways: Atmos data appears only in the Reporting Storage and Storage Pool Capacity data model and the Chargeback data model. Atmos has a physical hierarchy and a logical hierarchy that impact what you see in reports. Atmos resource management group (RMG) capacity is tracked in OnCommand Insight reporting as storage raw capacity. Atmos data is not grouped by and not reported on by tier. Atmos data can be reported on by an Atmos service level. Atmos logical hierarchy and OnCommand Insight business entity divisions OnCommand Insight reports on Atmos logical hierarchy in its business entities as follows: Business entity levels Tenant Line of business (LOB) Business Unit Project Atmos logical hierarchy division Tenant Subtenant NA NA

95 Data source setup and device identification 95 Field descriptions Field Port requirement Address of Atmos User name Password Poll Interval (min.) Description User defined. Network address for the Atmos node that is currently running the EMC Capacity Reporting Tool. Specified as an IP (nnn.nnn.nnn.nnn format) or as a host name that can be resolved through DNS. Name used for authentication into the EMC Capacity Reporting Tool API. The default is admin. Password used for authentication into the EMC Capacity Reporting Tool API. Interval, in minutes, at which the data source should poll the device. The recommended setting and default is 20 minutes. Requirements User name and password are not needed for EMC Capacity Reporting Tool authentication; however, they are needed for the reporting API. EMC Capacity Reporting Tool must be installed. An IP address of the Atmos node that is currently running the EMC Capacity Reporting Tool must be available. Access can be verified using telnet to the user-defined port. EMC Celerra SSH Configuring the data source for this vendor requires specific information. Field Description Port requirement SSH port 22 Address of Celerra Manager User name Password Poll interval (minutes) SSH process wait timeout (seconds) IP address Name used to log in to the Celerra device. The default is "administrator." Password used to log in to the Celerra device. Interval, in minutes, at which the data source should poll the device. The default is 20. The default is 600.

96 96 OnCommand Insight Installation and Administration Guide Requirements An IP address of the Control Station Read-only username and password. Access validation: Verify SSH access via PuTTY. Commands The following commands are invoked: fs_dedupe -info -all nas_disk -info nas_disk -list nas_fs -info -size -all nas_fs -list nas_pool -info -all nas_pool -list nas_pool -size -all nas_quotas -list -tree -fs nas_quotas -report -tree -fs nas_storage -list nas_storage -info <storagename> nas_version -l nas_volume -info -size -all nas_xml -info:all -level:3 /nas/sbin/t2tty -c <> "fcp topology" EMC CLARiiON (CLI) data source Before configuring this data source, make sure that the EMC Navisphere CLI is installed on the target device and on the OnCommand Insight server. The Navisphere CLI version must match the firmware version on the controller. NaviSphere Command Line Interface syntax naviseccli.exe -h <IP address> -user <user> -password <password> -scope <scope,use 0 for global scope> -port <use 443 by default> command

97 Data source setup and device identification 97 Inventory fields Field Description CLARiiON CLI port requirement 80, 443 CLARiiON port through which the data source communicates with the switch management console. By default, navicli.exe uses port 80 and naviseccli.exe uses port 443. Change this port if the CLARiiON array is configured to listen to a different port number. CLARiiON storage User name Password Poll interval (minutes) CLI Path to navicli.exe path or naviseccli.exe path Use secure client (naviseccli) Scope Network address for the storage device, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Name used to log in to the CLARiiON storage device. Password used to log in to the CLARiiON storage device. Interval, in minutes, at which the data source should poll the device. The default is 40. Full path to the executable. Provides a secure management facility for activating the required CLARiiON array replication support functionality. The secure client scope. This is an enumeration with the following values: Global, Local, LDAP. The default is Global. Performance field Field Perform poll interval (seconds) Description Set the Perform poll interval to 300 seconds. This is the recommended setting. Requirements An IP address of each CLARiiON Read-only Navisphere username and password to the CLARiiON arrays Access validation: Run NaviCLI from the OnCommand Insight Server to each array using the above username and password. NaviCLI version should correspond with the newest FLARE code on your array 3rd party software installed on OnCommand Insight Server/RAU: navicli

98 98 OnCommand Insight Installation and Administration Guide NaviSec CLI commands The following commands are invoked: naviseccli.exe help naviseccli.exe -h {ip} -User {user} -Password {password} -Scope 0 -port {port} getall naviseccli.exe -h {ip} -User {user} -Password {password} -Scope 0 -port {port} metalun -list naviseccli.exe -h {ip} -User {user} -Password {password} -Scope 0 -port {port} mirror sync -list naviseccli.exe -h {ip} -User {user} -Password {password} -Scope 0 -port {port} mirror async list naviseccli.exe -h {ip} -User {user} -Password {password} -Scope 0 -port {port} storagepool -list naviseccli.exe -h {ip} -User {user} -Password {password} -Scope 0 -port {port} thinlun list naviseccli.exe -h {ip} -User {user} -Password {password} -Scope 0 -port {port} storagegroup - list -gname {storage group name} (This can be run multiple times with different storage group names.) NaviCLI (Classic) commands navicli.exe help navicli.exe -h {ip} getall C:\Program Files\sanscreen\java\bin\java.exe jar C:\Program Files\EMC\Navisphere CLI \navicli.jar user {user} -password {password} -port {port} address {ip} metalun -list navicli.exe -h {ip} mirror sync -list navicli.exe -h {ip} mirror async list navicli.exe -h {ip} storagepool -list navicli.exe -h {ip} thinlun -list navicli.exe -h {ip} storagegroup -list -gname {storage group name} (This can be run multiple times with different storage group names.) Performance requirements Data logging must be started and Periodic Archiving turned On. This is done on the CLARiiON under the Analyzer menu. Performance commands The following commands are run for acquiring performance data: naviseccli.exe -h {ip} -User {user} -Password {password} -Scope 0 -port {port} getall naviseccli.exe -h {ip} -User {user} -Password {password} -Scope 0 -port {port} getdisk naviseccli.exe -h {ip} -User {user} -Password {password} -Scope 0 -port {port} metalun -list naviseccli.exe -h {ip} -User {user} -Password {password} -Scope 0 -port {port} thinlun -list

99 Data source setup and device identification 99 EMC Connectrix 7 data source Configuring the data source for this vendor requires specific information. Field Connectrix server User name Password Poll interval (minutes) Local IP Connectrix port Enable trapping Minimum time between traps (seconds) Description Network address for the Connectrix server, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Name used to log in to the Connectrix device. Password used to log in to the Connectrix device. Interval, in minutes, at which the data source should poll the device. The default value is 15 minutes. Local address of the OnCommand Insight Server. Used when working on an RAU with two NICs. Connectrix port through which the data source communicates with the switch management console (required if port numbers were changed on the Connectrix side). Check box used to trigger acquisition upon receiving an SNMP trap from the device. If you mark this box, you must also activate SNMP notifications. Minimum elapsed time between acquisition attempts triggered by traps, in seconds. Default = 10. EMC Connectrix 8.1, 8.6, 8.7, 8,8, 8.9, 9.0, 9.1, 9.5, 9.6, 9.7 data source Configuring the data source for this vendor requires specific information. Inventory fields Field EFC server User name Password Poll interval (minutes) Description Network address for the EFC server, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Name used to log in to the Connectrix device. Password used to log in to the Connectrix device. Interval, in minutes, at which the data source should poll the device. The default value is 15 minutes.

100 100 OnCommand Insight Installation and Administration Guide Field Exclude devices Fabric name Enable trapping Minimum time between traps (seconds) Inactive zone sets (comma delimited) NIC to use (when client machine has multiple NICs) Use the EFCM switch nickname as the OnCommand Insight switch name Description Comma-separated list of devices, identified by serial number, that will not be discovered by this data source. Fabric name to be reported by this data source (blank to report the fabric WWN). Check box used to trigger acquisition upon receiving an SNMP trap from the device. If you mark this box, you must also activate SNMP notifications. Minimum elapsed time between acquisition attempts triggered by traps, in seconds. The default is 15. List of inactive zone sets on which to perform acquisition (in addition to performing acquisition on the active zone sets). Separate multiple zone sets using a comma. Applicable when the data source reports to a Remote Acquisition Unit that has two or more network cards: one used to acquire information about SAN devices, and the other used to connect with the OnCommand Insight Server. Indication of which network interface to use on the RAU when reporting on SAN devices. Mark check box to enable. Performance field Field Perform poll interval (seconds) Description The recommended setting and default for the poll interval is 300 seconds.

101 Data source setup and device identification 101 EMC ECC StorageScope Host Resolver data source Configuring the data source for this vendor requires specific information. This applies to ECC StorageScope 5.x, ECC StorageScope 6.0, and ECC StorageScope 6.1. Field ECC port Description Port number used to access the RAMBDB data base. Server port through which the data source acquires information. Varies according to the version of Enterprise Control Center (ECC) installed on the customer side. The default port is 1521, but you can select ECC version 6.0 or earlier: 1521 ECC Version 6.1 or later: 1575 (SSL enabled) ECC server User name Password Poll interval (minutes) Protocol to connect to database. TCP or TCPS (encrypted) Query File System Information Network address for the ECC server, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Name used to log in to the ECC device. Password used to log in to the ECC device. Interval, in minutes, at which the data source should poll the device. The default is 30. TCP is cleartext communication and TCPS is encrypted communication. The default is TCP. Check this box to provide file system utilization information. To check if the Oracle RAMBDB service is started, do this: 1. From a Windows CLI, type: net start findstr RAMBDB 2. Do one of the following: If a line returns with the service name listed above, then the service is started already. If nothing is returned, start the service. Requirements Read-only username and password to access the views (default: stsview/sts) Access validation: Verify port access: telnet <ecc_ip> 1521 or 1575 as appropriate

102 102 OnCommand Insight Installation and Administration Guide EMC Solutions Enabler (CLI) with CLI Performance OnCommand Insight discovers Symmetrix storage arrays by using Solutions Enabler "symcli" commands against an existing Solutions Enabler server in your environment. This existing Solutions Enabler server has connectivity to the Symmetrix storage array through access to Gatekeeper volumes. Configuring the data source for this vendor requires specific information. Inventory fields Definitions are supplied for Fibre Channel and Switch Performance packages. The EMC Solutions Enabler Symmetrix CLI data source includes support for device configuration for thin provisioning and Symmetrix Remote Data Facility (SRDF). Field Port requirement Service name as specified in netcnfg Poll interval (minutes) Full path to CLI Exclude devices Description TCP connectivity to port 2707 on the existing Solutions Enabler server. Service Name for the Solution Enabler server as described in the local netcnfg file (Solutions Enabler install). Interval, in minutes, at which the data source should poll the device. The default is 40. Full path to the SYMCLI commands (default is C:\Program Files\EMC\SYMCLI\bin). Comma-separated list of devices, identified by serial number, that will not be discovered by this data source. For this data source, an example would be: Sym

103 Data source setup and device identification 103 Field Connection Caching Description Type of remote connection to the Solutions Enabler. Could be LOCAL, REMOTE_CACHED, or REMOTE. LOCAL means the OnCommand Insight Acquisition service is running on the Solutions Enabler server, which has Fibre Channel connectivity to the Symmetrix arrays you seek to discover, and has access to Gatekeeper volumes. This may be seen in some Remote Acquisition Unit (RAU) configurations. REMOTE_CACHED is the default and should be used in most cases. This uses the NETCNFG file settings to connect via IP to the Solutions Enabler server, which must have Fibre Channel connectivity to the Symmetrix arrays you seek to discover, and has access to Gatekeeper volumes. Sometimes REMOTE_CACHED options make CLI commands fail. In these cases, the REMOTE option should be used. Keep in mind that it will slow down the acquisition process (possibly to hours or even days in extreme cases). The NETCNFG file settings are still used for an IP connection to the Solutions Enabler server which has fibre channel connectivity to the Symmetrix arrays being discovered. Note: This setting does not change OnCommand Insight behavior with respect to the arrays listed as REMOTE by the "symcfg list" output. OnCommand Insight gathers data only on devices shown as LOCAL by this command. Replication field Field RPO polling interval (seconds) Description Interval, in seconds, at which the data source should poll the device. Default = 300. Performance fields Field Description Symstat polling interval (minutes) Interval given to the symstat command, which gathers data at that granularity, for example, IOPs for a volume over the 5- minute interval. Interval default is 5 minutes.

104 104 OnCommand Insight Installation and Administration Guide Field Filter Type Filter Device list Connection Caching Description Can be either excluded or included for acquisition by selecting the filter type as "exclude" or "include." The default is exclude. The comma-separated list of Solutions Enabler IP addresses to be included or excluded, depending upon the filter type selected. For this data source, an example would be: Sym Same as in Inventory fields. Requirements An IP address of the Solutions Enabler (SE) Server Solutions Enabler Server requirements: symapisrv and storsrvd services running EMC SYMAPI server license installed A properly configured <install_directory>\emc\symapi\config\netcnfg file is required. This enables the OnCommand Insight Server to make remote calls on the SE Server Access validation: Run symcfg list -v from the OnCommand Insight Server Third party software installed on the OnCommand Insight Server or RAU: The EMC Solutions Enabler (CLI) provider application must be installed and the version must match or be older than the version running on the Solutions Enabler Server. The Solutions Enabler "symcli" must be installed on the OnCommand Insight server. OnCommand Insight discovers all the Symmetrix arrays that are "Local" to this server, as seen in "symcfg list" output from that server. Commands The following commands are invoked: symaccess list view -sid <symid> -v symaccess list view -sid <symid> -v -detail symaccess show view <viewname> -sid <symid> symcfg list -sid <symid> -dir ALL -v symcfg list -v symcfg -sid <symid> list -datadev -v symcfg -sid <symid> list -tdev -v symcfg -sid <symid> list -tdev -detail -v (for 7.3 and greater) symcli symdev -sid <symid> list -v symdg list -v symdisk -sid <symid> list -v -hypers symfast -sid <symid> list -statesymfast -sid <symid> list -fp -v

105 Data source setup and device identification 105 symmaskdb -sid <symid> list database -v symsg -sid <symid> list -v symtier -sid <symid> list -vp -v Performance commands symstat -sid <SID> -i 60 -type BACKEND symstat -sid <SID> -i 60 -type DISKS symstat -sid <SID> -i 60 -type REQUESTS EMC Solutions Enabler (CLI) with SMI-S Performance data source OnCommand Insight discovers Symmetrix storage arrays by using Solutions Enabler "symcli" commands in conjunction with an existing Solutions Enabler server in your environment. The existing Solutions Enabler server has connectivity to the Symmetrix storage array through access to Gatekeeper volumes. Configuring the data source for this vendor requires specific information. Prerequisites Before configuring this data source, make sure the OnCommand Insight server has TCP connectivity to port 2707 on the existing Solutions Enabler server. OnCommand Insight discovers all the Symmetrix arrays that are "Local" to this server, as seen in "symcfg list" output from that server. On acquiring the OnCommand Insight host: The EMC Solutions Enabler (CLI) with SMI-S provider application must be installed and the version must match or be older than the version running on the Solutions Enabler Server. A properly configured {installdir}\emc\symapi\config\netcnfg file is required. This file defines service names for Solutions Enabler servers, as well as the access method (SECURE / NOSECURE /ANY). Note: If SMI-S user authentication is not enabled, the default values in the OnCommand Insight data source are ignored. Having symauth enabled on Symmetrix arrays might inhibit the ability of OnCommand Insight to discover them. OnCommand Insight Acquisition runs as the SYSTEM user on the OnCommand Insight / Remote Acquisition Unit server that is talking to the Solutions Enabler server. If hostname \SYSTEM does not have symauth privileges, OnCommand Insight fails to discover. Note: See Knowledge Base article on the NetApp Support Site at support.netapp.com. Field explanations The EMC Solutions Enabler Symmetrix CLI data source includes support for device configuration for thin provisioning and Symmetrix Remote Data Facility (SRDF). Definitions are supplied for Fibre Channel and Switch Performance packages.

106 106 OnCommand Insight Installation and Administration Guide Field Port requirement Service name as specified in netcnfg Poll interval (minutes) Full path to CLI Exclude devices Connection Caching Description 5988 and 5989 (SSL) Number of the server port through which the data source acquires information. Service Name for the Solution Enabler server as described in the local netcnfg file (Solutions Enabler install). Interval, in minutes, at which the data source should poll the device. The default is 40 minutes. Full path to the SYMCLI commands (default is C:\Program Files\EMC\SYMCLI\bin). Comma-separated list of devices, identified by serial number, that will not be discovered by this data source. For this data source, an example would be: Sym Type of remote connection to the Solutions Enabler. Could be LOCAL, REMOTE_CACHED, or REMOTE. LOCAL means the OnCommand Insight Acquisition service is running on the Solutions Enabler server, which has Fibre Channel connectivity to the Symmetrix arrays you seek to discover, and has access to Gatekeeper volumes. This may be seen in some Remote Acquisition Unit (RAU) configurations. REMOTE_CACHED is the default and should be used in most cases. This uses the NETCNFG file settings to connect using IP to the Solutions Enabler server, which must have Fibre Channel connectivity to the Symmetrix arrays you seek to discover, and has access to Gatekeeper volumes. Sometimes REMOTE_CACHED options make CLI commands fail. In these cases, the REMOTE option should be used. Keep in mind that it will slow down the acquisition process (possibly to hours or even days in extreme cases). The NETCNFG file settings are still used for an IP connection to the Solutions Enabler server which has fibre channel connectivity to the Symmetrix arrays being discovered. Note: This setting does not change OnCommand Insight behavior with respect to the arrays listed as REMOTE by the "symcfg list" output. OnCommand Insight gathers data only on devices shown as LOCAL by this command.

107 Data source setup and device identification 107 Field Filter Type Filter Device list Description Can be either excluded or included for acquisition by selecting the filter type as "exclude" or "include." Default=exclude The comma-separated list of Solutions Enabler IP addresses to be included or excluded, depending upon the filter type selected. For this data source, an example would be: Sym Replication field Field RPO polling interval (seconds) Description Interval, in seconds, at which the data source should poll the device. Default = 300. Performance fields Field SMI-S Host IP Description Host name or IP address of the EMC SMI-S provider host. Port The SMI-S port. The default is Protocol SMI-S namespace User name Password Polling interval (seconds) Filter Type Filter Device list HTTP (if unsecured access) or HTTPS (if secured access). SMI-S namespace used to query the data. Name used for authentication by the SMI-S host for performance data. Password used for authentication by the SMI-S host for performance data. The recommended setting and default for the poll interval is 1000 seconds. Can be either excluded or included for acquisition by selecting the filter type as "exclude" or "include." The default is exclude. The comma-separated list of Solutions Enabler IP addresses to be included or excluded, depending upon the filter type selected. For this data source, an example would be: Sym Requirements An IP address of the Solutions Enabler (SE) Server

108 108 OnCommand Insight Installation and Administration Guide Read-only username and password to the SE software Solutions Enabler Server 6.5X requirements: SMI-S provider for SMIS-S V1.2 installed After install, run \Program Files\EMC\SYMCLI\bin>stordaemon start storsrvd Access validation: Verify that the SMI-S provider is running: telnet <se_server> 5988 Note: No third-party software is required. EMC VNX data source Configuring the data source for this vendor requires specific information. Inventory fields Field Description Port requirement SSH port 22 User name Password Poll interval (minutes) SSH process wait timeout (seconds) Name used to log in to the VNX device. The default is "nasadmin." Password used to log in to the VNX device. Interval, in minutes, at which the data source should poll the device. The default is 40 The default is 600. Performance field Field Perform poll interval (seconds) Description Set the Perform poll interval to 300 seconds. This is the recommended setting. Requirements An IP address of the Control Station Read-only username and password. Access validation: Verify SSH access via PuTTY. Commands This data source runs the same commands as the EMC Celerra and EMC CLARiiON. /nas/opt/navisphere/bin/navicli -h {ip} getall /nas/opt/navisphere/bin/navicli -h {ip} metalun -list

109 /nas/opt/navisphere/bin/navicli -h {ip} mirror async list /nas/opt/navisphere/bin/navicli -h {ip} mirror sync -list /nas/opt/navisphere/bin/navicli -h {ip} storagegroup -list -gname <storagegroupname> /nas/opt/navisphere/bin/navicli -h {ip} storagepool -list /nas/opt/navisphere/bin/navicli -h {ip} thinlun -list /nas/opt/navisphere/bin/navicli -help /nas/sbin/t2tty -c <datamoverid> "fcp topology" cat /etc/hosts fs_dedupe -info -all nas_disk -info nas_disk -list nas_fs -info -size -all nas_fs -list nas_pool -info -all nas_pool -list nas_pool -size -all nas_quotas -list -tree -fs nas_quotas -report -tree -fs nas_storage -info <storagename> nas_storage -list nas_version -l nas_volume -info -size -all nas_xml -info:all -level:3 EMC VPLEX data source Configuring the data source for this vendor requires specific information. Field IP address of VPLEX Management Console Description Communication Port The default is 443. User name Password Poll Interval (min.) Connection timeout (sec) Data source setup and device identification 109 Host name or IP address of the VPLEX. Name used for authentication. The default is admin. Password used for authentication. Interval, in minutes, at which the data source should poll the device. Recommended and default setting is 20 minutes. Time in seconds waiting for command to finish. If not completed when timeout expires, the run fails. The default is 60 seconds.

110 110 OnCommand Insight Installation and Administration Guide Requirements An IP address of the VPLEX server Read-only username and password to the VPLEX server Validate access: Verify by using telnet to port 443. For a port other than the default port, with ny browser use Note: No third-party software is required. Engenio Arrays data source This data source collects inventory and performance information. There are two possible configurations (firmware 5.x and 6.x+) and they both have the same values. Inventory fields Field Port requirement 2463 Comma separated list of Array SANtricity Controller IPs Poll interval (min) Description Network address for the management controller of each array from which this data source will acquire information, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Separate multiple network addresses using a semicolon. Interval, in minutes, at which the data source should poll the device. 30=default Performance field Field OnCommand Insight Perform poll interval (up to 3600 seconds) Description Default is 300. Requirements IP address of each array Access validation: Ping the IP address of both controllers on each array. Note: No third-party software is required.

111 Data source setup and device identification 111 Fujitsu Eternus Configuring the data source for this vendor requires specific information. Field IP address User name Password Poll Interval (min.) SSH process wait timeout (sec) Description IP address of the storage. The administration-level name used to log into the Fujitsu device. Password used to log into the device. Interval, in minutes, at which the data source should poll the foundation package. Time in seconds waiting for the command to finish. If not completed when the timeout expires, the SSH Client disconnects. Requirements An IP address of the storage. This cannot be comma delimited. Administration-level username and password Validate access: Use SSH to the configured IP and log in. Ensure that the page scroll is disabled. Generic file system level utilization (FSLU) data source (Beta) Use this data source if you want to acquire data about your host and file system. Use of this data source requires that you have a custom data set (which could be a database, Excel file, or other type of data set file) that can be read by a script into the OnCommand Insight host_data database. This process requires the following elements: Data source configuration: The data source configuration should contain the default values for the database name, port, and credentials. You should configure only one data source of this type and the data source should exist on the local acquisition only. You create the FSLU data source in the OnCommand Insight Client using the Data Sources main view. Database: The host_data database includes your host and file system data and must be populated with data in order for this FSLU data source to work. OnCommand Insight acquires data from the host_data database on a daily basis (by default). The database is located on the OnCommand Insight server. Script: The script reads your data and writes it to the host_data database. Note: For assistance creating the script, contact NetApp Professional Services.

112 112 OnCommand Insight Installation and Administration Guide Field Name Poll interval (minutes) Number of days before nonupdated journals and hosts are removed Description This could be any text name. Interval, in minutes, at which the data source should poll the device. Default = If you want to remove entries older than 10 days by default, change this setting. Default = 10 days. Host2db.bat This example generates local host data using a SQL statement. REM generate local host data (ips, and file system usage) as a SQL the //Nologo option suppresses the script host version and copyright lines cscript //Nologo wmi2sql.vbs > testfile.sql REM update the database "c:\program Files\SANscreen\mysql\bin\mysql.exe" -uhosts -pnetapp123 host_data <testfile.sql> The following sample shows the contents of testfile.sql. START TRANSACTION; INSERT INTO journal (identifier, status) VALUES('localscript', 'SUCCESS') ON DUPLICATE KEY UPDATE journal_update_timestamp = CURRENT_TIMESTAMP; INSERT INTO HOST(hostname, journal_identifier) VALUES('TEST-DEV', 'localscript') ON DUPLICATE KEY UPDATE host_update_timestamp = CURRENT_TIMESTAMP, journal_identifier = 'localscript'; INSERT IGNORE INTO ip(ip, host_identifier) VALUES(' ', 'TEST-DEV'); INSERT INTO file_system(mount_name, host_identifier, allocated_capacity_mb,used_capacity_mb, fs_type, location_type) VALUES('C:', 'TEST-DEV', , , 'NTFS', 'LOCAL') ON DUPLICATE KEY UPDATE allocated_capacity_mb = , used_capacity_mb = , fs_type = 'NTFS', location_type = 'LOCAL'; INSERT INTO file_system(mount_name, host_identifier, allocated_capacity_mb,used_capacity_mb, fs_type, location_type) VALUES('H:', 'TEST-DEV', 81920, 448, 'NTFS', 'NAS') ON DUPLICATE KEY UPDATE allocated_capacity_mb = 81920, used_capacity_mb = 448, fs_type = 'NTFS', location_type = 'NAS'; INSERT INTO file_system(mount_name, host_identifier, allocated_capacity_mb,used_capacity_mb, fs_type, location_type) VALUES('L:', 'TEST-DEV', , , 'NTFS', 'NAS') ON DUPLICATE KEY UPDATE allocated_capacity_mb = , used_capacity_mb

113 Data source setup and device identification 113 = , fs_type = 'NTFS', location_type = 'NAS'; INSERT INTO file_system(mount_name, host_identifier, allocated_capacity_mb,used_capacity_mb, fs_type, location_type) VALUES('S:', 'TEST-DEV', 81920, 284, 'NTFS', 'NAS') ON DUPLICATE KEY UPDATE allocated_capacity_mb = 81920, used_capacity_mb = 284, fs_type = 'NTFS', location_type = 'NAS'; INSERT INTO file_system(mount_name, host_identifier, allocated_capacity_mb,used_capacity_mb, fs_type, location_type) VALUES('V:', 'TEST-DEV', , , 'NTFS', 'NAS') ON DUPLICATE KEY UPDATE allocated_capacity_mb = , used_capacity_mb = , fs_type = 'NTFS', location_type = 'NAS'; INSERT INTO file_system(mount_name, host_identifier, allocated_capacity_mb,used_capacity_mb, fs_type, location_type) VALUES('Z:', 'TEST-DEV', , , 'NTFS', 'NAS') ON DUPLICATE KEY UPDATE allocated_capacity_mb = , used_capacity_mb = , fs_type = 'NTFS', location_type = 'NAS'; COMMIT; HDS HiCommand Device Manager data source The HDS data source supports the HiCommand Device Manager server. OnCommand Insight communicates with the HiCommand Device Manager server using the standard HiCommand API. Configuring the data source for this vendor requires specific information. Inventory fields Field HiCommand Device Manager server HiCommand Device Manager port requirement User name Password Poll interval (minutes) Exclude devices Query host manager Description Network address for the HiCommand Device Manager server, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS Number of the HiCommand server port through which the data source acquires information. Name used to log in to the HiCommand. Password used to log in to the HiCommand. Interval, in minutes, at which the data source should poll the device. The default is 40 minutes. Comma-separated list of devices, identified by device ID, that will not be discovered by this data source. For this data source, an example would be: ARRAY.HDS9570V Provides host information on aliases from HiCommand.

114 114 OnCommand Insight Installation and Administration Guide Field HTTP timeout Description The timeout values are used for the connect and read processes. A value of 0 indicates that there is no timeout. The default value is 0. Note: In HDS USP, any disk can belong to more then one array group. Performance fields Field Polling interval (in seconds) for performance utility devices Devices - USP/R600 Storages SNM2 Devices - WMS/SMS/AMS Storages Report External Volumes Description The recommended setting and default for the poll interval is 300 seconds. Click Add to enter Data Source Property Group information. Click Add to enter Data Source Property Group information. Check this to enable performance data to appear for backend LUNs on performance-related views in the Client, if Hitachi Universal Storage Platform (USP) V virtualization layer is used. Requirements IP address of the HiCommand Device Manager server Read-only username and password for the HiCommand Device Manager software and "Peer" privileges Validate access: Log into the HiCommand Device Manager software using peer username and password. Verify access to the HiCommand Device Manager API: telnet <HiCommand Device_Manager_server_ip> 2001 Note: No third-party software is required. Commands <get target = "StorageArray"> <get target = "StorageArray"> (Components include: Logical Unit, path, WWN, WWN group, host information, path, volume connection, port controller, array group, port, LUN group, replication information) <get target = "Host">

115 Data source setup and device identification 115 Performance requirements HDS USP Performance Performance Monitor needs to be licensed. Monitoring switch needs to be enabled. Export Tools (Export.exe) needs to be copied to the OnCommand Insight Server. HDS AMS Performance Performance Monitor needs to be licensed. Storage Navigator Modular 2 (SNM2) CLI utility needs to be installed on the OnCommand Insight Server. Register all AMS, WMS, SMS storage arrays whose performance needs to be acquired by OnCommand Insight by using the following command: auunitaddauto.exe -ip <IP address of Controller0> IP address of Controller1> Ensure that all the arrays that you registered are listed in the output of this command: auunitref.exe HDS HiCommand Device Manager Lite data source The HDS data source supports the HiCommand Device Manager server. OnCommand Insight communicates with the HiCommand Device Manager server using the standard HiCommand API. Configuring the data source for this vendor requires specific information. Inventory fields Field HiCommand Device Manager server HiCommand Device Manager port User name Password Poll interval (minutes) Exclude devices Query host manager Description Network address for the HiCommand Device Manager server, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Number of the HiCommand server port through which the data source acquires information. Name used to log in to the HiCommand. Password used to log in to the HiCommand. Interval, in minutes, at which the data source should poll the device. Comma-separated list of devices, identified by device ID, that will not be discovered by this data source. For this data source, an example would be: ARRAY.HDS9570V Provides host information on aliases from HiCommand.

116 116 OnCommand Insight Installation and Administration Guide Field Description HTTP timeout (seconds) No timeout is supported by default. The default timeout is 0 seconds. Performance fields Field Polling interval (in seconds) for performance utility devices Devices - USP/R600 Storages SNM2 Devices - WMS/SMS/AMS Storages Description The recommended setting and default for the poll interval is 300 seconds. Click Add to enter Data Source Property Group information. Click Add to enter Data Source Property Group information. HP CommandView AE data source This data source supports the HiCommand Device Manager server. OnCommand Insight communicates with the HiCommand Device Manager server using the standard HiCommand API. The HP CommandView AE is also referred to as HDS HiCommand. Inventory fields Field HiCommand Device Manager server HiCommand Device Manager port requirement User name Password Poll interval (minutes) Exclude devices Query host manager HTTP timeout (seconds) Description Network address for the HiCommand Device Manager server, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS Number of the HiCommand server port through which the data source acquires information. Name used to log in to the HiCommand. Password used to log in to the HiCommand. Interval, in minutes, at which the data source should poll the device. Comma-separated list of devices, identified by device ID, that will not be discovered by this data source. For this data source, an example would be: ARRAY.HDS9570V Provides host information on aliases from HiCommand. The default value is 0, which indicates that there is no timeout.

117 Data source setup and device identification 117 Performance fields Field Polling interval (in seconds) for performance utility devices Devices - USP/R600 Storages SNM2 Devices - WMS/SMS/AMS Storages Report External Volumes Description The recommended setting and default for the poll interval is 300 seconds. Click Add to enter Data Source Property Group information. Click Add to enter Data Source Property Group information. Check this to enable performance data to appear for backend LUNs on performance-related views in the Client, if Hitachi Universal Storage Platform (USP) V virtualization layer is used. Requirements IP address of the Command View (AE) server Read-only username and password to the CVAE software Access validation: Log into CVAE software using read-only username and password. Verify access to CVAE API by entering: telnet <cvae_server_ip> 2001 Note: No third-party software needs to be installed. HP CommandView AE Lite data source The HP CommandView AE Lite data source supports the HP CommandView AE Lite edition, the CLI, and SMI-S only version of the HP CommandView AE. This version is the CLI and SMI-S-only version of Command View AE. For details, see an explanation from HP: qa.html. Inventory fields Field HiCommand Device Manager server HiCommand Device Manager port User name Description Network address for the HiCommand Device Manager server, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS Number of the HiCommand server port through which the data source acquires information. Name used to log in to the HiCommand.

118 118 OnCommand Insight Installation and Administration Guide Field Password Poll interval (minutes) Exclude devices Query host manager HTTP timeout (seconds) Description Password used to log in to the HiCommand. Interval, in minutes, at which the data source should poll the device. The default is 40 minutes. Comma-separated list of devices, identified by device ID, that will not be discovered by this data source. For this data source, an example would be: ARRAY.HDS9570V Provides host information on aliases from HiCommand. The default value is 0, which indicates that there is no timeout. Performance fields Field Polling interval (in seconds) for performance utility devices Devices - USP/R600 Storages SNM2 Devices - WMS/SMS/AMS Storages Description The recommended setting and default for the poll interval is 300 seconds. Click Add to enter Data Source Property Group information. Click Add to enter Data Source Property Group information. Requirements IP address of the Command View (AE) server This is a version of the device manager with only the CLI licensed. Read-only username and password to the CVAE software Access validation: Log into CVAE software using read-only username and password. Note: No third-party software needs to be installed. HP (EVA) Configuring the data source for this vendor requires specific information. Inventory fields Field Description Port requirements 2301/2372 Command View server Name of the Command View (CV) manager.

119 Data source setup and device identification 119 Field User name Password Poll interval (min) CLI home Exclude devices Description Name used to log in to the Command View manager. The name must be defined in Command View. Password used to log in to the Command View. Interval, in minutes, at which the data source should poll the device. Full pathname to the CLI home directory where sssu.exe is located. To validate access, run sssu.exe. Comma-separated list of array names, identified by array name, that will not be discovered by this data source. For this data source, an example would be: EVA6000 Performance fields Field Storage Performance poll interval (seconds) CLI home command timeout (seconds) Exclude devices Description Interval, in minutes, at which the data source should poll the device for performance data. Full pathname to the CLI home directory where sssu.exe is located. To validate access, run sssu.exe. The period of time that data source waits for the command to execute before it declares that command execution has failed (timed out). The command is a CLI command that the data source issues to the NSP administrating server (console). The default is 600 seconds. Comma-separated list of array names, identified by array name, that will not be discovered by this data source. For this data source, an example would be: EVA6000 Requirements IP address of the CV server Read-only username and password to the CV software. The user must be defined in the CV software. Third-party software installed on the OnCommand Insight Server/RAU: sssu.exe. The sssu.exe version should correspond to the CV version. Access validation: Run sssu.exe commands using username and password.

120 120 OnCommand Insight Installation and Administration Guide Commands LS CONTROLLER FULL XML LS DISK FULL XML LS DR_GROUP FULL XML LS HOST FULL XML LS SYSTEM FULL XML LS VDISK FULL XML SHOW VDISK FULL Performance requirements The HP StorageWorks Command View EVA software suite must be installed on the OnCommand Insight Server, or install a Remote Acquisition Unit (RAU) on the EVA server. 1. Install HP StorageWorks Command View EVA Software Suite on the OnCommand Insight Server, or install a Remote Acquisition Unit on the Command View EVA server. 2. Locate the evaperf.exe command. For example, c:\program Files\Hewlett-Packard \EVA Performance Monitor\ 3. Using the IP of the Command View server, run the following where 860 is the default port: a. Evaperf.exe server <Command View Server IP> 860 <username> b. Enter the Command View server password at the password prompt. This should return a command line prompt and nothing else. 4. Verify the setup by running evaperf.exe ls. You should see a list of arrays or controllers managed by the Command View server. Each line shows a controller on an EVA array. Performance commands Evaperf.exe all -csv -nfn -KB -cont <sampleduration> -dur <sampleduration> HP (XP) data source Configuring the data source for this vendor requires specific information. Field Description Port requirement 80, 443

121 Data source setup and device identification 121 Field CommandView server User name Password Poll interval (min) Path to cvcli.bat Exclude devices Description Network address for the management controller of each array from which this data source will acquire information, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Separate multiple network addresses using a semicolon. Name used to log in to the Command View. Password used to log in to the Command View. Interval, in minutes, at which the data source should poll the device. Absolute path to the CV CLI batch file (cvcli.bat) - with or without the trailing backslash (\). Comma-separated list of devices, identified by serial number, that will not be discovered by this data source. Requirements IP address of the Command View (CV) server Read-only username and password to the CV software The Command View (CV) CLI must be installed on the target device. Third-party software installed on the OnCommand Insight Server or RAU: cvcli Access validation: Run cvcli commands using the username and password. IBM DS (CLI) data source Configuring the data source for this vendor requires specific information. Inventory fields Field Description Port requirements 80, 443, and 1750 DS storage User name Password Poll interval (min) Network address for the DS device, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Name used to log in to the DS. Password used to log in to the DS. Interval, in minutes, at which the data source should poll the device. 40 is the default.

122 122 OnCommand Insight Installation and Administration Guide Field Storage display name dscli.exe path Exclude devices Description User-specified alias used as the storage name. Full path to the dscli utility. Comma-separated list of devices, identified by serial number, that will not be discovered by this data source. Performance fields Field Perform poll interval (seconds) Include: Data collected only from devices on list. Exclude: No data from these devices is collected. Device list to include/exclude Description The recommended setting and default for the poll interval is 300 seconds. Can be either excluded or included for acquisition by selecting the filter type as "exclude" or "include." The comma-separated list of Solutions Enabler IP addresses to be included or excluded, depending upon the filter type selected. Requirements IP address of each DS array Storage Display Name is optional and cosmetic only Read-only username and password on each DS array Third-party software installed on the OnCommand Insight Server: IBM dscli Access validation: Run dscli commands using the username and password Commands dscli.exe -hmc <ip address> -user <user> -passwd <password> lsarray -v off -hdr off -fmt xml -dev IBM.XXX dscli.exe -hmc <ip address> -user <user> -passwd <password> lsddm -l -v off -hdr off -fmt xml IBM.XXX dscli.exe -hmc <ip address> -user <user> -passwd <password> lsfbvol -v off -hdr off -fmt xml -dev IBM.XXX dscli.exe -hmc <ip address> -user <user> -passwd <password> lshostconnect -v off -hdr off -fmt xml -dev IBM.XXX dscli.exe -hmc <ip address> -user <user> -passwd <password> lsioport -v off -hdr off -fmt xml -dev IBM.XXX dscli.exe -hmc <ip address> -user <user> -passwd <password> lsrank -v off -hdr off -fmt xml -dev IBM.XXX

123 Data source setup and device identification 123 dscli.exe -hmc <ip address> -user <user> -passwd <password> lssi -v off -hdr off -fmt xml dscli.exe -hmc <ip address> -user <user> -passwd <password> lsvolgrp -v off -hdr off -fmt xml -dev IBM.XXX dscli.exe -hmc <ip address> -user <user> -passwd <password> -script Performance commands dscli.exe -hmc <ip address> -user <user> -passwd <password> -script "diskdata" dscli.exe -hmc <ip address> -user <user> -passwd <password> -script "RankPerfScript.txt" dscli.exe -hmc <ip address> -user <user> -passwd <password> -script "VolPerfScript.txt" dscli.exe -hmc <ip address> -user <user> -passwd <password> -script "volumedata.txt" IBM ESS (CLI) data source Configuring the data source for this vendor requires specific information. Field Description Port requirement 80, 443 ESS storage User name Password Poll interval (min) Storage display name esscli.exe path Network address for the ESS device, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Name used to log in to the ESS. Password used to log in to the ESS. Interval, in minutes, at which the data source should poll the device. User-specified alias used as the storage name. Full path to the esscli utility. Requirements IP address of each ESS array Read-only username and password on each array Third-party software installed on OnCommand Insight Server or RAU: IBM ESS esscli Access validation: Run esscli commands using the username and password.

124 124 OnCommand Insight Installation and Administration Guide Commands list diskgroup -fmt "dg,raid,width,dcap,dd" list hostconnection -fmt "host,profile,attach,init,ports" list port -fmt "server,port,loc,type,speed,protocol,topology,wwn,status" list server -fmt "server,model,mfg,wwn,codeec,cache,nvs,racks" list volume -fmt "server,vol,cap,units,voltype,lss,vs,label, volser" list volumeaccess -fmt "server,vol,target,lun,sz,host,init,ports" list volumespace -fmt "server,vs,raid,cap,free,fmt,on,vols,lss,status" IBM FAStT data source Configuring the data source for this vendor requires specific information. Inventory fields Field Array controller IP Poll interval (min) Description Network address for the management controller of each array from which this data source will acquire information, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Separate multiple network addresses using a semicolon. Interval, in minutes, at which the data source should poll the device. 30 is the default. Performance field Field OnCommand Insight Perform poll interval (up to 3600 seconds) Description Default is 300. IBM PowerVM data source (Beta) This data source collects information about virtual partitions running on IBM POWER hardware instances managed by a Hardware Management Console (HMC). Configuring the data source for this vendor requires specific information. Field SSH port requirement Description SSH-22 Port on which the SSH process accepts incoming connections on the HMC.

125 Data source setup and device identification 125 Field Hardware Management Console (HMC) address HMC User Password Poll interval (min) SSH process wait timeout in sec. Excluded managed system IDs (for example, NNNN- MMM*ZZZZZZZ) or display names (comma separated) Description Network IP address for the management port of HMC, or as a hostname that can be resolved through DNS. The user name to log into the HMC via SSH. The configured user must have View permission on all management system and logical partition security domains. The user must also have View permission on "HMC Configurations" and the ability to "Collect VPD Information" for the HMC Console security grouping. Finally, the user must be allowed "Virtual IO Server Command" access under the "Logical Partition" security grouping. Password of the HMC user. Interval, in minutes, at which the data source should poll the HMC. Defaults to 20 minutes. Timeout for any one SSH command, in seconds. List of managed POWER hardware systems to skip when retrieving data. Specified as either the full system ID or as system display name strings. Multiple values should be comma separated. Requirements Username and password that provide access to HMC via SSH. The user must be configured to have the View permission on all management systems and logical partition security domains. The user must also have View permissions on HMC Configurations and the ability to "Collect VPD Information" for the HMC Console security grouping. The user must also be allowed "Virtual IO Server Command" access under the "Logical Partition" security grouping. It is recommended to start from a role of an operator and remove roles. Read-only users on the HMC do not have privileges to run proxied commands on AIX hosts. IBM SVC (CLI) data source Configuring the data source for this vendor requires specific information. OnCommand Insight collects performance information from this data source. This data source provides support for V7000 devices. Field Port requirement 22 Clusters (IP) Description Network address for the cluster/s, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS.

126 126 OnCommand Insight Installation and Administration Guide Field User name Poll interval (min) Exclude devices Full path to private key SSH process wait timeout in sec. Description Name used to log in to the IBM IV (CLI) device. Interval, in minutes, at which the data source should poll the device. The default is 40. Comma-separated list of devices, identified by serial number, that will not be discovered by this data source. Full path to the IBM IV utility. Time in seconds waiting for command to finish. If not completed when timeout expires, the run fails. The default is 10. Requirements IP address of each SVC cluster Public and private key pair generated by OnCommand Insight and on the OnCommand Insight Server Public key installed on the SVC cluster Private key needs to be identified in the data source DS Storage is the IP address or the hostname Access validation: Open ssh session to the SVC cluster using the private key Note: No third-party software needs to be installed. Commands scp -f /tmp/svc.config.backup.xml svcconfig backup -quiet Performance requirements SVC Console, which is mandatory for any SVC cluster and required for the SVC discovery foundation package. Administrative access level required only for copying performance data files from cluster nodes to the config node Note: Because this access level is not required for the SVC foundation discovery package, the SVC foundation user might not work successfully. A private and public SSH key must be generated for this user and the private key stored so that it is accessible from the Acquisition unit. If the SVC foundation user has the proper permissions, then the same user and key works. The same SSH key can be used for inventory and performance data.

127 Data source setup and device identification 127 Enable data collection by connecting to the SVC cluster by SSH and running: svctask startstats -interval 1 Note: Alternatively, enable data collection using the SVC management user interface. IBM Tivoli Monitoring data source This data source is used solely for File System Utilization. It communicates directly with the Tivoli Monitoring Database, also known as the Tivoli Monitoring Data Warehouse. Oracle and DB2 databases are supported. Oracle configuration If the specified SID results in the error message containing "ORA-12154" on attempting to connect, double-check your Oracle DB network service configuration. If the access configuration specifies a fully qualified hostname (for example, "NAMES.DEFAULT_DOMAIN"), try inserting the fully qualified service name in the SID field. A simple example would be that the connection to SID "testdb" is failing and your Oracle configuration specifies a domain of "company.com". The following string can be used instead of the base SID to try and connect: "testdb.company.com." Field Tivoli Monitoring Database IP Tivoli Monitoring Database Port Port requirements Oracle SID User name Password Poll interval (min) Database driver to user Protocol used to connect to the database. May be TCP or TCPS. Oracle jar file Description IP address of server is the default for Oracle. http-80 (TCP) https-443 (TCPS) For Oracle, QTIVOLI is the default. User name for login. Password for login. 60=default Oracle is the default. TCP=default (TCPS is the secure option and depends on the database configuration.) ojdbc5.jar DB2 configuration Field Tivoli Monitoring Database IP Description IP address.

128 128 OnCommand Insight Installation and Administration Guide Field Tivoli Monitoring Database Port DB2 Database Name User name Password Poll interval (min) Database driver to user Protocol used to connect to the database. May be TCP or TCPS. DB2 jar file Description should be configured for DB2. Enter the following name: QTIVOLI, which is the default. User name for login. Password for login. 60=default For DB2 environments, set it to DB2 TCP=default (TCPS is the secure option and depends on the database configuration.) db2jcc_license_cu.jar, db2jcc.jar, db2jcc4.jar IBM TotalStorage DS4000 data source Configuring the data source for this vendor requires specific information. Inventory fields Field Port requirement 2463 Array controller IP Poll interval (min) Description Network address for the management controller of each array from which this data source will acquire information, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Separate multiple network addresses using a semicolon. Interval, in minutes, at which the data source should poll the device. 30 is the default. Performance field Field Perform poll interval (seconds) Description Interval, in minutes, at which the data source should poll the device for performance data. Requirements IP address of each DS5 or FAStT array

129 Access validation: Ping the IP address of both controllers on each array. Note: No third-party software needs to be installed. Data source setup and device identification 129 Performance This data source collects volume data statistics via the API. IBM XIV (CLI) data source The IBM XIV CLI requirements are included in the following table. This data source includes support for iscsi. Field IP Address User name Password Poll interval (minutes) Full path to XIV CLI directory Description IP address for the storage system. Name used to log in to the storage system. Password used to log in to the storage system. Interval, in minutes, at which the data source should poll the device. The default is 40 minutes. C:\Program Files\GUI10=default Requirements Port requirement: TCP port 7778 IP address of the XIV management interface Read-only username and password Third-party software installed on the OnCommand Insight Server or RAU: XIV CLI Access validation: Log into the XIV user interface from the OnCommand Insight Server using the username and password. Commands OnCommand Insight invokes the following commands. xcli -x -m <IP Address> -u <user> -p <password> config_get xcli -x -m <IP Address> -u <user> -p <password> disk_list xcli -x -m <IP Address> -u <user> -p <password> fc_port_list xcli -x -m <IP Address> -u <user> -p <password> fc_connectivity_list xcli -x -m <IP Address> -u <user> -p <password> host_list xcli -x -m <IP Address> -u <user> -p <password> ipinterface_list xcli -x -m <IP Address> -u <user> -p <password> mapping_list host = <hostname> xcli -x -m <IP Address> -u <user> -p <password> pool_list

130 130 OnCommand Insight Installation and Administration Guide xcli -x -m <IP Address> -u <user> -p <password> system_capacity_list xcli -x -m <IP Address> -u <user> -p <password> version_get xcli -x -m <IP Address> -u <user> -p <password> vol_list xcli -x -m<ip Address> -u <user> -p <password> host_connectivity_list McData (EFCM) Manager (8.1, 8.6, 8.7, 8.8, 8.9, 9.0,9.1, 9.5, 9.6, 9.7) data source Configuring the data source for this vendor requires specific information. Inventory fields Field Port requirement EFC server User name Password Poll interval (minutes) Fabric name Enable trapping Minimum time between traps (seconds) Inactive zone sets (comma delimited) NIC to use (when client machine has multiple NICs) Description 51510, 51511, 51512, Bi-directional. Also, a connection port over one of these ports 52688, 53865, 55042, 56219, 57396, 58573, 1099 Network address for the Enterprise Fabric Connectivity (EFC) server, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Name used to log in to the switch. Password used to log in to the McData device. Interval, in minutes, at which the data source should poll the EFC. 15 is the default Fabric name to be reported by this data source (blank to report the fabric WWN). Check box used to trigger acquisition upon receiving an SNMP trap from the device. If you mark this box, you must also activate SNMP notifications. Minimum elapsed time between acquisition attempts triggered by traps, in seconds. 15 is the default List of inactive zone sets on which to perform acquisition (in addition to performing acquisition on the active zone sets). Separate multiple zone sets using a comma. Applicable when the data source reports to a Remote Acquisition Unit that has two or more network cards: one used to acquire information about SAN devices, and the other used to connect with the OnCommand Insight server. Indication of which network interface to use on the RAU when reporting on SAN devices.

131 Data source setup and device identification 131 Field Exclude devices Use the EFCM switch nickname as the Insight switch name Description Comma-separated list of devices that will not be discovered by this data source. A check box that defaults to checked (true). Performance field Field Perform poll interval (seconds): Description The recommended setting and default for the poll interval is 300 seconds. Requirements The following items are required: An IP address of the EFCM Server. Read-only username and password for EFCM. Access validation: Access to the switch via Telnet from the OnCommand Insight Server, using the read-only username and password over port Note: No third-party software is required. McData EFCM 7 data source This information applies to the Enterprise Fabric Connectivity Manager (EFCM) 7 data source. Configuring the data source for this vendor requires specific information. Field Connectrix server User name Password Poll interval (minutes) Local IP Description Network address for the Connectrix server, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Name used to log in to the Connectrix device. Password used to log in to the Connectrix device. Interval, in minutes, at which the data source should poll the device. Local address of the OnCommand Insight Server. Used when working on an RAU with two NICs.

132 132 OnCommand Insight Installation and Administration Guide Field Connectrix port Enable trapping Minimum time between traps (sec) Description Connectrix port through which the data source communicates with the switch management console (required if port numbers were changed on the Connectrix side). Check box used to trigger acquisition upon receiving an SNMP trap from the device. If you mark this box, you must also activate SNMP notifications. Minimum elapsed time between acquisition attempts triggered by traps, in seconds. The default is 10. McData Sphereon SNMP data source Configuring the data source for this vendor requires specific information. Inventory fields Field Port requirement 161 Sphereon switch Poll interval (minutes) SNMP version SNMP community Description Network address for the switch, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Interval, in minutes, at which the data source should poll the device. V2 is the default SNMP read-only community string used to access the device. User name SMIS user name used to log in to the switch. Used only for V3. Password SMIS password used to log in to the switch. Used only for V3. SNMP Auth Protocol SNMP Privacy Protocol SNMP Privacy Password Fabric name Enable trapping Encryption type. MD5 is the default. Selections include: NONE, AES, DES, or TRIPLEDES. Provide a password for SNMP V3 encryption usage. Fabric name to be reported by this data source (blank to report the fabric WWN). Check box used to trigger acquisition upon receiving an SNMP trap from the device. If you mark this box, you must also activate SNMP notifications.

133 Data source setup and device identification 133 Field Minimum time between traps (seconds) Description Minimum elapsed time between acquisition attempts triggered by traps, in seconds. Performance field Field Insight Perform poll interval (seconds) Description The recommended setting and default for the poll interval is 300 seconds. Requirements An IP address of every switch Read-only community string HTTP access to the switch to obtain zoning information Access validation: Run the snmpwalk utility to the switch (see <install_path>\bin\) Note: No third-party software is required. SNMP MIBs EF-6000-MIB EOSN-FCPING-MIB EOSN-FCTRACEROUTE-MIB EOSN-MIB EOSN-PARTITIONING-MIB EOSN-REG EOSN-SECURITY-MIB EOSN-TC EOSN-TRAP-MIB FCFABRIC-ELEMENT-MIB FCMGMT-MIB FIBRE-CHANNEL-FE-MIB FIBRE-CHANNEL-MGMT-MIB IANAifType-MIB IF-MIB INET-ADDRESS-MIB RFC1155-SMI RFC1213-MIB RFC1215-MIB SNMP-COMMUNITY-MIB

134 134 OnCommand Insight Installation and Administration Guide SNMP-FRAMEWORK-MIB SNMP-NOTIFICATION-MIB SNMP-TARGET-MIB SNMP-USER-BASED-SM-MIB SNMPv2-CONF SNMPv2-MIB SNMPv2-SMI SNMPv2-TC SNMP-VIEW-BASED-ACM-MIB TRANSPORT-ADDRESS-MIB NetApp Clustered Data ONTAP data source Configuring the data source for this vendor requires specific information. This datasource uses the CLI to obtain capacity numbers. This should be used for storage systems using clustered Data ONTAP. Inventory fields Field Communication port requirement NetApp Management IP User name Password Connection Type Description 80 for HTTP or 443 for HTTPS. 80 is the default. IP address of a cluster management LIF or management IP of the cluster. Name used to log into the cluster. Password used to log into the NetApp cluster. Default is HTTP. Connection Port The default is 80. Poll Interval (min) Interval, in minutes, at which the data source should poll the device. Performance field Field Storage Insight poll interval (seconds) Description Interval, in seconds, at which the data source should poll the device for performance data.

135 Storage systems connection requirements As an alternative to using the default administrative user for this data source, you can configure a user with administrative rights directly on the NetApp storage systems so that this data source can acquire data from NetApp storage systems. Connecting to NetApp vfiler unit storage systems requires that the user, who is specified when acquiring the main pfiler (on which the vfiler units exist), meets the following conditions: The user must be on vfiler0 (root filer/pfiler). vfiler units are acquired when acquiring the main pfiler. This user must have at minimum the following role capabilities: "api-*": Use this to allow OnCommand Insight to execute all NetApp storage API commands. "login-http-admin": Use this to allow OnCommand Insight to connect to the NetApp storage via HTTP. "security-api-vfiler": Use this to allow OnCommand Insight to execute NetApp storage API commands to retrieve vfiler unit information. "cli-options": Use this to read storage system options. " cli-lun": Access these command for managing LUNs. Displays the status (LUN path, size, online/offline state, and shared state) of the given LUN or class of LUNs. "cli-df": Use this to display free disk space. "cli-ifconfig": Use this to display interfaces and IP addresses. OnCommand Insight executes the following calls made by the NetApp data source: aggr-get-iter cf-get-iter cf-status cifs-server-get-iter cifs-share-get-iter cluster-identity-get export-policy-get-iter export-rule-get-iter fc-config-list-info fcp-adapter-get-iter fcp-interface-get-iter fcp-service-get-iter flexcache-get-iter igroup-get-iter interim-license-list-get iscsi-initiator-auth-get-iter iscsi-initiator-get-iter iscsi-interface-get-iter iscsi-service-get-iter Data source setup and device identification 135

136 136 OnCommand Insight Installation and Administration Guide iscsi-session-get-iter iscsi-tpgroup-get-iter job-schedule-cron-get-iter job-schedule-get-iter job-schedule-interval-get-iter lun-get-iter lun-map-get-iter net-dns-get-iter net-interface-get-iter net-port-get-iter nfs-service-get-iter nis-get-iter portset-get-iter qtree-list-iter quota-report-iter sis-get-iter sis-policy-get-iter snapmirror-get-iter snapshot-policy-get-iter storage-adapter-get-adapter-info storage-adapter-get-adapter-list storage-disk-get-iter system-get-node-info-iter system-get-version system-node-get-iter volume-clone-get-iter volume-get-iter volume-move-get-iter volume-space-get-iter vserver-get-iter To configure an administrative user on NetApp storage, do the following: 1. Log into the NetApp storage system by using an SSH client (for example, PuTTY). 2. Use the useradmin command to ensure that the user has the needed role capabilities. 3. Do one of the following: Associate the user with the default "admin" or "root" user group. Create a custom group with these role capabilities. useradmin role add <user> -a login-http-admin,api-*,cli-rdfile,clioptions, cli-df,cli-lun,cli-ifconfig

137 useradmin group add <group> -r <user> useradmin user add <user> -g <group> Note: To update the roles, use modify instead of add. Data source setup and device identification 137 Requirements IP address of the FAS storage controller and cluster partner Username and password for the controller and the partner FCP license and mapped/masked volumes required for OnCommand Insight discovery CIFS and/or NFS license and CIFS shares or NFS exports required for OnCommand Insight NAS discovery Access validation: Telnet into the FAS controller from the OnCommand Insight Server using the username and password. Note: Third-party software is not required. NetApp Data ONTAP operating in 7-Mode (ONTAPI) data source Configuring the data source for this vendor requires specific information. This datasource uses the CLI to obtain capacity numbers. This should be used for storage systems using Data ONTAP software operating in 7-Mode. Inventory fields Field Communication port requirement Address of Filer User name Password Address of the partner filer in cluster User name of partner filer in cluster Password of partner filer in cluster Poll interval (min) Connection Type Description 80 or is the default. IP address. Name used to log into the device. Password used to log into the NetApp device. If storage systems are configured as fail-over clusters, add the second storage system's IP address here. If storage systems are configured as a fail-over cluster, add the user name for the second storage system here. If storage systems are configured as a fail-over cluster, add the second storage system password here. Interval, in minutes, at which the data source should poll the device. Default is HTTP. Connection Port The default is 80.

138 138 OnCommand Insight Installation and Administration Guide Performance field Field Storage insight poll interval (seconds) Description 300 is the default. Storage systems connection requirements As an alternative to using the default administrative user for this data source, you can configure a user with administrative rights directly on the NetApp storage systems so that this data source can acquire data from NetApp storage systems. Connecting to NetApp storage systems requires that the user, who is specified when acquiring the main pfiler (on which the storage system exist), meets the following conditions: The user must be on vfiler0 (root filer/pfiler). Storage systems are acquired when acquiring the main pfiler. This user must have at minimum the following role capabilities: "api-*": Use this to allow OnCommand Insight to execute all NetApp storage API commands. "login-http-admin": Use this to allow OnCommand Insight to connect to the NetApp storage via HTTP. "security-api-vfiler": Use this to allow OnCommand Insight to execute NetApp storage API commands to retrieve vfiler unit information. "cli-options": Use this to read storage system options. " cli-lun": Access these command for managing LUNs. Displays the status (LUN path, size, online/offline state, and shared state) of the given LUN or class of LUNs. "cli-df": Use this to display free disk space. "cli-ifconfig": Use this to display interfaces and IP addresses. OnCommand Insight executes the following calls made by the NetApp data source: aggr-list-info aggr-space-list-info - Get aggregate capacity details cifs-share-list-iter-end cifs-share-list-iter-next cifs-share-list-iter-start cifs-status cli-df cli-ifconfig - Get IP configuration (when net-ifconfig-get not supported) cli-lun cli-options disk-list-info fcp-adapter-list-info fcp-service-status

139 iscsi-initiator-auth-list-info iscsi-initiator-get-default-auth iscsi-node-get-name iscsi-portal-list-info iscsi-service-status iscsi-session-list-info iscsi-tpgroup-list-info license-list-info lun-list-info lun-map-list-info net-ifconfig-get - Get IP configuration nfs-exportfs-list-rules nfs-exportfs-list-rules-2 - NFS exports for later version 7-mode nfs-status perf-object-counter-list-info perf-object-get-instances-iter-end perf-object-get-instances-iter-next perf-object-get-instances-iter-start perf-object-list-info portset-list-info rdfile qtree-list quota-report security-api-vfiler snapmirror-get-status - Get storage synchronization data snapmirror-list-connections snapmirror-list-destinations snapshot-reserve-list-info storage-adapter-get-adapter-list - Discover back end/initiator FC ports system-cli system-get-info system-get-ontapi-version system-get-vendor-info system-get-version volume-list-info To configure an administrative user on NetApp storage, do the following: 1. Log into the NetApp storage system by using an SSH client (for example, PuTTY). 2. Use the useradmin command to ensure that the user has the needed role capabilities. 3. Do one of the following: Data source setup and device identification 139

140 140 OnCommand Insight Installation and Administration Guide Associate the user with the default "admin" or "root" user group. Create a custom group with these role capabilities. useradmin role add <user> -a login-http-admin,api-*,cli-rdfile,clioptions, cli-df,cli-lun,cli-ifconfig useradmin group add <group> -r <user> useradmin user add <user> -g <group> Note: To update the roles, use modify instead of add. Requirements IP address of the FAS storage controller and cluster partner Username and password for the controller and the partner FCP license and mapped/masked volumes required for OnCommand Insight discovery CIFS and/or NFS license and CIFS shares or NFS exports required for OnCommand Insight NAS discovery Access validation: Telnet into the FAS controller from the OnCommand Insight Server using the username and password. Note: Third-party software is not required. QLogic SANsurfer (SNMP) data source Configuring the data source for this vendor requires specific information. Inventory fields Field SANSurfer switch Poll interval (min) SNMP version SNMP community User name Password SNMP Auth Protocol Description Network address for the SANsurfer device, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Interval, in minutes, at which the data source should poll the device. V2 is the default. SNMP read-only community string used to access the device. SNMP name used to log in to the switch. Applies when using SNMP V3. SNMP password used to log in to the switch. Applies when using SNMP V3. Encryption type. MD5 is the default.

141 Data source setup and device identification 141 Enable trapping Minimum time between traps (sec) Fabric name Check box used to trigger acquisition upon receiving an SNMP trap from the device. If you mark this box, you must also activate SNMP notifications. Minimum elapsed time between acquisition attempts triggered by traps, in seconds. Fabric name to be reported by this data source (blank to report the fabric WWN). Performance field Field Perform poll interval (seconds): Description The recommended setting and default for the poll interval is 300 seconds. VMware This data source collects ESX Hosts information. Inventory fields Field Communication port requirement Virtual Center address User name Password Poll interval (min) Connection timeout (ms) Exclude VMs by Exclusion list (comma separated, or semicolon separated if comma is used in the value) Description http-80 https is the default. Network address for the VirtualCenter/vSphere server, specified as an IP (nnn.nnn.nnn.nnn format), or as a hostname that can be resolved through DNS. Name used to log in to the VMware server. You need an account with read-only privileges within Virtual Center/ vsphere. Password used to log in to the VMware server. Interval, in minutes, at which the data source should poll the device. Defaults to 20 minutes for VM Inventory. 60,000 milliseconds is the default. Optionally, choose to exclude ESX host IP or data center. Comma-separated list. Comma-separated list of devices, identified by a generic device ID, that will not be discovered by this data source.

142 142 OnCommand Insight Installation and Administration Guide Performance field Field Perform poll interval (seconds): Description The recommended setting and default for the poll interval is 300 seconds. Requirements Read-only privileges on all objects within Virtual Center. SDK access on the Virtual Center server Access validation: Log into Virtual Center Client using username and password. Verify that the SDK is enabled by entering: telnet <vc_ip> 443 Note: Third-party software is not required. Identifying hosts and tapes automatically with Auto Resolution (AR) OnCommand Insight can identify devices in your environment, determine types of those devices, and attach those devices to a host by using the Auto Resolution (AR) feature. You can enable or disable this option and you can configure AR settings. About this task You can configure the following AR options: Set a schedule for AR. Enable or disable AR manually using the Identify views. Enter domain names that can be appended to a host name when using DNS Lookup to resolve the host name. Set the way in which OnCommand Insight extracts and validates host or tape names during host or tape identification. You can resolve IP addresses and host names through DNS lookup. You can enable DNS lookup as a method to validate host names; you can match patterns of source names; or use the host name exactly as it appears in your Storage Resource Management (SRM) software. Set the methods and order in which OnCommand Insight performs the host or tape identification. Exclude specific storage vendors from AR. You might want to exclude specific vendors if you know, for example, that a specific host will become a legacy host and should be excluded from your new environment. You can determine whether AR is enabled or disabled by looking at the OnCommand Insight Client status bar.

143 Data source setup and device identification 143 Steps 1. Access the OnCommand Insight Client. 2. In the status bar, look at the AR icon: : AR is enabled : AR is disabled 3. To enable or disable AR or set the schedule, select the AR icon in the status bar. 4. In the Auto Resolution page of the Settings dialog box, enable or disable AR and set the schedule. Automatic host and tape resolution overview OnCommand Insight can identify devices in your environment automatically. Typically, after you set up data sources, you would use the automatic resolution (AR) feature for the next step in the identification process. During the AR setup, you configure the following information: Preferences and schedule Methods that OnCommand Insight uses to perform AR. You can set OnCommand Insight to use one of the following methods to identify devices: Delimiter pattern matching: OnCommand Insight uses the delimiter method to match the pattern to extract host names. This can be done for zone names, switch alias names, storage alias names, or Storage Resource Management (SRM) alias names for the generic device. You can set the character or characters used to delimit values and set the minimum host name length that the system uses to find hosts. For example, if your zones are named with a pattern combining the host name and the storage name, with the _ character as the separator, you can use the zone source method with the delimiter configured to use '_'. Say your zone names typically include the device name (such as, zone AAA_host3_access, where the device is host3. You can set up OnCommand Insight to resolve generic host devices automatically by looking for names that match your naming strategy. Regular expression use: You can create a regular expression for OnCommand Insight to use when resolving the host or tape name. This can be done from zone names or from switch, storage, or SRM alias names. As Is (SRM source only): Use this to use the host name exactly as it appears in the SRM software. If you use this, you can verify the host name by using DNS lookup or by using another validation process. Exclude specific storage vendors from the auto host or tape resolution process. After the host or tape resolution process is complete, OnCommand Insight shows the identified host name and IP address in OnCommand Insight views. Even after automatic host or tape resolution is completed, you have the option to override the AR identifications.

144 144 OnCommand Insight Installation and Administration Guide After OnCommand Insight tries to identify devices automatically, there might be some devices that OnCommand Insight cannot identify. You should identify these devices manually. Related tasks Identifying and managing FC generic devices on page 172 Identifying and managing iscsi sessions and NAS shares on page 190 Setting host and tape Auto Resolution schedule and preferences You can set the schedule and preferences for how you want the Auto Resolution (AR) process for hosts and tapes to function. About this task You can configure the following AR preferences: Set a schedule for AR. Enable or disable AR by setting the schedule to the Manual Only option. Enter domain names that can be appended to a resolved host name during DNS lookup to resolve the host name. Select whether you want to show a "connected to" alias instead of the standard port alias. Enable automatic host resolution for iscsi initiators and hosts accessing NFS shares by using DN lookup. If this checkbox is disabled, only-fc-based resolution will be performed. Steps 1. Do one of the following: From the OnCommand Insight Client Main Menu, select Tools > Settings > Auto Resolution. In the OnCommand Insight Client status bar, click the AR option. 2. In the Auto Resolution settings page, click the Preferences tab.

145 Data source setup and device identification Configure the AR schedule by selecting one of the following: Every time a change occurs in the environment Every day at a specific time At a set interval of time in hours, days, or weeks (for example, every 2 hours) Manually only using the FC Identify view or IP Identify view. This disables scheduling of automatic host resolution. 4. Complete the following: Option Domain Names Append domain name Allow underscore in host names Prefer 'connected to' alias Enable automatic resolution of IPs Description Configure one or more domain names that OnCommand Insight will append to the potential host name before the DNS lookup and validation. To include multiple names, separate them with semicolons. Check this to append the domain name to the resolved host name and display that in OnCommand Insight views. Check this to allow underscores in host names. Check this to use the "Connected to" alias instead of the standard port alias. Check this to enable automatic host resolution for iscsi initiators and hosts accessing NFS shares by using DNS lookup. If this checkbox is disabled, only FCbased resolution will be performed. See information about identifying and managing iscsi sessions and NAS shares.

146 146 OnCommand Insight Installation and Administration Guide Option Enable DNS lookup result processing Description Check this to enable post processing of names used in DNS lookups using regular expressions (as set up on the Methods tab). This option runs a regular expression on the name provided to the DNS lookup and returns the matching result as the resolution name rather than the name used for DNS lookup. This process further transforms the resulting name. See the full description and examples in the Auto Resolution Preference settings information for this view. 5. Click Apply to apply the changes. 6. Continue with the Methods and Storage and Tape Vendors tabs. Related tasks Identifying and managing iscsi sessions and NAS shares on page 190 Setting Auto Resolution methods on page 147 Selecting Auto Resolution storage and tape vendors on page 159 Related references Auto Resolution Preference settings on page 164 Enabling or disabling Auto Resolution by using the Identify views You can enable Auto Resolution (AR) so that OnCommand Insight can identify devices in your environment. You enable or disable AR on the Identify views. Before you begin You have configured Auto Resolution to run manually from the Identify views. About this task You can enable AR by setting a schedule using Tools > Settings > Auto Resolution or you can enable AR manually by using the Auto Resolution option in the FC Identify view or IP Identify view. Steps 1. Access the OnCommand Insight Client. 2. Select Configuration > IP Identify or Configuration > FC Identify. 3. At the upper right of the view, click the Auto Resolution green arrow. 4. To stop AR processing, click the red square. You can stop AR processing only before the DNS lookup has occurred as indicated by the blue bar:

147 Data source setup and device identification 147 A large blue bar of variable size moving from left to right indicates that DNS lookup has not finished and you can stop AR processing. A small, fixed-size blue bar moving back and forth indicates that DNS lookup has finished and you can no longer stop AR processing. Setting Auto Resolution methods OnCommand Insight can identify devices in your environment, determine device types, and attach devices to hosts using the Auto Resolution (AR) feature. You can set the method that OnCommand Insight uses to extract and validate host names during host identification. You can enable DNS lookup as a method to validate host names; you can match patterns of source names, or you can use the host name exactly as it appears in your Storage Resource Management (SRM) software. About this task Setting a method involves setting the following: Source of the data used to identify the host, for example, a switch alias, zone, or SRM. Method used to extract and validate host or tape names. This includes delimiter pattern matching or regular expression use (tape resolution can use only regular expression matching). The method that you choose depends upon the source naming strategy employed in your environment and affects the validation process used to validate the resolution. Delimiter method: Use delimiters when you want to match patterns of the source names. The host name is part of the source text, bounded by specific characters. For example, if your zones are named with a pattern combining the host name and the storage name, with the _ character as the separator, you can use the zone source method with the delimiter configured to use '_'. If you use delimiters, you must verify the host name using a DNS lookup. Regular expression: Use one or more regular expressions to identify host or tape name from source names. You might choose to use regular expressions if your source naming strategy is more complicated than what can be matched using the delimiter method. If you use regular expressions, you can verify the host or tape name by using DNS lookup or by using another validation process. Steps 1. Do one of the following: From the OnCommand Insight Client Main Menu, select Tools > Settings > Auto Resolution. In the OnCommand Insight Client status bar, click the AR option. 2. In the Auto Resolution settings page, click the Methods tab.

148 148 OnCommand Insight Installation and Administration Guide 3. In the Methods tab, to change the order in which the sources are used to identify hosts, click the source row and click Up or Down. 4. For the Re-evaluate column, do one of the following: Uncheck the Re-evaluate column: OnCommand Insight continues to apply the rule that successfully identified the device. In other words, identifications stick to the rule that completed the match. Check Re-evaluate: OnCommand Insight uses the checked rule to re-identify the device, again looking through all the rules in the order in which they appear. This is especially helpful if you change your strategy for device naming, such as naming with storage aliases. Without this check, you would have had to unidentify the device and configure AR again. With this check box enabled, OnCommand Insight can identify the device using your new strategy. The ability to migrate without unidentification enables you to preserve any annotations and policies that have been applied to the host. OnCommand Insight attempts to identify a device by using the rules in the order in which they appear. After identification is complete, OnCommand Insight typically uses the same rule that successfully performed the identification to process future identifications. OnCommand Insight does not run through the rules in order as it did before. However, you can change that by using the Re-evaluate check box. 5. Check the sources (for example, switch alias or zone) that should be used as a source to identify the host. There is a row for each combination of source, method, and validation. For example, SRM might have five lines. 6. To change the delimiters or regular expression used as the method to identify host names, do the following: a) Click the row. b) Click Configure.

149 7. Do one of the following: Data source setup and device identification 149 To configure a regular expression, see "Using regular expressions in host identification methods." To change the delimiter information, continue with the next step. (Applicable only with SRM). To use the host name exactly as it appears in the SRM software, check As Is. OnCommand Insight may or may not verify the host name using DNS. 8. If you selected a source with a Delimiters method, the Delimiters Configuration dialog box allows you to change the delimiter information (which represents how the data will be delimited, for example, with commas to separate one datum from the next). a) Delimiters: Enter the character used to separate the values of the devices. Defaults to an underscore (_) and dash (-). b) Minimum length of Host Name: Enter the minimum number of characters that OnCommand Insight should use to identify a host. OnCommand Insight performs DNS lookups only for host names that are this long or longer. c) Click OK. 9. Click Apply to apply the changes. 10. Navigate to the Storage and Tape Vendors tab. Related tasks Using regular expressions in host or tape identification methods on page 150 Related references Auto Resolution Methods settings on page 166

150 150 OnCommand Insight Installation and Administration Guide Using regular expressions in host or tape identification methods You can create a regular expression for OnCommand Insight to use when resolving the host or tape name. This can be done from zone names or from switch, storage, or SRM software alias names according to the methods specified in the Methods tab. Steps 1. Do one of the following: From the OnCommand Insight Client Main Menu, select Tools > Settings > Auto Resolution. In the OnCommand Insight Client status bar, click the AR option. 2. In the Auto Resolution settings page, click the Methods tab. 3. Check the sources (for example, switch alias or zone) that should be used as a source to identify the host. There is a row per combination of source, method, and validation. For example, SRM might have five lines. 4. To change the method (delimiters or regular expression) used to identify host names, do the following: a) Click the row. b) Click Configure. 5. To change the regular expression information (which lets you enter pattern matching expressions), do the following.

151 Data source setup and device identification 151 a) To add a new expression, click Add. Add a rule to identify host names for generic devices. b) To edit an expression, click the RegExp field and click the [...] icon to open an Editor dialog box. Enter the expression directly into the field or enter it in the Editor dialog box. The icon becomes visible only after you click in the RegExp field. c) To make the expression case sensitive, check Case Sensitive. d) To move an expression up or down in the list, click the expression and click either Up or Down. The order in which the expression appears is the order in which OnCommand Insight evaluates expressions. e) To preview the resulting host identification based on the set of expressions in the list, click Preview. f) To validate each potential host name against DNS, check DNS Validation. g) In the No Match section, view the list of generic devices that do not match any of the regular expressions entered. Use this information to add or change an expression so that these devices are resolved. h) Click OK to return to the Methods tab.

152 152 OnCommand Insight Installation and Administration Guide 6. In the Methods tab, to change the order in which the sources are used to identify hosts, click the source row and click Up or Down. 7. Click Apply to apply the changes. 8. Continue with the Storage and Tape Vendors tab. Regular expression examples If you have selected the regular expression approach as your source naming strategy, you can use the following regular expression examples as guides for your own expressions used in the OnCommand Insight automatic resolution methods. Formatting regular expressions When creating regular expressions for OnCommand Insight Automatic Resolution, you can configure output format by entering values in a field named FORMAT. The default setting is \1, which means that a zone name that matches the regular expression is replaced by the contents of the first variable created by the regular expression. In a regular expression, variable values are created by parenthetical statements. If multiple parenthetical statements occur, the variables are referenced numerically, from left to right. The variables can be used in the output format in any order. Constant text may also be inserted in the output, by adding it to the FORMAT field. For example, if the zone naming convention is: [Zone number]_[data center]_[hostname]_[device type]_[interface number] You might have the following zone names: S123_Miami_hostname1_filer_FC1 S14_Tampa_hostname2_switch_FC4 S3991_Boston_hostname3_windows2K_FC0 S44_Raleigh_hostname4_solaris_FC1 And you might want the output to be in the format: [hostname]-[data center]-[device type] To do this, you need to capture the host name, data center, and device type fields in variables, and use them in the output. The following regular expression would do this:.*?_([a-za-z0-9]+)_([a-za-z0-9]+)_([a-za-z0-9]+)_.* Because there are three sets of parentheses, the variables \1, \2 and \3 would be populated. You could then use the following format to ensure output in your preferred format: \2-\1-\3

153 Data source setup and device identification 153 Your output would thus be: hostname1-miami-filer hostname2-tampa-switch hostname3-boston-windows2k hostname4-raleigh-solaris The hyphens between the variables provide an example of constant text which is inserted in the formatted output. Example 1 showing zone names In this example, you use the regular expression to extract a Host name from the zone name. You could create a regular expression if you have something similar to the following zone names: S0032_myComputer1Name-HBA0 S0434_myComputer1Name-HBA1 S0432_myComputer1Name-HBA3 The regular expression that you could use to capture the host name would be: S[0-9]+_([a-zA-Z0-9]*)[_-]HBA[0-9] The outcome is a match of all zones beginning with S that are followed by any combination of digits, followed by an underscore, the alphanumeric hostname (mycomputer1name), an underscore or hyphen, the capital letters HBA, and a single digit (0-9). The hostname alone is stored in the \1 variable. The regular expression can be broken into its components: "S" represents the zone name and begins the expression. This matches only an "S" at the beginning of the zone name. The characters [0-9] in brackets indicate that what follows "S" must be a digit between 0 and 9, inclusive. The + sign indicates that the occurrence of the information in the preceding brackets has to exist 1 or more times. The _ (underscore) means that the digits after S must be followed immediately by only an underscore character in the zone name. In this example, the zone naming convention uses the underscore to separate the zone name from the host name. After the required underscore, the parentheses indicate that the pattern contained within will be stored in the \1 variable. The bracketed characters [a-za-z0-9] indicate that the characters being matched are all letters (regardless of case) and numbers. The * (asterisk) following the brackets indicates that the bracketed characters occur 0 or more times. The bracketed characters [_-] (underscore and dash) indicate that the alphanumeric pattern must be followed by an underscore or a dash.

154 154 OnCommand Insight Installation and Administration Guide The letters HBA in the regular expression indicate that this exact sequence of characters must occur in the zone name. The final set of bracketed characters [0-9] match a single digit from 0 through 9, inclusive. Example 2 In this example, skip up to the first underscore "_" then match E and everything after that up to the second "_" then skip everything after that. Zone: Z_E2FHDBS01_E1NETAPP Hostname: E2FHDBS01 RegExp:.*?_(E.*?)_.*? Example 3 The parentheses "( )" around the last section in the Regular Expression (below) identifies which part is the hostname. If you wanted VSAN3 to be the host name, it would be: [a-za-z0-9]+_([a-za- Z0-9]+).* Zone: A_VSAN3_SR48KENT_A_CX2578_SPA0 Hostname: SR48KENT RegExp: [a-za-z0-9]+_[a-za-z0-9]+_([a-za-z0-9]+).* Example 4 showing a more complicated naming pattern You could create a regular expression if you have something similar to the following zone names: mycomputername123-hba1_symm1_fa3 mycomputername123-hba2_symm1_fa5 mycomputername123-hba3_symm1_fa7 The regular expression that you could use to capture these would be: ([a-za-z0-9]*)_.* The \1 variable would contain only mycomputername123 after being evaluated by this expression. The regular expression can be broken into its components: The parentheses indicate that the pattern contained within will be stored in the \1 variable. The bracketed characters [a-za-z0-9] mean that any letter (regardless of case) or digit will match. The * (asterisk) following the brackets indicates that the bracketed characters occur 0 or more times. The _ (underscore) character in the regular expression means that the zone name must have an underscore immediately following the alphanumeric string matched by the preceding brackets. The. (period) matches any character (a wildcard).

155 The * (asterisk) indicates that the preceding period wildcard may occur 0 or more times. In other words, the combination.* indicates any character, any number of times. Example 5 showing zone names without a pattern You could create a regular expression if you have something similar to the following zone names: mycomputername_hba1_symm1_fa1 mycomputername123_hba1_symm1_fa1 The regular expression that you could use to capture these would be: (.*?)_.* The \1 variable would contain mycomputername (in the first zone name example) or mycomputername123 (in the second zone name example). This regular expression would thus match everything prior to the first underscore. The regular expression can be broken into its components: The parentheses indicate that the pattern contained within will be stored in the \1 variable. The.* (period asterisk) match any character, any number of times. The * (asterisk) following the brackets indicates that the bracketed characters occur 0 or more times. The? character makes the match non-greedy. This forces it to stop matching at the first underscore, rather than the last. The characters _.* match the first underscore found and all characters which follow it. Example 6 showing computer names with a pattern You could create a regular expression if you have something similar to the following zone names: Storage1_Switch1_myComputerName123A_A1_FC1 Storage2_Switch2_myComputerName123B_A2_FC2 Storage3_Switch3_myComputerName123T_A3_FC3 The regular expression that you could use to capture these would be:.*?_.*?_([a-za-z0-9]*[abt])_.* Because the zone naming convention has more of a pattern, we could use the above expression, which will match all instances of a hostname (mycomputername in the example) that ends with either an A, a B, or a T, placing that hostname in the \1 variable. The regular expression can be broken into its components: Data source setup and device identification 155 The.* (period asterisk) match any character, any number of times. The? character makes the match non-greedy. This forces it to stop matching at the first underscore, rather than the last.

156 156 OnCommand Insight Installation and Administration Guide The underscore character matches the first underscore in the zone name. Thus, the first.*?_ combination matches the characters Storage1_ in the first zone name example. The second.*?_ combination behaves like the first, but matches Switch1_ in the first zone name example. The parentheses indicate that the pattern contained within will be stored in the \1 variable. The bracketed characters [a-za-z0-9] mean that any letter (regardless of case) or digit will match. The * (asterisk) following the brackets indicates that the bracketed characters occur 0 or more times. The bracketed characters in the regular expression [ABT] match a single character in the zone name which must be A, B, or T. The _ (underscore) following the parentheses indicates that the [ABT] character match must be followed up an underscore. The.* (period asterisk) match any character, any number of times. The result of this would therefore cause the \1 variable to contain any alphanumeric string which: was preceded by some number of alphanumeric characters and two underscores was followed by an underscore (and then any number of alphanumeric characters) had a final character of A, B or T, prior to the third underscore. Example 7 Zone: mycomputername123_hba1_symm1_fa1 Hostname: mycomputername123 RegExp: ([a-za-z0-9]+)_.* Example 8 This example finds everything before the first _. Zone: MyComputerName_HBA1_Symm1_FA1 MyComputerName123_HBA1_Symm1_FA1 Hostname: MyComputerName RegExp: (.*?)_.* Example 9 This example finds everything after the 1st _ and up to the second _. Zone: Z_MyComputerName_StorageName Hostname: MyComputerName RegExp:.*?_(.*?)_.*?

157 Data source setup and device identification 157 Example 10 This example extracts "MyComputerName123" from the zone examples. Zone: Storage1_Switch1_MyComputerName123A_A1_FC1 Storage2_Switch2_MyComputerName123B_A2_FC2 Storage3_Switch3_MyComputerName123T_A3_FC3 Hostname: MyComputerName123 RegExp:.*?_.*?_([a-zA-Z0-9]+)*[ABT]_.* Example 11 Zone: Storage1_Switch1_MyComputerName123A_A1_FC1 Hostname: MyComputerName123A RegExp:.*?_.*?_([a-zA-z0-9]+)_.*?_ Example 12 The ^ (circumflex or caret) inside square brackets negates the expression, for example, [^Ff] means anything except upper or lower case F and [^a-z] means everything except lower case a to z, and in the case above, anything except the _. The format statement adds in the "-" to the output host name. Zone: mhs_apps44_d_a_10a0_0429 Hostname: mhs-apps44-d RegExp: ([^_]+)_([AB]).*Format in OnCommand Insight: \1-\2 ([^_]+)_ ([^_]+)_([^_]+).*Format in OnCommand Insight: \1-\2-\3 Example 13 In this example, the storage alias is delimited by "\" and the expression needs to use "\\" in order to define that there are actually "\" being used in the string, and that those are not part of the expression itself. Storage Alias: \Hosts\E2DOC01C1\E2DOC01N1 Hostname: E2DOC01N1 RegExp: \\.*?\\.*?\\(.*?) Example 14 This example extracts "PD-RV-W-AD-2" from the zone examples. Zone: PD_D-PD-RV-W-AD-2_01

158 158 OnCommand Insight Installation and Administration Guide Hostname: PD-RV-W-AD-2 RegExp: [^-]+-(.*-\d+).* Example 15 The format setting in this case adds the "US-BV-" to the hostname. Zone: SRV_USBVM11_F1 Hostname: US-BV-M11 RegExp: SRV_USBV([A-Za-z0-9]+)_F[12] Format: US-BV-\1 Using the regular expression editor in host or tape identification methods When you are setting up the automatic resolution (AR) methods, you can enter a regular expression using a wizard or you can use a regular expression editor, where you can enter the expression directly. This process discusses how to use the editor. Steps 1. From the OnCommand Insight Client Main Menu, select Tools > Settings > Auto Resolution. 2. In the Auto Resolution settings page, click the Methods tab. 3. To change regular expression used as the method to identify host or tape names, do the following: a) Click the row. b) Click Configure. 4. To add a new expression, click Add. 5. To edit an expression, click the RegExp field and click the [...] icon to open an Editor dialog box. Enter the expression directly into the field or enter it in the Editor dialog box. The icon becomes visible only after you click in the RegExp field. 6. In the Regexpr field, enter the expression. As you type the expression, OnCommand Insight highlights matches to your specifications in green, with a red underline to highlight matches for the parenthetical characters in the expression. If your expression is invalid, OnCommand Insight highlights the Regexp field in yellow. To obtain help and examples that show regular expression pattern-match characters, entities, and more, click the "help with regular expressions" link at the bottom. The following example shows part of the host name in the zone naming identification strategy. OnCommand Insight has found matching host names as shown in green.

159 Data source setup and device identification Use the Test Text field to enter text to test your expression. If your test is valid, OnCommand Insight highlights it in green. If it is invalid, it appears in yellow. 8. Click OK. You return to the Regexp wizard where your expression now appears. Selecting Auto Resolution storage and tape vendors You can add or exclude specific storage and tape vendors for auto resolution. You might want to exclude specific vendors if you know, for example, that a specific host will become a legacy host and should be excluded from your new environment. Steps 1. Do one of the following: From the OnCommand Insight Client Main Menu, select Tools > Settings > Auto Resolution.

160 160 OnCommand Insight Installation and Administration Guide In the OnCommand Insight Client status bar, click the AR option. 2. In the Auto Resolution Settings page, click the Storage and Tape Vendors tab. 3. To exclude a vendor from the host identification process, do the following: a) Click Add/Remove. b) In the list of Available Vendors in the Select Storage and Tape Vendors dialog box, click the vendor that you want to exclude. c) To look for vendors, click the magnifying glass icon in the left pane. Enter part of the name. The list shows all vendors that contain the entered text. d) Select the vendor name or names to add. e) Click Add. f) Click OK. 4. To remove a vendor so that it is no longer excluded from the host identification process, do the following: a) Click Add/Remove. b) In the list of Selected Vendors in the Select Storage and Tape Vendors dialog box, click the vendor that you want to remove from the exclusion list. c) To look for vendors, click the magnifying glass icon in the left pane. d) Enter part of the name. The list shows all vendors that contain the entered text. e) Click Remove. f) Click OK.

161 OnCommand Insight updates the list of vendors to be excluded from the host identification process. 5. Click OK. Data source setup and device identification 161 Related references Storage and Tape Vendors settings for Auto Resolution on page 171 Re-identifying generic devices with automatic resolution Automatic host or tape resolution (AR) runs once every minute and looks at the unidentified generic devices and applies the configured techniques. Previously identified generic devices are not ignored. For example, if a generic device was identified using zone information and that zone information later changes (to reflect a real change to a host), AR responds by re-identifying the device. About this task Re-identification is not exactly the same as the initial identification process. When the device is first identified, OnCommand Insight applies the configured source and methods in order. The first method that results in a validated host name is the one that is used. In contrast, in re-identification, OnCommand Insight considers only the source and method from the initial identification. For example, imagine a generic device and an AR configuration with the following two sources and identification methods: Storage Resource Management (SRM) as a source and use of a regular expression as the method Zone as a source and use of delimiters as the method The SRM and regular expression fail, but the zone and the delimiter method succeeds. The generic device is identified. Later, the environment might change so that the SRM can succeed. However, this is not applicable to the AR re-identification, and only the zone source combined with the delimiter method is used. This is because for the SRM to be used, you would need to manually unidentify the generic device and let the initial identification process run until it finished. From then on, only the SRM and regular expression would be used for the re-identification of the generic device. The following issues also apply to re-identification: Re-identification is performed only if the configured source and method is enabled. If you remove the checkmark from the configured rule, re-identification using that source and method stops. DNS changes are ignored during re-identification. If, through DNS validation, OnCommand Insight records an IP address for the resulting host name, that IP will be used for future identifications even if the DNS server returns a different address. If the re-identification fails, the previous identification is preserved.

162 162 OnCommand Insight Installation and Administration Guide Auditing automatic host and tape resolution You can audit the complex process of automatic resolution (AR) for hosts or tapes. You can also audit identification or re-identification events. About this task OnCommand Insight shows the following statuses related to identification: Status Not identified automatically Identification failed Identified to "X" Identified to "X, reidentification disabled Identified to "X" valid Manually identified Matches "X" storage vendor, ignored Description All AR rules failed or AR has never run. AR produced a possible identification, but it conflicts with existing identifications. Initial identification Re-identification was skipped because the method used to identify the device initially is now disabled in the AR configuration. Re-identification did not detect any changes A OnCommand Insight user performed a manual identification. AR will not attempt to re-identify this entry. AR identified the generic device as storage and not a host and ignores the result. If AR encounters warnings, it appends the text "(with warnings)" to the status value. Use the Resolution Details detail view to find out the nature of any warnings. Warning messages are displayed only on the following two statuses: Identified to "X" Identification to "X" valid The FC Identify view shows warnings also in the Errors/Warnings column, which represent errors or warnings related to manual identification. These are not the same warnings described here that AR generates. Steps 1. From the OnCommand Insight Open menu, select Configuration > FC Identify. 2. In the FC Identify view, review the Audit column. 3. To see detailed information about the AR process, in the OnCommand Insight status bar, click the Resolution Details icon.

163 Data source setup and device identification 163 The Resolution Details detail view shows the sequence of identification activities related to the generic device selected in the FC Identify view. Settings for Auto Resolution OnCommand Insight can identify devices in your environment, determine the type of device, and attach the device to a host with the Auto Resolution (AR) feature. You can also identify tapes using this option. Navigation From the OnCommand Insight Client, select Tools > Settings > Auto Resolution. You can also click the AR option in the OnCommand Insight Client status bar. The Auto Resolution page appears. Note: To initiate AR manually, select Open menu > Configuration and select either IP Identify or FC Identify. From one of these views, click the AR button. Description The Auto Resolution page includes the following tabs: Preferences tab Methods tab Storage and Tape Vendors tab You can determine whether Auto Resolution is enabled by looking at the AR status indicator on the OnCommand Insight Client status bar. Related concepts Automatic host and tape resolution overview on page 143 Related tasks Identifying hosts and tapes automatically with Auto Resolution (AR) on page 142

164 164 OnCommand Insight Installation and Administration Guide Auto Resolution Preference settings You can set a schedule for Auto Resolution, optionally enter domain names that will be appended to the resolved host or tape name, and enable Auto Resolution of IP hosts. Navigation From the OnCommand Insight Client, select Tools > Settings > Auto Resolution. You can also click the AR option in the OnCommand Insight Client status bar. The Auto Resolution page is displayed. Field descriptions Set auto resolution schedule Domain names Append domain name Choose one of the options to enable OnCommand Insight to resolve host or tape identification: Every time a change occurs in the environment Every day at a specific time At a set interval of time in hours, days, or weeks (for example, every 2 hours) Manually only using the IP Identify view. This disables scheduling of automatic host or tape resolution. Enter one or more domain names that OnCommand Insight will append to the resolved host name during the DNS lookup and validation. To include multiple names, separate them with semicolons. Check this append the domain name to the resolved host name and display that in OnCommand Insight views.

165 Data source setup and device identification 165 Allow underscore in host names Prefer 'connected to' alias Enable automatic resolution of IPs Enable DNS lookup result processing Check this to allow underscores in host names. Check this to use the "Connected to" alias instead of the standard port alias. Check this to enable automatic host resolution for iscsi initiators and hosts accessing NFS shares by using DNS lookup. If this check box is disabled, only FC-based resolution will be performed. Check this to enable post processing of names used in DNS lookups using regular expressions (as set up on the Methods tab). This option runs a regular expression on the name provided to the DNS lookup and returns the matching result as the resolution name rather than the name used for DNS lookup. This process further transforms the resulting name. Regular expression Format The regular expression you want to use to post-process the name before assigning it to a device. Indication of how to format the matching text to get the result you want. "\n" substitutes the text that matches the "nth" set of parentheses. For example, to remove the domain name from the source text of "hosta.netapp.com", the regular expression is "(.*)\.netap\.com" and the format is "\1" which retains the characters in the first set of parentheses. The following examples illustrate the post-processing results. Intent Source text Regular expression Format Result Retain entire source text Retain prefix and suffix Replace text in 1st parentheses with "app" and retain text in 2nd set of parentheses host_123 (.*) \1 host_123 host_123 (.*)_(.*) \1\2 host_123 host_123 (.*)_(.*) app\2 app123

166 166 OnCommand Insight Installation and Administration Guide Intent Source text Regular expression Format Result Remove the text in the 1st set of parentheses and replace the text in the 2nd set of parentheses with "app" and insert a dash. host_123 (.*)_(.*) app-\2 app-123 Retain text in 1st set of parentheses but remove domain name hosta.netapp. com (.*)\.netapp \.com \1 hosta Related concepts Automatic host and tape resolution overview on page 143 Related tasks Setting host and tape Auto Resolution schedule and preferences on page 144 Identifying hosts and tapes automatically with Auto Resolution (AR) on page 142 Auto Resolution Methods settings You can set up the methods that OnCommand Insight uses to extract and validate host or tape names. You can configure OnCommand Insight to validate switches by DNS Lookup. You can also set the order in which OnCommand Insight performs the name extraction methods. For example, for host names encoded as part of a switch alias, you can extract host names by entering delimiters or by using regular expressions to enter pattern search criteria. Navigation From the OnCommand Insight Client, select Tools > Settings > Auto Resolution. Click the Methods tab. You can also click the AR option in the OnCommand Insight Client status bar. The Settings Auto Resolution page appears. Select the Methods tab.

167 Data source setup and device identification 167 Field descriptions Source Method Check the source types for which you want to extract information. The order in which the rows appear is the order in which OnCommand Insight extracts and validates host or tape information. To move the row up or down, click Up or Down. Sources used to identify the host can include the following: Zone names containing embedded host names Switch alias names containing embedded host names Storage alias names containing embedded host names Storage Resource Management (SRM) software Sources used to identify the tape can include the following: Zone names containing embedded host names Switch alias names containing embedded host names Indicates the type of method by which OnCommand Insight extracts and validates host or tape information for the selected source. To configure the method, select the row and click Configure. Methods include the following: Delimiters: Use delimiters when you want to match patterns of the source names. (Applies to host, not tape, resolution.) The host name is part of the source text, bounded by specific characters. For example, if your zones are named with a pattern combining the host name and the

168 168 OnCommand Insight Installation and Administration Guide storage name, with the _ character as the separator, you can use the zone source method with the delimiter configured to use '_'. Ex: blade14_ds4800_1 (where blade14 is the host name) If you use delimiters, you must verify the host name using a DNS lookup. Regular expressions: Use one or more regular expressions to identify the host or tape name from source names. If you use regular expressions, you can verify the host or tape name by using DNS lookup or by using another validation process. As Is (SRM source only): Use this to use the host name exactly as it appears in the Storage Resource Management (SRM) software. If you use this, you can verify the host name by using DNS lookup or by using another validation process. (Applies to host, not tape, resolution.) Validation Reevaluate Indicates whether OnCommand Insight validates each resolved host or tape name for the selected source. With DNS lookup, a host name will be considered valid if it is found as a name in the DNS servers that the OnCommand Insight Server can access. Indication of whether to re-evaluate the rule. OnCommand Insight attempts to identify a device by using the rules in the order in which they appear. After identification is complete, OnCommand Insight typically uses the same rule that successfully performed the identification to process future identifications. OnCommand Insight does not run through the rules in order as it did before. However, you can change that by using the Re-evaluate checkbox. Do one of the following: Uncheck the Re-evaluate column: OnCommand Insight continues to apply the rule that successfully identified the device. In other words, identifications stick to the rule that completed the match. Check Re-evaluate: OnCommand Insight uses the checked rule to re-identify the device, again looking through all the rules in the order in which they appear. This is especially helpful if you change your strategy for device naming such as naming with storage aliases. Without this verification, you would have had to "unidentify" the device and configure AR again. With this check box enabled, OnCommand Insight can identify the device using your new strategy. The ability to migrate without having to unidentify the device enables you to preserve any annotations and policies that have been applied to the host. Options Configure Choose this to change the delimiter or regular expression method to extract host or tape information from the selected source. Up/Down Use this to move the selected source row up or down in the table.

169 Data source setup and device identification 169 Related concepts Automatic host and tape resolution overview on page 143 Related tasks Setting Auto Resolution methods on page 147 Identifying hosts and tapes automatically with Auto Resolution (AR) on page 142 Regular Expression wizard for Auto Resolution Use this wizard to enter a regular expression that OnCommand Insight will use to identify host names for generic devices. Navigation You can access this wizard by doing one of the following: From the OnCommand Insight Client menu, select Tools > Settings > Auto Resolution. The Auto Resolution Preferences tab displays. Click the Methods tab. Click a source that shows a Regular Expression method and click Configure. In the OnCommand Insight Client status bar, click the AR option. The Auto Resolution > Preferences tab displays. Field descriptions Regular Expressions table DNS validation Preview section No Match section Regexp: Click in this field and enter expression text directly or open an Editor dialog box, where you can enter expression text. Case sensitive: Check this to make your expression case sensitive. Format: OnCommand Insight uses this replacement string to format the string that is extracted using the expression to format the potential host or tape name. Includes an optional prefix, suffix, or both. Matches: Displays the number of generic devices that match the expression. Validates each potential host name against DNS lookup. Displays a preview of the application of the set of expression rules to extract host or tape names. OnCommand Insight runs resolution automatically after you edit an expression rule, delete a rule, or change the order of rules. Displays a list of generic devices that do not match any of the regular expressions entered. Use this information to add or change an expression so that these devices are resolved. Options Add Adds a rule to identify tape names or host names for generic devices.

170 170 OnCommand Insight Installation and Administration Guide Remove Removes the rule. Up Down Moves the expression up the list. The order in which the expression appears is the order in which OnCommand Insight evaluates expressions. Moves the expression down the list. Preview Displays the resulting host or tape identification based on the expressions and the order of expressions. Related concepts Automatic host and tape resolution overview on page 143 Related tasks Using regular expressions in host or tape identification methods on page 150 Identifying hosts and tapes automatically with Auto Resolution (AR) on page 142 Regular Expression Editor for Auto Resolution Use this editor to enter a regular expression that OnCommand Insight will use to identify host names for generic devices. Navigation From the OnCommand Insight Open menu, select Tools > Settings > Auto Resolution. The Auto Host Resolution Preferences tab appears. Click the Methods tab. Click a source that shows a Regular Expression method and click Configure. Click in the Regexp field to display the Regular Expression Editor. You can also click the AR option in the OnCommand Insight Client status bar. The Auto Resolution > Preferences tab appears. Field descriptions Regexp Switch alias names Test text Enter the expression text here for the regular expression. If the expression is invalid, OnCommand Insight highlights the Regexp field in yellow. To display additional information about the regular expression pattern-match characters and qualifiers, click the link at the bottom. As you type the expression, OnCommand Insight highlights any matches to the specifications in green. A red underline highlights those matches to the characters in parentheses within the expression. Enter any additional text you wish to verify against the expression.

171 Data source setup and device identification 171 Options Click here for help on regular expressions Displays information about regular-expression matching rules, character classes, quantifiers, and common mistakes made in regular expression development. Related tasks Using regular expressions in host or tape identification methods on page 150 Storage and Tape Vendors settings for Auto Resolution You can exclude vendors from the automatic host and tape resolution. Because these vendor devices should be considered storage arrays or tapes, OnCommand Insight should avoid the vendors of the storage and tape devices present in your environment to avoid potentially misidentifying the devices as hosts. You might want to exclude a vendor if you know, for example, that your environment includes legacy devices that you do not want to include in this storage structure. Navigation From the OnCommand Insight Client, select Tools > Settings > Auto Resolution. Click the Storage and Tape Vendors tab. You can also click the AR option in the OnCommand Insight Client status bar. The Auto Resolution settings page appears. Field description Storage and tape vendors are each assigned 3-byte identifiers when they register with the IEEE. Those 3-byte identifiers are part of the WWN. OnCommand Insight compares a device's WWN to this list to determine whether the device is a storage array or a tape. Vendor names Indicates the vendors that are excluded from automatic host resolution. Vendor names are specified in the IEEE Registration Authority's list of Organizationally Unique Identifiers (OUI). Identification Indicates that the vendor should be excluded from automatic host resolution. Option Add/Remove Click this to add or remove a vendor to or from the vendor exclusion list. Related concepts Automatic host and tape resolution overview on page 143

172 172 OnCommand Insight Installation and Administration Guide Related tasks Selecting Auto Resolution storage and tape vendors on page 159 Identifying hosts and tapes automatically with Auto Resolution (AR) on page 142 Identifying and managing FC generic devices Fibre Channel (FC) devices that cannot be identified automatically using the OnCommand Insight Auto Resolution (AR) feature as well as devices identified incorrectly or those you chose not to identify automatically are referred to as generic devices. Generic devices include hosts, ports, HBAs, disk storage, tapes, and switches that could not be identified automatically. You can use OnCommand Insight to identify them manually. About this task FC switches that are monitored by OnCommand Insight sometimes report back about devices whose identity is unknown. Each unknown port on such a device is reported as a generic device until it is identified. You should identify these generic devices so that you can obtain meaningful data about them. You can do the following tasks related to generic devices: View a list of generic devices. Identify FC-based generic devices manually. Set the host resolution method for selected devices. Delete FC-based device identification. Delete inactive devices. Audit device identification. Generic devices overview Each unknown port in a Fibre Channel (FC) environment is reported as a generic device until it is identified. A generic device can be any of the following: A host, storage, or switch port node. A host. Hosts can almost always be identified automatically by OnCommand Insight data sources. A switch device port. Switch ports are generally identified automatically by OnCommand Insight data sources and rarely require manual identification. A host bus adapters (HBA) with one or more ports. A disk storage array or device with one or more ports. Storage arrays are generally identified automatically as soon as the correct data source is configured. In some cases, however, you might have to identify a storage array manually.

173 A tape device. You must identify all generic tape devices manually. They are not discovered automatically by OnCommand Insight data sources. How OnCommand Insight displays generic devices When OnCommand Insight detects an unidentified device, it creates a new generic device that is visible throughout OnCommand Insight. You can see generic devices in the following places: Generic Devices main view FC Identify view Topology view Other main views Generic devices shown in Generic Devices main view Data source setup and device identification 173 Use the Generic Devices main view to see a list of generic devices in your environment. From this list, you can select a device and identify it. OnCommand Insight then displays the FC Identify view. After a device is identified, it no longer appears on the Generic Devices main view. Generic devices shown in the FC Identify view You should identify any unknown device that is listed. You can do this using the FC Identify view. Once an unknown device is identified, it still shows up on the FC Identify view. This lets you change its identification as necessary. See "Identifying generic devices using the FC Identify view." Generic devices shown in Topology view OnCommand Insight shows a generic device as an icon in the Topology view. You can identify the device from here.

174 174 OnCommand Insight Installation and Administration Guide After a device is identified, the device no longer shows on the Topology view as a generic device icon. See "Identifying generic devices from the Topology view." Viewing a list of generic devices Fibre Channel (FC) switches that are monitored by OnCommand Insight sometimes report back about devices whose identity is unknown. You can review a list of unknown ports or generic devices. You might want to review the list of generic devices to see those that are still unidentified. About this task After you identify a device, it no longer appears on the Generic Devices main view. Steps 1. Do one of the following: From the OnCommand Insight Open menu, select Inventory > Generic Devices. From the Shortcut bar, select Inventory > Generic Devices. 2. Review the list of generic devices. For descriptions of the columns, see "Generic Devices main view."

175 Data source setup and device identification 175 Generic Devices main view Fibre Channel switches that are monitored by OnCommand Insight sometimes report back about devices whose identity is unknown. Each unknown port on such a device is reported as a generic device until it is identified. Use this view to identify those FC-based devices that OnCommand Insight did not identify as hosts. After you identify a device, it no longer appears on the Generic Devices main view. Navigation You can access this main view in one of the following ways. From the OnCommand Insight Open menu, select Inventory > Generic Devices. From the navigation pane, select Inventory > Generic Devices. Column descriptions A host can have multiple ports connected to multiple switches; multiple generic devices might be identified as a single host. A host can have multiple IPs, and multiple IPs might be identified as a single host. For details about data source setup, device identification and data acquisition, see the OnCommand Insight Installation and Administration Guide. The following information appears in the main view for each generic device, if available. This information is reported by the data source that discovers the generic device. All unidentified FC devices are called generic devices until they are identified as a host, storage, or tape. After that happens, they are no longer generic devices, and no longer display on the Generic Devices view. However, the Identify views show all identifications made in OnCommand Insight, so you can review, update and correct identifications as needed. WWN Vendor Model FC Port Count Last Report Time World Wide Name assigned to the device. The name of the vendor who sells the generic device based on industry standard WWN allocation ranges. The device manufacturer's model number. The number of licensed ports on the device. Date and time when the information about the device was last received.

176 176 OnCommand Insight Installation and Administration Guide icon (Is the device offline?) An icon in this column indicates that the device is inactive (offline). Options To see details for a particular device, click on the device in the Generic Devices main view. At the bottom of the OnCommand Insight Client window, in the icon bar, click the Properties icon. Generic Devices Properties Select this to display the Generic Devices Properties view for the selected device in a separate window, allowing you to hold the properties of one device while selecting another device in the main view. From the Generic Devices main view, right-click to show a pop-up menu containing the following options. If other OnCommand Insight modules are installed, additional options appear. See the documentation for those modules, as appropriate. Identify Delete Inactive Device Analyze Select this to identify the selected device manually in a wizard. Removes the selected device, typically after you decommission it from your environment. OnCommand Insight confirms the request before removing the device from the database. Before using this option, make sure that the device is marked as inactive. An icon indicating whether the device is offline appears in this view. The device's icon in the Topology view should be grayed, as well as the corresponding row in the inventory display. There should not be any links from the device to other devices in the Topology view. This happens automatically when you remove the data source corresponding to the device. If no inactive devices exist, this option is disabled. See information about deleting inactive devices. Shows the performance information for the selected resource. This requires the OnCommand Insight Perform license. Generic Device Properties detail view Use this view to see detailed information about the generic device selected in the Generic Devices main view. Navigation This detail view is available after clicking a device in the Generic Devices main view. You can access this detail view in one of the following ways: From the OnCommand Insight Client Main Menu, select View > Detail Views > Properties. At the bottom of OnCommand Insight Client view, click the Properties detail view icon.

177 Attribute Descriptions The amount of information obtained during acquisition varies by manufacturer and model, so the information available varies. OnCommand Insight can report only on information that is available from the generic device itself, as reported by the data source that discovered the device. IP address Driver name WWN Vendor Model The IP address assigned to the device. The name of the driver managing access to the generic device. The World Wide Name assigned to the device. The name of the vendor who sells the generic device based on industry standard WWN allocation ranges. The device manufacturer's model number. FC Port Count The number of licensed ports on the device. Firmware The version of the firmware running on the device. Data source setup and device identification 177 Identifying FC-based generic devices manually Identify generic devices so that OnCommand Insight can obtain meaningful data about them. If you don't identify them, OnCommand Insight cannot provide data about them. You can identify generic devices in multiple ways. The process is essentially the same regardless of the view you use or the type of device you are trying to identify. About this task You can identify generic devices in the following ways: After viewing a list of generic devices and selecting one to act on using the Generic Devices main view. Using this view is a convenient way to find all generic devices and then act on one. From the FC Identify view. By importing a list of ports and their device names from a comma-separated file. You might want to do this if you have all your port and device name information gathered in one file. In that case, this method might be more efficient. After viewing a device's configuration map in the Topology view and finding a generic device in the map. This method is convenient if you are on the Topology map and spot a generic device. By adding a device to the list of generic devices and then identifying it. You might need to do this if the device is totally unknown to OnCommand Insight.

178 178 OnCommand Insight Installation and Administration Guide Identifying generic devices from the Generic Devices main view Identify generic devices starting from the Generic Devices main view. Identify generic devices so that OnCommand Insight can obtain meaningful data about them. Using this view is a convenient way to find all generic devices and then act on one. Steps 1. Do one of the following: From the OnCommand Insight Open menu, select Inventory > Generic Devices. From the Shortcut bar, select Inventory > Generic Devices. 2. In the Generic Devices view, do one of the following: Select Action > Identify Selected. Right-click and select Identify Selected. 3. In the Identify Selected view, click on a device that matches the one you want to identify. 4. Click OK. OnCommand Insight updates the table in the Generic Devices main view. Identifying generic devices using the FC Identify view After looking at a list of unidentified host HBA ports, disk storage paths, tape device ports, and switch ports, you can identify generic devices. Identify generic devices so that OnCommand Insight can obtain meaningful data about them. Steps 1. From the OnCommand Insight Open menu, select Configuration > FC Identify. 2. In the FC Identify view, select the row of the device you want to identify. If more than one port belongs to the same device, select all the generic devices (ports) that you want to match to the same device. 3. Do one of the following:

179 From the menu, select Action > Identify Selected. Right-click and select Identify Selected. 4. Optionally, to filter the list by IP, name, or device type, fill in the fields at the top. 5. In the Identify Selected view, click a device that matches the one you want to identify. 6. Click Update Changes. FC Identify view Use this view to identify generic devices manually. Fibre Channel (FC) switches that are monitored by OnCommand Insight Assure sometimes report back about devices whose identity is unknown. Each unknown port on such devices is reported as a generic device until it is identified. Use this view to identify any FC-based devices that OnCommand Insight did not identify as hosts. After you identify such a device, it still appears on the Configuration > FC Identify view, so that you can change data as needed. Navigation You can access this main view in any of the following ways. Data source setup and device identification 179 From the OnCommand Insight Open menu, select Configuration > FC Identify. From the Shortcut bar, select Configuration > FC Identify. Column descriptions The number following the table heading (in parentheses) indicates the total number of devices in the list. The view shows a list of unidentified host HBA ports, disk storage ports, tape device ports, and switch ports. The view shows information about the following: Each generic device that requires identification Each port that was originally classified as a generic device, then identified manually or through automatic host resolution. The following information appears for each generic device, if available. This information was either reported by the data source that discovered the generic device or identified manually. From this view, you can change the IP, name, or device type. WWN The World Wide Name assigned to the generic device. If the device is a port, this is the same as the value in the Port WWNs field.

180 180 OnCommand Insight Installation and Administration Guide Port WWNs IPs Name Type Source The World Wide Name for the generic port device. The IP address or addresses assigned to the device. Multiple IPs are separated by commas. To change the IP, double-click on the field. Multiple IPs can exist for a single host; however, multiple IPs cannot exist for a single tape or storage array. Name of the host, storage array, tape, or switch for the generic device. To change the name, double-click on the field. The type of device: host, storage (array), tape, or unknown. To change the type, select the type from the drop-down list. To remove identification, change the type to "Unknown." One of the following sources used to identify the host. This corresponds to the Source field in automatic host resolution. Values History SRM Switch Storage Unknown User Zone Description Resolved using historical information from previous version. Resolved using storage resource management (SRM) software. Resolved using switch alias names Resolved using storage alias names. Not resolved. Manually resolved. Resolved using zone names. Method The method that was used to identify the device. This corresponds to the Method field in automatic host resolution. Values <blank> As Is Delimiter Manual Regular Expression: abc.* Description Not resolved. Resolved using the As Is method when Storage Resource Management (SRM) is used. Resolved using the delimiter technique. Manually resolved. Resolved using the regular expression technique. The actual regular expression follows.

181 Data source setup and device identification 181 Values Upgraded from previous version Description Resolved using a method that was defined in an earlier version of OnCommand Insight, and that did not map correctly to the options available in the current release. Host-resolution processing works correctly as defined originally, but you can update to a more current method. Validation The method of validation that was used when identifying the device. Zones Switch Alias Values <blank> DNS Lookup Existing host with same name None SRM IP Description Not resolved. Validated through Domain Name Server lookup. This corresponds to the Validation field in automatic host resolution. Validated by matching the host name with the name of an existing host. Resolved but not validated. Resolved when Storage Resource Management (SRM) is in use, the SRM provides an IP, and DNS validation is not specified. The name of the zone or zones to which this port belongs, which will help with the identification. The switch alias name or names that reference the generic device. Displays the alias from the fabric to which the listed device's port is connected. Storage Alias The storage alias name or names that reference the generic device. SRM Alias SRM IP Vendor Audit The alias name that originated within a Storage Resource Management (SRM) application, and that references the generic device. The IP address used to identify the host running the SRM software. The name of the vendor who sells the generic device based on industry standard WWN allocation ranges. Messages about the identification process that might help you troubleshoot. For example, the following messages might appear: Manually identified. Not identified automatically. Matches XYZ storage vendor, ignored. Identification failed. Identified to XYZ, re-identification disabled.

182 182 OnCommand Insight Installation and Administration Guide Identified to XYZ. Identified to XYZ valid. The last two audit messages can include warning messages, which are described in the Resolution Details detail view. For example, a warning might appear if a host is present in multiple domains. In this case, automatic host resolution (AR) selects the first domain, but a warning appears indicating that there is a potential conflict. Errors/ Warnings Errors or warnings that apply for the generic device, such as the same WWN identified twice in the list or missing information. Options If you change the IP, name, or device type, the following options appear: Update Changes: Saves the changes you made to the data on this view. Cancel Changes: Cancels the changes you made to the data on this view. You can click on the Topology icon in the Icon bar. When selecting rows in the FC Identify view, the Topology view shows relevant connections for the selected WWN. If the WWN was identified as a host, storage, or tape, the Topology view reflects the identified device's topology. If the WWN has not been identified, the Topology view shows the generic device and its switch connectivity. From the FC Identify view, right-click to show a pop-up menu containing the following options. Auto Resolution Add New Device Click the green Auto Resolution arrow to initiate automatic host resolution. See information about identifying hosts automatically with Auto Resolution (AHR) in the OnCommand Insight Installation and Administration Guide. Progress is indicated in the progress box. After you click Update Changes, the last run AR date and time appear next to the view name along with an indication of errors and warnings. To stop AR processing, click the red square. You can stop AR processing only before the DNS lookup has occurred as indicated by the blue bar. A large blue bar moving from left to right indicates that DNS lookup has not finished and you can stop AR processing. A small, fixed-size blue bar moving back and forth indicates that DNS lookup has finished and you can no longer stop AR processing. Adds a port that has not been discovered yet by OnCommand Insight, but is planned for the near future. Predefining a device ensures that once OnCommand Insight discovers the device, it will be identified correctly. After you choose this option, OnCommand Insight adds a row to the main table, showing the fields in which you need to enter information in yellow. Double-click each field (for example, WWN and IP) and fill in the information or click in a field and select from the drop-down list.

183 Data source setup and device identification 183 Delete Identification Cancel Selected Clears any previous device identification from the selected row or rows. OnCommand Insightconfirms the request before removing the identification. Same as Delete Identification, but applicable before committing changes to OnCommand Insight by clicking Update Changes. Identify Selected Lets you identify the devices in one or more selected rows. If more than one port belongs to the same device, select all the ports (generic devices), then click this option and do one of the following: For new devices (totally unknown to OnCommand Insight), enter the IP, Name, and Device Type to identify the host, storage array, or tape device. Then, click OK. For generic devices (ports) that are on devices known to OnCommand Insight, use the list at the bottom to select the parent device. Optionally, fill in the fields at the top to filter the list, for example, by device type. See "Identifying FC-based generic devices manually." Configure Auto Resolution Identify from File Set Host Resolution Set Tape Resolution Initiates automatic host resolution. See "Identifying hosts automatically with Auto Resolution (AR)." Opens a CSV-formatted file that contains a predefined list of ports and their device names from which OnCommand Insight should identify as many generic devices as it can. See "Identifying generic devices from your port list file." Runs a host-resolution check for all selected generic devices. OnCommand Insight prompts for the method or methods. See "Making manual identifications with help from auto resolution rules." Runs a tape-resolution check for all selected generic devices. OnCommand Insight prompts for the method or methods. See "Making manual identifications with help from auto resolution rules." Related tasks Identifying and managing FC generic devices on page 172 Identifying hosts and tapes automatically with Auto Resolution (AR) on page 142 Deleting FC-based device identification on page 187

184 184 OnCommand Insight Installation and Administration Guide Identifying generic devices from your port list file You can identify generic devices by using a file containing a list of ports and their names. You can add only one IP per host using the list of ports; you cannot add multiple IPs per host using this method. Before you begin You must have a comma separated CSV-formatted file that contains a list of ports and their device names, which you will import into OnCommand Insight. Each line of the file must be formatted as shown below: WWN, IP, Name, Type For example: 11:22:33:44:55:66:77:88, ,myserver,Host Also, the header of this CSV file must include the following exact text: WWN,IP,Name,Type Steps 1. From the OnCommand Insight Client Launch menu, select Configuration > FC Identify 2. Do one of the following: From the menu, select Action > Identify from File. Right-click and select Identify from File. 3. In the Open dialog, browse to the file location and click Open. OnCommand Insight imports the data and places the data in the view. If the view already has a row containing the same WWN that was in the file, that row is updated with the IP, name, and type based on the contents of the file. If the file has WWNs that were not in the table, the WWNs are added as new rows with their changed values highlighted in yellow. 4. Click Update Changes. Identifying generic devices from the Topology view After you view the configuration of a device in the Topology view, you might see a generic device icon in the map. At that point, you might want to identify that generic device. You can do so directly from the Topology view. Steps 1. From the OnCommand Insight Client, display a main view, for example, one showing a host, storage array, or switch.

185 2. In the OnCommand Insight status bar, click the Topology icon. Data source setup and device identification In the Topology view, locate the generic device that is represented by the Generic Device icon. 4. Hold your cursor over the generic device icon. OnCommand Insight displays information about the device in a pop-up window. 5. To view additional details in the detail views, click on the generic device icon. The amount of information varies by manufacturer and model. 6. With the icon selected, right-click and select Identify Selected. 7. In the Identify Selected view, find a device that matches the one you want to identify. 8. Click OK. Adding and identifying a generic device You can add a port that has not been discovered yet by OnCommand Insight but is planned for the near future. Pre-defining a device ensures that once OnCommand Insight discovers the device, it will be identified correctly. About this task After you add the port, you can enter identifying information, such as WWN, IP, and name, if you know it. Alternatively, you can let OnCommand Insight identify it during the next Auto Resolution (AR) process. Steps 1. From the OnCommand Insight Open menu, select Configuration > FC Identify 2. In the FC Identify view, do one of the following: From the menu, select Action > Add New Device. Right-click and select Add New Device.

186 186 OnCommand Insight Installation and Administration Guide 3. Double-click in each field to enter the WWN, IP, and device name. 4. From the Type drop-down list that appears when you click in the column, select a device type. 5. If you add a new device and fill in the WWN/IP cell with a WWN or IP already used by a device in the table, OnCommand Insight displays a dialog that provides several options. Choose one of the following: Identify Original: Identify the original device (and remove the added duplicate). Remove Added Duplicate: Cancel the addition of the device. Re-Edit Added Device: Return to edit the identify cell of the added device. 6. Click Update Changes. Making manual identifications with auto resolution rules You can manually perform the identification with the help of the auto resolution rules. Choosing how the host is resolved lets you choose the method that best serves your environment. For example, if you have host names that can be identified using a pattern, you could choose to use the delimiter method or develop a regular expression to create advanced pattern queries. About this task You can choose one of the following identification methods for each source: Delimiters: Use delimiters when you want to match patterns of the source names. The host name is part of the source text, bounded by specific characters. For example, if your zones are named with a pattern combining the host name and the storage name, with the _ character as the separator, you can use the zone source method with the delimiter configured to use '_'. Ex: blade14_ds4800_1 (where blade14 is the host name) If you use delimiters, you must verify the host name using a DNS lookup. Regular expressions: Use one or more regular expressions to identify host name from source names. If you use regular expressions, you can verify the host name by using DNS lookup or by using another validation process. As Is (SRM source only): Use this to use the host name exactly as it appears in the Storage Resource Management (SRM) software. If you use this, you can verify the host name by using DNS lookup or by using another validation process.

187 Data source setup and device identification 187 Steps 1. From the OnCommand Insight Open menu, select Configuration > FC Identify 2. In the FC Identify view, select the row of the device you want to identify. If more than one port belongs to the same device, select all the generic devices (ports) that you want to match to the same device. 3. Do one of the following: Select Action > Set Host Resolution. Right-click and select Set Host Resolution. 4. In the Suggest Resolution view, for each source row, check the method by which the host name will be extracted. 5. To move the method up or down, select the row, and click Up or Down. OnCommand Insight executes the host resolution process in the order in which the methods appear, beginning with those at the top. 6. Click OK. 7. In the FC Identify view, click Update Changes. The source becomes "User" and the method appears as "manual." Deleting FC-based device identification Clear any previous device identification from a selected device. You might want to do this if you no longer want to track this device's configuration. Assure confirms the request before removing the identification. Steps 1. From the OnCommand Insight Open menu, select Configuration > FC Identify 2. In the FC Identify view, select the row or rows for the device or devices. 3. Do one of the following: Select Action > Delete Identification. Right-click and select Delete Identification. 4. In the Remove Selected Changes dialog box, click Yes. To delete identification from multiple selected devices, click Yes to All. 5. Click Update Changes.

188 188 OnCommand Insight Installation and Administration Guide Ensuring that a device is inactive Before you can delete a device from the OnCommand Insight database, it must be inactive. A device becomes marked as inactive the device reports that is no longer active or when you remove the data source corresponding to the device. About this task An inactive device's icon in the Topology Map should be grayed, as well as the corresponding row in the inventory display. There should not be any links from the device to other devices in the Topology Map. This happens automatically when you remove the data source corresponding to the device. Steps 1. From the OnCommand Insight Open menu, select Inventory and select the option corresponding to the device type that you're reviewing. For example, select the Hosts option. 2. In the main view, click on the device. Ensure that the row listing the device is grayed. 3. To see the topology for the device, at the bottom of the OnCommand Insight Client window, in the icon bar, click the Topology icon. Deleting inactive devices from OnCommand Insight inventory You can remove a selected device from the OnCommand Insight database, typically after you decommission the device in your environment. You might want to do this if you no longer want to track the configuration for a device and now want to remove it from all OnCommand Insight views. You can remove an inactive device from several views, including views showing hosts, switches, storage arrays, tapes, or Fibre Channel generic devices. Before you begin Make sure that the device is marked as inactive in the "Is the device offline?" column of the Storage Arrays, Switches, Tapes, or Generic Devices views. Its icon in the Topology Map should be grayed. There should not be any links from the device to other devices in the Topology Map. This happens automatically when you remove the data source corresponding to the device. About this task If the host stops accessing all of its shares, the host changes to an inactive state. You can remove an inactive host from the OnCommand Insight database through the Client. When you remove devices, OnCommand Insight removes any associated policies. For example, if you remove a host device, OnCommand Insight removes any host policies and path policies that are assigned to the target host device. Note: Policies can be set and managed only if a OnCommand Insight Assure license is installed.

189 Data source setup and device identification 189 Steps 1. From the OnCommand Insight Open menu, select Inventory and select a device option. 2. In the main view, click on the device. 3. Do one of the following: Select Actions > Delete Inactive Device. In the main view, right-click on the device and select Delete Inactive Device. OnCommand Insight confirms the request before removing it from the OnCommand Insight database. Auditing automatic host and tape resolution You can audit the complex process of automatic resolution (AR) for hosts or tapes. You can also audit identification or re-identification events. About this task OnCommand Insight shows the following statuses related to identification: Status Not identified automatically Identification failed Identified to "X" Identified to "X, reidentification disabled Identified to "X" valid Manually identified Matches "X" storage vendor, ignored Description All AR rules failed or AR has never run. AR produced a possible identification, but it conflicts with existing identifications. Initial identification Re-identification was skipped because the method used to identify the device initially is now disabled in the AR configuration. Re-identification did not detect any changes A OnCommand Insight user performed a manual identification. AR will not attempt to re-identify this entry. AR identified the generic device as storage and not a host and ignores the result. If AR encounters warnings, it appends the text "(with warnings)" to the status value. Use the Resolution Details detail view to find out the nature of any warnings. Warning messages are displayed only on the following two statuses: Identified to "X" Identification to "X" valid

190 190 OnCommand Insight Installation and Administration Guide The FC Identify view shows warnings also in the Errors/Warnings column, which represent errors or warnings related to manual identification. These are not the same warnings described here that AR generates. Steps 1. From the OnCommand Insight Open menu, select Configuration > FC Identify. 2. In the FC Identify view, review the Audit column. 3. To see detailed information about the AR process, in the OnCommand Insight status bar, click the Resolution Details icon. The Resolution Details detail view shows the sequence of identification activities related to the generic device selected in the FC Identify view. Identifying and managing iscsi sessions and NAS shares For devices that cannot be identified automatically using the OnCommand Insight automatic resolution (AR) feature, devices that were identified incorrectly, or those where you chose not to identify automatically, you can use OnCommand Insight for manual identification. You can review a list of discovered IPs associated with iscsi sessions or NAS shares. You can then identify IPs that OnCommand Insight could not associate with a host. iscsi sessions and NAS shares that cannot be identified automatically are referred to as unknown devices and are identified manually using the IP Identify view. Before you begin To access IP Identify view, you need the Assure: NAS, iscsi and Multiprotocol Capacity license. About this task You should identify these devices so that you can obtain meaningful data about them. If you do not identify them, OnCommand Insight cannot provide helpful data about them. Using OnCommand Insight, you can identify the following:

191 An iscsi session IP to a host A NAS share IP to a host An undiscovered IP that was entered manually An IP can be a specific address or a subnet. Identified IPs can be assigned to new or existing hosts. You can identify different IPs to the same host, but you cannot identify multiple devices to the same IP. You can identify an IP to any defined host or to a subnet. This includes the following subnets: A NAS share subnet IP to any host An undiscovered subnet IP that was manually entered You can also identify an IP to an ESX host. However, you cannot identify to a virtual machine if it has not been configured. In this case, you could add it to a host. If a VM is not known to OnCommand Insight, it appears as an identified host. However, after the VM datasource provides data, OnCommand Insight overrides the identification and creates the VM with the IP. After VM Insight acquires that "host," it is acknowledged as a VM. Note: You can manually or automatically identify to non-virtual machine hosts. You cannot add an IP, including an NFS share IP, to an existing VM. You can do the following tasks related to identifying iscsi sessions and NAS shares: Identify unknown devices manually. Correct identification of IPs. Remove identification of an IP that was manually identified. How OnCommand Insight displays NAS shares You can see a list of NAS shares in your environment in the Shares detail view detail view, which is available from several views, including the Hosts main view, the Storage Arrays main view, and the Topology view. To view discovered IPs for NAS shares that have not been identified to a host, use the IP Identify view. NAS shares are listed in the Shares detail view. Data source setup and device identification 191 To view discovered IPs for NAS shares that have not been identified to a host, use the IP Identify view. See "Identifying iscsi sessions and NAS shares manually."

192 192 OnCommand Insight Installation and Administration Guide Subnets appear with an asterisk in the IP column. How iscsi initiators appear Each iscsi entity on a network has a unique node name. This is a logical name that is not linked to an IP address. An iscsi node name has the following format: iqn.yyyy-mm.backward_naming_authority:unique_device_name An example in OnCommand Insight would be: iqn com.vmware:swanscreenlabesx1-4a4c07e0 Identifying iscsi sessions and NAS shares manually OnCommand Insight discovers IP addresses from the devices that access the storage. OnCommand Insight tries to associate an IP with a host. OnCommand Insight can also identify hosts that access NAS shares. You can manually identify those iscsi sessions or NAS shares that OnCommand Insight cannot identify or identified incorrectly. About this task You should identify these as hosts before you view them in other OnCommand Insight views. OnCommand Insight attempts to identify IP addresses even if the IP is not a true IP. The following scenarios could occur: Source Address Host name IP server Output from source address. server10 clearpoint Output after DNS lookup of server10 returns server20 point Output after DNS lookup of server20 failed, but a DNS lookup of point returned server30 webpoint webpoint DNS lookup of server30 and webpoint failed. Output could not be determined from address nor host name. In a file system environment, the IP must be a true IP, so you must correct these by fixing the DNS environment and deleting or recreating the manual identification.

193 After an IP is resolved, OnCommand Insight displays change messages in the Changes detail view, depending upon how the IP is used: If an IP is resolved to a host and that IP is used by an iscsi node, two change messages appear. The first message describes the IP resolution. The second message describes the identified iscsi initiator. If an IP is resolved to a host and that IP is used by a NAS share, only the IP message appears. Adding an IP Data source setup and device identification 193 You can add an IP manually by entering its IP address and name. You can later identify the IP to a new or existing host. Steps 1. From the OnCommand Insight Open menu, select Configuration > IP Identify. 2. Do one of the following: Select Action > Add New Device. Right-click and select Add New Device. OnCommand Insight adds a row to the main table, highlighting the fields in which you need to enter information in yellow. 3. Double-click each field (for example, IP) and fill in the information. 4. If the IP column is blank, OnCommand Insight displays a message requesting you to choose whether you want to resolve the IP with DNS lookup. You can choose this method or specify an IP. 5. Click Update Changes. 6. If you add a new device and fill in the WWN/IP cell with a WWN or IP already used by a device in the table, OnCommand Insight displays a dialog box with several options. Choose one of the following:

194 194 OnCommand Insight Installation and Administration Guide Identify Original: Identify the original device (and remove the added duplicate). Remove Added Duplicate: Cancel the addition of the device. Re-Edit Added Device: Return to edit the identify cell of the added device. 7. OnCommand Insight prompts for confirmation. In the Confirm Identification view, review the devices that were identified and click Confirm Changes. 8. To view resolution details, click the Resolution Details icon at the bottom of the view. Configuration > IP Identify view OnCommand Insight sometimes reports back about devices whose identity is unknown. This view lists discovered IPs that relate to NAS shares or iscsi sessions. Use this view to identify those IPs that could not be associated with a host. In an IP environment, OnCommand Insight discovers IP addresses from the devices accessing the storage. Navigation You can access this main view in any of the following ways. From the OnCommand Insight Open menu, select Configuration > IP Identify. From the Shortcut bar, select Configuration > IP Identify. To access this view, you need the Assure: NAS, iscsi and Multiprotocol Capacity license. Column descriptions After you identify the device, it still appears on the Configuration > IP Identify view, so that you can make corrections if needed. The device is removed from this view if a virtual machine (VM) data source claims the IP for the VM. The number following the table heading (in parentheses) indicates the total number of devices in the list. The following information appears for each device, if available. This information was either reported by the data source that discovered the device or entered manually. Address IP The IP or host name discovered from the environment. Unidentified or identified IPs are listed one IP per row. If a share has multiple IPs, you see one row per IP. The IP address assigned to the device. Unidentified or identified IPs are listed one IP per row. If a share has multiple IPs, you see one row per IP. To enter a new IP, double-click the field and enter the IP.

195 Data source setup and device identification 195 Note: If a share displays a non-ip (a name or subnet), a mock host appears in the Hosts main view if it has been identified, and the share is listed with its name or subnet in the IP Identify view. Name iscsi Node Share Name Audit Errors/ Warnings Name of the host. To enter a new name, double-click the field and enter the name. Name of initiator node using IP. If the IP host is connected only to a NAS device, this column is empty. List of NAS shares accessed by the IP belonging to the device. Displays in the following format: <storage> / <vfiler > / <volume> / <share>. Multiple shares are separated by commas. Messages about the identification process that might help you diagnose problems. For example, this message might appear: "Not identified automatically." This column indicates whether the IP was resolved by the Automatic Resolution (AR) feature or manually. Errors or warnings that apply for the device, such as missing information. Options If you change the IP or name, the following options appear: Update Changes: Saves the changes you made to the data on this view. Cancel Changes: Cancels the changes you made to the data on this view. From the IP Identify view main view, right-click to show a pop-up menu containing the following options. Auto Resolution Add New Device Click the green Auto Resolution arrow to initiate automatic host resolution. See information about identifying hosts automatically with Auto Resolution (AR) in the OnCommand Insight Installation and Administration Guide. Progress is indicated in the progress box. After you click Update Changes, the last run AR date and time appear next to the view name along with an indication of errors and warnings. To stop AR processing, click the red square. You can stop AR processing only before the DNS lookup has occurred as indicated by the blue bar. A large blue bar moving from left to right indicates that DNS lookup has not finished and you can stop AR processing. A small, fixed-size blue bar moving back and forth indicates that DNS lookup has finished and you can no longer stop AR processing. Adds an IP that has not been discovered yet by Assure, but is planned for the near future. Predefining a device ensures that once OnCommand Insight discovers the device, it will be identified correctly. After you choose this option, OnCommand Insight adds a row to the main table, showing the fields in which you need to

196 196 OnCommand Insight Installation and Administration Guide Delete Identification Cancel Selected Identify Selected Configure Auto Resolution Identify from File enter information highlighted in yellow. Double-click each field (for example, IP) and fill in the information. OnCommand Insight prompts for confirmation. Clears any previous device identification from the selected row or rows. OnCommand Insightconfirms the request before removing the identification. Cancels uncommitted changes to the selected rows. Lets you identify the devices in one or more selected rows. If more than one node or share belongs to the same device, select all the rows, then click this option. Enter the IP that you want to match to the selected host or hosts. Initiates automatic host resolution. Opens a CSV-formatted file that contains a predefined list of IPs and their device names from which OnCommand Insight should identify as many devices as it can. Each line of the file must be formatted as shown below: <Address>, <IP>, <Name> For example: server5, ,server5.netapp.com Related tasks Identifying and managing iscsi sessions and NAS shares on page 190 Deleting IP-based identification information on page 201 Identifying hosts and tapes automatically with Auto Resolution (AR) on page 142 Resolution Details view Use this view to determine how OnCommand Insight attempted to discover IPs that could not be associated with a host or discover FC devices reported as generic devices. You can also use this view to determine exactly where the selected resolution failed. This view can be used in both the IP Identify and the FC-based generic identify processes. Navigation You can access this main view in any of the following ways. From the OnCommand Insight Open menu, select Configuration > IP Identify. At the bottom of the view, click the Resolution Details icon. From the OnCommand Insight Open menu, select Configuration > FC Identify. At the bottom of the view, click the Resolution Details icon.

197 From the Shortcut bar, select Configuration > IP Identify or Configuration > FC Identify. At the bottom of the view, click the Resolution Details icon. Column descriptions The number following the table heading (in parentheses) indicates the total number of processes that OnCommand Insight performed to resolve the selected device identity. Order Data source setup and device identification 197 Lists the sequence of the steps taken to resolve the device identity. Details Displays the steps taken to resolve the IP or host name discovered from the environment. Messages about successful and unsuccessful resolutions are displayed. To troubleshoot a failed resolution, locate the step that failed. For example, these messages might appear: "DNS: reverse lookup failed." This message indicates that after OnCommand Insight tried to identify the selected address automatically unsuccessfully, the next step to lookup the address also failed. "Not identified automatically." This message indicates that the device could not be identified by the Auto Resolution (AR) process. Identifying an IP to a new host The Identify an IP to a host feature is used for a new host that has not been discovered yet, but is planned for the near future. Predefining a device ensures that once OnCommand Insight discovers the device, it will be identified correctly. You can review a list of IPs discovered that relate to NAS shares or to iscsi sessions and then identify IPs that OnCommand Insight could not be associated with a host. Steps 1. From the OnCommand Insight Open menu, select Configuration > IP Identify. 2. In the IP Identify view, select the row of the device you want to identify. If more than device belongs to the same IP, select all the devices that you want to match to the same IP. Nodes can have multiple IPs. OnCommand Insight displays each defined IP on a single row. 3. Do one of the following: Select Action > Identify Selected. Right-click and select Identify Selected. 4. In the Identify Selected view, in the Name field, type the name of the new undiscovered host. If the name is identified as an existing host, the table shows the corresponding row. Otherwise, no matches appear in the table. 5. Click OK.

198 198 OnCommand Insight Installation and Administration Guide OnCommand Insight adds the new host to the IP Identify view. 6. In the IP Identify view, click Update Changes. 7. To see messages concerning DNS lookup, validation, and response in the Resolution Details detail view for an IP, select the IP in the IP Identify view and click the Resolution Details icon in the OnCommand Insight status bar. Identifying an IP to an existing host Identify an iscsi session or NAS share IP to an existing host. Before you begin To access the IP Identify view, you need the Assure: NAS, iscsi and Multiprotocol Capacity license. This view is not available with only the Assure license. Steps 1. From the OnCommand Insight Open menu, select Configuration > IP Identify. 2. In the IP Identify view, select the row of the iscsi session or NAS share that you want to identify. If more than one session or share belongs to the same host, select all the IPs that you want to match to the same host. 3. Do one of the following: Select Action > Identify Selected. Right-click and select Identify Selected. OnCommand Insight shows a list of existing hosts. 4. Optionally, in the Identify Selected view, to filter the list by host name, enter the name at the top. 5. In the Identify Selected view, click a host that you want to associate with the selected IP or IPs. 6. Click OK. 7. In the IP Identify view, click Update Changes. 8. To see messages concerning DNS lookup, validation, and response in the Resolution Details detail view for an IP, select the IP in the IP Identify view and click the Resolution Details icon in the OnCommand Insight status bar.

199 Data source setup and device identification 199 Importing IP identification information Rather than enter device information, you can import it from a comma-separated file containing address, IP, and name information. After you import it, OnCommand Insight displays the IPs that were identified from the imported data. About this task The file must contain a header line that includes the exact address,ip,host text in the first line. The text is not case sensitive. <Address>,<IP>,<Name> The header components include: Address: The address is a globally unique identifier that identifies the host. It can be the IP or a host name. IP: Actual IP of the host. Host name: Name of the host. Here are some examples: Example Description , , server5.netapp.com IP of host repeated as Address. server5, , server5.netapp.com Address is server5 and actual IP was determined *, , server5.netapp.com Subnet for IP of host and actual IP was determined. Steps 1. From the OnCommand Insight Open menu, select Configuration > IP Identify. 2. Do one of the following: Select Action > Identify from File. In the IP Identify view, right-click and select Identify from File. 3. In the Open dialog box, locate the CSV file containing the host name and IP. 4. Click Open. OnCommand Insight imports the information into the OnCommand Insight Client, but the data is not committed. 5. To commit the changes to the OnCommand Insight database, click Update Changes. OnCommand Insight displays the identified IPs on the IP Identify view.

200 200 OnCommand Insight Installation and Administration Guide Identifying a subnet to a mock host You can identify a subnet to a mock host or to an existing host. About this task A subnet shows the identifier subnet address using an asterisk, for example, * The address is unique. Two subnets with similar addresses, for example, * and 1.1.1*.*, create two different hosts with no relationship to each other. There is no special handling for subnet masks. An IP Identify view could list the following "IPs": * If you identified these as hosts A ( ), B ( ), and C ( *); the C host looks like a single device to OnCommand Insight. The IP for the host or mock host is set to the host name or the subnet, respectively. You provide the name during the identification process. You can identify a subnet to a mock host or an existing host. Note: The hosts and mock hosts are shown in the same way.. Steps 1. From the OnCommand Insight Open menu, select Configuration > IP Identify 2. In the IP Identify view, select the row of the subnet device you want to identify. If more than one device belongs to the same IP, select all the devices that you want to match to the same IP. 3. Do one of the following: Select Action > Identify Selected. Right-click and select Identify Selected. 4. In the Identify Selected view, in the Name field, type the name of the new undiscovered host. If the name is identified as an existing host, the table shows the corresponding row. Otherwise, the table is empty as a result of no matches found. 5. Click Update Changes.

201 Data source setup and device identification 201 Deleting IP-based identification information Clear any previous device identification from a selected device. OnCommand Insight confirms the request before removing the identification. You can also remove Auto Resolution (AR) identifications or manual identifications of shared clients. Steps 1. From the OnCommand Insight Open menu, select Configuration > IP Identify. 2. In the IP Identify view, select the row or rows for the device or devices. 3. Do one of the following: Select Action > Delete Identification. Right-click and select Delete Identification. 4. In the Remove Selected Changes dialog box, click Yes. To delete identification from multiple selected devices, click Yes to All. OnCommand Insight highlights the entry in the IP Identify view in yellow. 5. Click Update Changes.

202 202 OnCommand Insight Installation and Administration Guide OnCommand Insight configuration and administration tasks The OnCommand Insight administrator's tasks include starting and stopping OnCommand Insight, configuring, monitoring the system, and troubleshooting. Starting and stopping the OnCommand Insight services As installed, the OnCommand Insight service starts automatically with your computer. This service includes a Local Acquisition Unit (LAU), which also starts automatically. The OnCommand Insight service and the LAU can also be stopped and restarted manually. OnCommand Insight operates as a service. It runs in the background and executes discovery, analysis, and monitoring operations continuously. Note: Remote Acquisition Units start and stop with the host server where they are installed. Starting the OnCommand Insight Server The OnCommand Insight Server starts automatically along with the Local Acquisition Unit (LAU). If you need to start the OnCommand Insight Server manually, you can use the Microsoft Windows Start menu. Step 1. Select Start > All Programs > NetApp OnCommand > Start OnCommand Insight Server. Starting the OnCommand Insight Client in Windows To start the OnCommand Insight Client, you can use either the Microsoft Windows Start menu option or open the Client directly from a browser. About this task You must open the OnCommand Insight Client on the OnCommand Insight Server. Steps 1. Select Start > All Programs > NetApp OnCommand > OnCommand Insight Client. 2. In the login window, enter your user name and password. The default (as-installed) user name is admin, and the password is admin123. Note: For security purposes, you need to change these defaults as soon as possible after installation and configure the Host View for the new password.

203 3. Click OK. OnCommand Insight configuration and administration tasks 203 After a successful login, the OnCommand Insight Client opens. Starting the OnCommand Insight Client in a browser You can open the OnCommand Insight Client from a web browser. Steps 1. Open a supported browser. 2. Enter the following URL to access the administration portal on the OnCommand Insight Server: The port number was configured when the Server was installed. It defaults to 80 if not specified differently in the URL. If you are accessing the Client from the OnCommand Insight Server, enter: 3. After connecting with the OnCommand Insight portal, the browser opens a window through which you can access various OnCommand Insight web services. Click the graphic illustration of the Client to open it. 4. Enter your user name and password in the login window and click OK. After a successful login, the Client window opens.

204 204 OnCommand Insight Installation and Administration Guide Stopping the OnCommand Insight Server and acquisition You can easily stop the OnCommand Insight Server and the acquisition process using the Microsoft Windows Start menu option. You might want to stop the Server if you need to install a service release or a file given to you by technical support. Step 1. Select Start > All Programs > NetApp OnCommand > Stop OnCommand Insight Server. Configuring your You need to configure OnCommand Insight to enable it access your system. The OnCommand Insight Server uses your to deliver reports to which you subscribe, and transports support information for troubleshooting to NetApp technical support. configuration prerequisites Before you can configure OnCommand Insight to access your system, you need to discover the host name or IP address to identify the (SMTP or Exchange) mail server and allocate an account for OnCommand Insight reports. Ask your administrator to create an account for OnCommand Insight. You will need the following information: The host name or IP address to identify the (SMTP or Exchange) mail server used by your organization. You can find this information through the application you use to read your . In Microsoft Outlook, for example, you can find the name of the server by viewing your account configuration: Tools - accounts - View or change existing account. Name of account through which OnCommand Insight will send regular reports. The account must be a valid address in your organization. (Most mail systems will not send messages unless they are sent from a valid user.) If the server requires a user name and password in order to send mail, obtain this information from your system administrator. Related tasks Configuring your for OnCommand Insight on page 204 Configuring your for OnCommand Insight If your users want to receive OnCommand Insight reports in their accounts, you need to configure your server for this feature. Steps 1. Log in as an administrator.

205 2. From the OnCommand Insight Main Menu, select Mail. 3. Enter the following information to configure the OnCommand Insight configuration and administration tasks 205 SMTP server address Sender e- mail User Name Password Server that is acting as the SMTP server in your organization, identified using either a hostname or an IP address (nnn.nnn.nnn.nnn format). If you specify a hostname, make sure the name can be resolved through DNS. account to be identified as the sender on all OnCommand Insight reports. This account must be a valid account within your organization. Optional. User name to access the server, required only if your SMTP server is protected by a user login. This is the same user name you use to log in to the application and that accesses your . Note: In most cases, a user name and password are required. Optional. Password to access the server, required only if your SMTP server is protected by a password. This is the same password you use to log in to the application that lets you read your . Enter it a second time for verification. 4. Click Submit. Related concepts configuration prerequisites on page 204 Managing user accounts User accounts, user authentication, and user authorization can be defined and managed in either of two ways: in Microsoft Active Directory (Version 2 or 3) LDAP (Lightweight Directory Access Protocol) server or in an internal OnCommand Insight user database. When a user logs in to OnCommand Insight, the server first tries to authenticate through LDAP (if LDAP is enabled). If OnCommand Insight cannot find the user on the LDAP server, it looks in its local database. Each user account is assigned one of the following permission levels: Guest permits you to log in to the OnCommand Insight client, and to view the various windows. Does not allow you to perform actions such as defining policy and identifying generic devices. If your user account is defined to OnCommand Insight's local user database (and not through LDAP), you can also modify your own password. User permits all guest-level privileges, as well as access to OnCommand Insight operations such as defining policy and identifying generic devices. Does not allow you to perform data source operations, nor to add or edit OnCommand Insight user accounts other than your own. Administrator permissions vary depending on whether you use LDAP:

206 206 OnCommand Insight Installation and Administration Guide If you authenticate and authorize users through LDAP, this level of permission allows you manage data sources. If you use only the local database to manage users, this level of permission allows you perform any operation, including adding new users and managing data sources. Best Practice: Limit the number of users with Administrator permissions by adding most users as users or guests. Setting up user accounts Having a different user account for each person provides a way of controlling the access rights, individual preferences, and accountability. Use an account that has Administrator privileges for this operation. Before you begin You must have completed the following tasks: Allocate a unique user name. Determine what password to use. Verify the correct user roles. About this task Add a new user account for each person who requires access to the OnCommand Insight system. Steps 1. Log into OnCommand Insight with Administrator privileges. 2. To define users in the internal OnCommand Insight user database (not using LDAP), click the User Management link in the Main Menu. If this is the first time you request the management window after opening the OnCommand Insight Admin Portal, you are asked to log in. 3. Click Add New User. 4. In the next window, enter the following information for the new user:

207 OnCommand Insight configuration and administration tasks 207 User Name Name assigned to the new user (alphanumeric, including a-z, A-Z, and 0-9). This name is used to log into OnCommand Insight. If using LDAP, this must be a valid LDAP user name. address address for the user is optional. It is required if the user subscribes to any reports. Password Password used to log into OnCommand Insight under this user account (typically selected by the user). 5. Select the OnCommand Insight role as Guest, User, Administrator, or superuser administrator (oadmin) that provide the levels of user permissions. The default admin and oadmin user designations cannot be deleted. 6. Click Add. A single user account is added onto the OnCommand Insight local database and listed in the User Management window. Configuring user definitions using LDAP To configure OnCommand Insight for user authentication and authorization from an LDAP server, you must be defined in the LDAP server as the OnCommand Insight Server Administrator. The default definition for this role is sanscreen.server.admin. About this task This procedure assumes that you are using Microsoft Active Directory Version 2 or 3 LDAP (Lightweight Directory Access Protocol). LDAP users display along with users who are defined locally to OnCommand Insight in the User Management table. Steps 1. Click the User Management link in the Main Menu. If this is the first time you request the management window after opening the OnCommand Insight Admin Portal, you are asked to log in. Be certain to use an account that has Administrator privileges for this operation. 2. Click LDAP Configuration. 3. Click Enable LDAP (shown in this example) to allow the LDAP user authentication and authorization.

208 208 OnCommand Insight Installation and Administration Guide 4. Enter the LDAP data required in these fields. The default settings are valid for the Active Directory. User principal name attribute Role attribute Mail attribute Distinguished name attribute Referral Attribute that identifies each user in the LDAP server (defaults to userprincipalname, which is globally unique). OnCommand Insight attempts to match the contents of this attribute with the username that has been supplied. LDAP attribute that identifies the user role (defaults to memberof). LDAP attribute that identifies the user address (defaults to mail). This is useful if you want to subscribe to the OnCommand Insight reports available from OnCommand Insight. OnCommand Insight picks up the user address the first time each user logs in and does not look for it after that. Note: If the address changes on the LDAP server, make sure to change it manually in OnCommand Insight. LDAP attribute that identifies the user distinguished name (defaults to distinguishedname). Indication of whether to follow the path to other domains if there are multiple domains in the enterprise. Always use the default (follow).

209 OnCommand Insight configuration and administration tasks 209 Timeout LDAP server Length of time to wait for a response from the LDAP server before timing out, in milliseconds (defaults to 2 seconds, which is adequate in all cases and should not be modified). IP address or DNS name to identify the LDAP server, typically provided in this format: ldap:// <ldap-server-address>:port or use the default port: ldap://<ldap-server-address> Domain LDAP node where OnCommand Insight should start looking for the LDAP user (typically the top-level domain for the organization). For example: DC=<enterprise>,DC=com Insight server administrators group Insight administrators group Insight users group Insight guests group Directory lookup user Directory lookup user password Confirm directory lookup user password Value of the Role Attribute that identifies the user as having Server Administrator privileges (defaults to sanscreen.server.admin). Value of the Role Attribute that identifies the user as having Administrator privileges (defaults to sanscreen.admin). Value of the Role Attribute that identifies the user as having User privileges (defaults to sanscreen.users). Value of the Role Attribute that identifies the user as having Guest privileges (defaults to sanscreen.guests). This is a special LDAP user who has permission to find LDAP users and determine their roles. If the LDAP server restricts the process of finding LDAP users and determining their roles, then you should enter the user information here. Otherwise, if any user can perform these functions, you may omit this field. Password for the user above (will not redisplay once the window is updated, for security reasons). Same password, repeated. 5. Click Validate Password to verify that the password you entered is valid on the server. 6. Click Update to save the changes.

210 210 OnCommand Insight Installation and Administration Guide Importing certificates into OnCommand Insight OnCommand Insight supports LDAP authentication over SSL, provided the Domain Controllers and Global Catalog servers in use for authentication have valid SSL certificates installed. You can import certificate information. Steps 1. When adding information in the LDAP configuration window, you might want to ensure that the LDAP certificates are on the servers. Click the Import Certificates button to start that process. 2. From the Import Certificates window, select one of these two methods to install the certificates: Automatically import them from configured LDAP servers by clicking Import from LDAP Server. Manually select the files from their local storage directory by using the Choose file field with the Browse button to select the file. In the Alias field, enter a name or use the OnCommand Insight default ldaps. Click Import from File to install the selected certificates. Important: To import the certificates manually, they need to be in a DER format for data encryption. Result The imported certificate contents display. After you finish To use LDAP with SSL, change the LDAP servers' value from: ldap://hostname, ldap://hostname1 to ldaps://hostname:636, ldaps://hostname1:636 OnCommand Insight LDAP requirements OnCommand Insight requires the hostname or IP address of the Active Directory (AD) LDAP server and the AD/LDAP domain name. The hostname must be resolvable by DNS. For the AD/LDAP domain name, a user's Distinguished Name (DN) is used, along with the provided password, as credentials to look up other users' roles after they are authenticated. This is a special LDAP user who is part of the Domain Users group and who has permission to find LDAP users and determine their roles. The following conditions apply: If the LDAP server restricts the process of finding LDAP users and determining their roles, then you should enter the user information in the LDAP configuration. Ensure that the password never expires for this account.

211 If any user can perform these functions, you can omit this field. If you omit this field, the Validate process verifies only the LDAP server and domain. At least three groups must be created in AD/LDAP. These groups should hold the usernames of the people who will have access to OnCommand Insight. There are no OnCommand Insight restrictions on AD/LDAP group names. Insight administrators group Insight users group Insight guests group OnCommand Insight configuration and administration tasks 211 At least one user must be added to each of the new AD/LDAP groups created for OnCommand Insight. When you log in to test that the LDAP configuration is working, how you log in depends on the value in the User Principal name attribute field. If the samaccountname is used, then you can test the configuration by using "domain\username." On the other hand, if the userprincipalname is used, you can test it by using the format of Changing user passwords A user with administrator privileges can change the password for any OnCommand Insight user account defined on the local server. Before you begin The following items must have been completed: Notifications to anyone who logs into the user account you are modifying. Identification of password to use. About this task When using this method, you cannot change the password for a user who is validated through LDAP. Steps 1. Log in with administrator privileges. 2. In the Main Menu, select User Management. 3. Locate the row that displays the user account you want to modify. 4. In that row, click the Change password link. 5. Enter the new password and then enter it again in the verification field. 6. Click Update.

212 212 OnCommand Insight Installation and Administration Guide Editing a user definition A user with administrator privileges can edit a user account to change the address or roles for OnCommand Insight or DWH and reporting functions. Before you begin Determine the type of user account (OnCommand Insight, DWH, or reporting or a combination) that needs to be changed. About this task For LDAP users, you can only modify the address. Steps 1. Log into OnCommand Insight or DHW and reporting with Administrator privileges. 2. In the Main Menu, click the User Management link. 3. In the User Management list, locate the row that displays the user account you want to edit. 4. Click the Edit link in that row to open the change window. 5. Change the address or select a different role. 6. Click Update to save the user account settings. The main user list opens with the changes recorded. Deleting a user account Any user with Administrator privileges can delete a user account, either when it is no longer used (for a local user definition) or to force OnCommand Insight to rediscover the user information the next time the user logs in (for an LDAP user). Steps 1. Log into OnCommand Insight with Administrator privileges. 2. In the Main Menu, click the User Management link. 3. In the User Management list, locate the row that displays the user account you want to remove. 4. Click the Delete link. OnCommand Insight confirms the request. 5. Click OK to confirm the operation and redisplay the main user list.

213 OnCommand Insight configuration and administration tasks 213 Configuring SNMP notifications OnCommand Insight supports SNMP notifications for changes and violations. For example, SNMP notifications are sent when data source thresholds are exceeded. Before you begin The following must have been completed: Determination of the IP address of the server that consolidates traps for each type of event. You may have to consult with your system administrator to obtain this information. Determination of the port number through which the designated machine obtains SNMP traps, for each type of event. (The default port for SNMP traps is 162.) Compilation of the MIB at your site. The proprietary MIB comes with the installation software to support OnCommand Insight traps. The NetApp MIB is compatible with all standard SNMP management software. Steps 1. To configure SNMP notifications, log into the OnCommand Insight portal as an administrator. 2. On the Main Menu, select SNMP/Syslog. 3. Click Add and enter the following information to configure traps: Trap IP Port The IP address to which OnCommand Insight sends SNMP trap messages. The port number to which OnCommand Insight sends SNMP trap messages. Community String Enter "public" for SNMP trap messages. 4. Click Submit. Verifying the SNMP configuration You should verify that an SNMP trap was received for each type of processing with requested changes and violations. Consult with your system administrator to do this because the approach varies depending on your organization's SNMP trap management and reporting software. Enabling the syslog facility You can identify a location for the log of the OnCommand Insight violations and performance alerts and activate the logging. Before you begin You need to know :

214 214 OnCommand Insight Installation and Administration Guide IP address of the server to store the system log Facility level specifying the type of program that is logging the message, such as LOCAL1 or USER About this task The syslog includes the following types of information: Violation changes Performance alerts The following units are used: Utilization metrics: percentage Traffic metrics: MB Traffic rate: MB/s Steps 1. Log into the OnCommand Insight portal as an administrator. 2. On the Main Menu, select SNMP/Syslog. 3. In the Syslog Configuration area, enter the log server IP address in the Syslog Host field. 4. In the Facility field, select the facility level specifying the type of program that is logging the message. 5. Check the Syslog Enabled box. 6. Click Submit. OnCommand Insight syslog contents You can enable a syslog on a server to collect OnCommand Insight violation and performance alert messages that include utilization and traffic data. Message types The OnCommand Insight syslog lists three types of messages: SAN path violations General violations Performance alerts Data provided Violation descriptions include the elements involved, time of the event, and relative severity or priority of the violation. Performance alerts include these data: Utilization percentages

215 OnCommand Insight configuration and administration tasks 215 Traffic types Traffic rate measured in MB OnCommand Insight administrative tasks You can perform the typical administrative tasks using the OnCommand Insight Administration Portal and Configuration menu in the Client. Configure servers and passwords. Monitor OnCommand Insight processing and make system changes. Back up and restore the OnCommand Insight database. Back up and restore the Data Warehouse and Reporting database. Consolidate host data from multiple servers. Audit system and user activities Use the specialized Admin Tools toolkit. Performing administrative tasks The OnCommand Insight administrative tasks are accessed through the main portal and the Admin Tools menu. Steps 1. To open the OnCommand Insight Admininstration Portal, enter the following URL: > or for secure communications: > The port number was configured when the server was installed. It defaults to 80 for the first and 443 for the second if not specified in the URL. 2. If you are accessing the OnCommand Insight Administration Portal from the OnCommand Insight Server, enter: The OnCommand Insight Administration Portal is displayed.

216 216 OnCommand Insight Installation and Administration Guide Configuring servers and passwords To configure OnCommand Insight for your passwords and multiple OnCommand Insight servers, use you can create a configuration XML file containing your specific data. Steps 1. In the Main Menu, click Insight Connect Applications to open applications, including a host portal and a utilization report, developed by NetApp using the OnCommand Insight Connect API. 2. Select Host View. 3. In the Host View, click Configure Multiple Servers. 4. Click the here link to display the XML example. 5. Copy the XML contents of the example file. The contents of the example file are as follows: - <HostView> - <SanScreenServers> - <!-- List your data centers here --> <Server name="dallas" host=" username="guest" password="" /> <Server name="boston" host=" username="guest" password="" /> <Server name="merrimack" host=" username="user" password="password123" /> </SanScreenServers> </HostView> 6. Click the browser Back button to return to the OnCommand Insight Host configuration window.

217 OnCommand Insight configuration and administration tasks In an XML text editor, create a new XML file using the example contents. 8. Change the OnCommand Insight server host name and credentials to match your environment. Save the new XML file. If you want to examine the XML schema file used to validate this configuration file, click the here link in the OnCommand Insight window to display the schema or review this sample schema. <?xml version="1.0" encoding="utf-8"?> - <!-- This schema file describes the structure of XML file with configuration information for HostView portal --> - <xs:schema xmlns:xs=" elementformdefault="qualified" attributeformdefault="unqualified"> - <xs:element name="hostview"> - <xs:complextype> - <xs:sequence> <xs:element ref="sanscreenservers" /> </xs:sequence> </xs:complextype> </xs:element> - <xs:element name="sanscreenservers"> - <xs:complextype> - <xs:sequence> <xs:element name="server" type="servertype" minoccurs="0" maxoccurs="unbounded" /> </xs:sequence> </xs:complextype> </xs:element> - <xs:complextype name="servertype"> <xs:attribute name="name" type="xs:string" use="required" /> <xs:attribute name="host" type="xs:string" use="required" /> <xs:attribute name="username" type="xs:string" use="required" /> <xs:attribute name="password" type="xs:string" use="required" /> </xs:complextype> </xs:schema> 9. In the Host View configuration file field, enter the path to the new file. 10. Click Save configuration to complete the operation and make the new file available to OnCommand Insight. Consolidating host data from multiple servers You might want to consolidate host information from multiple OnCommand Insight servers to see consolidated data. To do so, use the host configuration facility. Steps 1. In the Main Menu, select Insight Connect Applications. 2. Select Host View. 3. In the Host View, click Configure Multiple Servers. 4. Click the here link to display the XML example to use as the template for a customized configuration file, or if a customized configuration file was created previously for password changes, locate that file in the path listed in the Host View configuration file field. 5. In an XML text editor, change the XML file to add OnCommand Insight servers from which to receive host data.

218 218 OnCommand Insight Installation and Administration Guide For example, a new server entry in the file might be: <Server name="insight121" host=" username="admin_gbs" password="vgt2816b"/> 6. In the XML editor, save the changes in the file. 7. In OnCommand Insight, click on Save Configuration to make the new file available to OnCommand Insight. 8. Click the browser Back button to return to the Insight Connect Applications menu and select Host View. 9. Search for a host for which you want to see data. Note: You can view information for only one host at a time in this window. Auditing system and user activities If you want to track down unexpected changes, you can view an audit trail of OnCommand Insight system and its user activities. About this task OnCommand Insight generates audit entries for any user activities that affect the storage network or its management, including the following: Logging in Authorizing or unauthorizing a path Updating an authorized path Setting global policies or thresholds Adding or removing a data source Starting or stopping a data source Updating data source properties Adding, editing, or deleting a task Removing an application group Identify or changing the identification for a device Steps 1. From the OnCommand Insight Open menu, click Configuration > Audit. The Audit view appears. 2. Position your cursor over the Details column to see the complete text.

219 OnCommand Insight configuration and administration tasks 219 Audit view Use this view to identify system or user activities for a specified time in an audit log. Optionally, you can print the log. Navigation You can access the Audit view in one of the following ways: From the OnCommand Insight Open menu, select Configuration > Audit. From the navigation pane, select Configuration > Audit. Column descriptions The main table reflects the configuration of the host server itself, based on default configuration procedures from the manufacturer. The number following the table heading (in parentheses) indicates the total number of audit entries in the list. blank Time When you group the data using the Grouping drop-down list, this column shows the grouped values. For example, if you grouped this data by IP, this column displays the IP address. The number in parentheses indicates the number of audit entries in each grouped row. The date and time that the changes was made. User Name Name of user associated with the audit entry. IP Action Details IP address associated with the audit entry. Type of activity in the audit entry. The details of the audit entry. Position your cursor over the details to see the complete text. Options Print Date/Time selection Prints the log. Enables you to specify the date, week, or month of the log.

220 220 OnCommand Insight Installation and Administration Guide Using the Admin Tools toolkit The Admin Tools toolkit is accessible from a separate portal and provides many specialized administration options such as showing logs or customizing the Client Help menu. This toolkit provides administrators with these Admin Tools options: Show OnCommand Insight logs Browse the SAN and list the devices in the SAN Calculate RPO Run the server Trigger a VM NAS job Customize the options in the Client Help menu Opening the Admin Tools portal To access the administrators' toolkit, use the separate Admin Tools portal. Steps 1. To open the OnCommand Insight Admin Tools portal, open a browser and enter this URL customized for your environment: 2. Log in as an administrator. The Admin Tools menu opens. Showing OnCommand Insight logs To research problems, you might analyze the contents of the OnCommand Insight logs. These logs contain errors and warnings and include information about the length of time that some actions took, which might also be helpful in troubleshooting. Steps 1. Log into OnCommand Insight. 2. Below the Main Menu, select Troubleshooting > Logs. Note: This feature has the same function as the Admin Tools > Show Logs option. 3. Select the server, acquisition, or remote log that you want to analyze. The last 100 lines from the selected log are displayed.

221 OnCommand Insight configuration and administration tasks 221 Browsing the SAN to locate devices To locate a device or port in your environment based on its WWN, you can use the SANbrowse option. Steps 1. Log into the Admin Tools portal. 2. In the Admin Tools menu, select SANbrowse. 3. In the Search box, enter the WWN of the device or port you want to locate. Click Search. OnCommand Insight returns a report containing links to additional information, as shown in this example. 4. Click any of the links to see additional information related to a selected item. In this example, the first link in the search results was selected to produce this report with more links. Calculating the Recovery Point Objective (RPO) For users with the OnCommand Insight Replication license, you can calculate the Recovery Point Objective (RPO) time that would be used as the system recovery starting point. This is helpful if there is an outage and the system and data need to be restored. Steps 1. Log into the Admin Tools portal. 2. In the Admin Tools menu, select Calculate RPO.

222 222 OnCommand Insight Installation and Administration Guide After the RPO is recalculated, a "successfully calculated" message displays above the Admin Tools menu options. Running a paths and violations query If you are concerned about a recent change in the environment, you can use the Run server option to report changes in the paths and any new violations. Steps 1. Log into the separate Admin Tools portal. 2. In the Admin Tools menu, select Run server. The results of this query lists the changes found. Triggering VM NAS job To correlate the NFS share export IP address with the VM ESX IP address, you can use the Trigger VM NAS Job option in the Admin Tools. The NFS export IP relates to the NetApp data source, and the VM ESX IP relates to the Virtual Center data source. Steps 1. Log into the separate Admin Tools portal. 2. In the Admin Tools menu, select Trigger VM NAS Job. A report listing the results displays. Customizing the Help menu You can customize the Help menu by adding site-specific Help menu options. Customized Help menu options appear in any OnCommand Insight clients that are subsequently started and connected to the OnCommand Insight server. Clicking on the custom Help option launches the default web browser in a new window and displays the specified URL. Before you begin You should have created an HTML page, created a PDF document, or used a page on a web site. This content should have been placed in a URL-accessible folder. About this task Place the customized content as one of the following: On a file share accessible from all the clients In a web server folder In a custom deployment directory on the OnCommand Insight server that will serve the content. Note: We strongly recommend that you create your own deployment directory and add that directory to the OnCommand Insight server configuration. The directory should reside outside

223 of the OnCommand Insight installation directory. If it is not outside the installation directory, your content may be deleted when OnCommand Insight is uninstalled. You must be able to specify the content location as an absolute URL. If you are using the OnCommand Insight server, the server's path must be included in the URL. For example, you might specify: file:///aurormn.us.network file:///<server_host>: <server_port>/<your content's location relative to the server> The URL cannot contain spaces or special characters. If spaces are required, use their hexidecimal equivalents, as shown in these examples: Space: %20 Underscore: %5F OnCommand Insight configuration and administration tasks 223 The new Help option appears under a separator line in the Help menu. Steps 1. Access the OnCommand Insight Admin Tools portal by entering: <server_host>:<server_port>/admin/all.do 2. Log into OnCommand Insight as an administrator. 3. From the OnCommand Insight Admin Tools menu, select Manage Help Links. 4. In the Help Links view, click Add. 5. To add a separator line before the customized Help options, do the following: a) Help Menu Item: Enter "Separator" using any case. b) URL: Leave blank. 6. For each Help menu option, enter the following: a) Help Menu Item: Enter the label that will appear as the Help menu option. b) URL: Enter the absolute URL. 7. To add more Help menu option rows, click Add and enter the Help Menu Item label and URL. 8. Click Submit. Result All new Client sessions show the custom options in the Help menu. Clients already running do not show the new options until they are closed and started again.

224 224 OnCommand Insight Installation and Administration Guide Managing Data Warehouse and Reporting user accounts User accounts, user authentication, and user authorization for the OnCommand Insight reporting tools are defined and managed from the Data Warehouse (DWH). Based on these configurations, users and administrators gain access to some or all of the available OnCommand Insight reports. Access to the User Management in the Data Warehouse requires an account with System Administrator privileges. This includes: Full administrative capabilities for the Data Warehouse. Configuration and maintenance of all user accounts. Read access to the database. Capability to set up connectors in the ETL, schedule Data Warehouse jobs, reset the database, assign or change roles, and add and remove user accounts. Capability to run SQL queries. Accessing the Data Warehouse and Reporting The Data Warehouse portal provides access to administration options. From the Data Warehouse portal, you can also access the Reporting Connection portal. Steps 1. To open the Data Warehouse portal, enter this URL: 2. Log in as an administrator. The Data Warehouse portal resembles the OnCommand Insight Administration portal with a Main Menu and Advanced features listed in the left pane. 3. To access the reporting features, in the Main Menu, click Reporting Portal. Reporting user roles Each user account is assigned a role with a set of permissions. The number of users is limited by the number of Reporting licenses attached to each role. Each role can perform the following actions: Recipient Views OnCommand Insight Reporting portal dashboards and reports and sets personal preferences such as those for languages and time zones. Note: Recipients cannot create reports, run reports, schedule reports, export reports, nor perform administrative tasks.

225 OnCommand Insight configuration and administration tasks 225 Business Consumer Business Author Pro Author Administrator Runs reports in Business Insight (in standard mode) and runs reports interactively in addition to performing all Recipient options. Views scheduled reports, runs reports interactively, and creates some reports in addition to performing all Business Consumer options. Creates reports in addition to performing all Business Author options and has advanced reporting tool options that are available also with Report Studio. Performs reporting administrative tasks such as the import and export of report definitions, configuration of reports, configuration of data sources, and the shutdown and restart of reporting tasks. The following table shows the privileges and the maximum number of users allowed for each role: Feature Recipient Business Consumer View reports (in Detailed Reports tab, Public Folder tab, My Folders) Business Author (Insight Plan only) Pro Author (Insight Plan only) Admin Yes Yes Yes Yes Yes Run reports No Yes Yes Yes Yes Schedule reports No Yes Yes Yes Yes Create reports in Query Studio Create reports in Business Insight (Standard) Create reports in Business Insight (Advanced) Create reports in Report Studio Perform administrative tasks Number of users No No Yes Yes No No Yes Yes Yes No No No Yes Yes No No No No Yes No No No No No Yes Number of OnCommand Insight users

226 226 OnCommand Insight Installation and Administration Guide When you add a new Data Warehouse and Reporting user, if you exceed the limit in a role, the user is added as "deactivated," and you need to deactivate or remove another user with that role to give a new user membership. Note: Report authoring capabilities require Insight Plan license. These reporting user roles do not affect direct database access. These reporting user roles do not impact your ability to create SQL queries using the data marts. Adding a Reporting user Add a new user account for each person who requires access to the Reporting portal. Having a different user account for each person provides a way of controlling the access rights, individual preferences, and accountability. Before you begin Before adding a Reporting user: Allocate a unique user name. Determine what password to use. Verify the correct user role or roles. These roles are specialized in the Reporting portal. See "Reporting user roles" for details. Steps 1. Log in as the administrator to the DWH management portal. 2. On the lower left in the Advanced menu, click User Management. 3. In the User Management window, click Add New User. 4. Enter the following information for the new Reporting user: User Name Address Password OnCommand Insight role Reporting roles Name assigned to the new user (alphanumeric, including a-z, A-Z, and 0-9). This name is used to log in and is case-sensitive. User address and required if the user subscribes to any reports. Password used to log in to OnCommand Insight under this user account (typically selected by the user) and confirmed in the next field. Roles available to the user with appropriate permissions. Note: The options for the OnCommand Insight role are shown only if OnCommand Insight has been is installed on the same machine as the reporting facilities, which is not typical. Select the Reporting role for this user. For example, select Reporting Author. The Reporting Administrator role is unique and requires a separate license. This role can be added to any user.

227 OnCommand Insight configuration and administration tasks 227 No Access Selected by default. It indicates that the user should not have access to the OnCommand Insight Reporting portal. 5. Click Add. Related references Reporting user roles on page 224 Managing user accounts You can configure user accounts, user authentication, and user authorization from the Data Warehouse Portal. Each user account is assigned a role with one of the following permission levels. The number of users is limited by the number of Reporting licenses attached to each role. Steps 1. On the lower left in the Advanced section of the Data Warehouse Main Menu, select User Management. 2. Do one of the following: To edit an existing user, select the row for the user and click Edit. To change a user's password, select the row for the user and click Change password. To delete a user, select the row for the user and click Delete 3. To activate or deactivate a user, select the row for the user and click Activate or Deactivate. Configuring Reporting LDAP From the Data Warehouse portal, the Administrator can configure LDAP usage for Data Warehouse and Reporting. Steps 1. Log in as the administrator to the Data Warehouse portal. 2. On the lower left in the Advanced menu, click User Management.

228 228 OnCommand Insight Installation and Administration Guide 3. Click LDAP Configuration. 4. Mark the Enable LDAP box to start the LDAP user authentication and authorization process. 5. In the LDAP Configuration window, the majority of the fields contain default values. The default settings are valid for the Active Directory. Note: If you make any changes in this window, you must fill in the Directory lookup user and Directory lookup user password fields at the bottom. If you do not, the changes you make in the LDAP configuration will not be saved. User principal name attribute Attribute that identifies each user in the LDAP server (defaults to userprincipalname, which is globally unique). OnCommand Insight attempts to match the contents of this attribute with the username that has been supplied. Role attribute LDAP attribute that identifies the user role (defaults to memberof ). Mail attribute LDAP attribute that identifies the user address (defaults to mail). This is useful if you want to subscribe to the OnCommand Insight reports available from the OnCommand Insight portal. Note: OnCommand Insight picks up the user address the first time each user logs in and does not look for it after that. If the address changes on the LDAP server, make sure to change it manually in the OnCommand Insight database. Distinguished name attribute Referral Timeout (ms) LDAP servers (use comma to delimit) LDAP attribute that identifies the user distinguished name (defaults to distinguishedname ). Indication of whether to follow the path to other domains if there are multiple domains in the enterprise. Always use the default (follow ). Length of time to wait for a response from the LDAP server before timing out, in milliseconds (defaults to 2 seconds, which is adequate in all cases and should not be modified). IP address or DNS name to identify the LDAP server, typically provided in this format: ldap:// <ldap-server-address>:port or, to use the default port: ldap://<ldap-server-address> Note: To import the LDAP certificates, click Import Certificates and automatically import or manually locate the certificate files.

229 OnCommand Insight configuration and administration tasks 229 Domain OnCommand Insight server administrators group OnCommand Insight administrators group OnCommand Insight users group OnCommand Insight guests group Reporting administrators group Reporting pro authors group Reporting authors group Reporting consumers group LDAP node where OnCommand Insight should start looking for the LDAP user (typically the top-level domain for the organization). For example: DC=<enterprise>,DC=com Value of the Role Attribute that identifies the user as having Server Administrator privileges (defaults to sanscreen.server.admin ). Value of the Role Attribute that identifies the user as having Administrator privileges (defaults to sanscreen.admin). Value of the Role Attribute that identifies the user as having User privileges (defaults to sanscreen.users ). Value of the Role Attribute that identifies the user as having Guest privileges (defaults to sanscreen.guests ). Value of the Role Attribute that identifies the user as having Reporting administrator privileges (defaults to sanscreenreport.admins). See Reporting user roles for more information. Value of the Role Attribute that identifies the user as having Reporting pro author privileges (defaults to sanscreenreport.proauthors). Value of the Role Attribute that identifies the user as having Reporting author privileges (defaults to sanscreenreport.authors). Value of the Role Attribute that identifies the user as having Reporting consumer privileges (defaults to sanscreenreport.consumers). 6. If you changed any of the previous fields, enter Directory lookup values. Confirm the password and click Validate Password to check it on the server. 7. Click Update to save the changes. Setting up and running OnCommand Insight backups You can back up OnCommand Insight using the automatic daily backups, weekly backups, or a manual backup. You also need to configure backups for the Data Warehouse separately. About this task This procedure is described for customers using a Windows Internet Explorer browser.

230 230 OnCommand Insight Installation and Administration Guide Steps 1. To examine and set the backup options, log into the OnCommand Insight Admin Portal and click the Backup/Restore link. 2. The Daily database backups need to be enabled to be collected automatically. Click Enable to activate the automatic daily backups. 3. To configure automatic Weekly backups, perform these steps: a) Check the Enabled option. b) For Cleanup, select whether you want to keep the last 2 or 5 backups. c) In the Location field, type the directory path for storing the weekly backups. d) Click Update to save the weekly backup configuration. 4. If you want to create a Manual database backup, you have two selections to make: a) You need to identify Database information you want in the manual backup: