Veritas CommandCentral Storage Installation Guide

Transcription

1 Veritas CommandCentral Storage Installation Guide for Microsoft Windows and UNIX 5.0 MP1

2 CommandCentral Storage Installation Guide The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version 5.0 MP1.3 Legal Notice Copyright 2008 Symantec Corporation. All rights reserved. Symantec, the Symantec logo, Veritas, CommandCentral, NetBackup, SANPoint, SANPoint Control, and Storage Foundation are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. Third-party software may be recommended, distributed, embedded, or bundled with this Symantec product. Such third-party software is licensed separately by its copyright holder. All third-party copyrights associated with this product are listed in the accompanying documentation. AIX is a registered trademark of IBM Corporation. HP-UX is a registered trademark of Hewlett-Packard Development Company, L.P. Linux is a registered trademark of Linus Torvalds. Solaris is a trademark of Sun Microsystems, Inc. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR and subject to restricted rights as defined in FAR Section "Commercial Computer Software - Restricted Rights" and DFARS , "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations.

3 Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement. Symantec Corporation Stevens Creek Blvd. Cupertino, CA

4 Technical Support Symantec Technical Support maintains support centers globally. Technical Support s primary role is to respond to specific queries about product feature and function, installation, and configuration. The Technical Support group also authors content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantec s maintenance offerings include the following: A range of support options that give you the flexibility to select the right amount of service for any size organization A telephone and web-based support that provides rapid response and up-to-the-minute information Upgrade insurance that delivers automatic software upgrade protection Global support that is available 24 hours a day, 7 days a week worldwide. Support is provided in a variety of languages for those customers that are enrolled in the Platinum Support program Advanced features, including Technical Account Management For information about Symantec s Maintenance Programs, you can visit our Web site at the following URL: Contacting Technical Support Select your country or language under Global Support. The specific features that are available may vary based on the level of maintenance that was purchased and the specific product that you are using. Customers with a current maintenance agreement may access Technical Support information at the following URL: Select your region or language under Global Support. Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to recreate the problem.

5 When you contact Technical Support, please have the following information available: Product release level Hardware information Available memory, disk space, and NIC information Operating system Version and patch level Network topology Licensing and registration Customer service Router, gateway, and IP address information Problem description: Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: Select your region or language under Global Support, and then select the Licensing and Registration page. Customer service information is available at the following URL: Select your country or language under Global Support. Customer Service is available to assist with the following types of issues: Questions regarding product licensing or serialization Product registration updates such as address or name changes General product information (features, language availability, local dealers) Latest information about product updates and upgrades Information about upgrade insurance and maintenance contracts Information about the Symantec Value License Program

6 Advice about Symantec's technical support options Nontechnical presales questions Maintenance agreement resources Additional Enterprise services Issues that are related to CD-ROMs or manuals If you want to contact Symantec regarding an existing maintenance agreement, please contact the maintenance agreement administration team for your region as follows: Asia-Pacific and Japan: Europe, Middle-East, and Africa: North America and Latin America: Symantec offers a comprehensive set of services that allow you to maximize your investment in Symantec products and to develop your knowledge, expertise, and global insight, which enable you to manage your business risks proactively. Enterprise services that are available include the following: Symantec Early Warning Solutions These solutions provide early warning of cyber attacks, comprehensive threat analysis, and countermeasures to prevent attacks before they occur. Managed Security Services Consulting Services Educational Services These services remove the burden of managing and monitoring security devices and events, ensuring rapid response to real threats. Symantec Consulting Services provide on-site technical expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring and management capabilities, each focused on establishing and maintaining the integrity and availability of your IT resources. Educational Services provide a full array of technical training, security education, security certification, and awareness communication programs.

7 To access more information about Enterprise services, please visit our Web site at the following URL: Select your country or language from the site index.

8

9 Contents Technical Support... 4 Chapter 1 Introduction to CommandCentral Storage About Veritas CommandCentral Storage Components of CommandCentral Storage Chapter 2 Chapter 3 Planning your CommandCentral Storage installation CommandCentral Storage installation options Resources you need to plan and complete your installation Choosing CommandCentral Storage host systems Choosing a Management Server host Choosing a managed host Choosing an Agent Push Install Utility host The CommandCentral Storage Console host Storage network configurations affecting CommandCentral Storage Typical CommandCentral Storage configurations Single-fabric storage networks Multi-fabric storage networks Planning to upgrade your CommandCentral Storage Management Server from 4.x to 5.0 MP CommandCentral Storage host and firewall requirements CommandCentral Storage operating system requirements CommandCentral Storage firewall requirements CommandCentral Storage setup requirements... 35

10 10 Contents Chapter 4 Installing and uninstalling CommandCentral Storage Installation prerequisites CommandCentral Storage install and supported configuration prerequisites CommandCentral Storage dependencies with component packages Host clock settings /tmp directory settings Sun Enterprise Authentication Mechanism Symantec Product Authentication Service must be installed before installing CommandCentral Storage on a Storage Foundation 5.0 for Windows host Symantec Product Authentication Service installed in Root Broker only mode must be upgraded on Windows Symantec Product Authentication Service in VCS cluster must be version (or later) to install managed host Managed host installation on Windows should not be run simultaneously with another process that uses the Installshield scripting engine (IDriver.exe) Solaris 10 hosts must have zone support installed for Management Server installation Management Server installation fails on a host with core Solaris 10 installation ssh prerequisites for remote installation of UNIX managed hosts Upgrading the Symantec Product Authentication Service in a Veritas Cluster Server environment About the upgrade Preparing for the upgrade Upgrading on a node in a non-secure VCS cluster Upgrading on a node in a secure VCS cluster Installing CommandCentral Storage on UNIX Verifying the CommandCentral Storage installations on UNIX Verifying Management Server installation Verifying managed host installation Uninstalling CommandCentral Storage on UNIX Installing CommandCentral Storage on Windows Verifying the CommandCentral Storage installations on Windows Verifying Management Server installation Verifying managed host installation Verifying Agent Push Install Utility installation... 60

11 Contents 11 Uninstalling CommandCentral Storage on Windows Shared components remaining after uninstallation Chapter 5 Upgrading to CommandCentral Storage 5.0 MP Upgrade prerequisites Authentication Service prerequisites Upgrading the CommandCentral Storage Management Server to 5.0 MP About the Management Server upgrade Preparing to save 4.x user-defined discovery data Saving the discovery data Verifying that your discovery data was saved successfully Troubleshooting the data-saving step Selecting configuration options Upgrading the Management Server on Solaris Upgrading the Management Server on Windows Upgrading the CommandCentral Storage managed host to 5.0 MP Upgrading the UNIX managed host Upgrading the Windows managed host Upgrading the CommandCentral Storage Agent Push Install Utility to 5.0 MP Chapter 6 Managing CommandCentral Storage managed hosts remotely About the Agent Push Install Utility Installing managed hosts using the Agent Push Install Utility on Windows Selecting target hosts for the Agent Push Install Utility on Windows Configuring managed host packages on target hosts on Windows Running the install action on target hosts on Windows Agent Push Install Utility icon legend (Windows) Uninstalling or modifying managed hosts using the Agent Push Install Utility on Windows Remote agent installation on UNIX... 94

12 12 Contents Appendix A CommandCentral Storage software packages About CommandCentral Storage software packages CommandCentral Storage UNIX component packages Appendix B CommandCentral Storage managed host silent install About managed host silent installs General considerations for managed host silent installations Managed host silent install variables and arguments Performing a managed host silent install on UNIX Performing a managed host silent install on UNIX - OM and DM with the array management option Performing a managed host silent install on UNIX - OM and DM Performing a managed host silent install on UNIX - OM with the array management option Performing a managed host silent install on UNIX - OM Performing a managed host silent install on UNIX - DM Performing a managed host silent install on Solaris - OM and DM with the NetApp discovery option Performing a managed host silent install on Solaris - DM with the NetApp discovery option Performing a managed host silent install on Windows Performing a managed host silent install on Windows - OM and DM Performing a managed host silent install on Windows - OM Performing a managed host silent install on Windows - OM with the array management option Performing a managed host silent install on Windows - DM Performing a managed host silent install on Windows - DM with the NetApp discovery option Performing a managed host silent install on Windows - OM with the array management option and DM Performing a managed host silent install on Windows - DM with the NetApp discovery option and OM Performing a managed host silent install on Windows - OM with the array management option and DM with the NetApp discovery option

13 Contents 13 Appendix C Mounting the CommandCentral Storage 5.0 MP1 product disc on UNIX Mounting the CommandCentral Storage 5.0 MP1 product disc on HP-UX Mounting the CommandCentral Storage 5.0 MP1 product disc on AIX Mounting the CommandCentral Storage 5.0 MP1 product disc on Linux Mounting the CommandCentral Storage 5.0 MP1 product disc on Solaris Index

14 14 Contents

