Choosing Unique System Info (like System ID)

Making unique information

Some details need to be unique. For example, MAC-48 addresses need to be unique in order for communication on a subnet to occur.

Decide upon a system name

System names can be useful for networking. Also, they are a sensible way to keep track of disk images, which need filenames.

For a server that is going to be serving a particular purpose, the intended purpose of the machine is often considered when creating the system name. For a workstation, a name like “reception3” may be rather common.

Perhaps see: new sytem security, and/or setting a host name

Choosing a virtual machine number

Determine a virtual machine number. Note that if you are using an address range, like 209-214, then you may wish to choose a virtual machine number that is similar to that range. e.g., choose a number from 9 through 14, so that the virtual machine's “virtual machine number” will look similar to the IP address (or perhaps both the IPv6 address and the IPv4 address). There's no technical reason why those numbers must match, but making them match is usually a bit more pleasant.

What is needed is that the system's MAC-48 address must be unique for the subnet that it is on, and the system should not try to listen for network traffic on a TCP port that is being used by other software, nor a TCP port that other software is likely to want to start using. An easy way to handle these actual requirements is to make the “virtual machine number” unique, so that no other virtual machines will use the same “virtual machine number” on this same physical machine

Decide what disk images will be used.