Also seeing this on 8540 HA-SSO with 8.3.133.0, however, in addition to 'Reason 5' I am also seeing 'Reason 19' as pasted below.
UsmDb:HA_send_usmDbSpamSetRadSlotBand, ErrType:Apply Config failed on Standby, Reason:19, TStamp:2017-Nov-06 12:26:19
U...
Anyone else experiencing this issue? There seems to be two tickets open. We have open a ticket on our end too. if anyone knows a work around in google chrome, update 67 please share.
This is a nice annoying bug! It says it is fixed but I don't see where a new release has been pushed on 7/2 either on CCO or through the FMC updates window. Any idea what build number this is fixed in?
Will this be fixed in a future rule update or a Firepower patch? I am experiencing this issue with software 6.2.3.2-42 and rule update 2018-07-16-001-vrt.
I believe I just found the problem and solution.
When my customer FMC updated automatically Sunday morning automatically to VDB version 300, this problem started on their 6.2.3 version FMC ACP, and the rules started showing an error since the Apps al...
Hi,
I upgraded my RV345P with firmware .18 and I still have the problem with PPTP CHAP authentication
When is planned a fix for this issue ?
That's a pity to buy a CISCO router and not be able to use the VPN server
Thank you
Regards,
Romain
We saw the same error quite often in our network as well on some Android phones, firefox or IE, however the internal web auth works. I am also interested in workarounds with minimum business impact. Maybe using external web service is another option?...
Workaround #1 isn't working for me. I have confirmed localcli alias swap took place after the reboot, but as far as ESXi gui, the vnics in question still point to the same MAC addresses. Have I made a mistake?
[root@evm63:~] localcli --plugin-di...
Hello there, We are testing an upgrade to 7.1.4 from 7.1.1, but we are meting the bug CSCvh75595.Has anyone been impacted by this issue?What did you decide?We have 1000+ Port-channel with this behaviour change, and apply the workaround on both peers ...
Does anyone know if rebooting the VPC pair of 93180's will clear out this bug? The first workaround of defaulting the ports did not work. We are only able to change port descriptions. We upgraded the code during the build and the bug did not trigger ...
