ASA Version 9.x SSH and Telnet on the Inside and Outside Interfaces Configuration Example

Available Languages

Download Options

  • PDF
    View with Adobe Reader on a variety of devices
  • ePub
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)
    View on Kindle device or Kindle app on multiple devices
Updated:August 13, 2014
Document ID:118075

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Contents

Introduction
Prerequisites
Requirements
Components Used
Related Products
Conventions
Configure
Network Diagram
SSH Configurations
SSH Access to the Security Appliance
ASA Configuration
ASDM Version 7.2.1 Configuration
Telnet Configuration
Telnet Example Scenarios
Verify
Debug SSH
View Active SSH Sessions
View Public RSA Keys
Troubleshoot
Remove the RSA Keys from the ASA
SSH Connection Failed

Introduction

This document describes how to configure Secure Shell (SSH) on the inside and outside interfaces of the Cisco Series Security Appliance Versions 9.x and later. When you must configure and monitor the Cisco Adaptive Security Appliance (ASA) remotely with the CLI, the use of either Telnet or SSH is required. Because Telnet communications are sent in clear text, which can include passwords, SSH is highly recommended. The SSH traffic is encrypted in a tunnel and thereby helps protect passwords and other sensitive configuration commands from interception.

The ASA allows SSH connections to the security appliance for management purposes. The security appliance allows a maximum of five concurrent SSH connections for each security context, if available, and a global maximum of 100 connections for all of the contexts combined.

View Full Documentlogin required

Additional entitlement is required to view the full document.

Most of our content is available to the public. This document contains sensitive information and is available only to partners and customers with a valid service contract.

Learn more about Cisco Service Contracts

TAC Authored

Contributed by Cisco Engineers

  • Dinkar Sharma
    Cisco TAC Engineer.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products