When attempting to load an image from an external USB device WinPE fails to launch scripts contained in startnet.cmd as it can't find them or can't find the USB device. Have any other forum users experienced problems using WinPE with the UCS-E servers?
I am not sure if the equivalent to SCU exists for E series servers. There is something called CIMC running on another CPU within the chassis which gives low level access to the server and sounds simiilar to what you are describing.
What I am really looking for is whether anyone has done any work with WinPE based installations using USB media on the E series servers and specifically if they have found a solution to the problems I am having running installation scripts.
with regards to the server Have you changed the boot order in the setup BIOS? Correct me if Im wrong, but e-series still has a boot menu right? select the USB
To add, make sure you format the USB in FAT32 (typially USB Installation environment) Another alternative is converting it into *.iso image, and since you mentioned CIMC then that's the ticket, mount the *.iso through CIMC
We find the idea of booting from USB attractive because a KVM is installed locally and it requires minimal equipment / knowhow from the person doing the installation.
We don't have any trouble booting into WinPE on the USB drive but it's strange that when WinPE is attempting to run some scripts from the startnet.cmd it fails to find them on the USB drive. From the log it seems that WinPE is messing around installing the USB hardware (from which it has just booted) using Plug and Play. Unfortunately it doesn't complete this process until startnet.cmd has run.
Microsoft have some caveats about WinPE USB support and claim that it requires the BIOS to be compatible. I am not sure which exactly are the BIOS features that might make USB devices immediately available to WinPE but it would be interesting to know if Microsoft and Cisco have even looked at this on the UCS-E platform.
Yeah, and cisco actually endorses VMWare better than Windows (Hyper-V) Well, anyway if ever you are using USB, make sure all the installation files are in the root folder of the USB storage, root in the sense that there should be no new folders created or files inside a folder vice-versa.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...