This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Possible to flush or sync Nodealias so as to keep data up to date?

Possible to flush or sync Nodealias so as to keep data up to date?

Anonymous
Not applicable

‎03-27-2019 01:06 PM

Hi

Have an issue when nodealias is holding onto an IP address and thereby is being reported incorrectly under the end-system in control.

For example this is what nodealias was reporting on a specific port:

code:
Slot-1 Far-B20_23-L-GND.1 # show nodealias ports 3:18
Port  MAC Address     Alias ID Time Last Learned  VID  Protocol Source IP
----- ----------------- ---------- ------------------- ---- -------- ---------------
3:18  f0:92:1c:f4:f6:03     370 03-02-2019 08:54:26 202  bootpc
3:18  f0:92:1c:f4:f6:03     371 03-02-2019 08:54:28 202  ip    10.20.32.1
3:18  f0:92:1c:f4:f6:03     372 03-02-2019 08:54:28 202  mdns
3:18  f0:92:1c:f4:f6:03     373 03-02-2019 08:54:28 202  mdns
3:18  f0:92:1c:f4:f6:03     374 03-02-2019 08:54:28 202  llmnr
3:18  f0:92:1c:f4:f6:03     381 03-03-2019 02:16:52 202  ssdp
3:18  f0:92:1c:f4:f6:03     382 03-03-2019 11:24:11 202  ipv6   ::     
3:18  b0:0c:d1:49:3c:5d     610 03-08-2019 17:21:59 202  ipv6   ::     
3:18  b0:0c:d1:49:3c:5d     611 03-08-2019 17:22:24 202  ipv6   fe80::e41f:a0dc:71c6:d219
3:18  b0:0c:d1:49:3c:5d     612 03-08-2019 17:22:25 202  bootpc
3:18  b0:0c:d1:49:3c:5d     613 03-08-2019 17:22:29 202  ip    10.20.32.8
3:18  b0:0c:d1:49:3c:5d     614 03-08-2019 17:22:29 202  mdns
3:18  b0:0c:d1:49:3c:5d     615 03-08-2019 17:22:29 202  mdns
3:18  b0:0c:d1:49:3c:5d     616 03-08-2019 17:22:29 202  llmnr
3:18  b0:0c:d1:49:3c:5d     617 03-08-2019 17:22:30 202  ssdp
3:18  b0:0c:d1:49:3c:5d    1347 03-26-2019 15:23:10 0   ip    10.20.32.8
3:18  b0:0c:d1:49:3c:5d    1435 03-27-2019 10:06:21 202  ip    169.254.210.25


The end-system was reporting the IP address as 169.254.210.25, although it actually had an IP address of 10.20.32.8.

If I clear the nodealias entry i.e:

code:
clear nodalias port 3:5


Then the relook at the nodealias entries and then see the entry as follows, and the information is updated in NAC correctly:

code:
Slot-1 Far-B20_23-L-GND.4 # show nodealias ports 3:18
Port  MAC Address     Alias ID Time Last Learned  VID  Protocol Source IP
----- ----------------- ---------- ------------------- ---- -------- ---------------
3:18  b0:0c:d1:49:3c:5d    1698 03-27-2019 13:55:06 202  ip    10.20.32.8
3:18  b0:0c:d1:49:3c:5d    1699 03-27-2019 13:55:06 202  bootpc


I know I can tidy this up a little by perhaps specififying just the protocol of 'IP' for nodealias, but it's the same protocol that's causing the conflict.

Any ideas what I could do to improve the detection, maybe perhaps not use nodalias and just rely on DHCP snooping instead?

One other side effect to this issue is that when the wrong IP address is reported against the end-system reachability agent tests fail because tries to ping the wrong IP, and could ultimately quarantine the device.

Here is another example, the actual IP address of the end-system was 10.20.32.23 but because the most recent entry was showing 10.20.128.127 that's what assessment was using to ping against.

Still do a little digging, as a possibility for example a phone was plugged into that port also and why in this example a different IP was registered - although the same problem exists.

