Are you using Custom Kickstart in the System package. If yes, can you paste the kickstart file.
What Bill mentions, can be done while provisioning by specifying the following commands in the "Addition entries for kickstart file" section in the System Package.
### Enable Tech Support Mode (Remote)
### Enable Tech Support Mode (Local)
Hi Hemal, I have not customised the kickstart at all it is default.
I will try adding the entries into the kickstart file as you have recommended and see if that resolves the issue.
I will let you know the outcome when I do.
Thank you in advance
Hi Hemal, those additional entries worked, and the blade is now getting further along the provisioning route
I am now getting the following error
kick start device cannot be found on eth0
could this be that the static IP address that the server is given during provisioning does not have access to the application server once that address has been assigned once the DHCP address is released?
or is it likely to be something else?
When exactly do you see the error. Can you paste the exact error message or screen shot ??
I will take a screen shot tomorrow whilst I am on a webex session with the customer, unfortunatly they have closed down for the day.
What is the ‘kickstart network device’ set to in the system package?
It is set to eth0 in the system package, as mentioned it starts to pxe boot successfully with a DHCP address from the scope that has been assigned to it for pxe install, you can see it loading the sys.vgz cim.vgz etc and then starts to install the OS, it looks like the OS installs successfully, but when it gets to this stage you are unable to ping the blade from either the dhcp assigned ip address or the static ip address that has been assigned to it during provisioning.
Could it also be that within the service profile vNIC0 is set to a native vLAN of BMC_DHCPxxxx so that it can pick up the PXE DHCP scope? and that once it tries to set the Static IP address it has no route out?
I will take a screenshot of the exact error once I have access tomorrow.
Try giving colon separated MAC address or vmnic0 in Kickstart network device for ESXi 4.1.
As Rupali mentioned, try giving vmnic0...
refer the following doc, and try specifying the disk within the kickstart or via Use Disk Script option in the Disk Partition panel...
I have had a look at the document and am still unable to provision to the SAN disk, I have tried various options, by editing the system package, within the disk partition option I have tried instead of install to first disk I have tried install to disk vmhba0, hba0, vhba0 and others, when the server boots it is showing the following as attached disks
but every time I try to install with different varients I get the following error
I have also tried to edit the kick start entry with autopart firstdisk=remote, but this installs to the locally attached disks, I am assuming that this is because they are the first non usb disks that are being discovered.
Within the UCS template I am using storage pools to pre define the vHBAs with the mapped wwnn, wwpn of the HBA and wwn of the SAN FE, LUN ID.
Has anyone any Ideas at all?