Thomas-Krenn-Wiki - New pages [en]

Thomas-Krenn & Veeam Hardened Repository Hardware Setup

2026-09-29T06:07:53Z

Aranzinger: /* Instructions for BIOS update in Windows */

This article describes how to set up and update the RA1212-AIEPN+ server (Gigabyte MZ33-AR1). It guides you through setting up the hardware RAID in the BIOS and updating the BMC firmware and the BIOS, using the available methods for each.

== Creating the hardware RAID in the BIOS ==
<gallery>
file:Gigabyte Start Screen.png|Start the server and '''click''' '''[Del]''' or '''[F2]''' depending on the server to enter the '''BIOS'''.
file:BIOS Standardansicht.png|In the BIOS, switch to the tab '''"Advanced"'''.
file:BIOS Reiter „Advanced“ .png|In the tab '''"Advanced"''', select the desired '''RAID controller''' by pressing Enter.
file:BIOS Controller-Übersicht prüfen.png|Under the “'''ACTIONS'''” tab, select “'''Configure'''” and press Enter.
file:BIOS „Create Virtual Drive“ .png|In the configuration menu, select „'''Create Virtual''' '''Drive'''“.
file:BIOS Konfigurationsformular.png|Select „'''Select RAID''' '''Level'''“ and open it with Enter.
file:BIOS RAID-Level auswählen.png|Select the '''desired''' '''RAID level'''.
file:BIOS Laufwerk auswählen.png|Open „'''Select Drives'''“ with '''Enter.'''
file:BIOS RAID Controller Laufwerkliste.png|All drives are initially set to "'''Disabled'''".
file:BIOS Laufwerke Markieren.png|Select „'''Check All'''“, to select '''all connected drives'''.
file:BIOS RAID Controller "Apply Changes".png|'''Confirm''' the '''configuration''' with '''Apply Changes''' and Enter.
file:BIOS Bestätigung der Laufwerksauswahl.png|'''Confirm''' „'''OK'''“ with Enter.
file:BIOS Parameter prüfen und speichern.png|Under „'''Virtual''' '''Drive Name'''“, you can optionally enter a name. After this, select '''Save''' '''Configuration'''.
file:BIOS RAID Controller Sicherheitswarnung.png|The BIOS indicates that all data on the selected drives '''will be permanently deleted.'''
file:BIOS „Confirm“ auf Enabled setzen.png|In the '''selection list,''' select „'''Enabled'''“ and '''confirm''' with Enter.
file:BIOS Anlage bestätigen.png|Select „'''Yes'''“ and confirm with '''Enter'''.
file:BIOS Erfolgsmeldung.png|The '''RAID''' is now fully '''configured'''.
file:BIOS Parameter prüfen und speichern.png|With '''[ESC],''' exit the configurator to return to the BIOS “'''Advanced'''” screen
file:BIOS Reiter „Advanced“ .png|Next, switch to the tab "'''Save & Exit'''".
file:BIOS Einstellungen speichern.png|Select „'''Save Changes and Reset'''“.
</gallery>
== Update BMC firmware ==
''Instructions for updating the firmware of the RA1212-AIEPN+ server (Gigabyte MZ33-AR1).''

=== Updating BMC firmware on Linux ===
# Obtain root rights on Linux.
# Navigate to the root directory of the upgrade package
# Select one of the following options for flashing:
#* Execute "ami_bmc_fw_update_linux.sh" to program the AMI firmware.
#* Execute "insyde_bmc_fw_update_linux.sh" to program Insyde firmware.
# Enter "Y/y" to maintain the configuration or "N/n" to reflash the whole BMC firmware.

==== User commands ====

===== Script names =====

* ami_bmc_fw_update_linux.sh – Update script
* insyde_bmc_fw_update_linux.sh – Update script

===== Script =====

* ami_ami_bmc_fw_update_linux.sh [OPTION]
* insyde_bmc_fw_update_linux.sh [OPTION]

===== Description of options =====
This is the script for updating the BMC flash storage. In the following, the options are listed:
# '''cs'''
#* Select this option to update the firmware of the active backup/BMC. (CS=1 is only supported on the GBT Dual platform).
#** 0: Active
#** 1: Backup
#** Default value is 0.
# '''flashall'''
#* Flash the whole BMC without warning message.
#* Default: The user is asked if the configuration should be maintained or not.
# '''preserve'''
#* Flash the BMC and maintain the configuration without warning message.
#* Default: The user is asked if the configuration should be maintained or not.
# '''Architecture'''
#* '''x32'''
#** Set the update tool to 32-bit mode.
#** Default: x86-64-bit mode
#* '''arm'''
#** Sets the update tool to ARM mode (ARM-Linux only supports 64-bit).
#** Default: x86-64-bit mode
''Example of flashing the entire BMC and selecting the BMC address at address 0:''

<syntaxhighlight lang="bash">
ami_bmc_fw_update_linux.sh cs 0 flashall
insyde_bmc_fw_update_linux.sh cs 0 flashall
</syntaxhighlight>

=== Update BMC firmware on Windows ===
# Open the command prompt with Windows administrator privileges.
# Switch to the root directory of the upgrade package.
# Execute "ami_bmc_fw_update_win.bat" to program the AMI firmware.
#* Execute "insyde_bmc_fw_update_win.bat" to program the Insyde firmware.
# Enter „Y/y“ to maintain the configuration or enter "N/n" to reflash the whole BMC firmware.

==== User commands ====

===== Script names =====
* ami_bmc_fw_update_win.bat – Update script
* insyde_fw_update_win.bat – Update script

===== Script =====

* ami_bmc_fw_update_win.bat [OPTION]
* insyde_fw_update_win.bat [OPTION]

===== Description of options =====
Script for flashing the BMC. In the following, the options are listed:

# '''cs'''
#* Select this option to update the firmware of the active/backup BMC. (CS=1 is only supported on the GBT dual platform).
#** 0: Active
#** 1: Backup
#** Default value is 0.
# '''flashall'''
#* Flash the whole BMC without warning message.
#* Default: The user is asked if the configuration should be maintained or not.
# '''preserve'''
#* Flash the BMC and the configuration without maintaining the configuration.
#* Default: The user is asked if the configuration should be maintained.
# '''Architecture'''
#* x32
#** Sets the update tool to the 32-bit mode.
#** Default: x86-64-bit mode

''Example of flashing the entire BMC and selecting the BMC address at address 0:''

<syntaxhighlight lang="bash">
ami_bmc_fw_update_win.bat cs 0 flashall
insyde_bmc_fw_update_win.bat cs 0 flashall
</syntaxhighlight>

=== Update BMC firmware in UEFI ===
# Switch to the root directory of the upgrade package.
# Select one of the following options for flashing:
#* Execute "ami_bmc_fw_update_uefi.nsh" to program AMI-firmware.
#* Execute "insyde_bmc_fw_update_uefi.nsh" to program the Insyde firmware.
# Enter "Y/y" to maintain the configuration or enter "N/n" to flash the whole BMC.
# The function for maintaining the configuration in the ARM_UEFI environment is not supported for the Insyde firmware.

==== User commands ====

===== Script names =====

* ami_bmc_fw_update_uefi.nsh – Update script
* insyde_bmc_fw_update_uefi.nsh – Update script

===== Script =====

* ami_bmc_fw_update_uefi.nsh [OPTION]
* insyde_bmc_fw_update_uefi.nsh [OPTION]

===== Description of options =====
Script for updating the BMC flash storage. In the following, the options are listed:

# '''cs'''
#* Select this option to update the firmware of the active BMC or of the backup BMC. (CS=1 is only supported on the GBT Dual platform).
#** 0: Active
#** 1: Backup
#** The default value is 0.
# '''flashall'''
#* Flashing the whole BMC without warning message.
#* Default: The user is asked if the configuration should be maintained or not.
# '''preserve'''
#* Flash the BMC and the configuration without warning message.
#* Default: The user is asked if the configuration should be maintained or not.
# '''arm'''
#* Sets the update tool to arm mode.
#* Default: x86-64 mode

''Example of flashing the entire BMC and selecting BMC address 0 on x86:''

<syntaxhighlight lang="bash">
ami_bmc_fw_update_uefi.nsh cs 0 flashall
insyde_bmc_fw_update_uefi.nsh cs 0 flashall
</syntaxhighlight>

''Example of flashing the entire BMC and selecting the BMC address at address 0 in UEFI-ARM mode:''

<syntaxhighlight lang="bash">
ami_bmc_fw_update_uefi.nsh cs 0 flashall arm
insyde_bmc_fw_update_uefi.nsh cs 0 flashall arm
</syntaxhighlight>

