About ww

ww

The vrrp mac is the same for all vlans, i supose thats why it can show a different ip/mac every time you look

ww

Yes https://documentation.meraki.com/General_Administration/Managing_Dashboard_Access/Managing_Dashboard_Administrators_and_Permissions#Adding_a_Network_Admin

ww

Can you take a packet capture on the lan port and see if the device send traffic to your syslog server.

ww

You dont have any ap or switch in this network? Then you can split the combined network, and only combine the networks with active hardware

ww

Are you connected lan2 port?

ww

This explains postman and the meraki postman collection https://developer.cisco.com/meraki/build/meraki-postman-collection-getting-started/

ww

You can. Try first if you can claim the serial to your dashboard. And if the device is not eos https://documentation.meraki.com/General_Administration/Other_Topics/Product_End-of-Life_(EOL)_Policies

ww

On what ports? If you see it on AP ports that have a ssid in bridge mode its expected behavior. (Clients moving from AP to AP)

ww

I have tested ipsk on 27.x and that worked for me. I dont know about 28.x Did you also try with 27.x firmware?

ww

All meraki api are basically nb. Can you give a example what you need?

ww

I had exactly the same on 2 different networks/ orgs. different models-switches and AP's, and tried al different fw. you can try disable secureconnect, wait a few minutes, and enable it again. some more AP's will get authenticated. but some will still not work. i have a supportcase about this same issue.

ww

You can see the uplink decisions if you browse to the spoke network. and go to sdwan > vpn status https://documentation.meraki.com/MX/Monitoring_and_Reporting/SD-WAN_Monitoring#Overview

ww

Try power it off. Bring it near the mr. And power on. Check the ap network if the mv try to connect to the ssid.

ww

Should work for some products. Not for switches f.e. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Meraki_Device_to_Cloud_Connectivity_-_FIPS

ww

Are you sure you are using the template network id? You have seen the error before https://community.meraki.com/t5/Developers-APIs/Cisco-Meraki-API-v1-configure-Template-PSK/m-p/127166#M4961

ww

network_id = 'L_123123123' number = '0' ##number off ssid## response = dashboard.wireless.updateNetworkWirelessSsid( network_id , number , name = 'NAMEOFSSID' , enabled = True, psk = 'HerePSK' )

ww

You can use the 2nd wan port When you are done, set the primary interface to wan2 https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/MX_Load_Balancing_and_Flow_Preferences#Load_Balancing

ww

You bought a used one? The previous owner need to unclaim it. Maybe the seller is not the previews owner.. Not much you can do then.

ww

Meraki mx and ms already send the vlan ip interface as gateway ip by default. So normally you dont need to do that, only if you want another router to be the gateway for that subnet.

ww

Someone who manages your org and has a ip within the configured ip range. (Full admin rights).

ww

That is only for mx. When you want to run a dhcp server for a subnet (static route) not owned by the mx.

ww

there is a ip restriction on org level configured Login IP ranges: Restrict access to Dashboard (including the API) from certain IP addresses. https://documentation.meraki.com/General_Administration/Organizations_and_Networks/Organization_Menu/Organization_Settings#Security_Settings https://documentation.meraki.com/General_Administration/Managing_Dashboard_Access/Locked_Out_of_Dashboard#Recovering_Access_to_Accounts_Protected_by_Login_IP_Range_Restrictions

ww

https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Traffic_and_Bandwidth_Shaping https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Network-Based_Application_Recognition_(NBAR)_integration_with_MR_access_points https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Network-Based_Application_Recognition_(NBAR)_integration#Traffic_shaping_rules

ww

What did you see exactly? On the same vlan arp should just work between clients without interference of the mx.

ww

setup 1 : https://documentation.meraki.com/MX/Site-to-site_VPN/Configuring_Site-to-site_VPN_over_MPLS setup 2 : https://documentation.meraki.com/MX/Deployment_Guides/MPLS_Failover_to_Meraki_Auto_VPN

ww

Community Record

Badges