ldms_core gets the MAC address if you use the NMAP option. I do recommend XDD though.
Just remember that XDD is not for all agents. The best method is to see if there is a device that is usually on and if so, put it on that device only. If not, put it on three devices that are most likely to be on.
Do NOT add it to the default agent configuration. Do NOT enable it on all workstations. It only takes one device per subnet to do the job.
So if I create a seperate agent install, and only install it on one or two PC's per subnet, how and when will the MAC addresses for those printers, switches and routers on those subnets show up?
Will I need to do another scan or will info simply start to populate into the unmanaged Device discovery area? Will I need to remove the devices from the UDD and scan for them again?
XDD is a passive discovery program. It will listen to the network traffic and build a local list of machines. Since it is local, it will be able to listen to all broadcast packets, such as arp on the subnet. It builds a list of machines, and if they are not managed machines, it send them up in a list to the Core Server.
As to whether it will update a machine that doesn't have a MAC or whether it will be a new entry, leaving the blank MAC entry from UDD and having a separate entry for the one found by XDD, I don't know. If the MAC is the same, it is updated, but with the MAC being blank, the new entry from XDD may come in as a new unmanaged device.
Thank you all that makes sense to me now.
Just a couple more clarifications?
1) Can an XDD agent be put on a server OS? We use a seperate printer vlan, and the only agent in that vlan is on our print server. Can I install the xdd agent on the print server?
2) Again, we seperate out our phones on another vlan with no pc's or servers, any suggestions as to how I can get those MAC's?
Thanks again for all the advise.
2) UDD scan that network and use ldms_core to get the MAC Addresses and OS Names.
Thanks for all the help Jack.
I am trying to wrap my head around the ldms_core app.
I still do not understand how i tie it to LANDesk.
Right now I have it installed on a machine that is not the core, but that does have the 32bit console.
Is there suppose to be something created in the UDDCxExtender.xml file? If not, how do I initiate the program via a right click? If I schedule it, what switches am I really interested in? Device name & MAC address are really the only 2 things I need.
PS I have also installed WinPcap, per your documentation.
And I am dealing with LANDesk 8.8 SP1
I think you've been reading several different documents and merging them in your head
ldms_core.exe is here: http://www.droppedpackets.org/scripts/ldms_core -- it runs on a regular basis as a scheduled task and does core maintenance tasks. One of those tasks is to call NMAP and have it update any unmanaged node with no OS Name.
ldms_nmap_lpm.exe is here: http://www.droppedpackets.org/process-manager/ldms_nmap_lpm -- it only does NMAP of a single device at a time and was built for LPM before LPM was able to process incoming XML... with a modern LPM it isn't necessary. However, it's still a moderately useful program if you want to extend your Unmanaged Devices right-click menu, which is documented here: http://www.droppedpackets.org/interface/udd-menu-extension/
Either program requires NMAP, not just WinPCAP. Either program will also update the MAC address of an unmanaged node if it doesn't exist (and if NMAP was able to find it).