code:
Slot-1 Far-B20_23-L-GND.1 # show nodealias ports 3:11
Port   MAC Address          Alias ID  Time Last Learned    VID   Protocol  Source IP
-----  -----------------  ----------  -------------------  ----  --------  ---------------
3:11   a0:d3:c1:29:00:56         916  03-25-2019 12:32:01  202   ip        10.20.32.23
3:11   a0:d3:c1:29:00:56         918  03-25-2019 12:35:45  202   bootpc
3:11   a0:d3:c1:29:00:56         925  03-25-2019 12:46:57  202   llmnr
3:11   a0:d3:c1:29:00:56         926  03-25-2019 12:47:01  202   ssdp
3:11   a0:d3:c1:29:00:56         927  03-25-2019 12:47:04  202   mdns
3:11   a0:d3:c1:29:00:56        1130  03-26-2019 10:08:46  3999  ip        169.254.39.11
3:11   a0:d3:c1:29:00:56        1131  03-26-2019 10:08:47  3999  bootpc
3:11   a0:d3:c1:29:00:56        1132  03-26-2019 10:09:15  3999  llmnr
3:11   a0:d3:c1:29:00:56        1133  03-26-2019 10:09:16  3999  mdns
3:11   a0:d3:c1:29:00:56        1134  03-26-2019 10:09:17  3999  ssdp
3:11   a0:d3:c1:29:00:56        1140  03-26-2019 10:11:52  202   ip        169.254.39.11
3:11   a0:d3:c1:29:00:56        1264  03-26-2019 13:13:07  202   ip        10.20.128.127
3:11   a0:d3:c1:29:00:56        1795  03-27-2019 14:31:29  202   mdns


When doing a debug for IP resolution on NAC I get the following:

