02-07-2014 12:18 PM
Does Smartport support the 1142 AP and the 3502 AP? It keeps comming up as a Router device - CISCO_ROUTER_EVENT
The 1131 AP work fine.
02-07-2014 04:21 PM
Does Smartport support the 1142 AP and the 3502 AP?
You need to explain a bit more.
02-08-2014 10:02 AM
Using the Smartport built-in macros:
macro auto execute CISCO_WIRELESS_LIGHTWEIGHT_AP_EVENT
macro auto execute CISCO_WIRELESS_AP_EVENT
macro auto execute CISCO_ROUTER_EVENT
When we plug in a 1142 AP, the port is assigned to the correct vlan (240) and the macro description shows "CISCO_WIRELESS_LIGHTWEIGHT_AP_EVENT"
When we plug in a 3502 AP, the port is not assigned to the correct vlan (176) and the macro description shows "CISCO_ROUTER_EVENT"
Here are the macros:
macro auto execute CISCO_WIRELESS_LIGHTWEIGHT_AP_EVENT {
if [[ $LINKUP -eq YES ]]; then
conf t
interface $INTERFACE
macro description $TRIGGER
switchport access vlan 240
switchport mode access
spanning-tree portfast
exit
end
fi
if [[ $LINKUP -eq NO ]]; then
conf t
interface $INTERFACE
no macro description
no switchport access vlan 240
no spanning-tree portfast
if [[ $AUTH_ENABLED -eq NO ]]; then
no switchport mode access
fi
exit
end
fi
}
!
macro auto execute CISCO_WIRELESS_LIGHTWEIGHT_AP_EVENT {
if [[ $LINKUP -eq YES ]]; then
conf t
interface $INTERFACE
macro description $TRIGGER
switchport access vlan 176
switchport mode access
spanning-tree portfast
exit
end
fi
if [[ $LINKUP -eq NO ]]; then
conf t
interface $INTERFACE
no macro description
no switchport access vlan 176
no spanning-tree portfast
if [[ $AUTH_ENABLED -eq NO ]]; then
no switchport mode access
fi
exit
end
fi
}
!
Macro auto execute CISCO_ROUTER_EVENT {
if [[ $LINKUP -eq YES ]]; then
conf t
interface $INTERFACE
macro description $TRIGGER
switchport access vlan $ACCESS_VLAN
switchport mode access
spanning-tree portfast
exit
end
fi
if [[ $LINKUP -eq NO ]]; then
conf t
interface $INTERFACE
no macro description
no switchport access vlan $ACCESS_VLAN
no spanning-tree portfast
if [[ $AUTH_ENABLED -eq NO ]]; then
no switchport mode access
fi
exit
end
fi
}
!
02-08-2014 03:08 PM
Move this thread to the EEM section.
If Joe Clark is not busy, he should be able to help you.
02-09-2014 11:55 PM
ok, how do I move the thread?
02-10-2014 01:28 AM
Upper right-hand corner, under "Action".
02-12-2014 04:50 PM
The CDP platform needs to be AIR-LAP for it to fire that macro. Perhaps these APs identify themselves differently...
02-14-2014 07:04 AM
So what macro trigger do I use?
Here is what is available by typing the command - macro auto execute ?
CISCO_CUSTOM_EVENT
CISCO_DMP_EVENT
CISCO_IPVSC_EVENT
CISCO_LAST_RESORT_EVENT
CISCO_PHONE_EVENT
CISCO_ROUTER_EVENT
CISCO_SWITCH_EVENT
CISCO_WIRELESS_AP_EVENT
CISCO_WIRELESS_LIGHTWEIGHT_AP_EVENT
02-16-2014 02:55 PM
You may have to define your own trigger and a custom profile. What is the platform advertised by this AP?
02-17-2014 08:00 AM
AIR-LAP1131AG-A-K9 - this one works (CISCO_WIRELESS_LIGHTWEIGHT_AP_EVENT)
AIR-LAP1142N-A-K9 - this one does not work
AIR-CAO3502I-A-K9 - this one does not work
02-17-2014 08:07 AM
But what do you see in show cdp neighbor for these APs?
02-17-2014 02:55 PM
I typed the 3502 wrong is should be AIR-CAP3402I-A-K9
This is what I see as the platform (above) when I run "sh cdp n d". If I just type "sh cdp n" I see:
AIR-LAP11 for the AIR-LAP1131AG-A-K9
AIR-LAP11 for the AIR-LAP1142N-A-K9
AIR-CAP35 for the AIR-CAP3502I-A-K9
02-17-2014 03:04 PM
Okay, this is bug CSCtk00846, and it should be fixed in 12.2(55)SE4 (on the switch) with the CISCO_WIRELESS_LIGHTWEIGHT_AP_EVENT macro event. What version of code are you running?
02-17-2014 03:19 PM
We are running 12.2(55)SE3. So, this bug is for both the 1142 and 3502?
02-17-2014 03:22 PM
The fix for this bug should handle both regardless of whether or not they are native lightweight or were converted to lightweight.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide