Setting power inline static during shell trigged macro resets the port

[registry]

We have many Meraki accespoints running in "low power mode" (Meraki MR44). The accesspoints are connected to POE switches like 1000 or 9200L or 3650 etc.  Booting the AP sometimes resolves the problem, sometimes not.  The FIX for this problem is to put the interface in static power mode. Applying the command "power inline static" or "power inline static max 30000".  Now...

We let the Cisco ISE start a shell trigger macro in the switch (Auto smartport)  to set the Meraki AP port in trunk mode with a specific vlan depending on location. This works really well:

macro auto execute meraki-macro {
if [[ $LINKUP == YES ]]
then conf t
default interface $INTERFACE
interface $INTERFACE
macro description $TRIGGER
description ** Meraki **
switchport trunk native vlan 3
switchport mode trunk
exit
fi

If I add "power inline static" to the script, the port resets during execution....and start all over again and again in a endless loop. 

%AUTOSMARTPORT-5-INSERT: Device detected on interface GigabitEthernet1/0/1, executed meraki-macro
Oct 23 09:11:30.191: %SPANTREE-2-ROOTGUARD_CONFIG_CHANGE: Root guard disabled on port GigabitEthernet1/0/1.
Oct 23 09:11:30.449: %SYS-5-CONFIG_I: Configured from console by tty17

Oct 23 09:11:30.663: %ILPOWER-7-DETECT: Interface Gi1/0/1: Power Device detected: IEEE PD
Oct 23 09:11:31.214: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/1: Power granted
Oct 23 09:11:31.336: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to down
Oct 23 09:11:32.428: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down
Oct 23 09:11:32.625: %SYS-5-CONFIG_I: Configured from console by tty17
Oct 23 09:11:32.626: %AUTOSMARTPORT-5-REMOVE: Device removed from interface GigabitEthernet1/0/1, executed meraki-macro to remove the configuration

Oct 23 09:11:32.770: %ILPOWER-7-DETECT: Interface Gi1/0/1: Power Device detected: IEEE PD
Oct 23 09:11:34.121: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/1: Power granted
Oct 23 09:11:37.098: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up
Oct 23 09:11:38.105: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up
Oct 23 09:11:57.653: %DOT1X-5-FAIL: Authentication failed for client (a846.9d1a.94cb) on Interface Gi1/0/1 AuditSessionID 0A01118200000012003413B8
Oct 23 09:11:57.675: Applying command... 'no spanning-tree bpduguard enable ' at Gi1/0/1
Oct 23 09:11:57.678: %AUTOSMARTPORT-5-INSERT: Device detected on interface GigabitEthernet1/0/1, executed meraki-macro
Oct 23 09:11:57.715: %SPANTREE-2-ROOTGUARD_CONFIG_CHANGE: Root guard disabled on port GigabitEthernet1/0/1.
Oct 23 09:11:57.899: %SYS-5-CONFIG_I: Configured from console by tty17

Oct 23 09:11:58.345: %ILPOWER-7-DETECT: Interface Gi1/0/1: Power Device detected: IEEE PD
Oct 23 09:11:58.861: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to down
Oct 23 09:11:58.861: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/1: Power granted
Oct 23 09:11:59.895: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down
Oct 23 09:12:00.062: %SYS-5-CONFIG_I: Configured from console by tty17
Oct 23 09:12:00.062: %AUTOSMARTPORT-5-REMOVE: Device removed from interface GigabitEthernet1/0/1, executed meraki-macro to remove the configuration

Oct 23 09:12:00.211: %ILPOWER-7-DETECT: Interface Gi1/0/1: Power Device detected: IEEE PD
Oct 23 09:12:01.090: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/1: Power granted
Oct 23 09:12:04.684: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up
Oct 23 09:12:05.684: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up

Configuring the ports manually for APs is not an option. We tried all other recommendations. Meraki asked us to upgrade the switches - we did.  No change.  It looks like the lldp (we have this configured)  fails to negotiate power. Since the consumption is around 8 watt, the Meraki AP wants to allocate 30 watt to go into ".at" power standard.  Since the consumption is lower - the AP renegotiate a lower power standard.  Then goes into low power mode. This looks like a bug to me. 

So all I really want to do is to apply a power command without the switch resetting the port.  

All versions are latest stable release to present day.

Regards / Fred

[marce1000]

 -Advising to post in https://community.meraki.com/t5/Wireless/bd-p/wireless-lan

 too,

 M.

[jagan.chowdam]

https://documentation.meraki.com/MR/Other_Topics/Low_Power_Mode_on_Cisco_Switches

Jagan Chowdam

[Rich R]

Hmmm tricky situation. 

I'd say this is a Meraki bug but convincing them to fix that now isn't going to go anywhere so what to do instead ...
power inline static config is always going to reset the port - you can't avoid that.
Is there some way to dampen the macro so that it doesn't go into the endless loop?
Otherwise fixing the root issue is the best option so that you don't need to set static power at all which would avoid that problem altogether so I would try:

- Disable CDP so that you only have LLDP configured on the port.  Having both enabled can cause unexpected conflicts/interactions.
- Try spanning-tree portfast trunk / spanning-tree portfast edge trunk on the port (we found this helped with some Cisco APs)
- spanning-tree bpduguard disable (your logs show you're doing this already) but also "spanning-tree bpdufilter enable" - we got this as a solution from TAC for problems with Cisco APs.