cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1206
Views
0
Helpful
3
Replies

AutoSmartport Macro not working reliable (CAT9200, CAT9300)

Hello everybody,

I just wanted to share an experience we made with auto-smartport macro. Maybe someone has made similar experience or has an idea. 

Our Cisco ISE environment is profiling our Meraki AP´s and sending a Radius message to apply Auto-Smartport Macro.

With only a few AP´s connected it works great. 

But when connecting multiple AP´s (for example during reload of a switch) the macro is not executed reliable on the switch.

Some ports are getting configured correct, on other ports the macro seems to break:

Here is the Macro that is defined on the switch:

!
macro auto execute config-meraki-ap {
if [[ $LINKUP == YES ]]
then conf t
default interface $INTERFACE
interface $INTERFACE
macro description $TRIGGER
source template MERAKI-AP-WIFI-2.0
device-tracking attach-policy DEV-TRACKING_UPLINK
ip flow monitor FNF-STANDARD-MONITOR input
snmp trap link-status
snmp trap mac-notification change added
snmp trap mac-notification change removed
exit
fi
if [[ $LINKUP == NO ]]
then conf t
default interface $INTERFACE
interface $INTERFACE
source template STANDARD-PORT
device-tracking attach-policy DEV-TRACKING
ip flow monitor FNF-STANDARD-MONITOR input
exit
fi
}

 

Here is a good example how it looks when it fails completly:

AP´s are connected to the first 12 ports of the switch. 

steffenbodensohnheraeuscom_0-1729838995410.png

We are already in contact with Cisco TAC.

This issue happens on several IOS Versions we tested in our LAB. 

(17.3.4, 17.9.3, 17.12,...)

 

Best regards,

Steffen

 

 

 

 

3 Replies 3

sgu303
Level 1
Level 1

Hi, Were you able resolve this issue with TAC? We face the same issue

 

Yes, there is a related bug ID: CSCwm87264.

According to Cisco, the issue was caused by the execution of macro commands and BPDU Guard when applied to a range of ports. They provided us with a private image and informed us that the fix is planned for IOS versions 17.12 and 17.15.

We reached out a few weeks ago to ask whether the fix has already been included in any of the newer official IOS-XE releases, but we have not received any feedback so far.

Hi Steffen

Alright, thanks for your answer. Unfortunately the bug is private so I can't view it. But good to hear that they know of the issue and fixing it. We also have the issue on IOS devices. Do you know if it will also be fixed there and if so in which release?