HP P9000 Command View Advanced Edition Suite Software 7.3.1-00 Administrator Guide (web)
Table Of Contents
- Administrator Guide (Web Version)
- Table of Contents
- Preface
- 1 System configuration and requirements
- System configuration
- Network security configuration
- Common security risks
- Level 1 security: Setting up a firewall and creating a separate management LAN
- Level 2 security: Placing managed devices behind the firewall and creating a separate management LAN
- Level 3 security: Dual-homed management servers and creating a separate management LAN
- Level 4 security: A flat network
- Management server requirements
- Host requirements
- Related products
- System requirements for managing copy pairs
- System configuration for managing copy pairs
- System configuration for managing copy pairs: Local management
- System configuration for managing copy pairs: Using a pair management server
- System configuration for managing copy pairs: Using a virtual command device server
- System configuration for managing copy pairs: Using an SVP (when defining copy pairs in a configuration definition file)
- System configuration for managing copy pairs: Using an SVP (when defining copy pairs as a device group)
- Device Manager agent requirements for managing copy pairs
- Storage system requirements for managing copy pairs
- Notes on using Device Manager when RAID Manager is already managing copy pairs
- System configuration for managing copy pairs
- 2 Network configuration
- Port settings
- Ports used by P9000 Command View AE Suite products
- Changing ports used by Common Component
- Changing the 23015/tcp port used by Common Component
- Changing the 23016/tcp port used by Common Component
- Changing the 23017/tcp port used by Common Component
- Changing the 23018/tcp port used by Common Component
- Changing the 23025/tcp port used by Common Component
- Changing the 23026/tcp port used by Common Component
- Changing the 23031/tcp port used by Common Component
- Changing the 23032/tcp port used by Common Component
- Registering firewall exceptions
- Network settings for management servers with multiple NICs
- Device Manager settings in IPv6 environments
- Changing the IP address or host name of the management server
- Changing the URL for accessing P9000 Command View AE Suite products
- Port settings
- 3 User account management
- 4 Security
- 5 Configuring Device Manager for use with related products
- 6 Setting up logs and alerts
- 7 Configuring Device Manager for CIM/WBEM
- Device Manager and CIM/WBEM
- CIM/WBEM functions in Device Manager
- Enabling CIM/WBEM functions
- Setting up ports used by CIM/WBEM
- Verifying properties for executing CIM
- Configuring service discovery
- Configuring performance information acquisition
- User account settings for using the CIM/WBEM functions
- 8 Setting up a cluster environment
- Verifying the management server environment
- Setting up a cluster environment
- Installing P9000 Command View AE Suite on cluster management servers (new installation)
- Installing P9000 Command View AE Suite on cluster management servers (upgrade or overwrite)
- Changing the management server environment from a non-cluster environment to a cluster environment
- Removing P9000 Command View AE Suite from a cluster
- 9 Starting and stopping services
- 10 Managing the database
- Managing databases
- Backing up databases
- Restoring databases
- Migrating databases
- 11 Using and maintaining the Device Manager agent
- Before using the Device Manager agent
- When to restart the Device Manager agent service
- Specifying the IP address of the Device Manager agent network adapter
- Applying storage system configuration changes to Device Manager server
- Reinstalling the Device Manager agent after a host OS upgrade
- Device Manager agent in a Windows host environment
- Device Manager agent in an AIX host environment
- Device Manager agent in a Linux host environment
- Setting up the Device Manager agent
- Setting Device Manager server information in Device Manager agent
- Automatically reporting host information to the Device Manager server
- Managing copy pairs
- Changing the Java execution environment
- Changing the user who executes the Device Manager agent service
- Property settings for hosts that manage 100 or more LUs
- Device Manager agent operations
- Configuration definition file for managing copy pairs
- Prerequisites for using a configuration definition file in Device Manager
- Parameters and requirements for the configuration definition file
- Detailed rules for configuration definition files
- Notes about creating a configuration definition file
- Required operations when creating or changing a configuration definition file
- Note about deleting copy pairs
- Device Manager agent commands
- Before using the Device Manager agent
- 12 Setting up Host Data Collector
- Installing Host Data Collector
- Prerequisites for installing Host Data Collector (Windows)
- Installing Host Data Collector (Windows)
- Prerequisites for installing Host Data Collector (Solaris or Linux)
- Installing Host Data Collector (Solaris or Linux)
- Notes on using Host Data Collector computers in a cluster configuration
- Registering a Host Data Collector computer on the management server
- Specifying the Host Data Collector environment settings
- Removing Host Data Collector
- Installing Host Data Collector
- 13 Troubleshooting
- Common problems and solutions
- Maintenance information that must be collected if a failure occurs
- Acquiring maintenance information on the management server
- About acquiring maintenance information on a Host Data Collector computer
- Acquiring maintenance information on a host (for a host managed by Host Data Collector)
- Acquiring maintenance information on a host (for a host managed by Device Manager agent)
- Acquiring a thread dump of the HBase Storage Mgmt Common Service (Windows)
- Acquiring a thread dump of the HCS Device Manager Web Service (Windows)
- Acquiring a thread dump of the HBase Storage Mgmt Common Service (Linux)
- Acquiring a thread dump of the HCS Device Manager Web Service (Linux)
- Checking audit log data
- 14 Support and other resources
- A Device Manager server properties
- Device Manager server property files
- Device Manager server configuration properties (server.properties file)
- server.http.host
- server.http.port
- server.https.port
- server.rmi.port
- server.http.entity.maxLength
- server.base.home
- server.horcmconfigfile.hostname
- server.base.initialsynchro
- server.cim.agent
- server.cim.support
- server.cim.support.job
- server.cim.support.protocol
- server.cim.http.port
- server.cim.https.port
- server.configchange.enabled
- server.logicalview.initialsynchro
- server.mail.enabled
- server.mail.from
- server.mail.smtp.host
- server.mail.smtp.port
- server.mail.smtp.auth
- server.mail.errorsTo
- server.eventNotification.mail.to
- server.mail.alert.type
- server.mail.alert.status
- server.subsystem.ssid.availableValues
- server.smisclient.indication.port
- server.agent.differentialrefresh.manual.enabled
- server.agent.differentialrefresh.periodical.enabled
- Device Manager database properties (database.properties file)
- Device Manager log output properties (logger.properties file)
- Device Manager dispatcher properties (dispatcher.properties file)
- server.dispatcher.message.timeout
- server.dispatcher.message.timeout.in.processing
- server.dispatcher.daemon.pollingPeriod
- server.dispatcher.traps.purgePeriod
- server.dispatcher.daemon.receiveTrap
- server.dispatcher.daemon.configUpdate.detection.interval
- server.dispatcher.daemon.autoSynchro.doRefresh
- server.dispatcher.daemon.autoSynchro.type
- server.dispatcher.daemon.autoSynchro.dayOfWeek
- server.dispatcher.daemon.autoSynchro.startTime
- server.dispatcher.daemon.autoSynchro.interval
- server.dispatcher.daemon.configUpdate.detection.variable.enabled
- server.dispatcher.daemon.autoSynchro.performance.doRefresh
- server.dispatcher.daemon.autoSynchro.performance.startTime
- server.dispatcher.daemon.autoSynchro.logicalGroup.doRefresh
- Device Manager MIME type properties (mime.properties file)
- Device Manager client properties (client.properties file)
- Device Manager security properties
- Device Manager SNMP trap log output properties (customizedsnmptrap.properties file)
- Properties for communicating with the host (host.properties file)
- Properties for connecting to Host Data Collector (hostdatacollectors.properties file)
- Properties for migrations (migration.properties file)
- Properties for connecting to PA (hppa.properties file)
- Properties for the CIM/WBEM functions (jserver.properties file)
- B Tiered Storage Manager server properties
- Tiered Storage Manager server property files
- Tiered Storage Manager server operations properties (server.properties file)
- server.rmi.secure
- server.rmi.port
- server.rmi.security.port
- server.base.initialsynchro
- server.mail.smtp.host
- server.mail.from
- server.mail.errorsTo
- server.mail.smtp.port
- server.mail.smtp.auth
- server.eventNotification.mail.to
- server.eventMonitoringIntervalInMinute
- server.migration.multiExecution
- server.checkOutVolumeRange
- server.migration.dataErase.defaultValue
- server.migrationPlan.candidateVolumeCountLimit
- server.migrationPlan.candidateCapacityGroupDisplayMaxCount
- server.migration.maxRetryCount
- server.migration.waitForPairDeleteInMinute
- server.migration.remainTimeForDeletePairInMinute
- Tiered Storage Manager GUI properties (client.properties file)
- Tiered Storage Manager database properties (database.properties file)
- Tiered Storage Manager properties for accessing Device Manager server (devicemanager.properties file)
- Tiered Storage Manager log output properties (logger.properties file)
- Tiered Storage Manager security properties
- C Host Data Collector properties
- Host Data Collector property files
- Properties related to Host Data Collector operation (hdcbase.properties file)
- Host Data Collector logger properties (logger.properties file)
- Properties related to the Host Data Collector's Java environment (javaconfig.properties file )
- Host Data Collector configuration properties (alps.properties file)
- Host Data Collector product properties (about.properties file)
- Host Data Collector logger properties (log4jconfig.properties file)
- D Device Manager agent properties
- Device Manager agent property files
- Device Manager agent properties for connecting to the Replication Manager server (agent.properties file)
- Device Manager agent properties for hldutil command operations (hldutil.properties file)
- Device Manager agent log output properties (logger.properties file)
- Device Manager agent properties for program information (programproductinfo.properties file)
- Device Manager agent operations properties (server.properties file)
- server.agent.port
- server.http.localPort
- server.http.port
- server.http.host
- server.http.socket.agentAddress
- server.http.socket.bindAddress
- server.agent.maxMemorySize
- server.agent.shutDownTime
- server.agent.JRE.location
- server.http.entity.maxLength
- server.http.security.clientIP
- server.server.authorization
- server.server.serverIPAddress
- server.server.serverPort
- server.agent.rm.centralizePairConfiguration
- server.agent.rm.cuLdevForm
- server.agent.rm.exclusion.instance
- server.agent.rm.location
- server.agent.rm.optimization.userHorcmFile
- server.agent.rm.horcm.poll
- server.agent.rm.pairDefinitionForm
- server.agent.rm.moduleTimeOut
- server.http.server.timeOut
- server.util.processTimeOut
- server.agent.evtwait.timeout
- server.agent.rm.ignorePairStatus
- E Commands executed by Host Data Collector
- Acronyms and abbreviations
- Index
server.agent.rm.optimization.userHorcmFile
Specify whether to optimize the user-created RAID Manager configuration definition files. To optimize
the file, specify true. If you do this, the file is updated so that Device Manager can use it. Also, when
the Device Manager agent starts or when the configuration definition file is updated by pair operations,
the following optimizations are performed:
• The unit ID, LDEV number, and serial number of a command device are added as comments.
• If the above command device becomes unavailable due to, for example, a change to the volume
name, the configuration definition file information is updated so that the command device can be
used.
• If the host is connected to multiple command devices in a storage system and only some of those
command devices are specified, the rest of the command devices are specified as reserved com-
mand devices.
• Command devices that are not being used are deleted.
• The CU and LDEV numbers of a command device and pair volume are added as a comment in
the format cu:ldev.
• If there are multiple definitions for a command device of the same storage system in an SLPR en-
vironment, rearrange the order of the command device definitions.
• Apply the value specified in the server.agent.rm.horcm.poll property to poll of the
HORCM_MON parameter in the configuration definition file.
Default: false
server.agent.rm.horcm.poll
Specify the value defined for poll of the HORCM_MON parameter in the configuration definition file
(the monitoring interval for copy pairs) in hundredths of a second. If monitoring is not being performed,
specify -1.
The value specified for this property is applied to the configuration definition file at the following
times:
• When a pair is created or added
• When the configuration definition file is optimized
Default: None
#
#: In a newly created configuration definition file, poll is set to 1000. When a pair is added to an
existing configuration definition file or when a configuration definition file is optimized, the existing
settings are used.
server.agent.rm.pairDefinitionForm
Specify which format should be used to specify pair volume information in the configuration definition
file when creating a pair: HORCM_DEV format or HORCM_LDEV format. If you want to unify the format
into the HORCM_DEV format, specify HORCM_DEV. If you want to unify the format into the HORCM_LDEV
format, specify HORCM_LDEV. We recommend that you use the HORCM_LDEV format.
The Device Manager agent decides which format should be used in the configuration definition file
when creating a pair according to the following conditions:
• Which format is used in the existing configuration definition file: HORCM_DEV format or HOR-
CM_LDEV format.
Device Manager agent properties404