The occassional trials and tribulations of a jack of all tr ades sysadmin in a startup in Silicon Valley
We use a good of software that is locked up by FlexLM. FlexLM is a license management and enforcement system sold by Macrovision (formerlly Globetrotter) to makers of software. The system can enforce all sorts of policies; most of the time it either locks a program to only run a specific computer (tied to mac address, hardware dongle, ip address, etc.) or allows a vendor daemon running on a server to provide a certain number of client workstations to run the software concurrently.
Each of the nine application suites that we use that use FlexLM have a license file that is tied to a MAC Address. As part of our efforts to clean and make sane our critical infrastructure we made plans to move the FlexLM daemons to a virtual machine. Since VMware does not by default guarantee that a MAC address for a virtual machine will never change, I followed the best practices laid out by VMware to manually set a MAC.
The short version of that best practices document is that the range 00:50:56:00:00:00-00:50:56:3F:FF:FF is available for assignment by the end user. I choose 00:50:56:00:00:01. It seems one of the vendors of an application thought it was fake and questioned it. Oops, I hadn't thought about that issue. Cutting and pasting the output from the ifconfig command put an end to the complaint.
[2006/10/19 | /hardware | permanent link]