15 Chapter 1 Introduction to CommandCentral Storage This chapter includes the following topics: About Veritas CommandCentral Storage Components of CommandCentral Storage About Veritas CommandCentral Storage Veritas CommandCentral Storage by Symantec represents an entire storage resource management (SRM) solution, giving you what you need to manage your storage infrastructure more effectively. It gives you the following capabilities: Offers a single console from which data center administrators deploy, manage, and expand a multi-vendor networked storage environment. The CommandCentral Storage Console seamlessly integrates performance and policy management, storage provisioning, and zoning capabilities to ensure that the storage infrastructure runs as efficiently as possible. The Console enables users to set policies that automate notification, recovery, and other user-definable actions. Discovers and tracks the utilization and allocation of storage resources down to the disk level. The reporting features in CommandCentral Storage provide a complete and detailed view into precisely how and where storage for office documents, files, applications, , and databases is used in your enterprise. Shows usage trends and makes forward projections. You can gather data both locally and remotely (through a managed host). This means you can get baseline information without huge deployment costs. Armed with this data, you can do predictive modeling to analyze the return on your storage investment. You also have what you need to implement a program of departmental chargeback.

16 16 Introduction to CommandCentral Storage Components of CommandCentral Storage Using CommandCentral Storage together with other Symantec software, IT managers have the tools they need to perform real, active, end-to-end storage resource management and make strategic decisions about their future storage needs. Components of CommandCentral Storage Based on a distributed client-server architecture, CommandCentral Storage consists of the following components: CommandCentral Storage Management Server provides discovery of network and storage resources, storage arrays, hosts, files, and applications; provides data collection and logging, event and policy management, and notification services; generates HTML pages containing content gathered during discovery, data collection, and event and policy management. CommandCentral Storage managed host discovers additional information about objects on the storage network that may be configured out of view of the Management Server (such as those devices on a separate zone or fabric). On UNIX systems, the managed host installer will handle the installation of additional remote hosts. CommandCentral Storage Console displays information compiled from the Hardware Abstraction Layer (HAL) and other Management Server components through a standard Web browser. The console is an integrated part of the Management Server. CommandCentral Storage Agent Push Install Utility a Windows application that enables you to install, upgrade, or uninstall Windows managed hosts. Installation, upgrade, and uninstall of UNIX managed hosts is accomplished via the product s install and uninstall scripts. For a complete listing of new features, see the CommandCentral Storage Release Notes. Figure 1-1 shows a diagram of CommandCentral Storage components.

17 Introduction to CommandCentral Storage Components of CommandCentral Storage 17 XML HTTPS 8443 Web Browser Figure 1-1 CommandCentral Storage architecture overview Management Server Host Web Server 2994 Root Broker List of ABs Web Engine Authentication Client Authentication Broker PBX cc_users admin OS Jo, Tim, etc. HAL Agent, AM, CCStorage, CHM, DM LHM / HAL Explorers Alarm Service Alert Manager Central HAL Manager (CHM) TCP/IP 1885 Trap Processor SNMP UDP CCS Database HALCHM, ccstor, vxam DM Importer 2994 DM Database ccstor Management Server PBX Database Server PBX Managed Host LHM / HAL Explorers SICL DM Explorers 1556 Authentication Client

18 18 Introduction to CommandCentral Storage Components of CommandCentral Storage

19 Chapter 2 Planning your CommandCentral Storage installation This chapter includes the following topics: CommandCentral Storage installation options Resources you need to plan and complete your installation Choosing CommandCentral Storage host systems Storage network configurations affecting CommandCentral Storage Typical CommandCentral Storage configurations CommandCentral Storage installation options CommandCentral Storage offers several options for installation, depending on what your network needs. This chapter includes the installation options as well as the details of what each option offers for features. You can install CommandCentral Storage in the following ways: Standard (both Data Module and Operations Module): All product features. Operations Module only: Users can view detailed discovery data for storage objects, switches, and fabrics; provision storage; and create and manage policies. Data Module only: Users can view objects, display storage and consumption reports, and track specialized data such as storage consumption by application, by file system, and on a per-file and per-user basis.

20 20 Planning your CommandCentral Storage installation CommandCentral Storage installation options With each installation option, you can establish user credentials such that authorized users can access the product to perform sensitive management tasks and other users can perform only a more basic set of functions. Table 2-1 summarizes the features you get with each of the CommandCentral Storage installation options. Table 2-1 CommandCentral Storage Data Module (DM) and Operations Module (OM) features Feature Discover and visualize disk arrays; discover and create storage enclosures Discover and visualize NetApp devices as unified storage devices Discover and visualize NetApp replication features Discover and display database instances: Oracle, Sybase, DB2, and SQL Server Discover and display applications: Veritas NetBackup, Veritas Cluster Server, Exchange Server Discover and display physical disks and disk characteristics associated with specific LUNs Discover hosts and file systems associated with a given application Discover and visualize storage network elements such as switches and fabrics Display usage projections for hosts, databases, and NetApp storage devices Provide application health views, utilization details, and notifications for storage resources associated with specific hosts and applications Display largest files, file types breakdown, directories size, number of files, owner, and file aging Perform centralized policy management DM OM

