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.
It appears the ASA IOS train for versions 9.8(4)20 and higher have a bug that prevents copying any ASA image to flash. The result is always a "Signature not valid for file" error. Even when specifying /noverify on the copy operation. I first noticed ...
I have an issue with an IKEv2 route-based tunnel from an ASA Version 9.8(4)20 to Azure. On the Azure end, we have two address spaces defined for our local network. On the ASA end, we send all traffic destined for our one network in Azure through the ...
So yes, I finally figured it out. I ended up having to shutdown the sfr module prior to copying the image. After the transfer you can re-enable the sfr module. This has worked every time so far. I reported my findings and I tried getting Cisco TAC to...
Still no real progress other than that TAC confirmed other customers are experiencing the same issue. The report was they are having difficulty obtaining an ASA 5506-X to test with. Doesn't appear to be a good sign going forward. I know the platform ...
Worked with TAC yesterday. Was able to demonstrate the issue with multiple images in the 9.8(4)x train. The engineer indicated they would test this in their labs and get back to me.
Yeah I have a TAC case open. Going on day 3 and it's been pretty mum so far. I did quite a few searches but couldn't find anything relevant. Its got to be a bug. I'm just surprised it's survived this long. The MD5 checksums are valid. I knew the imag...
The problem is sorted out. It was caused by a Frankenstein hybrid route/policy based tunnel on the Azure end. We experienced the same symptoms when the ASA was configured as policy based VPN. Oh well. I wouldn't have learned as much about route-base...
