Configuration and Administration > Consoles

Consoles
Note: For console forms associated with the Blade Module, see Blade Management Module.
The “Consoles” option allows you to perform the following console management procedures:
Add a new console to connect to the AlterPath Manager and for user access.
Consoles List > “Add” button > Select Console Type > Console detail.
Configure blade(s) as part of the Blade Management Module.
Select or change the authentication method for console access.
Console Detail form > “Authentication” drop down list
NOTE: The AlterPath Manager authenticates users from the console or terminal server.
Assign the current console to any number of users.
Console Detail form > “Users ACL” tab > “Select user to console access” form.
Select the users to be notified of any alarms from the current console.
Console Detail form > “Notify” tab > “Select user to console notification” form.
Consoles List form > (select console name) > “Edit” button > Console detail form.
Assign or remove console(s) from the console group.
If you choose not to use the Console Wizard (Devices: Device List > Device Detail), then you can add consoles attached to the added device using the Consoles List and Console Detail forms.
Note: After adding a console, you must upload the configuration to the device before the console can become active. To prevent multiple uploads, it is advisable to add many consoles and then do one upload for the device to enable all the consoles that were added.
Note: See Difference between Auto Upload and Manual Upload.
Data buffering, data logging, and event notification are valid definitions only for consoles with permanent connections (i.e., data status is enabled).
Limitation of Remote Authentications in ACS Console Access
To upload configurations and firmware, you must configure the ACS device to use “root” as the admin user. However, access to an ACS console as root through the AlterPath Manager is currently not possible if the ACS serial port is configured to use any remote only or remote-down/local authentication.
Note: In this case, remote means any of remote (nis), Tacacs Plus, Radius, ldap, etc.
There are two scenarios that you can use to work around this limitation:
1.
Configure ACS consoles for remote/local or local/remote access (local/radius, radius/local, local/TacacsPlus, TacacsPlus/local are the options available in this case).This allows firmware upgrades, and configuration upgrades. It also allows console access by root and other users with access.
2.
If you want to configure remote only authentication or remote-down/local authentication (where remote can be any of the authentication protocols):
Configure the ACS device and consoles, using “root” as the admin user. Then upload the configuration (and firmware, if necessary) as root. Root is able to upload configuration and firmware to the ACS, but cannot access the ACS via the APM.
Next, configure the ACS device as the remote user. The remote user can access the ACS via the APM.
To View the Console List
To view the Console List form, perform the following steps:
1.
The system displays the Consoles List form:
Consoles List Form
From the Consoles List form, you can add, edit, or delete a console by selecting the appropriate button or link.
Note: For console forms associated with the Blade Management Module, see Blade Management Module.

Configuration and Administration > Consoles