Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Configuring an FTP server
- Using Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VII. Configuring cloud storage
- Section VIII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- Section X. Reference
Configuring Veritas Access in IPv4 and IPv6 mixed mode
Veritas Access supports both IPv4 and IPv6 addresses. You can configure the Veritas Access cluster in an IPv4 environment, or an IPV6 environment, or in a mixed mode environment where you have both IPv4 and IPv6 addresses. You can use the Veritas Access services from the client by using IPv4 as well as IPv6 addresses but there are some limitations for specific services. When you configure Veritas Access in mixed mode, you are required to add both IPv4 and IPv6 physical IPs to the NIC(s) of all the cluster nodes.
Note:
If you want to use the Veritas Access service over an IPv4 address, then you must configure the IPv4 address on both Veritas Access and the client. Similarly, if you want to use the Veritas Access service over an IPv6 address, then you must configure the IPv6 address on both Veritas Access and the client. Veritas Access does not convert IPV4 addresses to IPV6 addresses and vice versa for communication.
You can use the below mentioned steps to convert an IPv4 Veritas Access cluster to mixed mode.
To convert an IPv4 Veritas Access cluster to mixed mode
- Install a Veritas Access cluster with IPv4 addresses.
- Connect to the cluster using the master user credentials using the physical or master IP of the cluster.
network> ip addr show IP Netmask/Prefix Device Node Type Status -- -------------- ------ ---- ---- ------ 192.168.30.10 255.255.252.0 pubeth0 vascan_01 Physical 192.168.30.11 255.255.252.0 pubeth0 vascan_02 Physical 192.168.30.12 255.255.252.0 pubeth0 vascan_02 Virtual ONLINE (Con IP) 192.168.30.13 255.255.252.0 pubeth0 vascan_02 Virtual ONLINE 192.168.30.14 255.255.252.0 pubeth0 vascan_01 Virtual ONLINE
- Add the physical IPv6 IP.
network> ip addr add 2001:0:0:0::11 64 physical pubeth0 vascan_01 ACCESS ip addr WARNING V-493-10-1027 Default gateway for IPv6 is not configured. ACCESS ip addr SUCCESS V-493-10-1381 ip addr add successful. network> ip addr add 2001:0:0:0::12 64 physical pubeth0 vascan_02 ACCESS ip addr WARNING V-493-10-1027 Default gateway for IPv6 is not configured. ACCESS ip addr SUCCESS V-493-10-1381 ip addr add successful.
- Add the virtual IPV6 IP.
network> ip addr add 2001:0:0:0::13 64 virtual pubeth0 ACCESS ip addr WARNING V-493-10-1027 Default gateway for IPv6 is not configured. ACCESS ip addr SUCCESS V-493-10-1381 ip addr add successful. network> ip addr add 2001:0:0:0::14 64 virtual pubeth0 ACCESS ip addr WARNING V-493-10-1027 Default gateway for IPv6 is not configured. ACCESS ip addr SUCCESS V-493-10-1381 ip addr add successful.
- Add the IPv6 default gateway.
network> ip route add all :: 0 via 2001:0:0:0::1
- Check the cluster configuration in mixed mode.
IP Netmask/Prefix Device Node Type Status -- -------------- ------ ---- ---- ------ 192.168.30.10 255.255.252.0 pubeth0 vascan_01 Physical 192.168.30.11 255.255.252.0 pubeth0 vascan_02 Physical 2001:0:0:0:0:0:0:11 64 pubeth0 vascan_01 Physical 2001:0:0:0:0:0:0:12 64 pubeth0 vascan_02 Physical 192.168.30.12 255.255.252.0 pubeth0 vascan_02 Virtual ONLINE (Con IP) 192.168.30.13 255.255.252.0 pubeth0 vascan_02 Virtual ONLINE 192.168.30.14 255.255.252.0 pubeth0 vascan_01 Virtual ONLINE 2001:0:0:0:0:0:0:13 64 pubeth0 vascan_01 Virtual ONLINE 2001:0:0:0:0:0:0:14 64 pubeth0 vascan_02 Virtual ONLINE
You can use the below mentioned steps to convert an IPv6 Veritas Access cluster to mixed mode.
To convert an IPv6 Veritas Access cluster to mixed mode
- Install a Veritas Access cluster with IPv6 addresses.
- Connect to the cluster using the master user credentials using the physical or master IP of the cluster.
network> ip addr show IP Netmask/Prefix Device Node Type Status -- -------------- ------ ---- ---- ------ 2001:0:0:0:0:0:0:112 64 pubeth0 vascan_01 Physical 2001:0:0:0:0:0:0:113 64 pubeth1 vascan_02 Physical 2001:0:0:0:0:0:0:114 64 pubeth0 vascan_01 Virtual ONLINE (Con IP) 2001:0:0:0:0:0:0:116 64 pubeth1 vascan_01 Virtual ONLINE
- Add the physical IPv4 IP.
network> ip addr add 192.168.30.10 255.255.252.0 physical pubeth0 vascan_01 ACCESS ip addr SUCCESS V-493-10-1381 ip addr add successful. network> ip addr add 192.168.30.11 255.255.252.0 physical pubeth1 vascan_02 ACCESS ip addr SUCCESS V-493-10-1381 ip addr add successful.
- Add the virtual IPV4 IP.
network> ip addr add 192.168.30.12 255.255.252.0 virtual pubeth0 ACCESS ip addr SUCCESS V-493-10-1381 ip addr add successful.1381 ip addr add successful. network> ip addr add 192.168.30.13 255.255.252.0 virtual pubeth1 ACCESS ip addr SUCCESS V-493-10-1381 ip addr add successful.
- Add the IPv4 default gateway.
network> ip route add all 0.0.0.0 0.0.0.0 via 192.168.30.1
- Check the cluster configuration in mixed mode.
network> ip addr show IP Netmask/Prefix Device Node Type Status -- -------------- ------ ---- ---- ------ 192.168.30.10 255.255.252.0 pubeth0 vascan_01 Physical 192.168.30.11 255.255.252.0 pubeth1 vascan_02 Physical 2001:0:0:0:0:0:0:112 64 pubeth0 vascan_01 Physical 2001:0:0:0:0:0:0:113 64 pubeth1 vascan_02 Physical 2001:0:0:0:0:0:0:114 64 pubeth0 vascan_01 Virtual ONLINE (Con IP) 192.168.30.12 255.255.252.0 pubeth0 vascan_01 Virtual ONLINE 192.168.30.13 255.255.252.0 pubeth1 vascan_02 Virtual ONLINE 2001:0:0:0:0:0:0:116 64 pubeth1 vascan_01 Virtual ONLINE