Meraki

PhilipDAth · ‎Aug 10 2018

Can you ping the AP's IP address from a LAN connected machine?

PhilipDAth · ‎Aug 10 2018

You might need to access the local status page on one of the affected AP's and see why it is reporting that it is not happy. https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page#MR_Series

PhilipDAth · ‎Aug 10 2018

It sounds to me like the MR42Es are powering up okay but can not talk to the Internet. Have you got them in a VLAN that can access the Internet? Does that VLAN have DHCP running on it? Have you enable any security features like port security or 802.1x that might be stopping it working? Can you plug a PC into these ports and get to the Internet ok?

PhilipDAth · ‎Aug 9 2018

Correct, the MX84 simply bridges its LAN ports. It looks to me like you should have a working setup now.

PhilipDAth · ‎Aug 8 2018

You wont be able to terminate an OpenVPN client connection directly on an MX. OpenVPN is an SSL based VPN solution. You would need to setup your own OpenVPN server behind the MX to get this to work. If you can wait to the end of the year I suspect you might see an extra client CPN option appear.

PhilipDAth · ‎Aug 8 2018

The vMX can only have one interface. The decrypted traffic goes to the default gateway - which is usually the VPC.

PhilipDAth · ‎Aug 8 2018

Put the ISP traffic in one VLAN and present it to the WAN ports, and management traffic in another VLAN and present it to the LAN ports.

PhilipDAth · ‎Aug 7 2018

I'm guessing this is for a security purpose, and maybe you are familiar with the Cisco Country of Origin tool used to validate this. There is no such Meraki tool.

PhilipDAth · ‎Aug 7 2018

Port 1 (the ISP links) does not need to be tagged. Just put it into a VLAN and present that to the WAN ports of the MX.

PhilipDAth · ‎Aug 7 2018

The WAN interfaces each need their own IP address, and if there is a common subnet, you can also enable a Virtual IP. Using a virtual IP on the WAN interfaces is an optional configuration. https://documentation.meraki.com/MX-Z/Other_Topics/Warm_Spare#Virtual_IP

PhilipDAth · ‎Aug 7 2018

The WAN ports can be tagged, but can only belong to a single VLAN. You configure this via the local status page. https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page#MX-Z_Series_with_Multiple_Dedicated_WAN_Links The MX will use its WAN IP to talk to the Meraki cloud, and does not need a seperate management network. If you have other devices needing to talk to the Internet that are attached to VLAN11, then you can connect those via the LAN ports and configure a VLAN11 there. Note this would be using private IP address space. https://documentation.meraki.com/MX-Z/Networks_and_Routing/Configuring_VLANs_on_the_MX_Security_Appliance

PhilipDAth · ‎Aug 6 2018

Another option you could consider changing is the RX-SOP threshold. This allows you to tell the access point to ignore weak signals (such as those driving by). https://documentation.meraki.com/MR/Radio_Settings/RF_Profiles#RX-SOP You could either get someone to come in who can measure it for you, or maybe get some machines placed just a little further away than where you want coverage, and adjust RX-SOP until they just get chopped off.

PhilipDAth · ‎Aug 6 2018

Thank you for my latest swag @CarolineS. I think I'll use these in my vehicle. I have several charging cords, but someone always asks for one I don't have, and this will solve that problem.

PhilipDAth · ‎Aug 6 2018

It isn't written very well. The MX's use VRRP, which in essence is a virtual IP. The IP address is always serviced by the primary MX. The spare takes over the VRRP IP address if the primary fails.

PhilipDAth · ‎Aug 5 2018

Any chance you normally connect to 5Ghz and are now connecting to 2.4Ghz? Any traffic shaping policies that have been applied?

PhilipDAth · ‎Aug 1 2018

The support number for the UK is: +44 20 38 08 7003 Get the serial number off the back of one of the devices before you call. I would be tempted to find out if they will give you the email address of any administrator on the account. Then you can setup that email address, do a password reset, and get access. Otherwise you have to go through a longer legal proof process. When Meraki licencing runs out the devices stop working. So it is critical you maintain current licencing.

PhilipDAth · ‎Aug 1 2018

What country are you in and I'll look up the number for support.

PhilipDAth · ‎Aug 1 2018

You can probably guess the persons email address based on the naming convention you use for email ...

PhilipDAth · ‎Aug 1 2018

Do a password reset on their email address and see if you get anything back.

PhilipDAth · ‎Aug 1 2018

You can't.

PhilipDAth · ‎Aug 1 2018

Thank you everyone. Just one more month to go. Hopefully I can keep it up.

PhilipDAth · ‎Jul 31 2018

It has no impact on the uplink interface.

PhilipDAth · ‎Jul 31 2018

Yes, turn vlans on. All interfaces on the MX will be trunk interfaces. You'll probably want to change some of them to access interfaces in a specific VLAN.

PhilipDAth · ‎Jul 31 2018

1. Typically in this case you create a VLAN, and plug the MPLS into that VLAN. NAT is not done between VLANS. This guide talks about configuring MPLS failover to AutoVPN. If you ignore the failover and AutoVPN bits, the rest applies to your case. https://documentation.meraki.com/MX-Z/Deployment_Guides/MPLS_Failover_to_Meraki_Auto_VPN 2. The MX has to be online before you can configure it. So frequently you have to use the local status page to do this. Once the MX is online you can make some changes to the WAN interfaces through the dashboard - but be careful not to cut yourself off.

PhilipDAth · ‎Jul 31 2018

That is correct.

About PhilipDAth

PhilipDAth

Philip D'Ath

Community Record

Badges