/build/static/layout/Breadcrumb_cap_w.png
09/26/2019 131 views

we recently deployed a TON of new machines to different locations.  Many times we replaced existing machines with new machines  under a new naming convention.  The problem is all of these machines were staged within the network 10.63.78.x and when they were deployed in the new network of 10.63.63.x the MACHINE_NICS table didn't get updated.  As you can see below there was an old machine named LAT-TRN-01 which was replaced by LAT-TRN-D001.  The IP in the MACHINE table is correct, but the MAC is showing a bluetooth adapter?  the MACHINE_NICS table still shows the old IP from the main office.  I have confirmed that deleting the MACHINE entry and forcing a re-inventory will create it with the right IP, but this will cause problems with machines that might be offline or don't check in. 


Does anyone have a suggestion on forcing the MACHINE_NICS table to update and/or make the MACHINE table report the correct MAC? Thanks in advance.


mysql> Select M.ID 'M.ID', M.NAME 'M.NAME', M.USER 'M.USER', M.IP 'M.IP', M.MAC 'M.MAC', MN.IP 'MN.IP', MN.MAC 'MN.MAC', MN.NIC 'MN.NIC' from MACHINE M join MACHINE_NICS MN on M.ID = MN.ID where MN.IP like "10.63.63.18%" or M.IP like "10.63.63.18%";

+------+--------------+--------+--------------+-------------------+--------------+-------------------+---------------------------------------------+

| M.ID | M.NAME       | M.USER | M.IP         | M.MAC             | MN.IP        | MN.MAC            | MN.NIC                                      |

+------+--------------+--------+--------------+-------------------+--------------+-------------------+---------------------------------------------+

| 2632 | LAT-TRN-01   |        | 10.63.63.185 | 10:E7:C6:AF:40:36 | 10.63.63.185 | 10:E7:C6:AF:40:36 | Intel(R) Ethernet Connection (5) I219-LM #2 |

| 2632 | LAT-TRN-01   |        | 10.63.63.185 | 10:E7:C6:AF:40:36 | NULL         | 20:41:53:59:4E:FF | RAS Async Adapter                           |

| 2637 | LAT-TRN-D001 | mduong | 10.63.63.185 | 38:00:25:78:66:07 | NULL         | 38:00:25:78:66:07 | Bluetooth Device (Personal Area Network)    |

| 2637 | LAT-TRN-D001 | mduong | 10.63.63.185 | 38:00:25:78:66:07 | 10.63.78.192 | C4:65:16:A8:1B:55 | Intel(R) Ethernet Connection (7) I219-LM    |

| 2637 | LAT-TRN-D001 | mduong | 10.63.63.185 | 38:00:25:78:66:07 | NULL         | 38:00:25:78:66:03 | Intel(R) Wireless-AC 9560                   |

| 2637 | LAT-TRN-D001 | mduong | 10.63.63.185 | 38:00:25:78:66:07 | NULL         | 38:00:25:78:66:04 | Microsoft Wi-Fi Direct Virtual Adapter      |

| 2637 | LAT-TRN-D001 | mduong | 10.63.63.185 | 38:00:25:78:66:07 | NULL         | 88:2D:20:52:41:53 | WAN Miniport (IP)                           |

| 2637 | LAT-TRN-D001 | mduong | 10.63.63.185 | 38:00:25:78:66:07 | NULL         | 8C:D4:20:52:41:53 | WAN Miniport (IPv6)                         |

| 2637 | LAT-TRN-D001 | mduong | 10.63.63.185 | 38:00:25:78:66:07 | NULL         | 90:0A:20:52:41:53 | WAN Miniport (Network Monitor)              |

| 2637 | LAT-TRN-D001 | mduong | 10.63.63.185 | 38:00:25:78:66:07 | NULL         | 3A:00:25:78:66:03 | Microsoft Wi-Fi Direct Virtual Adapter      |

+------+--------------+--------+--------------+-------------------+--------------+-------------------+---------------------------------------------+

10 rows in set (0.05 sec)

2 Comments   [ + ] Show comments