21 Planning your CommandCentral Storage installation CommandCentral Storage installation options 21 Table 2-1 CommandCentral Storage Data Module (DM) and Operations Module (OM) features (continued) Feature Monitor network activity using collectors Provision storage by binding LUNs to hosts and applications Change impact analysis: identify how changes will affect resource availability for a given application Construct LUNs from physical disks Select multiple LUNs and perform masking and binding on them Organize storage resources by defining groups Create and manage zones to enhance network security Create object dependency groups with associated resources; display rolled-up status of an application based on status of dependent storage components Make paths available to Veritas Volume Manager hosts for Dynamic Multipathing Display reports showing storage capacity Display reports showing storage consumption Display reports showing alerts Display reports showing port usage and performance for switch ports, hosts, and arrays Save reports to file; reports to designated users Push install managed host code to remote hosts, either individually or in batch DM OM

22 22 Planning your CommandCentral Storage installation Resources you need to plan and complete your installation Resources you need to plan and complete your installation You need several documents and resources to plan and successfully complete your installation. To install any CommandCentral Storage, you need the following: CommandCentral Storage Hardware and Software Compatibility List This document is updated regularly at: CommandCentral Storage Release Notes The CommandCentral Storage Hardware and Software Configuration Guide, which describes the steps you must take for CommandCentral Storage to properly discover, monitor, and manage supported devices. A CommandCentral Storage product license key (possibly multiple keys for different product offerings and features) Administrator or root accounts and passwords for all target hosts A checklist of the CommandCentral Storage features you plan to use. See Storage network configurations affecting CommandCentral Storage on page 25. A diagram of your storage network (suggested for your reference) For upgrading a current installation, the CommandCentral Storage Migration Guide, which describes the steps you must take in order to upgrade your present CommandCentral Storage installation. Choosing CommandCentral Storage host systems Determine system requirements for CommandCentral Storage hosts. See the CommandCentral Storage Release Notes. In addition to these requirements, there are other factors, such as your storage network s design or the dependencies of the some of the product s components, that you should consider when choosing hosts. Choose hosts after considering the following information: Choosing a Management Server host Choosing a managed host Choosing an Agent Push Install Utility host

23 Planning your CommandCentral Storage installation Choosing CommandCentral Storage host systems 23 The CommandCentral Storage Console host Choosing a Management Server host Choosing a managed host The Management Server resides on the primary host and acts as the central point in CommandCentral Storage that coalesces discovery, monitoring, and management data from managed hosts and explorers. To identify the kind of system you need to host the Management Server, use the following criteria: The system should meet or exceed the system requirements. See system requirements in the CommandCentral Storage Release Notes. The system should provide data security and space for a growing database as the Management Server discovers new network objects and monitors network events. Ideally, the system should have RAID-protected storage and the capacity to grow its file systems. The system should have a connection to the principal switch on your storage network fabric redundant connections if possible. Additionally, if zones are implemented on the storage network, the Management Server host should be zoned together with the switch to which it is connected. The system should not be a cluster node host running Veritas Cluster Server (VCS) or Veritas Application Director (VAD); installing the Management Server in a cluster is not a supported configuration. Review information about the Management Server and its architecture. See the CommandCentral Storage Administrator s Guide. A CommandCentral Storage managed host serves as an extra set of eyes for the Management Server. When objects on the storage network are zoned apart from the Management Server, it relies on the managed hosts to discover the objects and report back with information about them. The managed hosts maximize CommandCentral Storage s ability to discover all objects on the fabric. Also, managed hosts might contain some applications that you want CommandCentral Storage to discover and monitor. To identify the kind of system you need for a managed host, use the following criteria: The system should meet or exceed the system requirements. See system requirements in the CommandCentral Storage Release Notes.

