Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About DerikA
DerikA
Getting noticed
Member since Jul 11, 2019
Aug 24 2022
Community Record
34
Posts
7
Kudos
3
Solutions
Badges
Jun 2 2022
8:05 AM
We are using 3rd party DNS filtering similar Umbrella. To prevent savey end users from using other DNS services I created a firewall rule on my lab MX allowing traffic to my DNS servers and to the 3rd party servers. I then created rules blocking traffic from any source to any destination on UDP and TCP ports 53 and 443. Testing showed this did not prevent me from resolving address if I manually set my DNS server. I have been searching the forms and it appears others have been able to make this work so what am I missing? Rule summary and order: 1: allow source, any internal network on ports 53 and 443 to destination my DNS and 3rd party DNS servers ports 53 and 443 2: deny source, any on ports 53 and 443 to destination any ports 53 and 443 (edited to fix a typo)
... View more
Feb 10 2022
6:51 AM
Hmm, reading on some Azure documentation it looks like BGP can only be enabled on an Azure VPN Gateway and not between the vMX and the internal Azure subnets. I'll post an update once I have spoken to my Azure admins.
... View more
Feb 10 2022
5:22 AM
What I've been told by our 3rd party vender that works with our Azure environment is that Azure only uses BGP or static routing. So, (me knowing very little of Azure) wouldn't it make sense that the we could set up a BGP peer in Azure which then could host the data center subnets? Basically replicating scenario 1 in BGP document from Meraki. https://documentation.meraki.com/MX/Networks_and_Routing/BGP
... View more
Feb 9 2022
4:54 PM
I have some questions around enabling BGP to advertise routes between my data center and my Meraki Organization. Situation: I manage the Meraki branch and hub networks, our SysAdmin and 3rd party vender manage our Azure datacenter. We have several spoke branches and 2 hubs, our corporate office and our vMX in Azure. Right now all the routing for the data center subnets to reach our branch subnets is done via a static route table in Azure (controlled by our SysAdmin). My vMX in Azure has all the data center subnets set up as local networks so they are advertised to all the branch MX devices (controlled by me). All my branch locations are set to load balance traffic over both WAN links and the AutoVPN is set to Active-Active so we have VPN tunnels active on both WAN links. Our branch and Azure subnets are getting more complex so I want to activate BGP to advertise the Meraki and data center subnets, eliminating static routes. My questions are: 1) If I activate BGP can I still have load balancing and Active-Active VPN tunnels or will I need to set a primary uplink and disable VPN tunnels on the secondary unlink? 2) If BGP is activated will the routes throughout my Meraki networks be disrupted as iBGP is establishing routes?
... View more
Jan 6 2022
1:12 PM
I have the wireless network set up using RADIUS authentication as documented here: https://documentation.meraki.com/MR/Encryption_and_Authentication/Configuring_RADIUS_Authentication_with_WPA2-Enterprise We are have user auth setup and using a Windows Group Policy so people don't have to enter there credentials every time and it has been working great. Then Windows 11 shows up and the things fell apart. If I try to connect using the wireless profile pushed by Active Directory the laptop give a message saying "Can't Connect to this Network" but if I find the hidden network and manually connect I can. RADIUS shows the following for logging: <Event><Timestamp data_type="4">01/06/2022 14:36:42.879</Timestamp><Computer-Name data_type="1">DC-01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><User-Name data_type="1">host/LAPTOP.CompanyName.local</User-Name><NAS-IP-Address data_type="3">1.1.2.241</NAS-IP-Address><NAS-Identifier data_type="1">00-00-00-00-00-13:vap3</NAS-Identifier><NAS-Port-Type data_type="0">19</NAS-Port-Type><Service-Type data_type="0">2</Service-Type><NAS-Port data_type="0">1</NAS-Port><Calling-Station-Id data_type="1">AC-74-B1-D9-E5-2C</Calling-Station-Id><Connect-Info data_type="1">CONNECT 54.00 Mbps / 802.11ac / RSSI: 54 / Channel: 44</Connect-Info><Acct-Session-Id data_type="1">9338353FC94ADA5F</Acct-Session-Id><Acct-Multi-Session-Id data_type="1">40797C9BB742FADC</Acct-Multi-Session-Id><Vendor-Specific data_type="2">000073E70217466172676F20436F7270202D20776972656C657373</Vendor-Specific><Vendor-Specific data_type="2">000073E7030F495420526F6F6D20466172676F</Vendor-Specific><Vendor-Specific data_type="2">000073E7040B20436F727020495420</Vendor-Specific><Called-Station-Id data_type="1">00-00-00-00-00-13:CompanyName</Called-Station-Id><Vendor-Specific data_type="2">000073E7010F495420526F6F6D20466172676F</Vendor-Specific><Framed-MTU data_type="0">1400</Framed-MTU><Client-IP-Address data_type="3">1.1.2.241</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Legacy Wireless Subnets</Client-Friendly-Name><Proxy-Policy-Name data_type="1">CompanyName</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">CompanyName\LAPTOP$</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">CompanyName\LAPTOP$</Fully-Qualifed-User-Name><Class data_type="1">311 1 1.1.1.6 01/01/2022 21:51:31 87093</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">CompanyName</NP-Policy-Name><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event> <Event><Timestamp data_type="4">01/06/2022 14:36:42.879</Timestamp><Computer-Name data_type="1">DC-01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311 1 1.1.1.6 01/01/2022 21:51:31 87093</Class><Session-Timeout data_type="0">30</Session-Timeout><Acct-Session-Id data_type="1">9338353FC94ADA5F</Acct-Session-Id><NP-Policy-Name data_type="1">CompanyName</NP-Policy-Name><Authentication-Type data_type="0">5</Authentication-Type><Client-IP-Address data_type="3">1.1.2.241</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Legacy Wireless Subnets</Client-Friendly-Name><Proxy-Policy-Name data_type="1">CompanyName</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">CompanyName\LAPTOP$</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">CompanyName\LAPTOP$</Fully-Qualifed-User-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event> <Event><Timestamp data_type="4">01/06/2022 14:36:42.910</Timestamp><Computer-Name data_type="1">DC-01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address data_type="3">1.1.2.241</NAS-IP-Address><NAS-Identifier data_type="1">00-00-00-00-00-13:vap3</NAS-Identifier><NAS-Port-Type data_type="0">19</NAS-Port-Type><Service-Type data_type="0">2</Service-Type><NAS-Port data_type="0">1</NAS-Port><Calling-Station-Id data_type="1">AC-74-B1-D9-E5-2C</Calling-Station-Id><Connect-Info data_type="1">CONNECT 54.00 Mbps / 802.11ac / RSSI: 54 / Channel: 44</Connect-Info><Acct-Session-Id data_type="1">9338353FC94ADA5F</Acct-Session-Id><Acct-Multi-Session-Id data_type="1">40797C9BB742FADC</Acct-Multi-Session-Id><Vendor-Specific data_type="2">000073E70217466172676F20436F7270202D20776972656C657373</Vendor-Specific><Vendor-Specific data_type="2">000073E7030F495420526F6F6D20466172676F</Vendor-Specific><Vendor-Specific data_type="2">000073E7040B20436F727020495420</Vendor-Specific><Called-Station-Id data_type="1">00-00-00-00-00-13:CompanyName</Called-Station-Id><Vendor-Specific data_type="2">000073E7010F495420526F6F6D20466172676F</Vendor-Specific><Framed-MTU data_type="0">1400</Framed-MTU><Client-IP-Address data_type="3">1.1.2.241</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Legacy Wireless Subnets</Client-Friendly-Name><User-Name data_type="1">host/LAPTOP.CompanyName.local</User-Name><Proxy-Policy-Name data_type="1">CompanyName</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">CompanyName\LAPTOP$</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">CompanyName\LAPTOP$</Fully-Qualifed-User-Name><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">CompanyName</NP-Policy-Name><Class data_type="1">311 1 1.1.1.6 01/01/2022 21:51:31 87094</Class><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event> <Event><Timestamp data_type="4">01/06/2022 14:36:42.910</Timestamp><Computer-Name data_type="1">DC-01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311 1 1.1.1.6 01/01/2022 21:51:31 87094</Class><Acct-Session-Id data_type="1">9338353FC94ADA5F</Acct-Session-Id><Session-Timeout data_type="0">30</Session-Timeout><NP-Policy-Name data_type="1">CompanyName</NP-Policy-Name><Client-IP-Address data_type="3">1.1.2.241</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Legacy Wireless Subnets</Client-Friendly-Name><Proxy-Policy-Name data_type="1">CompanyName</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">CompanyName\LAPTOP$</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">CompanyName\LAPTOP$</Fully-Qualifed-User-Name><Authentication-Type data_type="0">5</Authentication-Type><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event> <Event><Timestamp data_type="4">01/06/2022 14:36:42.942</Timestamp><Computer-Name data_type="1">DC-01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address data_type="3">1.1.2.241</NAS-IP-Address><NAS-Identifier data_type="1">00-00-00-00-00-13:vap3</NAS-Identifier><NAS-Port-Type data_type="0">19</NAS-Port-Type><Service-Type data_type="0">2</Service-Type><NAS-Port data_type="0">1</NAS-Port><Calling-Station-Id data_type="1">AC-74-B1-D9-E5-2C</Calling-Station-Id><Connect-Info data_type="1">CONNECT 54.00 Mbps / 802.11ac / RSSI: 54 / Channel: 44</Connect-Info><Acct-Session-Id data_type="1">9338353FC94ADA5F</Acct-Session-Id><Acct-Multi-Session-Id data_type="1">40797C9BB742FADC</Acct-Multi-Session-Id><Vendor-Specific data_type="2">000073E70217466172676F20436F7270202D20776972656C657373</Vendor-Specific><Vendor-Specific data_type="2">000073E7030F495420526F6F6D20466172676F</Vendor-Specific><Vendor-Specific data_type="2">000073E7040B20436F727020495420</Vendor-Specific><Called-Station-Id data_type="1">00-00-00-00-00-13:CompanyName</Called-Station-Id><Vendor-Specific data_type="2">000073E7010F495420526F6F6D20466172676F</Vendor-Specific><Framed-MTU data_type="0">1400</Framed-MTU><Client-IP-Address data_type="3">1.1.2.241</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Legacy Wireless Subnets</Client-Friendly-Name><User-Name data_type="1">host/LAPTOP.CompanyName.local</User-Name><Proxy-Policy-Name data_type="1">CompanyName</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">CompanyName\LAPTOP$</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">CompanyName\LAPTOP$</Fully-Qualifed-User-Name><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">CompanyName</NP-Policy-Name><Class data_type="1">311 1 1.1.1.6 01/01/2022 21:51:31 87095</Class><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event> <Event><Timestamp data_type="4">01/06/2022 14:36:42.942</Timestamp><Computer-Name data_type="1">DC-01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311 1 1.1.1.6 01/01/2022 21:51:31 87095</Class><Session-Timeout data_type="0">30</Session-Timeout><Acct-Session-Id data_type="1">9338353FC94ADA5F</Acct-Session-Id><NP-Policy-Name data_type="1">CompanyName</NP-Policy-Name><Authentication-Type data_type="0">5</Authentication-Type><Client-IP-Address data_type="3">1.1.2.241</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Legacy Wireless Subnets</Client-Friendly-Name><Proxy-Policy-Name data_type="1">CompanyName</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">CompanyName\LAPTOP$</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">CompanyName\LAPTOP$</Fully-Qualifed-User-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event> <Event><Timestamp data_type="4">01/06/2022 14:36:42.989</Timestamp><Computer-Name data_type="1">DC-01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address data_type="3">1.1.2.241</NAS-IP-Address><NAS-Identifier data_type="1">00-00-00-00-00-13:vap3</NAS-Identifier><NAS-Port-Type data_type="0">19</NAS-Port-Type><Service-Type data_type="0">2</Service-Type><NAS-Port data_type="0">1</NAS-Port><Calling-Station-Id data_type="1">AC-74-B1-D9-E5-2C</Calling-Station-Id><Connect-Info data_type="1">CONNECT 54.00 Mbps / 802.11ac / RSSI: 54 / Channel: 44</Connect-Info><Acct-Session-Id data_type="1">9338353FC94ADA5F</Acct-Session-Id><Acct-Multi-Session-Id data_type="1">40797C9BB742FADC</Acct-Multi-Session-Id><Vendor-Specific data_type="2">000073E70217466172676F20436F7270202D20776972656C657373</Vendor-Specific><Vendor-Specific data_type="2">000073E7030F495420526F6F6D20466172676F</Vendor-Specific><Vendor-Specific data_type="2">000073E7040B20436F727020495420</Vendor-Specific><Called-Station-Id data_type="1">00-00-00-00-00-13:CompanyName</Called-Station-Id><Vendor-Specific data_type="2">000073E7010F495420526F6F6D20466172676F</Vendor-Specific><Framed-MTU data_type="0">1400</Framed-MTU><Client-IP-Address data_type="3">1.1.2.241</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Legacy Wireless Subnets</Client-Friendly-Name><User-Name data_type="1">host/LAPTOP.CompanyName.local</User-Name><Proxy-Policy-Name data_type="1">CompanyName</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">CompanyName\LAPTOP$</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">CompanyName\LAPTOP$</Fully-Qualifed-User-Name><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">CompanyName</NP-Policy-Name><Class data_type="1">311 1 1.1.1.6 01/01/2022 21:51:31 87096</Class><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event> <Event><Timestamp data_type="4">01/06/2022 14:36:42.989</Timestamp><Computer-Name data_type="1">DC-01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311 1 1.1.1.6 01/01/2022 21:51:31 87096</Class><Session-Timeout data_type="0">30</Session-Timeout><Acct-Session-Id data_type="1">9338353FC94ADA5F</Acct-Session-Id><NP-Policy-Name data_type="1">CompanyName</NP-Policy-Name><Authentication-Type data_type="0">5</Authentication-Type><Client-IP-Address data_type="3">1.1.2.241</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Legacy Wireless Subnets</Client-Friendly-Name><Fully-Qualifed-User-Name data_type="1">CompanyName\LAPTOP$</Fully-Qualifed-User-Name><Proxy-Policy-Name data_type="1">CompanyName</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">CompanyName\LAPTOP$</SAM-Account-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event> <Event><Timestamp data_type="4">01/06/2022 14:36:43.020</Timestamp><Computer-Name data_type="1">DC-01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address data_type="3">1.1.2.241</NAS-IP-Address><NAS-Identifier data_type="1">00-00-00-00-00-13:vap3</NAS-Identifier><NAS-Port-Type data_type="0">19</NAS-Port-Type><Service-Type data_type="0">2</Service-Type><NAS-Port data_type="0">1</NAS-Port><Calling-Station-Id data_type="1">AC-74-B1-D9-E5-2C</Calling-Station-Id><Connect-Info data_type="1">CONNECT 54.00 Mbps / 802.11ac / RSSI: 54 / Channel: 44</Connect-Info><Acct-Session-Id data_type="1">9338353FC94ADA5F</Acct-Session-Id><Acct-Multi-Session-Id data_type="1">40797C9BB742FADC</Acct-Multi-Session-Id><Vendor-Specific data_type="2">000073E70217466172676F20436F7270202D20776972656C657373</Vendor-Specific><Vendor-Specific data_type="2">000073E7030F495420526F6F6D20466172676F</Vendor-Specific><Vendor-Specific data_type="2">000073E7040B20436F727020495420</Vendor-Specific><Called-Station-Id data_type="1">00-00-00-00-00-13:CompanyName</Called-Station-Id><Vendor-Specific data_type="2">000073E7010F495420526F6F6D20466172676F</Vendor-Specific><Framed-MTU data_type="0">1400</Framed-MTU><Client-IP-Address data_type="3">1.1.2.241</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Legacy Wireless Subnets</Client-Friendly-Name><User-Name data_type="1">host/LAPTOP.CompanyName.local</User-Name><Proxy-Policy-Name data_type="1">CompanyName</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">CompanyName\LAPTOP$</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">CompanyName\LAPTOP$</Fully-Qualifed-User-Name><NP-Policy-Name data_type="1">CompanyName</NP-Policy-Name><Class data_type="1">311 1 1.1.1.6 01/01/2022 21:51:31 87097</Class><Authentication-Type data_type="0">11</Authentication-Type><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event> <Event><Timestamp data_type="4">01/06/2022 14:36:43.020</Timestamp><Computer-Name data_type="1">DC-01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311 1 1.1.1.6 01/01/2022 21:51:31 87097</Class><Authentication-Type data_type="0">11</Authentication-Type><Acct-Session-Id data_type="1">9338353FC94ADA5F</Acct-Session-Id><NP-Policy-Name data_type="1">CompanyName</NP-Policy-Name><Fully-Qualifed-User-Name data_type="1">CompanyName\LAPTOP$</Fully-Qualifed-User-Name><Client-IP-Address data_type="3">1.1.2.241</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Legacy Wireless Subnets</Client-Friendly-Name><SAM-Account-Name data_type="1">CompanyName\LAPTOP$</SAM-Account-Name><Proxy-Policy-Name data_type="1">CompanyName</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><Packet-Type data_type="0">3</Packet-Type><Reason-Code data_type="0">265</Reason-Code></Event> Meraki shows: Connection start time Client device AP SSID Failure stage Failure reason Thu Jan 6, 2022, 14:37:02 ac:74:b1:d9:e5:2c IT Room Fargo MAGNUM Authentication Client failed 802.1X authentication to the RADIUS server.type='802.1X auth fail' num_eap='7' first_time='0.012763271' associated='false' radio='1' vap='3' Thu Jan 6, 2022, 14:35:03 ac:74:b1:d9:e5:2c IT Room Fargo MAGNUM Authentication Client failed 802.1X authentication to the RADIUS server.type='802.1X auth fail' num_eap='7' first_time='0.014429834' associated='false' radio='1' vap='3' Thu Jan 6, 2022, 14:31:06 ac:74:b1:d9:e5:2c IT Room Fargo MAGNUM Authentication Client failed 802.1X authentication to the RADIUS server.type='802.1X auth fail' num_eap='7' first_time='0.014113104' associated='false' radio='1' vap='3' Thu Jan 6, 2022, 14:28:45 ac:74:b1:d9:e5:2c IT Room Fargo MAGNUM Authentication Client failed 802.1X authentication to the RADIUS server.type='802.1X auth fail' num_eap='7' first_time='0.015952355' associated='false' radio='1' vap='3' Thu Jan 6, 2022, 14:27:05 ac:74:b1:d9:e5:2c IT Room Fargo MAGNUM Authentication Client failed 802.1X authentication to the RADIUS server.type='802.1X auth fail' num_eap='7' first_time='0.016288354' associated='false' radio='1' vap='3' Thu Jan 6, 2022, 14:25:55 ac:74:b1:d9:e5:2c IT Room Fargo MAGNUM Authentication Client failed 802.1X authentication to the RADIUS server.type='802.1X auth fail' num_eap='7' first_time='0.017201979' associated='false' radio='1' vap='3' I am not finding any useful information in system logs on the laptop but I am no expert at digging through windows logs so I may be missing something. Thank you in advance for any suggestions on how to resolve this.
... View more
Aug 20 2021
6:55 AM
@Inderdeep thanks for the response, yes I had looked that over. My concern, which maybe unwarranted, is the lack of options for how to screw the mount down when compared to a normal mount and the mount being plastic. I've been thinking about using small self tapping screws but I am worried about damaging the mount when screwing it into place. Hence the ask to see how other people have been mounting MR70s.
... View more
Aug 20 2021
6:32 AM
I acquired several MR70 access points to deploy in a cross dock (narrow warehouse with semi bays on either side) that is often open to the elements. Now that I have them I see the mounting plate is very different than other Meraki access points and made of plastic. Does anyone have any suggestions on how to mount these to I-beams? On the normal access points I have been buying clams, attaching them to a low profile electrical box and attaching the mounting plate to that but with the smaller plastic plate it does not have all the mounting options. Thanks for any suggestions.
... View more
Jul 27 2021
7:36 PM
Yes, the MX is doing the inter vlan routing. As for group policies, at this time no they don’t need to go between buildings.
... View more
Jul 27 2021
3:05 PM
I have several physical buildings in the same logical network sharing one MX, all utilizing Meraki wireless. I am not supporting outdoor wireless at this time. Each building has it's own subnets for data, phones and to some extent wireless. Each building has it's own street address and they are in a row with between 60-200 feet between the neighboring building. Considering just the wireless, it best to have all the buildings in the same Meraki network or would it be better to have each building in it's own Meraki network?
... View more
Jul 8 2021
3:30 PM
Not being well versed in Azure myself, can someone give me some insight on a few questions? 1) If a vMX goes down in Azure how fast could it be restored? Is there automation that could be created to automatically recover it? 2) Has anyone added a second vMX in Azure for high availability if the primary goes down and cannot be recovered? I would assume you do something like what @PhilipDAth demonstrated in AWS in this post. https://community.meraki.com/t5/Security-SD-WAN/How-to-Deploy-Meraki-dual-redundant-vMX100-in-HA-config-in/m-p/43731 Thanks in advance for your replies.
... View more
Jun 11 2021
7:49 AM
OK, sorry for the delay in following up. Here is the finial solution I am implementing. After talking with the Meraki tech he recommended he push code to the MX devices I would be moving from one organization to another as there was a chance that they could lose the static IP settings despite it did not happen in my testing. The code does not cause any issues later on so I had him apply the code to maintain the static IP config on any internet port. Planned move is in a couple weeks and I am expecting a smooth transition.
... View more
Jun 2 2021
12:58 PM
1 Kudo
I did some testing with a Lab organization and one of my Lab MX devices. Here is what process was and my results: Assigned a static public IP and gateway to WAN2 Connected WAN2 to internet circuit Confirmed connectivity Removed the Lab MX from the network, got a warning static IP may be lost Unclaimed the Lab MX Claimed the MX in the Lab organization Added it to a test network WAN2 of the MX did keep the static IP config. I repeated several time to confirm. I have reported the results the the Meraki tech I am working with and waiting for his input.
... View more
Jun 1 2021
7:37 AM
Meraki support is saying that once it is removed from the organization the MX will go to factory defaults losing any static IP information unless, I set the static IP information on the port and then have Meraki support push code to maintain that IP when it otherwise would default to DHCP. I believe this is via using the MX web page rather than the dashboard but need to confirm. I will update the thread once I have confirmation/more information.
... View more
May 28 2021
10:51 AM
I have 2 Meraki organizations, A and B. Org B has 8 remote networks in different cities. All of the MX devices in org B have static public IPs on private internet circuits, no MPLS lines or DHCP on the circuits. The question is when I remove an MX device from org B and add it to org A will the MX device be able to reach the internet to get the updated settings from the dashboard if it internet port needs a static IP? My ideas for options are: 1) someone onsite will have to manually config the internet port with the static IP via the devices web interface 2) a temporary alternate internet source providing DHCP is needed 3) power off the MX device, apply config changes to the dashboard, reconnect the MX device so it can then download the new config Anyone done this before and tried any of the 3 options or is there something else I can do?
... View more
May 10 2021
6:07 PM
@PhilipDAth sorry bumped the solved by accident, also I appreciate you always answering my questions as I’m still learning. I think I understand what you’re saying about symmetric routing, I’ll do some more reading on this now that I have a place to look. Most of the spokes are split tunnels primarily on non-MPLS circuits. Also the Corp/datacenter Cisco router is load balancing over 2 internet sources and the majority of the spoke locations are load balanced using Meraki MX load balancing.
... View more
May 10 2021
10:27 AM
Hopefully I can describe this right. First current network set up: Corp/datacenter: The edge is a Cisco router connected to our "core" L3 switch. Our MX100 is set as a one-armed concentrator/hub that is also connected to the "core" switch. The "core" layer 3 switch is handling the internal routing for the local Corp network and the MX100 providing VPN connection to all the spoke MXs. The external interface for the Cisco router has several external static IPs terminating to it and they NAT to internal devices in the datacenter/corporate office and to some devices in the spoke locations. Problem: NAT addresses going to spoke locations drop all traffic at the MX and cannot reach the spoke location. Any NAT address going to a subnet at the Corp location work. I have added the external IP range and the external interface IP of the Cisco router to the local network on the MX concentrator under Site To Site VPN - VPN Setting but traffic still is dropped. Is it possible to route NAT traffic for over the MX VPN in this configuration and if so how would I do so? I hope that all makes. Please let me know if you want to know any more details and thanks in advance for any assistance.
... View more
Apr 27 2021
12:13 PM
Correct we do not have any static routes in this situation. Like I said my worry is if the primary MX dies since the OSPF router ID is the static of the primary the locale networks on my layer 3 switch will lose the spoke networks attached to the hub MX pair. So just to confirm as a "best practice" it would be best to change the OSPF router ID to the VIP rather than the static of the primary MX, correct?
... View more
Apr 27 2021
11:49 AM
I have an MX100 set up as a VPN concentrator/hub for our Meraki networks. It is configured with a warm spare. We are then advertising OSPF to a Cisco layer 3 switch so the local network can see all the spoke networks. Primary MX100 static IP of 192.168.0.10 Spare MX100 static IP of 192.168.11 Gateway for both 192.168.0.1 Virtual IP of 192.168.0.2 OSPF Router ID is 192.168.0.10 All of this was set up before I arrived. My question is if the primary MX fails. Will OSPF still be advertised correctly? To me since it is using the static IP for primary MX as the router ID rather than the virtual IP it would fail. Is that correct? Thanks in advance for any isite. DerikA
... View more
Mar 20 2021
2:54 PM
1 Kudo
Before After
... View more
Mar 11 2021
1:37 PM
I have created a new guest wireless network that I am pushing to all of our location and I am having issues getting the splash page to show up on the guest wireless on any MX65W devices. I have the splash page turned on under Security and SD-WAN, Access Control and the selected Click-through for that VLAN but nothing shows up when I connect to the guest wireless. Fair notice I have not tested on a wired connection yet. I have used rules both in via both Group Policy and the Firewall to isolate the VLAN and restrict somethings and I have tested with and without these enabled. Any suggestions or advices? Thanks in advance!
... View more
Jan 21 2021
2:55 PM
@DarrenOC Yes I have, lol. Thanks everyone I got my answers, much appreciated.
... View more
Jan 21 2021
2:44 PM
@cmr OK, will the existing config on the MS225 stay when I create the stack or will I need to program it after making that stack?
... View more
Jan 21 2021
2:37 PM
2 Kudos
Sorry, I type-o’d the switch types. They are an existing MS225 and two new MS210s. I’m updating the original post.
... View more
Jan 21 2021
1:05 PM
Part 1: I have a MS225 in use now, two new MS210s and stacking cables. Can I create a stack with all 3 switches and not lose the port config on the one existing switch? Part 2: I want to have have this stack to have multiple connections to the 2 "Core" Cisco 3850 switches. I assume I would just aggregate several ports as the uplink trunk doing the mirroring this on the "Core" or is there a better way to do this? Thanks in advance for any help. note the reply from @DarrenOC that answers question 1, the existing MS225 should keep its config when added to the stack.
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 2380 | Feb 10 2022 6:51 AM | |
| 2064 | Jun 11 2021 7:49 AM | |
| 1542 | Aug 10 2020 5:07 AM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 2 | 3542 | |
| 2 | 2761 | |
| 1 | 2093 | |
| 1 | 10181 | |
| 1 | 3093 |
© 2024 Cisco Systems, Inc.
