Please enter search query.
Search <book_title>...
Veritas Access Appliance Administrator's Guide
Last Published:
2023-10-29
Product(s):
Appliances (8.0)
Platform: Access Appliance OS,Veritas 3340,Veritas 3350
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Configuring the network
- Configuring authentication services
- Configuring user authentication using digital certificates or smart cards
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- 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
- 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
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- 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
- Configuring episodic replication
- Section X. Reference
Accessing the root shell in lockdown mode
If your appliance is in lockdown mode and you need assistance from Veritas Support, you need to generate a One-Time Password (OTP) to allow your representative to access the root shell. The OTP has a two-hour expiration period, after which you need to generate the OTP again; so make sure that you have opened a support case with Veritas Support and your support representative is ready before you generate the OTP.
To access the root shell when the appliance is in lockdown mode:
- From any one of the nodes in the cluster, log in to Veritas Appliance Shell menu.
- Run the support generate-otp command to generate the OTP. A 10-digit number, which is the OTP, is displayed as shown in the following example:
[access 8.0] appnode-01 > support generate-otp One-time password: 3279459335 Operation completed successfully
- Mention the OTP in the support case. If you forget the OTP, you can use the support show-otp command to view it again. Your support representative uses this OTP to generate a security key, which you later need to specify when prompted.
- When your representative asks you to, enter the support unlock command. You are prompted for the security key, which your representative must generate using the OTP. Enter the security key and press Enter.
- To get root access for the current node, run the support elevate command. The other node remains locked. Enter the passphrase, which your representative specified while generating the security key. Press Enter.
- Enter the maintenance password to access the root shell.
- When your support representative is done troubleshooting the issue, enter the support lock command to close root access to the node. Root access to the node is closed automatically after 12 hours and all root sessions are terminated.