<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Setting power inline static during shell trigged macro resets the in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/setting-power-inline-static-during-shell-trigged-macro-resets/m-p/5214410#M276920</link>
    <description>&lt;P&gt;Hmmm tricky situation.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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 ...&lt;BR /&gt;power inline static config is always going to reset the port - you can't avoid that.&lt;BR /&gt;Is there some way to dampen the macro so that it doesn't go into the endless loop?&lt;BR /&gt;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&amp;nbsp;&lt;SPAN&gt;I would try:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;- Disable CDP so that you only have LLDP configured on the port.&amp;nbsp; Having both enabled can cause unexpected conflicts/interactions.&lt;BR /&gt;- Try&amp;nbsp;&lt;!--StartFragment --&gt;&lt;SPAN class="cf0"&gt;spanning-tree portfast trunk /&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="cf0"&gt;spanning-tree portfast edge trunk on the port (we found this helped with some Cisco APs)&lt;BR /&gt;-&amp;nbsp;&lt;!--StartFragment --&gt;spanning-tree bpduguard disable (your logs show you're doing this already) but also "&lt;!--StartFragment --&gt;spanning-tree bpdufilter enable" - we got this as a solution from TAC for problems with Cisco APs.&lt;!--EndFragment --&gt;&lt;!--EndFragment --&gt;&lt;/SPAN&gt;&lt;!--EndFragment --&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 24 Oct 2024 12:21:12 GMT</pubDate>
    <dc:creator>Rich R</dc:creator>
    <dc:date>2024-10-24T12:21:12Z</dc:date>
    <item>
      <title>Setting power inline static during shell trigged macro resets the port</title>
      <link>https://community.cisco.com/t5/wireless/setting-power-inline-static-during-shell-trigged-macro-resets/m-p/5213475#M276829</link>
      <description>&lt;P&gt;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.&amp;nbsp; Booting the AP sometimes resolves the problem, sometimes not.&amp;nbsp; 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".&amp;nbsp; Now...&lt;/P&gt;&lt;P&gt;We let the Cisco ISE start a shell trigger macro in the switch (Auto smartport)&amp;nbsp; to set the Meraki AP port in trunk mode with a specific vlan depending on location. This works really well:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;macro auto execute meraki-macro {&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;if [[ $LINKUP == YES ]]&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;then conf t&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;default interface $INTERFACE&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;interface $INTERFACE&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;macro description $TRIGGER&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;description ** Meraki **&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;switchport trunk native vlan 3&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;switchport mode trunk&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;exit&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;fi&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;%AUTOSMARTPORT-5-INSERT: Device detected on interface GigabitEthernet1/0/1, executed meraki-macro&lt;BR /&gt;Oct 23 09:11:30.191: %SPANTREE-2-ROOTGUARD_CONFIG_CHANGE: Root guard disabled on port GigabitEthernet1/0/1.&lt;BR /&gt;Oct 23 09:11:30.449: %SYS-5-CONFIG_I: Configured from console by tty17&lt;/P&gt;&lt;P&gt;Oct 23 09:11:30.663: %ILPOWER-7-DETECT: Interface Gi1/0/1: Power Device detected: IEEE PD&lt;BR /&gt;Oct 23 09:11:31.214: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/1: Power granted&lt;BR /&gt;Oct 23 09:11:31.336: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to down&lt;BR /&gt;Oct 23 09:11:32.428: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down&lt;BR /&gt;Oct 23 09:11:32.625: %SYS-5-CONFIG_I: Configured from console by tty17&lt;BR /&gt;Oct 23 09:11:32.626: %AUTOSMARTPORT-5-REMOVE: Device removed from interface GigabitEthernet1/0/1, executed meraki-macro to remove the configuration&lt;/P&gt;&lt;P&gt;Oct 23 09:11:32.770: %ILPOWER-7-DETECT: Interface Gi1/0/1: Power Device detected: IEEE PD&lt;BR /&gt;Oct 23 09:11:34.121: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/1: Power granted&lt;BR /&gt;Oct 23 09:11:37.098: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up&lt;BR /&gt;Oct 23 09:11:38.105: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up&lt;BR /&gt;Oct 23 09:11:57.653: %DOT1X-5-FAIL: Authentication failed for client (a846.9d1a.94cb) on Interface Gi1/0/1 AuditSessionID 0A01118200000012003413B8&lt;BR /&gt;Oct 23 09:11:57.675: Applying command... 'no spanning-tree bpduguard enable ' at Gi1/0/1&lt;BR /&gt;Oct 23 09:11:57.678: %AUTOSMARTPORT-5-INSERT: Device detected on interface GigabitEthernet1/0/1, executed meraki-macro&lt;BR /&gt;Oct 23 09:11:57.715: %SPANTREE-2-ROOTGUARD_CONFIG_CHANGE: Root guard disabled on port GigabitEthernet1/0/1.&lt;BR /&gt;Oct 23 09:11:57.899: %SYS-5-CONFIG_I: Configured from console by tty17&lt;/P&gt;&lt;P&gt;Oct 23 09:11:58.345: %ILPOWER-7-DETECT: Interface Gi1/0/1: Power Device detected: IEEE PD&lt;BR /&gt;Oct 23 09:11:58.861: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to down&lt;BR /&gt;Oct 23 09:11:58.861: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/1: Power granted&lt;BR /&gt;Oct 23 09:11:59.895: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down&lt;BR /&gt;Oct 23 09:12:00.062: %SYS-5-CONFIG_I: Configured from console by tty17&lt;BR /&gt;Oct 23 09:12:00.062: %AUTOSMARTPORT-5-REMOVE: Device removed from interface GigabitEthernet1/0/1, executed meraki-macro to remove the configuration&lt;/P&gt;&lt;P&gt;Oct 23 09:12:00.211: %ILPOWER-7-DETECT: Interface Gi1/0/1: Power Device detected: IEEE PD&lt;BR /&gt;Oct 23 09:12:01.090: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/1: Power granted&lt;BR /&gt;Oct 23 09:12:04.684: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up&lt;BR /&gt;Oct 23 09:12:05.684: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Configuring the ports manually for APs is not an option. We tried all other recommendations. Meraki asked us to upgrade the switches - we did.&amp;nbsp; No change.&amp;nbsp; It looks like the lldp (we have this configured)&amp;nbsp; 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.&amp;nbsp; Since the consumption is lower - the AP renegotiate a lower power standard.&amp;nbsp; Then goes into low power mode. This looks like a bug to me.&amp;nbsp;&lt;/P&gt;&lt;P&gt;So all I really want to do is to apply a power command without the switch resetting the port.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All versions are latest stable release to present day.&lt;/P&gt;&lt;P&gt;Regards / Fred&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2024 08:39:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/setting-power-inline-static-during-shell-trigged-macro-resets/m-p/5213475#M276829</guid>
      <dc:creator>registry</dc:creator>
      <dc:date>2024-10-23T08:39:11Z</dc:date>
    </item>
    <item>
      <title>Re: Setting power inline static during shell trigged macro resets the</title>
      <link>https://community.cisco.com/t5/wireless/setting-power-inline-static-during-shell-trigged-macro-resets/m-p/5213506#M276831</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;-Advising to post in&amp;nbsp;&lt;A href="https://community.meraki.com/t5/Wireless/bd-p/wireless-lan" target="_blank"&gt;https://community.meraki.com/t5/Wireless/bd-p/wireless-lan&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;too,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2024 09:13:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/setting-power-inline-static-during-shell-trigged-macro-resets/m-p/5213506#M276831</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-10-23T09:13:29Z</dc:date>
    </item>
    <item>
      <title>Re: Setting power inline static during shell trigged macro resets the</title>
      <link>https://community.cisco.com/t5/wireless/setting-power-inline-static-during-shell-trigged-macro-resets/m-p/5213691#M276851</link>
      <description>&lt;P&gt;&lt;A href="https://documentation.meraki.com/MR/Other_Topics/Low_Power_Mode_on_Cisco_Switches" target="_blank"&gt;https://documentation.meraki.com/MR/Other_Topics/Low_Power_Mode_on_Cisco_Switches&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Jagan Chowdam&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2024 13:48:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/setting-power-inline-static-during-shell-trigged-macro-resets/m-p/5213691#M276851</guid>
      <dc:creator>jagan.chowdam</dc:creator>
      <dc:date>2024-10-23T13:48:09Z</dc:date>
    </item>
    <item>
      <title>Re: Setting power inline static during shell trigged macro resets the</title>
      <link>https://community.cisco.com/t5/wireless/setting-power-inline-static-during-shell-trigged-macro-resets/m-p/5214410#M276920</link>
      <description>&lt;P&gt;Hmmm tricky situation.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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 ...&lt;BR /&gt;power inline static config is always going to reset the port - you can't avoid that.&lt;BR /&gt;Is there some way to dampen the macro so that it doesn't go into the endless loop?&lt;BR /&gt;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&amp;nbsp;&lt;SPAN&gt;I would try:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;- Disable CDP so that you only have LLDP configured on the port.&amp;nbsp; Having both enabled can cause unexpected conflicts/interactions.&lt;BR /&gt;- Try&amp;nbsp;&lt;!--StartFragment --&gt;&lt;SPAN class="cf0"&gt;spanning-tree portfast trunk /&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="cf0"&gt;spanning-tree portfast edge trunk on the port (we found this helped with some Cisco APs)&lt;BR /&gt;-&amp;nbsp;&lt;!--StartFragment --&gt;spanning-tree bpduguard disable (your logs show you're doing this already) but also "&lt;!--StartFragment --&gt;spanning-tree bpdufilter enable" - we got this as a solution from TAC for problems with Cisco APs.&lt;!--EndFragment --&gt;&lt;!--EndFragment --&gt;&lt;/SPAN&gt;&lt;!--EndFragment --&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2024 12:21:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/setting-power-inline-static-during-shell-trigged-macro-resets/m-p/5214410#M276920</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2024-10-24T12:21:12Z</dc:date>
    </item>
  </channel>
</rss>

