These rules are outbound rules, not inbound, so if the traffic is not blocked at the exit, the response will obviously not be blocked. ... View more

Check the Cloud Data Retention Policies:     https://documentation.meraki.com/General_Administration/Privacy_and_Security/Cloud_Data_Retention_Policies ... View more

Are you asking for help for your homework?   How about you tell us what you think the correct answer is, and why, and we take it from there. ... View more

the output you see is taken from the API response in the Postman application. ... View more

I will contact Meraki TAC ... View more

This document says it starts with 88:15 but I want to find the VMAC of my switch. will there be the same Virtual Mac for all VLANs or will each VLAN have a separate VMAC? ... View more

A defined ACL will apply to all switches within the network. All traffic that goes through the switch is evaluated by the ACL before being forwarded. That includes L2 traffic between ports on the same switch.    The following links provide more in depth information on this. https://documentation.meraki.com/MS/Layer_3_Switching/Configuring_ACLs https://documentation.meraki.com/MS/Other_Topics/Switch_ACL_Operation ... View more

That's because Meraki thinks that it is a normal condition. You probably don't have BPDU guard on that port , hence you don't have any warnings.    In that case , I don't think you will be able to spot those via the API. ... View more

To clarify this a bit further, you can have a LAG of ports that span across different switches within a physical stack. ... View more

Problem Description:  Wierd L2 BUM traffic Behaviour   SW - MS 15.21.1 HW - MS250-24P   Topology :                                  Interface 3                                          |                                          | L2 Vlan 100 Interface 1 -----------Switch MS 250----------- Interface 2                                         |                                         |                                    Interface 4   All ports are part of VLAN 100(access port), Nothing else is configured on the switch like storm control. On all ports, the Servers are connected which can capture the packets.   This is my lab device hence there is no production traffic or any other traffic load on the switch.   Summary :   When we send broadcast traffic from Interface 1, It is received on some of the interfaces not all(like sometimes I see the broadcast packet received on Interface 2 or 3 or 4 sometime 3 and 4). I have a packet capture setup to see on what interface I receive the broadcast.   Packet Test:   Injected packet from interface 1 -    mac_src aa:aa:aa:aa:aa:10 mac_dst ff:ff:ff:ff:ff:ff eth_type 0x800 ip_version 4 vlan_vid untagged ipv4_src 101.10.10.10 ipv4_dst 101.10.10.100  ip_proto 6   I received the above packet on interface 3 only(validated through captures setup on all connected servers.).    At the same time, I took the combined captures on the Dashboard for interfaces 2,3,4. it also shows one packet. Ideally, it should show three broadcast packets as the captures are for combined interfaces 2,3,4.   I just want to confirm if you see this behaviour in your LAB for the MS switch.   Regards, Pavan Pawar ... View more