Comments

  • This machine has also been in the new location for over a month
  • A little more food for thought. Direct Database dump/grep

    [16:41:11] sbenson@SRO-FOG-01[0]:/images/Kbox/ORG1-20190923$ grep 10.63.63.185 *

    ORG1.MACHINE_NICS.sql:111651 2632 Intel(R) Ethernet Connection (5) I219-LM #2 10:E7:C6:AF:40:36 10.63.63.185 255.255.255.0 True NULL lbsavings.com LAT-TRN-01

    ORG1.MACHINE.sql:2632 2019-08-16 09:16:17 2019-08-12 13:24:20 LAT-TRN-01 10:E7:C6:AF:40:36 10.63.63.185 fe80::9d71:751c:36b6:fe77 255.255.255.0 NULL Microsoft Windows 7 Enterprise N x646.1.7601 6 1 0 Service Pack 1 24 NULL 2019-08-16 09:15:46 2019-08-16 09:16:10 2019-08-16 09:16:17 0000-00-00 00:00:00 0000-00-00 00:00:00 empty 6.1.7601 7601 2019-02-01T13:49:00-08:00 2019-08-12T14:27:15-07:00 3,18:48 C:\\Windows empty 8192 2276.5 HP HP ProDesk 600 G3 SFF lbsavings.com Default System BIOS P07 Ver. 02.22 HP Default System BIOS MXL8271N7R PCI ISA CPU Chip Count: 1\nCPU Core Count: 4\nCPU0: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (4 cores) Conexant HD Audio\nIntel(R) Display Audio hp HLDS DVDRW GUD1N SCSI CdRom Device Intel(R) HD Graphics 530:1024 MB Generic PnP Monitor 183 2048 241 241 Fax\nMicrosoft XPS Document Writer\nNautilus Virtual Printer\nPrimoPDF\nSend To OneNote 2010 3592afff-96ee-49af-9cd0-618289e20daa 0 x64 0 NULLNULL NULL NULL NULL NULL NULL 8.1.52 0000-00-00 00:00:00 0000-00-00 00:00:00 NULL 1 empty desktop America/Los_Angeles 65536 LBS_NT\\ftablada 2018-07-16 10:00:00 MXL8271N7R MXL8271N7R NO .NET CLR 2.0.50727, .NET CLR 3.0.30729, .NET CLR 3.5.30729, .NET4.0C, .NET4.0E, .NET4.7 11.0.9600.19399 NULL x64 OK 1 4 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (4 cores)

    ORG1.MACHINE.sql:2637 2019-09-23 09:13:59 2019-08-13 13:01:30 mduong M Duong LAT-TRN-D001 38:00:25:78:66:07 10.63.63.185 fe80::b023:3de5:6743:4065 255.255.255.0 NULL Microsoft Windows 10 Enterprise x64 10.0.17763 10 0 0 29 NULL 2019-09-23 09:04:47 2019-09-23 09:05:27 2019-09-23 09:13:59 0000-00-00 00:00:00 0000-00-00 00:00:00 empty 10.0.17763 17763 2019-08-13T19:43:47-07:00 2019-09-20T21:35:37-07:00 2,11:29 C:\\Windows empty 8192 2586.3 HP HP ProDesk 600 G4 DM (TAA) lbsavings.com LBS_NT\\mduong mduong LBS_NT Q22 Ver. 02.07.00 Q22 Ver. 02.07.00 HP Q22 Ver. 02.07.00 MXL9234YDV PCI ISA CPU Chip Count: 1\nCPU Core Count: 6\nCPU0: Intel(R) Core(TM) i5-8500T CPU @ 2.10GHz (6 cores) Conexant HD Audio\nIntel(R) Display Audio Intel(R) UHD Graphics 630:1024 MB Generic PnP Monitor 128 4095 8 8 Fax\nIJ7200\nMicrosoft Print to PDF\nMicrosoft XPS Document Writer\nNautilus Virtual Printer\nSend To OneNote 16\nWebex Document Loader 9fb1fd85-11aa-49e8-8f1a-327abe26135a 0 x64 0 NULL NULL NULL NULL NULL NULL NULL 8.1.52 0000-00-00 00:00:00 0000-00-00 00:00:00 NULL 1 empty desktop America/Los_Angeles 32768 LBS_NT\\mduong 2019-04-11 10:00:00 MXL9234YDV MXL9234YDV NO .NET CLR 2.0.50727, .NET CLR 3.0.30729, .NET CLR 3.5.30729, .NET4.0C, .NET4.0E, .NET4.7 or newer (461814) 11.737.17763.0 NULL x64 OK 1 6 Intel(R) Core(TM) i5-8500T CPU @ 2.10GHz (6 cores)

    ORG1.NICS_IPS.sql:2632 111651 10.63.63.185 255.255.255.0 NULL

    ORG1.NICS_IPS.sql:2637 112034 10.63.63.185 255.255.255.0 NULL

    ORG1.NODE.sql:949 10.63.63.185 NULL 0 0 0 0 NULL 0 0 0 0 0 0 0 0 NULL NULL NULL NULL 0 NULL NULL NULL NULL NULLNULL 10.63.63.185 2011-02-09 10:36:07 0000-00-00 00:00:00 NULL 4 NULL NULL

    ORG1.OBJECT_HISTORY.sql:6280987 KBOT 1909 Nautilus Unity_17 2019-03-26 16:54:44 1018 Scott Benson Addition MACHINE LAT-TRN-01 (10.63.63.185)

    ORG1.OBJECT_HISTORY.sql:6316071 KBOT 1926 Network Backup Script -SBenson 2019-07-19 08:40:23 1018 Scott Benson Addition MACHINE LAT-TRN-01 (10.63.63.185)

    ORG1.OBJECT_HISTORY.sql:6331352 KBOT 1943 W10 SecureBoot 2019-09-06 12:35:14 1018 Scott Benson Addition MACHINE LAT-TRN-D001 (10.63.63.185)

    [16:42:40] sbenson@SRO-FOG-01[0]:/images/Kbox/ORG1-20190923$ grep 10.63.63.185 *|grep C4:65:16:A8:1B:55

    [16:42:49] sbenson@SRO-FOG-01[0]:/images/Kbox/ORG1-20190923$ grep C4:65:16:A8:1B:55 *

    ORG1.MACHINE_NICS.sql:112034 2637 Intel(R) Ethernet Connection (7) I219-LM C4:65:16:A8:1B:55 10.63.78.192 255.255.252.0 True Automatic lbsavings.com LAT-TRN-D001

    [16:43:01] sbenson@SRO-FOG-01[0]:/images/Kbox/ORG1-20190923$


