Add '00-22-BD-F8-19-FF' for /correlation/macaddress/excludedmacaddresses key. Open Admin Console, then open discoveryserver RAW Configuration dialog. However, there's nothing like that in there at present. User can set the MAC address '00-22-BD-F8-19-FF' to be excluded from discovery correlation rule. I suspect what is really required is for the database to contain statistics about the date when the machine was last in contact with the server, so you could easily sort by that in the console and use that to decide when they can be culled. It would be good to have better procedures for handling machines that are well and truly gone, but MAC addresses won't help. In 2.0 we introduced the ability to use the SMBIOS UUID as the primary key instead, although it turns out a number of manufacturers produce machines with duplicate "unique" IDs - in 2.0.1 I added code to detect duplicate UUIDs and fall back to using the MAC address as the primary machine identifier. Does anyone have a work around I got banned from the network at my remote drilling rig camp for ( I assume ) too much bandwidth usage. The aforementioned adapter doesnt support manual changes, so going in through settings is out. Just to add to this, the system won't normally let duplicate MAC addresses happen in all versions of GSS prior to 2.0, the MAC addresses in a machine was the primary internal identifier used in the client/server communication. Im trying to change my MAC address for the broadcom 802.11 ac Network adapter - im using windows 8.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |