Hi!

mmccallebaut · ‎04-11-2016

We want to use auto smartport for detecting the connection of AIR-CAP2702I-E-K9 devices in order to change the values on the interface (access-vlan number , ..) on a WS-C2960X-24PS-L switch. This was tested in a POC environment with three AIR-CAP2702I-E-K9 devices and it worked fine.

Now we installed a WS-C2960X-24PS-L switch and connected again 3 AIR-CAP2702I-E-K9 devices.

The triggering was correctly done on one interface but didn't succeed on two other interfaces ???

I try to figure it out why but can't find a plausible explanation. The CDP neighbor command doesn't show any differences:

(1/0/7 = OK ; 1/0/9 and 1/0/11 = NOK -> remark: we manually changed the access vlan on the NOK links):

C2960X#sho cdp ne gig 1/0/7 det
-------------------------
Device ID: AP1010047969A1
Entry address(es):
IP address: 10.46.85.36
IPv6 address: FE80::72E4:22FF:FE9F:F704 (link-local)
Platform: cisco AIR-CAP2702I-E-K9, Capabilities: Trans-Bridge Source-Route-Bridge IGMP
Interface: GigabitEthernet1/0/7, Port ID (outgoing port): GigabitEthernet0
Holdtime : 141 sec

Version :
Cisco IOS Software, C2700 Software (AP3G2-K9W8-M), Version 15.3(3)JA1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 19-Dec-14 11:20 by prod_rel_team

advertisement version: 2
Duplex: full
Power drawn: 16.800 Watts
Power request id: 59335, Power management id: 2
Power request levels are:16800 15400 13000 0 0
Management address(es):
IP address: 10.46.85.36

Total cdp entries displayed : 1

C2960X#sho cdp ne gig 1/0/9 det
-------------------------
Device ID: AP1010047969A2
Entry address(es):
IP address: 10.46.85.37
IPv6 address: FE80::5AAC:78FF:FEBB:1C54 (link-local)
Platform: cisco AIR-CAP2702I-E-K9, Capabilities: Trans-Bridge Source-Route-Bridge IGMP
Interface: GigabitEthernet1/0/9, Port ID (outgoing port): GigabitEthernet0
Holdtime : 141 sec

Version :
Cisco IOS Software, C2700 Software (AP3G2-K9W8-M), Version 15.3(3)JA1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 19-Dec-14 11:20 by prod_rel_team

advertisement version: 2
Duplex: full
Power drawn: 16.800 Watts
Power request id: 52368, Power management id: 2
Power request levels are:16800 15400 13000 0 0
Management address(es):
IP address: 10.46.85.37

Total cdp entries displayed : 1

The only difference we detect is in the device classifier:

MAC_Address Port_Id Profile Name Device Name
============== ========== =============================== =======================
70e4.229f.f704 Gi1/0/7 Cisco-AIR-LAP cisco AIR-CAP2702I-E-K9
58ac.78b9.9610 Gi1/0/11 Un-Classified Device cisco AIR-CAP2702I-E-K9
58ac.78bb.1c54 Gi1/0/9 Un-Classified Device cisco AIR-CAP2702I-E-K9
========================================================================

Here you see that the profile name is "Un-Classified Device" for the none-working interfaces.(Device name is the same)

The switch is running the latest IOS c2960x-universalk9-mz.152-4.E1.bin.

Can anybody help me on this subject please?

Thanks in advance,

Best regards

Mike

mmccallebaut · ‎04-14-2016

Problem is MAC address related. The OUI's of the access-points AIR-CAP2702I-E-K9 are not all known to the device classifier integrated in the switch. As I'm running the latest IOS the only possible work-around was triggering on MAC address instead of profile name. That's what I've done and everything is working with this new configuration. Thank you very much Cisco for all the different OUI's used for the same equipment (for the moment I've already 12 different OUI's for the AIR-CAP2702I-E-K9 !!)

mikaelbje · ‎11-23-2016

Hi!

Do you know if this has been fixed in the latest code? I have the same problem and haven't found any mentions of this in the release notes.

Do you have your current OUI list? I've found the following OUIs so far for AIR-CAP2702I-E-K9 in my install:

00a6ca

881dfc

f44e05

843dc6

On SW 15.0(2)EX5 but there's no point of upgrading if it hasn't been fixed in a later code.

mmccallebaut · ‎11-23-2016

Hello

our OUI list for this moment is:

oui list ECBD1D
oui list E86549
oui list CC46D6
oui list 84B261
oui list 70E422
oui list 58AC78
oui list 00FEC8
oui list 00F663
oui list 00F28B
oui list 00C88B
oui list 00C164
oui list 00A6CA
oui list 0081C4
oui list 007888
oui list 004268
oui list 003A7D
oui list 00351A

3 of your OUI 's aren't even in my list.

What we do is changing the configuration of all are switches via Prime whenever a new OUI is added.

In the future we will use the ISE for profiling (NAC) , so the auto smartport configuration in our switches will disappear in the near future.

Best regards

Mike

mikaelbje · ‎11-23-2016

Oh, god. And the list keeps on growing. Auto Smartports has worked fine as a poor man's profiling. I would've expected Cisco to keep their lists for their own devices up to date, but it seems that's too much to ask for.

Thanks for the OUI list mate.

Problems with device classifier for triggering AIR-CAP2702I-E-K9 devices