24 24 Planning your CommandCentral Storage installation Choosing CommandCentral Storage host systems You should install the managed host on every host on the storage network, if possible. You cannot install the managed hosts on the same host as the Management Server. The system can be a cluster node host running Veritas Cluster Server (VCS) or Veritas Application Director (VAD). Note: A managed host does not have to run the same operating system as the Management Server. For example, the Management Server can run on a Solaris system and the managed host reporting to the Management Server can run on Windows. Refer to information about the CommandCentral Storage managed host and its architecture. See the CommandCentral Storage Administrator s Guide. Choosing an Agent Push Install Utility host The CommandCentral Storage Agent Push Install Utility provides a centralized interface that enables you to manage (install, upgrade, or uninstall) managed hosts on multiple remote Windows hosts. This utility facilitates managed host deployment and improves your efficiency, because it does not require you to physically install the managed host on hosts spread throughout your enterprise. You can manage multiple UNIX managed hosts by using the product s install and uninstall scripts. To identify the kind of system you need to host the utility, use the following criteria: The system should meet or exceed the system requirements. See system requirements in the CommandCentral Storage Release Notes. A system running the utility must have a network connection to the various remote hosts to which you want to push the managed host. For information about the Agent Push Install Utility and its architecture, see the CommandCentral Storage Administrator s Guide. See About the Agent Push Install Utility on page 79. The CommandCentral Storage Console host The CommandCentral Storage Console is a graphical user interface that provides a central point to display and manage storage resources, create and modify policies,

25 Planning your CommandCentral Storage installation Storage network configurations affecting CommandCentral Storage 25 provision storage, administer access control, and view reports. The Console is automatically installed with the CommandCentral Storage Management Server. You access the Console through a web browser. One of the following Web browsers is required to run the Console: Microsoft Internet Explorer 6.x (Windows only) Mozilla 1.7 (Solaris only) Mozilla Firefox 1.07, 1.5, or x (Windows only) Your browser must support either JScript 5.5 (provided with Microsoft Internet Explorer 6.x) or JavaScript 1.2. Additionally, for Internet Explorer, Secure Sockets Layer (SSL) 3.0 ActiveX scripting must be enabled. If you are using pop-up blockers, either disable them or configure them to accept pop-ups from the CommandCentral Storage Management Servers to which you will connect. To display the CommandCentral Storage Topology Map in a Web browser, your workstation must have at least Java 5 (version 1.5) installed. Note: For Internet Explorer 6.0 on Windows 2000 (Server, Advanced Server, or Datacenter Server) and Windows 2003 Server (Standard Edition, Datacenter Edition, Enterprise Edition, or Web Edition), set the default Intranet zone security level to MEDIUM or lower. Storage network configurations affecting CommandCentral Storage Some CommandCentral Storage features are affected by how you configure your storage network. By deciding during the planning phase which features to use, you can identify the device configuration tasks that apply to you. Device configuration affects the features listed in Table 2-2. Table 2-2 Feature In-band and out-of-band discovery Device configuration and CommandCentral Storage features Description In-band discovery refers to finding objects over the Fibre Channel network. Out-of-band discovery refers to finding objects over an IP network.

26 26 Planning your CommandCentral Storage installation Typical CommandCentral Storage configurations Table 2-2 Feature Zoning LUN security Policies and reports In-context launch of third-party applications Device configuration and CommandCentral Storage features (continued) Description CommandCentral Storage lets you create, modify, and delete zones. The application can perform hard (port-level) or soft (advisory) zoning for switches in a fabric, based on how you configure the switch itself. LUN security refers to making storage array resources available to hosts on your storage network. It provides more granular control over host access to individual LUNs within an array. LUN security includes LUN binding and LUN masking. CommandCentral Storage can use policies to monitor conditions and take action when those conditions are met. An extensive set of predefined policies ship with the application. These policies detect and monitor properties for switches, switch ports, hosts, and disk arrays. (Examples of monitored conditions include: status, discarded frames, disk temperature, link failures, and so on.) Administrators can use these policies out of the box, modify the default conditions and actions for each policy, or create their own policies. The application also ships with a number of reports that provide inventory of fabrics, devices, hosts, switches, HBAs, and groups, as well as performance analysis. As well as providing its own tools and wizards, CommandCentral Storage can launch third-party applications. Note: You can launch a third-party application only if it is installed on the same host where you are running the browser to view the CommandCentral Storage Console. Typical CommandCentral Storage configurations A typical full installation of CommandCentral Storage consists of a single Management Server, multiple managed hosts, and multiple Consoles. The actual number of managed host and Console installations may vary according to user needs. Decide how to install the components on single-fabric and multi-fabric storage networks by following these guidelines: Single-fabric storage networks Multi-fabric storage networks

