Net Worker World

Search This Blog

BGP State

on January 09, 2015

Get link
Facebook
X
Pinterest
Email
Other Apps

router

Get link
Facebook
X
Pinterest
Email
Other Apps

Comments

Firepower FMC and FTD troubleshooting

1. Display real time log on FMC or FTD: pigtail for example: pigtail | grep 192.168.2.20 pigtail | grep sftunnel pigtail --help pigtail deploy pigtail gui 2. Restart communication channel manage_procs.pl run it from the sensor only, run it from FMC will reset all sensors' channel. This scripts are nice to be used when the FMC and FTD have communication problems like heartbeats are not received, policy deployment is failing or events are not received > expert ************************************************************** NOTICE - Shell access will be deprecated in future releases and will be replaced with a separate expert mode CLI. ************************************************************** admin@FTD:~$ sudo su Password: root@FTD:/home/admin# manage_procs.pl **************** Configuration Utility ************** 1 Reconfigure Cor...

Firepower 2100/1100 FTD/ASA initial setup, reimage, upgrade.

Chassis FXOS and FTD share same management IP (default 192.168.45.45) Chassis FXOS (192.168.45.45) and ASA ()use different management IP although on same physical interface. SSH to FXOS/FTD are on FTD CLI prompt, go to FXOS using the connect fxos command Console to Chassis is on FXOS CLI prompt, go to FTD using the connect ftd command The Firepower 1100 does not support the FXOS Firepower Chassis Manager; only a limited CLI is supported for troubleshooting purposes. The Firepower 2100 runs an underlying operating system called the Firepower eXtensible Operating System (FXOS). If you run ASA on Firepower 2100, ASA can be in the following modes: Appliance mode (the default after ASA 9.13)—Appliance mode lets you configure all settings in the ASA. Only advanced troubleshooting commands are available from the FXOS CLI. See the FXOS troubleshooting guide for more information. Firepower Chassis Manager is not supported . ciscoasa# connect fxos...

FMC and FTD with External Authentication

Configure FMC with LDAP for External Authentication 1. System > Users > External Authentication, Add External Authentication Object Set Defaults button will automatically fill up Attribute Mapping section. Once configures host info, Fetch DNs can retrieve Base DN NetworkAdmins is AD group, only members in this AD group can login FMC/FTD. In this lab, maps it to FMC Administrator group, don't select any Default User Role, once you select one, you can't unselect it. CLI Access Filter: when check "Same as Base Filter", cli access doesn't check user's AD group info, so all AD user will get access FMC/FTD cli. To restrict cli access, we can add a new AD attribute, in this lab, it is called "firepowercli". Refer this article to create a Unicode String attribute, restart AD Domain Services, then in AD set the value to "shell" for user needs FMC/FTD cli access. https://www.rebeladmin.com/2017/11/step-step-guide-create-custom-acti...

Powered by Blogger

BGP State

Comments

Post a Comment