Deployments to all FTD/FPRs are failing. Transcript details: Starting Export for Snort System (/usr/bin/rsync -a -L -K -O –no-owner –no-group –no-perms –safe-links /ngfw/var/cisco/deploy/sandbox/modulepack-pkg/so_rules/ee254ff06d1***4e01515a47 /ngfw/var/cisco/deploy/sandbox/exported-files/var/sf/detection_engines/994fb330-0d6***7520ddc2f872/so_rules) Failed Root cause: Another issue with SRU. Reference to TAC. Downloaded and applied latest rule to FMC. FTD/FPRs deployments succeeded. …
Tag: FTD
Recurring Snort Rule Update ran overnight, all FTD devices showed as Pending Deployment next day. On manual deploy to ALL failed at 75%. Single FTD deployment also failed at 75%. pigtail deploy on FMC USMS: 12-24 15:47:43 “property” : “deployment:device_failure_configuration_cli”, USMS: 12-24 15:47:43 “argumentList” : [ { USMS: 12-24 15:47:43 …
If you see errors like below Write-error on swap-device /bin/cat: /tmp/heimdall.pid: No such file or directory /bin/chown: cannot access ‘/opt/cisco/csp/applications/configs/max_restart’: Input/output error /opt/ssp-mgmt-scripts/ssp_system_mgmt_startup.sh /opt/cisco/platform/logs/ssp-pm.log: Read-only file system /sbin/fxos_log_shutdown: /opt/cisco/platform/logs/ssp-shutdown.log: Read-only file system login fails after system restore with a factory-reset or reset fails completely then your FTD SSD file system …
I saw this issue performing an upgrade readiness check from FMC on FTD. FMC was in HA deployment (Active/Standby pair). Other FTDs completed readiness checks successfully so it was not related to file corruption. This bug was also not related as FTD registration to both FMCs had been completed. Upgrade …
After deploying a single FTD at the remote site my next task was to configure two FTDs in a redundant High-Availability (HA) setup with Active/Passive fail-over. Again, I had to make sure the following requirements are met. configure FTD at the staging site with limited onsite availability ssh remote-access …