cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
753
Views
0
Helpful
4
Replies

FirePower Hardware Module Cabling CONNECTIONS

Atasawar1
Level 1
Level 1

My question is that how should we do the cabling on FirePower hardware module for data traffic coming in and going out from FirePower module.
In a software module, we create security zones as per the ASA interface as an inside interface on ASA will be an inside security zone and an outside interface of ASA will be outside security zone on FirePower module. But what about hardware module as it has its own interfaces?

How should we connect cables for in FirePower hardware module for incoming and outgoing data traffic? (Not management) 

Thanking you all in advance for your kind assistance. 

1 Accepted Solution

Accepted Solutions

On the 5585-X with FirePOWER SSP, the interfaces are a bit misleading as they are not specifc to the FirePOWER module (except the console port). Instead, they are expansion data interfaces for the overall ASA.

All ASAs with FirePOWER modules communicate to the module via the ASA backplane (called the fabric switch in a 5585-X). So you do not "assign" any physical (or logical) interfaces to the module. Instead you direct traffic to it as an action in your service policy.

I found a decent picture of the architecture in a Cisco Live presentation. See slide 34 in the following:

BRKSEC-2028 - Deploying Next Generation Firewall with ASA and Firepower Services (2015 San Diego)

https://www.ciscolive.com/online/connect/sessionDetail.ww?SESSION_ID=83691&tclass=popup

View solution in original post

4 Replies 4

Marvin Rhoads
Hall of Fame
Hall of Fame

What hardware and software platform are you asking about?

There are several in the FirePOWER family and the answer varies according to which you are asking about.

Hi Marvin,

It is ASA5585-SSP-40 hardware module. 

Software: 6.0.0

On the 5585-X with FirePOWER SSP, the interfaces are a bit misleading as they are not specifc to the FirePOWER module (except the console port). Instead, they are expansion data interfaces for the overall ASA.

All ASAs with FirePOWER modules communicate to the module via the ASA backplane (called the fabric switch in a 5585-X). So you do not "assign" any physical (or logical) interfaces to the module. Instead you direct traffic to it as an action in your service policy.

I found a decent picture of the architecture in a Cisco Live presentation. See slide 34 in the following:

BRKSEC-2028 - Deploying Next Generation Firewall with ASA and Firepower Services (2015 San Diego)

https://www.ciscolive.com/online/connect/sessionDetail.ww?SESSION_ID=83691&tclass=popup

Thank you, Marvin Rhoads for your kind response and clearing my doubts.

Review Cisco Networking for a $25 gift card