List FC VIF Path Status
Get-UcsDcxVc | where { $_.transport -eq "fc" } | select dn,switchid,operstate,adminstate,vnic,linkstate
List Ether VIF Path Status
Get-UcsDcxVc | where { $_.transport -eq "ether" } | select dn,switchid,operstate,adminstate,vnic,linkstate
As title, It is a memo of my daily work, it won't be very detail but enough to retrieve what I have to.
Thursday, July 11, 2019
Tuesday, July 2, 2019
Intel outdated driver conflict with Windows 10 1903
If you have Intel drivers with release date older than 2017, properly you will be blocked to update Windows 10 build 1903.
My experience is I have a Intel Network Adapter I219-V2 which was using a driver released in 2017 in version 20, somehow Intel discontinued the update of that driver and release a new series of network adapter software, the newest release date is 2019/06/06 in version 12.19.9.8. In a result that it cannot be upgraded by Windows Update nor directly upgraded by Intel Installation Package. I have to manual uninstall everything even the driver itself and install the Intel Installation Package manually in order to update to the newest driver.
Now, Windows 10 allows me to update to 1903.
My experience is I have a Intel Network Adapter I219-V2 which was using a driver released in 2017 in version 20, somehow Intel discontinued the update of that driver and release a new series of network adapter software, the newest release date is 2019/06/06 in version 12.19.9.8. In a result that it cannot be upgraded by Windows Update nor directly upgraded by Intel Installation Package. I have to manual uninstall everything even the driver itself and install the Intel Installation Package manually in order to update to the newest driver.
Now, Windows 10 allows me to update to 1903.
Subscribe to:
Posts (Atom)