code:
2019-03-28 09:44:14,075 DEBUG [com.enterasys.tesNb.server.ipresolution.IpResolutionConfigManager] (UpdateService Thread18:) matching ES A0-D3-C1-29-00-56 from switch 10.20.224.250 to location groups
2019-03-28 09:44:14,075 DEBUG [com.enterasys.tesNb.server.ipresolution.IpResolutionConfigManager] (UpdateService Thread18:) testing with location group: APs By Switch Port
2019-03-28 09:44:14,075 DEBUG [com.enterasys.tesNb.server.ipresolution.IpResolutionConfigManager] (UpdateService Thread18:) Configuring switch and port list: [10.20.224.200:1:45-48,2:45-48,3:45-48,4:45-48]
2019-03-28 09:44:14,076 DEBUG [com.enterasys.tesNb.server.ipresolution.IpResolutionConfigManager] (UpdateService Thread18:) location group APs By Switch Port did not match
2019-03-28 09:44:14,076 DEBUG [com.enterasys.tesNb.server.ipresolution.IpResolutionConfigManager] (UpdateService Thread18:) testing with location group: All Swicthes
2019-03-28 09:44:14,076 DEBUG [com.enterasys.tesNb.server.ipresolution.IpResolutionConfigManager] (UpdateService Thread18:) Configuring switch list: [10.0.254.0/24, 10.20.224.250]
2019-03-28 09:44:14,076 DEBUG [com.enterasys.tesNb.server.ipresolution.IpResolutionConfigManager] (UpdateService Thread18:) found a matching location group for this end-system IP resolve request: All Swicthes
2019-03-28 09:44:14,076 DEBUG [com.enterasys.tesNb.server.ipresolution.IpResolutionConfigManager] (UpdateService Thread18:) location to use for ip resolution for ES: A0-D3-C1-29-00-56 is All Swicthes
2019-03-28 09:44:14,076 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (UpdateService Thread18:) ESDMAC:29-00-56 Requesting resolve of IP address for MAC: A0-D3-C1-29-00-56
2019-03-28 09:44:14,076 INFO [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Starting IP Resolution for EndSystem: A0-D3-C1-29-00-56
2019-03-28 09:44:14,076 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 The located MAC to IP mapping is from a DHCP request, so unable to use for fully trusted DHCP IP for MAC: A0-D3-C1-29-00-56
2019-03-28 09:44:14,076 INFO [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Starting CtAliasMacAddressTable IP resolution for: A0-D3-C1-29-00-56 on switch: 10.20.224.250 and ifIndex: 3011
2019-03-28 09:44:14,076 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Starting to read from: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86
2019-03-28 09:44:14,108 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.1.4.10.20.32.23.1989, interface: 3011 == 3011
2019-03-28 09:44:14,112 INFO [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56,ESDIP:10.20.32.23 Discovered IP Address: 10.20.32.23
2019-03-28 09:44:14,112 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.1.4.10.20.128.127.1216, interface: 4013 == 3011
2019-03-28 09:44:14,112 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.1.4.169.254.39.11.1211, interface: 4013 == 3011
2019-03-28 09:44:14,112 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.1.4.169.254.39.11.2125, interface: 3011 == 3011
2019-03-28 09:44:14,115 INFO [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56,ESDIP:169.254.39.11 Discovered IP Address: 169.254.39.11
2019-03-28 09:44:14,115 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.8.0.1213, interface: 4013 == 3011
2019-03-28 09:44:14,115 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.8.0.1988, interface: 3011 == 3011
2019-03-28 09:44:14,118 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.27.32.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1217, interface: 4013 == 3011
2019-03-28 09:44:14,118 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.27.32.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2090, interface: 3011 == 3011
2019-03-28 09:44:14,121 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.27.32.128.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2042, interface: 3011 == 3011
2019-03-28 09:44:14,124 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.28.32.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1212, interface: 4013 == 3011
2019-03-28 09:44:14,124 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.28.32.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2026, interface: 3011 == 3011
2019-03-28 09:44:14,127 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.29.32.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1214, interface: 4013 == 3011
2019-03-28 09:44:14,127 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.29.32.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2126, interface: 3011 == 3011
2019-03-28 09:44:14,130 INFO [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Discovered IP List (2): IpAddressCollection [ipv4Addresses=[10.20.32.23, 169.254.39.11], ipv6Addresses=null]
2019-03-28 09:44:14,130 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 SNMP read from switch resulted in 2 IPs, filtering...
2019-03-28 09:44:14,130 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Keeping IPv4 address 10.20.32.23
2019-03-28 09:44:14,130 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Keeping IPv4 address 169.254.39.11
2019-03-28 09:44:14,130 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 SNMP read from switch found multiple IPs; [10.20.32.23, 169.254.39.11]
2019-03-28 09:44:14,130 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Unable to get IP address from switch: 10.20.224.250, checking for an MLAG Peer
2019-03-28 09:44:14,130 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 getIpFromNasSwitch, vlanId = -1, vlanName = null, location = All Swicthes
2019-03-28 09:44:14,130 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Switch SNMP request returned 2 IPs.
2019-03-28 09:44:14,130 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Attempting to resolve the IP with NetBIOS
2019-03-28 09:44:14,130 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Making NetBIOS requests to IPs: [10.20.32.23, 169.254.39.11]
2019-03-28 09:44:19,091 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 got back MAC: null for IP: 10.20.32.23
2019-03-28 09:44:19,091 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 got back MAC: null for IP: 169.254.39.11
2019-03-28 09:44:19,091 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Attempting to clear IP address entries on switch due to SNMP duplicates.
2019-03-28 09:44:19,091 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Retrieving ctAliasIds for: A0-D3-C1-29-00-56
2019-03-28 09:44:19,125 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Unable to read ctAliasMacAddressInterface(1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.1) for switch: 10.20.224.250 with error: SNMP_END_OF_MIB
2019-03-28 09:44:19,125 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Removing ctAliasEntries for: A0-D3-C1-29-00-56 on ifIndex: 3011
2019-03-28 09:44:19,125 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.ExtremeIdMgrIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 This worker does not support clearing entries.
2019-03-28 09:44:19,125 INFO [com.enterasys.tesNb.server.snmp.ipresolution.ExtrIpNetToMediaIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Removing IpNetToMedia for MAC: A0-D3-C1-29-00-56 on ifIndex: 3011
2019-03-28 09:44:24,125 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Attempting to resolve IP with SNMP re-read of IPs on switch
2019-03-28 09:44:24,125 INFO [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Starting CtAliasMacAddressTable IP resolution for: A0-D3-C1-29-00-56 on switch: 10.20.224.250 and ifIndex: 3011
2019-03-28 09:44:24,126 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Starting to read from: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86
2019-03-28 09:44:24,158 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.1.4.10.20.32.23.1989, interface: 3011 == 3011
2019-03-28 09:44:24,163 INFO [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56,ESDIP:10.20.32.23 Discovered IP Address: 10.20.32.23
2019-03-28 09:44:24,163 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.1.4.10.20.128.127.1216, interface: 4013 == 3011
2019-03-28 09:44:24,163 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.1.4.169.254.39.11.1211, interface: 4013 == 3011
2019-03-28 09:44:24,163 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.1.4.169.254.39.11.2125, interface: 3011 == 3011
2019-03-28 09:44:24,168 INFO [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56,ESDIP:169.254.39.11 Discovered IP Address: 169.254.39.11
2019-03-28 09:44:24,168 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.8.0.1213, interface: 4013 == 3011
2019-03-28 09:44:24,168 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.8.0.1988, interface: 3011 == 3011
2019-03-28 09:44:24,171 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.27.32.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1217, interface: 4013 == 3011
2019-03-28 09:44:24,171 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.27.32.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2090, interface: 3011 == 3011
2019-03-28 09:44:24,175 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.27.32.128.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2042, interface: 3011 == 3011
2019-03-28 09:44:24,178 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.28.32.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1212, interface: 4013 == 3011
2019-03-28 09:44:24,178 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.28.32.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2026, interface: 3011 == 3011
2019-03-28 09:44:24,181 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.29.32.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1214, interface: 4013 == 3011
2019-03-28 09:44:24,182 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Testing OID: 1.3.6.1.4.1.52.4.1.3.7.1.1.5.1.1.160.211.193.41.0.86.29.32.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2126, interface: 3011 == 3011
2019-03-28 09:44:24,184 INFO [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Discovered IP List (2): IpAddressCollection [ipv4Addresses=[10.20.32.23, 169.254.39.11], ipv6Addresses=null]
2019-03-28 09:44:24,185 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 SNMP re-read from switch resulted in 2 IPs, filtering...
2019-03-28 09:44:24,185 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Keeping IPv4 address 10.20.32.23
2019-03-28 09:44:24,185 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Keeping IPv4 address 169.254.39.11
2019-03-28 09:44:24,185 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 SNMP re-read from switch found multiple IPs; [10.20.32.23, 169.254.39.11]
2019-03-28 09:44:24,185 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Returning: [169.254.39.11]
2019-03-28 09:44:24,185 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 NAT: Append IP address 169.254.39.11 to mac A0-D3-C1-29-00-56


The sections that are interesting to me are as follows:

code:
2019-03-28 09:44:14,076 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 The located MAC to IP mapping is from a DHCP request, so unable to use for fully trusted DHCP IP for MAC: A0-D3-C1-29-00-56


code:
2019-03-28 09:44:14,130 INFO [com.enterasys.tesNb.server.snmp.ipresolution.CtAliasMacAddressIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Discovered IP List (2): IpAddressCollection [ipv4Addresses=[10.20.32.23, 169.254.39.11], ipv6Addresses=null]


code:
2019-03-28 09:44:14,130 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Keeping IPv4 address 10.20.32.23
2019-03-28 09:44:14,130 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Keeping IPv4 address 169.254.39.11


code:
2019-03-28 09:44:19,091 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 Attempting to clear IP address entries on switch due to SNMP duplicates.


code:
2019-03-28 09:44:19,125 DEBUG [com.enterasys.tesNb.server.snmp.ipresolution.ExtremeIdMgrIpResolutionSnmpWorker] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 This worker does not support clearing entries.


code:
2019-03-28 09:44:24,185 DEBUG [com.enterasys.tesNb.server.ipresolution.ResolveIpAddress] (ResolveIpAddressService Thread8:) ESDMAC:29-00-56 NAT: Append IP address 169.254.39.11 to mac A0-D3-C1-29-00-56


The elements that might be causing an issue are as follows:

code:
The located MAC to IP mapping is from a DHCP request, so unable to use for fully trusted DHCP IP for MAC: A0-D3-C1-29-00-56


and

code:
this worker does not support clearing entries.


I have additionally set various options in the IP Resolution configuration in NAC trying to correct issue without any luck:

f9ecac2ca34340fa80b8223ae0776bc2_7b190d47-876f-4755-bdb5-82084bdfb20b.png



Currently the switch is an X450G2 version 22.6.1.4
XMC / NAC version 8.2.4.42

Many thanks in advance.
0 Kudos
4 REPLIES 4

Anonymous
Not applicable

‎04-17-2019 12:12 PM

Hi Tomasz,

No worries. I implemented IDM with XML notification in the end, and it does seem much better.

Think I'll stick to using it for the foreseeable deployments.

Many thanks for your support.
0 Kudos

Tomasz
Valued Contributor II

‎04-16-2019 04:10 PM

Hi Martin,

Sorry for long delay.
Did you get some progress in the meantime?

If I remember well, IDM works as a charm with XMC but I hope that nodealias behavior will be eventually adjusted. It's a really nice feature itself.
I was playing with running EXOS + IDM + NAC but didn't take a look under the hood and now I'm cut off of the hardware for some short time... I'd try with this article first: https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configured-Identity-Management-for-XoS-in-NAC-Manager/

Kind regards,
Tomasz
0 Kudos

Anonymous
Not applicable

‎04-02-2019 09:49 PM

Hi Tomasz,

Thanks for replying.

Not sure if I tried disabling trusted DHCP (can't remember if its enabled by default?), but will give it a go.

To be honest I did originally have Identity management enabled, but disabled it in preference to NodeAlias thinking (without any solid fact) that it might be better.... then that might be just me having used it in the past with my EOS hat on 🙂

Will certainly give each a try, and just go with what works better.

In relation to ID Management, would I have to use that in conjunction with XML notification or is the information collected, perhaps through MIBs, when NAC trys to do an IP Discovery similar to how it does with NodeAlias?

Many thanks,

Martin
0 Kudos

Tomasz
Valued Contributor II

‎04-02-2019 08:00 PM

Hi Martin,

Just quick guess, did you try to disable 'Always use fully trusted DHCP IP' from the screenshot?
But that is related to DHCP Snooping, you might want to try to use DHCP Snooping instead of Nodealias.
Yeah... I miss some aging of nodealias entries or different behaviour so NAC could take the latest IP for a MAC from nodealias MIB instead of panicking... 😉
AFAIR you can also try to use Identity Management so you'd get IP, hostname and so on from EXOS as well.

Hope that helps,
Tomasz
0 Kudos
GTM-P2G8KFN