Community Chosen Answer

2

The MACHINE.MAC and MACHINE.IP columns should contain the data of the latest connection the device had with the appliance. Meaning, if a device checks in on the wired LAN connection it will show that MAC and IP, if on the next connection it is on wireless, it will show that MAC and IP. Based on that I'm not sure what you mean by the "correct MAC". 

Computer lat-trn-d001 is reporting multiple NICS because it has multiple network devices, one of which is a Bluetooth adapter.

As for why the IP address in the MACHINE_NICS table isn't being updated, I'm not sure. It's possible that the data is only captured on initial inventory and not updated in subsequent updates. You will probably need to enter a support ticket to know for certain. 

My question is what are you trying to learn with this report? Is there a reason that you aren't just using the IP address in the machine table?

Answered 09/27/2019 by: chucksteel
Red Belt

  • from your first statement, the IP and MAC listed in the MACHINE table is the correct IP, but the MAC is showing the bluetooth adapter, which has never had any ip assigned to it. The problem still exists that the nowhere within the database does it show the correct IP/MAC combo. But some how it shows that correct information within

    Inventory > Devices > LAT-TRN-D001 > Network Interfaces.
    • Ah, I didn't catch the incorrect MAC in the machine table. That's weird. I looked at the inventory.xml file for my machine and it shows the correct IP in the network interfaces section. I would have to do more hunting to see if I can find a machine where it differs from the machine table.

      I stand corrected on my previous statement. It appears that the MACHINE.MAC column contains the MAC of the first interface alphabetically on the machine.

      Can you check the inventory.xml on LAT-TRN-D001 and see what is lists for network interfaces?

All Answers

1

Are you on version 10 kbox?  I ran into a different nic related problem after I went to 10.  I submitted a beta ticket.  Some of my machines have the old cisco vpn software on them and Kace was reporting the fake IP/MAC they were getting from cisco as the machines active IP/MAC.  This orphans the machines because the kbox tries that connection vs the real one.  My ticket number was Beta 0296.  the agents could check in but kbox could not talk back since was using the non existent connection

It only got investigated and never accepted as a real bug.

9k=

Z


Answered 09/27/2019 by: SMal.tmcc
Red Belt

  • We are not on version 10. We're stuck on 8 because of a problem with our VMware environment not being 6.5 for version 9+
    • different bug then or has been around for longer then I thought
0

This is an ongoing bug that has been reported. I have the same issue. I did check on the status at KaceCon.  It is considered one of the highest priorities.  Hoping it will be in a bug fix releases soon.

Answered 10/08/2019 by: jmogle
Senior White Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share