Firepower Disk Usage Troubleshooting

-

1. Disk manager

   df-h 

root@FTD67:/# df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs          3.9G  398M  3.5G  11% /
devtmpfs        3.9G   12M  3.9G   1% /dev
tmpfs           3.9G  1.1M  3.9G   1% /run
tmpfs           3.9G  220K  3.9G   1% /var/volatile
/dev/sda1       510M  253M  258M  50% /mnt/boot
/dev/sda2       8.0G   80M  8.0G   1% /mnt/disk0
/dev/sda6       3.8G  574M  3.1G  16% /ngfw
/dev/sda8        28G  6.0G   21G  23% /ngfw/Volume
tmpfs           3.9G     0  3.9G   0% /dev/cgroups

admin@fmc724:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda5       3.7G  1.5G  2.0G  44% /
none             16G     0   16G   0% /dev
/dev/sda1        87M   16M   64M  20% /boot
/dev/sda7       237G   21G  205G  10% /Volume
none             16G  128K   16G   1% /dev/shm
tmpfs            16G     0   16G   0% /sys/fs/cgroup
tmpfs            16G     0   16G   0% /sys/fs/cgroup/pm
admin@fmc724:~$

admin@ftd724:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs          3.9G  9.8M  3.9G   1% /
devtmpfs        3.9G  5.2M  3.9G   1% /dev
tmpfs           3.9G  964K  3.9G   1% /run
/dev/sda1       510M  341M  170M  67% /mnt/boot
/dev/sda2       8.0G   95M  7.9G   2% /mnt/disk0
/dev/sda6       3.8G  1.8G  1.9G  50% /ftd
/dev/sda8        28G  4.6G   22G  18% /ngfw/Volume
tmpfs           3.9G     0  3.9G   0% /dev/cgroups


If disk usage monitor is enabled Health Policy, by default, Warning Threshold is 85%, Critical Threshold is 90%.

2. Du  - 
 “du” (Disk Usage): Find Disk Usage of Files and Directories

    2.1 Total size of a directory
    du -sh /ngfw/var
    -s: size
    -h: Human readable




    2.2 Size of directory and its subdirectories 






  2.3 size of all files and directories










  2.4 Size of 1st level subdirectories:






    2.5  Top 5 Biggest files and subdirectories

du -ah | sort -n -r | head -n 5








https://www.tecmint.com/check-linux-disk-usage-of-files-and-directories/


3. Delete folder or files
  /ngfw/Volume# rm -rf 6.4.0

-f, --force Ignore nonexistant files, and never prompt before removing.

    -r, -R, --recursive Remove directories and their contents recursively.


======================

Locations can be cleaned up:

1. Backup Folder  (FMC), files can also be deleted from GUI.

/var/sf/backup


2.Firepower Upgrade/Update folder, files can also be deleted from GUI.

/var/sf/updates


3. VDB folder, files can also be deleted from GUI.

/var/sf/vdb


4. Snort rules SRU/LSP folder

/var/sf/sru
/var/sf/lsp


Comments

Post a Comment

Popular posts from this blog

ASA IKEv1 VPN troubleshooting Steps and Tips

-
  1. Phase I proposal mismatch  Run show crypto isakmp sa  Initiator: MM_WAIT_MSG2 Responder: No info  Most likely this is phase1 proposal mismatch, verify IKEv1 policy, other symptoms:   Initiator log: Information Exchange processing failed All configured IKE versions failed to establish the tunnel Initiator debug: Received an un-encrypted NO_PROPOSAL_CHOSEN notify message, dropping Responder log: Error processing payload: Payload ID Responder debug:  All SA proposals found unacceptable 2. IKE version mismatch:  Run  show crypto isakmp sa  no info at both initiator and responder Initiator log: Removing peer from correlator table failed, no match! Reason: User Requested  All configured IKE versions failed to establish the tunnel Initiator debug: Oakley begin quick mode PHASE 1 COMPLETED IKE Initiator sending 1st QM pkt Removing peer from correlator table failed, no match! Session is being torn down. Reason: User Requested Responder log: Tunnel Rejected: Conflicting protocols specified
Read more

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 [admin] Connecting to fxos. Connected
Read more

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 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 Correlator  2   Reconfigure and flush Correlator  3    Restart Comm. channel  4   Update routes  5   Reset all routes  6   Validate Network  0   Exit *****
Read more