Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
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 TEAM-ind
TEAM-ind
Getting noticed
Member since Nov 21, 2017
2 weeks ago
Community Record
39
Posts
7
Kudos
0
Solutions
Badges
3 weeks ago
Hello, and thank you for your reply. Yes, that does work, but I am wondering why I need to do that, as I do not need to for other local networks.
... View more
3 weeks ago
Hello. I hope everyone is doing well. I am seeing a behavior when adding a subnet to our LAN. Each of our locations has an MX appliance. 192.168.102.0 /24 is newly added network at one location, and it is reachable from all locations and from VPN clients. However, when I split tunnel a VPN client, it is not reachable. I cannot figure out why. Other local subnets are reachable when using split tunnel, but not this newly added one. Can anybody provide a reason as to why that might be the case?
... View more
Labels:
- Labels:
-
Client VPN
Dec 8 2023
11:33 AM
I'm sure I'm not the only one to have noticed, but the MX client page has been performing poorly for some time now. Today, it's not working really at all for me. I opened a case and was told by support "This appears to be an issue that our dev team is currently working to address." Just thought I would share with the community. Happy Friday.
... View more
Nov 15 2023
2:44 PM
That is what I thought. However, I do have a load balancer that uses multicast sitting on the other stack in this network, and it does not seem to be communicating. While the stack circled blue needed to be added in order to allow multicast from an application called Singlewire, even though the default settings were the same. If I add the other stack that is in this network with the same settings, do I need to do that in a maintenance window? I am wondering if making these changes may cause interruptions to any other traffic on the network that is not related to multicast.
... View more
Nov 15 2023
12:47 PM
Older post, I know, but I have a related question: Do default multicast settings apply to all switches and stacks in the network? Or do you need to add each stack and define the settings? Circled red is the default setting, and circled blue is a stack within the network. For another stack in the network to have these settings, do I need to add that stack and apply the same settings?
... View more
Jul 12 2023
9:58 AM
I am currently co-term on licenses. The only devices that are close to expiration are my MX appliances (have MS, MR, MT and MV as well). I would like to just renew the MX licensing, but that is not an option with co-term. I was wondering about the implications of switching to the per-device model. Anyone with any recent experience with this? Also, I am noticing there does not appear to be an option within the Dashboard to switch to per-device, as this document states there should be: Meraki Licensing - Cisco Meraki I know I used to see it there. Was that removed?
... View more
Labels:
- Labels:
-
Licensing
Apr 10 2023
9:30 AM
Apr 10 2023
9:28 AM
Same here. MX, MS, MR, MT...all device status pages get failed to load message:
... View more
Jul 25 2022
12:59 PM
RSTP root info is on the summary page of each switch. Not sure if that is what you are looking for, or if you were wanting a report or list.
... View more
@Prasannajit: Are you using the Active-Active AutoVPN feature for site-to-site with one or more other MXs? If you have Active-Active AutoVPN, I believe you will get a VPN alert when WAN 2 drops, noting that a tunnel has failed. The alert will not specify whether it's due to WAN1 or WAN2 drop, but you do get an Alert that you would likely want to investigate. Not exactly the feature for which you are looking, but might be helpful.
... View more
Feb 16 2022
5:54 PM
This seems to be resolved with latest February updates from Microsoft. Applied all new updates on a couple of affected clients, and VPN still works.
... View more
Feb 7 2022
9:39 AM
Thanks for sharing your experience. It is nice to know I am not the only one. I assume Cisco has no incentive to resolve the issue as they would like to have customers buy Umbrella, as well.
... View more
Do you Aggr setup on the port(s) you are using on the MS225 as well?
... View more
Jan 27 2022
2:18 PM
I have AD integration configured for several years. I use it for both content filtering policies and VPN authentication. The AD servers are Server 2012 R2 domain controllers. I noticed two of then were producing tls errors in the dashboard. When I looked at the server, I see DCOM error Event ID 10036: The server-side authentication level policy does not allow the user <domain admin account> SID (S-1-5-21-71189414-624380436-382417117-21771) from address <MX IP Address> to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. Meraki stated the issue is with Microsoft Security and provided this link: https://support.microsoft.com/en-us/topic/kb5004442-manage-changes-for-windows-dcom-server-security-feature-bypass-cve-2021-26414-f1400b52-c141-43d2-941e-37ed901c769c I did not have success with the reg hack the article references, so I again asked support for help. I received this from Meraki Support: "After talking to our development team it looks like there is an update in the works for the AD integration but there is no current ETA on when that will be released. In the meantime, we suggest updating the registry key outlined in the following article by Microsoft." https://docs.microsoft.com/en-us/answers/questions/564347/server-2019-update-kb5005568-sept-2021-forcing-new.html?page=2&pageSize=10&sort=oldest Has anyone else seen this issue with an MX an AD integration?
... View more
Labels:
- Labels:
-
Other
Oct 26 2021
3:13 PM
I did replace the batteries even though the sensor indicated batteries were at 100%.
... View more
Oct 26 2021
3:11 PM
MV12 4.13 MR42 and MR42E was 27.7.1 when the sensor was working properly and never going offline. However is now 28.5 and able to support the MT10 and the MT10 is going offline and online many times a day. Logs show "detected insufficient RSSI from sensor" many times a day. These showed up only after upgrading the firmware on the MRs. Since the previous firmware did not support the MT sensors, I can only assume the sensor was connected to the MV camera previously, and it was working flawlessly. However, now it does not want to do that with the MRs being available...but the MRs don't provide good enough signal to accommodate the sensor, I guess. So my question is, why won't the sensor choose the MV that is four feet away and stay there? Up until October 10th (that is when the MR firmware upgrade occurred) the sensor and been in production for several months and had been online and trouble free the entire time. Now that the MRs are on a firmware that supports the sensor, I can't keep it online. Meraki is sending a replacement MT10, but I am assuming that will do the same thing. We shall see.
... View more
Oct 26 2021
10:45 AM
I do see in the logs environment that the sensor is connecting to a poorly performing AP. Is there a way to force a sensor to connect to an MV rather than an MR? I know it can use both as a gateway, but apparently it prefers APs. The MV is only four feet away. I am guessing it was always using that until the MR firmware upgrade.
... View more
Oct 26 2021
10:33 AM
I have an MT10 that goes offline for hours and causes a "red" indicator on the network to which it belongs. I have opened a support case and they emailed me a link to troubleshooting. Very helpful. Does anyone else have an issue with sensors going offline for hours at a time, then coming backing online on their own without any steps taken to resolve? This seemed to start after a recent MR firmware upgrade. I provided this information to support, but they said that is not the issue and do not revert. There is an MV camera about 4 feet from the sensor and the sensor should be using this MV as its gateway. Is there a way to check what the MT sensor is using as a gateway? Is there a log for this connection?
... View more
Oct 1 2021
8:55 AM
Please post follow up if/when you proceed with 15.44 on the mx400s. I've been holding off on my mx400 HA pair upgrade, due mostly to procrastination. But seeing this discussion, I am glad I procrastinated.
... View more
Apr 12 2021
6:48 AM
Hmm...I have the issue as well. MS350 and MX400...MX400 throughput indicates 350-400Mb/s, and MS350 says 30Mb/s. If switches don't have the CPU to accurately run the throughput test, that should be noted in the dashboard, I think.
... View more
Oct 22 2020
6:46 AM
Looks like the order of the switches is determined by MAC address, and not a whole lot a person can do other than make sure they are in the desired physical order in the rack (paying attention to the MAC when racking). Is this correct? I'm trying to reorder in the switch dashboard, myself.
... View more
Jun 19 2019
12:20 PM
3 Kudos
Older thread here, but I just wanted to post that Meraki supports states that this is fixed in 15.12: "The issue is fixed in 15.12. "Updated the AMP service to more gracefully handle cases where there are many out-of-order packets. This will result in fewer instances of file downloads failing when AMP is enabled." Please upgrade your MX(es) to 15.13 get the fix."" I have not verified this, but thought it worth sharing, anyway.
... View more
Dec 20 2018
6:35 AM
1 Kudo
Still no fixes for several known AMP issues, even with the latest 15.x that you need a support engineer to push. AMP is not going to be internal application friendly for quite sometime, based upon my experience with our internal SharePoint sites and forms, and a fix still not available in even the lastest beta.
... View more
Dec 11 2018
11:50 AM
Another update. 15.10 did not fix the AMP issue that I am seeing, and broke port 2 on an MX100 that was configured to use that port as internet 2. Rolled back to firmware 13.33 and port 2 works, again...AMP still has many issues, even with the latest beta, and the latest beta is not a good idea in a production environment. All done now. Thanks.
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 3 | 5732 | |
| 2 | 1041 | |
| 1 | 692 | |
| 1 | 6272 |
© 2024 Cisco Systems, Inc.
