topic Re: NAC Appliance+WS-C4506-E - MAC notification problem in Network Security

NAC Appliance+WS-C4506-E - MAC notification problem

sirota — Fri, 21 Feb 2020 11:05:12 GMT

Hello all,

I'm trying to get working NAC Appliance 4.5 with WS-C4506-E with MAC notification without any luck. It seems that C4506 detects a MAC change, sends a SNMP trap to NAC Manager and according to what I was able to sniff directly on NAM via tcpdump it even arrives on NAM but I don't see it in Discovered Clients - it's like NAM ignores it completely. It doesn't see the change, therefore doesn't change VLAN on managed port of source switch.

Strangely enough, the same exact configuration does work on c3750 without a problem. I'm using NAC Applience 4.5 and WS-C4506-E with SUP4 and cat4500-ipbasek9-mz.122-46.SG.bin IOS image. It even works with WS-C4506-E in link-up link-down mode which sadly is insufficient for my case as I need IP phones to be connected to switch before the end user.

Can anyone here direct me where the problem should be?

Thank you for any hints

RSi

Re: NAC Appliance+WS-C4506-E - MAC notification problem

Daniel Laden — Sat, 08 Nov 2008 18:15:32 GMT

Set the logging to all on the CAM, repeat the problem, review the /perfigo/logs/perfigo-log0.log.0 file on the CAM for any clues

Re: NAC Appliance+WS-C4506-E - MAC notification problem

j.ridgers — Fri, 30 Jan 2009 19:25:27 GMT

Hi Radoslav:

Was there any resolution to this problem? I am running into the exact same problem however I'm using NAC Appliance 4.1.6 and cat4500-ipbasek9-mz.122-31.SGA8.bin.

Re: NAC Appliance+WS-C4506-E - MAC notification problem

ziyadr — Sun, 01 Feb 2009 21:59:14 GMT

doesn your SNMP community string use special characters like @ ?? i had the exact same problem in the past and had to change my community strings cause versions of code dont like the @ in it.

Re: NAC Appliance+WS-C4506-E - MAC notification problem

sirota — Wed, 11 Feb 2009 13:41:36 GMT

Hi,

sorry for late response. I solved this issue by upgrading IOS to 12.2(50)SG becouse of a SNMP Trap bug with 12.2(46)SG. I don't know if it's the same issue with your 12.2(31) but give it a try and you'll see.

RSi