Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- About OVERKILL
OVERKILL
Getting noticed
Member since Jul 17, 2020
Online
Community Record
46
Posts
13
Kudos
1
Solution
Badges
Monday
Yes, the 14.xx releases aren't impacted because the vendor_ID flag isn't set in the firmware. That was added with the 15.xx series and that seems to be what is causing the issue on the Microsoft side.
... View more
a week ago
AnyConnect IS available on the Meraki platform, currently without a fee (because you need to be running 16.xx) but there will be a charge once the 16-series because stable.
... View more
11-02-2021
10:07 AM
2 Kudos
Interesting one today: We have a few Z3's at various teleworker residences. One of them has an MR20 on site as well, to provide wireless in a back section that the Z3 doesn't cover. Today, get a call that one of their devices won't connect. Everything else has WiFi. Interesting. Hop on the portal, see the devices connected, didn't pay much attention to what they were in fact connected to. Restart the Z3 and the AP, everything reconnects except this one device. Then it dawns on me that they are all connecting to the MR20. Signal strength is not great, as many of these devices are quite close to the Z3. Clearly, the wireless on the Z3 had stopped working when I had applied the 15.44 update (it had been working fine before) and this killed the wireless. A restart didn't bring it back. So, updated the unit to the 16.14 RC and boom, the wireless came back. This is the 2nd Z3 I've had bizarre wireless issues with, both of which in the same location (Cisco replaced the first one). The AP was a later addition and wasn't there when the first one conked out. Anybody else experience this?
... View more
Labels:
- Labels:
-
Firewall
10-14-2021
08:15 PM
Pretty minor upgrade from 16.12 from the looks of things, thanks for the share.
... View more
10-13-2021
06:48 AM
2 Kudos
Yes, the issue was fixed in 16.11. Of note, 16.12 has some significant improvements, including VPN throughput that makes it a worthwhile upgrade.
... View more
07-29-2021
06:24 AM
You lucked out, the certificate issue is a known bug with 16.9/16.10 per the release notes. Disabling it/re-enabling it did not help with my units.
... View more
07-29-2021
05:39 AM
1 Kudo
I had to roll the two I upgraded back to 16.7 because 16.9 broke the certificate.
... View more
07-28-2021
09:39 PM
I had this issue on an MX84, or one that sounds the same where the clients could not authenticate and it would have to be restarted if I wanted to immediately resolve it, otherwise, it seemed to start working again on its own if I let it sit. It was only one of my MX84's that had this issue, but it happens to be the one with the most VPN clients. Touch-wood, the issue went away when I upgraded to 16.7 on that one. What release are you on?
... View more
07-26-2021
02:38 PM
You are quite welcome. May be worth reaching out to support to see what's going on, perhaps the certificate issue isn't the only thing messed up with AnyConnect in 16.9 and 16.10.
... View more
07-26-2021
02:37 PM
1 Kudo
Nope, it's still broken, please see the update in my thread.
... View more
07-26-2021
08:20 AM
Yes, that is quite bizarre. This unit was also never enrolled in the closed beta either... Only thing I can think is that this has been on 16.x for quite a while, have you only just started running 16.x?
... View more
07-26-2021
07:12 AM
Yeah, that's my situation, all my MX's that run AnyConnect are on 16.6 or 16.7 now from the roll-back, 16.8 didn't fix anything significant from what I can see over those two releases so I'll probably just leave them there until we get a release that's an improvement.
... View more
07-26-2021
07:10 AM
Once you've installed a 16.x release and the unit has restarted, you should see AnyConnect as a heading under the Client VPN section:
... View more
07-25-2021
10:26 PM
If you install 16.x it will work, the problem is that right now, 16.10 still has the broken certificate error, so you'd have to contact support to get 16.8 (which works properly). I have an MX64 at home that AnyConnect can be enabled on (but I don't use it).
... View more
07-25-2021
10:22 PM
Update: With 16.10 out now, I checked the Release Notes to see what was still broken, it appears this is, along with the VPN performance hit that appeared in 16.4, so I guess I"m skipping this one.
... View more
07-25-2021
10:19 PM
1 Kudo
It is now, but I'm not sure it was when 16.9 was released.
... View more
07-18-2021
08:54 PM
1 Kudo
So, it seems the "solution" to this is to roll-back the firmware, then rename the device, wait until that takes (you can check by hitting the hostname with a browser until the new one works and it shows a valid SSL certificate that isn't self-signed) then changing it back to the previous hostname, which will then get another valid certificate. At this point, 16.9 breaks AnyConnect.
... View more
07-15-2021
06:38 PM
I performed what was indicated by @KarstenI on the MX I rolled back to 16.7 and it worked in terms of creating a valid certificate again. I forwarded this thread to the guy I was speaking with on the ticket, but I haven't heard anything back yet, but at least the error is gone.
... View more
07-15-2021
09:20 AM
OK thanks. I'll try that after hours on them if we don't get this resolved today.
... View more
07-15-2021
09:13 AM
Have you tried this with 16.9? I ask because, as per the separate thread I made on this, I can't even get AnyConnect to come up or resolve on another MX I have that I upgraded. I feel this may be a bigger issue on the certificate issuing and hostname integration side of things. I've opened a ticket about it.
... View more
07-15-2021
06:24 AM
Adding to this, I enabled AnyConnect on a unit that normally doesn't have it running (my personal MX) that I also upgraded to 16.9 and the service doesn't seem to be coming up (it's been about 20 minutes). Checking the event log, I see no mention of AnyConnect starting, rather, I'm seeing these suppressed log message notifications:
... View more
07-15-2021
06:05 AM
1 Kudo
This was mentioned in the official release thread for 16.9 but I think it warrants its own thread. I upgraded two MX84's running 16.7 to 16.9 last night, both are now throwing certificate errors to the clients. This is what we were getting before the upgrade: MX running 16.7 software And this is what both units are throwing this AM: MX running 16.9 software I rolled-back the firmware upgrade on one of them about 10 minutes ago and it is still throwing the self-signed certificate error unfortunately, which means that once you perform the upgrade, you cannot un-break it.
... View more
07-15-2021
05:50 AM
Just note that rolling back to 16.7 on one of the devices didn't fix the issue, it has a self-signed cert again.
... View more
07-15-2021
05:26 AM
Yep, I upgraded two sites last night and now I'm getting this as well. @Bsalami may be able to get this resolved quickly I'm hoping. My sites were running 16.6 and 16.7 respectively. It appears it shifted from an an external CA-issued cert to a self-signed one. This is what we get now: Unit running 16.9 This is from a unit running 16.7: Unit running 16.7
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 785 | 07-18-2021 08:54 PM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 2 | 160 | |
| 2 | 362 | |
| 1 | 583 | |
| 1 | 1385 | |
| 1 | 1441 |
