(Optional) Installing the SDI Driver
With the SDI driver, EVS disks can be attached to BMSs. The EVS disks can be used as system disks from which the BMSs are booted. This facilitates quick BMS provisioning. If you do not need to use EVS disks or your BMS does not have SD1 cards, skip this section.
Prerequisites
- You have logged in to the VM.
- You have downloaded the SDI driver (scsi_ep_front) as instructed in Software and have uploaded it to the VM.
The scsi_ep_front version must be 2.0.2.12 or later.
- WDK has been installed.
Download WDK from http://download.microsoft.com/download/4/E/0/4E07EAAD-E394-4EA8-B2B8-D46E46A409C5/wdk/wdksetup.exe.
Procedure
- Obtain the device management tool devcon.exe from the WDK directory C:\Program Files (x86)\Windows Kits\10\Tools\x64, and place devcon.exe in the same directory as the SDI driver.
- Find the EpScsiAdpt installation file and view the PCI ID.
- Open the CLI, go to the directory where the SDI driver and device management tool are located, and run the following command:
devcon install EpScsiAdpt.inf "PCI\VEN_19E5&DEV_1610&SUBSYS_000119E5"
The PCI ID is an example only.
- (Optional) Delete device nodes.
- If the environment where you create an image does not have SDI hardware, the storage controller in the device manager has exceptions.
- Open the CLI, go to the directory where the SDI driver and devcon installation tool are stored, and delete the abnormal device nodes.
Run the devcon.exe find "PCI\VEN_19E5*" command to locate abnormal device nodes.
Run the devcon.exe remove "@ROOT\SCSIADAPTER\0000" command to delete the nodes.
- Restart the VM.
- Check whether the exceptions in the storage controller are cleared.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot