Using ASDM To Manage A FirePOWER Module
Using ASDM To Manage A FirePOWER Module
module on ASA
Contents
Introduction
Components used
Prerequisites
Architecture
Background operation when a user connects to ASA via ASDM
Step 1 The user initiates the ASDM connection
Step 2 The ASDM discovers the ASA configuration and the FirePOWER module IP
Step 3 The ASDM initiates communication towards the FirePOWER module
Step 4 The ASDM retrieves the FirePOWER Menu Items
Troubleshooting
Recommended actions
Related Documents
Introduction
A FirePOWER module that is installed on ASA can be managed by either:
Components used
A Windows 7 host
ASA5525-X running ASA 9.6.2-3 code
ASDM software 7.6.2.150
FirePOWER software module 6.1.0-330
Prerequisites
Architecture
The ASA has 3 internal interfaces:
asa_dataplane = It is used to redirect packets from the ASA Data Path to the FirePOWER
software module
asa_mgmt_plane = It is used to allow the FirePOWER management interface to
communicate with the network
cplane = Control Plane interface that is used to transfer keepalives between the ASA and the
FirePOWER module
You can capture traffic in all internal interfaces:
The user specifies the ASA IP used for HTTP management, enters the credentials and initiates a
connection towards the ASA:
In the background an SSL tunnel between the ASDM and the ASA is established:
Enabling debug http 255 on ASA will show all the checks that are done in the background when
the ASDM connects to the ASA:
ASA5525# debug http 255 HTTP: processing ASDM request [/admin/exec/show+module] with cookie-
based authentication HTTP: processing GET URL '/admin/exec/show+module' from host 192.168.75.22
HTTP: processing ASDM request [/admin/exec/show+cluster+interface-mode] with cookie-based
authentication HTTP: processing GET URL '/admin/exec/show+cluster+interface-mode' from host
192.168.75.22 HTTP: processing ASDM request [/admin/exec/show+cluster+info] with cookie-based
authentication HTTP: processing GET URL '/admin/exec/show+cluster+info' from host 192.168.75.22
HTTP: processing ASDM request [/admin/exec/show+module+sfr+details] with cookie-based
authentication HTTP: processing GET URL '/admin/exec/show+module+sfr+details' from host
192.168.75.22
show module = The ASDM discovers the ASA modules
show module sfr details = The ASDM discovers the module details including the FirePOWER
management IP
The above will be seen in the background as a series of SSL connections from the PC towards the
ASA IP:
Since the ASDM knows the FirePOWER management IP it initiates SSL sessions towards the
module:
The above will be seen in the background as SSL connections from the ASDM host towards the
FirePOWER management IP:
The ASDM authenticates the FirePOWER and a Security Warning is shown since FirePOWER
Certificate is self-signed:
Step 4 The ASDM retrieves the FirePOWER Menu Items
After the successful authentication the ASDM retrieves from the FirePOWER the Menu Items:
The retrieved tabs:
Troubleshooting
In case ASDM cannot establish an SSL tunnel with the FP Management IP then it will only load
the following FirePOWER Menu Item:
The ASA FirePOWER Configuration Item will be missing as well:
Recommended actions
Verification 1
Make sure that the ASA management interface is UP and the switchport connected to it is in the
proper VLAN:
Verification 2
Make sure that the FirePOWER module is fully initialized, UP and running:
ASA5525# show module sfr details Getting details from the Service Module, please wait... Card
Type: FirePOWER Services Software Module Model: ASA5525 Hardware version: N/A Serial Number:
FCH1719J54R Firmware version: N/A Software version: 6.1.0-330 MAC Address Range: 6c41.6aa1.2bf2
to 6c41.6aa1.2bf2 App. name: ASA FirePOWER App. Status: Up App. Status Desc: Normal Operation
App. version: 6.1.0-330 Data Plane Status: Up Console session: Ready Status: Up DC addr: No DC
Configured Mgmt IP addr: 192.168.75.123 Mgmt Network mask: 255.255.255.0 Mgmt Gateway:
192.168.75.23 Mgmt web ports: 443 Mgmt TLS enabled: true A5525# session sfr console Opening
console session with module sfr. Connected to module sfr. Escape character sequence is 'CTRL-
^X'. > show version --------------------[ FP5525-3 ]-------------------- Model : ASA5525 (72)
Version 6.1.0 (Build 330) UUID : 71fd1be4-7641-11e6-87e4-d6ca846264e3 Rules update version :
2016-03-28-001-vrt VDB version : 270 ---------------------------------------------------- >
Verification 3
Check basic connectivity between the ASDM host and the FirePOWER module management IP
by using tools like ping and tracert/traceroute:
Verification 4
If the ASDM host and the FirePOWER management IP are in the same L3 network check the ARP
table on the ASDM host:
Verification 5
Enable capture on the ASDM device while you are connecting via ASDM to see if there is proper
TCP communication between the host and the FirePOWER module. At minimum you should see:
TCP 3-way handshake between the ASDM host and the ASA
SSL tunnel established between the ASDM host and the ASA
TCP 3-way handshake between the ASDM host and the FirePOWER module management IP
SSL tunnel established between the ASDM host and the FirePOWER module management IP
Verification 6
To check the traffic to and from the FirePOWER module you can enable capture on the
asa_mgmt_plane interface. In the capture below it can be seen:
Verification 7
Verify that the ASDM user has privilege level 15. One way to confirm this is by running debug http
255 while connecting via ASDM:
ASA5525# debug http 255 debug http enabled at level 255. HTTP: processing ASDM request
[/admin/asdm_banner] with cookie-based authentication (aware_webvpn_conf.re2c:444) HTTP: check
admin session. Cookie index [2][c8a06c50] HTTP: Admin session cookie
[A27614B@20480@78CF@58989AACB80CE5159544A1B3EE62661F99D475DC] HTTP: Admin session idle-timeout
reset HTTP: admin session verified = [1] HTTP: username = [user1], privilege = [14]
Verification 8
If between the ASDM host and the FirePOWER module there is NAT for the Firepower
Management IP then you need to specify the NATed IP:
Verification 9
Make sure that the FirePOWER module is not already managed by Firepower Management
Center (FMC) because in that case the FirePOWER tabs in ASDM will be missing:
ASA5525# session sfr console Opening console session with module sfr. Connected to module sfr.
Escape character sequence is 'CTRL-^X'. > show managers Managed locally. >
Another way:
ASA5525# show module sfr details Getting details from the Service Module, please wait... Card
Type: FirePOWER Services Software Module Model: ASA5525 Hardware version: N/A Serial Number:
FCH1719J54R Firmware version: N/A Software version: 6.1.0-330 MAC Address Range: 6c41.6aa1.2bf2
to 6c41.6aa1.2bf2 App. name: ASA FirePOWER App. Status: Up App. Status Desc: Normal Operation
App. version: 6.1.0-330 Data Plane Status: Up Console session: Ready Status: Up DC addr: No DC
Configured Mgmt IP addr: 192.168.75.123 Mgmt Network mask: 255.255.255.0 Mgmt Gateway:
192.168.75.23 Mgmt web ports: 443 Mgmt TLS enabled: true
Verification 10
Verify in the ASA Compatibility guide that the ASA/ASDM images are compatible:
http://www.cisco.com/c/en/us/td/docs/security/asa/compatibility/asamatrx.html
Verification 11
Verify in the Firepower Compatibility guide that the FirePOWER device is compatible with the
ASDM version:
http://www.cisco.com/c/en/us/td/docs/security/firepower/compatibility/firepower-compatibility.html
Related Documents
Cisco ASA FirePOWER Module Quick Start Guide
ASA with FirePOWER Services Local Management Configuration Guide, Version 6.1.0
ASA FirePOWER Module User Guide for the ASA5506-X, ASA5506H-X, ASA5506W-X,
ASA5508-X, and ASA5516-X, Version 5.4.1