PDF(684.2 KB) View with Adobe Reader on a variety of devices
ePub(704.4 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(472.6 KB) View on Kindle device or Kindle app on multiple devices
Updated:July 26, 2023
Document ID:220646
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.
This document describes how to configure Secure Firewall Management Center(FMC) with a different port instead of the Default Eth0 Interface.
Prerequisites
Requirements
Cisco recommends that you have knowledge of these topics:
Knowledge of Cisco Secure Firewall Management Center (formerly known as Firepower Management Center)
Knowledge of basic Networking
Components Used
The information in this document is based on these software and hardware versions:
Cisco Secure Firewall Management Center (FMC 1000, 1600, 2500, 2600, 4500, 4600, and virtual) running software version 5.x and above.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Background Information
About the Management Connection on Secure Firewall Management Center
After you configure the device with the FMC information and after you add the device to the FMC, either the device or the FMC can establish the management connection. Depending on the initial setup:
Either the device or the FMC can initiate.
Only the device can initiate.
Only the FMC can initiate.
Initiation always originates with eth0 on the FMC or with the lowest-numbered management interface on the device. Additional management interfaces are tried if the connection is not established. Multiple management interfaces on the FMC let you connect to discrete networks or segregate management and event traffic. However, the initiator does not choose the best interface based on the routing table.
The Internal Interface labeled as Management (Eth0) is a 1 Gigabit Ethernet embedded in the Device Chassis. Some models of FMC Chassis have an expansion slot that can carry a Network Module Expansion Card, which can be Copper or Fiber and up to 10 Gigabit, some Chassis embedded ports can support 10-Gigabit Ethernet SFP+ transceivers.
This figure shows the rear panel of the FMC 1000.
Figure 1. FMC 1000 Rear Panel
1
2 USB keyboard ports
You can connect a keyboard, and along with a monitor on the VGA port, you can access the console.
2
CIMC interface (labeled "M")
This interface is not supported.
3
Serial console port
This port is disabled by default; use the VGA port and keyboard USB port instead.
Log into the management center virtual at the console using admin as the username and the password for the admin account that you defined on the Initial Setup. Note that the password is case-sensitive.
Use the expert command to enter into Linux shell mode.
Edit the ims.conf file using vi editor with the command sudo vi /etc/sf/ims.conf:
Figure 4
4. Use the arrow keys on your keyboard and find the line MANAGEMENT=eth0:
Figure 5
5. Enter into INSERT mode to edit by typing the key "I", the bottom line at the screen can confirm with the message INSERT that we are in edit mode, and replace eth0 with the interface designed, use the previous Tables as reference:
Figure 6
6. Hit the Esc key on the Keyboard to exit INSERT mode and use the colon key ":" to enter in command mode, type "wq!" to save the changes and exit the file:
Figure 7
7. Disable the eth0 interface with the command sudo ip link set eth0 down:
Figure 8
8. Run the Network Configuration Wizard to re-enter the IP address, Network Mask and Gateway address with the commando sudo usr/local/sf/bin/configure-network, this command can create the interface and assign a default route:
Figure 9
9. Exit the Linux shell mode with the exit command.
Verify
To verify if the interface selected was enabled, use this procedure:
Run from Linux Shell mode the command sudo route -n to confirm the default route table for the new Management Interface:
Figure 10
Troubleshoot
If the new interface is not populated on the routing table, validate this:
Confirm that you disabled eth0 interface with sudo ifconfig command.
If the interface is still enabled, run the step 7 again.
Run the configure network script again on step 8 to generate the interface configuration and the default route.