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 PatTheCat
PatTheCat
Comes here often
Member since Nov 16, 2023
Jan 29 2024
Community Record
7
Posts
0
Kudos
0
Solutions
Badges
Dec 1 2023
12:52 PM
all config is correct. in the nps on the HQ side in the nps logs, I see success from the mr46 that can connect, it's as if the others that fail don't even hit the nps. no packet capture so far as to not sure what I'm looking for. my client is 10.0.0.0/8 so all aps are part of that client so I know that's good. secret is good. as I explained, once 4 mr46 will connect to HQ nps, next test, 10 will connect, next test 6 will connect... so doubt it's MTU. but locally no issue, they will all 14 connect all the time when nps is on the local network of the remote site.
... View more
Dec 1 2023
12:30 PM
hi, so I have a remote site, it's using meraki APs, specifically MX46. I have 1 radius in HQ, we're using microsoft NPS and 1 radius in the remote site, so local to the MX46. when from the dashboard I try to test the radius connection to the nps in the HQ, it will fail randomly some of them so over 14 ap, once 3 will fail then again 8 will fail then 6 will fail etc... but when I do the same test with the nps that's local to the MX, 100% success rate. ping time between the site and HQ is 70ms, no packet loss. configuration of the NPS is all good... anyone else had this issue? thanks.
... View more
Nov 16 2023
9:48 AM
yes but I have some spokes primary with hub1 and some spokes primary with hub2. if I make 1 hub more desirable with bgp in the meraki hub directly then I end up with asynchronous issue again. so let's say I say hub2 is less desirable with bgp and one of the spokes prefers hub2 due to geography and closer hub to the spoke. now the core prefers hub1. so if from core I ping spoke it will go through hub1 and come back to me through hub2 because spoke prefers hub2.
... View more
Nov 16 2023
9:42 AM
my other solution is to take my HUB1 which is actually a cluster of 2 test MX105 (active/passive) and split that into HUB1 and HUB3. I make HUB3 ospf lower priority advertisements as you show in the screenshot on top. then 1 spoke will connect to either HUB1 and HUB3 or HUB2 and HUB3. this way my routing issue is fixed since the backup to all spokes is HUB3 and it sends ospf with lower priority than hub1 and hub2. I'll still wait and consult with meraki and cisco to see what other options I have but for now this will work.
... View more
Nov 16 2023
6:30 AM
it won't work on the hub, if I change the cost of the ospf on the hub itself then that hub is either better always or lesser priority always. yet I have some spokes that prefer that given hub. seems to me only way as you say is directly on the core. but then again I have to know every subnet I want to give priority to on one side vs the other... too much manual entries. was hoping for maybe some other option :). thanks.
... View more
Nov 16 2023
6:02 AM
hi, I'm attaching a picture that explains it all. in a nutshell I have 2 hubs and I connect spokes to both hubs. HUb1 is first and Hub2 is second in the spoke hubs list. I need a way without doing any manual entry in the cisco core network for the network to know that to reach spoke the network should prefer to route through hub1. please see attached picture. many spokes but I've selected the middle one as example.
... View more
© 2024 Cisco Systems, Inc.
