The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,513 other followers

Archive for the ‘X9SRi-3F’ Category

IPMI will not grab IP even with DHCP turned on : homelab

Posted by jpluimers on 2021/08/13

TL;DR

  1. ensure the IPMI network cable is connected before connecting the power cable
  2. ensure the IPMI LAN is using the dedicated interface
  3. ensure the IPMI LAN interface is connected to a “non green” port of your network switch
  4. ensure the DHCP server has been cold rebooted
  5. ensure the IPMI VLAN configuration matches your network
  6. ensure the IPMI firewall configuration matches the network you try to reach IPMI from
  7. ensure the motherboard does not have a short-circuit anywhere

Otherwise SuperMicro devices might not get a DHCP address on the IPMI (BMC) interface, despite the tooling like [WayBack] ipmicfg indicating getting DHCP was succesful.

This especially holds for X9 boards, likely for newer boards as well.

Personally I never had the 4. and up above, but I bumped into 1. and 2. with SuperMicro boards and 3. with other devices.

Based on

Read the rest of this entry »

Posted in Hardware, Mainboards, Power User, SuperMicro, X9SRi-3F, X9SRi-F | Leave a Comment »

SC732D4-500B | Mid-tower | Chassis | Products | Super Micro Computer, Inc.

Posted by jpluimers on 2021/05/10

The [WayBack] SC732D4-500B | Mid-tower | Chassis | Products | Super Micro Computer, Inc. is a nice tower case, but remember that it has 2 USB 3.0 ports on the outside.

If you have a motherboard without onboard USB 3.0 pin headers, or one with incompatible pin headers, then you cannot use these ports with this standard cable that comes with the case:

Cable(S) CBL-0453L 1 USB 3.0,INT,19 PIN/F TO 19PIN/F,60CM,CONNECT TO CBL-0454L

Most of the X9 motherboards have no compatible pin headers.

These boards are an exception:

Too bad my boards are X9SRI-F and X9SRI-3F (do NOT get the bare X9SRI: it has no iPMI) with C6xx Dual processor Sandy Bridge-based Xeon chipsets (List of Intel Xeon chipsets) – Wikipedia:

This cable might fix this, though there is very little documentation on either of these cables:

Adapter Cable CBL-0454L USB3.0 to 2.0 adapter cable – 30cm(19pin male to 9pin female)

I could find no site with a picture of the first cable, and only newegg had pictures of the last one.

[WayBack] Supermicro CBL-0454L Supermicro CBL-0454L USB 3.0 to USB 2.0 Adapter Cable – Newegg.com

Luckily I had an X10 manual at hand, so here you can see the various pin-outs.

One end of the CBL-0454L has the same pin out as “USB (3.0) USB#11 Pin Definitions” (actually you need to double the rows) so CBL-0453L fits into it.

The other end of CBL-0454L fits into “Front Panel USB (2.0) #4/5, 6/7, 8/9” headers.

Fitting 2.5 inch drives in it

Another interesting aspect is part:

2.5″ HDD Bracket MCP-220-73201-0N HDD Cage (4x Internal 2.5″ fixed HDD bays)

Again hard to find pictures. There is only one at the whole supermicro site:

[WayBack] Supermicro | Products | SuperWorkstation | Mid-Tower | 5039C-T with Part List

[WayBack] 5039C-T_side.jpg

The part is [WayBack] Supermicro MCP-220-73201-0N Accessories with 0091016_2-5in-hdd-cage-4x-internal-2-5in-hdd.jpg (500×500)

–jeroen

Posted in Hardware, Mainboards, Power User, SuperMicro, X9SRi-3F, X9SRi-F | Leave a Comment »

Supermicro: 5 BIOS beeps might just mean internal VGA is disabled

Posted by jpluimers on 2021/05/03

A while ago, I got a second hand Supermicro workstation and wondered why the IPMI KVM would not show anything.

The video card in it worked fine, so I used it as a desktop machine setup for a while, happily running VMS.

I finally decided to move into a closet, so I removed the video card, and rebooted.

Then it beeped 5 times, which was odd: I expected it to switch from the video card to the internal video. It didn’t.

Older BIOS codes: [WayBack] AMI BIOS Beep Codes – Thomas-Krenn-Wiki

From PDF [WayBack] BIOS POST Codes for C7/X9/X10/X11/B9/B10/B1/A1 Motherboards

PEI Beep Codes

# of Beeps Description
1 Memory not Installed
1 Memory was installed twice (InstallPeiMemory routine in PEI Core called twice)
2 Recovery started
3 DXEIPL was not found
3 DXE Core Firmware Volume was not found
4 Recovery failed
4 S3 Resume failed
7 Reset PPI is not available

DXE Beep Codes

# of Beeps Description
1 Invalid password
4 Some of the Architectural Protocols are not available
5 No Console Output Devices are found
5 No Console Input Devices are found
6 Flash update is failed
7 Reset protocol is not available
8 Platform PCI resource requirements cannot be met

So I did a bit of reading in the manual, then found about a jumper which had happily been living out of view, under the video card:

VGA Enable (JPG1)

JPG1 allows you to enable or disable the onboard VGA connector. The default position is on pins 1 and 2 to enable VGA.

Setting the jumper to pins 1&2 made internal VGA available again, it happily booted and showed in the IPMI KVM.

Later I understood why the jumper was set to VGA disabled: when having two video cards, by default Windows will extend your desktop to an invisible monitor.

The easiest workaround for that is just to disable VGA. However, you can also change Windows

Older versus newer boards

