About KarstenI

KarstenI

What are you referring to with "Study-Guide"? At least my experience was that many of the questions were only to answer after reading lots ans lots of the documentation and practicing the stuff. Good luck next time.

KarstenI

I also opened a Case for this and at least the Supporter didn't directly say that it is not supported. Let's see what comes out of this.

KarstenI

I just tested it, and you are right that it doesn't work. But that is not because of CoA. It just seems that the MX is ignoring the RADIUS attribute for the VLAN. I am not 100% sure, but I think I have done this previously (on older MX versions) and it worked. Best to open a support case.

KarstenI

The MX doesn't do CoA. But you can still do Authentication and Authorization without. https://documentation.meraki.com/MX/Access_Control_and_Splash_Page/MX_Access_Policies_(802.1X)

KarstenI · ‎12-26-2022

Not the router, but the MX should get it's IP by DHCP from the TCR100. But first I would test the device separately to find out if the repeating loss is in the WAN or on the LAN side of the TCR100.

KarstenI · ‎12-25-2022

I assume that I am not the only one who doesn't yet understand what the problem is.Please draw a picture with all IPs and describe what works and what doesn't work.

KarstenI · ‎12-24-2022

Do you want to access the IP that is also the default-route on WAN2? The easiest way is to temporary set WAN2 as the primary WAN link and then access the device. If you need continuous access you need to configure a flow preference for the WAN2 subnet over WAN2.

KarstenI · ‎12-24-2022

You are right about the grace period, you have 30 days left. For the license ... no, it is not valid for a vMX because it is for the ... MX100. That leads to the question why you ordered it if you don't have one? By mistake? If the licenses is new, you can let it refund. About applying the licenses ... I wonder why you got three licenses. To extend the license duration of the organisation, you need to apply one license with all what is needed in one license. But if you have your dashboard license expired anyhow, you could add the first license with "Renew my Dashboard license" which resets the inventory devices to the device of the first license. After that you add the other licenses with "License more devices" and you are all good. And for you next renewal interval, come back and ask how to handle all of this before ordering the licenses. Happy Holidays!

KarstenI · ‎12-20-2022

I really would love to see this well documented by Meraki …

KarstenI · ‎12-20-2022

As mentioned, not natively. And I also like the Umbrella solution mentioned by @Brash. But if you are looking for SSL decryption for both out- and incoming traffic, an inline IPS device between your MX and the next switch could also do the job,

KarstenI · ‎12-19-2022

Nothing that is included in the Meraki solution. And in my opinion, if you need something like this, the best option is to choose an ISP that offers this as a service.

KarstenI · ‎12-12-2022

To add on what is already said: If PPPoE is used on the WAN, the MTU is automatically adjusted for the overhead If you need a different WAN MTU, Support can set this for you. But this reduced MTU is not accounted for when using non-Meraki IPsec VPNs and you will certainly run into problems.

KarstenI · ‎12-09-2022

No need to apologise. Yes, they are different software on different hardware. And the ENSDWI is completely touching the "other" solution.

KarstenI · ‎12-09-2022

Cisco has two SD-WAN solutions. In this community we talk about the Meraki implementation. The other solution is the "Cisco SD-WAN" which has its roots in the Viptella acquisition. These two solutions are completely separate and are not compatible with each other. And well, with you studying for ENSDWI, we are all sorry to see you go ... 😉 But the Cisco Learning Network https://learningnetwork.cisco.com or the Cisco Support Community https://community.cisco.com are probably the right places for your questions. Please come back for your ECMS studies! 🙂

KarstenI · ‎12-08-2022

Have fun and stay healthy!

KarstenI · ‎12-08-2022

Yes, these local functions will still work without dashboard-connectivity.

KarstenI · ‎12-07-2022

you could look into the MX75 which can go up to a Gig. But it's much more expensive than the MX64.

KarstenI · ‎12-02-2022

Well done everyone!

KarstenI · ‎12-02-2022

Yes, this will work. I also typically update the hubs last and my spokes were running v17 while one or more hubs were still on v16.

KarstenI · ‎12-01-2022

The typical way is to read the actual config from the network, adjust the settings and write the new config back.

KarstenI · ‎12-01-2022

Oh yes! That is a big improvement.

KarstenI · ‎12-01-2022

Whatever the idea was, I support it! 😀

KarstenI · ‎12-01-2022

The most important question is where this ACL is applied. Keep in mind that in the Meraki world, you don't apply an ACL to a switch. You apply the ACL to the switches in the network. And this line permit 172.x.x.x 0.0.0.31 could be wrong (at least if you want to act on the RFC1918 range) and perhaps should be permit 172.x.x.x 0.0.0.15

KarstenI · ‎11-30-2022

It shows if this rule acts on IPv4, IPv6 or on both DualStack.

KarstenI · ‎11-28-2022

With two gateways, I assume that you also have two dashboard networks. In this case the APs in the different networks will not mesh. The clients in the “middle” will have a bad time as they could change from one network to the other and each time they receive a new DHCP config and sessions will break.

KarstenI

Karsten Iwen

Community Record

Badges