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
About IPv4-IPv6-based network support on the Velocity physical appliance
The Veritas Velocity Appliance is supported on a dual stack IPv4-IPv6 network and can communicate with IPv6 clients. You can assign an IPv6 address to an appliance, configure DNS, and configure routing to include IPv6 based systems.
Consider the following points for IPv6 addresses:
The Velocity Appliance does not support a pure IPv6 network. An IPv4 address must be configured for the appliance, otherwise the initial configuration (which requires the command hostname set) is not successful. For this command to work, at least one IPv4 address is required.
For example, suppose that you want to set the hostname of the appliance to v46. To do that, first make sure that the appliance has at least one IPv4 address and then run the following command:
Main_Menu > Network > Hostname set v46
Only global addresses can be used, not addresses with link-local or node-local scope. Global-scope and unique-local addresses are both treated as global addresses by the host.
Global-scope IP addresses refer to the addresses that are globally routable. Unique-local addresses are treated as global.
You cannot use both an IPv4 and an IPv6 address in the same command. For example, you cannot use Configure 9ffe::9 255.255.255.0 1.1.1.1. You should use Configure 9ffe::46 64 9ffe::49.
Embedding the IPv4 address within an IPv6 address is not supported. For example, you cannot use an address like 9ffe::10.23.1.5.
You can enter only one IPv4 address for a network interface card (NIC) or bond. However, you can enter multiple IPv6 addresses for a NIC or bond.
Network File System (NFS) or Common Internet File System (CIFS) protocols are supported over an IPv4 network on the appliance. NFS or CIFS are not supported on IPv6 networks.
The Main_Menu > Network > Hosts command supports multiple IPv6 addresses to be assigned to the same host name having one network interface card (NIC). However, only one IPv4 address can be assigned to a specific host name having one NIC using this command.
You can add an IPv6 address of a network interface without specifying a gateway address.