It appears that most older SuperMicro systems have a hardware switch, but for newer chipsets supporting Intel Quick Sync Video a there is a BIOS setting: [WayBack] Enable internal graphics in SUPERMICRO servers | Any IT here? Help Me!

Windows 10 fixing video cards and ACPI_BIOS_ERROR

The reboot did not work fine: Windows 10 would not initialise properly, but hung when detecting video cards.

Read the rest of this entry »

Posted in Hardware, IPMI, Mainboards, Power User, SuperMicro, X10SRH-CF, X9SRi-3F, X9SRi-F | Leave a Comment »

Need to do some reading on local domains on the internal network

Posted by jpluimers on 2021/04/09

A long time I wondered why I saw ESXi systems on my local network have two entries in their /etc/hosts file:

[root@ESXi-X10SRH-CF:~] cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1   localhost.localdomain localhost
::1     localhost.localdomain localhost
192.168.71.91   ESXi-X10SRH-CF ESXi-X10SRH-CF

Then I bumped into someone who had a different setup:

[root@ESXi-X10SRH-CF:~] cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1   localhost.localdomain localhost
::1     localhost.localdomain localhost
192.168.0.23    esxi.dynamic.ziggo.nl esxi

So now I knew that the first entry can have a domain resolving it (it still makes be wonder why ziggo is using a top-level domain to resolve local stuff; but searching for  dynamic.ziggo.nl did not get me further on that).

So I installed a quick ESXi machine on that local network, and got the same.

When back home the machine still thought it was esxi.dynamic.ziggo.nl, though clearly I was outside a Ziggo network

I wanted to get rid of it, but that was hard.

Since I forgot to take screenshots beforehand, I can only provide the ones without a search domain bellow.

Reminder to self: visit someone within the Ziggo network, then retry.

Normally you can edit things like these in the default TCP/IP stack. There are two places to change this:

Neither of these allowed me to change it to a situation like this, but luckily the console did.

In the below files, I had to remove the bold parts, then restart the management network (I did keep a text dump, lucky me):

[root@esxi:/etc] grep -inr ziggo .
./vmware/esx.conf:116:/adv/Misc/HostName = "esxi.dynamic.ziggo.nl"
./resolv.conf:2:search dynamic.ziggo.nl 
./hosts:5:192.168.71.194    esxi.dynamic.ziggo.nl esxi
[root@esxi:/etc] cat /etc/resolv.conf 
nameserver 192.168.71.3
search dynamic.ziggo.nl 
[root@esxi:/etc] cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1   localhost.localdomain localhost
::1     localhost.localdomain localhost
192.168.71.194  esxi.dynamic.ziggo.nl esxi

Future steps

  1. Read more on local domains, search domains and related topics
  2. Configure a local domain on my local network, so DHCP hands it out, and DHCP handed out host names are put in the local DNS
  3. Test if all services on all machines still work properly

Reading list

Read the rest of this entry »

Posted in DNS, ESXi6.5, ESXi6.7, Hardware, Internet, Mainboards, Network-and-equipment, Power User, SuperMicro, Virtualization, VMware, VMware ESXi, X10SRH-CF, X9SRi-3F | Leave a Comment »

Running SuperMicro IPMIView on MacOS

Posted by jpluimers on 2021/03/16

I wrote about SuperMicro mainboards and IPMIView recently, but that ran only on Windows and Linux. Since I focus my desktop mainly on MacOS, and never on Linux, I did not want to use the Windows IPMView (though it did work most of the time).

Not having a MacOS version sounded odd, as there was an iOS version:

[WayBack] ‎Supermicro IPMIView on the App Store “This app is only available on the App Store for iOS devices.”

A quick search made me find a few links:

The last one looked most promising, so I forked it.

Following the steps already made me write down a few notes for changes in the README.md file.

But then I bumped into a strange error when wanting to use the KVM Console from IPMIView, as it threw the same error all the time:

".jre/Contents/Home/bin/java": error=2, No such file or directory

I made a quick note in [WayBack] KVM Console cannot start due to java not found · Issue #1 · jpluimers/IPMIView.app · GitHub:

When starting a KVM Console, you get this error: ".jre/Contents/Home/bin/java": error=2, No such file or directory

Try to fix this.

Later I dug a bit deeper, and managed to fix it in the script steps of the README.md:

git clone https://github.com/TheCase/IPMIView.app
pushd IPMIView.app/
mkdir -p Resources/IPMIView
pushd Resources/IPMIView/
tar -zxvf ~/Downloads/IPMIView*.tar.gz --strip=1
pushd jre/
mkdir -p Contents/Home/bin
pushd Contents/Home/bin
ln -s `which java` java
popd
popd
popd
popd
rsync -avlo IPMIView.app/ ~/Applications/IPMIView.app/

Of course I ran into another problem on one of my SuperMicro machines: the KVM Console would consistently crash. Luckily that was solved by a IPMI Firmware Upgrade:

[WayBack] java – Supermicro IPMIView KVM Console does not work at all – Server Fault

The problem was the firmware for the IPMI on these boards was too old (not the same as the BIOS – updating the BIOS will not help in this case). Digging around SuperMicro’s site (never did get a reply from them), I found the Firmware Revision of 3.20 & was able to install it. On the IPMI device tab, under “Device Information”, you should see: Firmware Revision 3.20 IPMI Revision: 2.0 I can now see the KVM Console in both the IPMIView software

–jeroen

Posted in Hardware, IPMI, Mainboards, Power User, SuperMicro, X10SRH-CF, X9SRi-3F | Leave a Comment »

 
%d bloggers like this: