Ramblings of an IT Professional (Aaron's Computer Services) Aaron Jongbloedt
Hard drive e·lec·tric·i·ty and performance
Random HardWare: Dell Optiplex USFF, SSDs, battery backed ram, & SIX port NICs?
Firmware Updates on Cisco C220M3 Servers, Flash & Java
TLDR:
To Update Firmware:
-use a really old web browser that has Flash Support, I use Mozilla that is built into Parted Magic circa 2017, log into the CIMC
-launch the remove KVM, feature, save the JNLP file to an USB thumb drive
-run that java file on a computer that has Java installed, after adding the IP of the CIMC into the security exceptions control panel, within 90 seonds of downloading it, else it times out.
-Activate Virtual Boot Devices, mount the ISO, power on the server and choose "Cisco mapped vKVM DVD"
LONG VERSION
Cisco makes some really rock solid hardware, and rightly so considering the price one pays. However Cisco (among others) is not best at providing support in the form of firmware and driver support equipment after they deam them are End-Of-Life.
Cisco's version of IMPI is known as CMC (Cisco Interface Magagment Console?), much like HP's ILO and Dell's iDRAC. It workes(ed) quite well. Lots of details, configurations, and statistics. However It was built on Adobe's Flash technology and the remote IP based KVM is based on Java. Several years ago 2017 is when Flash was set to be sunsetted, for security reasons. Cisco's response was basically more or less: "meh, if you want to run 5 year old servers, you are on your own, buy new stuff".
<taken from Cisco Support site>
Support for Web UI Interface on Cisco UCS M3 Rack Server Software Post Flash Deprecation
The Cisco Cloud and Compute organization at Cisco expects that the Web UI interface of UCS M3 Standalone Rack Server Software – Cisco IMC – will not be accessible on future versions of web browsers that are going to deprecate support for Flash Player based content.
Cisco started shipping UCS C-Series and S-Series M3 Servers in 2012 and announced in 2015 and 2016 the EOL of all M3 rack server models, before Adobe announced the EOL of Flash Player support in July 2017. While we will continue to provide applicable service and support such as critical security fixes via patch releases for M3 servers through the End of Support date in December 2021, we do not plan to retrofit UCS C-Series and S-Series M3 platforms with HTML5-based Web UI interface for Cisco IMC.
Well now, that is just great. Yes these servers were released to the market around 2012, and when Flash was set to die they would have been roughly 5 years old, and outside of the normal 3 year warranty window. Making them roughly 10 year old machines at the time of post. This wouldn't have been to bad of an issue, but browsers and operating systems have made it next to impossible to use Flash and hard to use Java. So manufactures like Cisco made servers with feature we could no longer use, and decided to not give its customers a viable alternative.
Some driver and firmware updates have trickled through, thank you Cisco, however we have issues. In order to obtain firmware updates, one must have a current Cisco Support contract! The downloads are essentially behind a pay-wall! Boo!
Then assuming one can obtain the firmware ISO, the normal thing to do is to write the image to a USB thumb drive, boot the server from that thumb drive which loads a specialized Linux environment to do the updates. However nearly every version yeilds some sort of error during the boot process. I literally tried six version and different ways of writting the ISO's, each had a different failure.
Ok well when one logs into the CIMC there is an option to update the BIOS and some firmware. However when pointing this feature to the various files on that thumb drive (derived from the ISOs) web interface complains.
Random VMware vCenter/ESXi v7.0 issues:
Cannot change Virtual Machine settings:
I had a VM that in the vCenter console I could not change any of the hardware; the OK button was greyed out. If I "Launched the Remote Console" I could change things. Except for the hard drive, it claimed the maximum size it could be expanded to was the current size, and if I tried to resize it I was greated with: "expand disk capacity specified parameter is incorrect dc" Turns out the issue was the virtual serial port was connected. Dispite being able to vmotion the VM. Disconnect it and all was well!
Storage vMotion fails with Error 195887107
In the VMware documentation, it occurs on the virtual machines that have disks with the multi-writer attribute. While in my environment the virtual machine was not like this, after a bit of Google searching, I found a hint in one of the forums that said the error is related to disk size.
Solution
Add 1 GB of space to each disk of the virtual machine to re-size each disk by a factor of 1 MB and then I ran a storage vMotion task on the virtual machine and it completed successfully, but why 1 MB? because of the following description.
“The size of a virtual volume must be a multiple of 1 MB, with a minimum size of 1 MB. As a result, all virtual disks that you provision on a virtual datastore or migrate from any datastore other than the virtual datastore should be an even multiple of 1 MB in size. If the virtual disk you migrate to the virtual datastore is not an even multiple of 1 MB, extend the disk manually to the nearest even multiple of 1 MB.”
Refrence
https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.storage.doc/GUID-EDCF74B5-F652-4F2D-9678-1B188684691D.html?hWord=N4IghgNiBcILYFcIBcCWAHCBTAzgAgHsAzPOAIxAF8g
Thanks to: Yahya Zahedi in the VMware Communities
Cannot change host swap file location
Added a new host to the cluster; the VMware cluster is set to have the host specifiy where VM swap file location is. In the section to make this change all the options are greyed out. Thanks to u/eldego over at Reddit, that this is a bug in the GUI, using the keyboard (arrows and spacebar) to make the slections works. This bug was fixed in VCSA 7.0 U3a.
Cannot create a new datastore:
From vCenter: Task Name: Update disk partitions and Status: Cannot change the host configuration.
From ESXi: Description Creates a new VMFS datastore: State Failed - Cannot change the host configuration.
Errors Failed to update disk partitions for /vmfs/devices/disks/naa.600508b1001c3bfffd4fd3a4b8856609.
Quoting "Cookies04" from the VMware Communities
1. Show connected disks.
ls -lha /vmfs/devices/disks/
(Verify the disk is seen. You will probably see your disk ID then :1. This is a partition on the disk. We only need to work about the main disk ID.)
2. Show the error on disk.
partedUtil getptbl /vmfs/devices/disks/(disk ID)
(It will probably indicate that the GPT is located beyond the end of the disk.)
3. Wipe disk and rewrite with a basic MSDOS partion.
partedUtil setptbl /vmfs/devices/disks/(disk ID) msdos
(The output from this should be similar to msdos and the next line will be o o o o)
"Old" hardware:
VMware, I hate how depricate older hardware!!!! My homelab was running on HP ML350 G6's. They were upgraded from ESXi v6.7 to v7, inplace, not fresh installs. Six months goes by and I just now realize that my 1gbps NICs were not showing. Turns out that the Intel i350 NICs built into the HP are not supported by VMware after v6.7. There is a VERY, VERY long list of hardware Vmware just decided to turn their backs on, including three other different quad and dual port 1gbps NICs I had in my inventory.
I wasn't affected to badly as my server has 10gbps NICs in addtion to the 1gbps. I had a Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet in inventory that I was able to install and configure. It is a very good idea to look at the hardware compatibility list prior to doing upgrades. I found a list of depricaed hardware and edited it, here is the link (make note of the three tabs in this spreadsheet). The Intel i350 NICs (Dell Part Number 0k9cr1) also work
Random Hardware specs...
NVMe SSD's get FASTER
Most of you know SSD's are way faster than spinning, traditional hard drives, as there is no moving parts, just memory chips. Many of you are aware that NVMe is way faster than SSD's, as the SATA controller is bypassed and the I/O happens right on the PCI-e bus. Now there is a newer generation of NVMe hard drives, and they have roughly double the speed of first generation NVMe drives. This new speed is all thanks to the newer PCIe 3.0 x4 interface and NVMe 1.3 protocol.
Mac Pro "TrashCan"
Posting mostly because the hardware is interesting. This MacPro known as late 2013 or 6,1, or as most people refer to it: "The Trashcan". In this particular case two of them are running VMware ESXi v6.5 which is supported by VMware and Apple says it is legal to run as many virtual Mac VM's. Apple claims they only support 32gb of RAM (8gb * 4 slots), but these have 64gb, and others on the internet say it will do 128gb. The CPU is also upgradeable. I did successfully test DDR3 FB ECC RAM out of an HP ProLiant G7. The hard drive is a NVMe,
SuperMicro Cloud Computing "SuperServer" "MicroCloud"
Need a lot of servers in a really small space? How does putting 24 servers into 3U's of space? SuperMicro might have a solution. This particular one is very long in the tooth, but I figure it is worth the share as many of us didn't know the existance of such a beast.
Each of these 3U chassis hold 12 blades. Each blade contains two computers (yes two distict computers sharing one circut board). Each server contains four DDR3 RAM slots, one Intel Xeon E5-26XX CPU, one 2.5" SATA port, two network cards, and a shared IMPI and KVM port.
Motherboard Specs:
https://www.supermicro.com/en/products/motherboard/X10SLE-DF
The chassis:
https://www.supermicro.com/en/products/system/3U/5038/SYS-5038ML-H24TRF.cfm
100Gbps Ethernet Switch!! :O
Repurposing/reformatting used NetApp Drives (520 -> 512 sectors)
TLDR:
From a Linux System:
sg_scan -i <--shows what drives are attached to the system
sg_readcap /dev/sg# <--shows information on the drive in question
sg_format -v --format --size=512 /dev/sg# --six <--reformats the drive in question to 512 sectors
NetApp and other manufactures will often format their drives to a different sector size, 520 is most common. Unfortunately most computers/Operating systems can't deal with them; most only speak 512, or even 4k. In my case I have a bunch of Toshiba 900gb SAS 10k RPM drives with NetApp firmware on them. Interestingly the SAS controller doesn't even show them at post. Using my trusted PartedMagic bootable thumb drive, the normal tools "Disk Health", "Partition Editor", and "Erase Disk" don't even see the disks. They do show up in the hardware inventory though. The solution is to do a low level format of the drives and resetting them to 512 sectors.
Open a command prompt; type: "sg_scan -i"; this shows what drives are attached to the system, in my case the physical drives start with "sg" then a number. In my case it shows SG0 and SG1.
Next verify what the drive specifications are: "sg_readcap /dev/sg0"; in my case it shows that drive is set to a sector size of 520.
Then type: "sg_format -v --format --size=512 /dev/sg0"; in my case I got a message about being illegal. Normally this would work, but something peculiar about how NetApp treats the drives. To get around this add the "--six" parameter. This switch uses 6 byte MODE SENSE/SELECT to probe disk, instead of 10 byte mode; no idea what that means, but whatever it works.
The process took me about 7 hours on a PCI-e LSI SAS2008 Fusion
controller doing a pair of 900gb 10k drives. Reboot the machine, the
drives show up at post, and are usable by the operating system.
Bonus Linux commands
type:
"smartctl --all /dev/sg#" this will show further details on the drive including the hours of usage, power cycles, etc.
"smartctl -H /dev/sg#" this will show health statics
"smartctl -t /dev/sd# short (or long)" this will conducts a smart test, FYI the short test takes about 5 minutes and the long about 2 hours on a 900gb 10k SAS drive






