Veritas Access Appliance Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Configuring the network
- Configuring authentication services
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Configuring ISCSI
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- 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 Access Appliance as an Object Store server
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Section VI. Monitoring and troubleshooting
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Configuring event notifications and audit logs
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- About managing application I/O workloads using maximum IOPS settings
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About the NFS shares
- Creating and maintaining CIFS shares
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- Using Access Appliance with OpenStack
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- Section X. Reference
Support for multiple data subnets
Access Appliance now supports multiple data subnets. This is applicable to all the protocols that the Access Appliance supports. If you have different subnets, you can access the services of the Access Appliance cluster via those subnets. The protocol specific entities and features decide how the subnets are utilized by the individual protocol. Multiple subnets can be configured with or without multiple VLANs.
Note:
Data network isolation depends on the customer network configuration. The application configuration in Access Appliance does not restrict the customer from using the same network for multiple protocols.
If you have multiple subnets and you want to create multiple VLANs for each subnet, then Veritas recommends the following:
For each subnet, add the required number of IPs as physical IPs to create the VLAN. The required number of IPs is equal to the number of nodes that are present. Do not add extra IPs.
Create the VLAN using the network vlan add command. The IPs that you added are automatically picked for VLAN creation.
Add a route for the newly created subnet, if required.
If you want to create another VLAN, repeat the above steps.
Note:
If the IPs are not added in the correct sequence, the network vlan add command may pick IPs which belong to different subnets.
For example:
Network> ip addr show IP Netmask/Prefix Device Node Type Status -- -------------- ------ ---- ---- ------ 192.168.10.5 255.255.255.0 eth5 vaupg_01 Physical 192.168.10.13 255.255.255.0 eth5 vaupg_02 Physical 192.168.10.2 255.255.255.0 eth4 vaupg_01 Physical 192.168.10.10 255.255.255.0 eth4 vaupg_02 Physical 10.209.192.206 255.255.252.0 eth1 vaupg_01 Physical 10.209.192.208 255.255.252.0 eth1 vaupg_02 Physical 10.209.194.38 255.255.252.0 eth1 vaupg_01 Virtual ONLINE (Con IP) 192.168.10.22 255.255.255.0 eth5 vaupg_01 Virtual ONLINE 192.168.10.25 255.255.255.0 eth5 vaupg_02 Virtual ONLINE 192.168.10.28 255.255.255.0 eth4 vaupg_02 Virtual ONLINE 192.168.10.30 255.255.255.0 eth4 vaupg_01 Virtual ONLINE
Network> ip addr modify 192.168.10.2 192.168.30.2 255.255.255.0 ACCESS ip addr WARNING V-493-10-0 Given IP (192.168.10.2) is not a virtual ip. ACCESS ip addr SUCCESS V-493-10-1381 ip addr modify successful. Network> ip addr modify 192.168.10.10 192.168.30.10 255.255.255.0 ACCESS ip addr WARNING V-493-10-0 Given IP (192.168.10.10) is not a virtual ip. ACCESS ip addr SUCCESS V-493-10-1381 ip addr modify successful. Network> ip addr modify 192.168.10.28 192.168.30.15 255.255.255.0 ACCESS ip addr SUCCESS V-493-10-1381 ip addr modify successful. Network> ip addr modify 192.168.10.30 192.168.30.20 255.255.255.0 ACCESS ip addr SUCCESS V-493-10-1381 ip addr modify successful.
ip addr show IP Netmask/Prefix Device Node Type Status -- -------------- ------ ---- ---- ------ 192.168.10.5 255.255.255.0 eth5 vaupg_01 Physical 192.168.10.13 255.255.255.0 eth5 vaupg_02 Physical 192.168.30.2 255.255.255.0 eth4 vaupg_01 Physical 192.168.30.10 255.255.255.0 eth4 vaupg_02 Physical 10.209.192.206 255.255.252.0 eth1 vaupg_01 Physical 10.209.192.208 255.255.252.0 eth1 vaupg_02 Physical 10.209.194.38 255.255.252.0 eth1 vaupg_01 Virtual ONLINE (Con IP) 192.168.10.22 255.255.255.0 eth5 vaupg_01 Virtual ONLINE 192.168.10.25 255.255.255.0 eth5 vaupg_02 Virtual ONLINE 192.168.30.15 255.255.255.0 eth4 vaupg_02 Virtual ONLINE 192.168.30.20 255.255.255.0 eth4 vaupg_01 Virtual ONLINE
Network> ip route show vaupg_01 ---------------- IPv4 routing table: main =========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface =========================================================================== 0.0.0.0 10.209.192.1 0.0.0.0 UG 0 0 0 eth1 10.209.192.0 0.0.0.0 255.255.252.0 U 0 0 0 eth1 180.20.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5 192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4 192.168.229.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 IPv4 routing table: 3 =========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface =========================================================================== 0.0.0.0 10.209.192.1 0.0.0.0 UG 0 0 0 eth1 10.209.192.0 0.0.0.0 255.255.252.0 U 0 0 0 eth1 IPv4 routing table: 2 ========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface ========================================================================== 192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4 IPv4 routing table: 1 ========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface ========================================================================== 0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 eth5 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5 vaupg_02 ---------------- IPv4 routing table: main =========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface =========================================================================== 0.0.0.0 10.209.192.1 0.0.0.0 UG 0 0 0 eth1 10.209.192.0 0.0.0.0 255.255.252.0 U 0 0 0 eth1 180.20.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5 192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4 192.168.229.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 IPv4 routing table: 3 =========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface =========================================================================== 0.0.0.0 10.209.192.1 0.0.0.0 UG 0 0 0 eth1 10.209.192.0 0.0.0.0 255.255.252.0 U 0 0 0 eth1 IPv4 routing table: 2 ======================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface ======================================================================== 192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4 IPv4 routing table: 1 ========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface ========================================================================== 0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 eth5 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5 Network> ip route add all 0.0.0.0 0.0.0.0 via 192.168.30.1 dev any scope=local ACCESS ip route SUCCESS V-493-10-1462 ip route add success Network> ip route show vaupg_01 ---------------- IPv4 routing table: main =========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface =========================================================================== 0.0.0.0 10.209.192.1 0.0.0.0 UG 0 0 0 eth1 10.209.192.0 0.0.0.0 255.255.252.0 U 0 0 0 eth1 180.20.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5 192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4 192.168.229.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 IPv4 routing table: 3 ========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface ========================================================================== 0.0.0.0 10.209.192.1 0.0.0.0 UG 0 0 0 eth1 10.209.192.0 0.0.0.0 255.255.252.0 U 0 0 0 eth1 IPv4 routing table: 2 ========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface ========================================================================== 0.0.0.0 192.168.30.1 0.0.0.0 UG 0 0 0 eth4 192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4 IPv4 routing table: 1 ========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface ========================================================================== 0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 eth5 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5 vaupg_02 ---------------- IPv4 routing table: main =========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface =========================================================================== 0.0.0.0 10.209.192.1 0.0.0.0 UG 0 0 0 eth1 10.209.192.0 0.0.0.0 255.255.252.0 U 0 0 0 eth1 180.20.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5 192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4 192.168.229.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 IPv4 routing table: 3 ========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface ========================================================================== 0.0.0.0 10.209.192.1 0.0.0.0 UG 0 0 0 eth1 10.209.192.0 0.0.0.0 255.255.252.0 U 0 0 0 eth1 IPv4 routing table: 2 ========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface ========================================================================== 0.0.0.0 192.168.30.1 0.0.0.0 UG 0 0 0 eth4 192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4 IPv4 routing table: 1 ========================================================================== Destination Gateway Genmask Flags MSS Window irtt Iface ============ ============ ============= ===== === ====== ==== ===== 0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 eth5 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5