Veritas Velocity™ User's Guide
- Getting to know Velocity
- Setting up Velocity
- How to set up the Velocity Storage Server
- How to set up the Velocity Client
- Setting up the Velocity on-premises management server
- Upgrading Velocity
- Velocity Storage Server
- Users and roles
- Oracle database ingestion using Velocity
- How to use copy preparation to mask or sanitize sensitive data
- Oracle database ingestion using NetBackup CoPilot
- Microsoft SQL Server database ingestion using Velocity
- Database sources and copies
- About scheduling ingestions for a database source
- Retention periods for database sources and copies
- Sandboxes
- Database recovery
- Alerts and logs
- Managing the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- About WAN optimization on the Velocity physical appliance
- About the Veritas Remote Management Console on the Velocity physical appliance
- About Velocity physical appliance storage
- About users on the Velocity physical appliance
- About Velocity physical appliance checkpoints
- About factory reset on the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- Monitoring the Velocity physical appliance
- Velocity physical appliance security
- About Velocity physical appliance user account privileges
- About the Velocity physical appliance intrusion detection system
- About Velocity physical appliance operating system security
- Recommended IPMI settings on the Velocity physical appliance
- Best practices
- Troubleshooting
- Glossary
- Context-sensitive topics
- Section I. Velocity shell menu commands
- Introduction
- Appendix A. Main > Manage > Storage
- Appendix B. Main > Manage > Cloud
- Appendix C. Main > Manage > Software
- Appendix D. Main > Monitor
- Appendix E. Main > Network
- Appendix F. Main > Settings
- Appendix G. Main > Support
Replacing the default IPMI SSL certificate on the physical appliance
Veritas recommends that you replace the default Veritas Remote Management Console (IPMI) SSL certificate with either a certificate signed by a trusted internal or external certificate authority (in PEM format), or by a self-signed certificate.
Use the following procedure to create a minimal self-signed certificate on a Linux computer and import it into the IPMI web interface:
To create and implement a minimal self-signed certificate
- On a Linux computer, type the following command to generate the private key:
openssl genrsa -out ipmi.key 2048
In this case, the private key is named
ipmi.key
. - Type the following command to generate a certificate signing request (
ipmi.csr
) usingipmi.key
:openssl req -new -key ipmi.key -out ipmi.csr
Fill in each field with the appropriate values. To leave a field blank, enter a period (.).
Note:
To avoid extra warnings in your browser, set the common name to the fully qualified domain name of the IPMI interface.
- Type the following command to sign
ipmi.csr
withipmi.key
and create a certificate calledipmi.crt
that is valid for 1 year:openssl x509 -req -in ipmi.csr -out ipmi.crt -signkey ipmi.key -days 365
- Type the following command to concatenate
ipmi.crt
andipmi.key
to create a certificate in PEM format calledipmi.pem
:cat ipmi.crt ipmi.key > ipmi.pem
- Log on to the Veritas Remote Management Console.
Note:
If you need to access the Veritas Remote Management Console from another computer, copy the
ipmi.pem
file to that computer. - On the Configuration tab, select SSL from the left pane.
Next to New SSL Certificate, click Browse... and select the
ipmi.pem
file.Click Upload.
Note:
A warning may appear that says an SSL certificate already exists. Press OK to continue.
- Click Browse... again to import the privacy key. (Note that it now says New Privacy Key next to the button instead of New SSL Certificate.)
Select the
ipmi.pem
file and click Upload.When the confirmation dialog appears, click OK to restart the web service.
- (Optional) Close and reopen the Veritas Remote Management Console to verify that the new certificate is being presented.