Connection Info
The following table describes the UI features on the Connection Info tab:
Field | Description |
|---|---|
Session Name | (Required) Enter the session name. |
Console Type | Select the type of console from the dropdown list to change the defaults on the Screen Processing tab. Administrators can use the new z/VM Host session field to specify the console that is connected to the z/VM host and if the consoles are for a z/VM guest. |
Startup Script | Enter the RDL code that is executed when the Automation server starts the session. This is a function call. |
CCS Server | (Required) Enter the CCS server name. |
Host | (Required) Enter the name of the host on which the CCS server is running. This must be the localhost unless the CCS server is not on the same BMC AMI Ops Console Management computer as the Automation server. |
Non-Encrypted Port | (Required) Enter the port number that has encryption enabled. Select the Use SSL Port check box to enter the SSL port data. |
CCS Console | (Required) Enter the CCS Console name. |
User Name | (Required) Enter a valid user name used to authenticate the Automation servers' access to this console. We recommend that you do not use an operator user ID. |
Password | (Required) Enter the password for the selected user name. |
Console Character Set | Select the EBCDIC to UNICODE character translation table that is used for the session. Character translations are usually performed by the CCS server, but some languages require you to change the character translations from the default. |
Backup Session | Select the backup session from the drop-down list. If the CCS server connection is disrupted, the automation server automatically switches to the backup session for console messages. For more information, see To select or disable an Automation Server backup session. |
Cancel | Click Cancel to discard the new or modified information. |
Create/Save & Exit | Click to create and save the new or modified session information. |
To select or disable an Automation Server backup session
An automation server can switch to a backup session if the connection to the primary console fails.
For example, you may have two OSA-ICC adapters for your CPC, osaicc1.z16.example.com and osaicc2.z16.example.com. These OSA-ICC adapters have different IP addresses, DNS names, and network paths.
To configure BMC AMI Ops Console Management to use this redundancy, follow these steps:
- Set up one CCS server to connect to the primary OSA-ICC adapter.
For example, if the upstream host is osaicc1.z16.example.com, it has a console session that connects to the proper LU on that OSA-ICC. - Set up a second CCS server to connect to the alternate OSA-ICC.
For example, if the upstream host is osaicc2.z16.example.com, it has a console session that connects to the proper LU on that OSA-ICC. - In the Automation server, perform these actions:
- Define both console connections.
- Disable the alternate console connection.
- From the Backup Session list select your backup console connection for the primary console connection.
When the automation server starts the console session, it connects to the primary CCS console first. If that succeeds, it processes screen updates as expected. If the connection to the primary CCS console fails, either on the initial connection or later, the automation server attempts to connect to the backup CCS console. When the backup console connection is successful, the automation server processes screen updates and generates messages from the backup console.