Documente Academic
Documente Profesional
Documente Cultură
Version 4.4
boxmgmt Guide
302-002-829
REV 01
Copyright 2016 EMC Corporation. All rights reserved. Published in the USA.
Published April, 2016
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a
particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.
EMC, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other
countries. All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).
EMC Corporation
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.EMC.com
CONTENTS
Tables
Chapter 1
Chapter 2
Installation
Chapter 3
Setup
11
Modify settings............................................................................................. 12
Enter cluster details......................................................................... 12
Number of virtual ports per port....................................................... 12
WWN node/port pair addresses....................................................... 12
Enable/disable initiator-only mode.................................................. 12
Number of VMware ITLs needed....................................................... 12
MTU configuration............................................................................12
Configure repository volume .........................................................................13
Get remote settings....................................................................................... 13
Retrieve previous settings............................................................................. 13
Apply settings............................................................................................... 13
View settings.................................................................................................13
Reset settings changes..................................................................................13
Advanced options......................................................................................... 13
Clear reservations............................................................................ 13
Unregister reservations.................................................................... 13
Reboot Regulation............................................................................14
Security options............................................................................... 14
Appliance Config Params................................................................. 15
Run Scripts...................................................................................... 15
Remove host from SSH known host file............................................ 15
Storage device customizations.........................................................15
Register with ESRS gateway..............................................................16
Set time via NTP............................................................................... 16
Enable/Disable logging of incoming FC headers............................... 16
Clear reservations............................................................................ 16
Unregister reservations.................................................................... 16
BMC support.................................................................................... 16
Console configuration .................................................................................. 17
Chapter 4
Diagnostics
19
IP diagnostics................................................................................................20
Cluster connectivity tests................................................................. 20
View IP details................................................................................. 20
View routing table............................................................................ 20
Test throughput............................................................................... 20
Ports diagnostics............................................................................. 20
System connectivity......................................................................... 20
SAN diagnostic..............................................................................................21
Run SAN diagnostics........................................................................ 21
RecoverPoint 4.4 boxmgmt Guide
CONTENTS
Chapter 5
Cluster operations
25
Chapter 6
Shutdown/Reboot operations
27
Reboot RPA................................................................................................... 28
Shutdown RPA...............................................................................................28
TABLES
TABLES
CHAPTER 1
Installation Manager (boxmgmt)
The Installation Manager, also known as boxmgmt, allows you to modify and manage
existing RPA configurations and test and diagnose the settings and connectivity of RPAs
before and after they are attached to RPA clusters.
Accessing Installation Manger
To access the Installation Manager, use an ssh client. Create an ssh session to the IP
address of the RPA, user = boxmgmt.
Using Installation Manager
To select a menu option, enter the number of the desired selection. To accept the current
value or the default if there is no current value, press Enter.
CHAPTER 2
Installation
Installation
Installation
10
CHAPTER 3
Setup
The Setup menu allows you to execute deployment activities independent of the various
Deployment Manager wizards.
l
l
l
l
l
l
l
l
l
Modify settings..................................................................................................... 12
Configure repository volume .................................................................................13
Get remote settings............................................................................................... 13
Retrieve previous settings..................................................................................... 13
Apply settings....................................................................................................... 13
View settings.........................................................................................................13
Reset settings changes..........................................................................................13
Advanced options................................................................................................. 13
Console configuration .......................................................................................... 17
Setup
11
Setup
Modify settings
To change RPA setting, first detach the RPA from the RPA cluster. You must apply (or
reapply) the modified configuration to each of the RPAs in the installation. If you have
changed the cluster name or time zones, you must format (or reformat) the repository
volume in both clusters. Then re-attach the RPA to the RPA cluster.
MTU configuration
The MTU configuration option is used to view or change the maximum transmission
unit (MTU) packet size (in bytes) of an RPAs LAN, WAN, and iSCSI interfaces. To prevent
12
Setup
communication problems, the MTU value must be the same on all RPAs in the
environment. The default MTU value is set by the RPA operating system.
Apply settings
To set a machine's configuration, you must apply the settings that you type in or retrieved
from an installed RPA.
View settings
Displays cluster settings.
Advanced options
Clear reservations
This command is useful if the reservation is preventing the RPAs from communicating
with that volume.
Once you select the command, the Installation Manager presents a list of all volumes
available to the RPA. Select the volume from which you want to clear the reservation. The
Installation Manager returns a notification stating whether the action has succeeded or
failed.
Unregister reservations
The Unregister reservations option is for use by EMC Customer Service.
13
Setup
When the storage array supports the SCSI-3, the RPA automatically registers with the
storage array so that it can perform I/O operations. The RPA also unregisters
automatically.
In exceptional cases, it may be necessary to unregister manually. To unregister manually,
select Unregister reservations. All LUNs that are accessible to the RPA are listed. Select
the one you wish to unregister.
Reboot Regulation
If Reboot Regulation is enabled, frequent RPA reboots or failures will cause the RPA
automatically to detach from its cluster.
l
Use the Set parameters command to configure the number of reboots and the
time interval.
The default values are 6 reboots within 120 minutes. Use Restore default
parameters command to reset the parameters to these default values.
After you have identified and corrected the problem, reactivate the RPA by re-attaching it
to its RPA cluster.
Security options
Change web server mode options
https and http
The RPA listens both on the HTTP port (port 80) and HTTPS port (port 443).
https only
The RPA listens only on the HTTPS port (port 443). The RPA will present a certificate
when a connection is made. To enforce a consistent security policy requiring HTTPS,
HTTPS only must be set on every RPA in the entire system.
Change web server certificate
To enforce a consistent security policy, Change web server certificate must be used to
change to a non-default certificate on every RPA in the entire system. Follow directions on
screen. If your certificate is not in Base64 format, you must use FTP.
Enable/disable remote connection
To enable or disable the use of secure shell (SSH) to connect to this RPA. Only affects the
admin and boxmgmt users. To manage remote access of other users to the RPA, change
their privileges.
Log-on banner options
Display log-on banner text
The text appears before the user logs on.
Enter log-on banner text
Enter the text that will appear before the user logs on.
Disable log-on banner text
To remove the text displayed before the user logs on.
Change appliance communication security level
Relevant only on RPAs running RecoverPoint 4.1.1 or later. When the RPA is attached to a
cluster, this command changes the MPI security level of the entire system. The following
MPI security levels are available:
14
Setup
Accessible
Communication between RPAs is not authenticated or encrypted. RPAs can
communicate with each other only by adhering to the RecoverPoint proprietary
protocol.
Authenticated
RPA clusters use certificates to authenticate each other before communicating. This
option minimally impacts RPA performance.
Authenticated and encrypted
RPA clusters use certificates to authenticate each other before communicating. All
communication between RPA clusters is also encrypted. This option moderately
impacts RPA performance. This security level is FIPS compliant.
When the WAN connection between clusters is down, changing the RPA communication
security level of the cluster will only succeed when cluster isolation mode is enabled.
When cluster isolation mode is enabled, changing the RPA communication security level
will succeed only at the RPA cluster on which the command is run. The RPA
communication security level at the other RPA clusters must be manually changed to
match the local RPA cluster security level.
View certificate
Relevant only on RPAs running RecoverPoint 4.1.1 or later.
Change cluster certificate
Relevant only on RPAs running RecoverPoint 4.1.1 or later. To change the authentication
certificate of the remote RPA clusters. Paste the new remote cluster certificate here.
Enable/disable cluster isolation
Relevant only on RPAs running RecoverPoint 4.1.1 or later.
Enable cluster isolation mode when you need to regenerate a new certificate or change
the RPA communication security level and the WAN connection between RPA clusters is
down. After enabling cluster isolation, run the CLI command
regenerate_encryption_keys. In boxmgmt, select View the certificate. Then log in
to boxmgmt at the other cluster and select Change cluster certificate to paste the
certificate from the other cluster. Then disable cluster isolation mode.
Run Scripts
To run a signed script provided by EMC Customer Service. Scripts run only for the
designated customer in the designated time period. Paste the entire script exactly as
received from EMC Customer Service.
15
Setup
Customers call EMC Customer Service and request to open a Service Request.
Clear reservations
Do not use this command unless instructed to do so by authorized RecoverPoint
Customer Service. This command is useful if the reservation is preventing the RPAs from
communicating with that volume.
Unregister reservations
The Unregister reservations command is for use by EMC Customer Service.
When the storage array supports the SCSI-3, the RPA automatically unregisters
reservations. In exceptional cases, it may be necessary to unregister manually.
BMC support
BMC support is available for Gen5 and Gen6 RPAs. By default, BMC support is disabled.
The Baseboard Management Controller (BMC) may be accessed through the following
BMC interface ports:
Table 1 BMC interface ports
Gen6
Setup
Configure BMC
Note
If the LAN or WAN port is shared by the RPA and the BMC server, network issues may
affect BMC access.
Console configuration
To configure the boxmgmt console.
Console configuration
17
Setup
18
CHAPTER 4
Diagnostics
The Diagnostic menu allows you to test the functionality and connectivity of your RPA
configuration before and after attaching it to the RPA cluster.
l
l
l
l
IP diagnostics........................................................................................................20
SAN diagnostic......................................................................................................21
Synchronization diagnostics................................................................................. 22
Collect system information.................................................................................... 22
Diagnostics
19
Diagnostics
IP diagnostics
Cluster connectivity tests
The following connectivity tests are performed:
l
NTP server
Other host
View IP details
As shown
Test throughput
For a single cluster, the Test throughput option does not appear.
The system uses iperf to test throughput to another RPA. Enable the iperf server
before testing throughput. Disable the iperf server after testing throughput.
Ports diagnostics
Procedure
1. Verify that none of the ports used by the RPAs are blocked (for instance, by a firewall).
You must test each RPA individually by designating each RPA in turn to be the server.
2. Before selecting the server option, detach the RPA that you intend to designate as the
server.
3. After you have designated one RPA as a server, go to another RPA, designated it as a
client, and use it to test throughput to the server RPA.
System connectivity
Only relevant for physical RPAs
System connectivity test
l
Full mesh network check test communication between any RPA to any other RPA in
the system.
Diagnostics
Message
Meaning
Machine is down
<appliance> is down
All OK
SAN diagnostic
Run SAN diagnostics
As shown
SAN diagnostic
21
Diagnostics
Synchronization diagnostics
Output similar to the following appears.
remote
refid
st t when poll reach delay offset jitter
======================================================================
========
*10.10.0.1
10.254.140.22 4 u 2
64
377
0.141 18.094 4.571
Diagnostics
If the entered interval is from more than 30 days ago, some logs may not be available
for collection.
When collecting system information, the following error conditions apply
l
If the collection from the remote cluster failed because of a WAN failure, run the
process locally in the remote cluster.
In the event of simultaneous info collection from the same RPA, only the collector that
established the first connection can succeed.
23
Diagnostics
24
CHAPTER 5
Cluster operations
l
l
l
l
l
l
Cluster operations
25
Cluster operations
26
CHAPTER 6
Shutdown/Reboot operations
l
l
Reboot RPA........................................................................................................... 28
Shutdown RPA.......................................................................................................28
Shutdown/Reboot operations
27
Shutdown/Reboot operations
Reboot RPA
As shown
Shutdown RPA
As shown
28