Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi everyone,
I’d like to share a troubleshooting experience during an upgrade from FTD 7.2.5.1 to 7.6.2 on a Firepower 4115 HA pair managed by FMC, and how we ultimately resolved a persistent sftunnel communication failure related to certificates.
En...
Hi All,
After certain FMC and FTD upgrades, it is possible to encounter a situation where the FTD fails to register back to the FMC even though all connectivity checks appear normal. FMC and FTD can reach each other, port 443 is open, and the sftunne...
I am trying to upgrade viptela image from cli because it's not managed by vmanage however i am getting the following error:
vedge# request software install viptela-20.4.1.2-mips64.tar.gz rebootERROR: install: Kernel image not found
Note that the MD5s...
i am trying to upgrade my vedge viptela image using the following command and i am getting the following error:
vedge# request software install reboot viptela-20.4.1.2-mips64.tar.gzls: cannot access 'viptela-20.4.1.2-mips64.tar.gz': No such file or d...
Thanks for the follow-up, Marvin.The first occurrence of this behavior was observed last year during an upgrade from FTD 7.0.x to 7.2.x. After extensive troubleshooting and eliminating all the usual causes—reachability, sftunnel status, certificates,...
i faced the same issue twice, when upgrading the FTD from 7.0.x to 7.2.x and currently i faced it when i upgraded the FMC to 7.6.2 and the FTD to 7.4.2 (FTD model: 2130)
i did telnet and immediately checked NAT table:
Pro Inside global Inside local Outside local Outside globaltcp 195.112.197.10:7000 192.168.4.117:7000 91.151.227.41:59002 91.151.227.41:59002
yes i did delete it and re add also i cleared the nat trans...
