Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About CoreyDavoll1
CoreyDavoll1
Getting noticed
Member since Feb 6, 2023
2 weeks ago
Community Record
57
Posts
94
Kudos
2
Solutions
Badges
Nov 13 2024
10:23 AM
Does anyone out there use the Paessler PRTG Meraki sensor? I've had it setup for a while without much issues but yesterday I started getting alerts that both wan interfaces on random MX's were in a failed state. This seems to be cycling through all our MX's 1 to 2 at a time. I've engaged their support and am waiting to hear back but from the logs it looks like the api is returning the failed state. Below is a snippet from their log [{"networkId":"L_586030901511592891","serial":"Q2YN-GQZV-VK8K","model":"MX85","highAvailability":{"enabled":false,"role":"primary"},"lastReportedAt":"2024-11-13T17:35:25Z","uplinks":[{"interface":"wan1","status":"failed","ip":"50.220.75.194","gateway":"50.220.75.193","publicIp":"50.220.75.194","primaryDns":"208.67.222.222","secondaryDns":"208.67.220.220","ipAssignedBy":"static"},{"interface":"wan2","status":"failed","ip":"131.239.184.74","gateway":"131.239.184.73","publicIp":"131.239.184.74","primaryDns":"208.67.222.222","secondaryDns":"207.67.220.220","ipAssignedBy":"static"}]}] 2024-11-13 18:00:38.552508 DEBG TId 5264 Result of Sensor 20521> Uplink Q2YN-GQZV-VK8K 2024-11-13 18:00:38.552508 DEBG TId 5264 Result of Sensor 20521> - wan1 has status failed 2024-11-13 18:00:38.552508 DEBG TId 5264 Result of Sensor 20521> - wan2 has status failed 2024-11-13 18:00:38.552508 DEBG TId 5264 Result of Sensor 20521> Requesting device statuses 2024-11-13 18:00:39.169841 DEBG TId 5264 Result of Sensor 20521> 200 OK
... View more
Sep 13 2024
12:06 PM
4 Kudos
I just specify the vlans that I need for the trunk Also, that Catalysts don't support port profiles yet so the Catalyst and the connecting MS port both need to be configured identically (MS without a port profile)
... View more
Sep 9 2024
10:48 AM
4 Kudos
If you don't have a lot of switches to look at then you can just use the switch summary page and make sure port is checked.
... View more
Sep 9 2024
7:11 AM
2 Kudos
The MS130's also have an issue in the 16.x firmware with the control plane that could be causing it. The fix has been implemented in 17.1.2. I've been running this since it was released and it has fixed the majority of my CRC/STP/UDLD issues.
... View more
Aug 28 2024
5:23 PM
4 Kudos
MS17.1.2 is now released. Pushing it to one of sites tonight. Hopefully this finally fixes the issue.
... View more
Aug 23 2024
7:22 AM
What firmware are you running? We've been chasing a similar issue. I'm waiting on the next release of ms17 to see if they have all the fixes implemented.
... View more
Aug 21 2024
7:07 AM
8 Kudos
Aug 21 2024
6:53 AM
4 Kudos
It's a caveat that the management IP needs to be independent of its own layer 3 routing. https://documentation.meraki.com/MS/Layer_3_Switching/MS_Layer_3_Switching_and_Routing Layer 3 Interface (SVI) Caveats Switch Management IP and Layer 3 Interfaces (SVIs) The management IP is treated entirely different from the SVIs and must be a different IP address. It can be placed on a routed or non-routed VLAN (e.g.: a management VLAN independent from client traffic). Traffic from the management IP address to the Cisco Meraki Cloud Controller will not use the layer 3 routing settings; instead, it will be using its configured default gateway. Therefore, it is important that the IP address, VLAN, and default gateway configured in your switch management IP can still provide connectivity to the internet independently from the switche's own L3 routing settings. The Switch (or Stack) management IP configuration cannot have Gateway address defined as one of its own SVI address when it is performing Layer 3 routing. It will not be able to check in using the assigned management IP when the gateway is pointed to itself. For example, if 192.168.1.1 is one of the L3 interfaces (SVI) on a switch (or stack), you cannot have 192.168.1.1 as the gateway for its management IP (Switching > Switches > LAN IP). For switch stacks performing L3 routing, ensure that the management IP subnet does not overlap with the subnet of any of it's own configured L3 interfaces. Overlapping subnets on the management IP and L3 interfaces can result in packet loss when pinging or polling (via SNMP) the management IP of stack members. Note: The overlapping subnet limitation does not apply to the MS390 series switches.
... View more
Aug 14 2024
7:26 AM
At first glance your config looks good. I've been chasing the same issues with UDLD but I'm using MS130's in my access and they connect to C9300's. I think the 16.x firmware has had issues and support had me update to 17.x to test and that has helped some. Might be worth opening a support case to see if you're running into that bug.
... View more
Aug 5 2024
10:23 AM
Nope, maybe the node you're on is having issues. What error are you getting?
... View more
Aug 5 2024
10:08 AM
Well they did try to blame the cables and ports before they fessed up to the issue. I'm still seeing the issue on 17.1.1 so they haven't fixed everything yet. One site that has an MS350 and MS130's seems to be better than when it was on 16.9 but not 100% yet. When I updated my 130's at another site to 17.1.1 that are connected to a C9300 with CS16.8, the issue got worse.
... View more
Jul 29 2024
9:52 AM
6 Kudos
Congrats everyone!
... View more
Jul 26 2024
10:33 AM
Well, my site that has a MS350 at the core and 2 MS130's that's on the beta MS17 code had the UDLD issue again. It was stable for a week. Guess I'll wait for the next release.
... View more
Jul 25 2024
8:16 AM
3 Kudos
Congrats!!!
... View more
Jul 24 2024
5:09 AM
3 Kudos
I applied the MS17 code on Thursday night. My SE said that there are some fixes in the beta but they haven't fixed all the triggers yet. In my site that has a MS350 at the core and 2 MS130's (MS350->MS130-01->MS130-02->MS350), the firmware seems to have corrected the issue. However, at another site that has a C9300 and 5 MS130's (C9300->MS130-01->MS130-02->MS130-03->MS130-04->MS130-05->C9300) it just made it worst so I downgraded back to 16.9
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 967 | Jun 19 2024 6:56 AM | |
| 1491 | Apr 6 2023 1:09 PM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 8 | 5107 | |
| 6 | 1906 | |
| 6 | 1157 | |
| 6 | 5672 | |
| 5 | 1679 |
© 2024 Cisco Systems, Inc.