=== Update BMC firmware via IPMI ===
<gallery widths="150" heights="150">
file:Ipmi dashboard.png|Log in to the IPMI and click on '''Maintenance.'''
file:IPMI Maintenance.png|Select '''Firmware Update'''
file:IPMI Firmware Update.png|Click on '''Dump BIOS''' and then on the folder symbol to select the correct firmware update file (Important: Then click the folder icon and select the correct firmware update file (IMPORTANT: The file extension must be '''.ima_enc''')
file:IPMI Firmware Update Dateiauswahl.png|Verify if the '''.ima_enc''' file is selected and click on '''Start firmware update'''.
file:IPMI Firmware Update Konfi.png|To preserve all configurations, check the box next to “'''Preserve all configurations'''.”
file:IPMI Firmware Update Proceed.png|You can then click '''Proceed to Flash'''. A window labeled '''Update Firmware''' should appear, and the update should begin.
file:IPMI Firmware Update fertig.png|As soon as the update is completed, click on OK (Attention: As soon as you click on OK, '''the server restarts''')
file:IPMI Firmware Update ueberpruefung.png|After restarting the server, you can log in to IPMI again and then check the '''firmware version.'''
</gallery>

== BIOS update ==
''Instructions for updating the BIOS of the RA1212-AIEPN+ server (Gigabyte MZ33-AR1).''

=== Before updating ===
1: Extract the file "MZ33-AR1_R23_F16.zip" to a bootable USB drive formatted with FAT/FAT32.

=== Instructions for updating the BIOS for the EFI shell ===
# Insert the USB flash drive into the system to perform the BIOS upgrade.
# Turn on the system and boot into the built-in shell.
# Enter your USB file system, such as "fs0:" or "fsx:", where "x" is the number of your USB file system.
# Flash script for the BIOS-update:
#* Execute "f_GtoT.nsh" for CPUs of the AMD EPYC 9004 series.
#* Execute "f.nsh" for CPUs of the AMD EPYC 9005 series.
# Once the BIOS flash process is complete, the system must be shut down for the changes to take effect.

=== Instructions for updating the BIOS for Windows ===
# Insert the USB flash drive containing the BIOS update.
# Use the command line.
#* Enter \Tool\WIN\afuwin32 and execute f_GtoT.bat for Windows 32-bit.
#* Enter \Tool\WIN\afuwin64 and execute f_GtoT.bat for Windows 64-bit.
# For CPUs of the AMD EPYC 9005-series:
#* Enter \Tool\WIN\afuwin32 and execute f.bat for Windows 32-bit.
#* Enter \Tool\WIN\afuwin64 and execute .bat for Windows 64-bit.
# Once the BIOS flash is complete, the system must be shut down for the changes to take effect.

=== Instructions for updating the BIOS via IPMI ===
<gallery widths="150" heights="150">
file:Ipmi dashboard.png|Log in to the IPMI and click on '''Maintenance.'''
file:IPMI Maintenance.png|Select '''Firmware Update.'''
file:IPMI Firmware Update.png|Click on '''Dump BIOS'''. After this, click on the folder symbol to select the correct BIOS update file. (IMPORTANT: File extension must be '''.RBU''')
file:IPMI BIOs Update Dateiauswahl.png|Verify if the '''.RBU''' file is selected and click on '''Start firmware update'''.
file:IPMI BIOs Update preserve.png|To maintain all configurations, select the checkbox next to '''Preserve all Configuration.'''
file:IPMI BIOs Update Proceed.png|You can then click '''Proceed to Flash'''. A window labeled '''Update Firmware''' should appear, and the update should begin.
file:IPMI BIOs Update fertig.png|As soon as the update is completed, click on OK (ATTENTION: As soon as you click on OK, '''the server restarts''').
file:IPMI BIOs Update ueberpruefung.png|After restarting the server, you can log in to IPMI again and then check the BIOS version.
</gallery>

{{Presch}}
{{Pstreifinger}}
{{Aranzinger}}
[[Category:Veeam]]
[[de:Thomas-Krenn & Veeam Hardened Repository Hardware Setup]]

Supermicro BMC Safety Instructions September 2026

2026-09-28T08:56:38Z

Aranzinger: Created page with "In '''September 2026''', Supermicro published a security bulletin on '''CVE-2026-33197'''. There is a potential security vulnerability that could allow an attacker to generate additional UEFI boot entries and to boot into the UEFI shell. The pre-boot environment can be manipulated by using shell scripts, for example, to overwrite Secure Boot memory values or to execute malware early in the system boot process. == Overview == {| class="wikitable" |+ !Security vulnerab..."

In '''September 2026''', Supermicro published a security bulletin on '''CVE-2026-33197'''. There is a potential security vulnerability that could allow an attacker to generate additional UEFI boot entries and to boot into the UEFI shell. The pre-boot environment can be manipulated by using shell scripts, for example, to overwrite Secure Boot memory values or to execute malware early in the system boot process.

== Overview ==

{| class="wikitable"
|+
!Security vulnerability
!Risk potential:
|-
| align="center" |[https://www.cve.org/CVERecord?id=CVE-2026-33197 CVE-2026-33197]
| align="center" |8.7 (high)
|-
|}

== Solution for problem ==

Supermicro published a BIOS update, which is able to solve the problem. It is recommended to verify the release notes of the corresponding version.

=== Updates for Thomas-Krenn products ===

Updates on the corresponding system can be found in the <tklink type="sitex" id="440">download area of Thomas-Krenn</tklink>.
The versions have been tested by us to guarantee the stability and compatibility of our systems.

If you require the latest version for your system and it is not yet available in our download area, you can get it at [https://www.supermicro.com/en/support/resources/downloadcenter/swdownload Supermicro].

{{Thomas-Krenn.AG}}
{{Aranzinger}}
[[Category:Server Hardware]]
[[de:Supermicro BMC Sicherheitshinweis September 2026]]

LPI Security Essentials

2026-09-19T13:42:23Z

Wfischer:

'''LPI Security Essentials''' is the entry-level certification in the security field offered by the Linux Professional Institute (LPI). In this wiki article, we outline the detailed learning objectives for the LPI Security Essentials exam (Version 1.0, Exam Code 020-100).<ref>[https://www.lpi.org/our-certifications/exam-020-objectives/ Security Essentials Exam 020 Objectives] (www.lpi.org)</ref>

== Topic 1: Security Concepts ==
{| class="wikitable"
|+
!Subject Area
!Weight
!Key Knowledge Areas
!Partial list of the used files, terms, and utilities
|-
|1.1 Goals, Roles and Actors
|1
|
* Importance of IT security
* Common security goals
* Common roles in security
* Common goals of attacks against IT systems and devices
* Concept of attribution and related issues
|
* Confidentiality, integrity, availability, non-repudiation
* Hackers, crackers, script kiddies
* Black hat and white hat hackers
* Accessing, manipulating or deleting data
* Interrupting services, extorting ransom
* Industrial espionage
|-
|1.2 Risk Assessment and Management
|2
|
* Know common sources for security information
* Security incident classification schema and important types of security vulnerabilities
* Concepts of security assessments and IT forensics
* Awareness of Information Security Management Systems (ISMS) and Information Security Incident Response Plans and Teams
|
* Common Vulnerabilities and Exposures (CVE)
* CVE ID
* Computer Emergency Response Team (CERT)
* Penetration testing
* Untargeted attacks and Advanced Persistent Threats (APT)
* Zero-day security vulnerabilities
* Remote execution and explication of security vulnerabilities
* Privilege escalation due to security vulnerabilities
|-
|1.3 Ethical Behavior
|2
|
* Implications for others of actions taken related to security
* Handling information about security vulnerabilities responsibly
* Handling confidential information responsibly
* Awareness of personal, financial, ecological, and social implication of errors and outages in information technology services
* Awareness of legal implications of security scans, assessments, and attacks
|
* Responsible Disclosure and Full Disclosure
* Bug Bounty programs
* Public and private law
* Penal law, privacy law, copyright law
* Liability, financial compensation claims
|}

== Topic 2: Encryption ==
{| class="wikitable"
|+
!Subject Area
!Weight
!Key Knowledge Areas
!Partial list of the used files, terms, and utilities
|-
|2.1 Cryptography and Public Key Infrastructure
|3
|
* Concepts of symmetric, asymmetric, and hybrid cryptography
* Concept of Perfect Forward Secrecy
* Concepts of hash functions, ciphers, and key exchange algorithms
* Differences between end-to-end encryption and transport encryption
* Concepts of Public Key Infrastructures (PKI), Certificate Authorities, and Trusted Root-CAs
* Concepts X.509 certificates
* How X.509 certificates are requested and issued
* Awareness of certificate revocation
* Awareness of Let’s Encrypt
* Awareness of important cryptographic algorithms
|
* Public Key Infrastructures (PKI)
* Certificate Authorities
* Trusted Root-CAs
* Certificate Signing Requests (CSR) and certificates
* X.509 certificate fields: Subject, Issuer, Validity
* RSA, AES, MD5, SHA-256, Diffie–Hellman key exchange, Elliptic Curve Cryptography
|-
|2.2 Web Encryption
|2
|
* Major differences between plain text protocols and transport encryption
* Concepts of HTTPS
* Important fields in X.509 certificates for the use with HTTPS
* How X.509 certificates are associated with a specific web site
* Validity checks web browsers perform on X.509 certificates
* Determining whether or not a website is encrypted, including common browser messages
|
* HTTPS, TLS, SSL
* X.509 certificate fields: subject, Validity, subjectAltName
|-
|2.3 Email Encryption
|2
|
* Email encryption and email signatures
* OpenPGP
* S/MIME
* Role of OpenPGP key servers
* Role of certificates for S/MIME
* How PGP keys and S/MIME certificates are associated with an email address
* Using Mozilla Thunderbird to send and receive encrypted email using OpenPGP and S/MIME
|
* GnuPGP, GPG keys, key servers
* S/MIME and S/MIME certificates
|-
|2.4 Data Storage Encryption
|2
|
* Concepts of data, file, and storage device encryption
* Using VeraCrypt to store data in an encrypted container or an encrypted storage devices
* Core features of BitLocker
* Using Cryptomator to encrypt files stored in file storage cloud services
|
* VeraCrypt
* BitLocker
* Cryptomator
|}

== Topic 3: Device and Storage Security ==
{| class="wikitable"
|+
!Subject Area
!Weight
!Key Knowledge Areas
!Partial list of the used files, terms, and utilities
|-
|3.1 Hardware Security
|2
|
* Major components of a computer
* Smart devices and the Internet of Things (IoT)
* Security implications of physical access to a computer
* USB devices devices types, connections, and security aspects
* Bluetooth devices types, connections, and security aspects
* RFID devices types, connections, and security aspects
* Awareness of Trusted Computing
|
* Processors, memory, storage, network adapters
* Tablets, smartphones, smart tvs, routers, printers smart home, alarm, IoT devices (e.g. light bulbs, thermostats, TVs)
* USB
* Bluetooth
* RFID
|-
|3.2 Application Security
|2
|
* Common types of software
* Various sources for applications and ways to securely procure and install software
* Updates for firmware, operating systems, and applications
* Sources for mobile applications
* Common security vulnerabilities in software
* Concepts of local protective software
|
* Firmware, operating systems, applications
* App stores
* Local packet filters, endpoint firewalls, application layer firewalls
* Buffer overflows, SQL injections
|-
|3.3 Malware
|3
|
* Common types of malware
* Concepts of rootkit and remote access
* Cirus and malware scanners
* Awareness of the risk of malware used for spying, data exfiltration, and address books copies
|
* Viruses, ransomware, trojan malware, adware, cryptominers
* Backdoors and remote access
* File copying, keylogging, camera, microphone hijacking
|-
|3.4 Data Availability
|2
|
* Importance of backups
* Common backup types and strategies
* Security implications of backups
* Creating and securely storing backups
* Data storage, access, and sharing in cloud services
* Security implications of cloud storage and shared access in the cloud
* Awareness of the dependence on Internet connection and the synchronization of data between cloud services and local storage
|
* Full, differential and incremental backups
* Backup retention
* File sharing cloud services
|}

== Topic 4: Network and Service Security ==
{| class="wikitable"
|+
!Subject Area
!Weight
!Key Knowledge Areas
!Partial list of the used files, terms, and utilities
|-
|4.1 Networks, Network Services and the Internet
|4
|
* Various types of network media and network devices
* Concepts of IP networks and the Internet
* Concepts of routing and Internet Service Providers (ISPs)
* Concepts of MAC and link-layer addresses, IP addresses, TCP and UDP ports, and DNS
* Concepts of cloud computing
|
* Wired networks, WiFi networks, cellular networks
* Switches, Routers, Access Points
* Default Router
* Internet Service Provider
* IPv4, IPv6
* TCP, UDP, ICMP, DHCP
* DNS, DNS host names, forward DNS, reverse DNS
* Cloud computing
* Infrastructure as a Service (IaaS)
* Platform as a Service (PaaS)
* Software as a Service (SaaS)
|-
|4.2 Network and Internet Security
|3
|
* Implications of link layer access
* Risks and secure use of WiFi networks
* Concepts of traffic interception
* Common security threats in the Internet along with approaches of mitigation
|
* Link layer
* Unencrypted and public WiFi
* WiFi security and encryption
* WEP, WPA, WPA2
* Traffic interception
* Man in the Middle attacks
* DoS and DDoS attacks
* Botnets
* Packet filters
|-
|4.3 Network Encryption and Anonymity
|3
|
* Virtual private networks (VPN)
* Concepts of end-to-end encryption
* Anonymity and recognition in the Internet
* Identification due to link layer addresses and IP addresses
* Concepts of proxy servers
* Concepts of TOR
* Awareness of the Darknet
* Awareness of cryptocurrencies and their anonymity aspects
|
* Virtual Private Network (VPN)
* Public VPN providers
* Organization-specific VPN (e.g. company or university VPNs)
* End-to-end encryption
* Transfer encryption
* Anonymity
* Proxy servers
* TOR
* Hidden service
* .onion
* Blockchain
|}

== Topic 5: Identity and Privacy ==
{| class="wikitable"
|+
!Subject Area
!Weight
!Key Knowledge Areas
!Partial list of the used files, terms, and utilities
|-
|5.1 Identity and Authentication
|3
|
* Concepts of digital identities.
* Concepts of authentication, authorization, and accounting
* Characteristics of secure password (e.g. length, special characters, change frequencies, complexity)
* Using a password manager
* Concepts of security questions and account recovery tools
* Concepts of multi-factor authentication (MFA), including common factors
* Concepts of single sign-on (SSO) and social media logins
* Role of email accounts for IT security
* How passwords are stored in online services
* Common attacks against passwords
* Monitoring personal accounts for password leaks (e.g. search engine alerts for usernames and password leak checkers)
* Understanding of the security aspects of online banking and credit cards
|
* Online and offline password managers
* keepass2
* Single sign-on (SSO)
* Two-factor authentication (2FA) and multi-factor authentication (MFA)
* One-time passwords (OTP), time-based one-time passwords (TOTP)
* Authenticator applications
* Password hashing and salting
* Brute force attacks, directory attacks, rainbow table attacks
|-
|5.2 Information Confidentiality and Secure Communication
|2
|
* Implications and risks of data leaks and intercepted communication
* Phishing and social engineering and scamming
* Concepts of email spam filters
* Securely handling of received email attachments
* Sharing information securely and responsibly using email cloud shares and messaging services
* Using encrypted instant messaging
|
* Phishing and social engineering
* Identity theft
* Scamming and scareware
* Email spam, email spam filtering
* Non-disclosure agreements (NDA)
* Information classification
|-
|5.3 Privacy Protection
|2
|
* Importance of personal information
* How personal information can be used for a malicious purpose
* Concepts of information gathering, profiling, and user tracking
* Managing profile privacy settings on social media platforms and online services
* Risk of publishing personal information
* Rights regarding personal information (e.g. GDPR)
|
* Stalking and cybermobbing
* HTTP cookies, browser fingerprinting, user tracking
* Script blockers and ad blockers in web browsers
* Profiles in online services and social media
* Contacts and privacy settings in social media
|}

== Einzelnachweise ==
<references />

{{Wfischer}}
[[Category:LPI Certifications]]
[[de:LPI Security Essentials]]

LVM basics

2026-08-25T11:32:42Z

Aranzinger: Created page with "The '''Logical Volume Manager''' (LVM) allows an abstracted and flexible administration of data storage of a computer system. Compared to the traditional method using partitions, another higher '''abstraction layer''' is introduced that should enable a simpler and more efficient administration and configuration of the data carrier. For example, multiple hard drives can be combined into a '''''logical volume''''' and used as a single data storage unit. Another simplificat..."

The '''Logical Volume Manager''' (LVM) allows an abstracted and flexible administration of data storage of a computer system. Compared to the traditional method using partitions, another higher '''abstraction layer''' is introduced that should enable a simpler and more efficient administration and configuration of the data carrier. For example, multiple hard drives can be combined into a '''''logical volume''''' and used as a single data storage unit. Another simplification offers the opportunity to group Logical Volumes in '''''Volume Groups''''', which can also be given names to. These classifications and naming conventions also provide the administrator with a '''logical reference''' to the data stored in the Logical Volumes.

This article shows the implementation of LVM in Linux.

==Physical Volumes (PVs)==
A PV is always represented by a block device, for example a hard drive (''Device'') or a partition. When a partition or device is initialized as a PV, the block device is marked with an LVM label and populated with metadata. The LVM label identifies the block device as a PV and it includes the ''Random Unique Identifier'' (UUID). It stores the size of the devices in bytes and records where the metadata is located.
<ref>http://www.centos.org/docs/5/html/Cluster_Logical_Volume_Manager/metadata_contents.html</ref>
[[file:Lvm-aufbau.png|200px|thumb|right|Setup PV-VG-LV]]
The metadata is required for the exact descripiton of the Volume Groups. An identical copy of the metadata is stored on the PVs of a VG by default. When creating a PV, it is possible to define that 0, 1 or 2 copies of metadata are stored. Once this number is defined, it can not be changed anymore. Storing the metadata in multiple locations is intended to prevent accidental overwriting.<ref>[http://www.centos.org/docs/5/html/Cluster_Logical_Volume_Manager/physical_volumes.html CentOS LVM Dokumentation]</ref> The size of the metadata area can be also changed when creating a PV. Under circumstances, this area may get too small, which can lead to problems, as this size cannot be changed later: [[LVM VG vgname metadata too large for circular buffer beheben|Fix LVM VG vgname metadata too large for circular buffer]].

When a PV is created, it is divided into many small, equally sized pieces called '''''Physical Extents''''' (PEs).<ref>
http://docs.hp.com/en/B2355-90672/ch03s06.html</ref> These PEs are the smallest possible amount of data that can be allocated. By default, it is 4 MiB, but it can be changed when creating the "volume group" that is based on it. Since the lvm2-format, the number of PEs is not limited anymore. According to Man-Page of vgcreate, a high number of PEs can slow down the provided tools. The I/O performance is, however, not affected.

==Volume Groups (VGs)==
One or more PVs can be summarized to one or more VGs. This VG represents a pool of data storage from which logical volumes can later be allocated.
The storage available of a VG is divided into small, uniformly sized parts, which are ''Logical Extents''. These are the counterparts to the PEs at the PV level. The task of the VG is to assign the '''''Logical Extents''''' to the ''Physical Extents'' correctly. By grouping them in an intermediate layer, PEs from different devices can also be combined into a VG.

==Logical Volumes (LVs)==
VGs are divided into one or more LVs on which the file systems are created. There are three different types of LVs that can be created:
[[file:Linear-lvm.png|150px|thumb|right|Aufbau eines linearen LVs]]
#''Linear Volumes'': A well-organized summary of PEs to a LV. The size of the underlying PVs must not be the same. They are forwarded consolidated to the LVs. Furthermore, a LV does not have to consist of a VG. Multiple LVs can be also created from a VG as long as the VG has enough available storage. The sizes of the generated LVs may vary, but they are at least as large as a PE.
#''Striped Volumes'': As with [http://de.wikipedia.org/wiki/RAID#RAID_00 RAID 0], the data in the Logical Volume (LV) is distributed alternately across the Physical Volumes (PVs). This can, under circumstances, increase the performance, but not the reliability.[[file:Striped-lvm.png|150px|thumb|right|Aufbau eines striped LVs]] The image "Setup of a striped LV" shows how "Stripes" 1 through 6 are written sequentially to the underlying PVs. In this case, it is possible that individual I/O operations can be performed in parallel, thereby speeding up the write operation.
#''Mirrored Volumes'': Similar to [http://de.wikipedia.org/wiki/RAID#RAID_1:_Mirroring_.E2.80.93_Spiegelung RAID 1], the data is mirrored to the underlying devices. Multiple reflections can also be distributed across different “legs”. The device that should be copied is divided in so-called "Regions" that are synchronized when changes are made. The size of these regions is 512KB by default, but can also be changed.<ref>http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/mirror_create.html</ref>

==LVM and Device Mapper==
Since the Linux kernel 2.6, LVM is implemented using the device mapper. LVM uses the ''linear'' Device Mapper Target.<ref>[http://en.wikipedia.org/wiki/LVM2#Implementation LVM2 - Implementation] (en.wikipedia.org)</ref>

==Advantages of using LVMs<ref>[http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/logical_volumes.html Red Hat 6 Documentation LVMs]</ref>==
*Flexible capacities
*:Multiple hard drives can be summarized to a LV.
*Changes in size
*:LVs can be extended or reduced without having to reformat or repartition the underlying devices.
*Reallocation of data during operation
*:Data can be rearranged while the system is running. This may be helpful if a [http://en.wikipedia.org/wiki/Hot_swapping hot-swapable] is swapped.
*Disk striping
*:Data can be simply mirrored.
*Volume snapshots
*:Snapshots can be created from one device, for example to create fuses from the snapshots

==Disadvantages of using LVMs<ref>http://wiki.ubuntuusers.de/Logical_Volume_Manager</ref>==
*If the data is distributed across different devices (“striping”), the risk of a disk failure increases. This can only be considered a drawback of LVM itself to a limited extent, since it is actually a design choice made when structuring the storage architecture.
*To access the data via Live CDs, they must support LVM management. Generally, the access to LVMs is only supported by Linux at the moment.
*The old Grub version could not be used on LVMs. Therefore, a separate, non-LVM boot partition was required. GRUB 2 does not require this anymore.<ref>http://grub.enbug.org/LVMandRAID</ref>

==Instructions and configurations==
The following websites are quite helpful when installing and configuring LVMs:
*http://www.howtoforge.com/linux_lvm
*http://tldp.org/HOWTO/LVM-HOWTO/index.html
*http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/index.html
*http://www.howtogeek.com/howto/40702/how-to-manage-and-use-lvm-logical-volume-management-in-ubuntu/
*http://www.ibm.com/developerworks/linux/library/l-lvm2/index.html
In each individual case, it is necessary to check which LVM tools are being used, since LVM is constantly being further developed. Therefore, new features may be introduced that are not yet available in older versions. You can find out which version of LVM is currently installed as follows:
<pre>
root@ubuntu:~# lvm version
LVM version: 2.02.54(1) (2009-10-26)
Library version: 1.02.39 (2009-10-26)
Driver version: 4.15.0
</pre>

== References ==
<references />

{{Gschoenberger}}
{{Aranzinger}}
[[Category:LVM]]
[[de:LVM Grundlagen]]

Collecting System Statistics on Ubuntu using serverstats

2026-08-25T06:51:24Z

Aranzinger: Created page with "For the analysis of operating system statistics, there are numerous opportunities. For a '''rough analysis''', it is enough to take a closer look at the most important components. The '''rrd'''-used tool '''serverstats''' offers a fast and easy access to statistics and graphs about load, processes, memory and hard drive. In the following article, it is described how to install and configure serverstats on Ubuntu 14.04 LTS. == Installation == The package ''serverstat..."

For the analysis of operating system statistics, there are numerous opportunities. For a '''rough analysis''', it is enough to take a closer look at the most important components. The '''rrd'''-used tool '''serverstats''' offers a fast and easy access to statistics and graphs about load, processes, memory and hard drive. In the following article, it is described how to install and configure serverstats on [[Ubuntu 14.04 LTS]].

== Installation ==
The package ''serverstats'' is located in the Ubuntu repos and is therefore installed via <ref>[http://packages.ubuntu.com/trusty/serverstats Ubuntu Package serverstats] (packages.ubuntu.com)</ref>
<pre>
$ sudo apt-get install serverstats
[...]
The following extra packages will be installed:
libapache2-mod-php5 libc-client2007e libgd3 libjbig0 libjpeg-turbo8 libjpeg8
libmcrypt4 libmysqlclient18 libperl5.18 libsensors4 libsnmp-base libsnmp30
libtiff5 libvpx1 libxpm4 mlock mysql-common php5 php5-cli php5-common
php5-gd php5-imap php5-json php5-mcrypt php5-mysql php5-readline php5-snmp
rrdtool
[...]
The following NEW packages will be installed:
libapache2-mod-php5 libc-client2007e libgd3 libjbig0 libjpeg-turbo8 libjpeg8
libmcrypt4 libmysqlclient18 libperl5.18 libsensors4 libsnmp-base libsnmp30
libtiff5 libvpx1 libxpm4 mlock mysql-common php5 php5-cli php5-common
php5-gd php5-imap php5-json php5-mcrypt php5-mysql php5-readline php5-snmp
rrdtool serverstats
0 upgraded, 29 newly installed, 0 to remove and 0 not upgraded.
Need to get 8,686 kB of archives.
After this operation, 35.6 MB of additional disk space will be used.
[...]
</pre>

== Configuration ==
Useful information on ''serverstats'' can be found in the <code>/usr/share/doc/serverstats/</code> directory:
<source lang="bash">
:/usr/share/doc/serverstats$ ls
changelog.Debian.gz examples graph-config.txt.gz simple-config.txt
copyright faq.txt README.Debian sources.txt.gz
</source>
To make the interface accessible via web-browser, the example configuration for Apache is copied and activated in the corresponding <code>/etc</code>-directory:
<pre>
:/usr/share/doc/serverstats# cp examples/apache.conf /etc/apache2/sites-available/serverstats.conf
# a2ensite serverstats.conf
# service apache2 reload
</pre>

In principle, this completes an initial, simple configuration. The web interface displays the graphs generated from the rrd data:

[[file:ubuntu-serverstats-graph1.png|400px]]

=== Add components ===
The main configuration file for serverstats is located at:
<source lang="bash">
$ ls /etc/serverstats/
graph.php log.php main.php monitor.php rra.php simple.php sources.php
</source>
By default, basic configuration is provided via the ''simple.php'' file. In this file, additional components are now configured. In the following example, the hard drive ''/dev/sda'' (the “disk” section already exists, but ''used'' is set to ''true''):
<source lang="bash">
$ cd /etc/serverstats/
$ sudo vi simple.php
'disk' => array(
'used' => true,
'disks' => array('sda'),
'graphs' => array(
'iorate' => array('used' => true, 'title' => 'IO-Rate (%s)')
)
),
</source>

You can check whether the configuration was successful by verifying whether rrd data has been generated:
<source lang="bash">
$ cd /var/lib/serverstats/rrd
:/var/lib/serverstats/rrd$ ls
cpu.rrd disk_sda.rrd load.rrd memory.rrd traffic_proc_eth0.rrd users.rrd
</source>
The new graphs appear automatically in the web interface because a cron job calls "update.php" every minute:
<source lang="bash">
$ cat /etc/cron.d/serverstats
$ Update the serverstatistic every minute.
* * * * * nobody if [ -x /usr/bin/php5 ] && [ -f /usr/share/serverstats/update.php ]; then /usr/bin/php5 /usr/share/serverstats/update.php > /dev/null; fi
</source>
The structure of the rrd data can be determined from the plugins. In case of a ''disk'' plugin, it is <code>/proc/diskstats</code>:
<source lang="bash">
$ grep diskstats /usr/share/serverstats/sources/disk.php
public function __construct($disk, $withpartitions = false, $sector_size = 512, $path_stat = '/proc/diskstats')
</source>

[[file:ubuntu-serverstats-graph2.png|400px]]

== References ==
<references />

{{Gschoenberger}}
{{Aranzinger}}
[[Category:Ubuntu]]
[[Category:Linux_Performance]]
[[de:System-Statistiken unter Ubuntu mit serverstats sammeln]]

Linux Performance Analysis with collectd

2026-08-21T08:12:12Z

Aranzinger: Created page with "collectd is a daemon that collects system statistics in structured form. The data is in rrd format and can be used for '''performance analysis''' and '''reporting''' of the resource consumption. For the visual representation of the collected collectd-data, there are multiple '''frontends''', which are developed largely independently of collectd. In the following, it is explained how to install and configure collectd on Ubuntu 14.04 LTS. We will also take a look at fr..."

collectd is a daemon that collects system statistics in structured form. The data is in rrd format and can be used for '''performance analysis''' and '''reporting''' of the resource consumption. For the visual representation of the collected collectd-data, there are multiple '''frontends''', which are developed largely independently of collectd. In the following, it is explained how to install and configure collectd on [[Ubuntu 14.04 LTS]]. We will also take a look at front ends that generate '''graphs''' from the collectd rrd-data. Alternatively, [[Serverstats]] or [[Sar]] can also be used for similar analysis.

== Installation ==
For the installation of the minimal collectd-daemon, it is recommended the option ''--no-install-recommends'' on Ubuntu. Otherwise, significantly more packages would be installed. For the general installation and configuration, the following packages are sufficient:
<source lang="bash">
$ sudo apt-get install --no-install-recommends collectd
[...]
The following extra packages will be installed:
collectd-core fontconfig fontconfig-config fonts-dejavu-core libcairo2
libdatrie1 libdbi1 libfontconfig1 libgraphite2-3 libharfbuzz0b libltdl7
libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpixman-1-0 librrd4
libthai-data libthai0 libxcb-render0 libxcb-shm0 libxrender1
Suggested packages:
collectd-dev librrds-perl liburi-perl libhtml-parser-perl
libregexp-common-perl libconfig-general-perl httpd-cgi apache2 apcupsd bind9
hddtemp ipvsadm lm-sensors mbmon memcached mysql-server nginx
notification-daemon nut openvpn olsrd pdns-server postgresql time-daemon
ttf-baekmuk ttf-arphic-gbsn00lp ttf-arphic-bsmi00lp ttf-arphic-gkai00mp
ttf-arphic-bkai00mp
Recommended packages:
libesmtp6 liblvm2app2.2 libmemcached10 libmnl0 libmodbus5 libmysqlclient18
libnotify4 libopenipmi0 liboping0 libperl5.18 libpq5 libprotobuf-c0
librabbitmq1 libsensors4 libsnmp30 libtokyotyrant3 libupsclient3
libvarnishapi1 libvirt0 libyajl2 default-jre-headless rrdtool ttf-dejavu
ttf-bitstream-vera
The following NEW packages will be installed:
collectd collectd-core fontconfig fontconfig-config fonts-dejavu-core
libcairo2 libdatrie1 libdbi1 libfontconfig1 libgraphite2-3 libharfbuzz0b
libltdl7 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpixman-1-0
librrd4 libthai-data libthai0 libxcb-render0 libxcb-shm0 libxrender1
0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,649 kB of archives.
After this operation, 13.6 MB of additional disk space will be used.
[...]
</source>

== Configuration ==
The main configuration file is located at <code>/etc/collectd/collectd.conf</code>. In this file, the so-called plugins control the monitoring and logging of the resource.<ref>[https://collectd.org/wiki/index.php/Table_of_Plugins Table of Plugins] (collectd.org)</ref> By default, several plugins are already active that monitor basic resources:
<pre>
$ egrep '^LoadPlugin' /etc/collectd/collectd.conf
LoadPlugin syslog
LoadPlugin battery
LoadPlugin cpu
LoadPlugin df
LoadPlugin disk
LoadPlugin entropy
LoadPlugin interface
LoadPlugin irq
LoadPlugin load
LoadPlugin memory
LoadPlugin processes
LoadPlugin rrdtool
LoadPlugin swap
LoadPlugin users
</pre>
Detailed configuration options are specified in the plugin's XML sections. In the following example, the hard drive to be monitored is:
<pre>
$ sudo vi /etc/collectd/collectd.conf
<Plugin disk>
Disk "sdb"
IgnoreSelected false
</Plugin>
</pre>
After changing the configuration file, collectd must be restarted:
<pre>
$ sudo service collectd restart
</pre>

== rrd data ==
The generated statistics are located in the <code>/var/lib/collectd/rrd</code> directory. These can be analyzed directly on the host for further analysis or copied to another system. The following paragraph describes how graphs are created from the data.

== Generate Graphs from rrd data ==
To create graphs from the rrd data, some libraries are required for the processing of the rrd data<ref>[https://collectd.org/wiki/index.php/First_steps collectd collectd First Steps] (collectd.org)</ref>
<source lang="bash">
$ sudo apt-get install librrds-perl libconfig-general-perl libhtml-parser-perl libregexp-common-perl libjson-perl
</source>

=== collectd-web ===
An easy and good way to get graph paper is ''collectd-web''.<ref>[https://collectd.org/wiki/index.php/Collectd-web collectd Frontend collectd-web] (collectd.org)</ref><ref>[http://collectdweb.appspot.com/ collectd Website] (collectdweb.appspot.com)</ref>
<source lang="bash">
$ git clone git://github.com/httpdss/collectd-web.git
Cloning into 'collectd-web'...
$ sudo cp -a collectd-web/ /var/www/html/
$ sudo vi /etc/apache2/sites-available/collectd-web.conf
<Directory /var/www/html/collectd-web>
Options Indexes FollowSymLinks MultiViews
AllowOverride all
Order allow,deny
allow from all
</Directory>
$ sudo a2ensite collectd-web
</source>

For Apache, the following settings are required:
<source lang="bash">
$ sudo a2enmod cgi
</source>

After activating the web-configuration for collectd-web, the graphs of the rrd-data is accessible via browser:
<gallery>
Rrd-graph-collectd1.png|collectd performance data on load.
rrd-graph-collectd2.png|collectd performance data on processes and forks.
rrd-graph-collectd3.png|collectd performance data on memory.
rrd-graph-collectd4.png|collectd performance data on disk.
</gallery>

== References ==
<references />

{{Gschoenberger}}
{{Aranzinger}}
[[Category:Ubuntu]]
[[Category:Linux_Performance]]
[[de:Linux Performance Auswertung mit collectd]]

Linux Network Analysis with mtr

2026-08-21T07:01:32Z

Aranzinger:

The network diagnosis tool '''mtr''' (My Traceroute) combines the functionality of the tools [[Linux Netzwerk Analyse mit traceroute|traceroute]] and ping in an individual program. It can be used as text-based ncurses program or as graphical GTK+ program. [http://www.bitwizard.nl/mtr/ mtr] has been developed by BitWizard B.V., which is a Dutch company.

== Function ==

The program is called up on the command line together with a host as parameter. For the "Host" field, enter the hostname or IP address to which you want to test the connection from the current computer:

mtr www.google.com

After the DNS trigger, mtr sends multiple ICMP ''echo requests'' (Pings) to the resolved IP address. However, the TTL (Time to live) is limited in the IP package. The first ICMP echo request only has a TTL of 1. The next request has a TTL of 2 and so on. Due to this limited TTL, the IP packet is discarded at the first, second, etc., hop (router). The router in question then responds with an ICMP "Time-to-live exceeded" message. As a result, mtr receives such a message from each router and thus knows which routers are along the path to the host.

After the TTL has been increased until the host is finally reached, mtr starts over from the beginning. Over time, mtr then calculates average values, best-case values, and worst-case values.

== Installation ==

mtr is already included with most Linux distributions. It can be installed via the respective package management with the following package names:
* Red Hat/CentOS/Fedora/SuSE: '''mtr''' (text version), '''mtr-gtk''' (graphical version)
* Debian/Ubuntu: '''mtr-tiny''' (text version), '''mtr''' (text version and graphical version)

== Example ==

The following examples show some mtr requests. The first three hops, however, have been anonymized.

=== Interactive output ===

The following output shows the mtr command being run. On Debian/Ubuntu, the parameter -t is required for the console version if the package mtr is installed (and not mtr-tiny):

mtr www.google.com

<pre>
My traceroute [v0.80]
tpw (0.0.0.0) Wed Dec 18 09:24:14 2013
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. dsldevice.lan 0.0% 24 68.4 66.2 4.8 100.6 23.8
2. XXXXX(Provider)XXXXX.at 0.0% 24 19.8 20.6 19.1 29.6 2.5
3. 195.3.66.157 0.0% 24 19.7 21.2 19.0 51.4 6.7
4. 195.3.68.1 0.0% 24 22.3 25.5 21.8 42.3 6.3
5. 195.3.70.154 0.0% 24 22.3 25.6 22.0 51.1 8.3
6. 62.47.120.150 0.0% 24 26.3 27.4 26.1 38.6 2.9
7. 209.85.243.119 0.0% 24 26.9 26.8 26.3 27.5 0.3
8. 209.85.241.212 0.0% 24 64.1 49.5 38.6 73.8 14.0
9. 209.85.251.249 0.0% 24 38.4 39.8 38.0 47.1 2.2
10. 209.85.242.49 0.0% 24 39.5 39.0 38.4 39.6 0.3
11. fra02s17-in-f20.1e100.net 0.0% 24 39.0 38.6 38.1 39.1 0.3
</pre>

=== Report output ===

mtr can also be executed in a report mode (<code>-r</code>). The number of requests is stated with the parameter <code>-c</code>. With <code>-w</code>, it is achieved, that long host names are displayed completely and not cut off:

<pre>
user@tpw:~$ mtr -r -w -c 10 www.google.com
HOST: tpw Loss% Snt Last Avg Best Wrst StDev
1.|-- dsldevice.lan 0.0% 10 96.9 42.2 1.3 99.8 47.3
2.|-- XXXXX(Provider)XXXXX.at 0.0% 10 19.9 20.7 19.4 28.3 2.7
3.|-- 195.3.66.157 0.0% 10 19.6 19.4 18.9 20.1 0.3
4.|-- 195.3.68.1 0.0% 10 21.9 22.3 21.9 22.7 0.2
5.|-- 195.3.70.186 0.0% 10 22.5 29.8 22.2 87.5 20.4
6.|-- 62.47.120.150 10.0% 10 46.2 34.3 26.3 76.8 17.2
7.|-- 209.85.243.119 0.0% 10 26.7 27.3 26.4 33.0 2.0
8.|-- 209.85.241.212 0.0% 10 51.9 54.6 40.1 61.6 6.1
9.|-- 209.85.251.249 0.0% 10 38.9 38.8 38.7 39.0 0.1
10.|-- 209.85.242.49 0.0% 10 39.7 39.3 38.8 40.2 0.4
11.|-- fra02s17-in-f18.1e100.net 0.0% 10 39.0 38.6 38.2 39.0 0.2
user@tpw:~$
</pre>

=== Graphical output ===

The graphical version is started with the xmtr command or with mtr at Debian/Ubuntu:

xmtr www.google.com

[[file:Ubuntu-mtr-My-traceroute-Screenshot.png|left|thumb|250px|The command xmtr (mtr on Debian/Ubuntu) launches the graphical version of mtr from the command line (My traceroute)]] 

== Analysis ==

For more distant sites, you can determine which hops (routers) are connected by [http://de.wikipedia.org/wiki/Seekabel submarine cable] connections (for example, across the Atlantic).

For more distant pages, you can use the respective "round-trip time" to determine which hops (routers) are involved [http://de.wikipedia.org/wiki/Seekabel submarine cable] connections (for example, across the Atlantic). This can be seen when analyzing the connection to www.areca.com.tw:

<pre>
user@tpw:~$ mtr -r -w -c 10 www.areca.com.tw
HOST: tpw Loss% Snt Last Avg Best Wrst StDev
1.|-- dsldevice.lan 0.0% 10 42.9 63.0 42.7 97.5 21.8
2.|-- 194-166-175-254.adsl.highway.telekom.at 0.0% 10 19.5 20.8 19.4 28.9 3.0
3.|-- 195.3.66.157 0.0% 10 18.7 19.3 18.5 19.8 0.4
4.|-- 195.3.68.1 0.0% 10 21.9 27.1 21.7 70.7 15.3
5.|-- 195.3.70.178 10.0% 10 22.5 25.4 21.8 39.3 6.3
6.|-- win-b4-link.telia.net 0.0% 10 22.7 22.7 22.4 23.0 0.2
7.|-- prag-bb1-link.telia.net 0.0% 10 28.9 28.7 28.4 29.2 0.3
8.|-- ffm-bb1-link.telia.net 0.0% 10 99.3 56.1 46.7 99.3 18.9
9.|-- ash-bb3-link.telia.net 30.0% 10 142.3 149.8 136.7 193.0 19.5
| `|-- 213.155.131.145
| |-- 213.155.135.61
| |-- 80.91.250.203
| |-- 213.155.135.57
10.|-- sjo-bb1-link.telia.net 80.0% 10 215.8 212.9 210.0 215.8 4.1
| `|-- 213.155.135.129
11.|-- chunghwa-ic-155505-sjo-bb1.c.telia.net 80.0% 10 204.6 208.6 204.6 212.7 5.7
12.|-- r4001-s2.tp.hinet.net 50.0% 10 346.3 345.5 343.3 346.4 1.3
13.|-- 220-128-12-2.HINET-IP.hinet.net 90.0% 10 341.3 341.3 341.3 341.3 0.0
14.|-- tpdt-3011.hinet.net 90.0% 10 346.4 346.4 346.4 346.4 0.0
15.|-- TCHN-3011.hinet.net 80.0% 10 357.6 358.1 357.6 358.5 0.6
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
user@tpw:~$
</pre>

This query apparently travels between the following routers via a long submarine cable connection across the ocean, as indicated by the large differences in the average ping times (Avg):
* between hop 8 (56.1 ms) and 9 (149.8 ms)
* between hop 11 (208.6 ms) and 12 (345.5 ms)

== More information ==
* Information on normal traceroute on Linux: [[Linux Netzwerk Analyse mit traceroute|Linux Network Analysis with traceroute]]

{{Wfischer}}
{{Aranzinger}}
[[Category::Linux-Netzwerk]][[Category:Linux Performance]]
[[de:Linux Netzwerk Analyse mit mtr]]

UEFI Secure Boot

2026-08-20T10:57:27Z

Aranzinger: /* Recommendations from Canonical */

Secure Boot is a part of the UEFI specification that should guarantee the authenticity of important software parts. Critical parts of the firmware, such as the OS loader, should only be executed if they have been authorized to do so in advance by a trusted institution. Therefore, rootkits are excluded that take root even before the operating system (OS) boots.

Cryptographic mechanisms ([https://de.wikipedia.org/wiki/Elektronische_Signatur Signatures]) avoid that untrusted software components are executed.

The key in the UEFI firmware verify the authenticity of, for example, bootloaders. A bootloader is only executed if it presents a valid "signature". <ref name=ozlabs>[http://ozlabs.org/docs/uefi-secure-boot-impact-on-linux.pdf UEFI Secure Boot Impact on Linux] (ozlabs.org)</ref> If a signature can not be verified or is not valid, the system can not start. For example, if the bootloader's signature does not match the one expected by the UEFI firmware, the system will not boot.

== Current information ==
* [http://blog.hansenpartnership.com/wp-uploads/2013/02/UEFI-Secure-Boot-2013.pdf UEFI Secure Boot - Where we stand] (LCA2013, James Bottomley) (blog.hansenpartnership.com)
* [http://www.linuxtag.org/2013/fileadmin/www.linuxtag.org/slides/Dr._Udo_Seidel_-_UEFI_Secure_Boot__The_story_behind_and_where_Linux_stands.e343.pdf UEFI Secure Boot - The story behind and where Linux stands] (LinuxTag 2013, Dr. Udo Seidel) (linuxtag.org)

== Advantages of Secure Boot ==
Using Secure Boot offers the following benefits:
* Malware protection: Secure Boot is particularly effective at detecting rootkits that infiltrate critical parts of the operating system before the actual boot process begins.
* The signature system allows specific software to be excluded, ensuring that only the desired software is used.

== Disadvantages of Secure Boot ==
* Above all, the fact that the Platform Key (PK; see below) is not under the end customer's control turns out to be a disadvantage.
* For Secure Boot, all software components must be signed accordingly. This also applies to the associated hardware drivers for the firmware. For the subsequent installation of hardware systems, it must be made sure that the key from the hardware manufacturer of the new component is stored on the system.<ref name=ozlabs />

Choice of the operating system:
* Alternative operating systems or Dual Boot configurations are made more difficult by Secure Boot. The fact that Linux installations can now only be performed after manually disabling Secure Boot in the UEFI firmware creates yet another obstacle to using Linux.
* With Dual Boot, you would even have to constantly switch between Secure Boot and Non-Secure Boot in order to boot signed and unsigned operating systems.

=== Recommendations from Canonical ===
In a [http://blog.canonical.com/2011/10/28/white-paper-secure-boot-impact-on-linux/ whitepaper from Canonical] (blog.canonical.com), the following recommendations about Secure Boot are stated:
* Factory default: At this time, it is not yet clear whether Linux can be used out of the box. With Secure Boot disabled by default, it would be easier to use Linux. However, this setting is controversial from a security standpoint, as it allows unsigned OS loaders to run.

* For the use of Custom firmwares, there must be a possibility to reconfigure the keys in setup mode. A GUI or a user interface would be necessary. Given the limited user base, it is questionable whether firmware manufacturers will offer this feature.

* The UEFI system should be shipped in Setup mode (see below), which allows the first signature keys to be added to the signature databases during OS installation. This prevents keys from being present on the system at the time of delivery—against the user's wishes—that would exclude other systems.

== Secure Boot and Windows 8/Server2012 ==
The Windows 8 Certification Requirements<ref>[http://msdn.microsoft.com/library/windows/hardware/hh748188 Windows 8 Hardware Certification Requirements] (msdn.microsoft.com)</ref> - for the certification of hardware - prescribe the following things for the Secure Boot (page 188ff, excerpts from this):
* ''Mandatory. Secure Boot must ship enabled'' - Secure Boot is activated per default.
**''Note II: Windows Server systems may ship with Secure Boot disabled, but all other provisions of this sub-requirement must be met'' - A deactivated Secure Boot is allowed for Windows Server.
*''Mandatory. When Secure Boot is Enabled, Compatibility Support Modules (CSM) must NOT be loaded'' - It is not possible anymore to boot in Legacy Mode (CSM) with activated Secure Boot.
*''Mandatory. Support for the UEFI "forbidden" signature database'' - A database to revoke/black list signatures must be supported.
*''Mandatory. Secure firmware update process'' - A secure firmware update process so that only signed firmware is installed. Furthermore, the Secure Boot Public Key is also protected.

== Secure Boot and Linux ==
The above mentioned requirements for Windows 8 as well as Windows Server 2012 certified hardware have a larger influence on the use of common distributions with Secure Boot.

For information on the current approach to '''installation''' under Secure Boot, see the wiki article [[Installing Operating Systems on UEFI Systems]].

When the Secure Boot issue first arose, distribution vendors responded as follows:
* '''Ubuntu'''
** [https://lists.ubuntu.com/archives/ubuntu-devel/2012-June/035445.html UEFI Secure Boot and Ubuntu - implementation] (ubuntu-devel Mailing List, Posting von Steve Langasek, 22.06.2012)
** [http://www.heise.de/open/meldung/Ubuntu-bekommt-von-Microsoft-signierten-Loader-fuer-Secure-Boot-Systeme-1624326.html Ubuntu receives from Microsoft signed loader for Secure-Boot-Systems] (heise open, 22.06.2012)
** [http://www.heise.de/open/meldung/Ubuntu-UEFI-Secure-Boot-mit-Grub-2-1714764.html Ubuntu: UEFI Secure Boot with Grub 2] (heise open, 21.09.2012)
** [http://www.pro-linux.de/news/1/18910/canonical-aendert-plan-fuer-secure-boot.html Canonical changes plan for Secure Boot] (pro-linux.de, 21.09.2012)
* '''Fedora'''
** [http://mjg59.dreamwidth.org/16863.html UEFI Secure boot in Fedora: status update] (Matthew Garrett's Blog)
** [http://www.heise.de/open/meldung/Fedora-18-soll-UEFI-Secure-Boot-unterstuetzen-1650141.html Fedora 18 should support UEFI Secure Boot] (heise open, 24.07.2012)
** [https://fedoraproject.org/wiki/Features/SecureBoot Features/SecureBoot] (fedoraproject.org/wiki)
* '''SUSE'''
** [https://www.suse.com/blogs/uefi-secure-boot-details/ SUSE and Secure Boot: The Details] (SUSE Blog)
** [http://www.heise.de/open/meldung/UEFI-Secure-Boot-fuer-Suse-Linux-1664594.html UEFI Secure Boot for Suse-Linux] (heise open, 10.08.2012)
* More information:
** [http://www.heise.de/newsticker/meldung/Linux-auf-Secure-Boot-Geraeten-installieren-1741789.html Install Linux on Secure-Boot-Devices] (heise open, 01.11.2012)

== Technical function ==
=== Available key ===
Secure Boot relies heavily on the use of asymmetric cryptography. The root of trust is granted to the owner of a so-called '''Platform Key''' (PK). Another pair of keys - '''Key Exchange Keys''' (KEKs) - is also located in the firmware.

According to the specifications, the purpose of PK and KEK is the following:<ref name="uefi-spec">[http://www.uefi.org/specs/ UEFI Specification page 1451] (uefi.org/specs)</ref>
*The PKs develop a base of trust between the platform owner and the platform firmware.
*The KEKs develop a base of trust between the operating system and the platform firmware.
The key is located in the so-called "Signature Databases", that are databases in which they are stored.
The following "trust databases" are used:<ref name='dep-secb'>[http://www.uefi.org/learning_center/1_-_UEFI_Summit_Deploying_Secure_Boot_July_2012.pdf Deploying Secure Boot: Key Creation and Management] (uefi.org)</ref>
*Platform Key Database
**Objects for modifying the KEKs.
* Key Exchange Key Database
**Objects for modification of KEKs.
*Key Exchange Key Database
**Includes those trust objects that are permitted to modify the allowed and forbidden signature databases.
*Allowed/Authorized signature database
**Includes those trust objects that are used for the signature verification of the firmware (for example signed firmware driver).
*Forbidden database
**Contains signatures that have been revoked and who are therefore no longer trusted.

=== Firmware mode ===
Without a PK, the UEFI system is in '''Setup Mode''', in which the PK and KEK databases can be modified and populated without authentication. After the PK is loaded, the UEFI platform is in '''user mode''', and remains there until the PK is removed (PK clear).
In principle, both the PK and the KEK can be changed as desired in setup mode. In user mode, they can only be changed if they are signed with the firmware's current PK. According to the specifications, the following schema results: PK and KEK can only be changed if:<ref name='uefi-spec' />
*In the setup mode, when PKpub is signed with its associated PKpriv.
* In user mode, when the PKpub is signed with the current PKpriv of the firmware.

KEKs can always be read but only be written, when:
*in setup mode (without authentication)
*in user mode, when the KEK is signed with the current PKpriv of the firmware.

The owner of the PK is typically the "platform owner". The KEKs are under control of the OEM or OS-seller.

Microsoft demands for Windows 8 that Secure Boot is activated per default. A technet-article describes how the database keys interact with each other:<ref>[http://technet.microsoft.com/en-us/library/hh824987.aspx Secure Boot Overview] (technet.microsoft.com)</ref>
<blockquote>
''The Key Enrollment Key database (KEK) is a separate database of signing keys that can be used to update the signature database and revoked signatures database. Microsoft requires a specified key to be included in the KEK database so that in the future Microsoft can add new operating systems to the signature database or add known bad images to the revoked signatures database.''

''The OEM stores the signature database, revoked signatures database, and KEK signature databases on the firmware nonvolatile RAM (NV-RAM) at manufacturing time. These signature databases must be included to boot Windows by using Secure Boot.''

''After these databases have been added, and after final firmware validation and testing, the OEM locks the firmware from editing, except for updates that are signed with the correct key or updates by a physically present user who is using firmware menus, and then generates a platform key (PK). The PK can be used to sign updates to the KEK or to turn off Secure Boot.''
</blockquote>
In summary, this leads to the following key points:
*Microsoft possesses in KEK a key that allows to add new signed OS and to revoke software parts.
*The signature databases are stored in the firmware's NVRAM at the time of manufacture.
*Using a Platform Key (PK) provided by the manufacturer, you can update the KEKs or disable Secure Boot.

== References ==
<references />

{{Aranzinger}}
[[Category:UEFI]]

Safety Information on Intel Products 2026.3 IPU

2026-08-18T10:08:53Z

Aranzinger:

In August '''2026''', Intel published new security advisories on different Intel products as part of the IPU 2026.3. Some of these safety instructions require '''firmware updates'''.

In this article, you will find an excerpt and hints on these security advisories as well as information on where to find updates on Thomas-Krenn products.

== Affected systems ==

* Intel Xeon processors
* Intel Core processors
* Intel Atom processors
* Intel Pentium processors
* Intel Celeron processors

== Security advisories ==
In this table, you will find safety instructions on the firmware that has been published by Intel.

{| class="wikitable"
|- style="background-color: #EFEFEF; font-weight: bold;"
! align="center" |Intel security advisory
! align="center" |Title
! align="center" |Affected systems
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01475.html INTEL-SA-01475]
|align=center | Intel® Slim Bootloader Advisory
| rowspan="47" align="left" | (see Intel-SA)
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01443.html INTEL-SA-01443]
|align=center | 2026.3 IPU, 3rd Gen Intel® Xeon® Scalable Processor Firmware Advisory
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01442.html INTEL-SA-01442]
|align=center | 2026.3 IPU, Intel® Xeon® Processor Firmware Advisory
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01441.html INTEL-SA-01441]
|align=center | 2026.3 IPU, Intel® Processor Firmware Advisory
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01439.html INTEL-SA-01439]
|align=center | Intel® Xeon® processor with Alias Checking Trusted Module Advisory
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01437.html INTEL-SA-01437]
|align=center | 2026.3 IPU, Intel® UEFI Firmware Advisory
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01436.html INTEL-SA-01436]
|align=center | 2026.3 IPU, Intel® Trust Domain Extensions (Intel® TDX) module Advisory
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01435.html INTEL-SA-01435]
|align=center | Intel® Processor Firmware Advisory - 01435
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01428.html INTEL-SA-01428]
|align=center | Intel® Processor Firmware Advisory - 01428
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01427.html INTEL-SA-01427]
|align=center | 2026.3 IPU, Intel® Chipset Firmware Advisory
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01423.html INTEL-SA-01423]
|align=center | 2026.3 IPU, Intel® Processor Load Value Injection Zero Data Advisory
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01419.html INTEL-SA-01419]
|align=center | 2026.2 IPU, Intel® Trust Domain Extensions (Intel® TDX) module Advisory
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01404.html INTEL-SA-01404]
|align=center | Intel® Xeon® 6 processor with Intel® TDX Advisory
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01379.html INTEL-SA-01379]
|align=center | Intel® Xeon® 6 Processor Firmware Advisory
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01372.html INTEL-SA-01372]
|align=center | VRT0010, Intel® Chipset Firmware Advisory
|-
|align=center | [https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01371.html INTEL-SA-01371]
|align=center | VRT0011, Intel® Chipset Firmware Advisory
|}

== Updates for Thomas-Krenn products ==
Updates for the corresponding system can be found in the <tklink type="sitex" id="440">Thomas-Krenn download area</tklink>.
The updates in the download area have been tested by us to guarantee the stability and compatibility of our systems.

If you require the latest version for your system and it is not yet available in our download area, you can get it at [https://www.asus.com/de/support/download-center/ Asus], [https://www.supermicro.com/en/support/resources/downloadcenter/swdownload Supermicro] or [https://www.gigabyte.com/de/Support/Consumer/Download Gigabyte].

== More information ==
* [https://www.intel.com/content/www/us/en/security-center/default.html Security Center] (www.intel.com)
* [https://www.supermicro.com/en/support/security_Intel_IPU2026.3 Intel Platform Update (IPU) Update 2026.3, August 2026] (www.supermicro.com)
* [https://www.supermicro.com/en/support/security_Intel_IPU2026.2_part2 Intel Platform Update (IPU) Update 2026.2 Part 2, August 2026] (www.supermicro.com)
* [https://www.heise.de/news/Flawed-x86-instruction-bypasses-trivial-protection-mechanism-11409272.html A flawed x86 instruction bypasses a trivial protection mechanism] (heise.de, August 2026)
* [https://www.phoronix.com/news/Intel-CPU-microcode-20260811 Intel CPU microcode 20260811 release fixes eight security issues] (phoronix.com, August 2026)
* [https://www.heise.de/news/The-Security-Co-Processor-is-unsafe-in-many-CPUs-11411837.html The Security-Coprocessor is unsafe in many CPUs] (heise.de, August 2026)
{{Thomas-Krenn.AG}}
{{Aranzinger}}
[[Category:Intel]]
[[de:Sicherheitshinweise zu Intel Produkten 2026.3 IPU]]

AMD Safety Vulnerabilities - August 2026

2026-08-18T07:15:25Z

Aranzinger:

On '''August 11th, 2026''', AMD published security bulletins with safety vulnerabilities. '''AMD-SB-3033'''<ref>[https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3033.html SEV Firmware Arbitrary Code Execution] (www.amd.com/en/resources/product-security)</ref> and '''AMD-SB-7064'''<ref>[https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7064.html Trusted Platform Module (TPM) Reference Code Errata] (www.amd.com/en/resources/product-security)</ref> can be resolved with firmware updates.

== Affected systems ==

* Systems with AMD Ryzen Threadripper PRO 3000WX processors
* Systems with AMD Ryzen Threadripper PRO 5000WX processors
* Systems with AMD Ryzen Threadripper 7000 / PRO 7000WX processors

'''AMD EPYC systems:'''

* Systems with "Zen 4" [[AMD EPYC 4004 Raphael]] processors
* Systems with "Zen 5" [[AMD EPYC 4005 Grado]] processors
* Systems with "Zen 3" [[AMD EPYC 7003 Milan]] processors
* Systems with "Zen 4" [[AMD EPYC 9004 Genoa and Bergamo]] & 8004 Siena processors
* Systems with "Zen 5" [[AMD EPYC 9005 Turin]] processors

== Problem solution ==

Here is a tabular list of the corresponding CVEs and corrective measures for the respective generation, if available.

'''AMD EPYC 4004 Raphael / 4005 Grado'''

{| class="wikitable"
|+
!Safety Vulnerability
!Risk potential:
! align="center" |'''Platform Initialization Version'''
|-
| align="center" |[https://www.cve.org/CVERecord?id=CVE-2026-6726 CVE-2026-6726]
| align="center" |8.5 (high)
| align="center" |ComboAM5PI 1.2.0.3k (2026-05-31)
|-
| align="center" |[https://www.cve.org/CVERecord?id=CVE-2026-6727 CVE-2026-6727]
| align="center" |8.3 (high)
| align="center" |ComboAM5PI 1.2.0.3k (2026-05-31)
|-
|}

'''AMD EPYC 7003 Milan'''

{| class="wikitable"
|+
!Safety vulnerability
! align="center" |'''Platform Initialization Version'''
|-
| align="center" |[https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3033.html AMD-SB-3033]
| align="center" |MilanPI 1.0.0.J (2025-12-02)
|-
|}

'''AMD EPYC 9004 Genoa / Bergamo & EPYC 8004 Siena:'''

{| class="wikitable"
|+
!Safety vulnerability
! align="center" |'''Platform Initialization Version'''
|-
| align="center" |[https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3033.html AMD-SB-3033]
| align="center" |GenoaPI 1.0.0.H (2025-12-02)
|-
|}

'''AMD EPYC 9005 Turin / Turin Dense'''

{| class="wikitable"
|+
!Safety vulnerability
! align="center" |'''Platform Initialization Version'''
|-
| align="center" |[https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3033.html AMD-SB-3033]
| align="center" |Turin PI-SP5 1.0.0.8 (2025-11-10)
|-
|}

'''AMD Ryzen Threadripper PRO 3000WX'''

{| class="wikitable"
|+
!Safety vulnerability
!Risk potential:
! align="center" |'''Platform Initialization Version'''
|-
| align="center" |[https://www.cve.org/CVERecord?id=CVE-2026-6726 CVE-2026-6726]
| align="center" |8.5 (high)
| align="center" |ChagallWSPI-sWRX8 1.0.0.f (2026-05-17)
CastlePeakWSPI-sWRX8 1.0.0.J (2026-05-17)
|-
| align="center" |[https://www.cve.org/CVERecord?id=CVE-2026-6727 CVE-2026-6727]
| align="center" |8.3 (high)
| align="center" |ChagallWSPI-sWRX8 1.0.0.f (2026-05-17)
CastlePeakWSPI-sWRX8 1.0.0.J (2026-05-17)
|-
|}

'''AMD Ryzen Threadripper PRO 5000WX'''

{| class="wikitable"
|+
!Safety vulnerability
!Risk potential:
! align="center" |'''Platform Initialization Version'''
|-
| align="center" |[https://www.cve.org/CVERecord?id=CVE-2026-6726 CVE-2026-6726]
| align="center" |8.5 (high)
| align="center" |ChagallWSPI-sWRX8 1.0.0.f (2026-05-17)
|-
| align="center" |[https://www.cve.org/CVERecord?id=CVE-2026-6727 CVE-2026-6727]
| align="center" |8.3 (high)
| align="center" |ChagallWSPI-sWRX8 1.0.0.f (2026-05-17)
|-
|}

'''AMD Ryzen Threadripper 7000 / PRO 7000WX'''

{| class="wikitable"
|+
!Safety vulnerability
!Risk potential:
! align="center" |'''Platform Initialization Version'''
|-
| align="center" |[https://www.cve.org/CVERecord?id=CVE-2026-6726 CVE-2026-6726]
| align="center" |8.5 (high)
| align="center" |StormPeakPI-SP6_1.1.0.0l (2026-05-11)
StormPeakPI-SP6_1.0.0.1n (2026-05-11)
|-
| align="center" |[https://www.cve.org/CVERecord?id=CVE-2026-6727 CVE-2026-6727]
| align="center" |8.3 (high)
| align="center" |StormPeakPI-SP6_1.1.0.0l (2026-05-11)
StormPeakPI-SP6_1.0.0.1n (2026-05-11)
|-
|}

Supermicro Security Bulletins for the safety vulnerabilities have already been published. A list with BIOS-versions of the respective mainboards, to close the gaps, is also available. In the following, there is an excerpt from this table, in which all mainboards, that are offered by Thomas-Krenn, are listed: <ref>[https://www.supermicro.com/en/support/security_center#!advisories Supermicro Security Center] (www.supermicro.com)</ref>

{| class="wikitable"
|+
!AMD motherboard
! align="center" |'''BIOS version'''
|-
| align="center" |H12SSW-iN/NT
| align="center" |3.6
|-
| align="center" |H12SSL-i/C/CT/NT
| align="center" |3.6
|-
| align="center" |H12DSi-N6/NT6
| align="center" |3.6
|-
| align="center" |H13SSW
| align="center" |3.8
|-
| align="center" |H13SSL-N/NC
| align="center" |3.8
|}

=== Updates for Thomas-Krenn products ===
Updates for respective system can be found in the <tklink type="sitex" id="440">Thomas-Krenn download area</tklink>.
The versions in the download area have been tested by us to guarantee the stability and compatibility of our systems.

If you require the latest version for your system and it is not yet available in our download area, you can get it at [https://www.asus.com/de/support/download-center/ Asus] or [https://www.supermicro.com/en/support/resources/downloadcenter/swdownload Supermicro].

== Sources ==
* [https://www.heise.de/news/Der-Security-Ko-Prozessor-in-vielen-CPUs-ist-unsicher-11411837.html The Security Coprocessor is unsafe in many CPUs] (heise.de, August 2026)
* [https://www.golem.de/news/sicherheitsluecken-zwei-fehler-hebeln-tpm-schutz-aus-2608-211899.html Two vulnerabilities bypass TPM protection] (golem.de, August 2026)

== References ==
<references/>

{{Thomas-Krenn.AG}}
{{Aranzinger}}
[[Category:AMD Safety Information]]
[[de:AMD Sicherheitslücken - August 2026]]

OPNsense plugins

2026-08-11T07:12:58Z

Aranzinger: Created page with "The functions of the Open Source firewall OPNsense can be extended by multiple '''plugins'''. The following table shows the plugins available with the corresponding version numbers (OPNsense version 25.1.1): {| class="wikitable" !Plugin !Version !Description |- |os-acme-client |4.11 |ACME Client |- |os-apcupsd |1.2_3 |APCUPSD - APC UPS daemon |- |os-beats |1 |Send logs, network, metrics and heartbeat to Elasticsearch |- |os-bind |1.34_2 |BIND domain name service |-..."

The functions of the Open Source firewall [[OPNsense]] can be extended by multiple '''plugins'''.

The following table shows the plugins available with the corresponding version numbers (OPNsense version 25.1.1):

{| class="wikitable"
!Plugin
!Version
!Description
|-
|os-acme-client
|4.11
|ACME Client
|-
|os-apcupsd
|1.2_3
|APCUPSD - APC UPS daemon
|-
|os-beats
|1
|Send logs, network, metrics and heartbeat to Elasticsearch
|-
|os-bind
|1.34_2
|BIND domain name service
|-
|os-c-icap
|1.9
|c-icap connects the web proxy with a virus scanner
|-
|os-cache
|1.0_1
|Webserver cache
|-
|os-caddy
|2.0.4_2
|Modern Reverse Proxy with Automatic HTTPS, Dynamic DNS and Layer4 Routing
|-
|os-chrony
|1.5_3
|Chrony time synchronisation
|-
|os-clamav
|1.8.1
|Antivirus engine for detecting malicious threats
|-
|os-collectd
|1.4_1
|Collect system and application performance metrics periodically
|-
|os-cpu-microcode-amd
|1.1
|AMD CPU microcode updates
|-
|os-cpu-microcode-intel
|1.1
|Intel CPU microcode updates
|-
|os-crowdsec
|1.0.12
|Lightweight and collaborative security engine
|-
|os-ddclient
|1.28
|Dynamic DNS client
|-
|os-debug
|1.7
|Debugging Tools
|-
|os-dec-hw
|1.1_3
|Deciso hardware specific information
|-
|os-dmidecode
|1.2
|Display hardware information on the dashboard
|-
|os-dnscrypt-proxy
|1.16
|Flexible DNS proxy supporting DNSCrypt and DoH
|-
|os-etpro-telemetry
|1.8
|ET Pro Telemetry Edition
|-
|os-freeradius
|1.9.28_1
|RADIUS Authentication, Authorization and Accounting Server
|-
|os-frr
|1.49
|The FRRouting Protocol Suite
|-
|os-ftp-proxy
|1.0_4
|Control ftp-proxy processes
|-
|os-gdrive-backup
|1
|Backup configurations using Google Drive
|-
|os-git-backup
|1.1_1
|Track config changes using git
|-
|os-google-cloud-sdk
|1.0_1
|Google Cloud SDK
|-
|os-grid_example
|1.1
|A sample framework application
|-
|os-haproxy
|4.6_1
|Reliable, high performance TCP/HTTP load balancer
|-
|os-helloworld
|1.4_1
|A sample framework application
|-
|os-hw-probe
|1.0_1
|Collect hardware diagnostics
|-
|os-igmp-proxy
|1.5_6
|IGMP-Proxy Service
|-
|os-intrusion-detection-content-et-open
|1.0.2_2
|IDS Proofpoint full ET open ruleset complementary subset for ET Pro Telemetry edition
|-
|os-intrusion-detection-content-et-pro
|1.0.2_1
|IDS Proofpoint ET Pro ruleset (needs a valid subscription)
|-
|os-intrusion-detection-content-ptopen
|1
|IDS Positive Technologies ESC ruleset
|-
|os-intrusion-detection-content-snort-vrt
|1.2
|IDS Snort VRT ruleset (needs registration or subscription)
|-
|os-iperf
|1.0_2
|Connection speed tester
|-
|os-lcdproc-sdeclcd
|1.1_1
|LCDProc for SDEC LCD devices
|-
|os-lldpd
|1.2
|LLDP allows you to know exactly on which port is a server
|-
|os-maltrail
|1.10_1
|Malicious traffic detection system
|-
|os-mdns-repeater
|1.2
|Proxy multicast DNS between networks
|-
|os-munin-node
|1.1_1
|Munin monitoring agent
|-
|os-ndp-proxy-go
|1.1
|IPv6 Neighbor Discovery Protocol (NDP) Proxy
|-
|os-ndproxy
|1.1
|Neighbor Discovery Proxy
|-
|os-net-snmp
|1.6
|Net-SNMP is a daemon for the SNMP protocol
|-
|os-netbird
|1.1
|Peer-to-peer VPN that seamlessly connects your devices
|-
|os-netdata
|1.2_1
|Real-time performance monitoring
|-
|os-nextcloud-backup
|1.0_1
|Track config changes using NextCloud
|-
|os-nginx
|1.35_4
|Nginx HTTP server and reverse proxy
|-
|os-node_exporter
|1.2
|Prometheus exporter for machine metrics
|-
|os-nrpe
|1.1_1
|Execute nagios plugins
|-
|os-ntopng
|1.3
|Traffic Analysis and Flow Collection
|-
|os-nut
|1.9_1
|Network UPS Tools
|-
|os-openconnect
|1.4.6
|OpenConnect Client
|-
|os-openvpn-legacy
|1
|OpenVPN legacy support
|-
|os-OPNProxy
|1.0.5_4
|OPNsense proxy additions
|-
|os-postfix
|1.24
|SMTP mail relay
|-
|os-puppet-agent
|1.2
|Manage Puppet Agent
|-
|os-qemu-guest-agent
|1.3
|QEMU Guest Agent for OPNsense
|-
|os-radsecproxy
|1.1
|RADIUS proxy provides both RADIUS UDP and TCP/TLS (RadSec) transport
|-
|os-realtek-re
|1
|Realtek re(4) vendor driver
|-
|os-redis
|1.1_3
|Redis DB
|-
|os-relayd
|2.9_2
|Relayd Load Balancer
|-
|os-rfc2136
|1.9_4
|RFC-2136 Support
|-
|os-rspamd
|1.13_2
|Protect your network from spam
|-
|os-sftp-backup
|1.1_2
|Backup configurations using SFTP
|-
|os-shadowsocks
|1.3
|Secure socks5 proxy
|-
|os-siproxd
|1.3_3
|Siproxd is a proxy daemon for the SIP protocol
|-
|os-smart
|2.4
|SMART tools
|-
|os-squid
|1.4
|Squid is a caching proxy for the web
|-
|os-sslh
|1.0_1
|sslh configuration front-end
|-
|os-strongswan-legacy
|1
|IPsec legacy support
|-
|os-stunnel
|1.0.6_1
|Stunnel TLS proxy
|-
|os-sunnyvalley
|1.5_1
|Vendor Repository for Zenarmor (Enterprise Security Modules - NGFW, SSE, SASE, f.k.a Sensei)
|-
|os-tailscale
|1.3
|VPN mesh securely connecting clients using WireGuard
|-
|os-tayga
|1.3
|Tayga NAT64
|-
|os-telegraf
|1.12.13
|Agent for collecting metrics and data
|-
|os-tftp
|1
|TFTP server
|-
|os-theme-advanced
|1.1
|Theme based on AdvancedTomato GUI
|-
|os-theme-cicada
|1.4
|The cicada theme - dark grey onyx
|-
|os-theme-flexcolor
|1
|Theme with 3 different color schemes: black as default, light and dark-light
|-
|os-theme-rebellion
|1.9.3
|A suitably dark theme
|-
|os-theme-tukan
|1.3
|The tukan theme - blue/white
|-
|os-theme-vicuna
|1.5
|The vicuna theme - blue sapphire
|-
|os-tinc
|1.7_4
|Tinc VPN
|-
|os-tor
|1.1
|The Onion Router
|-
|os-turnserver
|1.1
|The coturn STUN/TURN Server
|-
|os-udpbroadcastrelay
|1.0_5
|Control udpbroadcastrelay processes
|-
|os-upnp
|1.8
|UPnP IGD & PCP/NAT-PMP Service
|-
|os-virtualbox
|1.0_1
|VirtualBox guest additions
|-
|os-vmware
|1.5_1
|VMware tools
|-
|os-vnstat
|1.3_1
|Network traffic monitor
|-
|os-wazuh-agent
|1.2_3
|Agent for the open source security platform Wazuh
|-
|os-wol
|2.5_3
|Wake on LAN Service
|-
|os-xen
|1.2_1
|Xen guest utilities
|-
|os-zabbix6-agent
|1.18
|Zabbix monitoring agent
|-
|os-zabbix6-proxy
|1.16
|Zabbix monitoring proxy
|-
|os-zabbix7-agent
|1.18
|Zabbix monitoring agent
|-
|os-zabbix7-proxy
|1.16
|Zabbix monitoring proxy
|-
|os-zabbix72-agent
|1.18
|Zabbix monitoring agent
|-
|os-zabbix72-proxy
|1.16
|Zabbix monitoring proxy
|-
|os-zabbix74-agent
|1.18
|Zabbix monitoring agent
|-
|os-zabbix74-proxy
|1.16
|Zabbix monitoring proxy
|-
|os-zerotier
|1.3.2_6
|Virtual Networks That Just Work

|}

{{Wfischer}}
{{Aranzinger}}
[[Category:OPNsense]]
[[Category:Review 2025 Q3]]
[[de:OPNsense Plugins]]

Update VMware ESXi

2026-08-06T10:45:03Z

Aranzinger: /* References */

Updates for VMware ESXi can be easily installed via the command line, even for the free version of the ESXi hypervisor. In this example, we explain how to install updates via command line using [[VMware ESXi 6.7]].<ref>[https://kb.vmware.com/articleview?docid=2008939 “esxcli software vib” commands to patch an ESXi 5.x/6.x host] (kb.vmware.com, VMware Knowledge Base Article 2008939)</ref>

== Download updates ==
In the following knowledge base article about VMware, you will find information on how to download the updates that are currently available for your system:
* https://kb.vmware.com/s/article/1021623
<gallery>
File:ESXi-6.7-Update-01-Downloads.png|Download available updates from VMware.
</gallery>

== Load updates to EXSi host ==
In the next step, load the updates to the ESXi host. This is, for example, possible by using the datastore browser in the vSphere web client.
<gallery>
File:ESXi-6.7-Update-02-Web-Client.png|Open datastore browser.
File:ESXi-6.7-Update-03-New-Directory.png|Create new directory.
File:ESXi-6.7-Update-04-Upload.png|Click on upload and select files.
File:ESXi-6.7-Update-05-Files.png|Files have been uploaded.
</gallery>

== Install updates on the command line ==
Activate the SSH shell in the web client, stop or migrate all virtual machines and put the host into maintenance mode:
[root@localhost:~] vim-cmd hostsvc/maintenance_mode_enter

Next, install the updates on the esxcli command as follows:
<pre>
[root@localhost:~] esxcli software vib update -d /vmfs/volumes/datastore1/updates/ESXi670-201806001.zip
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: VMware_bootbank_cpu-microcode_6.7.0-0.14.8941472, VMware_bootbank_esx-base_6.7.0-0.14.8941472, VMware_bootbank_vsan_6.7.0-0.14.8941472, VMware_bootbank_vsanhealth_6.7.0-0.14.8941472, VMware_locker_tools-light_10.2.1.8267844-8941472
VIBs Removed: VMware_bootbank_cpu-microcode_6.7.0-0.0.8169922, VMware_bootbank_esx-base_6.7.0-0.0.8169922, VMware_bootbank_vsan_6.7.0-0.0.8169922, VMware_bootbank_vsanhealth_6.7.0-0.0.8169922, VMware_locker_tools-light_10.2.0.7253323-8169922
VIBs Skipped: VMW_bootbank_ata-libata-92_3.00.9.2-16vmw.670.0.0.8169922, VMW_bootbank_ata-pata-amd_0.3.10-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-atiixp_0.4.6-4vmw.670.0.0.8169922, VMW_bootbank_ata-pata-cmd64x_0.2.5-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-pdc2027x_1.0-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-serverworks_0.4.3-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-sil680_0.4.8-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-via_0.3.3-2vmw.670.0.0.8169922, VMW_bootbank_block-cciss_3.6.14-10vmw.670.0.0.8169922, VMW_bootbank_bnxtnet_20.6.101.7-11vmw.670.0.0.8169922, VMW_bootbank_brcmfcoe_11.4.1078.0-8vmw.670.0.0.8169922, VMW_bootbank_char-random_1.0-3vmw.670.0.0.8169922, VMW_bootbank_ehci-ehci-hcd_1.0-4vmw.670.0.0.8169922, VMW_bootbank_elxiscsi_11.4.1174.0-2vmw.670.0.0.8169922, VMW_bootbank_elxnet_11.4.1094.0-5vmw.670.0.0.8169922, VMW_bootbank_hid-hid_1.0-3vmw.670.0.0.8169922, VMW_bootbank_i40en_1.3.1-18vmw.670.0.0.8169922, VMW_bootbank_iavmd_1.2.0.1011-2vmw.670.0.0.8169922, VMW_bootbank_igbn_0.1.0.0-15vmw.670.0.0.8169922, VMW_bootbank_ima-qla4xxx_2.02.18-1vmw.670.0.0.8169922, VMW_bootbank_ipmi-ipmi-devintf_39.1-4vmw.670.0.0.8169922, VMW_bootbank_ipmi-ipmi-msghandler_39.1-4vmw.670.0.0.8169922, VMW_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.670.0.0.8169922, VMW_bootbank_iser_1.0.0.0-1vmw.670.0.0.8169922, VMW_bootbank_ixgben_1.4.1-11vmw.670.0.0.8169922, VMW_bootbank_lpfc_11.4.33.1-6vmw.670.0.0.8169922, VMW_bootbank_lpnic_11.4.59.0-1vmw.670.0.0.8169922, VMW_bootbank_lsi-mr3_7.702.13.00-4vmw.670.0.0.8169922, VMW_bootbank_lsi-msgpt2_20.00.04.00-4vmw.670.0.0.8169922, VMW_bootbank_lsi-msgpt35_03.00.01.00-10vmw.670.0.0.8169922, VMW_bootbank_lsi-msgpt3_16.00.01.00-1vmw.670.0.0.8169922, VMW_bootbank_misc-cnic-register_1.78.75.v60.7-1vmw.670.0.0.8169922, VMW_bootbank_misc-drivers_6.7.0-0.0.8169922, VMW_bootbank_mtip32xx-native_3.9.6-1vmw.670.0.0.8169922, VMW_bootbank_ne1000_0.8.3-4vmw.670.0.0.8169922, VMW_bootbank_nenic_1.0.11.0-1vmw.670.0.0.8169922, VMW_bootbank_net-bnx2_2.2.4f.v60.10-2vmw.670.0.0.8169922, VMW_bootbank_net-bnx2x_1.78.80.v60.12-2vmw.670.0.0.8169922, VMW_bootbank_net-cdc-ether_1.0-3vmw.670.0.0.8169922, VMW_bootbank_net-cnic_1.78.76.v60.13-2vmw.670.0.0.8169922, VMW_bootbank_net-e1000_8.0.3.1-5vmw.670.0.0.8169922, VMW_bootbank_net-e1000e_3.2.2.1-2vmw.670.0.0.8169922, VMW_bootbank_net-enic_2.1.2.38-2vmw.670.0.0.8169922, VMW_bootbank_net-fcoe_1.0.29.9.3-7vmw.670.0.0.8169922, VMW_bootbank_net-forcedeth_0.61-2vmw.670.0.0.8169922, VMW_bootbank_net-igb_5.0.5.1.1-5vmw.670.0.0.8169922, VMW_bootbank_net-ixgbe_3.7.13.7.14iov-20vmw.670.0.0.8169922, VMW_bootbank_net-libfcoe-92_1.0.24.9.4-8vmw.670.0.0.8169922, VMW_bootbank_net-mlx4-core_1.9.7.0-1vmw.670.0.0.8169922, VMW_bootbank_net-mlx4-en_1.9.7.0-1vmw.670.0.0.8169922, VMW_bootbank_net-nx-nic_5.0.621-5vmw.670.0.0.8169922, VMW_bootbank_net-tg3_3.131d.v60.4-2vmw.670.0.0.8169922, VMW_bootbank_net-usbnet_1.0-3vmw.670.0.0.8169922, VMW_bootbank_net-vmxnet3_1.1.3.0-3vmw.670.0.0.8169922, VMW_bootbank_nhpsa_2.0.22-1vmw.670.0.0.8169922, VMW_bootbank_nmlx4-core_3.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_nmlx4-en_3.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_nmlx4-rdma_3.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_nmlx5-core_4.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_nmlx5-rdma_4.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_ntg3_4.1.3.0-1vmw.670.0.0.8169922, VMW_bootbank_nvme_1.2.1.34-1vmw.670.0.0.8169922, VMW_bootbank_nvmxnet3-ens_2.0.0.21-1vmw.670.0.0.8169922, VMW_bootbank_nvmxnet3_2.0.0.27-1vmw.670.0.0.8169922, VMW_bootbank_ohci-usb-ohci_1.0-3vmw.670.0.0.8169922, VMW_bootbank_pvscsi_0.1-2vmw.670.0.0.8169922, VMW_bootbank_qcnic_1.0.2.0.4-1vmw.670.0.0.8169922, VMW_bootbank_qedentv_2.0.6.4-8vmw.670.0.0.8169922, VMW_bootbank_qfle3_1.0.50.11-9vmw.670.0.0.8169922, VMW_bootbank_qfle3f_1.0.25.0.2-14vmw.670.0.0.8169922, VMW_bootbank_qfle3i_1.0.2.3.9-3vmw.670.0.0.8169922, VMW_bootbank_qflge_1.1.0.11-1vmw.670.0.0.8169922, VMW_bootbank_sata-ahci_3.0-26vmw.670.0.0.8169922, VMW_bootbank_sata-ata-piix_2.12-10vmw.670.0.0.8169922, VMW_bootbank_sata-sata-nv_3.5-4vmw.670.0.0.8169922, VMW_bootbank_sata-sata-promise_2.12-3vmw.670.0.0.8169922, VMW_bootbank_sata-sata-sil24_1.1-1vmw.670.0.0.8169922, VMW_bootbank_sata-sata-sil_2.3-4vmw.670.0.0.8169922, VMW_bootbank_sata-sata-svw_2.3-3vmw.670.0.0.8169922, VMW_bootbank_scsi-aacraid_1.1.5.1-9vmw.670.0.0.8169922, VMW_bootbank_scsi-adp94xx_1.0.8.12-6vmw.670.0.0.8169922, VMW_bootbank_scsi-aic79xx_3.1-6vmw.670.0.0.8169922, VMW_bootbank_scsi-bnx2fc_1.78.78.v60.8-1vmw.670.0.0.8169922, VMW_bootbank_scsi-bnx2i_2.78.76.v60.8-1vmw.670.0.0.8169922, VMW_bootbank_scsi-fnic_1.5.0.45-3vmw.670.0.0.8169922, VMW_bootbank_scsi-hpsa_6.0.0.84-3vmw.670.0.0.8169922, VMW_bootbank_scsi-ips_7.12.05-4vmw.670.0.0.8169922, VMW_bootbank_scsi-iscsi-linux-92_1.0.0.2-3vmw.670.0.0.8169922, VMW_bootbank_scsi-libfc-92_1.0.40.9.3-5vmw.670.0.0.8169922, VMW_bootbank_scsi-megaraid-mbox_2.20.5.1-6vmw.670.0.0.8169922, VMW_bootbank_scsi-megaraid-sas_6.603.55.00-2vmw.670.0.0.8169922, VMW_bootbank_scsi-megaraid2_2.00.4-9vmw.670.0.0.8169922, VMW_bootbank_scsi-mpt2sas_19.00.00.00-2vmw.670.0.0.8169922, VMW_bootbank_scsi-mptsas_4.23.01.00-10vmw.670.0.0.8169922, VMW_bootbank_scsi-mptspi_4.23.01.00-10vmw.670.0.0.8169922, VMW_bootbank_scsi-qla4xxx_5.01.03.2-7vmw.670.0.0.8169922, VMW_bootbank_shim-iscsi-linux-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-iscsi-linux-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libata-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libata-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libfc-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libfc-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libfcoe-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libfcoe-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-vmklinux-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-vmklinux-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-vmklinux-9-2-3-0_6.7.0-0.0.8169922, VMW_bootbank_smartpqi_1.0.1.553-10vmw.670.0.0.8169922, VMW_bootbank_uhci-usb-uhci_1.0-3vmw.670.0.0.8169922, VMW_bootbank_usb-storage-usb-storage_1.0-3vmw.670.0.0.8169922, VMW_bootbank_usbcore-usb_1.0-3vmw.670.0.0.8169922, VMW_bootbank_vmkata_0.1-1vmw.670.0.0.8169922, VMW_bootbank_vmkfcoe_1.0.0.0-1vmw.670.0.0.8169922, VMW_bootbank_vmkplexer-vmkplexer_6.7.0-0.0.8169922, VMW_bootbank_vmkusb_0.1-1vmw.670.0.0.8169922, VMW_bootbank_vmw-ahci_1.2.0-6vmw.670.0.0.8169922, VMW_bootbank_xhci-xhci_1.0-3vmw.670.0.0.8169922, VMware_bootbank_elx-esx-libelxima.so_11.4.1184.0-0.0.8169922, VMware_bootbank_esx-dvfilter-generic-fastpath_6.7.0-0.0.8169922, VMware_bootbank_esx-ui_1.25.0-7872652, VMware_bootbank_esx-xserver_6.7.0-0.0.8169922, VMware_bootbank_lsu-hp-hpsa-plugin_2.0.0-13vmw.670.0.0.8169922, VMware_bootbank_lsu-lsi-lsi-mr3-plugin_1.0.0-12vmw.670.0.0.8169922, VMware_bootbank_lsu-lsi-lsi-msgpt3-plugin_1.0.0-8vmw.670.0.0.8169922, VMware_bootbank_lsu-lsi-megaraid-sas-plugin_1.0.0-9vmw.670.0.0.8169922, VMware_bootbank_lsu-lsi-mpt2sas-plugin_2.0.0-7vmw.670.0.0.8169922, VMware_bootbank_native-misc-drivers_6.7.0-0.0.8169922, VMware_bootbank_qlnativefc_3.0.1.0-5vmw.670.0.0.8169922, VMware_bootbank_rste_2.0.2.0088-7vmw.670.0.0.8169922, VMware_bootbank_vmware-esx-esxcli-nvme-plugin_1.2.0.32-0.0.8169922
[root@localhost:~] esxcli software vib update -d /vmfs/volumes/datastore1/updates/ESXi670-201807001.zip
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: VMW_bootbank_qedentv_2.0.6.4-10vmw.670.0.17.9214924, VMware_bootbank_esx-base_6.7.0-0.17.9214924, VMware_bootbank_vsan_6.7.0-0.17.9214924, VMware_bootbank_vsanhealth_6.7.0-0.17.9214924
VIBs Removed: VMW_bootbank_qedentv_2.0.6.4-8vmw.670.0.0.8169922, VMware_bootbank_esx-base_6.7.0-0.14.8941472, VMware_bootbank_vsan_6.7.0-0.14.8941472, VMware_bootbank_vsanhealth_6.7.0-0.14.8941472
VIBs Skipped: VMW_bootbank_ata-libata-92_3.00.9.2-16vmw.670.0.0.8169922, VMW_bootbank_ata-pata-amd_0.3.10-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-atiixp_0.4.6-4vmw.670.0.0.8169922, VMW_bootbank_ata-pata-cmd64x_0.2.5-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-pdc2027x_1.0-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-serverworks_0.4.3-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-sil680_0.4.8-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-via_0.3.3-2vmw.670.0.0.8169922, VMW_bootbank_block-cciss_3.6.14-10vmw.670.0.0.8169922, VMW_bootbank_bnxtnet_20.6.101.7-11vmw.670.0.0.8169922, VMW_bootbank_brcmfcoe_11.4.1078.0-8vmw.670.0.0.8169922, VMW_bootbank_char-random_1.0-3vmw.670.0.0.8169922, VMW_bootbank_ehci-ehci-hcd_1.0-4vmw.670.0.0.8169922, VMW_bootbank_elxiscsi_11.4.1174.0-2vmw.670.0.0.8169922, VMW_bootbank_elxnet_11.4.1094.0-5vmw.670.0.0.8169922, VMW_bootbank_hid-hid_1.0-3vmw.670.0.0.8169922, VMW_bootbank_i40en_1.3.1-18vmw.670.0.0.8169922, VMW_bootbank_iavmd_1.2.0.1011-2vmw.670.0.0.8169922, VMW_bootbank_igbn_0.1.0.0-15vmw.670.0.0.8169922, VMW_bootbank_ima-qla4xxx_2.02.18-1vmw.670.0.0.8169922, VMW_bootbank_ipmi-ipmi-devintf_39.1-4vmw.670.0.0.8169922, VMW_bootbank_ipmi-ipmi-msghandler_39.1-4vmw.670.0.0.8169922, VMW_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.670.0.0.8169922, VMW_bootbank_iser_1.0.0.0-1vmw.670.0.0.8169922, VMW_bootbank_ixgben_1.4.1-11vmw.670.0.0.8169922, VMW_bootbank_lpfc_11.4.33.1-6vmw.670.0.0.8169922, VMW_bootbank_lpnic_11.4.59.0-1vmw.670.0.0.8169922, VMW_bootbank_lsi-mr3_7.702.13.00-4vmw.670.0.0.8169922, VMW_bootbank_lsi-msgpt2_20.00.04.00-4vmw.670.0.0.8169922, VMW_bootbank_lsi-msgpt35_03.00.01.00-10vmw.670.0.0.8169922, VMW_bootbank_lsi-msgpt3_16.00.01.00-1vmw.670.0.0.8169922, VMW_bootbank_misc-cnic-register_1.78.75.v60.7-1vmw.670.0.0.8169922, VMW_bootbank_misc-drivers_6.7.0-0.0.8169922, VMW_bootbank_mtip32xx-native_3.9.6-1vmw.670.0.0.8169922, VMW_bootbank_ne1000_0.8.3-4vmw.670.0.0.8169922, VMW_bootbank_nenic_1.0.11.0-1vmw.670.0.0.8169922, VMW_bootbank_net-bnx2_2.2.4f.v60.10-2vmw.670.0.0.8169922, VMW_bootbank_net-bnx2x_1.78.80.v60.12-2vmw.670.0.0.8169922, VMW_bootbank_net-cdc-ether_1.0-3vmw.670.0.0.8169922, VMW_bootbank_net-cnic_1.78.76.v60.13-2vmw.670.0.0.8169922, VMW_bootbank_net-e1000_8.0.3.1-5vmw.670.0.0.8169922, VMW_bootbank_net-e1000e_3.2.2.1-2vmw.670.0.0.8169922, VMW_bootbank_net-enic_2.1.2.38-2vmw.670.0.0.8169922, VMW_bootbank_net-fcoe_1.0.29.9.3-7vmw.670.0.0.8169922, VMW_bootbank_net-forcedeth_0.61-2vmw.670.0.0.8169922, VMW_bootbank_net-igb_5.0.5.1.1-5vmw.670.0.0.8169922, VMW_bootbank_net-ixgbe_3.7.13.7.14iov-20vmw.670.0.0.8169922, VMW_bootbank_net-libfcoe-92_1.0.24.9.4-8vmw.670.0.0.8169922, VMW_bootbank_net-mlx4-core_1.9.7.0-1vmw.670.0.0.8169922, VMW_bootbank_net-mlx4-en_1.9.7.0-1vmw.670.0.0.8169922, VMW_bootbank_net-nx-nic_5.0.621-5vmw.670.0.0.8169922, VMW_bootbank_net-tg3_3.131d.v60.4-2vmw.670.0.0.8169922, VMW_bootbank_net-usbnet_1.0-3vmw.670.0.0.8169922, VMW_bootbank_net-vmxnet3_1.1.3.0-3vmw.670.0.0.8169922, VMW_bootbank_nhpsa_2.0.22-1vmw.670.0.0.8169922, VMW_bootbank_nmlx4-core_3.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_nmlx4-en_3.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_nmlx4-rdma_3.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_nmlx5-core_4.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_nmlx5-rdma_4.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_ntg3_4.1.3.0-1vmw.670.0.0.8169922, VMW_bootbank_nvme_1.2.1.34-1vmw.670.0.0.8169922, VMW_bootbank_nvmxnet3-ens_2.0.0.21-1vmw.670.0.0.8169922, VMW_bootbank_nvmxnet3_2.0.0.27-1vmw.670.0.0.8169922, VMW_bootbank_ohci-usb-ohci_1.0-3vmw.670.0.0.8169922, VMW_bootbank_pvscsi_0.1-2vmw.670.0.0.8169922, VMW_bootbank_qcnic_1.0.2.0.4-1vmw.670.0.0.8169922, VMW_bootbank_qfle3_1.0.50.11-9vmw.670.0.0.8169922, VMW_bootbank_qfle3f_1.0.25.0.2-14vmw.670.0.0.8169922, VMW_bootbank_qfle3i_1.0.2.3.9-3vmw.670.0.0.8169922, VMW_bootbank_qflge_1.1.0.11-1vmw.670.0.0.8169922, VMW_bootbank_sata-ahci_3.0-26vmw.670.0.0.8169922, VMW_bootbank_sata-ata-piix_2.12-10vmw.670.0.0.8169922, VMW_bootbank_sata-sata-nv_3.5-4vmw.670.0.0.8169922, VMW_bootbank_sata-sata-promise_2.12-3vmw.670.0.0.8169922, VMW_bootbank_sata-sata-sil24_1.1-1vmw.670.0.0.8169922, VMW_bootbank_sata-sata-sil_2.3-4vmw.670.0.0.8169922, VMW_bootbank_sata-sata-svw_2.3-3vmw.670.0.0.8169922, VMW_bootbank_scsi-aacraid_1.1.5.1-9vmw.670.0.0.8169922, VMW_bootbank_scsi-adp94xx_1.0.8.12-6vmw.670.0.0.8169922, VMW_bootbank_scsi-aic79xx_3.1-6vmw.670.0.0.8169922, VMW_bootbank_scsi-bnx2fc_1.78.78.v60.8-1vmw.670.0.0.8169922, VMW_bootbank_scsi-bnx2i_2.78.76.v60.8-1vmw.670.0.0.8169922, VMW_bootbank_scsi-fnic_1.5.0.45-3vmw.670.0.0.8169922, VMW_bootbank_scsi-hpsa_6.0.0.84-3vmw.670.0.0.8169922, VMW_bootbank_scsi-ips_7.12.05-4vmw.670.0.0.8169922, VMW_bootbank_scsi-iscsi-linux-92_1.0.0.2-3vmw.670.0.0.8169922, VMW_bootbank_scsi-libfc-92_1.0.40.9.3-5vmw.670.0.0.8169922, VMW_bootbank_scsi-megaraid-mbox_2.20.5.1-6vmw.670.0.0.8169922, VMW_bootbank_scsi-megaraid-sas_6.603.55.00-2vmw.670.0.0.8169922, VMW_bootbank_scsi-megaraid2_2.00.4-9vmw.670.0.0.8169922, VMW_bootbank_scsi-mpt2sas_19.00.00.00-2vmw.670.0.0.8169922, VMW_bootbank_scsi-mptsas_4.23.01.00-10vmw.670.0.0.8169922, VMW_bootbank_scsi-mptspi_4.23.01.00-10vmw.670.0.0.8169922, VMW_bootbank_scsi-qla4xxx_5.01.03.2-7vmw.670.0.0.8169922, VMW_bootbank_shim-iscsi-linux-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-iscsi-linux-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libata-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libata-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libfc-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libfc-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libfcoe-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libfcoe-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-vmklinux-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-vmklinux-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-vmklinux-9-2-3-0_6.7.0-0.0.8169922, VMW_bootbank_smartpqi_1.0.1.553-10vmw.670.0.0.8169922, VMW_bootbank_uhci-usb-uhci_1.0-3vmw.670.0.0.8169922, VMW_bootbank_usb-storage-usb-storage_1.0-3vmw.670.0.0.8169922, VMW_bootbank_usbcore-usb_1.0-3vmw.670.0.0.8169922, VMW_bootbank_vmkata_0.1-1vmw.670.0.0.8169922, VMW_bootbank_vmkfcoe_1.0.0.0-1vmw.670.0.0.8169922, VMW_bootbank_vmkplexer-vmkplexer_6.7.0-0.0.8169922, VMW_bootbank_vmkusb_0.1-1vmw.670.0.0.8169922, VMW_bootbank_vmw-ahci_1.2.0-6vmw.670.0.0.8169922, VMW_bootbank_xhci-xhci_1.0-3vmw.670.0.0.8169922, VMware_bootbank_cpu-microcode_6.7.0-0.14.8941472, VMware_bootbank_elx-esx-libelxima.so_11.4.1184.0-0.0.8169922, VMware_bootbank_esx-dvfilter-generic-fastpath_6.7.0-0.0.8169922, VMware_bootbank_esx-ui_1.25.0-7872652, VMware_bootbank_esx-xserver_6.7.0-0.0.8169922, VMware_bootbank_lsu-hp-hpsa-plugin_2.0.0-13vmw.670.0.0.8169922, VMware_bootbank_lsu-lsi-lsi-mr3-plugin_1.0.0-12vmw.670.0.0.8169922, VMware_bootbank_lsu-lsi-lsi-msgpt3-plugin_1.0.0-8vmw.670.0.0.8169922, VMware_bootbank_lsu-lsi-megaraid-sas-plugin_1.0.0-9vmw.670.0.0.8169922, VMware_bootbank_lsu-lsi-mpt2sas-plugin_2.0.0-7vmw.670.0.0.8169922, VMware_bootbank_native-misc-drivers_6.7.0-0.0.8169922, VMware_bootbank_qlnativefc_3.0.1.0-5vmw.670.0.0.8169922, VMware_bootbank_rste_2.0.2.0088-7vmw.670.0.0.8169922, VMware_bootbank_vmware-esx-esxcli-nvme-plugin_1.2.0.32-0.0.8169922, VMware_locker_tools-light_10.2.1.8267844-8941472
[root@localhost:~] esxcli software vib update -d /vmfs/volumes/datastore1/updates/ESXi670-201808001.zip
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: VMware_bootbank_cpu-microcode_6.7.0-0.20.9484548, VMware_bootbank_esx-base_6.7.0-0.20.9484548, VMware_bootbank_esx-ui_1.25.1-9210161, VMware_bootbank_vsan_6.7.0-0.20.9484548, VMware_bootbank_vsanhealth_6.7.0-0.20.9484548
VIBs Removed: VMware_bootbank_cpu-microcode_6.7.0-0.14.8941472, VMware_bootbank_esx-base_6.7.0-0.17.9214924, VMware_bootbank_esx-ui_1.25.0-7872652, VMware_bootbank_vsan_6.7.0-0.17.9214924, VMware_bootbank_vsanhealth_6.7.0-0.17.9214924
VIBs Skipped: VMW_bootbank_ata-libata-92_3.00.9.2-16vmw.670.0.0.8169922, VMW_bootbank_ata-pata-amd_0.3.10-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-atiixp_0.4.6-4vmw.670.0.0.8169922, VMW_bootbank_ata-pata-cmd64x_0.2.5-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-pdc2027x_1.0-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-serverworks_0.4.3-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-sil680_0.4.8-3vmw.670.0.0.8169922, VMW_bootbank_ata-pata-via_0.3.3-2vmw.670.0.0.8169922, VMW_bootbank_block-cciss_3.6.14-10vmw.670.0.0.8169922, VMW_bootbank_bnxtnet_20.6.101.7-11vmw.670.0.0.8169922, VMW_bootbank_brcmfcoe_11.4.1078.0-8vmw.670.0.0.8169922, VMW_bootbank_char-random_1.0-3vmw.670.0.0.8169922, VMW_bootbank_ehci-ehci-hcd_1.0-4vmw.670.0.0.8169922, VMW_bootbank_elxiscsi_11.4.1174.0-2vmw.670.0.0.8169922, VMW_bootbank_elxnet_11.4.1094.0-5vmw.670.0.0.8169922, VMW_bootbank_hid-hid_1.0-3vmw.670.0.0.8169922, VMW_bootbank_i40en_1.3.1-18vmw.670.0.0.8169922, VMW_bootbank_iavmd_1.2.0.1011-2vmw.670.0.0.8169922, VMW_bootbank_igbn_0.1.0.0-15vmw.670.0.0.8169922, VMW_bootbank_ima-qla4xxx_2.02.18-1vmw.670.0.0.8169922, VMW_bootbank_ipmi-ipmi-devintf_39.1-4vmw.670.0.0.8169922, VMW_bootbank_ipmi-ipmi-msghandler_39.1-4vmw.670.0.0.8169922, VMW_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.670.0.0.8169922, VMW_bootbank_iser_1.0.0.0-1vmw.670.0.0.8169922, VMW_bootbank_ixgben_1.4.1-11vmw.670.0.0.8169922, VMW_bootbank_lpfc_11.4.33.1-6vmw.670.0.0.8169922, VMW_bootbank_lpnic_11.4.59.0-1vmw.670.0.0.8169922, VMW_bootbank_lsi-mr3_7.702.13.00-4vmw.670.0.0.8169922, VMW_bootbank_lsi-msgpt2_20.00.04.00-4vmw.670.0.0.8169922, VMW_bootbank_lsi-msgpt35_03.00.01.00-10vmw.670.0.0.8169922, VMW_bootbank_lsi-msgpt3_16.00.01.00-1vmw.670.0.0.8169922, VMW_bootbank_misc-cnic-register_1.78.75.v60.7-1vmw.670.0.0.8169922, VMW_bootbank_misc-drivers_6.7.0-0.0.8169922, VMW_bootbank_mtip32xx-native_3.9.6-1vmw.670.0.0.8169922, VMW_bootbank_ne1000_0.8.3-4vmw.670.0.0.8169922, VMW_bootbank_nenic_1.0.11.0-1vmw.670.0.0.8169922, VMW_bootbank_net-bnx2_2.2.4f.v60.10-2vmw.670.0.0.8169922, VMW_bootbank_net-bnx2x_1.78.80.v60.12-2vmw.670.0.0.8169922, VMW_bootbank_net-cdc-ether_1.0-3vmw.670.0.0.8169922, VMW_bootbank_net-cnic_1.78.76.v60.13-2vmw.670.0.0.8169922, VMW_bootbank_net-e1000_8.0.3.1-5vmw.670.0.0.8169922, VMW_bootbank_net-e1000e_3.2.2.1-2vmw.670.0.0.8169922, VMW_bootbank_net-enic_2.1.2.38-2vmw.670.0.0.8169922, VMW_bootbank_net-fcoe_1.0.29.9.3-7vmw.670.0.0.8169922, VMW_bootbank_net-forcedeth_0.61-2vmw.670.0.0.8169922, VMW_bootbank_net-igb_5.0.5.1.1-5vmw.670.0.0.8169922, VMW_bootbank_net-ixgbe_3.7.13.7.14iov-20vmw.670.0.0.8169922, VMW_bootbank_net-libfcoe-92_1.0.24.9.4-8vmw.670.0.0.8169922, VMW_bootbank_net-mlx4-core_1.9.7.0-1vmw.670.0.0.8169922, VMW_bootbank_net-mlx4-en_1.9.7.0-1vmw.670.0.0.8169922, VMW_bootbank_net-nx-nic_5.0.621-5vmw.670.0.0.8169922, VMW_bootbank_net-tg3_3.131d.v60.4-2vmw.670.0.0.8169922, VMW_bootbank_net-usbnet_1.0-3vmw.670.0.0.8169922, VMW_bootbank_net-vmxnet3_1.1.3.0-3vmw.670.0.0.8169922, VMW_bootbank_nhpsa_2.0.22-1vmw.670.0.0.8169922, VMW_bootbank_nmlx4-core_3.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_nmlx4-en_3.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_nmlx4-rdma_3.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_nmlx5-core_4.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_nmlx5-rdma_4.17.9.12-1vmw.670.0.0.8169922, VMW_bootbank_ntg3_4.1.3.0-1vmw.670.0.0.8169922, VMW_bootbank_nvme_1.2.1.34-1vmw.670.0.0.8169922, VMW_bootbank_nvmxnet3-ens_2.0.0.21-1vmw.670.0.0.8169922, VMW_bootbank_nvmxnet3_2.0.0.27-1vmw.670.0.0.8169922, VMW_bootbank_ohci-usb-ohci_1.0-3vmw.670.0.0.8169922, VMW_bootbank_pvscsi_0.1-2vmw.670.0.0.8169922, VMW_bootbank_qcnic_1.0.2.0.4-1vmw.670.0.0.8169922, VMW_bootbank_qedentv_2.0.6.4-10vmw.670.0.17.9214924, VMW_bootbank_qfle3_1.0.50.11-9vmw.670.0.0.8169922, VMW_bootbank_qfle3f_1.0.25.0.2-14vmw.670.0.0.8169922, VMW_bootbank_qfle3i_1.0.2.3.9-3vmw.670.0.0.8169922, VMW_bootbank_qflge_1.1.0.11-1vmw.670.0.0.8169922, VMW_bootbank_sata-ahci_3.0-26vmw.670.0.0.8169922, VMW_bootbank_sata-ata-piix_2.12-10vmw.670.0.0.8169922, VMW_bootbank_sata-sata-nv_3.5-4vmw.670.0.0.8169922, VMW_bootbank_sata-sata-promise_2.12-3vmw.670.0.0.8169922, VMW_bootbank_sata-sata-sil24_1.1-1vmw.670.0.0.8169922, VMW_bootbank_sata-sata-sil_2.3-4vmw.670.0.0.8169922, VMW_bootbank_sata-sata-svw_2.3-3vmw.670.0.0.8169922, VMW_bootbank_scsi-aacraid_1.1.5.1-9vmw.670.0.0.8169922, VMW_bootbank_scsi-adp94xx_1.0.8.12-6vmw.670.0.0.8169922, VMW_bootbank_scsi-aic79xx_3.1-6vmw.670.0.0.8169922, VMW_bootbank_scsi-bnx2fc_1.78.78.v60.8-1vmw.670.0.0.8169922, VMW_bootbank_scsi-bnx2i_2.78.76.v60.8-1vmw.670.0.0.8169922, VMW_bootbank_scsi-fnic_1.5.0.45-3vmw.670.0.0.8169922, VMW_bootbank_scsi-hpsa_6.0.0.84-3vmw.670.0.0.8169922, VMW_bootbank_scsi-ips_7.12.05-4vmw.670.0.0.8169922, VMW_bootbank_scsi-iscsi-linux-92_1.0.0.2-3vmw.670.0.0.8169922, VMW_bootbank_scsi-libfc-92_1.0.40.9.3-5vmw.670.0.0.8169922, VMW_bootbank_scsi-megaraid-mbox_2.20.5.1-6vmw.670.0.0.8169922, VMW_bootbank_scsi-megaraid-sas_6.603.55.00-2vmw.670.0.0.8169922, VMW_bootbank_scsi-megaraid2_2.00.4-9vmw.670.0.0.8169922, VMW_bootbank_scsi-mpt2sas_19.00.00.00-2vmw.670.0.0.8169922, VMW_bootbank_scsi-mptsas_4.23.01.00-10vmw.670.0.0.8169922, VMW_bootbank_scsi-mptspi_4.23.01.00-10vmw.670.0.0.8169922, VMW_bootbank_scsi-qla4xxx_5.01.03.2-7vmw.670.0.0.8169922, VMW_bootbank_shim-iscsi-linux-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-iscsi-linux-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libata-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libata-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libfc-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libfc-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libfcoe-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-libfcoe-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-vmklinux-9-2-1-0_6.7.0-0.0.8169922, VMW_bootbank_shim-vmklinux-9-2-2-0_6.7.0-0.0.8169922, VMW_bootbank_shim-vmklinux-9-2-3-0_6.7.0-0.0.8169922, VMW_bootbank_smartpqi_1.0.1.553-10vmw.670.0.0.8169922, VMW_bootbank_uhci-usb-uhci_1.0-3vmw.670.0.0.8169922, VMW_bootbank_usb-storage-usb-storage_1.0-3vmw.670.0.0.8169922, VMW_bootbank_usbcore-usb_1.0-3vmw.670.0.0.8169922, VMW_bootbank_vmkata_0.1-1vmw.670.0.0.8169922, VMW_bootbank_vmkfcoe_1.0.0.0-1vmw.670.0.0.8169922, VMW_bootbank_vmkplexer-vmkplexer_6.7.0-0.0.8169922, VMW_bootbank_vmkusb_0.1-1vmw.670.0.0.8169922, VMW_bootbank_vmw-ahci_1.2.0-6vmw.670.0.0.8169922, VMW_bootbank_xhci-xhci_1.0-3vmw.670.0.0.8169922, VMware_bootbank_elx-esx-libelxima.so_11.4.1184.0-0.0.8169922, VMware_bootbank_esx-dvfilter-generic-fastpath_6.7.0-0.0.8169922, VMware_bootbank_esx-xserver_6.7.0-0.0.8169922, VMware_bootbank_lsu-hp-hpsa-plugin_2.0.0-13vmw.670.0.0.8169922, VMware_bootbank_lsu-lsi-lsi-mr3-plugin_1.0.0-12vmw.670.0.0.8169922, VMware_bootbank_lsu-lsi-lsi-msgpt3-plugin_1.0.0-8vmw.670.0.0.8169922, VMware_bootbank_lsu-lsi-megaraid-sas-plugin_1.0.0-9vmw.670.0.0.8169922, VMware_bootbank_lsu-lsi-mpt2sas-plugin_2.0.0-7vmw.670.0.0.8169922, VMware_bootbank_native-misc-drivers_6.7.0-0.0.8169922, VMware_bootbank_qlnativefc_3.0.1.0-5vmw.670.0.0.8169922, VMware_bootbank_rste_2.0.2.0088-7vmw.670.0.0.8169922, VMware_bootbank_vmware-esx-esxcli-nvme-plugin_1.2.0.32-0.0.8169922, VMware_locker_tools-light_10.2.1.8267844-8941472
[root@localhost:~]
</pre>

== Verify updates ==
You can also use esxcli to verify the versions that were just installed:
<pre>
[root@localhost:~] esxcli software vib list
Name Version Vendor Acceptance Level Install Date
----------------------------- ------------------------------------ ------ ---------------- ------------
ata-libata-92 3.00.9.2-16vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ata-pata-amd 0.3.10-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ata-pata-atiixp 0.4.6-4vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ata-pata-cmd64x 0.2.5-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ata-pata-hpt3x2n 0.3.4-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ata-pata-pdc2027x 1.0-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ata-pata-serverworks 0.4.3-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ata-pata-sil680 0.4.8-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ata-pata-via 0.3.3-2vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
block-cciss 3.6.14-10vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
bnxtnet 20.6.101.7-11vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
brcmfcoe 11.4.1078.0-8vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
char-random 1.0-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ehci-ehci-hcd 1.0-4vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
elxiscsi 11.4.1174.0-2vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
elxnet 11.4.1094.0-5vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
hid-hid 1.0-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
i40en 1.3.1-18vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
iavmd 1.2.0.1011-2vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
igbn 0.1.0.0-15vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ima-qla4xxx 2.02.18-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ipmi-ipmi-devintf 39.1-4vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ipmi-ipmi-msghandler 39.1-4vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ipmi-ipmi-si-drv 39.1-4vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
iser 1.0.0.0-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ixgben 1.4.1-11vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
lpfc 11.4.33.1-6vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
lpnic 11.4.59.0-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
lsi-mr3 7.702.13.00-4vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
lsi-msgpt2 20.00.04.00-4vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
lsi-msgpt35 03.00.01.00-10vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
lsi-msgpt3 16.00.01.00-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
misc-cnic-register 1.78.75.v60.7-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
misc-drivers 6.7.0-0.0.8169922 VMW VMwareCertified 2018-08-27
mtip32xx-native 3.9.6-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ne1000 0.8.3-4vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
nenic 1.0.11.0-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-bnx2 2.2.4f.v60.10-2vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-bnx2x 1.78.80.v60.12-2vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-cdc-ether 1.0-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-cnic 1.78.76.v60.13-2vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-e1000 8.0.3.1-5vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-e1000e 3.2.2.1-2vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-enic 2.1.2.38-2vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-fcoe 1.0.29.9.3-7vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-forcedeth 0.61-2vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-igb 5.0.5.1.1-5vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-ixgbe 3.7.13.7.14iov-20vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-libfcoe-92 1.0.24.9.4-8vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-mlx4-core 1.9.7.0-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-mlx4-en 1.9.7.0-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-nx-nic 5.0.621-5vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-tg3 3.131d.v60.4-2vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-usbnet 1.0-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
net-vmxnet3 1.1.3.0-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
nhpsa 2.0.22-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
nmlx4-core 3.17.9.12-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
nmlx4-en 3.17.9.12-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
nmlx4-rdma 3.17.9.12-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
nmlx5-core 4.17.9.12-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
nmlx5-rdma 4.17.9.12-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ntg3 4.1.3.0-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
nvme 1.2.1.34-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
nvmxnet3-ens 2.0.0.21-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
nvmxnet3 2.0.0.27-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
ohci-usb-ohci 1.0-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
pvscsi 0.1-2vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
qcnic 1.0.2.0.4-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
qedentv 2.0.6.4-8vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
qfle3 1.0.50.11-9vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
qfle3f 1.0.25.0.2-14vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
qfle3i 1.0.2.3.9-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
qflge 1.1.0.11-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
sata-ahci 3.0-26vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
sata-ata-piix 2.12-10vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
sata-sata-nv 3.5-4vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
sata-sata-promise 2.12-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
sata-sata-sil24 1.1-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
sata-sata-sil 2.3-4vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
sata-sata-svw 2.3-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-aacraid 1.1.5.1-9vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-adp94xx 1.0.8.12-6vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-aic79xx 3.1-6vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-bnx2fc 1.78.78.v60.8-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-bnx2i 2.78.76.v60.8-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-fnic 1.5.0.45-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-hpsa 6.0.0.84-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-ips 7.12.05-4vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-iscsi-linux-92 1.0.0.2-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-libfc-92 1.0.40.9.3-5vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-megaraid-mbox 2.20.5.1-6vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-megaraid-sas 6.603.55.00-2vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-megaraid2 2.00.4-9vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-mpt2sas 19.00.00.00-2vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-mptsas 4.23.01.00-10vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-mptspi 4.23.01.00-10vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
scsi-qla4xxx 5.01.03.2-7vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
shim-iscsi-linux-9-2-1-0 6.7.0-0.0.8169922 VMW VMwareCertified 2018-08-27
shim-iscsi-linux-9-2-2-0 6.7.0-0.0.8169922 VMW VMwareCertified 2018-08-27
shim-libata-9-2-1-0 6.7.0-0.0.8169922 VMW VMwareCertified 2018-08-27
shim-libata-9-2-2-0 6.7.0-0.0.8169922 VMW VMwareCertified 2018-08-27
shim-libfc-9-2-1-0 6.7.0-0.0.8169922 VMW VMwareCertified 2018-08-27
shim-libfc-9-2-2-0 6.7.0-0.0.8169922 VMW VMwareCertified 2018-08-27
shim-libfcoe-9-2-1-0 6.7.0-0.0.8169922 VMW VMwareCertified 2018-08-27
shim-libfcoe-9-2-2-0 6.7.0-0.0.8169922 VMW VMwareCertified 2018-08-27
shim-vmklinux-9-2-1-0 6.7.0-0.0.8169922 VMW VMwareCertified 2018-08-27
shim-vmklinux-9-2-2-0 6.7.0-0.0.8169922 VMW VMwareCertified 2018-08-27
shim-vmklinux-9-2-3-0 6.7.0-0.0.8169922 VMW VMwareCertified 2018-08-27
smartpqi 1.0.1.553-10vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
uhci-usb-uhci 1.0-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
usb-storage-usb-storage 1.0-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
usbcore-usb 1.0-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
vmkata 0.1-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
vmkfcoe 1.0.0.0-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
vmkplexer-vmkplexer 6.7.0-0.0.8169922 VMW VMwareCertified 2018-08-27
vmkusb 0.1-1vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
vmw-ahci 1.2.0-6vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
xhci-xhci 1.0-3vmw.670.0.0.8169922 VMW VMwareCertified 2018-08-27
cpu-microcode 6.7.0-0.0.8169922 VMware VMwareCertified 2018-08-27
elx-esx-libelxima.so 11.4.1184.0-0.0.8169922 VMware VMwareCertified 2018-08-27
esx-base 6.7.0-0.0.8169922 VMware VMwareCertified 2018-08-27
esx-dvfilter-generic-fastpath 6.7.0-0.0.8169922 VMware VMwareCertified 2018-08-27
esx-ui 1.25.0-7872652 VMware VMwareCertified 2018-08-27
esx-xserver 6.7.0-0.0.8169922 VMware VMwareCertified 2018-08-27
lsu-hp-hpsa-plugin 2.0.0-13vmw.670.0.0.8169922 VMware VMwareCertified 2018-08-27
lsu-lsi-lsi-mr3-plugin 1.0.0-12vmw.670.0.0.8169922 VMware VMwareCertified 2018-08-27
lsu-lsi-lsi-msgpt3-plugin 1.0.0-8vmw.670.0.0.8169922 VMware VMwareCertified 2018-08-27
lsu-lsi-megaraid-sas-plugin 1.0.0-9vmw.670.0.0.8169922 VMware VMwareCertified 2018-08-27
lsu-lsi-mpt2sas-plugin 2.0.0-7vmw.670.0.0.8169922 VMware VMwareCertified 2018-08-27
native-misc-drivers 6.7.0-0.0.8169922 VMware VMwareCertified 2018-08-27
qlnativefc 3.0.1.0-5vmw.670.0.0.8169922 VMware VMwareCertified 2018-08-27
rste 2.0.2.0088-7vmw.670.0.0.8169922 VMware VMwareCertified 2018-08-27
vmware-esx-esxcli-nvme-plugin 1.2.0.32-0.0.8169922 VMware VMwareCertified 2018-08-27
vsan 6.7.0-0.0.8169922 VMware VMwareCertified 2018-08-27
vsanhealth 6.7.0-0.0.8169922 VMware VMwareCertified 2018-08-27
tools-light 10.2.1.8267844-8941472 VMware VMwareCertified 2018-08-27
[root@localhost:~]
</pre>

== Perform reboot and exit maintenance mode ==
Now, perform the reboot:
[root@localhost:~] reboot

After the reboot, exit maintenance mode:
[root@localhost:~] vim-cmd hostsvc/maintenance_mode_exit

== References ==
<references />

{{Wfischer}}
{{Aranzinger}}
[[Category:VMware vSphere 6.7]]
[[de:VMware ESXi updaten]]

IPMI configuration for Supermicro systems

2026-08-06T09:30:00Z

Aranzinger: Created page with "This article describes tools for the configuration of IPMI modules for Supermicro systems. Alternatively, the ipmitool can also be used if the server is operated on Linux (see also IPMI Configuration under Linux using ipmitool). == IPnMAC == With this tool (on Linux IPMICFG, see below), it is possible to set the IP address and the MAC address locally on the server. It must be taken into consideration that the correct MAC..."

This article describes tools for the configuration of IPMI modules for Supermicro systems. Alternatively, the ipmitool can also be used if the server is operated on Linux (see also [[Configuring IPMI under Linux using ipmitool|IPMI Configuration under Linux using ipmitool]]).

== IPnMAC ==

With this tool (on Linux IPMICFG, see below), it is possible to set the IP address and the MAC address locally on the server. It must be taken into consideration that the correct MAC address is already preconfigured.

== XGICFG ==

With the XGICFG tool (for DOS), diverse network parameters can be locally set for the IPMI module on the server. The possible options are listed in the following:

-m Show IP and MAC
-m IP Set IP (format :###.###.###.###)
-k Show Subnet Mask
-k Mask Set Subnet Mask (format :###.###.###.###)
-dhcp on Enable the DHCP
-dhcp off Disable the DHCP
-g Show Gateway IP
-g IP Set Gateway IP (format :###.###.###.###)

== IPMICFG ==

IPMICFG allows the local configuration of multiple IPMI settings and is available for the following operating systems:
* Windows (In addition to the command-line program IPMICFG, it also includes the graphical ''IPMI Configuration Utility'')
* Linux
* DOS

Detailed information on IPMICFG: [[IPMI configuration for Supermicro servers with ipmicfg]]

== IPMI view ==
[[Supermicro IPMI View]] also allows the IPMI configuration of Supermicro systems. For the access via IPMI view, however, a working IP address for IPMI must have been set up beforehand.

== psetup ==
IPMI modules, that are based on the Raritan KIRA chip (such as the IPMI module for X7 motherboards), can also be configured by using psetup: [[Raritan KIRA basierendes Remote Management mit psetup konfigurieren|Configuration of Raritan KIRA based Remote Management with psetup]].

== IPMI configuration via BIOS ==

For the new Supermicro motherboards (X8/X9/H8 series), the configuration of the IPMI module is possible via mainboard BIOS: [[Supermicro IPMI Configuration through BIOS or Web Interface]]

== Weblinks ==

[https://www.thomas-krenn.com/redx/tools/mb_download.php/mid.x426274344b6e4f5a6365383d/SW_IPMICfg-Utility-Windows_1.5_110420.zip Download IPMI Config-Tool for Windows]

[https://www.thomas-krenn.com/redx/tools/mb_download.php/mid.x4146352f4e6338477669733d/IPMICFG-DOS_v1.25_100106_1.zip Download IPMI Config-Tool for DOS]

[https://www.thomas-krenn.com/redx/tools/mb_download.php/mid.x77383743655052663377773d/SW_IPMICFG-Linux_v1.37_20110429.zip Download IPMI Config-Tool for Linux]

[ftp://ftp.supermicro.com/CDR-0010_2.10_IPMI_Server_Managment/ Content IPMI CD]

[ftp://ftp.supermicro.com/CDR-0010_2.10_IPMI_Server_Managment/IPMI_Solution/ IPMI-View]

[ftp://ftp.supermicro.com/CDR-0010_2.10_IPMI_Server_Managment/Manuals IPMI Documentation]

[[Category:IPMI]]
[[pl:Konfiguracja IPMI w systemach Supermicro]]
[[de:IPMI Konfiguration für Supermicro Systeme]]
{{Aranzinger}}

Software tools for IPMI at a glance

2026-08-06T05:51:48Z

Aranzinger: /* Manufacturer specific toolsy */

For [[IPMI Basics|IPMI]], there are multiple software tools for different purposes and operating systems. In the following, there is an overview of useful '''IPMI tools'''.

== Linux ==

=== IPMItool ===
[http://ipmitool.sourceforge.net/ IPMItool] is already included in multiple Linux distributions.

You can now communicate with IPMItool in two different ways with IPMI BMC's:
* via network by using a so-called LAN channel. In this case, only IPMItool is required.
* locally via a system interface to the BMC of the computer on which you are currently using IPMItool. In this case, the IPMI device driver from OpenIPMI is required (see below).

Originally, IPMItool was often bundled with OpenIPMI in packages provided by distributions. However, since these are independent software tools, IPMItool is now usually provided as a standalone package.<ref>[https://bugzilla.redhat.com/show_bug.cgi?id=466762 Bug 466762 - Review Request: ipmitool - Utility for IPMI control ] (bugzilla.redhat.com)</ref>

More information on the IPMItool in Thomas-Krenn-Wiki:
* [[IPMI Konfiguration unter Linux mittels ipmitool|Configuring IPMI under Linux using ipmitool]]
* [[Ipmitool zur Remotesteuerung von Servern nutzen|Using Ipmitool to Remotely Control Servers]]
* [[Ipmitool zur Sensorabfrage von Servern nutzen|Using Ipmitool to Check Server Sensors]]

=== OpenIPMI ===
[http://openipmi.sourceforge.net/ OpenIPMI] consists of two parts:
* an IPMI device driver for the Linux kernel
* a user-level library that provides a higher abstraction of IPMI

Updates from OpenIPMI in RHEL:
* [http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Technical_Notes/OpenIPMI.html OpenIPMI updates in RHEL 5.4]
* [http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.5.b1/html/Technical_Notes/ch01.html#OpenIPMI OpenIPMI updates in RHEL 5.5]

More information on OpenIPMI in Thomas-Krenn-Wiki:
* [[IPMI Analyse mit openipmish|IPMI analysis with openipmish]]

=== FreeIPMI ===
[[FreeIPMI]], just like IPMItool, allows IPMI queries both over the network and locally via a system interface. FreeIPMI, however, requires '''no IPMI device driver'''. The required code for the access via system interface is already included in FreeIPMI. It is not possible to run the OpenIPMI device driver and FreeIPMI at the same time.

FreeIPMI is specifically designed to meet the requirements of large computer clusters (HPC). At Thomas-Krenn, we use FreeIPMI at [[IPMI Sensor Monitoring Plugin]] (v2 and v3) for Nagios/Icinga.

FreeIPMI is included in RHEL 5 as Technology Preview.<ref>http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Release_Notes/sect-Release_Notes-Technology_Previews.html</ref>

=== IPMIutil ===
[http://ipmiutil.sourceforge.net/ IPMIutil] is another tool in the IPMI environment. In addition to Linux, it is also available for Windows, Solaris, BSD, and EFI. More details can be found in the [http://ipmiutil.sourceforge.net/docs/ipmisw-compare.htm comparison table of IPMIutil].

IPMIutil is included in Fedora 14.<ref>http://fedoraproject.org/wiki/Features/ipmiutil</ref>

== Windows ==

=== Microsoft IPMI provider ===
The Microsoft IPMI provider is not an independent tool. Instead, as a WMI provider, it allows other tools to access IPMI BMC information.

More information at Microsoft:
* [http://msdn.microsoft.com/en-us/library/aa391402%28VS.85%29.aspx IPMI Provider (Windows)] (http://msdn.microsoft.com)

=== IPMIutil for Windows ===
(see [[#IPMIutil]])

== iPhone ==
[[file:IPhone-IPMI-touch-01.png|right|thumb|300px|IPMI touch on the iPhone]]
There are two IPMI apps for the iphone by [http://www.yellowkompressor.com/ www.yellowkompressor.com]
* [http://www.yellowkompressor.com/ipmi-touch/ipmi-touch/ IPMI touch] (subject to a fee), [http://itunes.apple.com/app/ipmi-touch/id325614107 IPMI touch in the AppStore]
* [http://www.yellowkompressor.com/ipmi-touch/ipmi-light/ IPMI light] (free of charge), [http://itunes.apple.com/app/ipmi-light/id325610519 IPMI light in the AppStore]

== Manufacturer-specific tools ==

=== Supermicro tools ===
See [[IPMI Konfiguration für Supermicro Systeme|IPMI configuration for Supermicro systems]].

== References ==
<references />

{{Wfischer}}
{{Aranzinger}}
[[Category:IPMI]]
[[pl:Przegląd narzędzi programowych IPMI]]
[[de:Softwaretools für IPMI im Überblick]]

Terraform with Proxmox VE tutorial

2026-08-05T05:48:16Z

Aranzinger: Created page with "This article is about the first use of Terraform with Proxmox VE. You will receive all the necessary information beginning with the installation of Terraform to the first deployment of a Proxmox resource (VM). == Overview == Once setup is complete, the basic workflow in Terraform with Proxmox VE is as follows: # '''Install Terraform''' # '''Create Proxmox API-Token:''' for Terraform to access Proxmox VE # '''Create Terraform Provider:''' Communicates Terraform that..."

This article is about the first use of Terraform with [[Proxmox VE]]. You will receive all the necessary information beginning with the installation of Terraform to the first deployment of a Proxmox resource (VM).

== Overview ==
Once setup is complete, the basic workflow in Terraform with Proxmox VE is as follows:
# '''Install Terraform'''
# '''Create Proxmox API-Token:''' for Terraform to access Proxmox VE
# '''Create Terraform Provider:''' Communicates Terraform that Proxmox VE is the deployment target
# '''Create Cloud-Init-Image:''' For a simple and completed deployment including IP addresses
# '''Create or modify Terraform resources'''
# '''Terraform Init:''' Terraform tests the connection to the provider
# '''Terraform Plan:''' Terraform displays the planned changes
# '''Terraform Apply:''' Terraform displays/modifies the resources

== Terraform installation ==
=== Terraform installation ===

A Debian 12 container has been created and Terraform has been installed with the following commands:<ref>[https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli Terraform Installation] (developer.hashicorp.com)</ref>

<pre>
apt install curl unzip &&
curl -O https://releases.hashicorp.com/terraform/1.5.3/terraform_1.5.3_linux_amd64.zip &&
unzip terraform_1.5.3_linux_amd64.zip
mv terraform /usr/local/bin
</pre>

=== Creation of API token in PVE ===

First, an API token must be created in Proxmox VE. This can be made on datacenter level at <code>Permissions -> API-Tokens -> Add</code>. It is important that <code>Privilege Separation</code> is set to <code>No</code> for this functional test, or that you do not check the box when creating the API token. Please make a copy of the API key after you create it, as you will not be able to view it again later. In our case, this results in the following credentials:

<pre>root@pam!terraform2
b057aea1-a092-49c3-b530-a53fd9e6fccc</pre>

== Terraform configuration ==
=== Creating Terraform provider ===

So that Terraform knows, that it should use Proxmox as provider, a <code>provider.tf</code>-file must be created:

<pre>touch provider.tf
nano provider.tf
</pre>

<pre>
terraform {

required_providers {
proxmox = {
source = "telmate/proxmox"
version = "2.9.14"
}
}
}

variable "proxmox_api_url" {
type = string
}

variable "proxmox_api_token_id" {
type = string
sensitive = true
}

variable "proxmox_api_token_secret" {
type = string
sensitive = true
}

provider "proxmox" {

pm_api_url= var.proxmox_api_url
pm_api_token_id = var.proxmox_api_token_id
pm_api_token_secret = var.proxmox_api_token_secret
pm_tls_insecure = true
}
</pre>

=== Enter API credentials ===

In addition, Terraform must now authenticate with Proxmox VE using the API user and API key. Here, the configuration file <code>credentials.auto.tfvars</code> can be used and adapted to the environment:

<pre>
touch credentials.auto.tfvars
nano credentials.auto.tfvars
</pre>

<pre>
proxmox_api_url = "https://10.2.1.130:8006/api2/json"
proxmox_api_token_id = "root@pam!terraform2"
proxmox_api_token_secret = "b057aea1-a092-49c3-b530-a53fd9e6fccc"
</pre>

== Cloudinit under Proxmox VE ==
Since using cloud images makes sense in Terraform, here is a quick look at how to create and modify one. For this, an Ubuntu image is downloaded '''on the Proxmox hypervisor''' and the package <code>libguestfs-tools</code> is installed, which is required to make adjustments in the cloud image.<ref>[https://libguestfs.org/virt-customize.1.html virt-customize - Customize a virtual machine] (libguestfs.org)</ref>
Details for the creation of Cloud-Init-Templates can be found in the article [[Cloud Init Templates in Proxmox VE - Quickstart]]

=== Virt-Customize ===
The Virt-Customize tool is quite extensive and is also able to perform the following option:
<pre>
--run SCRIPT
--touch FILE
--firstboot SCRIPT
--mkdir DIR
--move SOURCE:DEST
--install PKG,PKG
--firstboot-install PKG,PKG
--append-line FILE:LINE
</pre>

== Overview in Proxmox VE ==
The templates are prepared and you can now use these templates to deploy as many VMs as you like. In the following example, there are 4 VMs that are ready to run immediately, including IP configuration, hostname, etc. To achieve this, 3 additional resource files were created with the names <code>srv_demo_2.tf</code>, <code>srv_demo_3.tf</code> and <code>srv_demo_4.tf</code> and adapted to our needs.

[[file:Proxmox Terraform.png|Terraform-Container and both templates (9000) and (9001)|frameless|without]]

== Terraform Workflow ==
=== Terraform Init ===

After this, it can be tested if Terraform can access the Proxmox host via API. For this, <code>terraform init</code> is used:

<pre>root@js-terraform-01:~# terraform init

Initializing the backend...

Initializing provider plugins...
- Reusing previous version of telmate/proxmox from the dependency lock file
- Using previously-installed telmate/proxmox v2.9.14

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
root@js-terraform-01:~# </pre>

=== Create Terraform resource ===

The goal of Terraform is, simply put, to be able to provision individual resources on various hypervisors (in this case with Proxmox VE). For this, Terraform configuration files are created, which describe what the resource to be provisioned should look like. Here is an example of the <code>srvdemo1.tf</code> file. We will be using a clone, so we need the VM template <code>ubuntu2204-ci</code>, which will later be created using a cloud image.

<pre>
touch srvdemo1.tf
nano srvdemo1.tf
</pre>

<pre>resource "proxmox_vm_qemu" "srv_demo_1" {
name = "srv-demo-1"
desc = "Ubuntu-Server"
target_node = "PMX4"
sshkeys = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCj8ipwPHVSI/yvERzILBD52zL1jj6Ja3ptWlVhR0WK6ElBekwKL314Sps79xAitJb>
agent = 1
clone = "ubuntu2204-ci"
qemu_os = "l26"
# this l26 is a small l like linux
cores = 2
sockets = 1
cpu = "host"
memory = 8096
scsihw = "virtio-scsi-pci"

vga {
type = "std"
}

disk {
storage = "vm_nvme"
type = "scsi"
size = "83212M"
discard = "on"
ssd = "1"
}

network {
bridge = "vmbr0"
model = "virtio"
}

## must match the template

os_type = "cloud-init"
ipconfig0 = "ip=dhcp"
nameserver = "192.168.110.61"
ciuser = "tk"
}
</pre>

A VM is created, including IP configuration. In addition, a cloud image is used, which you can also customize to suit your own needs.

=== Terraform plan ===

With <code> terraform plan </code>, you can use Terraform to provision the VM. This means that no resources are created yet. The configuration file and the connection to the provider are tested and validated.

<pre>root@js-terraform-01:~# terraform plan
+ create

Terraform will perform the following actions:

# proxmox_vm_qemu.srv_demo_1 will be created
+ resource "proxmox_vm_qemu" "srv_demo_1" {
+ additional_wait = 5
+ agent = 1
+ automatic_reboot = true
+ balloon = 0
+ bios = "seabios"
+ boot = (known after apply)
+ bootdisk = (known after apply)
+ ciuser = "tk"
+ clone = "ubuntu2204-ci"
+ clone_wait = 10
+ cores = 2
+ cpu = "host"
+ default_ipv4_address = (known after apply)
+ define_connection_info = true
+ desc = "Ubuntu-Server"
+ force_create = false
+ full_clone = true
+ guest_agent_ready_timeout = 100
+ hotplug = "network,disk,usb"
+ id = (known after apply)
+ ipconfig0 = "ip=dhcp"
+ kvm = true
+ memory = 8096
+ name = "srv-demo-1"
+ nameserver = "192.168.110.61"
+ onboot = false
+ oncreate = true
+ os_type = "cloud-init"
+ preprovision = true
+ reboot_required = (known after apply)
+ scsihw = "virtio-scsi-pci"
+ searchdomain = (known after apply)
+ sockets = 1
+ ssh_host = (known after apply)
+ ssh_port = (known after apply)
+ sshkeys = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCj8ipwPHVSI/yvERzILBD52zL1jj6JaSKoN1t1ftXEKbp+cuwZPUWykvSaR13ptWlVhR0WK6ElBekwKL314Sps79xAitJbbD35yDuMVtLUK/Bo+j2ehuWWmFZMwi1UKsPgCzF/YarsX12aCIS2Gyyf2NnscgOGlQKIdcgtfO23Xz18yxQxmFuRFVbFscd7gghRoQWsoKKwldbCKS8JEbXE8Mrb5mA7XD1C4dQLMnFvoJUvx3UqZinQHc20lWjqlZIOZ0uxRz6ssVFoCn+bKKNdf43JEnwPhcxQC2vGmKWunojNsXCifdx16fvd/wegXrdL8uw2oWUAvNsjCIUYCFn+VOn5JXEAxlXCAUNN9Z9H6/64QhwTjAXibwzB8Yj2+mGqd2ODy9ZIs+nzqxsmITA8+ayaEigZngol54f6vafmQzRHrM6Zn768UEYqEGb2LgYtI/0eTClO+E0HAPVfwpRwy6T1MhmIY8otSizE3PN3pg+fcyxv9oyMnxVsYCpspzE= root@js-terraform-01>"
+ tablet = true
+ target_node = "PMX4"
+ unused_disk = (known after apply)
+ vcpus = 0
+ vlan = -1
+ vmid = (known after apply)

+ disk {
+ backup = true
+ cache = "none"
+ discard = "on"
+ file = (known after apply)
+ format = (known after apply)
+ iops = 0
+ iops_max = 0
+ iops_max_length = 0
+ iops_rd = 0
+ iops_rd_max = 0
+ iops_rd_max_length = 0
+ iops_wr = 0
+ iops_wr_max = 0
+ iops_wr_max_length = 0
+ iothread = 0
+ mbps = 0
+ mbps_rd = 0
+ mbps_rd_max = 0
+ mbps_wr = 0
+ mbps_wr_max = 0
+ media = (known after apply)
+ replicate = 0
+ size = "83212M"
+ slot = (known after apply)
+ ssd = 1
+ storage = "vm_nvme"
+ storage_type = (known after apply)
+ type = "scsi"
+ volume = (known after apply)
}

+ network {
+ bridge = "vmbr0"
+ firewall = false
+ link_down = false
+ macaddr = (known after apply)
+ model = "virtio"
+ queues = (known after apply)
+ rate = (known after apply)
+ tag = -1
}

+ vga {
+ type = "std"
}
}

</pre>

=== Terraform Apply ===

You can then create the resources using <code>terraform apply </code>. Confirm with <code>yes</code>, and then (in this case, 4 VMs) will be deployed. The output has been shortened for clarity, so that only the complete output of <code>srv_demo_1</code> is displayed:

<pre>root@js-terraform-01:~# terraform apply

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:

# proxmox_vm_qemu.srv_demo_1 will be created
+ resource "proxmox_vm_qemu" "srv_demo_1" {
+ additional_wait = 5
+ agent = 1
+ automatic_reboot = true
+ balloon = 0
+ bios = "seabios"
+ boot = (known after apply)
+ bootdisk = (known after apply)
+ ciuser = "tk"
+ clone = "ubuntu2204-ci"
+ clone_wait = 10
+ cores = 2
+ cpu = "host"
+ default_ipv4_address = (known after apply)
+ define_connection_info = true
+ desc = "Ubuntu-Server"
+ force_create = false
+ full_clone = true
+ guest_agent_ready_timeout = 100
+ hotplug = "network,disk,usb"
+ id = (known after apply)
+ ipconfig0 = "ip=dhcp"
+ kvm = true
+ memory = 8096
+ name = "srv-demo-1"
+ nameserver = "192.168.110.61"
+ onboot = false
+ oncreate = true
+ os_type = "cloud-init"
+ preprovision = true
+ reboot_required = (known after apply)
+ scsihw = "virtio-scsi-pci"
+ searchdomain = (known after apply)
+ sockets = 1
+ ssh_host = (known after apply)
+ ssh_port = (known after apply)
+ sshkeys = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCj8ipwPHVSI/yvERzILBD52zL1jj6JaSKoN1t1ftXEKbp+cuwZPUWykvSaR13ptWlVhR0WK6ElBekwKL314Sps79xAitJbbD35yDuMVtLUK/Bo+j2ehuWWmFZMwi1UKsPgCzF/YarsX12aCIS2Gyyf2NnscgOGlQKIdcgtfO23Xz18yxQxmFuRFVbFscd7gghRoQWsoKKwldbCKS8JEbXE8Mrb5mA7XD1C4dQLMnFvoJUv= root@js-terraform-01>"
+ tablet = true
+ target_node = "PMX4"
+ unused_disk = (known after apply)
+ vcpus = 0
+ vlan = -1
+ vmid = (known after apply)

+ disk {
+ backup = true
+ cache = "none"
+ discard = "on"
+ file = (known after apply)
+ format = (known after apply)
+ iops = 0
+ iops_max = 0
+ iops_max_length = 0
+ iops_rd = 0
+ iops_rd_max = 0
+ iops_rd_max_length = 0
+ iops_wr = 0
+ iops_wr_max = 0
+ iops_wr_max_length = 0
+ iothread = 0
+ mbps = 0
+ mbps_rd = 0
+ mbps_rd_max = 0
+ mbps_wr = 0
+ mbps_wr_max = 0
+ media = (known after apply)
+ replicate = 0
+ size = "83212M"
+ slot = (known after apply)
+ ssd = 1
+ storage = "vm_nvme"
+ storage_type = (known after apply)
+ type = "scsi"
+ volume = (known after apply)
}

+ network {
+ bridge = "vmbr0"
+ firewall = false
+ link_down = false
+ macaddr = (known after apply)
+ model = "virtio"
+ queues = (known after apply)
+ rate = (known after apply)
+ tag = -1
}

+ vga {
+ type = "std"
}
}

# proxmox_vm_qemu.srv_demo_2 will be created
# proxmox_vm_qemu.srv_demo_3 will be created
# proxmox_vm_qemu.srv_demo_4 will be created

Plan: 4 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.

Enter a value: yes

proxmox_vm_qemu.srv_demo_4: Creating...
proxmox_vm_qemu.srv_demo_2: Creating...
proxmox_vm_qemu.srv_demo_3: Creating...
proxmox_vm_qemu.srv_demo_1: Creating...
...
proxmox_vm_qemu.srv_demo_4: Creation complete after 39s [id=PMX4/qemu/103]
proxmox_vm_qemu.srv_demo_3: Creation complete after 47s [id=PMX4/qemu/101]
proxmox_vm_qemu.srv_demo_1: Creation complete after 49s [id=PMX4/qemu/102]
proxmox_vm_qemu.srv_demo_2: Creation complete after 53s [id=PMX4/qemu/104]

Apply complete! Resources: 4 added, 0 changed, 0 destroyed.
</pre>
[[file:Proxmox Terraform Apply.png|without|small|650x650px|Terraform allocates Proxmox VMs]]

== More information ==
* [https://www.youtube.com/watch?v=dvyeoDBUtsU& YouTube video on Proxmox Automation with Terraform]: Live-Demo on using and configuring Terraform in Proxmox VE
* [https://registry.terraform.io/providers/Telmate/proxmox/latest Proxmox Terraform Provider]: Terraform-Provider Docs (Telmate/proxmox)

== References ==
<references />

 
{{jsterr}}
{{Aranzinger}}
[[Category:VMs/Containers]]
[[de:Terraform mit Proxmox VE Tutorial]]