Customizing Your ACLI Settings
This section describes several ways you can customize the way you log into the ACLI and the way the ACLI displays information. Where applicable, these descriptions also contain instructions for configuration.
Disabling the Second Login Prompt
With this feature enabled, the OCSBC logs you in as a Superuser (i.e., in administrative mode) regardless of your configured privilege level for an SSH session. However, if you log via SSH, you still need to enter the password for local or RADIUS authentication.
Persistent ACLI more Parameter
To make using the ACLI easier, the Oracle Communications Session Border Controller provides a paging feature controlled through the ACLI cli more command (which you can set to enabled or disabled). Disabled by default, this feature allows you to control how the Oracle Communications Session Border Controller displays information on your screen during a console or SSH session. This command sets the paging feature on a per session basis.
Customers who want to set the paging feature so that settings persist across sessions with the Oracle Communications Session Border Controller can set a configuration parameter that controls the paging feature. Enabling this parameter lets you set your preferences once rather than having to reset them each time you initiate a new session with the Oracle Communications Session Border Controller.
Customized Login Banner
A text file can be put on the Oracle Communications Session Border Controller to be used as a banner to be printed before each login. The file must be called /code/banners/banner.txt. The contents of this file will be printed before each User Access Verification login sequence. The limits are that no more than 79 characters per line and no more than 20 lines from the banner.txt file will be printed.
The banner.txt file used for the ACLI customized login banner has to be saved in the /code/banners directory. If that directory does not already exist on your system, you do not have to create the directory prior to placing the banner file because the Oracle Communications Session Border Controller will create it upon boot if it does not exist.