Dynamic workload movement with BladeSystem Matrix: Fluid movement between physical and virtual resources for flexibility and cost-effective recovery

9
In all instances, new interfaces are automatically configured to use DHCP. In moves of the sort we
are talking about, it is usually desirable for the network configuration to be the same after the move
as it was before. This is where PINT comes in to the picture. PINT gathers network configuration
information from the OS on the original server and stores it in its configuration file. When the image
is moved to another server, PINT reads in the information from the configuration file and gathers the
current network configuration from the OS. This essentially creates lists of potential move sources and
targets. Only interfaces with static IP addresses are considered as sources and only interfaces
configured as DHCP are considered as targets.
PINT then goes through the lists looking for matches between sources and targets based on the MAC
address. Any matches are paired in a list of moves that will be performed. They are also removed
from the source and target lists. Once all the MAC address matches have been determined, PINT will
go through the two lists pairing candidates with targets until one of the lists is exhausted. ows
Windows keeps most of the interface and configuration information in the registry. If the image is
booted on a new server, and Windows perceives any differences in the attached NICs, it „orphans‟
these old interfaces and configurations in the sense that they no longer have an attachment to a NIC
in the server.
PINT is installed as a service and will start automatically when Windows starts all of the services.
PINT waits for any plug and play activity to complete before gathering information from its
configuration file and the OS. PINT creates the list of source and target pairings as described earlier
and performs the moves. Once all of the moves have been completed, PINT initiates a clean
shutdown and restart. When the server starts up again, the network changes will all be in place.
PINT remains in the server as a service but is in a suspended state waiting for certain events. It only
actively runs when it receives one of the following events:
IP configuration change event
PINT considers any changes made while the server is up and running to be intentional
changes made by the user. PINT records the changes and updates its configuration file.
Stop event
If the user stops the PINT service PINT receives an event that lets it know to shutdown.
User command event
If a user makes any changes via the PINT command line PINT is notified and acts
accordingly.
[Note]:
If a NIC in the destination server requires a different set of drivers than those on
the source server, you must install the new drivers before using PINT on the
destination server.