I want to deploy an ESX server on BL480c servers where the service console must be in a separate VLAN (vlan id 2). To deploy the ESX server I am using the Altiris 6.5 deployment server. This deployment server is also situated in the same VLAN. Both the deployment server and the blade servers are connected to the same GbE2C blade interconnect switch. The deployment server port is VLAN 2 fixed and the network ports for the ESX servers are VLAN tagging enabled.
To get the ESX service console in the appropiate VLAN I am using VLAN tagging on the ESX server.
When I deploy the ESX server, the server gets an IP from DHCP and loads the boot image. When the boot image has loaded and started, the ESX server can not longer make a connection to the deployment server. An ifconfig only returns the loopback interface information.
However when I disable vlan tagging on the switch for the esx server ports I get connection to the deployment server and the server continues to deploy. Since my default.cfg scripts points to vlan 2 for the service console I loose connection when the service console interface is being configured. This is logical because vlan tagging is on that moment disabled on the switch. So disabling vlan tagging on the switch is not a valid option for an automatic installation of my esx servers.
Does somebody know the solution for this problem or does somebody know how to avoid this while keeping it an automated installation ?