27 Planning your CommandCentral Storage installation Typical CommandCentral Storage configurations 27 Single-fabric storage networks To optimize CommandCentral Storage discovery, monitoring, and management capabilities, you should ensure that every object on the fabric is visible to the Management Server or a managed host (that reports its discovery findings back to the Management Server). You should install the managed host on as many storage network-attached hosts as possible so that CommandCentral Storage can discover which hosts have OS handles for each storage device. If an object is zoned apart from all hosts on the fabric, CommandCentral Storage will not be able to fully discover that object s attributes. You should install the Console on as many client systems as the administrator and other users require. Each client system must have network access to the Management Server host; if desired, you can install the Console on the same system as the Management Server or managed host. Caution: Do not install more than one Management Server on the same storage network fabric. Multi-fabric storage networks On a multi-fabric storage network, decide whether to manage the fabrics together or individually. If the fabrics are each managed individually, then the configuration described for single-fabric storage networks may be used for each fabric. To manage all fabrics from a single CommandCentral Storage install, you must configure your storage network using the following guidelines in this order: Install the Management Server on any fabric most likely the largest or most important fabric. On the same fabric as the Management Server, install the managed host on as many hosts as possible (as described in the section describing single-fabric storage networks). On every other fabric, configure one managed host to run the GS explorer (GS). That managed host should have a connection to the principal switch on its fabric. You can configure an managed host to run GS through the Console. See the CommandCentral Storage Administrator s Guide for more information. Install other managed host on every fabric in such a way that every object on the fabric is visible to at least one managed host.

28 28 Planning your CommandCentral Storage installation Typical CommandCentral Storage configurations Caution: Do not install more than one Management Server on the same storage network fabric. Planning to upgrade your CommandCentral Storage Management Server from 4.x to 5.0 MP1 Upgrading the CommandCentral Storage Management Server from version 4.x to version 5.0 MP1 requires careful planning to preserve your current CommandCentral Storage environment. See the CommandCentral Storage Migration Guide.

29 Chapter 3 CommandCentral Storage host and firewall requirements This chapter includes the following topics: CommandCentral Storage operating system requirements CommandCentral Storage firewall requirements CommandCentral Storage setup requirements CommandCentral Storage operating system requirements Table 3-1 provides operating system requirements for CommandCentral Storage hosts. Table 3-1 Component CommandCentral Storage Management Server CommandCentral Storage operating system requirements Operating systems supported Solaris Windows Server

30 30 CommandCentral Storage host and firewall requirements CommandCentral Storage firewall requirements Table 3-1 Component CommandCentral Storage managed host CommandCentral Storage operating system requirements (continued) Operating systems supported Solaris HP-UX AIX Red Hat Linux Windows Server CommandCentral Storage Console Agent Push Install Utility Any platform with network access to the Server host and a supported Web browser. The minimum recommended resolution for the Console is 1024 x 768. For information about supported browsers, see the CommandCentral Storage Release Notes. Windows Server Note: For more information about particular operating system versions supported and updates required to run CommandCentral Storage, see the CommandCentral Storage Release Notes. CommandCentral Storage firewall requirements For the Management Server and managed hosts to communicate across a firewall, the following requirements must be met: The firewall must be configured to allow https access to a specific port. (See the table that follows). A range of ports for sending information must be specified in the Management Server. If your Windows host has the Windows Firewall enabled, and it is being configured as a management host, you will have to open port 4032 (or, disable the Windows Firewall). Authorization commands may hang on some later versions of Windows that enable the Windows Firewall by default, unless you make this change. Note: Some device explorers use hardware vendor command line tools. Because of this, you must ensure that all firewall requirements for using the CLIs have been met according to the vendor's specifications.

31 CommandCentral Storage host and firewall requirements CommandCentral Storage firewall requirements 31 For more information on the specific ports required to communicate between HAL explorers and device controllers, consult the topic related to the specific device. See the CommandCentral Storage Hardware and Software Configuration Guide CommandCentral Storage uses the default ports in Table 3-2 to transfer information. Figure 3-1 that immediately follows this table also shows these default port assignments: Table 3-2 CommandCentral Storage default port assignments Port Protocol Initiator - Recipient Bidirectional (Yes/No) Purpose Impact if Blocked 161 SNMP Devices - Alarm Service on Management Server No Alert and performance data (monitoring) in CommandCentral Storage Incomplete alert and performance data in CommandCentral Storage. 162 UDP Management Server - other No UDP Traps are sent as a notification mechanism Traps cannot be used as a notification method to send information to another management application. 162 UDP Devices - Management Server No UDP Traps are used as a data source for monitoring storage network Traps cannot be used as a backup mechanism for SNMP polling CORBA Various communications to and from Management Server, Authentication Broker, and managed hosts No Many purposes such as: authentication, monitoring, discovery, file and mail scanning, etc. CommandCentral Storage will not function SICL on managed host - Alert Manager on Management Server Yes Alert and performance data (monitoring) in CommandCentral Storage Incomplete alert and performance data in CommandCentral Storage.

