Veritas Access Appliance Administrator's Guide
- 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
Managing the banner from the command-line interface
You can create a customized text banner that appears when you sign in to Access Appliance UI or the system console. You can use the login banner to communicate various kinds of messages to users. Typical uses for the login banner include legal notices, warning messages, and company policy information.
If the Security Technical Implementation Guide (STIG) mode is enabled for the cluster, the login banner cannot be modified.
To display the banner:
- Use SSH to log in to one of the nodes with admin credentials.
The Veritas Appliance Shell is displayed.
- Enter support elevate and enter the maintenance account password.
- To go to the Access command-line interface, enter LOGNAME=admin /opt/VRTSnas/clish/bin/clish -u admin
- To display the banner, enter the following command
access-clus> system banner get No login banner is currently set for the appliance.
Note:
No banner is set by default.
To set the banner:
- Use SSH to log in to one of the nodes with admin credentials.
The Veritas Appliance Shell is displayed.
- Enter support elevate and enter the maintenance account password.
- To go to the Access command-line interface, enter LOGNAME=admin /opt/VRTSnas/clish/bin/clish -u admin
- To set the banner, run the following command:
# access-clus> system banner set Enter Header (Type <enter> and <Ctrl + d> to complete the body. Max 250 characters) This is header Enter Body (Type <enter> and <Ctrl + d> to complete the body. Max 4000 characters) This is body text line 1. This is body text line 2.
The banner is made up of two parts, the header and the body. The header is the heading for the banner and the body is the banner content. The header can be a maximum of 250 characters and body can be a maximum of 4000 characters.
After the banner is set, you can view the banner using the system banner get command:
access-clus> system banner get **************** This is header **************** This is body text line 1. This is body text line 2.
Note:
If STIG is enabled on the system, you cannot change the default STIG banner.
accessclus> system banner set ACCESS Banner ERROR V-493-10-0 The banner cannot be set as STIG is enabled on the cluster.