How a SmartPorts Automation Works
A SmartPorts Automation inspects the incoming traffic on a switch port for user-defined match conditions and applies different configurations to the switch port, depending on which conditions are matched. The configurations to be applied upon a match are defined using SmartPorts Profiles.
A match condition is a combination of Match type and Match criteria. Match type is the kind of information a switch will look into in the traffic received on the port. Supported match types are LLDP system description and MAC address. Match criteria is one or more, comma-separated values to be matched for the selected match type.
Match criteria support the use of * (asterisk) as a wild card. The supported syntaxes for match criteria are:
- A case sensitive string for the LLDP system description value(s), such as Meraki MV32 Cloud Managed Security Camera or Meraki MV*.
MAC address in any of the following formats: aabbccddeeff, aa:bb:cc:dd:ee:ff, aa-bb-cc-dd-ee-ff, aabb.ccdd.eeff. Wildcards can be used with any of the formats for a generic match such as aa:bb:cc*.
An Automation is a sequence of rules, each of which is a collection of one or more match conditions. Match conditions in a rule operate as a logical AND. That is, all conditions in a rule should match for the rule to be considered a match. For this reason, a match type can be used only once per rule. For example, multiple match conditions for LLDP system description cannot be added in a single rule. If there are multiple LLDP system description values, they should be entered as comma-separated values in the match criteria instead. Values provided in the match criteria operate as a logical OR, which means that any one of them being matched will be sufficient for the condition to be considered a match.
A rule, when matched, applies a single profile to the switch port. Each automation allows a default action to be used if no rules are matched. The default action can be used to apply a specific profile on the ports or leave their configuration unmodified.
When an automation is enabled on a switch port, the switch monitors the traffic coming in on the port for a short period of time after the port is enabled or a connection is detected on it. At the end of the monitoring period, the profile mapped to the rule that has been matched is applied to the port. If multiple rules are matched, the rule with the lowest sequence number in the automation is considered as the match.
https://documentation.meraki.com/Switching/MS_-_Switches/Design_and_Configure/Configuration_Guides/P...
I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.
Please, if this post was useful, leave your kudos and mark it as solved.
