Cisco ASA Series Cli Configuration Manual page 996

Configuring ASA Access for ASDM, Telnet, or SSH
Model License Requirement
All models Base License.
Guidelines and Limitations
This section includes the guidelines and limitations for this feature.
Context Mode Guidelines
Supported in single and multiple context mode.
Firewall Mode Guidelines
Supported in routed and transparent firewall mode.
IPv6 Guidelines
Supports IPv6.
Model Guidelines
For the ASASM, a session from the switch to the ASASM is a Telnet session, but Telnet access
configuration according to this section is not required.
Additional Guidelines
•
•
•
•
•
•
Cisco ASA Series CLI Configuration Guide
1-2
You cannot use Telnet to the lowest security interface unless you use Telnet inside a VPN tunnel.
Management access to an interface other than the one from which you entered the ASA is not
supported. For example, if your management host is located on the outside interface, you can only
initiate a management connection directly to the outside interface. The only exception to this rule is
through a VPN connection. See the
on page 1-13.
The ASA allows:
–
A maximum of 5 concurrent Telnet connections per context, if available, with a maximum of
100 connections divided among all contexts.
–
A maximum of 5 concurrent SSH connections per context, if available, with a maximum of 100
connections divided among all contexts.
–
A maximum of 5 concurrent ASDM instances per context, if available, with a maximum of 32
ASDM instances among all contexts.
The ASA supports the SSH remote shell functionality provided in SSH Versions 1 and 2 and
supports DES and 3DES ciphers.
XML management over SSL and SSH is not supported.
(8.4 and later) The SSH default username is no longer supported. You can no longer connect to the
ASA using SSH with the pix or asa username and the login password. To use SSH, you must
configure AAA authentication using the aaa authentication ssh console LOCAL command; then
define a local user by entering the username command. If you want to use a AAA server for
authentication instead of the local database, we recommend also configuring local authentication as
a backup method.
Chapter 1
"Configuring Management Access Over a VPN Tunnel" section
Configuring Management Access