Managing configuration change using Telnet or SSH sessions

This topic contains example procedures that can be performed to manage configuration changes using Telnet/SSH sessions in a quick start stand-alone BMC Network Automation configuration. The examples in this topic are specific to an environment consisting of Cisco IOS routers.

Users can launch Telnet/SSH sessions directly from the system and via a URL from your browser Favorites. All client Telnet/SSH sessions are sent through a proxy server. You can launch the session from the Dashboard, Device List pop-up window, or by navigating to Network > Actions > Telnet/SSH Session in the UI.

Your Telnet/SSH session is tracked as a job with the transcript recording the session command/response interaction and the resulting Job Summary report showing the before and after Configuration Difference report (assuming changes are made).

BMC Network Automation uses the SSH2 or Telnet access mode supported by the device to establish the client session.

BMC Network Automation allows a Telnet/SSH session to run independently of other span actions (for example, Deploy to Active and Snapshot actions can occur at the same time a Telnet/SSH session is in progress on a device).

You can optionally work with familiar SSH clients such as Bitvise, OpenSSH, and SecureCRT. BMC Network Automation acts as a proxy server between these familiar SSH clients and the managed network devices.
When acting as a proxy, BMC Network Automation creates a connection to the network devices using the appropriate access mode (for example, Telnet, SSH2).

The following are the benefits of using an SSH client:

• The CLI login uses the same authentication mechanism used for logging into the browser interface.
• There is no need to sit in front a computer that supports a web browser.
• Working with a CLI terminal may be faster, providing a performance advantage over using the web browser interface.
• CLI keyboard command shortcuts are supported.
• Copy and paste is supported.
• Users can list all devices for which they have permission to view.
• Multiple CLI sessions can be opened to different network devices enabling efficient troubleshooting.
• All interactions between the SSH client and the managed devices are recorded. Keystrokes entered during the session are captured and displayed in the job transcripts.
• Event trails are captured.

For more information, see Opening a Telnet or SSH session.

Back to top

Launching a Telnet or SSH session to make a change

The following example demonstrates how to launch a Telnet or SSH session to make a change.

1. Open the Telnet/SSH Session page.
2. In the Device field, select the appropriate realm, and click .
3. In the pop-up, select your Cisco Router.
4. In the Annotation field, enter Updating Cisco IOS Banner.
5. Click Submit.
6. Modify the device’s banner while in the session.
7. Click End Session to close the session.

Back to top

Viewing changes made in the Telnet or SSH session

The following example demonstrates how to view the changes made in the Telnet or SSH session.

1. After the Telnet/SSH session is completed, the status of the action in the Jobs page (Network > Actions > Jobs) should be Completed. Note you may need to change the filter to include Telnet/SSH Session jobs in the list; the default Recent Jobs view does not show Telnet/SSH Session jobs.

2. Open the Job Details report by clicking  Details in the Actions column for the completed Telnet/SSH session.
   
   

   Note

   The Job Details report displays the workflow summary along with a link to the Job Summary Report and link to the Transcript for viewing the session keystrokes.

    

3. Open the Job Summary Report by clicking on the Job Summary link and note that  actual changes made during the Telnet/SSH session are shown side-by-side.

   
   

   Note

   You can also view these changes in the Dashboard by clicking  Discrepancy in the Running vs Trusted Running column for the device.

Back to top