About Inderdeep

Inderdeep

@ClusterNet : Check the v1 documents now https://developer.cisco.com/meraki/api-v1/#!get-organization-uplinks-statuses

Inderdeep

@WarrenG : Check this out https://documentation.meraki.com/MR/Encryption_and_Authentication/Cloud_Hosted_Meraki_Authentication For MAC, Check this tread https://community.meraki.com/t5/Wireless-LAN/MR-authentication-with-MAC/m-p/56629

Inderdeep

@UCcert : You know it all ..

Inderdeep

@UCcert : Thank you !

Inderdeep

@MeredithW : Thanks for such an appreciation and Proud moment for me to have been accepted into the Cisco Meraki Community All-Star 2021 cohort.

Inderdeep

@Skysails8080 : first of all, yes LLDP is supported on Meraki Switches https://documentation.meraki.com/General_Administration/Other_Topics/LLDP_Support_on_Cisco_Meraki_Products Secondly, The MS Access Switch utilize LLDP to recognize the VoIP phone connected and retrieve various properties of the phone. QoS on the MS Switch tags specific traffic that is incoming on the desired switch ports and prioritizes traffic which is important for voice traffic due to its sensitivity to latency. https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Configuring_the_MS_Access_Switch_for_Standard_VoIP_Deployments To your point, Voice VLANs and QoS (Quality of Service) to separate voice traffic into its own broadcast domain and tag it for optimal transfer and prioritization.

Inderdeep

@Skysails8080 : I would recommend to check below links https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Verifying_Voice_and_Data_VLAN_tags_with_LLDP_phones

Inderdeep

@LucasMendes : You gets an HTTP status code of 500 with the message "Internal Server Error " as a response for API calls. ... It means that the server encountered an unexpected condition that prevented it from fulfilling the request. This error is usually returned by the server when no other error code is suitable. https://datatracker.ietf.org/doc/html/rfc7231#section-6.6 Check this tread if it helps, I would say its not client issue, Open a Support ticket with Meraki https://community.meraki.com/t5/Developers-APIs/HTTP-500-and-502-Error-Page-not-found-while-using-API-on-a-very/m-p/88763#M3525

Inderdeep

@LucasMendes : I am not able to open this above URL. Can you check this https://developer.cisco.com/meraki/api-v1/#!get-network-insight-application-health-by-time

Inderdeep

@tomiles : https://documentation.meraki.com/General_Administration/Support/Contacting_Support

Inderdeep

@tomiles : You need to correlate your hardware, firmware and features which may triggered with a known issue. I would suggest you to open a Support ticket with Meraki.

Inderdeep

@DarrenOC : Check this out https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/802.11k_and_802.11r_Overview#How_do_802.11k_and_802.11r_help.3F

Inderdeep

@rodrigogrechi : Correct no API for that.

Inderdeep

@LucasMendes : I dont think so there is any API call for that !

Inderdeep

@LucasMendes : Is that what you are talking about ? https://documenter.getpostman.com/view/7928889/SVmsVg6K#f0ae5e46-9b6a-48b2-a1ed-3e9db39c7a50

Inderdeep

@tantony : well i think i saw somewhere that All the IP addresses on our network start with 172.17 and have a 24-bit subnet mask is in the 'reserved' range of IP addresses that is not routable on the public Internet. That may cause issue.

Inderdeep

@tantony : 172.17.X.X/24 subnet which give you valid User IPs ( 172.17.X.1 - 172.17.X.254). I dont think any issue with the IP range

Inderdeep

@ITJosh : Check this guide may be helpful for you https://documentation.meraki.com/MX/Client_VPN/Guided_Client_VPN_Troubleshooting

Inderdeep

@hmc250000 : Check this one https://documentation.meraki.com/MX/NAT_and_Port_Forwarding/Port_Forwarding_and_NAT_Rules_on_the_MX

Inderdeep

@rodrigogrechi : Check if this helps https://dunxd.com/2015/09/24/custom-pie-charts-in-meraki/

Inderdeep

@LucasMendes : Check if this helps https://dunxd.com/2015/09/24/custom-pie-charts-in-meraki/

Inderdeep

@Dunky : Did you check this guide https://documentation.meraki.com/MX/Site-to-site_VPN/Configuring_Site_to_Site_VPN_tunnels_to_Azure_VPN_Gateway

Inderdeep

@klaus_heck : I think you need to use the override option for username and password for ASN https://0x2142.com/meraki-mg-setting-up-merakis-new-lte-gateway/

Inderdeep

@Kamome : Check this out https://documentation.meraki.com/General_Administration/Licensing/Meraki_Licensing_FAQs

Inderdeep

@klaus_heck : Check below To set up the cellular failover connection, follow the steps below: Power off the MX. Swapping/installing SIM cards while the MX is powered on may cause unexpected behavior or errors For the MX67C, connect the antennas for cellular reception. Antennae are pre-attached for the MX68CW Open the SIM tray using the SIM card removal tool included in the box Insert a nano SIM card (4FF size) and close the SIM tray Connect the uplink for the MX device via a wired connection to connect to the Meraki cloud Power on the MX and wait for the MX to show as online in the Meraki dashboard Check with the carrier of choice if an APN needs to be configured. If so, do that from the Meraki Dashboard under Security & SD-WAN > Monitor > Appliance Status > Uplink tab Navigate to Security & SD-WAN > Monitor > Appliance Status > Uplink tab and next to Status, select the edit (pencil) button and then select Enabled. When the cellular uplink is successfully connected, you will be able to see the status on the left hand side of the Appliance Status page and in the Uplink tab. The connection will say Ready when it is successfully connected Test the cellular failover connection by unplugging the wired connection or by using the traceroute tool under Security & SD-WAN > Monitor > Appliance Status in the Tools tab If, after following the steps above, the SIM card is not detected, please confirm with your carrier that the SIM card is active and has data. You will need the ICCID of the SIM card and IMEI of the device to get troubleshooting help from the carrier A list of certified carriers can be found in our MX67 and MX68 Overview and Specifications document Please contact the Meraki Support team if the cellular connection is still not being recognized after following the steps above

Inderdeep

Community Record

Badges