Please enter search query.
Search <book_title>...
Veritas InfoScale™ 8.0 Virtualization Guide - Linux
Last Published:
2021-12-21
Product(s):
InfoScale & Storage Foundation (8.0)
Platform: Linux
- Section I. Overview of Veritas InfoScale Solutions used in Linux virtualization
- Overview of supported products and technologies
- About Veritas InfoScale Solutions support for Linux virtualization environments
- About Kernel-based Virtual Machine (KVM) technology
- About the RHEV environment
- Overview of supported products and technologies
- Section II. Implementing a basic KVM environment
- Getting started with basic KVM
- Veritas InfoScale Solutions configuration options for the kernel-based virtual machines environment
- Installing and configuring Cluster Server in a kernel-based virtual machine (KVM) environment
- Configuring KVM resources
- Getting started with basic KVM
- Section III. Implementing Linux virtualization use cases
- Application visibility and device discovery
- Server consolidation
- Physical to virtual migration
- Simplified management
- Application availability using Cluster Server
- Virtual machine availability
- Virtual machine availability for live migration
- Virtual to virtual clustering in a Red Hat Enterprise Virtualization environment
- Virtual to virtual clustering in a Microsoft Hyper-V environment
- Virtual to virtual clustering in a Oracle Virtual Machine (OVM) environment
- Disaster recovery for virtual machines in the Red Hat Enterprise Virtualization environment
- Disaster recovery of volumes and file systems using Volume Replicator (VVR) and Veritas File Replicator (VFR)
- Multi-tier business service support
- Managing Docker containers with InfoScale Enterprise
- About the Cluster Server agents for Docker, Docker Daemon, and Docker Container
- Managing storage capacity for Docker containers
- Offline migration of Docker containers
- Disaster recovery of volumes and file systems in Docker environments
- Application visibility and device discovery
- Section IV. Reference
- Appendix A. Troubleshooting
- Appendix B. Sample configurations
- Appendix C. Where to find more information
- Appendix A. Troubleshooting
Consistent naming across KVM Hosts
While enclosure based naming (EBN) provides persistent naming for a single node, it does not guarantee consistent naming across nodes in a cluster. The User Defined Names (UDN) feature of DMP allows DMP devices to be given both persistent and consistent names across multiple hosts. When using User Defined Names, a template file is created on a host, which maps the serial number of the enclosure and device to unique device name. User Defined Names can be manually selected, which can help make mappings easier to manage.
To create consistent naming across hosts
- Create the User Defined Names template file.
# /etc/vx/bin/vxgetdmpnames enclosure=3pardata0 > /tmp/user_defined_names # cat /tmp/user_defined_names enclosure vendor=3PARdat product=VV serial=1628 name=3pardata0 dmpnode serial=2AC00008065C name=3pardata0_1 dmpnode serial=2AC00002065C name=3pardata0_2 dmpnode serial=2AC00003065C name=3pardata0_3 dmpnode serial=2AC00004065C name=3pardata0_4
- If necessary, rename the devices. In this example, the DMP devices are named using the name of the guest they are to be mapped to.
# cat /dmp/user_defined_names enclosure vendor=3PARdat product=VV serial=1628 name=3pardata0 dmpnode serial=2AC00008065C name=guest1_1 dmpnode serial=2AC00002065C name=guest1_2 dmpnode serial=2AC00003065C name=guest2_1 dmpnode serial=2AC00004065C name=guest2_2
- Apply the User Defined Names file to this node, and all other hosts.
# vxddladm assign names file=/tmp/user_defined_names
- Verify the user defined names have been applied.
# vxdmpadm getdmpnode enclosure=3pardata0 NAME STATE ENCLR-TYPE PATHS ENBL DSBL ENCLR-NAME ============================================================================== guest_1_1 ENABLED 3PARDATA 2 2 0 3pardata0 guest_1_2 ENABLED 3PARDATA 2 2 0 3pardata0 guest_2_1 ENABLED 3PARDATA 2 2 0 3pardata0 guest_2_2 ENABLED 3PARDATA 2 2 0 3pardata0