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.
Fabulous - so by following the normal process of naming sub-interfaces (from memory the documentation has guided you to use points for subifs since the dawn of time) - I now have to delve into the CLI to construct packet captures.I see the bug is mar...
As usual, I've taken the FMC to the new version - the attached devices are now all pending upgrade to that new version.So, follow the normal path : Product Upgrades -> etc -> get to the point where you run the readiness check... Readiness check runs,...
Has anyone else attempted an upgrade from 9-202502 to 9-202504 yet? I've tried it 2 times so far - both fail at the final step (it seems the application doesn't complete its startup - at least according to the syslog). Thankfully rolling back to the ...
Hello hive mind of the Cisco Community. I'm planning some scheduled reloads of a fleet of Catalyst 9348 (although this behaviour appears to also be true in a 3850) - to perform the upgrade from IOS-XE 16.6.6 to 16.6.7... Typically copy the software ...
Click where it says "Manage Virtual Routers" - it's a "hidden" clickable link... you're then taken to the Virtual Routers page.Certainly how it works in 7.6.x (you may also wish to think about updating from 7.4.2 to something nearer current version i...
@Mark Elsen That isn't fixed then is it? That is fix identified.Sure, I can use CLI as a workaround - not everyone has the skill/knowledge (or is confident to use it)
You always have to apply the latest "full" release (in this case 7.6.2) then apply the patch (7.6.2.1). FMC running 7.6.2 will be unable to patch FTD to 7.6.2.1.Immaterial if you upgrade the FMC to 7.6.2.1 then start on the firewalls, or FMC to 7.6.2...