32 32 CommandCentral Storage host and firewall requirements CommandCentral Storage firewall requirements Table 3-2 CommandCentral Storage default port assignments (continued) Port Protocol Initiator - Recipient Bidirectional (Yes/No) Purpose Impact if Blocked 1556 DM explorers on managed host - DM importer on Management Server Yes File scanning No file scanning data and no data available for reports TCP/IP Alarm Service - Alert Manager No Trap sharing None. Not used across firewall SSL 4.x Agent - migration explorer on Management Server No Enables communication between the 4.x Agent and the Management Server The Management Server will not receive data from the 4.x Agent Web Engine - Authentication Service running within Symantec Web Server (VRTSweb) No User authentication Users will not be able to log in to the Console 2821 Authentication Service running within Symantec Web Server (VRTSweb) - Authentication Service and Authorization Service on Management Server No User authorization Users will not be able to log in to the Console 2994 JDBC database - Web Engine Web Engine - database Yes Store settings None. Not used across firewall JDBC DM database - Web Engine No Report data, store settings None. Not used across firewall. Web Engine - DM database 2994 JDBC Database - CHM CHM - Database No Agent discovery, store settings None. Not used across firewall JDBC Database - Alert Manager Alert Manager - Database Yes Policy, collectors, alerts, store settings None. Not used across firewall.

33 CommandCentral Storage host and firewall requirements CommandCentral Storage firewall requirements 33 Table 3-2 CommandCentral Storage default port assignments (continued) Port Protocol Initiator - Recipient Bidirectional (Yes/No) Purpose Impact if Blocked 5431 SICL running on 4.x Agent - Alert Manager on Management Server No 8181 HTTP over TCP/IP Web browser - Web Engine Yes Run CommandCentral Storage Console Users will not be able to access the Console HTTPS over TCP/IP Web Browser - Web Engine Yes Run CommandCentral Storage Console Users will not be able to access the Console x DM explorers - DM importer on Management Server No File scanning and reports based on on 4.x Agent data No file scanning data for 4.x Agents.

34 34 CommandCentral Storage host and firewall requirements CommandCentral Storage firewall requirements Figure 3-1 CommandCentral Storage default ports XML HTTPS 8443 Web Browser Management Server Host Web Server 2994 Root Broker List of ABs Web Engine Authenication Client Authentication Broker PBX cc_users admin OS Jo, Tim, etc. HAL Agent, AM, CCStorage, CHM, DM LHM / HAL Explorers Alarm Service Alert Manager Central HAL Manager (CHM) TCP/IP 1885 Trap Processor SNMP UDP CCS Database HALCHM, ccstor, vxam DM Importer 2994 DM Database ccstor Management Server PBX Database Server PBX Managed Host LHM / HAL Explorers SICL DM Explorers 1556 Authenication Client

35 CommandCentral Storage host and firewall requirements CommandCentral Storage setup requirements 35 CommandCentral Storage setup requirements You must configure the managed hosts to communicate with and send discovery information to the Management Server. At the time you install the managed host product, you specify the CommandCentral Storage Management Server with which the managed host communicates. When adding managed hosts, you must decide whether to enable switch and array exploration. (By default, switch and array exploration are DISABLED.) Enabling switch exploration on a managed host causes the managed host s GS explorer (GS) to run. See the CommandCentral Storage Administrator s Guide. To enable users to select a domain at logon, Windows Management Server hosts must be configured either in DNS or with a fully-qualified domain name.

36 36 CommandCentral Storage host and firewall requirements CommandCentral Storage setup requirements

37 Chapter 4 Installing and uninstalling CommandCentral Storage This chapter includes the following topics: Installation prerequisites Upgrading the Symantec Product Authentication Service in a Veritas Cluster Server environment Installing CommandCentral Storage on UNIX Verifying the CommandCentral Storage installations on UNIX Uninstalling CommandCentral Storage on UNIX Installing CommandCentral Storage on Windows Verifying the CommandCentral Storage installations on Windows Uninstalling CommandCentral Storage on Windows Installation prerequisites After reviewing your network needs and planning your CommandCentral Storage installation, you are ready to proceed with the installation itself. This chapter includes the specific instructions required to install CommandCentral Storage Management Server and the CommandCentral Storage managed hosts. You should verify the CommandCentral Storage install and supported configuration prerequisites prior to starting your installation. See CommandCentral Storage install and supported configuration prerequisites on page 39.

