Veritas™ Resiliency Platform 2.2 Deployment Guide
- Section I. Overview and planning
- Overview of Resiliency Platform
- Recovery to premises using third-party replication technologies
- Recovery to premises using Resiliency Platform Data Mover
- Recovery to AWS using Resiliency Platform Data Mover
- Recovery to vCloud Using Resiliency Platform Data Mover
- System requirements
- Section II. Deploying and configuring the virtual appliances
- Section III. Setting up and managing the resiliency domain
- Setting up the resiliency domain
- Managing Infrastructure Management Servers
- Managing NetBackup and NetBackup Appliances
- Adding NetBackup master server
- Managing Veritas InfoScale Operations Manager Server
- Managing Resiliency Platform Data Mover gateway pairing
- Setting up the resiliency domain
- Section IV. Adding the asset infrastructure
- Managing asset infrastructure
- Preparing and maintaining host assets
- Managing Hyper-V virtualization server assets
- Managing VMware virtualization server assets
- About adding a host for discovery of VMware servers
- Managing enclosure assets
- About the discovery host for enclosures
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Managing asset infrastructure
- Section V. Managing users and global product settings
- Managing licenses
- Managing user authentication and permissions
- Configuring authentication domains
- Managing service objectives
- Managing reports
- Managing settings
- Section VI. Updating or uninstalling the product
- Updating Resiliency Platform
- Using YUM virtual appliance as YUM server
- Uninstalling Resiliency Platform
- Updating Resiliency Platform
- Section VII. Troubleshooting and maintenance
- Troubleshooting and maintenance
- Displaying risk information
- Troubleshooting and maintenance
- Section VIII. Reference
Verifying NaviSecCLI communication with CLARiiON enclosure
Use the following procedure to verify the communication of NaviSecCLI with the CLARiiON enclosure.
To verify that the NaviSecCLI can communicate with CLARiiON arrays
- Enter the following command at the command prompt of CLARiiON management host:
naviseccli -h arrayIPAddress -user userName -password passWord -scope userScope networkadmin -get
Where:
arrayIPAddress is the IP address, the fully qualified domain name, or the name of one of the storage processors in the array.
userName is a valid user name for the account in the array.
passWord is the password for userName.
userScope is the scope of the user that you specified when you created the account in the array. It can be Local, Global, or LDAP.
Review the information that displays:
If NaviSecCLI can communicate with the arrays, the following information is displayed:
Storage Processor: SP B Storage Processor Network Name: cx500-2spb Storage Processor IP Address: 10.100.18.18 Storage Processor Subnet Mask: 255.255.248.0 Storage Processor Gateway Address: 10.100.16.1
If this command succeeds, the Management Server uses the credentials to communicate with the array.
If NaviSecCLI cannot communicate with the array, the following information is displayed:
Broken Pipe Valid IP Address with Feature not installed: naviseccli -h cx500a -user admin -password password -scope 0 networkadmin -get Management Server - Feature software is not installed or the command may have been typed incorrectly usage: metalun migrate connection mirror snapview analyzer