Meraki

RaphaelL · ‎Mar 15 2023

Kind of a big deal is the title next to @alemabrahao username. His response is indeed : For sure.

RaphaelL · ‎Mar 15 2023

I was able to capture it. I'm not an expert on that field at all. But it seems you were right with the M2. I can see a couple a 'retry' then finaly M2,M4 and the client is auth again : Rollbacking to MR28.X fixes the issue. Weird. I will update my ticket

RaphaelL · ‎Mar 15 2023

No. Currently you have to go network per network to retrieve the clients info. I'm not aware of any other endpoint that would be more efficient.

RaphaelL · ‎Mar 15 2023

When you click on MG 3.100 and you go back to the changelog of MG 3.0 , they are different from the actual changelog reported yesterday : Other MG 3.0: First beta image! 🎉 Cellular WAN Connectivity NAT and Passthrough modes supported IPv6 Support (Firmware only) Dual SIM Support - SIM slot selection via dashboard/LSP Auto SIM failover - if SIM1 is not present, auto switch to SIM2 ZTP via auto APN detection and multi-APN retry Custom APN setting via dashboard/LSP Safemode for troubleshooting Known Issues DHCP section is not disabled in passthrough mode Licensing is not enforced properly on Dashboard. Device shows up as a "wireless AP" on the licensing page Enabling/disabling SIM PIN/PUK currently unavailable Limitation If SIM1 is configured as Primary, Dashboard will not show the details of SIM2 until SIM2 is made active. If SIM2 is configured as Primary, Dashboard will likely have the details of SIM1 Changing carrier provided MTU is not available. ECO is available to change MTU only in passthrough mode 🤔 EDIT: The one and only @cmr had already spotted the issue under : A new candidate cellularGateway firmware is now available on Tue, 14 Mar 2023.

RaphaelL · ‎Mar 14 2023

Makes sense that Meraki would re-use codes from Cisco's WLC. Those '103' started to appear out of nowhere.

RaphaelL · ‎Mar 14 2023

That's what I said. Logs are Auth/Assoc So I was only focusing on section 9.4.1.7 ( de-auth ) , but my codes are in the section 9.4.1.9 ( auth ).

RaphaelL · ‎Mar 14 2023

Edit : The full list of specified 802.11 reason codes can be found in IEEE's documentation in this article (requires account) under "Table 9-49—Reason codes" in section "9.4.1.7 Reason Code field". So I was only focusing on section 9.4.1.7 ( de-auth ) , but my codes are in the section 9.4.1.9 ( auth ). My first question is still valid.

RaphaelL · ‎Mar 14 2023

Source ?

RaphaelL · ‎Mar 14 2023

Hi , Does anyone know if Meraki is disclosing it's proprietary reason codes ? 802.11 reason codes are already available through the IEEE ( as mentioned in the documentation below ) https://documentation.meraki.com/MR/Monitoring_and_Reporting/Common_Wireless_Event_Log_Messages Here is an example of a reason code from Meraki : Also , I think that Meraki is not using the IEEE reason code description/id correctly ... 53 = MESH-MAX-PEERS : The mesh STA has reached the supported maximum number of peer mesh STAs 49 = REASON_INVALID_PMKID : Invalid pairwise master key identifier (PMKID) 8: LEAVING_NETWORK_DISASSOC : Disassociated because sending STA is leaving (or has left) BSS Or Am I misinterpreting the IEEE documents ? Edit :Yes I was. Thanks ,

RaphaelL · ‎Mar 10 2023

Was the MX sending the TCP-reset ? It would pretty easy to determine with the IP TTL. Take the TTL of the SYN-ACK from the 443 conversation and compare with the TTL of the TCP reset.

RaphaelL · ‎Mar 10 2023

Bottom is the original SYN ( on my computer , before VPN tunnel ) , Top (inside the VPN tunnel ) is the SYN after MSS clamping.

RaphaelL · ‎Mar 10 2023

So TCP. Have you tried to capture on the VPN tunnel to see the 3-way handshake ? Do you see any fragments on the other end ? MTU shouldn't be an issue since the MSS is clamped.

RaphaelL · ‎Mar 10 2023

Hi , Is it TCP based or else ? https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Troubleshooting_MTU_Issues The MX will clamp the TCP-MSS

RaphaelL · ‎Mar 9 2023

I'm hiting 740/800 with MX18.106 which is kinda nice but really over the specs !

RaphaelL · ‎Mar 9 2023

It won't block intra-vlan traffic ( L2 ). Simply L3 trafic.

RaphaelL · ‎Mar 9 2023

No you can't. Support can tell you if the device has rebooted or not.

RaphaelL · ‎Mar 9 2023

I'm curious about this. non-existent device on a non-existent network Is it devices that were recently RMA'd or removed from a network ? On my largest Org I would expect to find this also , but I could'nt.

RaphaelL · ‎Mar 9 2023

Hi , I'm using a MX68CW at home. My wan speeds are 1G/1G on a fiber link. I only have a couple vlans and no security features at all , so I should be maxed out by the Stateful firewall throughput of 600Mbps ( which is probably a safe value determined by Meraki and not really the limit of the hardware ) However , when doing multiple speed tests I can achieve speeds way higher than that : Shaping 600/600 Shaping 599/599 ( maximum - 1 ) What is the highest value that you guys are hitting with a MX68 ? Also the maximum of the trafic shapping slider is 600/600. Which I guess that if the slider is set to the maximum , it really means = unlimited and not a capped value like the dashboard shows. That behavior is not mentioned in https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/SD-WAN_and_Traffic_Shaping Running MX.18.106. Same behavior seen on MX16.16 Thanks !

RaphaelL · ‎Mar 8 2023

You upgraded from what version out of curiosity ?

RaphaelL · ‎Mar 7 2023

Received mine today ! Huge thanks to @AmyReyes

RaphaelL · ‎Mar 6 2023

After reviewing #3 it is present @ https://developer.cisco.com/meraki/api-v1/#!get-device-appliance-performance but I can't use the search bar to find it...

RaphaelL · ‎Mar 6 2023

Hi , https://documentation.meraki.com/MX/Monitoring_and_Reporting/Device_Utilization 3 Things concerning Device utilization 1- Reading Device Utilization via API MX device utilization can be retrieved using the API as well. This section refers a link to the API v0. It should be updated to v1. 2- The Performance API call returns latest performance score average from within the last one hour. e.g. If the Performance API is queried at 21:00, the API will return the performance score average from 20:00. Is it really per hour ? My stats says otherwise : In 1 hour , I noticed around 4 updates to the score. 3- Can't find any reference to /devices/{serial}/appliance/performance in the Developper Hub documentation , but the endpoint is present in the OpenApi Spec. "/devices/{serial}/appliance/performance": { "get": { "description": "Return the performance score for a single MX. Only primary MX devices supported. If no data is available, a 204 error code is returned.", "operationId": "getDeviceAppliancePerformance", "parameters": [ { "name": "serial", "in": "path", "type": "string", "required": true } ], "responses": { "200": { "description": "Successful operation", "schema": { "type": "object" }, "examples": { "application/json": { "perfScore": 10 } } } }, "summary": "Return the performance score for a single MX", "tags": [ "appliance", "monitor", "performance" ] } }, I have no idea if I should have opened a case about those points. Thanks ,

RaphaelL · ‎Mar 3 2023

I misread the documentation. I think you have to do /networks/{networkId}/sm/devices?fields[]=ownerEmail or /networks/{networkId}/sm/devices?fields=ownerEmail Then you could filter the json received with the selected Email. If that makes sense

RaphaelL · ‎Mar 3 2023

I don't have anything SM related to test , but according to the API doc it might be : https://developer.cisco.com/meraki/api-latest/#!get-network-sm-devices /networks/{networkId}/sm/devices?ownerEmail="john.doe@hotmail.com"

RaphaelL · ‎Mar 3 2023

Hi , The section "Packets" from : https://documentation.meraki.com/MS/Monitoring_and_Reporting/Switch_Port_View should now include 'Topology changes' This section displays detailed packet information in relation to the selected switch port, including the total, sent, received and rate values for Total, Broadcast, and Multicast traffic. This table will also display counters for CRC align errors, Fragments, and Collisions. An example is provided in figure 3 below. Suggestion : This section displays detailed packet information in relation to the selected switch port, including the total, sent, received and rate values for Total, Broadcast, and Multicast traffic. This table will also display counters for CRC align errors, Fragments, Collisions and Topology Changes. An example is provided in figure 3 below. And update the corresponding screenshot 🙂 Thanks !

About RaphaelL

RaphaelL

Raphael Letourneau

Community Record

Badges