There's a Linux template VM someone left powered in an a scanned subnet.One of the secondary network interfaces (which is disabled) has a MAC address that wasn't changed when we deployed the VM's built off of the template.Whoops.įor god's sake, give me a "DO NOT MERGE" flag on the ASSET or modify the behavior so it puts assets in a "Duplicate Asset Queue" that I can either choose to enable for auto-approval or perform manual review/approval. I have two firewalls in Azure in an HA setup, I add the MAC address referenced in the notes to tsysMacBlacklist.Manually add the asset again and MAC address.Add it to the blacklist.Re-add the asset again.Rescan again.MERGED AGAIN.Guess I have to pull the MAC address of every SINGLE INTERFACE. Ok.I'll add the MAC addresses to the Blacklist (tsysMacBlacklist) to prevent merging. I had all of our switches defined in the system with all the numerous custom field values I've defined for Team Ownership definition, vulnerability management information, security compliance requirements, etc.After the last upgrade the system decided to discover about half of these as "new assets" when it did the next scheduled network discovery scan and it merged the original assets into the "new" assets and blew away all the manually entered data.Looks like I'm wasting another 90 minutes of my life on data entry. Looks like I have one firewall now instead of the 10 I went through and populated with copious amounts of metadata. I have remote site firewalls that were built using a baseline config, so the internal interfaces all have the same MAC address.Thanks FortiGate.
The current circle of hell I'm trapped in is trying to get all my network assets populated in the platform without them being merged into one another randomly. But the more and more I have to deal with the constant idiosyncrasies and deficiencies the more I'm growing to loath the product. I've been a champion of LanSweeper in my org for the last few years.
0 kommentar(er)