38 38 Installing and uninstalling CommandCentral Storage Installation prerequisites You should verify the CommandCentral Storage installation directory dependencies prior to starting your installation. See CommandCentral Storage dependencies with component packages on page 39. You should verify host clock settings prior to starting your installation. See Host clock settings on page 39. You should verify the /tmp directory settings prior to installing on Solaris. See /tmp directory settings on page 40. You should verify that the Sun Enterprise Authentication Mechanism is present prior to installing the Management Server on Solaris. See Sun Enterprise Authentication Mechanism on page 40. You should verify that the Symantec Product Authentication Service in the VCS cluster is version 4.3 prior to installing a managed host. See Symantec Product Authentication Service in VCS cluster must be version (or later) to install managed host on page 43. You should verify that the Symantec Product Authentication Service is installed before installing CommandCentral Storage on a Storage Foundation 5.0 for Windows host. See Symantec Product Authentication Service must be installed before installing CommandCentral Storage on a Storage Foundation 5.0 for Windows host on page 40. You should verify that the Symantec Product Authentication Service is installed in Root + Authentication Broker mode before installing the CommandCentral Storage Management Server on a Windows host. See Symantec Product Authentication Service installed in Root Broker only mode must be upgraded on Windows on page 41. You should verify that no process that uses the Installshield scripting engine is running while installing the managed host on a Windows. See Managed host installation on Windows should not be run simultaneously with another process that uses the Installshield scripting engine (IDriver.exe) on page 43. You should verify that Solaris 10 hosts have zone support installed prior to Management Server installation. See Solaris 10 hosts must have zone support installed for Management Server installation on page 43.

39 Installing and uninstalling CommandCentral Storage Installation prerequisites 39 You should verify the ssh prerequisites before performing remote installations on UNIX managed hosts. See ssh prerequisites for remote installation of UNIX managed hosts on page 45. CommandCentral Storage install and supported configuration prerequisites Before installing CommandCentral Storage 5.0 MP1, it is important to note the following: The CommandCentral Storage Management Server must be installed first The CommandCentral Storage Managed Hosts must now specify their target server at install time The CommandCentral Storage Management Server must be up and running before the CommandCentral Storage managed host is installed. DNS lookup should be successful from the Management Server to the managed host, and from the managed host to the Management Server. In a non-dns environment, specify a network reachable IP address for the Management Server during the managed host installation. Additionally, ensure that the managed host is reachable from the Management Server on the IP address specified during managed host configuration. The CommandCentral Storage Management Server cannot be located on the same server as the CommandCentral Service server components CommandCentral Storage dependencies with component packages Host clock settings Before installing CommandCentral Storage 5.0 MP1 on all Unix platforms, it is important to note that the CommandCentral Storage installer has internal dependencies with the configuration files used by different component packages. Therefore it is recommended that you run the./installccstor command directly from the UNIX directory. If you run the installccstor command from directories other than the UNIX directory, the CommandCentral Storage installer may not be able to find the correct configuration files used by the component packages and abort the installation. Verify that the clock and time zone settings are correct for each host where you plan to install CommandCentral Storage. To ensure the success of all the

40 40 Installing and uninstalling CommandCentral Storage Installation prerequisites /tmp directory settings installations, it is important that each host s clock and time zone setting be accurate to its location. If installing the managed host on Solaris, verify that the /tmp directory has default permissions. The managed host installation will fail if the user, group, and other profiles do not have write permission to the /tmp directory. If the managed host installation fails, you can troubleshoot the installation by reviewing the install logs. If the install "checkinstall" is not able to create directories below the /tmp directory, change the directory permissions and re-run the installation. To change the /tmp directory permissions Type the following commands: # chmod 1777 /tmp # chown root Sun Enterprise Authentication Mechanism If installing the Management Server on Solaris, verify that the Sun Enterprise Authentication Mechanism (SEAM) is present. During installation, the CommandCentral Storage installer verifies if the Sun Enterprise Authentication Mechanism is present by checking for the following files: /etc/gss/mech /usr/lib/libgss.so.1 /usr/lib/gss Prior to installation, verify that the files exist on the target host. If the files are not found, the installation program will fail. Symantec Product Authentication Service must be installed before installing CommandCentral Storage on a Storage Foundation 5.0 for Windows host Before you install CommandCentral Storage on a Windows host that has Storage Foundation 5.0 installed, you must have the Symantec Product Authentication Service installed.