10-23-2021 04:54 AM - edited 10-23-2021 04:55 AM
Hi
in the office where I work, we have an old Firepower 2100 firewall with 16 interfaces,
8 ethernet and 4 fiber. So far we have only used 2, one inside and one outside.
Now I need to add a server on another ethernet port to be able to reach it via ipsec,
but any interface I program and which obviously I put in "no shut" remains in shutdown.
The only interfaces that work are 1, 2 and management. I tried everything and searched online
but found no explanation. It seems absurd to me to have 12 ports and only be able to use 2.
Can anyone help me please?
Solved! Go to Solution.
10-23-2021 07:16 AM
Hi My name is Minhyeok from Korea.
It seems to me that it is in the no shut state on the ASA, but in the shutdown state on the firepower chassis manager.
You have to connect in fxos and try to port no shutdown.
You can access both gui and cli.
Find fxos manual
Thank you
10-23-2021 08:53 AM
try to understand the issue, is the interface physically connected to switch or any other device :
here is a quick start guide to managing devices with chassis manager.
10-23-2021 07:16 AM
Hi My name is Minhyeok from Korea.
It seems to me that it is in the no shut state on the ASA, but in the shutdown state on the firepower chassis manager.
You have to connect in fxos and try to port no shutdown.
You can access both gui and cli.
Find fxos manual
Thank you
10-24-2021 10:43 PM
Thank you minhyeokcho48844
in fxos manual i've founded my question's answer.
I followed this steps and all ok
Step 1
Enter eth-uplink and then fabric a mode.
scope eth-uplink
scope fabric a
Example:
firepower-2110# scope eth-uplink
firepower-2110 /eth-uplink # scope fabric a
firepower-2110 /eth-uplink/fabric #
Step 2
Enable the interface.
enter interface interface_id
enable
Example:
firepower-2110 /eth-uplink/fabric # enter interface Ethernet1/8
firepower-2110 /eth-uplink/fabric/interface # enable
firepower-2110 /eth-uplink/fabric/interface* #
thank you for Help
10-23-2021 08:53 AM
try to understand the issue, is the interface physically connected to switch or any other device :
here is a quick start guide to managing devices with chassis manager.
10-24-2021 10:44 PM
Thank you for answer balaji.bandi
in fxos manual i've founded this step and all ok now
Step 1
Enter eth-uplink and then fabric a mode.
scope eth-uplink
scope fabric a
Example:
firepower-2110# scope eth-uplink
firepower-2110 /eth-uplink # scope fabric a
firepower-2110 /eth-uplink/fabric #
Step 2
Enable the interface.
enter interface interface_id
enable
Example:
firepower-2110 /eth-uplink/fabric # enter interface Ethernet1/8
firepower-2110 /eth-uplink/fabric/interface # enable
firepower-2110 /eth-uplink/fabric/interface* #
03-28-2024 01:05 PM
Just wanted to add, that we had to do an extra step, so here is the full fix action:
in FXOS
example:
firepower-2110# scope eth-uplink
firepower-2110 /eth-uplink# scope fabric a
firepower-2110 /eth-uplink/fabric# enter interface Ethernet1/8
firepower-2110 /eth-uplink/fabric/interface# enable
firepower-2110 /eth-uplink/fabric/interface* # exit
firepower-2110 /eth-uplink/fabric# exit
firepower-2110 /eth-uplink# exit
firepower-2110# commit-buffer
Data didn't start passing until after we did the commit-buffer command, hope this helps someone
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide