Unable to correctly provision a multi NIC VM when management NIC is not first in list
When provisioning a multi NIC server in VMWare, it is not possible to create the VM with the expected order of network interfaces and with the management network interface not being the first one defined.
The current implementation of TSAM requires the management network to be the first network interface in the image if you need a gateway or static route on the management network. The reordering happens automatically during provisioning of the network segment if the sub-network has either a gateway or static route definition. This means that, even if the customer defines it differently, the management network is moved first in case of a gateway or static route being required.
If the management network does not have a static route or gateway, the management network can be any interface on the image.
Resolving the problem
This is working as designed per the current implementation in TSAM. A request for enhancement has been opened for the requirement of the management interface being any interface in the image when either a static route or gateway is configured on it, RFE ID is 30446.
|Systems and Asset Management||IBM Service Delivery Manager||Linux, Windows||7.2.2, 7.2.1, 7.2.4|
More support for:
Tivoli Service Automation Manager
Software version: 7.2.2, 188.8.131.52, 184.108.40.206, 7.2.3, 7.2.4
Operating system(s): Linux, Windows
Reference #: 1624188
Modified date: 27 January 2015