# AXE-7220SR

2U GPU Server

with

4th/5th Gen Intel® Xeon® Scalable Processor

# User’s Manual

![Front view of a server rack with multiple drive bays and indicator lights (no visible text or labels)](.axe-7220sr-50m-22810-1000-10/36a0b46578004289f913f678297dd96328e1d03c70933c82c524c2f6e0ec8df3.jpg)

Manual Rev.: Rev. 1.0

Revision Date: August 12, 2025

Part No.: 50M-22810-1000

# Preface

# Copyright © 2025 ADLINK Technology, Inc.

This document contains proprietary information protected by copyright. All rights are reserved. No part of this manual may be reproduced by any mechanical, electronic, or other means in any form without prior written permission of the manufacturer.

# Disclaimer

The information in this document is subject to change without prior notice in order to improve reliability, design, and function and does not represent a commitment on the part of the manufacturer.

In no event will the manufacturer be liable for direct, indirect, special, incidental, or consequential damages arising out of the use or inability to use the product or documentation, even if advised of the possibility of such damages.

# Environmental Responsibility

ADLINK is committed to fulfill its social responsibility to global environmental preservation through compliance with the European Union’s Restriction of Hazardous Substances (RoHS) directive and Waste Electrical and Electronic Equipment (WEEE) directive. Environmental protection is a top priority for ADLINK. We have enforced measures to ensure that our products, manufacturing processes, components, and raw materials have as little impact on the environment as possible. When products are at their end of life, our customers are encouraged to dispose of them in accordance with the product disposal and/or recovery programs prescribed by their nation or company.

![Symbol of a trash bin crossed out by two diagonal lines (no text or numbers present)](.axe-7220sr-50m-22810-1000-10/c0ddb0d8ff7c0d35cd221272f4a15e2ca412469db21c95a51bf3ff586b0ac2c0.jpg)

![The image displays a rectangular graphic resembling a row in a table or a form interface. It is divided vertically into two distinct sections. On the left, there is a narrow white column that is split horizontally into two equal sections by a thin black line. On the right, a wide black rectangle spans the entire vertical height of the graphic, adjacent to the white column. The top and bottom edges of the entire graphic are defined by thin horizontal black lines. There is no visible text.](.axe-7220sr-50m-22810-1000-10/61cceeb059b3afda760e95e1c2ff357cd19c6fa4789047a7fdf63202df186f65.jpg)

# Trademarks

Product names mentioned herein are used for identification purposes only and may be trademarks and/or registered trademarks of their respective companies.

Revision History

<table><tr><td>Revision</td><td>Release Date</td><td>Description of Change(s)</td></tr><tr><td>1.0</td><td>2025-08-12</td><td>Initial release</td></tr></table>

# Conventions

![A yellow triangular warning sign featuring a black exclamation point inside and the text 'CAUTION:' printed in black capital letters below it.](.axe-7220sr-50m-22810-1000-10/1e8a184134d62ee87716707d5f90cecbc42e844b70ff02169e2c205cb0c490d9.jpg)

mise en garde

Information to prevent minor physical injury, component damage, data loss, and/or program corruption when trying to complete a task.

Informations destinées à prévenir les blessures corporelles mineures, les dommages aux composants, la perte de données et/ou la corruption de programme lors de l'exécution d'une tâche.

![The image shows a red equilateral triangle containing a white exclamation point in the center. Below the triangle, the text 'WARNING:' appears in black capital letters.](.axe-7220sr-50m-22810-1000-10/e883f5c32c7348a88c5a6517e1d34007513f8c77394a836be3836eca7d91a44a.jpg)

AVERTISSEME

Information to prevent serious physical injury, component damage, data loss, and/or program corruption when trying to complete a specific task. Informations destinées à prévenir les blessures corporelles graves, les dommages aux composants, la perte de données et/ou la corruption de programme lors de l'exécution d'une tâche spécifique.

# Table of Contents

# Preface .................

1.1 Introduction. 9
1.2 Block Diagram . . 10
1.3 Mechanical Overview.. .11

1.3.1 AXE-7220SR Rear Panel.. .11
1.3.2 AXE-7220SR Front Panel . . 12
1.3.3 AXE-7220SR Internal Layout .. . 13
1.3.4 Mechanical Dimensions . . 14

# 2 Specifications .... . 15

2.1 AXE-7220SR Specifications . 15

# 3 Getting Started ................ . 17

3.1 Removing the Chassis Cover .. . 17
3.2 Installing Memory Modules . . 18
3.3 PCIe Card Installation. . 20

3.3.1 PCIe x16 Slot . . 20
3.3.2 PCIe x16 Slot with x8 Lanes (SKU2).. . 24

3.4 PCIe Slot Secondary Power Supply .. . 27
3.5 Rails Assembly and Rack Installation .. .. 29
3.6 Uninstalling the Rails from the Chassis.
3.7 Connecting the System to Ground.. .. 36
3.8 System Power Cable Installation .. . 37
3.9 Login to the BMC via Console Port.. . 38

3.10 BMC eth0 Default and Static IP Settings . . 40
3.11 BMC eth1 Default and Static IP Settings . . 41
3.12 BIOS Update.. . 42

3.12.1Updating BIOS via Host with BIOS Tool.. 42

3.13 BMC Firmware Update via Network.. . 43
3.14 BMC Firmware Update via Host with Yafuflash.. . 46
3.15 CPLD Update.. . 47

# 3.15.1 Yafuflash 47

3.16 Enter BIOS Setup . 49
3.17 Create a RAID Volume.. . 50
3.18 Clear CMOS . 53

# 4 System Interfaces.. . 54

4.1 Status LEDs.. . 54
4.2 LAN Ports . . 55
4.3 RGPS Port.. 56
4.4 SFP+ Ports . . 57
4.5 Dual USB 3.0 and RJ-45 Console Port.. . 58
4.6 1PPS/TOD Connector... 59
4.7 HDD/User LED Jumper.. . 60
4.8 User LED Commands. . 61

4.8.1 OEM ADLINK Set LED Status.. 61
4.8.2 OEM ADLINK Get LED Status . . 62

4.9 Board Layout .. 63

# 5 BIOS Setup..................... 65

5.1 BIOS Setup Menu.. . 65

5.1.1 Menu Selection Bar.. 65
5.1.2 Menu Conventions . 66

5.2 Main Menu.. 66

5.2.1 BIOS Information.. 67
5.2.2 System Information .. 67

5.3 Platform Configuration Menu .. 68

5.3.1 PCH-IO Configuration . 69
5.3.2 Miscellaneous Configuration . 72
5.3.3 Network Configuration.. 73
5.3.4 System Event Log. 74

5.4 Advanced Menu.. . 75

5.4.1 Serial Port Console Redirection . 76
5.4.2 NVMe Configuration.. 79
5.4.3 PCI Subsystem Settings . 80
5.4.4 Network Stack Configuration. 81
5.4.5 Advanced Power Management .. 82
5.4.6 Trusted Computing. 88
5.4.7 Intel(R) I210 Gigabit Network Connection... 89
5.4.8 Intel(R) Ethernet Connection E823-L for 10GbE . 90

5.5 Socket Configuration Menu.. . 91

5.5.1 Processor Configuration.. 92
5.5.2 Common RefCode Configuration .. 93
5.5.3 Memory Configuration.. 94
5.5.4 IIO Configuration .. 96

5.6 Server Mgmt Menu . 99

5.6.1 BMC Network Configuration.. . 100

5.7 Security Menu.. 101
5.8 Boot Menu . 102
5.9 Save & Exit Menu . . 103

# 6 BMC ... . 104

6.1 BMC Introduction .. . 104

6.1.1 Software Interface .. . 104

6.1.1.1 Web GUI.. . 104
6.1.1.2 IPMI Interface .. . 105
6.1.1.3 Redfish . 105

6.2 Web GUI Introduction . 106

6.2.1 Web Login. . 106

6.2.1.1 Environment Setup.. . 106

6.2.1.2 User Sign-In.. . 107

6.2.2 Web Interface Overview .. 109
6.2.3 Server Information.. .111

6.2.3.1 FRU Information .. ..111

6.2.3.2 Sensor Information .... ..112

6.2.3.2.1 Introduction to sensor interface .. ..112

6.2.3.2.2 Detailed Sensor Information ... ..114

6.2.3.2.3 Modifying Sensor Thresholds . ..115

6.2.4 Server Information.. .117

6.2.4.1 IPMI Event Log. ..117

6.2.4.2 System Log.. ..119

6.2.4.3 Audit Log... . 120

6.2.4.4 Video Log . . 120

6.2.4.5 SOL Video Log . .. 122

6.2.5 Power Control . . 123

6.2.6 BMC Settings . . 124

6.2.6.1 Captured BSOD.. . 125

6.2.6.2 Date & Time.. . 126

6.2.6.3 External User Services .. . 129

6.2.6.3.1 LDAP/E-Directory Settings . . 129

6.2.6.3.2 Active Directory Settings.. . 132

6.2.6.3.3 RADIUS Settings .. . 136

6.2.6.4 Service Management.. . 139

6.2.6.5 Network Configuration . . 140

6.2.6.5.1 Network IP Settings . .. 140

6.2.6.5.2 Network Link Configuration .. . 142

6.2.6.5.3 DNS Configuration.. . 142

6.2.6.5.4 Sideband Interface (NC-SI) .. . 146

6.2.6.6 NIC Management . . 147

6.2.7 Remote Management.. 149

6.2.7.1 KVM.. . 149

6.2.7.2 SOL . . 156

6.2.8 Server Maintenance . 157

6.2.8.1 Firmware Update . . 157

6.2.8.1.1 BMC Update. . 157

6.2.8.1.2 BIOS Update .. 162

6.2.8.1.3 HPM Firmware Update – CPLD/BIOS . . 164

6.2.8.1.4 PLDM Firmware Update ... .. 167

6.2.8.2 Firmware Configuration . .. 170

6.2.8.2.1 Dual Image Configuration.. . 170

6.2.9 One-Click Log Collection.. . 172

6.2.10Firmware and Hardware versions . . 173

6.2.11PLDM . . 173

6.3 IPMI . 176

6.3.1 Overview of ipmitool.. . 176

6.3.1.1 General Usage of ipmitool . . 176

6.3.1.2 Specific Interface Options.. . 176

6.3.2 ipmitool Command Introduction.. . 179

6.3.2.1 Fan Control.. . 179

6.3.2.2 Sensor Information .. . 181

6.3.2.3 Power Control.. . 183

6.3.2.3.1 Redundancy Mode .. . 183

6.3.2.3.2 Power Supply Reading . . 184

6.3.2.3.3 Chassis Power Reboot Reasons.. .. 186

6.3.2.3.4 Power Control Method... .. 186

6.3.2.4 LED Control.. . 187

6.3.2.4.1 OEM Command.. .. 187

6.3.2.4.2 ipmitool for UID LED . . 189

6.3.2.5 Network Configuration .... .. 190

6.3.2.5.1 Get the current configuration of the management port . .. 190

6.3.2.5.2 Set the IP address source . . 190

6.3.2.5.3 Set the IP address ... . 190

6.3.2.5.4 Set the netmask. . 191

6.3.2.5.5 Set the default gateway IP address .. . 191

6.3.2.5.6 Set network configuration via BIOS . .. 191

6.3.2.6 x86 Watchdog Configuration . .. 193

6.3.2.6.1 Configure the watchdog via BIOS.. .. 193

6.3.2.6.2 Get Watchdog Timer.. . 193

6.3.2.6.3 Set Watchdog Timer .. .. 194

6.3.2.6.4 Reset Watchdog Timer .. .. 195

6.3.2.6.5 Shutoff Watchdog Timer .. . 195

6.3.2.7 BIOS POST Code. . 196

6.3.2.7.1 Read Latest BIOS POST Code ... .. 196

6.3.2.7.2 Read BIOS POST Codes .. . 196

6.3.2.8 MAC Address Burning ....... .. 197

6.3.2.8.1 Burning ethx MAC Address Preparation . .. 197

6.3.2.8.2 Burning ethx MAC Address... . 197

6.3.2.9 SOL . . 198

6.3.2.10 Firmware and Hardware Versions .. .. 199

6.3.2.10.1 Get Device ID . .. 199

6.3.2.10.2 Get CPLD Version and SKU Version . . 200

6.3.2.11 CPLD Update. . 201

6.4 Redfish... . 202

6.4.1 Network Configuration.. 202

6.4.1.1 GET - Ethernet Interface Collection... . 202

6.4.1.2 GET - Ethernet Interface Instance .. . 202

6.4.1.3 PATCH - Ethernet Interface Instance.. . 206

6.4.2 BIOS Configuration .. . 208

6.4.2.1 GET - HostInterface Instance . . 208

6.4.2.2 GET – BIOS and BIOS/SD .. . 209

6.4.2.3 POST – Reset BIOS Settings . . 210

6.4.2.4 POST – Change BIOS Password . . 210

6.4.2.5 PATCH – BIOS SD . ..211

6.4.3 x86 Watchdog Configuration . 212

6.4.3.1 GET - BIOS Watchdog Configuration .. . 212

6.4.3.2 PATCH - BIOS Watchdog Configuration.. . 213

6.4.4 Sensor Information. . 214

6.4.5 BMC Update.. . 218

6.4.5.1 GET - Preserve Configuration .. . 218

6.4.5.2 PATCH - Preserve Configuration . . 219

6.4.5.3 POST – Firmware Update . . 220

6.4.6 BIOS Update. 223

6.4.6.1 GET - BIOS Update Status.. . 223

6.4.6.2 POST – Firmware Update . . 224

6.4.7 CPLD Update.. . 228

6.4.7.1 GET - CPLD Update Status.. . 228

6.4.7.2 POST – Firmware Update . . 228

6.4.8 Power Control . 231

6.4.9 Firmware and Hardware Versions.. . 232

6.4.10BIOS Version.. 233

Important Safety Instructions... . 234

Consignes de Sécurité Importantes.. . 236

Getting Service.. . 238

# Overview

# 1.1 Introduction

The ADLINK AXE-7220SR is a 2U 19" rackmount edge computing server with $4 ^ { \mathrm { t h } } 8 5 ^ { \mathrm { t h } }$ Gen Intel® Xeon® Scalable Family Processor. The AXE-7220SR features an I/O intensive architecture with up to 2x PCIe x16 Gen4 FHFL & 1x PCIe x8 Gen4 FHHL, 4x 2.5’’ SATA drive bays, 2x SFP28 ports, and 2x 1GbE ports. It also features IEEE 1588v2 Precision Time Protocol (PTP) and is an ideal platform for 5G mobile edge computing infrastructure deployment. And it is also worked with GPU.

The main features of the AXE-7220SR as follows:

• Intel® Sapphire Rapids-SP/EE Family Processor
• 6x DDR5 DIMMs, 4800MT/s (6 channels, 1DPC)
On-board 2x 25G SFP28 Ethernet ports
• 2U 19’’ rackmount form factor for telecom infrastructure deployment
• Motherboard shared by 2U systems supporting varying storage bays and PCIe slots
• RunBMC with AST2600, IPMI v2.0/Redfish compliant
• Designed for 5G: DU,DU+CU, DU+CU+MEC, MEC, uCPE and GPU server

# 1.2 Block Diagram

![The provided flowchart depicts the connectivity of a mainboard system, centered around a CPU, PCH (Platform Controller Hub), and a 260PIN SODIMM interface.\n\n**1. CPU and Memory (Top Section)**\n*   **Block:** **CPU 150W/225W Sapphire Rapid**\n    *   **Connections:**\n        *   Connects to **DIMM1 DDR5 RDIMM**, **DIMM2 DDR5 RDIMM**, and **DIMM3 DDR5 RDIMM** (via lines labeled A, B, C, D).\n        *   Connects to **DIMM4 DDR5 RDIMM**, **DIMM5 DDR5 RDIMM**, and **DIMM6 DDR5 RDIMM** (via lines labeled E, F, G, H).\n        *   Connects to **RC X8 CARD** via **CN29** and **PCIE GEN4 x8**.\n        *   Connects to **25GbE E810-XXVAM2** via **PCIE GEN3 x8**.\n        *   Connects to **RC CARD** via two **PCIE GEN4 x16** links.\n        *   Connects to **PCH Emmitsburg** via **DMI x8**.\n\n**2. High-Speed Expansion and Interconnects (Left Side)**\n*   **Block:** **RC X8 CARD** (containing **PCIE 4.0 SLOT** and **PCIE x8 link**)\n    *   **Connections:**\n        *   Connects to **OCULINK CABLE** (containing **Oculink PCIE x8**) via **PCIE 4.0 SLOT**.\n        *   Connects to **25G X2 CONN (SFP28)** via **CN21** and **25G x2**.\n*   **Block:** **25GbE E810-XXVAM2**\n    *   **Connections:**\n        *   Receives connection from **OCULINK CABLE** via **PCIE GEN4 x8**.\n        *   Sends connection to **260PIN SODIMM** via **NC51 MAC3**.\n*   **Block:** **RC CARD** (containing **Riser card**)\n    *   **Internal Labels:** **PCIE_SW**, **PCIE 4.0 x16 or x8 link PCIE_SLOT1 up x16 SLOT**, **PCIE 4.0 x0 or X8 link PCIE_SLOT2 X16 SLOT**, **PCIE 4.0 x16 or x8 link PCIE_SLOT3 x16 SLOT**, **PCIE 4.0 X0 or X8 link PCIE_SLOT4 down x16 SLOT**.\n    *   **Connections:**\n        *   Connects to **CPU**.\n        *   Connects to **RJ45 GBE x2** via **USB2.0**.\n\n**3. Central IO Hub (260PIN SODIMM)**\n*   **Block:** **260PIN SODIMM** (labeled **CN17** at bottom)\n    *   **Connections:**\n        *   Connects to **PCH Emmitsburg** via **NC51 (MAC4)**, **eSPI**, **PCIe GEN2 x1**, and **USB2.0 x2** (labeled **USB2A_10**, **USB2B_12**).\n        *   Connects to **VGA CONN (CN27)** via **VGA**.\n        *   Connects to **CONSOL CONN (RJ45) (CN28)** via **UART**.\n        *   Connects to **SWITCH (SW5)** via **UART**.\n        *   Connects to **RS422 (RJ45) (CN25)** via **UART**.\n        *   Connects to **RGPS (RJ45) (RGP51)** via **UART**.\n        *   Connects to **CLKB DAPU (CN16)** via **UART 4**.\n        *   Connects to **MUX** via **SPI**.\n\n**4. PCH and Peripheral Connections (Right Side)**\n*   **Block:** **PCH Emmitsburg** (with labels **FIA(7:0)**, **FIA(13)**, **FIA(12)**, **FIA(14)**, **USB2_6**, **USB2_10**, **USB2_12**)\n    *   **Connections:**\n        *   Connects to **1GbE I210A** via **PCIe GEN2 x1**.\n        *   Connects to **1GbE I210B** via **PCIe GEN2 x1**.\n        *   Connects to **MID USB (CN20)** via **USB2.0**.\n        *   Connects to **Minisas SATA x4 (CN19)** via **SATA3.0 x4**.\n        *   Connects to **UP (CN28)** via **USB3.0/2.0**.\n        *   Connects to **DOWN** via **USB3.0/2.0**.\n        *   Connects to **M.2 (B-key) SSD or 5G CARD (CN13)** via **USB3.0/2.0**.\n        *   Connects to **M.2 (M key) SATA or NVME (CN5)** via **SATA x1** and **PCIe x2 (or SATA x1)**.\n        *   Connects to **SATA A (RSV) (SATA1)** via **SATA3.0 x1**.\n        *   Connects to **SATA B (RSV) (SATA2)** via **SATA3.0 x1**.\n        *   Connects to **CKLB GPS (CN18)** via **UART0**.\n        *   Connects to **Riser (down and Oculink)** via **UART1**.\n\n**5. Specific Peripheral Blocks**\n*   **Block:** **RJ45 GBE x2** (containing **DOWN** and **UP** labels)\n    *   **Connections:**\n        *   Connects to **1GbE I210A** (labeled **DOWN**).\n        *   Connects to **1GbE I210B** (labeled **UP**).\n*   **Block:** **Minisas SATA x4 (CN19)**\n    *   **Connections:**\n        *   Connects to **RF CARD1** via **S3.22**.\n        *   Connects to **RF CARD2** via **E1.20**.\n*   **Block:** **M.2 (B-key) SSD or 5G CARD (CN13)**\n    *   **Connections:** Connects to **SIM (CN15)**.\n*   **Block:** **SWITCH (SW5)**\n    *   **Connections:** Connects to **JUMPER (CN23)** via **UART1** and **UART5**.\n\n**6. Boot and Control Logic (Bottom Left)**\n*   **Block:** **Main BIOS ROM (BIOS1)**\n    *   **Connections:** Connects to **MUX**.\n*   **Block:** **MUX**\n    *   **Connections:**\n        *   Connects to **TPM** (labeled **TPM**) via **SPI** and **TPM_CN1**.\n        *   Connects to **260PIN SODIMM** via **SPI**.\n*   **Block:** **CPLD 10M50DA**\n    *   **Connections:** Connects to **BMC SMBUS** (indicated by a dashed arrow).](.axe-7220sr-50m-22810-1000-10/c752fd578263327e50687aa82f29f96360769dc76e97914b9fe300b742dc6750.jpg)

# 1.3 Mechanical Overview

# 1.3.1 AXE-7220SR Rear Panel

![Redundant\nPower Supply\nHeath/Alert/\nHDD LED\n1x FHHL PCIe Slots\n1GbE\n(Host)\nPower\nButton & LED\nConsole Port\n4x FHFL PCIe Slots\nGrounding\nStud\n4x SMA\n2x SFP28\nVGA\n2x USB\n1GbE\n(Host & BMC)\nUID\nButton & LED\nRGPS\n1PPS/TOD Port](.axe-7220sr-50m-22810-1000-10/69e75698019c8b9d5bb69ff2d1c9b173ee1a7c89a3de11d62f198adc81ddf914.jpg)

# 1.3.2 AXE-7220SR Front Panel

![Power/UID\nButton & LED\nFans X 4\n4x SATA Bay\nSATA Order](.axe-7220sr-50m-22810-1000-10/b711e1c73be62af5f4368b4c127ced05901e7fe592fc6d525744002d6c46478c.jpg)

# 1.3.3 AXE-7220SR Internal Layout

![4x SATA\nDrive Bays\nFans\n6x DDR5 DIMM\nM.2\nSATA/NVM\nE Slot\n2x PCIe x16\nGen4 FHFL\nPSU\nM.2 SATA B-key 2280/5G Module\n3052 Slot Card (under the clock)](.axe-7220sr-50m-22810-1000-10/e7fa3409f79bf414401e4a2c6cd785a38c96350663eaf94e69518c882d39f77b.jpg)

See 3.1 Removing the Chassis Cover on page 17 for instructions on removing the cover.

# 1.3.4 Mechanical Dimensions

Units: mm

![Technical line drawing of a rectangular device with dimension annotations (451.10 and 2), no readable text or symbols present.](.axe-7220sr-50m-22810-1000-10/bd1275ea417c9a44ad8870599fabc2ab682ed9f3777d153b8e2a07a02e61d076.jpg)

![Back panel of a server rack with multiple ports and connectors, dimension标注 438 (no text or symbols on the device itself)](.axe-7220sr-50m-22810-1000-10/922172cabe7a178d1dc7ec7ad58267b65fedbddee76cf1e6549864aabd74c214.jpg)

![Technical line drawing of a vertical panel with mounting holes and a dimension label (87), no readable text or symbols present.](.axe-7220sr-50m-22810-1000-10/df65e4880b91665115680f1cff55e7c878b0851e0482b08e5d7622b9c3509452.jpg)

# 2 Specifications

# 2.1 AXE-7220SR Specifications

Main System

<table><tr><td>CPU</td><td>Single 4th or 5th Gen Intel Xeon Scalable processor, up to 225W TDP</td></tr><tr><td>Chipset</td><td>Intel® C740 Series chipsets</td></tr><tr><td>Memory</td><td>6x DDR5 DIMM, Max. 4800MT/s (6 channels, 1DPC)</td></tr><tr><td>BIOS</td><td>AMI BIOS on SPI flash memory</td></tr><tr><td>Operating System</td><td>Ubuntu 22.04Microsoft Windows Server 2019CentOS Linux 7.8</td></tr><tr><td>Hardware Acceleration</td><td>QAT supported by SPR-SP processor SKU</td></tr><tr><td>Trusted Platform Module</td><td>Plug-in TPM 2.0 module</td></tr><tr><td>Chassis Management</td><td>IPMI v2.0/Redfish compliant with iKVM and SOL support</td></tr></table>

Interfaces

<table><tr><td>Expansion</td><td>2x FHFL single/dual PCIe x16 Gen4 slot (via riser card) or4x FHFL single PCIe x8 Gen4 slot+1x FHHL single PCIe x16 Gen4 slot with x8 lanes (via riser card)</td></tr><tr><td>Ethernet</td><td>2x 1G RJ45 Ethernet port2x 25G SFP28 Ethernet ports</td></tr><tr><td>Remote Console</td><td>1x RJ-45 serial port</td></tr><tr><td>USB</td><td>2x USB 3.0 (5V/0.9A) / USB 2.01x USB 2.0 Header (internal)</td></tr><tr><td>Other</td><td>1x VGA port</td></tr><tr><td>LEDs</td><td>Health, Alert, HDD, Power, UID</td></tr><tr><td>Control Buttons</td><td>Power, UID (front access)</td></tr><tr><td>Internal</td><td>2x 1pps MMCX header</td></tr></table>

Storage

<table><tr><td>Drive Bays (SKU dependent)</td><td>SKU1: 2x 2.5” SATA 6Gb/s</td></tr><tr><td>Internal</td><td>2x onboard M.2 NVME/SATA socket</td></tr></table>

Mechanical & Environmental

<table><tr><td>Form Factor</td><td>2U 19” rackmount 438mm x 87mm x 451.1mm (WxHxD)</td></tr><tr><td>Fans</td><td>4x fans, smart fan speed control</td></tr><tr><td>Power</td><td>800W/1300W/1600W 1+1 redundant PSUsAC: 100V to 240V AC @50-60Hz</td></tr><tr><td>Temperature &amp; Humidity</td><td>Operating: 10% to 95% RH @40°C, non-condensingStorage: 5% to 90% RH, non-condensing</td></tr><tr><td rowspan="2">Shock</td><td>Operating: half-sine 2G, 11ms pulse, 100 pulses on each of three axes</td></tr><tr><td>Non-operating: trapezoidal, 25G, 170 inches/sec delta V, three drops on each of three axes</td></tr><tr><td>Vibration</td><td>Non-operating: 2.2Grms, 10 minutes per axis on all three axes</td></tr><tr><td>Acoustic</td><td>Sound pressure &lt; 75 dBA @1m with all fans maximum speed</td></tr><tr><td>Certifications (TBC)</td><td>FCC, CE, CCC Class A, UL, CB and RoHS compliantNote: Certifications were passed with 1600W PSU installed.</td></tr><tr><td>MTBF</td><td>150,000 hours (TBC)</td></tr></table>

# 3 Getting Started

# 3.1 Removing the Chassis Cover

Follow the instructions below to remove the chassis top cover.

![The image displays a standard warning sign. It features a yellow equilateral triangle with a thick black border. Inside the triangle is a large black exclamation point. Below the triangle, the word 'CAUTION:' is printed in black, capital letters.](.axe-7220sr-50m-22810-1000-10/737cb98d0ccc610dc84fe30993ec010d9cf23dc6d11403cc036289c9f0ec1aec.jpg)
mise en garde

All installation procedures are restricted to skilled personnel.

Toutes les procédures d'installation sont réservées au personnel qualifié.

1. Loosen the two screw one on each side of the chassis (arrow).
2. Press down on the two depressions with your thumbs and slide the cover towards the rear of the chassis and remove the cover.

![Pure diagram of a rectangular structure with directional arrows and no text or symbols](.axe-7220sr-50m-22810-1000-10/2f1a73c63e8abcdbf7076f0b849359cc3d662d198ba7ca1a2586ac0aba26d69c.jpg)

# 3.2 Installing Memory Modules

![ASSEMBLY INSTRUCTIONS:\n1. MOVE ALL 4 WIRESTO LOOKED POSITION\n2. TORQUE-4 NUTS TO 6-12IN-LB](.axe-7220sr-50m-22810-1000-10/e46065ba9a8f5da6bb2671011bed2897dbe10f10eb21b0e8008c365101ee14f7.jpg)

Sapphire Rapids DDR5 only DIMM configurations Diagram

<table><tr><td rowspan="2">DIMM Quantity</td><td colspan="6">AXE-7220SR DIMM</td></tr><tr><td>DIMM1</td><td>DIMM2</td><td>DIMM3</td><td>DIMM4</td><td>DIMM5</td><td>DIMM6</td></tr><tr><td>1DIMM</td><td></td><td></td><td>V</td><td></td><td></td><td></td></tr><tr><td>1DIMM</td><td></td><td></td><td></td><td>V</td><td></td><td></td></tr><tr><td>1DIMM</td><td></td><td>V</td><td></td><td></td><td></td><td></td></tr><tr><td>2DIMM</td><td></td><td></td><td>V</td><td></td><td>V</td><td></td></tr><tr><td>2DIMM</td><td>V</td><td></td><td></td><td>V</td><td></td><td></td></tr><tr><td>4DIMM</td><td>V</td><td></td><td>V</td><td>V</td><td>V</td><td></td></tr><tr><td>6DIMM</td><td>V</td><td>V</td><td>V</td><td>V</td><td>V</td><td>V</td></tr></table>

![The image features a yellow triangular warning sign with a black border containing a black exclamation point. Below the triangle, the text 'CAUTION:' is written in black capital letters.](.axe-7220sr-50m-22810-1000-10/44bab64df4db7cab55e3e773c0e91279ad525d0bf34343355f824fd4fea77435.jpg)
mise en garde

All installation procedures are restricted to skilled personnel.

Toutes les procédures d'installation sont réservées au personnel qualifié.

# 3.3 PCIe Card Installation

Sample installation instructions for FHFL PCIe expansion cards are described below. For detailed information on the specific installation procedures for your cards, please contact our ADLINK representative.

![The image displays a standard safety warning sign. It features a yellow triangle with a black border containing a black exclamation point in the center. Directly below the triangle is a white rectangular area with the word 'CAUTION:' printed in black capital letters.](.axe-7220sr-50m-22810-1000-10/c6394f1bf5f373cff44826767fa1328c09b70668912a4a8ecfa6be05f025e7ba.jpg)
mise en garde

All installation procedures are restricted to skilled personnel. Only UL listed PCIe expansion cards or PCIe cards with openings less than 5 mm in any dimension are recommended

Toutes les procédures d'installation sont réservées au personnel qualifié. Seules les cartes d'extension PCIe répertoriées UL ou les cartes PCIe avec des ouvertures inférieures à 5 mm dans n'importe quelle dimension sont recommandées.

# 3.3.1 PCIe x16 Slot

1. Remove the six screws at the positions shown below. Remove the PCIe bracket in the direction of the arrow

![Technical diagram of a computer tower with labeled hardware components and red annotations highlighting specific ports or features.](.axe-7220sr-50m-22810-1000-10/185b90ad36b122b82b3bd660e6d2c901f3da62bd76a49edd2dd1962e97215221.jpg)

2. . Remove the PCIe panel from the bracket, and remove the pcie rear bkt
![Technical line drawing of a server rack with multiple ports and mounting brackets (no text or symbols)](.axe-7220sr-50m-22810-1000-10/2324ea7837b59e4f45ded93907d2731c5b0da5e6f95251ad9c4a32429c3c84eb.jpg)

![Technical line drawing of a mechanical assembly with multiple parallel plates and mounting brackets (no text or symbols)](.axe-7220sr-50m-22810-1000-10/5d54740be149e2ec5333b791b923d5623fdd2e4d67a27ae2ea4d8048bd035218.jpg)

3. Insert the PCIE card into the CONN of the PCIE Riser board and secure it with a screw at the front panel

![Technical diagram of a NVIDIA server rack with labeled ports and mounting hardware](.axe-7220sr-50m-22810-1000-10/598c9ac65a593e3f7b95d743a8b633cfc3d81625599019a44687d4c9d91c5786.jpg)

4. Insert the PCIe tail fixing bracket with screws.

![Technical diagram of a Huawei networking server rack with labeled hardware components and red circles highlighting specific ports.](.axe-7220sr-50m-22810-1000-10/069df6b48666d6941fe1a7feecf0e3c614826422a5552c0e0d9789988a56fade.jpg)

5. Insert the PCIe component into the chassis and secure it with screws.

![Technical diagram of a server rack with labeled ports and red annotations indicating specific hardware zones.](.axe-7220sr-50m-22810-1000-10/fc5544bc2f2cd6a7a6f41888b09dc16c64e559d143629bb511323eaa259517d7.jpg)

Rear bkt:

![Technical diagram of an internal computer or hardware unit with two red-circled components, no visible text or symbols.](.axe-7220sr-50m-22810-1000-10/baff1ee2ee2d657bcbe2708a1cc8f2988d53829e040249baefea94269adaf6fc.jpg)

# 3.3.2 PCIe x16 Slot with x8 Lanes (SKU2)

1. Remove the six screws at the positions shown below. Remove the PCIe bracket in the direction of the arrow

![Technical diagram of an internal computer drive bay with red annotations highlighting specific components (no text or symbols present)](.axe-7220sr-50m-22810-1000-10/a9fecbb25478ead67c35b84ddf09697b4ba0ef1bcc932b72951eb0ddafd35966.jpg)

2. Remove the PCIe panel from the bracket, and remove the pcie rear bkt

![Technical line drawing of a computer chassis with connectors and ports (no text or symbols)](.axe-7220sr-50m-22810-1000-10/da9fb444ddd8965aa1ad914056554a24413e57b143fdfa4875faeb55e376de67.jpg)

3. Insert the PCIE card into the CONN of the PCIE Riser board and secure it with a screw at the front panel.

![Technical line drawing of a computer chassis panel with mounting holes and a red circular annotation highlighting a component (no text or symbols present)](.axe-7220sr-50m-22810-1000-10/c27d9e4b93367e068e1a887413c7f1fcaf22184bd3799de951e71249ca2e7345.jpg)

4. Insert the PCIe tail fixing bracket with screws.

![Technical line drawing of a computer chassis with mounting holes and highlighted ports (no text or symbols)](.axe-7220sr-50m-22810-1000-10/16a307e4e6ee1771f01d3982a9288450e17c5a020b9ecc92f2397c30ec5550c5.jpg)

5. Insert the PCIe component into the chassis and secure it with screws.

![Technical diagram of an electronic device chassis with labeled components and red arrows indicating features (no text or symbols present)](.axe-7220sr-50m-22810-1000-10/5a4ab3053ae60482e252d8a3dae521aaac6376eda4512fd845203d0537db0834.jpg)

# 3.4 PCIe Slot Secondary Power Supply

The AXE-7220SR is equipped with two 16-pin 12V power connector on the power board to provide secondary power for PCIe expansion cards if required. Two adapter cables are included. The pin definitions of the connectors and cables are described below. (see 1.3.3 AXE-7220SR Internal Layout on page 13)

![The image displays a standard yellow triangular warning sign with a black border and a large black exclamation point in the center. Below the triangle, the text 'CAUTION:' appears in black capital letters. Underneath that, the French text 'mise en garde' is visible.](.axe-7220sr-50m-22810-1000-10/2467ad8b6a00243ebc809284703328a0b160da17129d465c59762e4eeef6389b.jpg)

All installation procedures are restricted to skilled personnel.

Toutes les procédures d'installation sont réservées au personnel qualifié.

# 16-pin 12V Power Connector Pinout

![GND GND GND GND GND GND\n12 11 10 9 8 7\nS4 S3 S2 S1\nGND GND\n6 5 4 3 2 1\n+12V+12V +12V +12V +12V +12V](.axe-7220sr-50m-22810-1000-10/684a8bfbf73a3dbc2b2680393aa4b7422e1363a170953327a2e263404bbc5c54.jpg)

# Adapter Cable Connector Pinout

![P1\n1\n7\nS1\nS4\n6\n12\n30REF\n25REF\n550±20\n30REF\n12\n6\nS4\nS1\nP2\n①②⑦\n⑥\n③④⑤\n7\n1](.axe-7220sr-50m-22810-1000-10/b8c15968c67600052959a1b2eb6077a0162be425c67ce79771e476e20b3c77ba.jpg)

![A red triangle containing the text 'x1'.](.axe-7220sr-50m-22810-1000-10/90b0755c00e9a2a3c95f2915b63a2ddc0f475c7b3ed24b9c0616bca40da8e7b5.jpg)

WIRE LIST
![| Category | Count | Subcategory |\n|---|---|---|\n| P1 | 0 | yellow #16 |\n| P1 | 0 | black #16 |\n| P2 | 0 | 1 |\n| P2 | 0 | yellow #16 |\n| P2 | 0 | black #16 |\n| P2 | 0 | yellow #16 |\n| P2 | 0 | black #16 |\n| P2 | 0 | yellow #16 |\n| P2 | 0 | black #16 |\n| P2 | 0 | yellow #16 |\n| P2 | 0 | yellow #16 |\n| P2 | 0 | yellow #16 |\n| P2 | 0 | yellow #16 |\n| P2 | 0 | yellow #16 |\n| P2 | 0 | yellow #16 |\n| P2 | 0 | yellow #16 |\n| P2 | 0 | yellow #16 |\n| P2 | 0 | yellow #16 |](.axe-7220sr-50m-22810-1000-10/ac7029373677aac60db55615f7630b3969c40b69af03a3b6e7f75070cd33d288.jpg)

![600±10\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30REF\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Ref\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Re\n30Rf\nP1 12 6 S4 7 S1 1 P2 8 5 #1 #2 P2 9 P3 1 4 5 6 7 8 9 1 4 5 6 7 8 9 1 4 5 6 7 8 9 1 4 5 6 7 8 9 1 4 5 6 7 8 9 1 4 5 6 7 8 9 1 4 5 6 7 8 9 1 4 5 6 7 8 9 9 1 4 5 6 7 8 9 1 4 5 6 7 8 9 1 4 5 6 7 8 9 1 4 5 6 7 8 9 1 4 5 6](.axe-7220sr-50m-22810-1000-10/d57a485874c8b1c08b6190a8545add006616176d52aee5abfb1f515bb451fd45.jpg)

![|        | P1  | P2  | P3  |\n| ------ | --- | --- | --- |\n| #16    | 6   |     | 4   |\n| #16    | 5   |     | 5   |\n| #16    | 4   |     | 6   |\n| #16    | 3   |     | 4   |\n| #16    | 2   |     | 5   |\n| #16    | 1   |     | 6   |\n| #16    | 12  |     | 1   |\n| #16    | 11  |     | 2   |\n| #16    | 10  |     | 3   |\n| #16    | 9   |     | 1   |\n| #16    | 8   |     | 2   |\n| #16    | 7   |     | 3   |\n| #28    | S3  |     | #1   |\n| #28    | S4  |     | #2   |\n| #24    |     |     | #24 |\n#1    #24\n#24\n#24\n#24](.axe-7220sr-50m-22810-1000-10/921cc1e13aa569d54cbdfb81fdb40d8f93901362230224d84b3734875baeea0e.jpg)

# 3.5 Rails Assembly and Rack Installation

![The image displays a yellow triangular warning sign with a black border and a black exclamation point in the center. Below the triangle, the text 'CAUTION:' appears in black capital letters. Underneath that, the text 'mise en garde' is partially visible.](.axe-7220sr-50m-22810-1000-10/246e00a51192488eb527f282fec7b5eda27fb77298e9f59186d57f1d8b32f1bd.jpg)

Stability hazard – The rack may tip over causing serious personal injury Before extending the rack to the installation position, read the installation instructions. Do not put any load on the slide-rail mounted equipment in the installation position. Do not leave the slide-rail mounted equipment in the installation position.

Danger d’instabilité - Le rack peut basculer et provoquer des blessures corporelles graves. Avant d’étendre le rack en position d’installation, lire les instructions d’installation. Ne pas charger l’équipement monté sur rail de glissière en position d’installation.

Note: Please check rack post type before proceeding. The pre-installed rail type is for square hole posts. If the rack post has round holes, please switch to the appropriate screws as shown below. Veuillez vérifier le type de poteau de rack avant de continuer. Le type de rail préinstallé est destiné aux poteaux à trous carrés. Si le montant du rack comporte des trous ronds, veuillez utiliser les vis appropriées comme indiqué ci-dessous.

![Left\nRight](.axe-7220sr-50m-22810-1000-10/1b1d6130a03f40624de9f44732d4cfe468801e9531423800b32a2e9a203e2b2e.jpg)

To switch from round hole to square hole, remove the “A” type screws (pre-installed) and switch to “B” type screws.

![A 9.5 Square Hole\n(Pre-installed)](.axe-7220sr-50m-22810-1000-10/582513cca24beb334c643d6f29852c2fcfaa6f13bc16c0f993e58598ac60c93f.jpg)

![⑧ 7.1 Round Hole](.axe-7220sr-50m-22810-1000-10/5b19de8c1a830f278276661446baac30aa75bc432b599f1a91c7db2445be731e.jpg)

1. Remove the inner rail.

![This diagram illustrates the removal of an inner member from a telescoping rail assembly. The labeled blocks and connections are as follows:\n\n*   **Instructional Text:** Located on the left, a block labeled with a circled number **2** reads: 'Pull release button A or B to take out inner member.'\n*   **Inset Box A:** A square box labeled with a circled **A** and a circled number **2** above it. It depicts a release button with a black arrow pointing diagonally left and the text '**Pull**'. A thick black line connects this box to a dashed circle on the rail.\n*   **Inset Box B:** A square box labeled with a circled **B** and a circled number **2** above it. It depicts a different release button design with a black arrow pointing diagonally left and the text '**Pull**'. A thick black line connects this box to a second dashed circle further along the rail.\n*   **Main Rail Assembly:** A long, diagonal metal rail stretches from the bottom left to the top right.\n*   **Label 1:** A circled number **1** is placed near the second dashed circle on the rail, accompanied by the text '**Click!**'.\n*   **Bottom Arrow:** A large, downward-pointing arrow is centered below the rail.](.axe-7220sr-50m-22810-1000-10/f21eefab2ca78ed2aac2b589a451a2b2ea64e735d5a69ec12c5248a99623d859.jpg)

![3 inner rail\nouter rail\nbracket](.axe-7220sr-50m-22810-1000-10/23f2ff77e9829987918579562577926874cf8e2fa899fab432385e57a21f97f6.jpg)

# 2. Install the inner rail onto the chassis.

![1U\n2U\nClick!\nM4x3.2](.axe-7220sr-50m-22810-1000-10/9954c42263e4a9637ba81dd2c4ed7bec4195fcd4a318af86338be360c14bab86.jpg)

# 3. Attach the outer rail/bracket assembly to the rack.

![The diagram illustrates a mechanical assembly process, likely for a drawer slide.\n\n**Top Section:**\nTwo parallel rails are shown at an angle. Dashed circles highlight the locking mechanisms at the ends of the rails. Arrows indicate the rails sliding toward each other to align.\n\n**Step 1:**\nInside a dotted oval labeled **1**, a rectangular block with three vertical slots is aligned with a component containing three cylindrical pins. Three arrows point from the pins toward the slots, indicating insertion.\n\n**Step 2:**\nInside a dotted oval labeled **2**, the pins are shown fully inserted into the slots. The text **Click!** is written next to the assembly.\n\n**Connection:**\nA white arrow points from the **1** oval to the **2** oval.](.axe-7220sr-50m-22810-1000-10/09c7ea0e4ae778bf95a2a23e0657394d1a56552722cc5484d1941e8fe03a9041.jpg)

Note: Front and rear bracket installation procedures are the same. The left and right sides of the rail are symmetrical. Repeat the installation steps for the other side.

4. Insert chassis with mounted inner rails to complete the installation.

Ensure the ball bearing retainer is located at the front of the rail.
Insert the chassis into the outer rails.
When the chassis is fully inserted, pull/push the release tab on the inner rails.
Secure the system to the rack using the captive screws located on the rack handles of the system.

![This flowchart illustrates a four-step installation process for mounting a chassis onto rails within a rack.\n\n**Labeled Blocks:**\n*   **Circle 1:** Located at the top left, highlighting the attachment of the first rail. A magnified inset shows a latch engaging with the text '**Click!**'.\n*   **Circle 2:** Located in the middle left, highlighting the movement of the chassis toward the second rail.\n*   **Circle 3:** Located in the middle, highlighting the attachment of the second rail. A magnified inset shows a latch mechanism with the text '**Pull**'.\n*   **Circle 4:** Located at the far right, highlighting the insertion of the unit into the rack. A magnified inset shows a latch mechanism with the text '**locking**'.\n\n**Connections and Flow:**\n*   **Step 1 to 2:** A black arrow on the chassis points right, indicating it is slid onto the first rail (labeled **1**). A large white arrow points right, showing the chassis moving toward the second rail.\n*   **Step 2 to 3:** The chassis slides onto the second rail. The dashed circle labeled **3** indicates the latch point, and the inset shows a 'Pull' action.\n*   **Step 3 to 4:** A large white arrow points right, showing the fully assembled unit sliding into the rack frame. The dashed circle labeled **4** indicates the final locking mechanism, with an inset arrow showing the latch securing the unit.](.axe-7220sr-50m-22810-1000-10/b3a1e050aa9e00dac8aab450c464e4be7cf8f1c18cd7eea3a68e5a41f0e7ba4e.jpg)

# 3.6 Uninstalling the Rails from the Chassis

M4 x3.2
Release the latch to detach the inner rail.

![Diagram illustrating the internal structure and assembly of a server rack, with numbered annotations indicating component locations.](.axe-7220sr-50m-22810-1000-10/e3ebd9e805df9863b2722641b95c5753fa44731bb643fa58bd3a3652b0e48179.jpg)

Detach the outer rail/bracket assembly from the rack.

![Based on the image provided, here is an accurate description of the diagram's components and flow:\n\n**Labeled Blocks:**\n\n*   **Top Assembly:** Two sets of drawer slides are shown in an extended position.\n    *   The top set features a dashed arrow pointing left, indicating movement toward the other slide part.\n    *   The bottom set features a dashed arrow pointing right, indicating movement away from the drawer.\n*   **Inset 1:** A dotted oval circle labeled with a black circle containing the number **1**. Inside this block is a close-up view of the side of a drawer featuring three screws/knobs. The text **'Pull'** appears below with a curved arrow pointing left.\n*   **Inset 2:** A dotted oval circle labeled with a black circle containing the number **2**. Inside this block is a close-up view of a mounting bracket with three vertical slots. Three arrows point into these slots from the left.\n\n**Connections:**\n\n*   A solid white arrow points from the main bottom drawer slide assembly to **Inset 1**.\n*   A solid white arrow points from **Inset 1** to **Inset 2**.](.axe-7220sr-50m-22810-1000-10/71e69e2e88343b38da89f61664244bad858c3cb714981f3487bd1282363aeb99.jpg)

Note: Front and rear bracket detachment procedures are the same. The left and right sides of the rail are symmetrical. Repeat the steps for the other side.

Loosen the captive screws and then pull out the chassis.
Pull release button A or B to remove the chassis.

![Based on the provided image, here is the description of the flowchart/diagram:\n\n**Labeled Blocks:**\n*   **Top Block:** A server chassis featuring two circular callouts labeled **1**.\n*   **Detail Block (Left):** A dashed circle highlighting a latch mechanism with the text **Release**.\n*   **Middle Block:** The server chassis attached to long mounting rails.\n*   **Bottom Block:** The server chassis showing two highlighted circular areas, with one area marked by a large circle labeled **2**.\n*   **Instruction Blocks (Bottom Left):** Two rounded square boxes.\n    *   One box contains a circular label **B** and an arrow with the text **Pull**.\n    *   The adjacent box contains a circular label **A** and an arrow with the text **Pull**.\n*   **Final Block (Bottom Right):** The server chassis separated from the rails, connected by a dashed line.\n\n**Connections:**\n*   An arrow points from the **Top Block** to the **Detail Block (Left)**.\n*   A large hollow arrow points from the **Top Block** to the **Middle Block**.\n*   An arrow points from the highlighted areas in the **Bottom Block** toward the **Instruction Blocks**.\n*   A large hollow arrow points from the **Middle Block** toward the **Bottom Block**.](.axe-7220sr-50m-22810-1000-10/b0742e31dd32c4a7f602dd12648f6d0546a121d3d323c2d106d244b04d4657eb.jpg)

# 3.7 Connecting the System to Ground

# AC Version

A grounding stud (M4 size) is provided on the rear of the chassis for additional connection to ground. The bonding wire shall be minimum 14 AWG and with green and yellow insulation jacket.

![Grounding\nStud](.axe-7220sr-50m-22810-1000-10/ab9bd548c42520d0f3fe54a50549714e28eba31e118eebcd1afc2295d10c5e3b.jpg)

The others are connected to ground by the PSU ground pin of the 3-prong IEC power cord. Please use the power cord provided with the system for your region.

![Grounding Stud](.axe-7220sr-50m-22810-1000-10/b5e1a21113a4ddc0c7f5e612b9b20ca588ef75ccf7277f2628b1cae634f93e91.jpg)

# 3.8 System Power Cable Installation

# AC PSU Input

3-prong IEC power connector

![3-prong IEC power\nconnector](.axe-7220sr-50m-22810-1000-10/ccd6eb00b9430eb708e74807c142ed169960905100faf8893029f4e7f8adae00.jpg)

![The image displays a yellow triangular warning sign with a black border and a black exclamation point in the center. Below the sign, the text 'CAUTION:' is printed in blue capital letters. Underneath that, the phrase 'mise en garde' is written in black lowercase letters.](.axe-7220sr-50m-22810-1000-10/e394ed60b7bcd206b9c9677e51da72b92b2206c2627e34ce0fd9fc8db919c2a5.jpg)

All installation procedures are restricted to skilled personnel.

The terminal block is suitable for a minimum 14 AWG, minimum 60V, minimum 105 °C, VW-1 power cord. Torque value is 1.2 N·m.

Toutes les procédures d'installation sont réservées au personnel qualifié. Le bornier est adapté à un cordon d'alimentation VW-1 minimum de 14 AWG, minimum 60 V, minimum 105 °C. La valeur de couple est de 1,2 N·m.

# 3.9 Login to the BMC via Console Port

# Step 1

Set the Console Port to BMC mode using the 4-pole DIP Console Port Mode Switch (SW5) on the mother board inside the chassis (see 4.9 Board Layout on page 62).

<table><tr><td>Pin</td><td>Default</td><td>BMC Debug</td></tr><tr><td>1</td><td>On</td><td>Off</td></tr><tr><td>2</td><td>On</td><td>Off</td></tr><tr><td>3</td><td>Off</td><td>On</td></tr><tr><td>4</td><td>Off</td><td>On</td></tr></table>

# Step 2

Use the included RJ-45 to DB-9 console port adapter cable to connect the PC to the RJ-45 console port of the AXE-7220SR (see 1.3.1 AXE-7220SR Front Panel on page 11). See 4.5 Dual USB 3.0 and RJ-45 Console Port on page 58 for the adapter cable pin definition.

![Exterior view of a beige USB cable connector with port pins (no text or symbols visible)](.axe-7220sr-50m-22810-1000-10/23b2ba8b3a4c631ffcb0f07997ef575ffff955df564fca0dbe3af4bce066c812.jpg)

# Step 3

Open a serial port console tool (such as PuTTY), choose the higher COM port (it may be different depending on the computer), then set the baud rate to 115200.

![PuTTY Configuration\nCategory:\nSession\nLogging\nTerminal\nKeyboard\nBell\nFeatures\nWindow\nAppearance\nBehaviour\nTranslation\nSelection\nColours\nConnection\nData\nProxy\nTelnet\nRlogin\nSSH\nSerial\nBasic options for your PuTTY session\nSpecify the destination you want to connect to\nSerial line Speed\nCOM3 115200\nConnection type:\nRaw Telnet Rlogin SSH Serial\nLoad, save or delete a stored session\nSaved Sessions\nCOM3\nDefault Settings\n2600T\n2600_CPU_Server\n2610T\n2610T_board\nCOM3\nCSA-7400\nLoad\nSave\nDelete\nClose window on exit:\nAlways Never Only on clean exit\nAbout Help Open Cancel](.axe-7220sr-50m-22810-1000-10/5a3a47241da9eb4a1724d3e93c038ed06906e7085756f05cb1ccc1d2151eba23.jpg)

# Step 4

Input the user name “sysadmin” and password “superuser” to login to the system.

![AMI00306425F122 login: sysadmin\nPassword:\nlogin(1773): pam_unix(login:account): account sysadmin has password changed in future\nlogin(1773): pam_unix(login:session): session opened for user sysadmin by LOGIN(uid=0)\n(1773 INFO)SERIAL Login from IP:127.0.0.1 user:sysadmin\n\nlogin(1773): (1773 INFO)SERIAL Login from IP:127.0.0.1 user:sysadmin\n\nlogin(1773): root login on 'ttyS4'\n~ #](.axe-7220sr-50m-22810-1000-10/ccb2e690994714823fc5d18b15c6fa73ae7346462b11e29f27af943a3e67422e.jpg)

# 3.10 BMC eth0 Default and Static IP Settings

The default IP setting is DHCP. Users can login to the BMC to modify the IP.

# Static IP Settings:

Show the current LAN setting

 ipmitool lan print 1

Set the IP source to static

 ipmitool lan set 1 ipsrc static

Set the IP address

 ipmitool lan set 1 ipaddr xxx.xxx.xxx.xxx

Set the netmask address

 ipmitool lan set 1 netmask xxx.xxx.xxx.xxx

Set the gateway address

 ipmitool lan set 1 defgw ipaddr xxx.xxx.xxx.xxx

# Restore Default:

Set IP source to DHCP

 ipmitool lan set 1 ipsrc dhcp

Note: BMC IP can be set in the BIOS. See 5.6.1 BMC Network Configuration on page 97.

# 3.11 BMC eth1 Default and Static IP Settings

The default IP setting is DHCP. Users can login to the BMC to modify the IP.

# Static IP Settings:

Show the current LAN setting

 ipmitool lan print 8

Set the IP source to static

 ipmitool lan set 8 ipsrc static

Set the IP address

 ipmitool lan set 8 ipaddr xxx.xxx.xxx.xxx

Set the netmask address

 ipmitool lan set 8 netmask xxx.xxx.xxx.xxx

Set the gateway address

 ipmitool lan set 8 defgw ipaddr xxx.xxx.xxx.xxx

# Restore Default:

Set IP source to DHCP

 ipmitool lan set 8 ipsrc dhcp

Note: BMC IP can be set in the BIOS. See 5.6.1 BMC Network Configuration on page 97.

# 3.12 BIOS Update

Users can update the AXE-7220SR system BIOS over various interfaces (Gigabit LAN, KCS, console port).

# 3.12.1 Updating BIOS via Host with BIOS Tool

1. Boot/Login to Shell
2. Update the BIOS over host with the following commands.

Example:

AfuEfix64 BIOS.ROM /p /b /n /k (to update BIOS without ME)

```c
Shell> fs0:
FS0:\> cd AXE-7220_0510_Image
FS0:\AXE-7220_0510_Image\> dir
Directory of: FS0:\AXE-7220_0510_Image\
12/04/2024 15:17 &lt;DIR&gt; 16,384 .
12/04/2024 15:17 &lt;DIR&gt; 0 ..
06/08/2023 14:44 621,616 AfuEfix64.efi
11/27/2024 10:36 16,777,216 AXE-7220_0510.ROM
11/27/2024 10:39 1,169 HISTORY.txt
11/27/2024 10:40 400 pBIOS.nsh
4 File(s) 17,400,401 bytes
2 Dir(s)
FSO:\AXE-7220_0510_Image\>
```

Note: Updating BIOS via BMC, please refer Chapter 6.

# 3.13 BMC Firmware Update via Network

This section outlines the various methods available for updating the BMC firmware. BMC firmware updates can be performed through three primary methods:

# 1. Web interface update

For detailed steps and guidelines, please refer to Section 6.2.8.1.1 BMC Update.

# 2. Redfish update

3. For detailed steps and guidelines, please refer to Section 6.6.4.5 BMC Update.

# 4. Yafuflash tool update

See below for detailed steps and guidelines.

Yafuflash supports three primary methods for updating BMC firmware: via Network, USB, and KCS. Below is an example via Network and its steps.

# Network Medium:

./Yafuflash -nw -ip [BMC\_ip] -u [username] -p [user password] [FW\_IMAGE\_FILE]

# Example:

./Yafuflash -nw -ip 192.168.0.1 -u admin -p admin.123 rom.ima

This command uses the network to upgrade BMC.

# Step-by-Step Guide (Using Network Update as Example):

# 1. Initiating Update Command:

root@bmc-AXE-7220SR:/home/bmc/yafu/v7-LTS-v13/Linux\_x86\_64# ./Yafuflash -nw -ip 172.20.2.36 -u admin -p admin.123 rom.ima

INFO: Yafu INI Configuration File not found... Default options will not be applied...

Creating IPMI session via network with address 172.20.2.36...Done

\+ +

| YAFUFlash - Firmware Upgrade Utility v7.01.0111 |

| Copyright (c) 2020 American Megatrends International, LLC |

+- ---+

Image to be updated is Inactive Image (Image-2)

Please type (Y/y) to proceed or (N/n) to change the Image:

# Note:

The system will prompt if you want to proceed with updating the inactive image.
Typing Y will proceed with the update, while N will lead to the image selection interface.

# 2. Selecting the Image to Update:

If Y is selected, the system will prompt if you want to proceed with updating the inactive image:

<table><tr><td>+----+</td></tr><tr><td>| YAFUFlash - Firmware Upgrade Utility v7.01.0111 |</td></tr><tr><td>| Copyright (c) 2020 American Megatrends International, LLC |</td></tr><tr><td>+----+</td></tr><tr><td>Image to be updated is Inactive Image (Image-2)</td></tr><tr><td>Please type (Y/y) to proceed or (N/n) to change the Image:y</td></tr><tr><td>The Module root allocated size is different from the one in the Image</td></tr><tr><td>The Module osimage location is different from the one in the Image</td></tr><tr><td>The Module www location is different from the one in the Image</td></tr><tr><td>The Module extlog location is different from the one in the Image</td></tr><tr><td>The Module extlog location is different from the one in the Image</td></tr><tr><td>The Module bootlogo location is different from the one in the Image</td></tr><tr><td>The Module arcity size is different from the one in the Image</td></tr><tr><td>So, type (Y/y) to do Full Firmware Upgrade or (N/n) to exit</td></tr><tr><td>Enter your Option :</td></tr></table>

# If N is selected:

INFO: Yafu INI Configuration File not found... Default options will not be applied...

Creating IPMI session via network with address 172.20.2.36...Done

<table><tr><td>+----+</td></tr><tr><td>| YAFUFlash - Firmware Upgrade Utility v7.01.0111 |</td></tr><tr><td>| Copyright (c) 2020 American Megatrends International, LLC |</td></tr><tr><td>+----+</td></tr><tr><td>Image to be updated is Inactive Image (Image-2)</td></tr><tr><td>Please type (Y/y) to proceed or (N/n) to change the Image:n</td></tr><tr><td>Please type Option &#x27;0&#x27; : to Flash Inactive Image Image-2</td></tr><tr><td>&#x27;1&#x27; : to Flash Image-1</td></tr><tr><td>&#x27;2&#x27; : to Flash Image-2</td></tr><tr><td>&#x27;3&#x27; : to Flash both Images :</td></tr></table>

Note: User will be presented with options to choose which image to update: inactive image, Image-1, Image-2, or both

# 3. Firmware Update Process:

After making the selection, you will be prompted to confirm the update by typing Y.

<table><tr><td colspan="5">Firmware Details</td></tr><tr><td></td><td></td><td>RomImage</td><td>Image 1</td><td>Image 2</td></tr><tr><td>ModuleName</td><td>Description</td><td>Version</td><td>Version</td><td>Version</td></tr><tr><td>1. boot</td><td>BootLoader</td><td>13.5.000000</td><td>13.5.000000</td><td>13.5.000000</td></tr><tr><td>2. conf</td><td>ConfigParams</td><td>13.5.000000</td><td>13.5.000000</td><td>13.5.000000</td></tr><tr><td>3. root</td><td>Root</td><td>13.5.000000</td><td>13.5.000000</td><td>13.5.000000</td></tr><tr><td>4. osimage</td><td>Linux OS</td><td>13.5.000000</td><td>13.5.000000</td><td>13.5.000000</td></tr><tr><td>5. www</td><td>Web Pages</td><td>13.5.000000</td><td>13.5.000000</td><td>13.5.000000</td></tr><tr><td>6. extlog</td><td>ExtendedLog</td><td>13.5.000000</td><td>13.5.000000</td><td>13.5.000000</td></tr><tr><td>7. extlog</td><td>ExtendedLog</td><td>13.5.000000</td><td>13.5.000000</td><td>13.5.000000</td></tr><tr><td>8. bootlogo</td><td></td><td>1.0.000000</td><td>1.0.000000</td><td>1.0.000000</td></tr><tr><td>9. arcity</td><td></td><td>13.5.010003</td><td>13.5.010003</td><td>13.5.010003</td></tr><tr><td colspan="5">Existing Image and Current Image are SameSo, type (Y/y) to do Full Firmware Upgrade or (N/n) to exitEnter your Option :</td></tr></table>

Upon confirmation, the BMC firmware update will begin. The BMC will automatically reboot after the update is completed.

# WARNING!

FIRMWARE UPGRADE MUST NOT BE INTERRUPTED ONCE IT IS STARTED.

PLEASE DO NOT USE THIS FLASH TOOL FROM THE REDIRECTION CONSOLE.

Preserving Env Variables... done

Uploading Firmware Image : 100%... done

Skipping [boot] Module ....

Flashing [conf] Module ....

Flashing Firmware Image : 100%... done

Verifying Firmware Image : 100%... done

Flashing [root] Module ....

Flashing Firmware Image : 100%... done

Verifying Firmware Image : 100%... done

Flashing [osimage] Module ....

Flashing Firmware Image : 100%... done

Verifying Firmware Image : 100%... done

Flashing [www] Module ....

Flashing Firmware Image : 100%... done

Verifying Firmware Image : 100%... done

Flashing [extlog] Module ....

Flashing Firmware Image : 100%... done

Verifying Firmware Image : 100%... done

Flashing [extlog] Module ....

Flashing Firmware Image : 100%... done

Verifying Firmware Image : 100%... done

Flashing [bootlogo] Module ....

Flashing Firmware Image : 100%... done

Verifying Firmware Image : 100%... done

Flashing [arcity] Module ....

Flashing Firmware Image : 100%... done

Verifying Firmware Image : 100%... done

Resetting the firmware.........

# 3.14 BMC Firmware Update via Host with Yafuflash

The AXE-7220SR supports a BMC Chassis Management firmware, IPMI v2.0/Redfish compliant.

To update the BMC firmware via host with Yafuflash, perform the following steps.

1. Login to the OS with root user permission.
2. Update the BMC over host using the commands below:

# KCS Medium:

./Yafuflash -kcs [FW\_IMAGE\_FILE]

# Example:

./Yafuflash -kcs rom.ima

This performs the BMC upgrade via KCS.

# USB Medium:

./Yafuflash -cd [FW\_IMAGE\_FILE]

# Example:

./Yafuflash -cd rom.ima

This command utilizes a USB drive to upgrade BMC.

# 3.15 CPLD Update

This section outlines the various methods available for updating the CPLD firmware. CPLD firmware updates can be performed through four primary methods:

# 1. Web interface update

For detailed steps and guidelines, please refer to Section 6.2.8.1.3 HPM Firmware Update – CPLD/BIOS.

# 2. Redfish update

For detailed steps and guidelines, please refer to Section 6.4.7 CPLD Update.

# 3. Yafuflash tool update

See below for detailed steps and guidelines.

# 4. ipmitool update

For detailed steps and guidelines, please refer to Section 6.3.2.11CPLD Update.

# 3.15.1 Yafuflash

Yafuflash supports three primary methods for updating CPLD firmware: via Network, USB, and KCS. Below are examples and steps for each method.

# Network Medium:

./Yafuflash -nw -ip [BMC\_ip] -u [username] -p [user password] -d 0x04 [HPM\_FILE]

# Example:

./Yafuflash -nw -ip 192.168.0.1 -u admin -p admin.123 -d 0x04 outputjbc\_02b4.hpm

This command uses the network to upgrade CPLD.

# USB Medium:

./Yafuflash -cd -d 0x04 [HPM\_FILE]

# Example:

./Yafuflash -cd -d 0x04 outputjbc\_02b4.hpm

This command utilizes a USB drive to upgrade CPLD.

# KCS Medium:

./Yafuflash -kcs -d 0x04 [HPM\_FILE]

# Example:

./Yafuflash -kcs -d 0x04 outputjbc\_02b4.hpm

This performs the CPLD upgrade via KCS.

# Step-by-Step Guide (Using Network Update as Example):

# 1. Get CPLD Device List

BMC will response what CPLD device is connected to BMC via JTAG/SPI.

root@BMC:/# ./Yafuflash -nw -ip 172.20.2.18 -u admin -p admin.123 -d 0x04 outputjbc\_02b4.hpm

INFO: Yafu INI Configuration File not found... Default options will not be applied...

Creating IPMI session via network with address 172.20.2.18...Done

```txt
| YAFUFlash - Firmware Upgrade Utility v7.01.0111 |
| Copyright (c) 2020 American Megatrends International, LLC |
+----+
Beginning CPLD Update...
Total CPLD Device Count: 1
----
Device Number: 0
----
Device Name: ALTERA 10M50DA CPLD
ID Code: 31050dd
User Code: 00000000
Interface: JTAG
Interface Number: 0
----
Enter a Device Number to Enable CPLD Firmware Update Mode: 0
Enabled CPLD Firmware Update Mode ...
Please type (Y/y) to Update or (N/n) to Cancel
Enter your Option : y
```

Enable CPLD Firmware Update Mode: the user must select one of CPLD, then it will notify the CPLD component to lock that for the firmware update.

Note: If a CPLD firmware has been uploaded, it will print "Error in activate flash mode".

# 2. Firmware Update Processing

```txt
Uploading Image : 100%... done
Flashing Firmware Image : 100%... done
Verifying Firmware Image : 100%... done
```

# 3.16 Enter BIOS Setup

To enter the BIOS setup screen, follow these steps:

1. Power on the AXE-7220SR.
2. Press the &lt;Delete&gt; or &lt;ESC&gt; key on your keyboard when you see the following text prompt: “Press DEL or ESC to enter Setup”.

(Note: If Quick Boot is enabled, the screen below will not display, but pressing the &lt;Delete&gt; or &lt;ESC&gt; key will still allow you to enter the BIOS setup screen.)

![ami™\nVersion 2.22.1292. Copyright (C) 2024 AMI\nAXE-7220 REV:0.5.10\nPress (DEL) or (ESC) to enter setup.\nConfiguring firmware is in progress...\nImporting firmware configuration settings from OData server.](.axe-7220sr-50m-22810-1000-10/988b5fcbb6b2bafea23ea0b9fd2926085e498ee5bffe02d7930b2f165939c8a7.jpg)

3. After pressing the &lt;Delete&gt; or &lt;ESC&gt; key, the main BIOS setup menu will display. You can access the other setup screens from the main BIOS setup menu, such as Chipset and Power menus.

# 3.17 Create a RAID Volume

To create a RAID volume, the RAID option must be enabled in the BIOS so that the system loads the RAID option ROM code (see SATA Configuration on page 72).

1. Go to Platform Configuration > PCH-IO Configuration > SATA and RST Configuration > Controller 1 SATA Configuration.
2. Set SATA Mode Selection to RAID, save changes, and reboot the system.

![Aptio Setup - AMI\nPlatform Configuration\nController 2 SATA And RST Configuration\n^ |Determines how SATA\n* |controller(s) operate.\nSATA Configuration (Enabled) *\nSATA Mode Selection (AHCI) *\nSATA Test Mode (Disabled) *\nAggressive LPM Support (Enabled) *\nForce SATA Gen Speed (Gen3) *\nSATA SGPIO Enable (Enabled) +\nSATA Port 0 (Not Installed) +\nSoftware Preserve /--- SATA Mode Selection ---+\nSATA Port 0 AHCI\nHot Plug RAID\nConfigured as eSATA\nExternal\nSpin Up Device (Disabled) +|Enter: Select\nSATA Device Type (Hard Disk Drive) +|+/-: Change Opt.\nDITO Configuration (Disabled) +|F1: General Help\nDITO Value 625 +|F8: Previous Values\nDM Value 15 +|F9: Optimized Defaults\nSATA Port 1 (Not Installed) +|F10: Save & Exit\nSoftware Preserve Unknown +|ESC: Exit\nSATA Port 1 (Enabled) +\nHot Plug (Disabled) +\nConfigured as eSATA Hot Plug supported v](.axe-7220sr-50m-22810-1000-10/a21a4aec71f612e478ecfbc39f65d2339a692af3310ed7ff87fc454f69da3095.jpg)

# To create a RAID volume, go to the Advanced menu

<table><tr><td>Pcie Delay support [Enabled]Delay Time in Seconds 0ACPI SettingsAST2600 Super IO ConfigurationSerial Port Console RedirectionUSB ConfigurationPCI Subsystem SettingsNetwork Stack ConfigurationRedfish Host Interface SettingsNVMe ConfigurationTrusted ComputingIntel(R) VROC sSATA ControllerIntel(R) Ethernet Controller E810-XXV for SFP -00:30:64:8E:BE:CEIntel(R) Ethernet Controller E810-XXV for SFP -00:30:64:8E:BE:CF</td><td>This formset allows the user to manage RAID volumes on the Intel(R) RAID Controller++: Select Screen↑↓: Select ItemEnter: Select+/-: Change Opt.F1: General HelpF8: Previous ValuesF9: Optimized DefaultsF10: Save &amp; ExitESC: Exit</td></tr></table>

Enter the Intel(R) VROC SATA Controller submenu and click on Create RAID Volume.

<table><tr><td colspan="2">Aptio Setup - AMI Advanced</td></tr><tr><td rowspan="2">Intel(R) VROC 8.0.0.4006 sSATA Driver▶ Create RAID VolumeNon-RAID Physical Disks:▶ Port 4, TS128GMTS552T2 SN:G232820007, 119.24GB▶ Port 6, 2.5&quot; SATA SSD 3TE7 SN:BCA12304180120008, 111.79GB▶ Port 7, 2.5&quot; SATA SSD 3TE7 SN:BCA12304180120006, 111.79GB</td><td>This page allows you to create a RAID volume</td></tr><tr><td>+:-: Select Screen↑↓: Select ItemEnter: Select+/-: Change Opt.F1: General HelpF8: Previous ValuesF9: Optimized DefaultsF10: Save &amp; ExitESC: Exit</td></tr></table>

# 3.18 Clear CMOS

See 4.9 Board Layout on page 60 for the location of the Clear CMOS jumper (J3).

<table><tr><td>J3</td><td>Setting</td></tr><tr><td>1-2</td><td>default</td></tr><tr><td>2-3</td><td>Clear CMOS</td></tr></table>

# 4 System Interfaces

![Health LED\nAlert LED\nHDD LED\nPower\nButton\nand LED\nUID Button and\nLED\n2x SFP28\n▽1 SFP28 △2\nVGA\nRGPS\nConsole\nPort\n2x GbE\nUSB 3.0\n2x USB\n1PPS/TOD\nPorts\n▽I SYN △O\n▽1 GbE △2](.axe-7220sr-50m-22810-1000-10/3419382bbf63e79d07b651a205c62e648d20b32da8c65ed48fda80b886b3c0ce.jpg)

# 4.1 Status LEDs

# Health LED (green)

The Health Behavior LED has the following behavior.

Default: Green indicates healthy BMC status.
Override: User can use the OEM LED command to override the LED status to reflect the system health status.

# Alert LED (red)

Off: Indicates normal system operation. On: Indicates a critical alarm.

# Drive Activity (HDD) LED (yellow)

The Drive Activity (HDD) LED is controlled by SATALED# from the M.2 storage. When SATA storage is active (read/write), the LED will blink.

Note1 : This LED can also be user defined. See 4.7 HDD/User LED Jumper and 4.8 User LED Commands on pages 60 and 58.

Note2 : Only work with M.2 storage.

# Power Button and LED (green/yellow)

The Power LED will light when the system is booted up (S0 state).

Off: No power.
Yellow: Standby power
Green: Main power

# UID Button and LED (blue)

The UID button/indicator is used to conveniently locate the server. The LED can be turned off or on manually by pressing the UID button or remotely controlled by management command.

# 4.2 LAN Ports

<table><tr><td>Pin #</td><td>Signal</td></tr><tr><td>1</td><td>TX1+</td></tr><tr><td>2</td><td>TX1-</td></tr><tr><td>3</td><td>TX2+</td></tr><tr><td>4</td><td>TX2-</td></tr><tr><td>5</td><td>TX3+</td></tr><tr><td>6</td><td>TX3-</td></tr><tr><td>7</td><td>TX4+</td></tr><tr><td>8</td><td>TX4-</td></tr></table>

![LED1\nLED2\n8\n1](.axe-7220sr-50m-22810-1000-10/65b441be35bfaa92150e6929beee05b4b64604607981d6def3e4a7423abcb90b.jpg)

# LAN LED Behaviour

The LAN LEDs are integrated into the RJ-45 connector. Their behavior is as follows:

The LED1 (Speed) indicates the speed of the LAN connection.

<table><tr><td colspan="2">LED1 (Speed)</td></tr><tr><td>10 Mbps</td><td>Off</td></tr><tr><td>100 Mbps</td><td>Green</td></tr><tr><td>1000 Mbps</td><td>Orange</td></tr></table>

The LED2 (Link/Activity) indicates that a link has been established by lighting orange. When data is transmitted the LED blinks orange.

<table><tr><td colspan="2">LED2 (Link/Activity)</td></tr><tr><td>Link with no activity</td><td>Steady</td></tr><tr><td>Link with activity</td><td>Blinking</td></tr></table>

# 4.3 RGPS Port

<table><tr><td>Pin #</td><td>Signal</td></tr><tr><td>1</td><td>P12V</td></tr><tr><td>2</td><td>GND</td></tr><tr><td>3</td><td>CONN_1PPS_RGPS_N</td></tr><tr><td>4</td><td>CONN_TOD_RGPS_TXD_P</td></tr><tr><td>5</td><td>CONN_TOD_RGPS_TXD_N</td></tr><tr><td>6</td><td>CONN_1PPS_RGPS_P</td></tr><tr><td>7</td><td>CONN_TOD_RGPS_RXD_N</td></tr><tr><td>8</td><td>CONN_TOD_RGPS_RXD_P</td></tr></table>

![8\n1](.axe-7220sr-50m-22810-1000-10/fca673dde5a9ba42a3d0262c289385c1a5ee57ff2ecea4a9481ad365ce40a92f.jpg)

# RGPS power setting header

<table><tr><td>J5</td><td>Setting</td></tr><tr><td>1-2</td><td>NO RGPS power (default)</td></tr><tr><td>2-3</td><td>RGPS power</td></tr></table>

# 4.4 SFP+ Ports

<table><tr><td>Pin</td><td>Signal Name</td></tr><tr><td>1</td><td>GND</td></tr><tr><td>2</td><td>TX_FAULT</td></tr><tr><td>3</td><td>TX_DSBL</td></tr><tr><td>4</td><td>SDA</td></tr><tr><td>5</td><td>SCL</td></tr><tr><td>6</td><td>MOD_ABS</td></tr><tr><td>7</td><td>RS0</td></tr><tr><td>8</td><td>RX_OS</td></tr><tr><td>9</td><td>RS1</td></tr><tr><td>10</td><td>GND</td></tr><tr><td>11</td><td>GND</td></tr><tr><td>12</td><td>RD-</td></tr><tr><td>13</td><td>RD+</td></tr><tr><td>14</td><td>GND</td></tr><tr><td>15</td><td>VCCR</td></tr><tr><td>16</td><td>VCCT</td></tr><tr><td>17</td><td>GND</td></tr><tr><td>18</td><td>TX+</td></tr><tr><td>19</td><td>TX-</td></tr><tr><td>20</td><td>GND</td></tr></table>

![20\n11\n1\n10](.axe-7220sr-50m-22810-1000-10/b42d8cdeda0a906f5f9b68a80cae5e2f4b62ca5e071602104df89010f788f3bb.jpg)

SFP+ LED Behavior
![Link\nStatus\nLink\nActivity](.axe-7220sr-50m-22810-1000-10/915b797c170f25ff6ae6b79d11ad266a798524fca4fb70f1e4a8d6d5c0bcd546.jpg)

The LEDs point to the respective port.

<table><tr><td>LED</td><td>Status</td><td>Behavior</td></tr><tr><td rowspan="2">Link Status</td><td>Link up</td><td>Green (blink)</td></tr><tr><td>Link down</td><td>Off</td></tr><tr><td rowspan="2">Link Activity</td><td>Active</td><td>Green 25G / Orange 10G/1G (steady)</td></tr><tr><td>Not active</td><td>Off</td></tr></table>

# 4.5 Dual USB 3.0 and RJ-45 Console Port

<table><tr><td>Pin</td><td>Signal Name</td></tr><tr><td>R1</td><td>N/C</td></tr><tr><td>R2</td><td>N/C</td></tr><tr><td>R3</td><td>COM_TXD</td></tr><tr><td>R4</td><td>GND</td></tr><tr><td>R5</td><td>GND</td></tr><tr><td>R6</td><td>COM_RXD</td></tr><tr><td>R7</td><td>N/C</td></tr><tr><td>R8</td><td>N/C</td></tr><tr><td>U1</td><td>5V</td></tr><tr><td>U2</td><td>USB2_N</td></tr><tr><td>U3</td><td>USB2_P</td></tr><tr><td>U4</td><td>GND</td></tr><tr><td>U5</td><td>SSRX_N</td></tr><tr><td>U6</td><td>SSRX_P</td></tr><tr><td>U7</td><td>GND</td></tr><tr><td>U8</td><td>SSTX_N</td></tr><tr><td>U9</td><td>SSTX_P</td></tr><tr><td>U10</td><td>5V</td></tr><tr><td>U11</td><td>USB2_N</td></tr><tr><td>U12</td><td>USB2_P</td></tr><tr><td>U13</td><td>GND</td></tr><tr><td>U14</td><td>SSRX_N</td></tr><tr><td>U15</td><td>SSRX_P</td></tr><tr><td>U16</td><td>GND</td></tr><tr><td>U17</td><td>SSTX_N</td></tr><tr><td>U18</td><td>SSTX_P</td></tr></table>

![R8\nR1\nU18\nU14\nU10\nU13\nU9\nU5\nU1\nU4](.axe-7220sr-50m-22810-1000-10/eaf7d7b781d8d243da02f9e2f4b2abdf847780084c0a347af1f90adde612ca4b.jpg)

The AXE-7220SR comes with an RJ-45 to DB-9 console port adapter cable.

<table><tr><td>DB-9 Pin</td><td>Signal</td></tr><tr><td>1</td><td>—</td></tr><tr><td>2</td><td>RXD</td></tr><tr><td>3</td><td>TXD</td></tr><tr><td>4</td><td>DTR</td></tr><tr><td>5</td><td>SG</td></tr><tr><td>6</td><td>DSR</td></tr><tr><td>7</td><td>RTS</td></tr><tr><td>8</td><td>CTS</td></tr><tr><td>9</td><td>—</td></tr></table>

![9\n1\nA\n8\nB\n1\nB向](.axe-7220sr-50m-22810-1000-10/efa10f73c9002c693959e1bf7c35df9168ef38e93bac54f31fdf40bf2f0e39f6.jpg)

# 4.6 1PPS/TOD Connector

<table><tr><td>Pin #</td><td>Signal (Upper)</td><td>Signal (Lower)</td></tr><tr><td>1</td><td>NC</td><td>NC</td></tr><tr><td>2</td><td>NC</td><td>NC</td></tr><tr><td>3</td><td>1PPS_TXD_N</td><td>1PPS_RXD_N</td></tr><tr><td>4</td><td>GND</td><td>GND</td></tr><tr><td>5</td><td>GND</td><td>GND</td></tr><tr><td>6</td><td>1PPS_TXD_P</td><td>1PPS_RXD_P</td></tr><tr><td>7</td><td>TOD_TXD_N</td><td>TOD_RXD_N</td></tr><tr><td>8</td><td>TOD_TXD_P</td><td>TOD_RXD_P</td></tr></table>

![1\n8](.axe-7220sr-50m-22810-1000-10/e54ed4e1e1fb9ea83da613408d20ee7f6bbc6c61e7bcf31f750d126dfccf3d90.jpg)

Vi SYN △O

# 4.7 HDD/User LED Jumper

The HDD/User LED Jumper (SW2, see 4.9 Board Layout on page 60) can be used to set the function of the Drive Activity LED (default is Drive Activity).

![1\n2\n3](.axe-7220sr-50m-22810-1000-10/f85fada8b2e3b90d28f93a1728dd30d24c6510589d3f523738a398bb469dc2c0.jpg)

<table><tr><td>SW2</td><td>Setting</td></tr><tr><td>1-2</td><td>HDD Drive Activity (default)</td></tr><tr><td>2-3</td><td>User Defined</td></tr></table>

# 4.8 User LED Commands

# 4.8.1 OEM ADLINK Set LED Status

NetFn=2Eh, Cmd=10h

<table><tr><td>Byte</td><td>Data Field</td></tr><tr><td>1~3</td><td>ADLINK Manufacturer ID -005F13h, LS byte first.</td></tr><tr><td>4</td><td>LED ID:02h = USR LED (Yellow, HDD shared)03h = Alert LED (Red)04h = Health LED (Green)Other values: reserved</td></tr><tr><td>5</td><td>LED Function:00h = LED OFF override.01h - 1Eh = LED BLINKING override. The off duration is specified by the value of this byte, and the on duration is specified by the value of byte 5. Both values specify the time in hundreds of milliseconds (100 ms-3 s).1Fh = LED state is restored to Local Control state20h-FEh ReservedFF = LED ON override</td></tr><tr><td>6</td><td>On-duration:The LED on-time in hundreds of milliseconds if (01h &lt;=Byte 6&lt;=1Eh) and ignored otherwise.Otherwise, this field is ignored and is set to 0h.</td></tr><tr><td></td><td>Response Field</td></tr><tr><td>1</td><td>Completion Code</td></tr><tr><td>2~4</td><td>ADLINK Manufacturer ID -005F13h, LS byte first.</td></tr></table>

# 4.8.2 OEM ADLINK Get LED Status

NetFn=2Eh, Cmd=11h

<table><tr><td>Byte</td><td>Data Field</td></tr><tr><td>1~3</td><td>ADLINK Manufacturer ID -005F13h, LS byte first.</td></tr><tr><td>4</td><td>LED ID:02h = USR LED (Yellow, HDD shared)03h = Alert LED (Red)04h = Health LED (Green)Other values: reserved</td></tr><tr><td></td><td>Response Field</td></tr><tr><td>1</td><td>Completion Code</td></tr><tr><td>2~4</td><td>ADLINK Manufacturer ID D of ran, LS byte first.</td></tr><tr><td>5</td><td>LED ID:02h = USR LED (Yellow, HDD shared)03h = Alert LED (Red)04h = Health LED (Green)Other values: reserved</td></tr><tr><td>6</td><td>LED Function:00h = LED OFF override.01h - 1Eh = LED BLINKING override. The off duration is specified by the value of this byte, and the on duration is specified by the value of byte 7. Both values specify the time in hundreds of milliseconds (100 ms-3 s).1Fh = LED is in Local Control state20h-FEh ReservedFF = LED ON override</td></tr><tr><td>7</td><td>On-duration:The LED on-time in hundreds of milliseconds if (01h Byte 6 1Eh) and ignored otherwise set to 0h.</td></tr></table>

4.9 Board Layout
![A\nB\nG\nO\nN\nI\nL\nJ\nC\nH F R K E M D](.axe-7220sr-50m-22810-1000-10/44cf628ea4771106617dae1ba75714a1531f611df21101bbcf632e8be4bb0694.jpg)

<table><tr><td>A</td><td>Intel® Xeon® Scalable Processor</td><td>J</td><td>Primary BIOS SPI Flash</td></tr><tr><td>B</td><td>DDR5 Socket</td><td>K</td><td>RGPS port</td></tr><tr><td>C</td><td>Port 80 connector</td><td>L</td><td>OCP Connector</td></tr><tr><td>D</td><td>BMC/AXE-7220SR LAN RJ-45</td><td>M</td><td>1PPS+TOD Ports</td></tr><tr><td>E</td><td>Console Port RJ-45 + USB 3.0</td><td>N</td><td>PCIe Connector</td></tr><tr><td>F</td><td>SFP28 Connectors</td><td>O</td><td>Clear CMOS Jumper (J3)</td></tr><tr><td>G</td><td>M.2 Slot</td><td>P</td><td>BMC Mode Switch (SW5)</td></tr><tr><td>H</td><td>Status LEDs</td><td>Q</td><td>HDD/User LED Switch (SW2)</td></tr><tr><td>I</td><td>RunBMC connector</td><td>R</td><td>VGA port</td></tr></table>

# 5 BIOS Setup

# 5.1 BIOS Setup Menu

The BIOS setup utility is invoked by pressing &lt;ESC&gt; or &lt;DEL&gt; keys. User can change BIOS settings during setup utility runs. A system reset is required for new settings to take effect.

In the BIOS setup utility, there are several hot keys are designed for specific purposes, as listed below.

&lt;F1&gt;: General help in setup menu
&lt;F8&gt;: Load previous BIOS values
&lt;F9&gt;: Load BIOS default in setup utility
&lt;F10&gt;: Save & Exit setup utility

To navigate through the BIOS setup menu, use the following.

<table><tr><td>→←</td><td>Left/Right. The Left and Right &lt; Arrow &gt; keys allow you to select a setup screen.For example: Main screen, Advanced screen, Chipset screen, and so on.</td></tr><tr><td>↑↓</td><td>Up/Down The Up and Down &lt; Arrow &gt; keys allow you to select a setup item or sub-screen.</td></tr><tr><td>+-</td><td>Plus/Minus The Plus and Minus &lt; Arrow &gt; keys allow you to change the field value of a particular setup item.For example: Date and Time.</td></tr><tr><td>Tab</td><td>The &lt; Tab &gt; key allows you to select setup fields.</td></tr></table>

# 5.1.1 Menu Selection Bar

The Menu Selection Bar is located at the top of the screen. It displays the top level available menus to the user:

Main Menu
Advanced Menu
Platform Configuration Menu
Server Mgmt
Security Menu
Boot Menu
Save & Exit Menu

# 5.1.2 Menu Conventions

The appearance of the setup menu listed in this chapter is a sample to describe the item list. It is shown on a VT100 terminal via serial console. The menu conventions are as follows.

# Using color

The mandatory BIOS setup fields are in black. The BIOS setup fields currently not used are in grey. The display only strings are in black.

# Using brackets

Editable menu options are marketed with squares ‘[‘ and ‘]’ to distinguish them from display only fields that can’t be modified.

# 5.2 Main Menu

The Main Menu provides read-only information about the system and also allows you to set the system date and time. The tables below show screen shots of the Main menu details, submenus and settings.

<table><tr><td>Main</td><td>Advanced</td><td>Platform</td><td>Configuration</td><td>Socket</td><td>Configuration</td><td>Server</td><td>Mgmt</td><td>Security</td><td>Boot</td><td>&gt;</td></tr><tr><td colspan="11"></td></tr><tr><td colspan="6">BIOS Information</td><td rowspan="2" colspan="5">Set the Date. Use Tab to switch between Date elements.</td></tr><tr><td colspan="4">BIOS Vendor</td><td colspan="2">American Megatrends</td></tr><tr><td colspan="4">BIOS Version</td><td colspan="2">0.5.10</td><td colspan="5">Default Ranges:</td></tr><tr><td colspan="4">Build Date</td><td colspan="2">11/15/2024</td><td colspan="5">Year: 1998-9999</td></tr><tr><td colspan="4">RC Version</td><td colspan="2">107.D20</td><td colspan="5">Months: 1-12</td></tr><tr><td colspan="4">SPS FW Version</td><td colspan="2">6.1.4.5</td><td colspan="5">Days: Dependent on monthRange of Years may vary.</td></tr><tr><td colspan="11">System Information</td></tr><tr><td colspan="4">Project Name</td><td colspan="2">AXE-7220</td><td colspan="5"></td></tr><tr><td colspan="4">CPU Board Version</td><td colspan="2">A2</td><td colspan="5"></td></tr><tr><td colspan="4">CPU Brand String</td><td colspan="2">Intel(R) Xeon(R) Gold 5418N</td><td colspan="5"></td></tr><tr><td colspan="4">CPU Frequency</td><td colspan="2">1.80GHz</td><td colspan="5">&lt;--</td></tr><tr><td colspan="4">Total Memory</td><td colspan="2">16384 MB (DDR5)</td><td colspan="5">&gt; &lt;: Select Screen</td></tr><tr><td colspan="4">Memory Frequency</td><td colspan="2">4000 MHz</td><td colspan="5">^v: Select Item</td></tr><tr><td colspan="4">PCH SKU</td><td colspan="2">EBG B1</td><td colspan="5">Enter: Select+/-: Change Opt.</td></tr><tr><td colspan="4">System Date</td><td colspan="2">[Mon 12/16/2024]</td><td colspan="5">F1: General Help</td></tr><tr><td colspan="4">System Time</td><td colspan="2">[22:58:41]</td><td colspan="5">F8: Previous Values</td></tr><tr><td rowspan="3" colspan="4">Access Level</td><td rowspan="3" colspan="2">Administrator</td><td colspan="5">F9: Optimized Defaults</td></tr><tr><td colspan="5">F10: Save &amp; Exit</td></tr><tr><td colspan="5">ESC: Exit</td></tr></table>

# 5.2.1 BIOS Information

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>BIOS Vendor</td><td>Info-only.American Megatrends</td><td>Display vendor name of system BIOS.</td></tr><tr><td>BIOS Version</td><td>Info-only.x.yy.zz</td><td>Display version of booting BIOS.</td></tr><tr><td>Build Date</td><td>Info-only.MM/DD/YYYY</td><td>It shows the date that BIOS was built.</td></tr><tr><td>MRC Version</td><td>Info-only.xxx.Ryy</td><td>Display the revision of MRC code which is implemented in BIOS.</td></tr><tr><td>ME FW Version</td><td>Info-only.ww:x.y.z.aaa</td><td>Display the version of Intel manageability firmware which is implemented in BIOS.</td></tr></table>

# 5.2.2 System Information

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Project Name</td><td>Info-only.</td><td>Shows Project Name</td></tr><tr><td>CPU Board Version</td><td>Info-only.</td><td>Shows Main Board Version</td></tr><tr><td>CPU Brand String</td><td>Info-only.Intel(R) Core, ...</td><td>Shows what CPU is booting the system.</td></tr><tr><td>CPU Frequency</td><td>Info-only.XXXX MHz</td><td>Shows CPU frequency.</td></tr><tr><td>Total Memory</td><td>Info-only.XXXX MB (DDR4)</td><td>Shows total memory size used on the motherboard and memory type.</td></tr><tr><td>Memory Frequency</td><td>Info-only.XXXX MHz</td><td>Shows memory frequency.</td></tr><tr><td>System Date</td><td>MM/DD/YYYY</td><td>For configuring/showing system date.When setting the Date, usekey to switch between Date elements.</td></tr><tr><td>System Time</td><td>HH:MM:SS</td><td>For configuring/showing system time.When setting the Time, usekey to switch between Time elements.</td></tr><tr><td>Access Level</td><td>Info-only.Administrator/User</td><td>It shows what access level is used to enter BIOS setup menu.</td></tr></table>

# 5.3 Platform Configuration Menu

This menu contains the Platform Configuration settings.

![Aptio Setup - AMI\nMain Platform Configuration Advanced Socket Configuration Server Mgmt\n▶ PCH-IO Configuration\n▶ Miscellaneous Configuration\n▶ Network Configuration\n▶ System Event Log\n------------------\n------------------\nSetup Warning:\nSetting items on this Screen to incorrect\nvalues\nmay cause system to malfunction!\nPCH Parameters\n++: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/c0ae7f141978552170464d68fe10ce5f4c7242fe5781cf2b989684506d2f558f.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>PCH-IO Configuration</td><td>Sub-Menu</td><td>For PCH-IO setting</td></tr><tr><td>Miscellaneous Configuration</td><td>Sub-Menu</td><td>For Miscellaneous Configuration</td></tr><tr><td>Network Configuration</td><td>Sub-Menu</td><td>For configuring Network.</td></tr><tr><td>System Event Log</td><td>Sub-Menu</td><td>System Event Log</td></tr></table>

# 5.3.1 PCH-IO Configuration

![Aptio Setup - AMI\nPlatform Configuration\nPCH-IO Configuration\n► PCI Express Configuration\n► SATA Configuration\nSerial IRQ Mode (Continuous)\nState After G3 (SO State)\nPCI Express\nConfiguration settings\n+: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/35dcf35805e5f8badab246aa4bcffbdb207dc72ef9b1e6b81e17eafe13492975.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>PCI Express Configuration</td><td>Sub-Menu</td><td>PCI Express Configuration</td></tr><tr><td>SATA Configuration</td><td>Sub-Menu</td><td>SATA Configuration</td></tr><tr><td>Serial IRQ Mode</td><td>Quiet Continuous</td><td>Configure Serial IRQ Mode.</td></tr><tr><td>State After G3</td><td>S0 State S5 State</td><td>Specify what state to go to when power is re-applied after a power failure</td></tr></table>

# PCI Express Configuration

![Aptio Setup - AMI\nPlatform Configuration\nPCI Express Configuration\n► PCI Express Root Port Cluster 0(x8)\n► PCI Express Root Port 9(I210)\n► PCI Express Root Port 10(I210)\nPCI Express Root Port Settings.](.axe-7220sr-50m-22810-1000-10/c7d50a4701ac7c2e23e3426e6bdc9b8ea9f9b988435f62a49903a5045b5aa708.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>PCI ExpressConfiguration</td><td>Sub-Menu</td><td>To enable or disable PCI-E Port.</td></tr></table>

# SATA Configuration

![Aptio Setup - AMI\nPlatform Configuration\n► Controller 1 SATA Configuration\n► Controller 2 SATA Configuration\nSATA Controller 1\nDevice Options Settings](.axe-7220sr-50m-22810-1000-10/36026eb9b8dde9039dcc5685a787f0560c80472ed8f6febe0205a8e2c0f52537.jpg)

![Aptio Setup - AMI\nPlatform Configuration\nController 1 SATA Configuration\nSATA Configuration (Enabled)\nSATA Mode Selection (AHCI)\nSATA Port 0 TS64GMTS400 - 64.0 GB\nPort 0 (Enabled)\nHot Plug (Disabled)\nConfigured as eSATA Hot Plug supported\nSATA Port 1 (Not Installed)\nPort 1 (Enabled)\nHot Plug (Disabled)\nConfigured as eSATA Hot Plug supported\nSATA Port 2 (Not Installed)\nPort 2 (Enabled)\nHot Plug (Disabled)\nConfigured as eSATA Hot Plug supported\nSATA test settings\n++: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/8cb34fa7e7c30309532aa6f0e479ed1a79a386b73d6bd90e59d0f39df8330fe7.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>SATA Configuration</td><td>DisabledEnabled</td><td>To enable or disable SATA Controller.</td></tr><tr><td>SATA Mode Selection</td><td>AHCIRAID</td><td>For SATA operating mode setting.</td></tr><tr><td>SATA Port X</td><td>Info Only</td><td>To show installed SATA info</td></tr><tr><td>Port X</td><td>EnableDisable</td><td>To enable or disable this SATA port</td></tr><tr><td>Hot Plug</td><td>EnableDisable</td><td>To enable or disable this port as Hot Pluggable</td></tr></table>

# 5.3.2 Miscellaneous Configuration

<table><tr><td>Miscellaneous Configuration
----
---
Wake On Lan Support [Disable]
Active Video [Auto]
RTC Wake system from [Disable]
S4/S5</td><td>Enable or Disable Wake
On Lan Support</td></tr><tr><td></td><td>+: Select Screen
↑↓: Select Item
Enter: Select
+/-: Change Opt.
F1: General Help
F8: Previous Values
F9: Optimized Defaults
F10: Save &amp; Exit
ESC: Exit</td></tr></table>

Version 2.22.1282 Copyright (C） 2022 AMI

AB

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Wake On LAN Support</td><td>DisabledEnabled</td><td>To enable or disable WOL</td></tr><tr><td>Active Video</td><td>AutoOnboard DevicePCIE Device</td><td>Select BIOS display device</td></tr><tr><td>RTC Wake system from S4/S5</td><td>DisabledEnabled</td><td>System will wake on the day::hr::min::sec specified</td></tr></table>

# 5.3.3 Network Configuration

![Aptio Setup - AMI\nPlatform Configuration\nLegacy Option ROMs (Disabled)\nsupport\nEFI Network (Disabled)\nEnable/Disable Legacy\nPXE Option ROM\nexecution for LANs.\n++: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/72548aba96c9f50ab3a6493141859fe7cec15789290fda6275eaf21940a88777.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Legacy Option ROMs support</td><td>EnabledDisabled</td><td>Enable or disable Legacy PXEOption ROM</td></tr><tr><td>EFI Network</td><td>EnabledDisabled</td><td>Enable or disable EFI Network Driver</td></tr></table>

# 5.3.4 System Event Log

<table><tr><td rowspan="2">System Event Log
----
---
System Errors [Enable]
RAS Log Level [MIN (BASIC_FLOW)]</td><td>System Error
Enable/Disable setup
options.</td></tr><tr><td>+: Select Screen
↑↓: Select Item
Enter: Select
+/-: Change Opt.
F1: General Help
F8: Previous Values
F9: Optimized Defaults
F10: Save &amp; Exit
ESC: Exit</td></tr><tr><td colspan="2">Version 2.22.1282 Copyright (C) 2022 AMI AB</td></tr></table>

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>System Errors</td><td>DisabledEnabled</td><td>To enable or disable system error log</td></tr><tr><td>RAS Log Level</td><td>MIN (BASIC_FLOW)MID (BASIC_FLOW, FUNC_FLOW)MAX(BASIC_FLOW, FUNC_FLOW, REG)</td><td>RAS Log setup options.</td></tr></table>

# 5.4 Advanced Menu

This menu contains the Advanced settings.

![Aptio Setup - AMI\nMain Platform Configuration Advanced Socket Configuration Server Mgmt\nSerial Port Console Redirection\nNVMe Configuration\nPCI Subsystem Settings\nNetwork Stack Configuration\nAdvanced Power Management Configuration\nTrusted Computing\nPcie Delay support (Enabled)\nDelay Time in seconds 0\nTls Auth Configuration\nAll Cpu Information\nEmulation Configuration\nRAM Disk Configuration\nIntel(R) I210 Gigabit Network Connection -\n00:30:64:6F:70:B2\nIntel(R) I210 Gigabit Network Connection -\n00:30:64:6F:70:B3\nPcie Delay support\nfunction, setting delay\ntime to scan PCIe card\n++: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/9109adf12e86ab9624c2ea3b3df3fdd392e60cc406868873b56ea878799abc3c.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Serial Port Console Redirection</td><td>Sub-Menu</td><td>For configuring serial console.</td></tr><tr><td>NVME Configuration</td><td>Sub-Menu</td><td>For NVME devices</td></tr><tr><td>PCI Subsystem Settings</td><td>Sub-Menu</td><td>PCI settings</td></tr><tr><td>Network Stack Configuration</td><td>Sub-Menu</td><td>For configuring Network Stack.</td></tr><tr><td>Advanced Power Management Configuration</td><td>Sub-Menu</td><td>For Advanced Power Management</td></tr><tr><td>Trusted Computing</td><td>Sub-Menu</td><td>For TPM settings</td></tr><tr><td>PCIe Delay support</td><td>Disabled Enabled</td><td>PCIe Delay support function, setting delay time to scan PCIe card default is 0s,max is 10s</td></tr><tr><td>Tls Auth ConfigurationAll CPU InformationEmulation Configuration</td><td>No Detail</td><td>Dynamic page</td></tr><tr><td>Intel(R) I210 Gigabit Network Connection - ...Intel(R) Ethernet Connection E823-L 10GbE SFP+ ...</td><td>Sub-Menu</td><td>Onboard Ethernet controller configuration loaded by EFI driver. The setup page is designed by Intel and is shown when running the Ethernet EFI driver. It is related to the “Network” settings on the Boot setup page.</td></tr></table>

# 5.4.1 Serial Port Console Redirection

![Aptio Setup - AMI\nAdvanced\nCOMO\nConsole Redirection (Enabled)\n► Console Redirection Settings\nCOM1\nConsole Redirection (Disabled)\n► Console Redirection Settings\nCOM2\nConsole Redirection (Disabled)\n► Console Redirection Settings\nCOM3\nConsole Redirection (Disabled)\n► Console Redirection Settings\nCOM4(Pci Bus0,Dev26,Func0)\nConsole Redirection\nConsole Redirection\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection\nConsole Redirection\nConsole Redirection Settings\nConsole Redirection\nConsole Redirection\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection\nConsole Redirection\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nConsole Redirection Settings\nSoftware Setup - AMI Advanced\nConsole Redirection Enable or Disable.\n+:-: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI AB](.axe-7220sr-50m-22810-1000-10/30820c9ed2113432928172086ec51bcedec549f665550f6b5650c1f0da220874.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Console Redirection</td><td>EnabledDisabled</td><td>Enable or disable serial portconsole redirection function.</td></tr><tr><td>Console Redirection Settings</td><td>Sub-Menu</td><td>For configuring serial port settingswhen console redirection functionis enabled.</td></tr></table>

# Serial Port Console Redirection > COM0

<table><tr><td colspan="2">Aptio Setup - AMI Advanced</td></tr><tr><td>COMO
Console Redirection Settings</td><td rowspan="2">Emulation: ANSI:
Extended ASCII char set. VT100: ASCII char set. VT100Plus: Extends VT100 to support color, function keys, etc.
VT-UTF8: Uses UTF8 encoding to map Unicode</td></tr><tr><td>Terminal Type [ANSI]
Bits per second [115200]
Data Bits [8]
Parity [None]
Stop Bits [1]
Flow Control [None]
VT-UTF8 Combo Key [Enabled]</td></tr><tr><td>Support
Recorder Mode [Disabled]
Resolution 100x31 [Disabled]
Putty KeyPad [VT100]</td><td>+: Select Screen
↑↓: Select Item
Enter: Select
+/-: Change Opt.
F1: General Help
F8: Previous Values
F9: Optimized Defaults
F10: Save &amp; Exit
ESC: Exit</td></tr></table>

Version 2.22.1282 Copyright (C) 2022 AMI

AB

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Terminal Type</td><td>VT100VT100+VT-UTF8ANSI</td><td>Configure type of console emulation.Emulation:ANSI: Extended ASCII char set.VT100: ASCII char set.VT100+: Extends VT100 to support color, function keys, etc.VT-UTF8: Uses UTF8 encoding to map Unicode chars onto 1 or more bytes.</td></tr><tr><td>Bits per second</td><td>9600192003840057600115200</td><td>Selects serial port transmission speed.The speed must be matched on the other side. Long or noisy lines may require lower speed.</td></tr><tr><td>Data Bits</td><td>78</td><td>Configure the number of data bits in each transmitted or received serial character for both serial ports.</td></tr><tr><td>Parity</td><td>NoneEvenOddMarkSpace</td><td>Configures if parity bit is generated (transmit data) or checked.A parity bit can be sent with the data bits to detect some transmission errors.Even: parity bit is 0 if the num of 1's in the data bits is even. Odd: parity bit is 0 if num of 1's in the data bits is odd.Mark: parity bit is always 1. Space: Parity bit is always 0. Mark and Space Parity do not allow for error detection.They can be used as an additional data bit.</td></tr><tr><td>Stop Bits</td><td>12</td><td>Configures the number of stop bits transmitted and received in each serial character for both serial ports. Stop bits indicate the end of a serial data packet. (A start bit indicates the beginning). The standard setting is 1 stop bit. Communication with slow devices may require more than 1 stop bit.</td></tr><tr><td>Flow Control</td><td>NoneHardware RTS/CTS</td><td>Configures flow control for console redirection. Hardware flow control uses RTC/CTS.</td></tr><tr><td>VT-UTF8 Combo Key Support</td><td>DisabledEnabled</td><td>Enable VT-UTF8 Combination Key Support for ANSI/VT100 terminals</td></tr><tr><td>Recorder Mode</td><td>DisabledEnabled</td><td>This mode only text wil be sent</td></tr><tr><td>Resolution 100x31</td><td>DisabledEnabled</td><td>To enable or disable extended terminal resolution</td></tr><tr><td>Putty Keypad</td><td>VT100</td><td>Select Function Key and keypad on Putty</td></tr></table>

# 5.4.2 NVMe Configuration

<table><tr><td colspan="3">Aptio Setup - AMI Advanced</td></tr><tr><td>Seg:Bus:Dev:Func</td><td>00:02:00:00</td><td rowspan="6">Select either Short or Extended Self Test. Short option will take couple of minutes and extended option will take several minutes to complete.</td></tr><tr><td>Model Number</td><td>TS256GMTE452T</td></tr><tr><td>Total Size</td><td>256.0 GB</td></tr><tr><td>Vendor ID</td><td>126F</td></tr><tr><td>Device ID</td><td>2263</td></tr><tr><td>Namespace: 1</td><td>Size: 256.0 GB</td></tr><tr><td>Device Self Test: Self Test Option</td><td>[Short]</td><td rowspan="7">+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save &amp; Exit ESC: Exit</td></tr><tr><td>Self Test Action</td><td>[Controller Only Test]</td></tr><tr><td>Run Device Self Test</td><td></td></tr><tr><td>Short Device Selftest</td><td>[Not Available]</td></tr><tr><td>Result</td><td></td></tr><tr><td>Extended Device</td><td>[Not Available]</td></tr><tr><td>Selftest Result</td><td></td></tr></table>

Version 2.22.1282 Copyright (C) 2022 AMI

AB

# 5.4.3 PCI Subsystem Settings

<table><tr><td rowspan="2">PCI Bus Driver Version A5.01.26
PCI Devices Common Settings:
Above 4G Decoding [Enabled]
SR-IOV Support [Enabled]</td><td>Enables or Disables
64bit capable Devices
to be Decoded in Above
4G Address Space (Only
if System Supports 64
bit PCI Decoding).</td></tr><tr><td>+:-: Select Screen
↑↓: Select Item
Enter: Select
+/-: Change Opt.
F1: General Help
F8: Previous Values
F9: Optimized Defaults
F10: Save &amp; Exit
ESC: Exit</td></tr><tr><td colspan="2">Version 2.22.1282 Copyright (C) 2022 AMI AB</td></tr></table>

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Above 4G Decoding</td><td>DisabledEnabled</td><td>To enable or disable decoded in above 4G address space.</td></tr><tr><td>SR-IOV Support</td><td>DisabledEnabled</td><td>Enable or disable Single Root IO virtualization support</td></tr></table>

# 5.4.4 Network Stack Configuration

<table><tr><td colspan="2">Aptio Setup - AMI Advanced</td></tr><tr><td>Network Stack [Disabled]</td><td>Enable/Disable UEFI Network Stack</td></tr><tr><td></td><td>+:-: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save &amp; Exit ESC: Exit</td></tr><tr><td colspan="2">Version 2.22.1282 Copyright (C) 2022 AMI AB</td></tr></table>

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Network Stack</td><td>DisabledEnabled</td><td>To enable or disable network stack.</td></tr></table>

# 5.4.5 Advanced Power Management

<table><tr><td colspan="2">Aptio Setup - AMI Advanced</td></tr><tr><td>Advanced Power Management Configuration
--------CPU P State Control
▶ Hardware PM State Control
▶ CPU C State Control
▶ Package C State Control
▶ CPU Thermal Management
▶ CPU - Advanced PM Tuning</td><td>P State Control
Configuration Sub Menu,
include Turbo, XE and
etc.</td></tr><tr><td></td><td>+: Select Screen
↑↓: Select Item
Enter: Select
+/-: Change Opt.
F1: General Help
F8: Previous Values
F9: Optimized Defaults
F10: Save &amp; Exit
ESC: Exit</td></tr><tr><td colspan="2">Version 2.22.1282 Copyright (C) 2022 AMI AB</td></tr></table>

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>CPU P State Control</td><td>Sub-Menu</td><td>P State Control (Turbo, EIST and ETC.)</td></tr><tr><td>Hardware PM State Control</td><td>Sub-Menu</td><td>Hardware P-State settings</td></tr><tr><td>CPU C State Control</td><td>Sub-Menu</td><td>CPU C State settings</td></tr><tr><td>Package C State Control</td><td>Sub-Menu</td><td>Package C State settings</td></tr><tr><td>CPU Thermal Management</td><td>Sub-Menu</td><td>CPU Thermal related settings</td></tr><tr><td>CPU – Advanced PM Tuning</td><td>Sub-Menu</td><td>Advanced PM Tuning settings</td></tr></table>

# CPU P State Control

<table><tr><td rowspan="2" colspan="2">CPU P State ControlSpeedStep (Pstates) [Enable]Boot performance mode [Max Performance]Energy Efficient Turbo [Enable]Turbo Mode [Enable]</td><td>Enable/Disable EIST(P-States)</td></tr><tr><td>++: Select Screen↑↓: Select ItemEnter: Select+/-: Change Opt.F1: General HelpF8: Previous ValuesF9: Optimized DefaultsF10: Save &amp; ExitESC: Exit</td></tr><tr><td colspan="3">Version 2.22.1282 Copyright (C) 2022 AMIAB</td></tr></table>

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>SpeedStep (Pstates)</td><td>DisableEnable</td><td>Enhanced Intel SpeedStep Technology</td></tr><tr><td>Boot performance mode</td><td>Max PerformanceMax EfficientSet by Intel Node Manager</td><td>Select the performance state that the BIOS will set before OS hand off.</td></tr><tr><td>Energy Efficient Turbo</td><td>DisableEnable</td><td>Energy Efficient Turbo Disable, MSR 0x1FC [19]</td></tr><tr><td>Turbo Mode</td><td>DisableEnable</td><td>Enable/Disable processor Turbo Mode</td></tr></table>

# Hardware PM State Control

![Aptio Setup - AMI\nAdvanced\nHardware PM State Control\nHardware P-States (Native Mode)\nDisable: Hardware\nchooses a P-state based\non OS Request (Legacy\nP-States)\nNative Mode: Hardware\nchooses a P-state based\non OS guidance\nOut of Band\n+: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/112bb10bc7de000aa3b268750b663d9a24bf2b510868ab3cd986b9c566c83bc1.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Hardware P-States</td><td>DisableNative ModeNative Mode with No Legacy Support</td><td>Disable: Legacy P-States.Native Mode: Hardware chooses a P-state based on OS guidance.Native Mode with No Legacy Support: Hardware autonomously chooses a P-state.</td></tr></table>

# CPU C State Control

<table><tr><td rowspan="2">CPU C State ControlEnable Monitor MWAIT [Enable]CPU C1 auto demotion [Enable]CPU C1 auto undemotion [Enable]CPU C6 report [Auto]Enhanced Halt State [Enable](C1E)OS ACPI Cx [ACPI C2]</td><td>Allows Monitor andMWAIT instructions.</td></tr><tr><td>++: Select Screen↑↓: Select ItemEnter: Select+/-: Change Opt.F1: General HelpF8: Previous ValuesF9: Optimized DefaultsF10: Save &amp; ExitESC: Exit</td></tr><tr><td colspan="2">Version 2.22.1282 Copyright (C) 2022 AMIAB</td></tr></table>

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Enable Monitor MWAIT</td><td>Disable Enable</td><td>Allows Monitor and MWAIT instructions</td></tr><tr><td>CPU C1 auto demotion</td><td>Disable Enable</td><td>Allows CPU to automatically demote to C1. Takes effect after reboot</td></tr><tr><td>CPU C1 auto undemotion</td><td>Disable Enable</td><td>Allows CPU to automatically undemote from C1</td></tr><tr><td>CPU C6 report</td><td>Disable/Enable/Auto</td><td>Enable/Disable CPU C6(ACPI C3) report to OS</td></tr><tr><td>Enhanced Halt State (C1E)</td><td>Disable/Enable</td><td>Core C1E auto promotion Control.</td></tr><tr><td>OS ACPI Cx</td><td>ACPI C2 ACPI C3</td><td>Report CC3/CC6 to OS ACPI C2 or ACPI C3</td></tr></table>

# Package C State Control

![Aptio Setup - AMI\nAdvanced\nPackage C State Control\nPackage C State (C0/C1 state)\nC2C3TT 0\nDynamic L1 (Enable)\nPKG C-state Lat. Neg. (Disable)\nLTR IIO Input (Ignore IIO LTR input.)\nPackage C State limit\n+:-: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/00e31840285a87808bf188421ca86cf8eccd75c08f75cd6a559ccf3ba9e8866e.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Package C State Control</td><td>C0/C1 stateC2 stateC6 (non-retention) stateAuto</td><td>Package C State limit</td></tr><tr><td>C2C3TT</td><td>0</td><td>Default = 0, means [AUTO]</td></tr><tr><td>Dynamic L1</td><td>DisableEnable</td><td>PCU_MISC_CONFIG Bit[21] = dynamic L1 enable</td></tr><tr><td>PKG C-state Lat. Neg.</td><td>Disable/Enable</td><td>MSR 1FCh Bit[30]PCH_NEG_DISABLE</td></tr><tr><td>LTR IIO Input</td><td>Take IIO LTR input.Ignore IIO LTR input</td><td>MSR 1FCh Bit[29] = LTR_IIO_DISABLE.Disable = Ignore IIO LTR input</td></tr></table>

CPU Thermal Management
![Aptio Setup - AMI\nAdvanced\nCPU Thermal Management\n▶ CPU T State Control\nCPU T State setting](.axe-7220sr-50m-22810-1000-10/91956665dc337585ec169f345b0144ecef32f5f4b75984731abd8431ee369e19.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>CPU T State Control</td><td>Sub-menu</td><td>CPU T State settings</td></tr></table>

![Aptio Setup - AMI\nAdvanced\nCPU T State Control\nSoftware Controlled (Disable)\nT-States\nEnable/Disable Software\nControlled T-States](.axe-7220sr-50m-22810-1000-10/b3ccda5ebce3e7d3894fff838e50c672c0d24d9ae20e8c186b4b7ac6c0eee008.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Software Controlled T-States</td><td>Disable Enable</td><td>Software Controlled T State setting</td></tr></table>

CPU-Advanced PM Tuning
![Aptio Setup - AMI\nAdvanced\nCPU - Advanced PM Tuning\nUncore Freq Scaling (Enable)\nUncore Freq RAPL (Enable)\nIf disable, user can\ninput Uncore Frequency.](.axe-7220sr-50m-22810-1000-10/f0f0cad5c9a5fb49556cd821e895e65b85d6495f6f957ee1dfb53c126759d9c9.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Uncore Freq Scaling</td><td>DisableEnable</td><td>If disable, user can input Uncore Frequency</td></tr></table>

# 5.4.6 Trusted Computing

<table><tr><td rowspan="2">Configuration
Security Device [Enable]
Support
Disable Block Sid [Disabled]
NO Security Device
Found</td><td>Enables or Disables
BIOS support for
security device. O.S.
will not show Security
Device. TCG EFI
protocol and INT1A
interface will not be
available.</td></tr><tr><td>+: Select Screen
↑↓: Select Item
Enter: Select
+/-: Change Opt.
F1: General Help
F8: Previous Values
F9: Optimized Defaults
F10: Save &amp; Exit
ESC: Exit</td></tr><tr><td colspan="2">Version 2.22.1282 Copyright (C) 2022 AMI AB</td></tr></table>

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Security Device</td><td>DisabledEnabled</td><td>Enable or Disable security device, such as TPM</td></tr></table>

# 5.4.7 Intel(R) I210 Gigabit Network Connection

When the BIOS boots the system, it will launch the onboard Intel® Ethernet I210 controller’s UEFI driver. The driver provides a setup page for configuring Ethernet parameters and shows information about Ethernet controller. When EFI Network is disabled, the Ethernet UEFI driver is not executed and this setup page will not be shown (see 5.3.3 Network Configuration on page 735).

![Aptio Setup - AMI\nAdvanced\n► Firmware Image Properties\n► NIC Configuration\n► iSCSI Configuration\n► Device Level Configuration\nBlink LEDs 0\nUEFI Driver Intel(R) PRO/1000\n9.7.06 PCI-E\nAdapter PBA 000300-000\nDevice Name Intel(R) I210 Gigabit\nNetwork Connection\nChip Type Intel i210\nPCI Device ID 1533\nPCI Address 03:00:00\nLink Status (Disconnected)\nLink Speed Status (Auto Negotiated)\nView device firmware\nversion information.\n++: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/5a657378a735fe00ad0da5898bb1755e7ae8ef0957d0e1185d0a68efab0ca8d3.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>NIC Configuration</td><td></td><td>For configuring link speed and wake function.</td></tr></table>

# 5.4.8 Intel(R) Ethernet Connection E823-L for 10GbE

When the BIOS boots the system, it will launch the onboard Intel® Ethernet E823-L controller’s UEFI driver. The driver provides a setup page for configuring Ethernet parameters and shows information about Ethernet controller. When EFI Network is disabled, the Ethernet UEFI driver is not executed and this setup page will not be shown (see 5.3.3 Network Configuration on page 70).

![Aptio Setup - AMI\nAdvanced\n► Firmware Image Properties\n► NIC Configuration\nBlink LEDs 0\nUEFI Driver Intel(R) 100GbE 3.1.18\nAdapter PBA N/A\nDevice Name Intel(R) Ethernet\nConnection E823-L for\nSFP\nChip Type Intel E823-L\nPCI Device ID 124D\nPCI Address F4:00:01\nLink Status (Disconnected)\nMAC Address 00:00:00:00:01:01\nVirtual MAC Address 00:00:00:00:00:00\nView device firmware\nversion information.\n+: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/3ac429a7a93bc321d6b009de2fa4c0da23dc7f5592d9d27cb03c729d747e5a30.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>NIC Configuration</td><td></td><td>For configuring link speed and wake function.</td></tr></table>

# 5.5 Socket Configuration Menu

This menu contains the settings for Socket Configuration.

![Aptio Setup - AMI\nMain Platform Configuration Advanced Socket Configuration Server Mgmt\n► Processor Configuration\n► Common RefCode Configuration\n► Memory Configuration\n► IIO Configuration\nDisplays and provides option to change the Processor Settings\n+:-: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/9b1718c9c1da4349440e4e9afab0d01b257096bf59d569a0779b64ec1a35009b.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Processor Configuration</td><td>Sub-Menu</td><td>For CPU settings</td></tr><tr><td>Common RefCode Configuration</td><td>Sub-Menu</td><td>For RC settings</td></tr><tr><td>Memory Configuration</td><td>Sub-Menu</td><td>PCU_MISC_CONFIG Bit[21] = dynamic L1 enable</td></tr><tr><td>IIO Configuration</td><td>Sub-Menu</td><td>MSR 1FCh Bit[30]PCH_NEG_DISABLE</td></tr></table>

# 5.5.1 Processor Configuration

![Aptio Setup - AMI\nSocket Configuration\nProcessor BSP Revision 606C1 - ICX-D LCC B\nProcessor Socket Socket 0 Socket 1\nProcessor ID 000606C1*\nProcessor Frequency 3.000GHz\nProcessor Max Ratio 1EH\nProcessor Min Ratio 08H\nMicrocode Revision 01000132\nL1 Cache RAM(Per Core) 80KB\nL2 Cache RAM(Per Core) 1280KB\nL3 Cache RAM(Per 15360KB\nPackage)\nProcessor O Version Intel (R)Xeon(R) D-1749 NT CPU @ 3.00GHz\nHyper-Threading (ALL) (Enable)\nEnable Intel(R) TXT (Disable)\nVMX (Enable)\nEnables the Vanderpool\nTechnology, takes\neffect after reboot.\n++: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/7497127e25f746b9290520775aca75edd3b73a49d0402d2654686d054662b73a.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>CPU string</td><td>Info only</td><td>To show CPU info</td></tr><tr><td>Hyper-Threading [ALL]</td><td>DisableEnable</td><td>To enable or disable logical processor threads</td></tr><tr><td>Enable Intel(R) TXT</td><td>DisableEnable</td><td>Enables Intel(R) TXT</td></tr><tr><td>VMX</td><td>EnableDisable</td><td>To enable or disable the Vanderpool Technology(VTx)</td></tr></table>

# 5.5.2 Common RefCode Configuration

![Aptio Setup - AMI\nSocket Configuration\nCommon RefCode Configuration\n----\n---\nMMCFG Base (Auto)\nMMCFG Size (Auto)\nMMIO High Base (2T)\nMMIO High Granularity (64G)\nSize\nNuma (Enable)\nSelect MMCFG Base\n+: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/fa26d49c675a7669c9b780341073c1f4d26ea41daae5ff133dcebf08b73e1e71.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>MMCFG Base</td><td>1G/1.5G/1.75G...Auto</td><td>Select MMCFG Base</td></tr><tr><td>MMCFG Size</td><td>1G/2G...Auto</td><td>Select MMCFG Size</td></tr><tr><td>MMIO High Base</td><td>2T/1T/512G</td><td>Select MMIO High Base</td></tr><tr><td>MMIO High Granularity Size</td><td>16G/64G/256G</td><td>Selects the allocation size used to assign mmioh resources</td></tr><tr><td>Numa</td><td>DisableEnable</td><td>Enable or Disable Non uniform Memory Access</td></tr></table>

# 5.5.3 Memory Configuration

![Aptio Setup - AMI\nSocket Configuration\n----\n---\nIntegrated Memory Controller (iMC)\n----\n---\nEnforce POR    (POR)\nEnforce Population POR    (Enforce Supported\nPopulations)\nMemory Frequency    (Auto)\nIMC BCLK    (Auto)\n► Memory Topology\n► Memory Timings Override\n\nEnable - Enforces Plan\nOf Record restrictions\nfor DDR4 frequency and\nvoltage programming.\nDisable - Disables this\nfeature and user is\nable to run at higher\nfrequencies, specified\n\n+:-: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\n\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/6fb2d6561816f6d86828375ee9b6be736109df4bba34ab19fc8e49594f73487a.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Enforce POR</td><td></td><td></td></tr><tr><td>Enforce Population POR</td><td></td><td></td></tr><tr><td>Memory Frequency</td><td>Auto800100010661200......</td><td>To select maximum memory frequency</td></tr><tr><td>Attempt Fast Boot</td><td>AutoDisableEnable</td><td>To enable or disable skip memory reference code on warm boots, Auto is Enable now</td></tr><tr><td>Attempt Fast Cold Boot</td><td>AutoDisableEnable</td><td>To enable or disable skip memory reference code on cold boots, Auto is Enable now</td></tr></table>

# Memory Topology

![Aptio Setup - AMI\nSocket Configuration\n\n---\nSocket0.ChA.Dimm0: 2666MT/s Transcend SRx8\n16GB RDIMM\nSocket0.ChB.Dimm0: 2666MT/s Transcend SRx8\n16GB RDIMM\n\n---\n+: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\n\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/dacfbc6ad7475d8c0e763f3b820b20d74421cb7621ce6de15cc922a5a21ff5d3.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>SocketX.ChX.DimmX</td><td>Info only</td><td>To show channel /dimm spd info</td></tr></table>

# Memory Timings Override

![Aptio Setup - AMI\nSocket Configuration\nXMP Profile (Disable) Selects the XMP profile to use](.axe-7220sr-50m-22810-1000-10/9bc6613979d9ff4db349c183082e4e091afa861705abba6a9efc9ffa1e184564.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>XMP Profile</td><td>Disable Enable</td><td>To enable or disable Intel Extreme Memory Profiles to support memory over-clock</td></tr></table>

# 5.5.4 IIO Configuration

![Aptio Setup - AMI\nSocket Configuration\n\nIIO Configuration\n---\n► Socket0 Configuration\n► Intel® VT for Directed I/O (VT-d)\n\n+:-: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\n\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/c6dfdc67cb2c9b7410aedd8447de5a8acd03b48aa97e59293b41366ef592ab5b.jpg)

# Sub-Menu: Socket0 Configuration

![Aptio Setup - AMI\nSocket Configuration\nIOUO (IIO PCIe Port 1) (x16)\n► Port 1A\nSelects PCIe port\nBifurcation for\nselected slot(s)\n+: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/d086326b880f2373c4874ad3653035400772eedec67b1755621aa0bd7b82c82d.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>IOU0 (IIO PCIe Port 1)</td><td>X4x4x4x4 / X4x4x8X8x4x4 / X8x8 / X16</td><td>Selects PCIe port bifurcation for riser card upstream port</td></tr><tr><td>Port 1A</td><td>Sub Page</td><td>To show PCIe port link status</td></tr></table>

# Socket0 Configuration > Port 1A

![Aptio Setup - AMI\nSocket Configuration\nPort 1A\nIn auto mode the BIOS\nwill remove the EXP\nport if there is no\ndevice or errors on\nthat device and the\ndevice is not HP\ncapable.\nEnable/Disable is used\nPCI-E Port (Enable)\nLink Speed (Gen 3 (8 GT/s))\nOverride Max Link (x16)\nWidth\nPCI-E Port DeEmphasis (-3.5 dB)\nPCI-E Port Link Status Link Did Not Train\nPCI-E Port Link Max Max Width x16\nPCI-E Port Link Speed Link Did Not Train\n++: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/4fb894c82d2b8980911d97fcf018f5a7b1d26e78354cbac0041f1f03eb96b884.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>PCI-E Port</td><td>Disable/Enable</td><td>To enable or disable PCI-E Port</td></tr><tr><td>Link Speed</td><td>Gen 1 (2.5 GT/s)Gen 2 (5 GT/s)Gen 3 (8 GT/s)</td><td>Choose Link Speed</td></tr><tr><td>Override Max Link Width</td><td>Auto/X1/X2/X4/X8/X16</td><td>Override the max link width that was set by bifurcation</td></tr><tr><td>PCI-E Port DeEmphasis</td><td>-3.5 dB / -6.0 dB</td><td>De-Emphasis control (LNKCON2[6])</td></tr><tr><td>PCI-E Port Link StatusPCI-E Port Link MaxPCI-E Port Link Speed</td><td>Info Only</td><td>To show PCIE-E Port link or lot; width; speed</td></tr></table>

# Intel(R) VT for Directed I/O (vt-d)

![Aptio Setup - AMI\nSocket Configuration\nIntel® VT for Directed I/O (VT-d)\n----\n---\nIntel® VT for (Enable)\nDirected I/O\nEnable/Disable Intel®\nVirtualization\nTechnology for Directed\nI/O (VT-d) by reporting\nthe I/O device\nassignment to VMM\nthrough DMAR ACPI\nTables.\n++: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/aa334f52ffcdf2d85d5c99ce14324102c3c2bcf6a55c6ceac7e9ec04b93a4d74.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Intel(R) VT for Directed I/O (VT-d)</td><td>Disable Enable</td><td>To enable or disable Intel Virtualization Technology for Directed I/O</td></tr></table>

# 5.6 Server Mgmt Menu

This menu contains the Server Management settings.

![Aptio Setup - AMI\nMain Platform Configuration Advanced Socket Configuration Server Mgmt\nBMC Self Test Status PASSED\nBMC Device ID 32\nBMC Device Revision 1\nBMC Firmware Revision 1.02\nIPMI Version 2.0\nIPMI BMC Interface KCS\nBMC Support (Enabled)\nWait For BMC (Enabled)\nTime Zone(UTC Offset) 0x07FF\nCurrent Time Zone +00:00\nPOST Watchdog Timer (Disabled)\nPOST Watchdog timeout (6 minutes)\nPOST Watchdog Timer (Do Nothing)\nPolicy\nOS Watchdog Timer (Disabled)\nOS Wtd Timer Timeout (10 minutes)\nOS Wtd Timer Policy (Reset)\nWait For BMC response\nfor specified time out.\nIn PILOTII, BMC starts\nat the same time when\nBIOS starts during AC\npower ON. It takes\naround 30 seconds to\ninitialize Host to BMC\n+: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/c90e39152e31469e5c5f4805bb3d209e09041e2ab2f701ecb852ff033f7aca2e.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>BMC Self Test Status</td><td>Info-only</td><td>To show BMC self test status</td></tr><tr><td>BMC Device ID</td><td>Info-only</td><td>To show BMC Device ID</td></tr><tr><td>BMC Device Revision</td><td>Info-only</td><td>To show BMC Device Revision</td></tr><tr><td>BMC Firmware Revision</td><td>Info-only</td><td>To show BMC Firmware version</td></tr><tr><td>IPMI Version</td><td>Info-only</td><td>To show IPMI version</td></tr><tr><td>BMC Interfaces(s)</td><td>Info-only</td><td>To show BMC interface such as KCS</td></tr><tr><td>BMC support</td><td>EnabledDisabled</td><td>To enable or disable communicate with BMC</td></tr><tr><td>Wait For BMC</td><td>EnabledDisabled</td><td>To enable or disable wait for BMC 30s before sending Self Test command</td></tr><tr><td>Time Zone (UTC Offset)Current Time Zone</td><td>0x7FFFInfo-only</td><td>Enter UTC Offset in hours, ox7FFF to consider BIOS time as local time</td></tr><tr><td>POST Watchdog Timer</td><td>EnabledDisabled</td><td>Enable or Disable POST Watchdog Timer(FRB-2 timer)</td></tr><tr><td>POST Watchdog timeout</td><td>3mins/4mins5mins/6mins</td><td>Select 3mins/4mins/5mins/6mins for POST Watchdog Timer Expiration value</td></tr><tr><td>POST Watchdog Timer Policy</td><td>Do NothingResetPower DownPower Cycle</td><td>Configure how the system should respond if the POST Watchdog Timer (FRB-2 Timer) expires. Not available if Timer is disabled.</td></tr><tr><td>OS Watchdog Timer</td><td>EnabledDisabled</td><td>If enabled, starts a BIOS timer which can only be shut off by Management Software after the OS loads. Helps determine that the OS successfully loaded or follows the OS Boot Watchdog Timer policy.</td></tr><tr><td>OS Watchdog timeout</td><td>5 minutes10 minutes15 minutes20 minutes</td><td>Select 5mins/10mins/15mins/20mins for OS Boot Watchdog Timer Expiration. Not available if OS Boot Watchdog Timer is disabled.</td></tr><tr><td>OS Watchdog Timer Policy</td><td>Do NothingResetPower DownPower Cycle</td><td>Configure how the system should respond if the OS Boot Watchdog Timer expires. Not available if OS Boot Watchdog Timer is disabled.</td></tr><tr><td>BMC network configuration</td><td>Sub-Menu</td><td>Configure BMC network parameters</td></tr></table>

# 5.6.1 BMC Network Configuration

![Aptio Setup - AMI\nServer Mgmt\n--BMC network configuration--\n******************\nConfigure IPv4 support\n******************\nLan channel 1\nConfiguration Address (DynamicBmcDhcp)\nsource\nCurrent Configuration DynamicAddressBmcDhcp\nAddress source\nStation IP address 0.0.0.0\nSubnet mask 0.0.0.0\nStation MAC address 00-30-64-6F-70-B2\nRouter IP address 0.0.0.0\nRouter MAC address 00-00-00-00-00-00\nLan channel 2\nSelect to configure LAN\nchannel parameters\nstatically or\ndynamically(by BIOS or\nBMC). Unspecified\noption will not modify\nany BMC network\nparameters during BIOS\n++: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/e3db330caef7334eb8bc5c8bfb3d149a7b49724fd2e1f207a551ba6b2549d95b.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Configure IPV4 support</td><td>Read only</td><td></td></tr><tr><td>Configuration Address source</td><td>StaticDynamicBmcDhcp</td><td>Select to configure LAN channel parameters statically or dynamically(by BIOS or BMC)</td></tr><tr><td>Configure IPV6 support</td><td>Read only</td><td></td></tr><tr><td>IPV6 Support</td><td>Disable / Enable</td><td>Enable or Disable LAN IPV6 Support</td></tr><tr><td>Configuration Address source</td><td>StaticDynamicBmcDhcp</td><td>To configure LAN Address source when IPV6 supported</td></tr></table>

# 5.7 Security Menu

This menu contains the Security settings.

![Aptio Setup - AMI\nSecurity Boot Save & Exit\nIf ONLY the User's password is set, then this\nis a power on password and must be entered to\nboot or enter Setup. In Setup the User will\nhave Administrator rights.\nThe password length must be\nin the following range:\nMinimum length 3\nMaximum length 20\nAdministrator Password\nUser Password\nSecure Boot\nSecure Boot\nconfiguration\n+: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/cc2f1a28cee8f51c623f5e181050e993b7b6a73d88ce51fbe7b03e9acc90c8be.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Administrator Password</td><td>Enter to set password</td><td>Configure/Clear Administrator Password.When pressing enter, a menu will be popped up for creating new password. When password installed, press enter without inputting password, it will clear password.</td></tr><tr><td>User Password</td><td>Enter to set password</td><td>Configure/Clear User Password.When pressing enter, a menu will be popped up for creating new password. When password installed, press enter without inputting password, it will clear password.</td></tr><tr><td>Secure Boot</td><td>Sub-Menu</td><td>Secure Boot Menu. Default is Disabled.</td></tr></table>

# 5.8 Boot Menu

This menu contains the settings for bootable devices in the system.

![Aptio Setup - AMI\nSecurity Boot Save & Exit\nBoot Configuration\nSetup Prompt Timeout 3\nBootup NumLock State (On)\nQuiet Boot (Enabled)\nBoot Configuration\nBoot Option #1 (Hard Disk:Windows\nBoot Manager (P0:\nTS64GMTS400))\nBoot Option #2 (NVME:ubuntu\n(TS256GMTE452T))\nBoot Option #3 (UEFI AP:UEFI:\nBuilt-in EFI Shell)\nBoot Option #4 (CD/DVD)\nBoot Option #5 (SD)\nBoot Option #6 (USB Hard Disk)\nNumber of seconds to\nwait for setup\nactivation key.\n65535(0xFFFF) means\nindefinite waiting.\n+: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/11f7f751d02c5ad7bd60e1063de330b46a250113177481ca722aeefbc96ed294.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Setup Prompt Timeout</td><td>3</td><td>Number of seconds to wait for setup activation</td></tr><tr><td>Bootup NumLock State</td><td>OnOff</td><td></td></tr><tr><td>Quiet Boot</td><td>EnabledDisabled</td><td></td></tr><tr><td>Boot Option #1 ~ #9</td><td>#1: Hard Disk#2: CD/DVD#3: SD#4: USB Hard Disk#5: USB CD/DVD#6: USB Key#7: USB Floppy#8: USB LAN#9: Network</td><td>For boot priority setting.</td></tr><tr><td>XXXX Drive BBS Priorities</td><td>Sub-Menu</td><td>When the bootable device is attached to system and found by BIOS, it will be listed at boot option#. If there are many devices with the same device type found, it can set priority among these devices through this sub-menu.</td></tr></table>

# 5.9 Save & Exit Menu

![Aptio Setup - AMI\nSecurity Boot Save & Exit\nSave Options\nSave Changes and Exit\nDiscard Changes and Exit\nSave Changes and Reset\nDiscard Changes and Reset\nSave Changes\nDiscard Changes\nDefault Options\nRestore Defaults\nSave as User Defaults\nRestore User Defaults\nBoot Override\nWindows Boot Manager (P0: TS64GMTS400)\nubuntu (TS256GMTE452T)\nExit system setup after\nsaving the changes.\n++: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1282 Copyright (C) 2022 AMI\nAB](.axe-7220sr-50m-22810-1000-10/56e6be4ca9324347f560d2fa3b94fa3b315674dcb63517d09938151b2a1645b7.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Save Changes and Exit</td><td>Enter</td><td>Save changed settings and exit BIOS setup utility.</td></tr><tr><td>Discard Changes and Exit</td><td>Enter</td><td>Skip changed setting and exit BIOS setup utility.</td></tr><tr><td>Save Changes and Reset</td><td>Enter</td><td>Save all changed settings and let system do reset to boot system.</td></tr><tr><td>Discard Changes and Reset</td><td>Enter</td><td>Discard all changed settings and let system do reset to boot system.</td></tr><tr><td>Save Changes</td><td>Enter</td><td>Save all changed settings.</td></tr><tr><td>Discard Changes</td><td>Enter</td><td>Discard changes done so far to any of the setup options.</td></tr><tr><td>Restore Default</td><td>Enter</td><td>Load the default made when BIOS was built.</td></tr><tr><td>Save as User Default</td><td>Enter</td><td>Save all changed done so far as User Defaults.</td></tr><tr><td>Restore User Default</td><td>Enter</td><td>Load the default that user save as user defaults.</td></tr><tr><td>Boot Override</td><td>Info-only</td><td></td></tr></table>

# 6 BMC

This chapter provides detailed information on understanding, configuring, and managing the BMC, intended for system administrators who are involved in using ADLINK MECS edge server.

<table><tr><td>Abbreviation</td><td>Description</td></tr><tr><td>BMC</td><td>Baseboard management controller</td></tr><tr><td>CLI</td><td>Command line interface</td></tr><tr><td>FRU</td><td>Field replaceable unit</td></tr><tr><td>GUI</td><td>Graphical user interface</td></tr><tr><td>IPMI</td><td>Intelligent platform management interface</td></tr><tr><td>IPU</td><td>Intelligence Processing Unit</td></tr><tr><td>NTP</td><td>Network time protocol</td></tr><tr><td>PSU</td><td>Power supply unit</td></tr><tr><td>SDR</td><td>Sensor data record</td></tr><tr><td>SEL</td><td>System event log</td></tr><tr><td>SNMP</td><td>Simple network management protocol</td></tr><tr><td>SoL</td><td>Serial over LAN</td></tr><tr><td>PLDM</td><td>Platform Level Data Model</td></tr><tr><td>MCTP</td><td>Management Component Transport Protocol</td></tr></table>

# 6.1 BMC Introduction

# 6.1.1 Software Interface

BMC (Baseboard Management Controller) is equipped with a multitude of interfaces, each designed to cater to different aspects of server management and monitoring. These interfaces provide comprehensive control and insight, ensuring administrators can effectively oversee server operations.

# 6.1.1.1 Web GUI

The product supports Web GUI access through HTTPS (port 443), with HTTP disabled by default for enhanced security. The Web GUI offers a management interface, enabling users to view system information, system events, and status, as well as to control the managed servers.

# 6.1.1.2 IPMI Interface

The IPMI (Intelligent Platform Management Interface) is a standardized interface used for remote monitoring and management of server systems. It provides a powerful set of tools for system administrators to control and monitor servers independently of the operating system.

# Features of IPMI

Remote Management: IPMI allows for remote management of servers, including power control, rebooting, and accessing BIOS configurations.

Health Monitoring: It enables monitoring of physical attributes such as temperature, fan speeds, and power supply status.

Event Logging: Critical system events and hardware status changes are logged, facilitating efficient troubleshooting.

Security: IPMI supports secure interfaces and protocols for safe remote management.

# 6.1.1.3 Redfish

Redfish is a modern, RESTful API used for the management of servers, storage, and networking equipment in data centers and large-scale enterprise environments. It's designed to replace older, less efficient management interfaces with a standardized, scalable, and secure approach.

# 6.2 Web GUI Introduction

The Web GUI of BMC is a critical component that offers an intuitive and user-friendly platform for managing and monitoring server operations remotely. This web-based interface ensures administrators can efficiently interact with the server’s BMC from anywhere.

# 6.2.1 Web Login

Web login to the BMC interface is a straightforward process designed to provide secure and easy access to server management tools.

# 6.2.1.1 Environment Setup

Before logging into the BMC's Web GUI, certain environmental prerequisites must be met:

 Network Configuration
Ensure the server and the device used for access are on the same network or have a route to connect.
 Browser Requirements:
Verify that the web browser used is compatible with the BMC's Web GUI. Commonly supported browsers include Chrome, Firefox, Safari, and Edge.
 BMC IP Address
Since the BMC is configured to use a dynamic IP address, you will need to retrieve the current IP address from the server’s BIOS interface.
Navigate to the "Server Mgmt" tab and select the "BMC network configuration" option.

![Aptio Setup - AMI\nServer Mgmt\n--BMC network configuration--\n******************\nConfigure IPv4 support\n******************\nLan channel 1\nConfiguration Address (Unspecified)\nCurrent Configuration DynamicAddressBmcDhcp\nStation IP address 0.0.0.0\nSubnet mask 0.0.0.0\nStation MAC address 00-30-64-66-77-88\nRouter IP address 0.0.0.0\nRouter MAC address 00-00-00-00-00-00\nLan channel 2\nConfiguration Address (Unspecified)\nCurrent Configuration DynamicAddressBmcDhcp\nStation IP address 172.20.2.12\nSelect to configure LAN\nchannel parameters\nstatically or\ndynamically(by BIOS or\nBMC). Unspecified\noption will not modify\nany BMC network\nparameters during BIOS\n+: Select Screen\n↑↓: Select Item\nEnter: Select\n+/-: Change Opt.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1289 Copyright (C) 2024 AMI\nAB](.axe-7220sr-50m-22810-1000-10/3500ea34d7bf796642a2d0744d8eff65f45d86537818e5fb2cc05a5d075793ef.jpg)

 Security Considerations

For security reasons, access to the BMC Web GUI is exclusively through HTTPS.

# 6.2.1.2 User Sign-In

 Accessing the Login Page

Open your web browser and type in the BMC's IP address, obtained from the BIOS, preceded by "https://". For example, https://[BMC-IP-Address].

This action will direct you to the BMC Web GUI login page.

![MEGARAC\nMECS-7120\nUsername\nPassword\nUS - English\nRemember Username\nSign me in\nI forgot my password](.axe-7220sr-50m-22810-1000-10/bdb630e244369bcd5dbcd010ec9c444391d71bc861b0ff5e6e0900fb7a63bb2a.jpg)

 Selecting Language

Below the login fields, there is an option to select your preferred language.

The BMC Web GUI supports multiple languages, including Simplified Chinese, Traditional Chinese, and English.

Choose your desired language from the dropdown menu before logging in.

 Entering Login Credentials

On the login page, you will be prompted to enter your username and password.

The default username: admin

The default password: admin.123

After entering these credentials, click the "Sign me in" button to proceed.

 Other fields

Remember Username: Check this option to remember your login Username. If you select this option, the browser will save your credentials internally in its memory, and when you open that site the next time, it will auto-fill Username for you.

I Forgot my Password: If you forget your password, you can generate a new password using this link.

# 6.2.2 Web Interface Overview

This section provides an overview of the BMC's Web Interface, emphasizing the functionalities and information displayed on the main interface. The primary purpose of the main interface is to offer a quick and comprehensive understanding of the current status of the BMC.

![MECS-7120\nVersion Information\nBMC: 1.4.dd360de7\nBIOS: 1.2.10\nCPLD: 02b4\nHW: A2 SKU: 1U\nMar 15 2024 05:58:02 UTC\nHost Online\nQuick Links..\nDashboard\nSensor\nSystem Inventory\nFRU Information\nLogs & Reports\nOne-click log collection\nSettings\nRemote Control\nImage Redirection\nPower Control\nMaintenance\nSign out\nDashboard Control Panel\nHome ) Dashboard\n0 d 0 hrs\nPower-On Hours\n1\nAccess Logs\nMore info](.axe-7220sr-50m-22810-1000-10/9784cc764cc04f80d1fce4066de429d072d76d71a7e10553479fc3adc3002c5f.jpg)

The BMC Web GUI is primarily divided into three sections, each offering specific functionalities and information crucial for server management.

# 1. Top Menu Bar

Functionality: The top menu bar is designed for receiving and viewing server messages, setting BMC global configurations, and accessing the BIOS configuration interface. This area serves as a quick access point for important notifications and system adjustments.

<table><tr><td>Function</td><td>Icon</td><td>Detailed Description</td></tr><tr><td>Message</td><td>&lt;img src="images/fa2856e6f4825d2b65ebcf3d8464e1182b29985dd5933e8fda59fc9a299a6c19.jpg"/&gt;</td><td>Display the messages received.</td></tr><tr><td>Notification</td><td>&lt;img src="images/25c2fb2aaadad4b9ddc4d73885f9beccf9ca287b7609f33d1447032dfb79e049.jpg"/&gt;</td><td>Display the notifications received.</td></tr><tr><td>Language</td><td>&lt;img src="images/909301a3fbab8a2e871184d7a9285b81f361dd3c193ace1d461256aee4b766b8.jpg"/&gt;</td><td>Set Board Language.</td></tr><tr><td>Bios interface</td><td>&lt;img src="images/4fdbe1975e0b87c50bed487c8b4f7014db2b70b8cdf9c268179c5ad761acec09.jpg"/&gt;</td><td>Open the new window or popup to configure the BIOS settings.</td></tr><tr><td>Dashboard Expansion</td><td>&lt;img src="images/3a7bc27b8a1e16bf6390da8bbd079a118be202f4b69046f153205fe37a274220.jpg"/&gt;</td><td>Show/Hide limited Dashboard Widgets.</td></tr><tr><td>2FA</td><td>&lt;img src="images/31ab50439acf825cee9053d1b24791127c90548e839302c1857f0decf0bbd803.jpg"/&gt;</td><td>Enable/Disable Two Factor Authentication.</td></tr><tr><td>Synchronization</td><td>&lt;img src="images/ebeb7c2081aacb130027c2f2e38a24627f447a80c0ad6eddfbdd854908c1f92a.jpg"/&gt;</td><td>On/Off to synchronize with latest Sensor and Event Log updates.</td></tr><tr><td>Refresh</td><td>&lt;img src="images/13ac21967ced374de2cbcbc76d61ae0334efcf4c9020dc987e7a7844792b5151.jpg"/&gt;</td><td>Reload the current page.</td></tr><tr><td>Profile</td><td>[CGSA] admin ▼</td><td>Set the User Profile.</td></tr></table>

# 2. Server Version Information

This section of the interface displays the current version information of various server components, listed in the following order:

<table><tr><td>Version Information</td></tr><tr><td>BMC: 1.4.dd360de7</td></tr><tr><td>BIOS: 1.2.10</td></tr><tr><td>CPLD: 02b4</td></tr><tr><td>HW: A2 SKU: 1U</td></tr><tr><td>Mar 15 2024 05:58:02 UTC</td></tr></table>

BMC Version Information
BIOS Version Information
CPLD Version Information
. Hardware Version Information
SKU Version Information
. BMC Image Build Date and Time

The version information window provides a quick overview of the server's hardware and firmware status, ensuring that administrators are immediately aware of the current versions and operational status.

# 3. Function Menu bar

The menu bar displays the following.

Version Information will be displayed with the latest version, date and time details. Power Control Status will be displayed as Host Online. To Change the Power Control Status, click Host Online link.

 Dashboard
 Sensor
 System Inventory
 FRU Information
 Logs & Reports
 One-click log collection

 Remote Control
 Image Redirection
 Power Control
 Maintenance
 Sign out

# 6.2.3 Server Information

# 6.2.3.1 FRU Information

<table><tr><td colspan="4">Available FRU Devices</td></tr><tr><td>FRU Device ID</td><td>0✓</td><td></td><td></td></tr><tr><td>FRU Device Name</td><td>BMC_FRU</td><td></td><td></td></tr><tr><td colspan="4">Chassis Information Board Information Product Information</td></tr><tr><td>Chassis Information Area Format Version</td><td colspan="3">1 Board Information Area Format Version 1</td></tr><tr><td>Chassis Type</td><td colspan="3">Unspecified Language English</td></tr><tr><td>Chassis Part Number</td><td colspan="3">91-XXXX-XXX Manufacture Date Time Fri Nov 17 19:33:00 2023</td></tr><tr><td>Chassis Serial Number</td><td colspan="3">0000000000000000000 Board Manufacturer ADLINK Technology</td></tr><tr><td rowspan="22" colspan="4">Chassis Extra Board Product Name MECS-7120 Product Part Number 91-XXXX-XXX</td></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr><td></td></tr></table>

The FRU (Field Replaceable Unit) Information interface in the BMC Web GUI is accessed by clicking on the "FRU Information" option in the left-hand function bar. This feature allows users to view electronic label information for the motherboard and other components, providing detailed FRU data.

Structure and Functionality of the FRU Information Interface. The FRU information is divided into four main sections, each offering specific insights:

<table><tr><td>Information Category</td><td>Description</td></tr><tr><td>Available FRU Devices</td><td>Details about each FRU device:FRU Device IDFRU Device Name</td></tr><tr><td>Chassis Information</td><td>Information related to the server's chassis, featuring:Chassis Information Area Format VersionChassis TypeChassis Part NumberChassis Serial NumberChassis Extra</td></tr><tr><td>Board Information</td><td>Data about the server's mainboard, encompassing:Board Information Area Format VersionLanguageManufacture Date TimeBoard ManufacturerBoard Product NameBoard Serial NumberBoard Part NumberFRU File IDBoard Extra</td></tr><tr><td>Product Information</td><td>Comprehensive details about the product, including:Product Information Area Format VersionLanguageProduct ManufacturerProduct NameProduct Part NumberProduct VersionProduct Serial NumberAsset TagFRU File IDProduct Extra</td></tr></table>

# 6.2.3.2 Sensor Information

The Sensor Information panel in the BMC Web GUI provides a detailed overview of the current status and readings from various sensors within the server. Accessing and understanding this data is essential for maintaining the server's health and performance.

Accessing the Sensor Information Panel
Navigating to the Panel
Click on the "Sensor" button located on the left side of the BMC Web GUI

# 6.2.3.2.1 Introduction to sensor interface

This will lead you to the Sensor Information interface, which is central for real-time sensor status monitoring.

# Sensor Information Interface Layout

The Sensor Information interface is divided into four distinct sections, each providing specific types of sensor data:

# 1. Critical Sensors

![Sensor Reading Live reading of all sensors\nCritical Sensors (0)\n#All threshold sensors are normal](.axe-7220sr-50m-22810-1000-10/15221e5b9a8f2c0a6d96886c0afbb063930779fda723362c560e2c4f47ee30d0.jpg)

This section displays the status of critical sensors, highlighting if any sensor has exceeded its threshold or is showing abnormal readings.

It's a focal point for quickly identifying potential issues that require immediate attention.

# 2. Discrete Sensor States

<table><tr><td>Sensor Name</td><td>State</td></tr><tr><td>ACPI_Power</td><td>S0/G0 &#x27;Working</td></tr><tr><td>FAN1_Presence</td><td>Device Inserted / Device Present</td></tr><tr><td>FAN2_Presence</td><td>Device Inserted / Device Present</td></tr><tr><td>FAN3_Presence</td><td>Device Inserted / Device Present</td></tr><tr><td>FAN4_Presence</td><td>Device Inserted / Device Present</td></tr><tr><td>FAN5_Presence</td><td>Device Inserted / Device Present</td></tr><tr><td>HDD1_Status</td><td>Drive Presence</td></tr><tr><td>HDD2_Status</td><td>Drive Absence</td></tr><tr><td>PSU1_Presence</td><td>Device Inserted / Device Present</td></tr><tr><td>PSU1_Status</td><td>Presence Detected, Power Supply Failure Detected, Power Supply Input Lost (AC/DC)</td></tr><tr><td>PSU2_Presence</td><td>Device Inserted / Device Present</td></tr><tr><td>PSU2_Status</td><td>Presence Detected</td></tr></table>

Shows the status of discrete sensors, particularly focusing on those that are offline. This part is crucial for identifying sensors that are not functioning or are disconnected.

# 3. Normal Sensors

Normal Sensors (46)

<table><tr><td>Sensor Name</td><td>Reading</td><td>Behavior</td></tr><tr><td>↓ CPU_Outlet_Temp</td><td>28 °C</td><td></td></tr><tr><td>○ CPU_Power</td><td>34 Watts</td><td></td></tr><tr><td>↓ CPU_TJMAX</td><td>99 °C</td><td></td></tr><tr><td>↓ CPU_Temp</td><td>31 °C</td><td></td></tr><tr><td>↓ DIMM_A1_Temp</td><td>23 °C</td><td></td></tr><tr><td>♣ FAN1_Speed_Inner</td><td>7050 Rpm</td><td></td></tr><tr><td>♣ FAN1_Speed_Outter</td><td>6000 Rpm</td><td></td></tr><tr><td>♣ FAN2_Speed_Inner</td><td>7050 Rpm</td><td></td></tr><tr><td>♣ FAN2_Speed_Outter</td><td>6000 Rpm</td><td></td></tr><tr><td>♣ FAN3_Speed_Inner</td><td>7050 Rpm</td><td></td></tr><tr><td>♣ FAN3_Speed_Outter</td><td>6000 Rpm</td><td></td></tr><tr><td>♣ FAN4_Speed</td><td>6750 Rpm</td><td></td></tr></table>

Displays the actual readings from various sensors.

These readings include data such as temperature, fan speeds, voltage levels, and more. The section provides a comprehensive view of the real-time operating conditions of the server.

# 4. Disabled Sensors

XDIMM\_B1\_Temp

XDIMM\_H1\_Temp

XTBF100\_Up\_Temp

XPSU2\_PIN

XDIMM\_C1\_Temp

xPSU2\_Inlet\_Temp

XTBF100\_Down\_Temp

XPSU2\_Status

XDIMM\_E1\_Temp

XPSU2\_Sec\_Temp

XPSU2\_VOUT

XTBF100\_Up\_PWR

XDIMM\_G1\_Temp

XPSU2\_Prm\_Temp

XPSU2\_POUT

XTBF100\_DoWn\_PWR

Lists sensors that are currently not in operation or are disabled.

This section helps in identifying which sensors are not contributing to the monitoring process and may need reactivation or maintenance.

# 6.2.3.2.2 Detailed Sensor Information

Accessing and Viewing Sensor Details. To view detailed information about a specific sensor, simply click on the desired sensor listed in the Sensor Information panel. This action will lead you to a dedicated detail page for that sensor.

On this detailed page, extensive information about the selected sensor is displayed, including its current operational status, various parameters, and any unique specifications.

Sensor State Reading- Ox8001

January2024

![The image displays a partial view of a blue, circular object, resembling the top portion of a balloon, suspended by a thin black line from above. Inside the blue area, there is a ring of small, white, circular dots arranged around a central point. There is no visible text in the image.](.axe-7220sr-50m-22810-1000-10/c5cc73cc3e90c2129622257d64395d637a6d5a41a2e80fed4a8c400745518f77.jpg)

![The image displays a blue circular icon. Inside the lower half of the blue circle is a white semi-circle. Within this white area, small blue dots are arranged to resemble a face, featuring two 'eyes' and a curved line of dots for a smile. A thin white line extends vertically from the top center of the blue circle.](.axe-7220sr-50m-22810-1000-10/d1cc0713b7053e13df64d0dec3bb5a0f59ccb571fc588459bc623aa41ddea987.jpg)

![The image displays a blue circular icon with a thin vertical line extending upwards from its top center. Inside the lower portion of the blue circle is a white semi-circle. Within this white area is a black schematic pattern of dots connected by thin lines, resembling a network or circuit.](.axe-7220sr-50m-22810-1000-10/4b08db7dc32034d681fe1c3a1f4fb4f1b14e6e570356401666b27b379d77775e.jpg)

![The image displays a solid blue circle. Inside the circle is a white shape that resembles a scalloped semi-circle or a cloud, positioned towards the bottom center. Inside this white shape are several small, dark dots arranged in a scattered pattern. There is no text in the image.](.axe-7220sr-50m-22810-1000-10/3baf3d8d626cdb52ea43c583f1ca20c15a41639e82b22e6d3b0957f9cb2876bb.jpg)

![The image contains a graphic of a blue circle. Inside the circle is a white, arched shape resembling a dome. Within this white area, a series of small black dots are arranged in a semi-circle arc, mimicking the numbers on a clock face. There is no text in the image.](.axe-7220sr-50m-22810-1000-10/a829e917ec521e984a5813e8c456ae330cc1b196e831beb32b090f4ceb1b5751.jpg)

![The image shows a blue circular icon. Inside the blue circle, there is a white semi-circle shape at the bottom. Within this white area, there are several small black dots arranged in an arc pattern.](.axe-7220sr-50m-22810-1000-10/99dba694666a7f092697ef2b9d10d958b4c303a1b1bc44a6095a70cea77701be.jpg)

Customizing Sensor Thresholds:

For general sensors, the detailed interface provides the capability to adjust various sensor threshold parameters. Administrators have the flexibility to modify several threshold levels including:

Upper Non-Recoverable

Upper Critical

Upper Non-Critical

Lower Non-Critical

Lower Critical

Lower Non-Recoverable

# Practical Application:

Adjusting these thresholds is vital for preemptive alerts and ensuring that sensors are operating within safe and optimal ranges.

![The image displays a narrow vertical section centered on a light green circle containing a white question mark (?). Flanking the circle are vertical strips: a dark, blurry area to the left and a white area to the right. The top and bottom portions are out-of-focus white space.](.axe-7220sr-50m-22810-1000-10/365c800ed31b551ae6ddc4f103d8eb6789044d32ba7c3787e6eb7368f8581805.jpg)

贝POV8\_E810 Sensor Information
![| Time (HH:MM:SS) | Volts |\n| --------------- | ----- |\n| 14:51:20        | 0.83  |\n| 14:51:41        | 0.79  |\n| 14:52:45        | 0.82  |\n| 14:53:06        | 0.79  |\n| 14:53:26        | 0.82  |\n| 14:53:47        | 0.79  |\n| 14:00:00        | 0.83  |](.axe-7220sr-50m-22810-1000-10/e3296efee6163d477a10308446c9a87b5127d2f887799c7b119bf5232e2265ac.jpg)

0.81Volts

<table><tr><td>Upper Non-Recoverable</td><td>0.88 Volts</td></tr><tr><td>Upper Critical</td><td>NA</td></tr><tr><td>Upper Non-Critical</td><td>NA</td></tr><tr><td>Lower Non-Critical</td><td>0.76 Volts</td></tr><tr><td>Lower Critical</td><td>0.74 Volts</td></tr><tr><td>Lower Non-Recoverable</td><td>0.72 Volts</td></tr></table>

Change Thresholds

If the synchronization button in the top menu bar is active, accessing the detail interface for a general sensor will enable a graphing feature. This feature provides a line graph depicting the sensor’s data over time. It serves as a visual tool for quickly assessing the sensor’s performance.

# 6.2.3.2.3 Modifying Sensor Thresholds

Accessing Sensor Thresholds Modification Interface. In the Sensor Details interface, locate and click on the "Change Thresholds" button. This action will redirect you to the Sensor Thresholds interface.

# Sensor Thresholds

# Change Threshold Values

![The image displays a blurry, light green circle containing a white question mark in the center, set against a white background.](.axe-7220sr-50m-22810-1000-10/2f3b4ce25dcb785fec0b78fdffcdfc53605839499291e5bd50ee85c014970b97.jpg)

#

# Sensor Name

Upper Non-recoverable

13.20

Upper Critical

12.84

Upper Non-critical

12.60

Lower Non-critical

11.40

Lower Critical

11.16

Lower Non-recoverable

10.80

Retain Threshold Values

Save

# Sensor Thresholds Interface:

The Sensor Thresholds interface displays each sensor's name along with its threshold values.
Users can view and modify thresholds for each sensor, including upper and lower warning and critical limits.
Thresholds not applicable or unavailable for a sensor are marked as "NA".

# Retaining Threshold Values

At the bottom of the interface, a "Retain Threshold Values" checkbox is provided.

Note: If this option is not selected, threshold adjustments will be temporary, reverting to default upon BMC reboot or power loss.

# 6.2.4 Server Information

BMC provides various logging functions that are crucial for system diagnosis, monitoring, and security. Logs are divided into different types, each with a specific purpose.

# Accessing BMC Logs

To view these logs, navigate to the BMC web interface:

From the left-side functional panel, click on "Logs & Reports".
A dropdown menu will appear, listing the following types of logs available for viewing:

![Logs & Reports\n» IPMI Event Log\n» System Log\n» Audit Log\n» Video Log\n» SOL Video Log](.axe-7220sr-50m-22810-1000-10/03e2ba4d757a96fcf7ab696c066b588f2ffb3f20ea83aece34d4edad607651f1.jpg)

 IPMI Event Log
 System Log
 Audit Log
 Video Log
 SOL Video Log

# 6.2.4.1 IPMI Event Log

This page displays the list of event logs occurred by the different sensors on this device. Double click on a record to see the details of that entry. You can use the sensor type or sensor name filter options to view those specific events or you can also sort the list of entries by clicking on any of the column headers.

To open the Event Log page, click Logs & Reports -> Event Log from the menu bar. A sample screenshot of Event Log page is shown below.

![| Year | Event Log Count |\n| :--- | :--- |\n| January 2000 | 1 |\n| January 2022 | 3 |\n| January 2024 | 2 |](.axe-7220sr-50m-22810-1000-10/88d082c9e9213462951b7ebd51d3ebe5034b4555315c1e1028c71fd817ac278b.jpg)

The Event Log page consists of the following Fields.

Filter By Date: Filtering can be done by selecting Start Date and End Date using Calendar.

Note: Date should be in MM/DD/YYYY format.

By default, all log time will be displayed in BMC time zone.

Filter By Type: The category could be either All Events, System Event Records, OEM Event Records, BIOS Generated Events, SMI Handler Events, System Management Software Events, System Software - OEM Events, Remote Console Software Events, Terminal Mode Remote Console software Events.

Note: Once the Filter By Date and Filter type are selected, the list of events will be displayed with the Event ID, Time Stamp, Sensor Type, Sensor Name and Description.

UTC Offset: Displays the current UTC Offset value based on which event Time Stamps will be updated. Navigational arrows can be used to selectively access different pages of the Event Log.

Event Log Statistics: Displays the statistical graph for the selected date.

Clear Event Logs: To delete all the event logs.

Download Event Logs: To download the event logs.

# Procedure

1. From the Filter ByDate field, select the time period by Start Date and End Date using Calendar for the event categories. The events will be displayed according to the selected date.
2. From the Filter By Type field, select the Type of the event and Sensor name to view the events for the date. The events will be displayed based on the selected time period.
3. To clear all events from the list, click Clear All Event Logs.
4. To download the event logs, click Download Event Logs.

Note: When Clear All Event Logs action is performed, there might be some events present even after clearing those events are generated after performing clear operation which can be verified using its timestamp.

# 6.2.4.2 System Log

System Log page will display all the system events occurred in this device that has been already configured.

Note: Logs have to be configured under Settings -> Log Settings in order to display any entries.

To open the Event Log page, click Logs & Reports -> System Log from the menu bar.

![System Log All system event logs\nFilter by Date Start Date End Date Event Category Alert\nSystem Log: 1 out of 1 event entries\nJanuary 2024\nID: 1 January 22nd 2024, 6:40:12 pm AMI003064F3092B kernel: kernel - - ( 7.330370) Copyright (c) 2009-2015 American Megatrends Inc. -](.axe-7220sr-50m-22810-1000-10/c383d23cd95935b55fbbac15526d520ae974dad391fb0ef3243a2c0cd82473d2.jpg)

# Procedure

To view System Log, click the System Log tab to view all system events. Entries can be filtered based on Filter By Date (Start Date and End Date) and Event Category like Alert, Critical, Error, Notification, Warning, Debug, Emergency and Information.

# 6.2.4.3 Audit Log

Audit Log page will display all the system events occurred in this device that has been already configured.

Note: Logs have to be configured under Settings -> Log Settings -> Advanced Log Settings in order to display any entries.

To open the Event Log page, click Logs & Reports -> Audit Log from the menu bar.

![Audit Log All audit logs\nFilter by Date Start Date End Date\nJanuary 2024\nID: 4 January 23rd 2024, 10:03:13 am AMI003064F3092B spx_restservice: spx_restservice - - (2094 : 2094 INFO)https Login from IP:172.20.2.72 user:admin -\nID: 3 January 22nd 2024, 7:13:34 pm AMI003064F3092B spx_restservice: spx_restservice - - (2094 : 2094 INFO)HTTPS logout from IP:172.20.2.54 user:admin -\nID: 2 January 22nd 2024, 6:40:35 pm AMI003064F3092B login(2273): login 2273 - (2273 : 2273 INFO)SERIAL Login from IP:127.0.0.1 user:sysadmin -\nID: 1 January 22nd 2024, 6:40:25 pm AMI003064F3092B spx_restservice: spx_restservice - - (2094 : 2094 INFO)https Login from IP:172.20.2.54 user:admin -](.axe-7220sr-50m-22810-1000-10/28024ea807bfbc7feb70e559db76fdaf00acc176748558a9e100a9772fddcc66.jpg)

# 6.2.4.4 Video Log

The video log page will record the configured system events in the device in a video format that has been already configured.

Note: Video Trigger Settings should be enabled, to display the Video Log page. Video Trigger Settings can be configured under Settings -> Video Recording -> Auto Video Settings -> Video Trigger Settings.

To open the Video Log page, click Logs & Reports -> Video Log from the menu bar. A sample screenshot of Video Log page is shown below

![Video Log All video event logs\nFilter by Date Start Date End Date\nVideo Log: 1 out of 1 event entries\nJanuary 2024\nvideo_dump_2024y-01m-23d_10h-55m-26s.dat Post Event Recorded on Tuesday, January 23rd 2024, 10:55:45 am\nID: 1 7 minutes ago](.axe-7220sr-50m-22810-1000-10/69c2e6796aacbeef054b5a80dbf8de88bf357a974f6238938a4b982e5c023aff.jpg)

After clicking on the video event, the video conversation box will pop up. Play the current video. In this interface, you can choose to download or delete the current video log.

![Video Log\nFilter by:\nJanuary 2\nDuration 8000\nID: 1 an hour ago\nUS - English\n2FA\nSync\nRefresh\nadmin\nHome ) Video Log](.axe-7220sr-50m-22810-1000-10/763b6d6ff9824aa3e233b7dfdbf8cce17c53ac21871d456337c7a9b0f6dfc7f4.jpg)

Note: Video will be allowed to play/download only if file size is lesser than 40MB. Browsers have various memory restrictions, due to this browser cannot store and process data greater than 40MB (approximately). If file size is greater than 40MB, user will be notified with a message to use Java player Application.

The video data may not be proper if the browser zoom in/out settings are changed during video playback.

To download a video, you need to wait for the video buffering to complete before downloading.

# 6.2.4.5 SOL Video Log

The sol log page will record configured system events through sol.

Note: SOL Trigger Settings should be enabled, to display the SOL Log page. SOL Trigger Settings can be configured under Settings -> Video Recording -> SOL Settings -> SOL Trigger Settings.

SOL Configurations can set the baud rate of the serial port.

To open the Video Log page, click Logs & Reports -> SOL Log from the menu bar. A sample screenshot of SOL Log page is shown below.

![SOL Video log All SOL Video log\nS.No File Name File Information\n1 SOLHostCapture_Archive_1_01232024_13_26_08.log Tuesday, January 23rd 2024, 1:26:08 pm](.axe-7220sr-50m-22810-1000-10/21d78800cbff8365d89437a0b4609e6c23a826d311bccc63ec1652c3925262fd.jpg)

S.No - The serial number

File Name - The video filename

File Information - Day, date and time of video upload

Download - To download the selected video

Delete - To delete the selected video.

Note: The timestamp displayed in the file information represents last modified time, and it will be updated (if the file is modified) when the webpage is refreshed.

# 6.2.5 Power Control

It is used to control power on the WEB. A sample screenshot of service management is shown as below.

![Power Control on Host Server\nPower Actions\nHost is currently on\nPower Off\nPower On\nPower Cycle\nHard Reset\nACPI Shutdown](.axe-7220sr-50m-22810-1000-10/37f428de1c0007b134ddf47707923427ecc860dedaea787b48baa8425472ceea.jpg)

The power control consists of the following items.

 Power off: Power on the chassis.
 Power on: Power off the chassis.
 Power Cycle: Power off the chassis and power on the chassis.
 Hard Reset: Restart the chassis.
 ACPI Shutdown: Soft power off the chassis.

# 6.2.6 BMC Settings

The BMC Settings section in the BMC web interface is a centralized location for accessing and modifying a wide range of configuration settings for the BMC.

1. In the BMC web interface, click on the "Settings" button located in the functional menu on the left side.
2. This action will open a group menu that displays various configurable options and settings.

![The image displays a dark gray icon of a camera on a white background. It features a rounded rectangular body with two small rectangular shapes at the top center. In the middle of the body is a large circle representing a lens, which contains a smaller, white concentric circle.](.axe-7220sr-50m-22810-1000-10/1931816ca91276af147932bacbf40804908eb65c3ad92cb69980d5f66277a0b3.jpg)

![The image displays a dark grey circular icon containing a white graphic that resembles the hands of a clock. The graphic consists of two white lines meeting at a right angle: one line points vertically upward and the other points horizontally to the right, indicating a time of roughly 3:00.](.axe-7220sr-50m-22810-1000-10/f37334afa5134b20818b928068872748982c34db8416c13ab902205253989c85.jpg)

![The image displays a stylized, flat-icon graphic of a book. The book is depicted in dark grey or black and is angled slightly towards the right. On the front cover, there are white horizontal lines: two thick bars near the top and a thinner line below them. A darker vertical section on the left side represents the spine. Beneath the main black shape is a white shape outlined in black, representing the bottom edge or pages of the book. The background is white.](.axe-7220sr-50m-22810-1000-10/36914a358fae74e9d41094abb51f0b424c0f8668ac363cc1f1f988c1a36cb648.jpg)

![The image displays a black icon resembling a computer mouse against a white background. It is a vertical shape with a rounded top and a straight bottom. A vertical line runs down the center of the upper portion, dividing it into two sections that resemble the left and right buttons of a mouse, while the lower portion is a solid black block.](.axe-7220sr-50m-22810-1000-10/5a92dfa8190616cf740b472791eaad8adaa27237f95678f164e688842ea3be00.jpg)

![The image shows a white document icon with a folded top-right corner set against a black background. Inside the white shape, there are horizontal black lines of varying lengths representing text.](.axe-7220sr-50m-22810-1000-10/8254cd83fa3e7713d48b37972e198f63a555a4192f494dc77fb7e343475b69cb.jpg)

![A black line drawing of a toaster.](.axe-7220sr-50m-22810-1000-10/7175b9e80660646aacf9bf3540be7564373ae3a7f70eeb37c90bd86d722ec0e8.jpg)

![This is a low-resolution, black and white icon representing a hierarchy or organizational chart. It features a single square block at the top center connected by lines to three square blocks arranged in a horizontal row directly below it. The structure illustrates a top-down relationship, with one superior node overseeing three subordinate nodes.](.axe-7220sr-50m-22810-1000-10/dd3f339315df463fb2ac778efa321de2805cd328d316faad22c7bbee79b123dc.jpg)

![The image displays a black icon consisting of a downward-pointing arrow on the left and a vertical stack of horizontal black bars of varying lengths on the right, resembling lines of text.](.axe-7220sr-50m-22810-1000-10/6daa65a9f0e41e4f48950b84e107935d65d99ca5779611baba4142288ab4f284.jpg)

![The image displays a black graphic on a white background. At the very top is a thin, horizontal black line. Below this line is a black shape resembling a capital letter 'T' or a funnel. It features a wide, horizontal top bar and a narrower vertical stem descending from the center. The bottom edge of the stem is slanted diagonally upwards from left to right.](.axe-7220sr-50m-22810-1000-10/65038ba981a0a359e615d180d8247d3493ab76e8c92f29c716a390943671d5a3.jpg)

![The image displays a small, pixelated icon featuring three dark grey gears against a white background. A large gear is situated on the left, meshed with two smaller gears stacked vertically on the right side. There is no text in the image.](.axe-7220sr-50m-22810-1000-10/98f755513236e15e0bb1dc92dec3cb774e4083f45081e850132f94a3529e8e2c.jpg)

![The image displays a black rectangular shape containing a white 'X' symbol in the center. The 'X' is formed by two intersecting diagonal lines of uniform thickness. A vertical white line runs down the center of the image, and a small sliver of a black shape is visible on the far right edge.](.axe-7220sr-50m-22810-1000-10/64351f5fe34b4b3c307b6d9ef63429cbbbd743ae67696016c8098efdb629f0c8.jpg)

![A black, starburst-shaped icon with jagged edges radiating outward is centered on a plain white background.](.axe-7220sr-50m-22810-1000-10/bd6728f7c11eb6468c8223aa2b96fd89306ffd01f12933832daa846d0b8d8bb9.jpg)

![A simple, dark gray icon of a closed padlock featuring a U-shaped shackle and a rectangular body.](.axe-7220sr-50m-22810-1000-10/6a28dddf2e5a6ef6e8e049cb7bc249d74825d72d040121f9079387c7ed5f153e.jpg)

![The image shows a dark silhouette icon of two stylized human figures. A larger figure is in the foreground on the left, with a smaller figure positioned slightly behind it on the right, set against a white background.](.axe-7220sr-50m-22810-1000-10/dbc494ba4428747ab7acdf028ae04e41ea810eb72b226b1f03d73b25d0e8b4ea.jpg)

![The image shows a simple icon on a white background. On the left is a solid dark grey square. To the right of the square are two dark grey triangles pointing to the right. The first triangle is larger than the second. The entire graphic is enclosed within a thin black border.](.axe-7220sr-50m-22810-1000-10/fbb8d9150aada6f47fcf69e8f1f106a9b28e3642221aaa707e9aeba709a37521.jpg)

![The image displays a simple black line drawing on a white background. It features three hollow circles connected by straight lines. Two circles are arranged vertically on the left side and are connected by a vertical line. A third circle is positioned to the right, aligned horizontally with the midpoint of the vertical line. A horizontal line extends from the vertical line to connect to this third circle, forming a T-shaped junction.](.axe-7220sr-50m-22810-1000-10/7e7b704e63bc41db6b285b385409101557b44d787bd73dd22500ee012fb4583e.jpg)

# Features

Comprehensive Configuration: This interface allows you to adjust and set most of the BMC's configurations, tailoring the controller to your specific needs and preferences.

Information Retrieval: Besides configuration, this section also provides access to essential information about the BMC and the server it manages.

# 6.2.6.1 Captured BSOD

This page displays a snapshot of the blue screen captured if the host system crashed since last reboot.

A screenshot of Captured BSOD is shown below.

![Captured BSOD\nLast BSOD Screen Captured\nterminal File Edit View Search Terminal Help\nroot@amiqa:~\nroot@amiqa:-#](.axe-7220sr-50m-22810-1000-10/63f0b5844e65405c4c679112ae82568137d86ef3e9e66ef2f209d25a635fcc55.jpg)

Note: KVM service should be enabled to display the BSOD screen. KVM Service can be configured under Settings -> Services -> KVM.

# 6.2.6.2 Date & Time

This field is used to set the date and time on the BMC. A sample screenshot of Date & Time is shown as below.

# Date&Time

# ConfigureDate&Time

![The image displays a blurry, light green circle featuring a white question mark centered within it.](.axe-7220sr-50m-22810-1000-10/8fa8df566ed9eeac21e654955c223f8128bef3243315542b68e918382df1e1fd.jpg)

![World map with scattered white circular markers indicating locations, no text or labels present](.axe-7220sr-50m-22810-1000-10/78eae50140804e9719d6da3245e8f5efb220eb8f8a52c4386dd1f5099ae6353a.jpg)

Select Time Zone

\_Feb 26,202410:45:52AM(GMT+08:00 CST)-Asia/Shanghai

Automatic NTP Date&Time

√ Automatic PTP Date& Time

PTP Interface

![The image features a white background containing five thin, horizontal black lines that are evenly spaced across the width.](.axe-7220sr-50m-22810-1000-10/81f0e66f5ac968e60b5664309e5b0b0e5b1175d0ae5f63a1e021b8671c2028b7.jpg)

PTP Transport

![Ipv4](.axe-7220sr-50m-22810-1000-10/04188a6f7de89dca2d44f44865da1ed1cb06e4a77b0aa8a64672b5b0172e704b.jpg)

PTP Unicast IP

PTP Inbound Latency

PTP Priority1

![The image displays the digit '0' twice, stacked vertically on the left side. Below the digits is a solid black horizontal line that spans the entire width of the image.](.axe-7220sr-50m-22810-1000-10/6c5df3876e708e7df0a0db872a397bbfb8304ee94985b00f03909d370f6ff387.jpg)

Panic Mode

PTP Preset

PTP Ipmode

Unicast

PTP Delay Mechanism

E2E

PTP Outbound Latency

PTP Max Master capacity

5

PTP Log request delay

![The image features a horizontal sequence of four identical white rectangular icons against a teal background. Each icon contains faint horizontal and vertical lines, resembling a simplified grid or spreadsheet symbol. There is no text in the image.](.axe-7220sr-50m-22810-1000-10/c4398ef71c61ed6a3c0ca97d639fd104251c44a441995a0fbb3fbceb0e745297.jpg)

Save

The Date & Time section consists of the following fields.

Configure Date & Time: Displays Time zone list containing the UTC offset along with the locations and Navigational line to select the location which can be used to display the exact local time.

Select Time Zone: This field is used to set the date and time on the BMC.

Note: Based on the manual selection of GMT or ETC/GMT, time zone alone will be changed and date & time will remain the same.

Automatic NTP Date & Time: To automatically synchronize Date and Time with the NTP Server.

Primary NTP Server: To configure a primary NTP server to use when automatically setting the date and time.

The following address formats & Domain name format are supported:

 IPv4 Address format
 IPv6 Address format
 Domain name format allowed ‘A-Z’, ‘a-z’, ‘0-9’, dash (-), underscore (\_) and dot(.) characters

Secondary NTP Server: To configure a secondary NTP server to use when automatically setting the date and time.

The following address formats & Domain name format are supported

 IPv4 Address format
 IPv6 Address format
 Domain name format allowed ‘A-Z’, ‘a-z’, ‘0-9’, dash (-), underscore (\_) and dot(.) characters

Automatic PTP Date & Time: To enable/disable the use of PTP servers to automatically set the date and time.
PTP Interface: To configure a PTP server interface to use when automatically setting the date and time.
PTP Preset: To configure a PTP Preset type to use when automatically setting the date and time.
PTP Transport: To configure a PTP Transport type to use when automatically setting the date and time.
PTP Ipmode: To configure a PTP Ipmode type to use when automatically setting the date and time.
PTP Unicast IP: To configure a Unicast IP when ipmode is unicast and server to use when automatically setting the date and time.
PTP Delay Mechanism: To configure a PTP Delay Mechanism type to use when automatically setting the date and time.

PTP Inbound Latency: To configure an Inbound latency of the server to use when automatically setting the date and time.
PTP Outbound Latency: To configure a PTP outbound latency server to use when automatically setting the date and time.
PTP Priority1: To configure a priority of PTP clock to use when automatically setting the date and time.
PTP Max Master capacity: To configure a max master capacity of the PTP clock to use when automatically setting the date and time.
Panic Mode: To configure a PTP clock to not reset if jump is more than 1 second, use when automatically setting the date and time.

Save: To save the settings.

Note: If the time zone is selected as Manual Offset, the map selection will be disabled. The Time-Zone settings will be reflected only after saving the settings. If disable the Automatic Date & Time, the time needs to select by users themselves or the time would not change.

# Procedure

1. Select the Timezone location either using drop down or Map.
2. Enable Automatic Date &Time option to enable/disable the use of NTP servers to automatically set the date and time.

a) In the Primary NTP Server and Secondary NTP Server fields, specify the NTP servers of the device respectively.

Note: Secondary NTP server is optional field. If the Primary NTP server is not working fine, then the Secondary NTP Server will be tried.

3. Enable Automatic PTP Date &Time to enable/disable the use of PTP servers to automatically set the date and time.

a) Enter the Interface, Preset, Transport, Ipmode, Unicast IP, Delay Mechanism, Inbound Latency, Outbound Latency, Priority1, Max Master capacity and Log request delay details in their corresponding fields.
b) Enable/Disable Panic Mode to not reset if jump is more than 1 second, use when automatically setting the date and time.

4. Click Save button to save the settings.

# 6.2.6.3 External User Services

# 6.2.6.3.1 LDAP/E-Directory Settings

The Lightweight Directory Access Protocol (LDAP)/E-Directory Settings is an application protocol for querying and modifying data of directory services implemented in Internet Protocol (IP) networks.

In MegaRAC GUI, LDAP is an Internet protocol that MegaRAC® card can use to authenticate users. If you have an LDAP server configured on your network, you can use it as an easy way to add, manage and authenticate MegaRAC® card users. This is done by passing login requests to your LDAP Server. This means that there is no need to define an additional authentication mechanism, when using the MegaRAC card. Since your existing LDAP Server keeps an authentication centralized, you will always know who is accessing the network resources and can easily define the user or group-based policies to control access.

To open External User Services page, click Settings -> External User Services from the menu bar. A sample screenshot of External User Services page is shown below.

![External User Services\nLDAP/E-Directory Settings\nActive Directory Settings\nRADIUS Settings](.axe-7220sr-50m-22810-1000-10/3946bc66351b0b9025a1f5b3f536347a79ca9f3d466e54f332c1eaa7ad24b27d.jpg)

To open LDAP/E-DIRECTORY Settings page, click Settings -> External User Services -> LDAP/E-Directory Settings from the menu bar.

A sample screenshot of External User Services page is shown below.

![LDAP/E-Directory Settings\nGeneral Settings\nRole Groups](.axe-7220sr-50m-22810-1000-10/3cd723b2e938ae63883a0270342a65d040f2787d136e8966c3f5d85dc814ec13.jpg)

The fields of LDAP/E-Directory Settings Page are explained below.

General Settings: To configure LDAP/E-Directory Settings. Options are Enable LDAP/E-Directory Authentication, IP Address, Port and Search base.

Role Groups: To add a new role group to the device. Alternatively, double click on a free slot to add a role group.

Note: It is recommended to Enable LDAP configuration from configure general settings page otherwise error message will pop-up stating that "LDAP configuration is not enabled" while trying to create/view LDAP role groups.

# Procedure

Entering the details in General LDAP/E-Directory Settings Page.

1. In the LDAP/E-Directory Settings Page, click General Settings. A sample screenshot of General LDAP Settings page is given below.

General LDAP Settings

![Enable LDAP/E-Directory Authentication\nEncryption Type\n✓ No Encryption ○ SSL ○ StartTLS\nCommon Name Type\n✓ IP Address ○ FQDN\nServer Address\nPort\n389\nBind DN\nE.g., cn=admin,ou=login,dc=domain,dc=com\nPassword\nWhitespace not allowed\nSearch Base\nE.g., ou=login,dc=domain,dc=com\nAttribute of User Login\ncn\nSave](.axe-7220sr-50m-22810-1000-10/e7cf4fea6751501911537e6a3b214c1723159395e80f55a676e291a0c1d6d6c1.jpg)

2. Click Enable LDAP/E-Directory Authentication, to enable LDAP/E-Directory Settings.
Note: During login prompt, use username to login as an LDAP Group member.
3. Select the encryption type for LDAP/E-Directory from the Encryption Type.
Note: Configure proper port number, when SSL is enabled.
4. Select the Common Name Type as IP Address.
5. Enter the IP address of LDAP server in the Server Address field.

# Note:

IP Address made of 4 numbers separated by dots as in ‘xxx.xxx.xxx.xxx’.

Each Number ranges from 0 to 255.

First Number must not be 0.

Supports IPv4 Address format and IPv6 Address format.

Configure FQDN address, when using StartTLS with FQDN.

6. Specify the LDAP Port in the Port field.

#

Default Port is 389. For SSL connections, default port is 636. The Port value ranges from 1 to 65535.

7. Specify the Bind DN that is used during bind operation, which authenticates the client to the server.

# Note:

Bind DN is a string of 4 to 253 alpha-numeric characters.

It must start with an alphabetical character.

Special Symbols like dot(.), comma(,), hyphen(-), underscore(\_), equal-to(=) are allowed.

Example: cn=manager,ou=login, dc=domain,dc=com

8. Enter the password in the Password field.

# Note:

Password must be at least 1 character long.

White space is not allowed.

This field will not allow more than 48 characters.

9. Enter the Search Base. The Search base allows the LDAP server to find which part of the external directory tree to be searched. The search base may be something equivalent to the organization, group of external directory.

# Note:

Search base is a string of 4 to 253 alpha-numeric characters.

It must start with an alphabetical character.

Special Symbols like dot(.), comma(,), hyphen(-), underscore(\_), equal-to(=) are allowed.

Example: ou=login,dc=domain,dc=com.

10. Select Attribute of User Login to find the LDAP/E-Directory server which attribute should be used to identify the user.

Note: It only supports cn or uid.

11. Select CA Certificate File from the Browse field to identify the certificate of the trusted CA certs.

12. Select the Certificate File to find the client certificate filename.

13. Select Private Key to find the client private key filename.

Note: All the 3 files are required, when SSL or StartTLS is enabled.

14. Click Save to save the settings.

# To add a new Role Group

1. In the LDAP/E-Directory Settings Page, Click Role Groups and select a blank row.

Note: It is recommended to Enable LDAP configuration from configure general settings page otherwise error message will pop-up stating that "LDAP configuration is not enabled" while trying to create/view LDAP role groups.

2. Click Add Role Group or alternatively double click on the blank row to open the Add Role group Page as shown in the screenshot below.

Role Groups

![Group Name\nGroup Domain\neg, dc=domain\nGroup Privilege\nKVM Access\nVMedia Access\nSave](.axe-7220sr-50m-22810-1000-10/dbc36e347299cb74df224c90ec2a917584838c035c876d8eb5921addbf6eec1d.jpg)

3. In the Group Name field, enter the name that identifies the role group.

# Note:

Maximum size of Role Group Name is 255 bytes.

Special symbols hyphen and underscore are allowed.

4. In the Group Domain field. Enter the Role Group Domain where the role group is located.

# Note:

Maximum size of Group Domain Name is 255 bytes.

It must start with an alphabetical character.

Special Symbols like dot(.), comma(,), hyphen(-), underscore(\_), equal-to(=) are allowed.

Example: cn=manager,ou=login, dc=domain,dc=com

5. In the Group Privilege field, enter the level of privilege (User, Administrator, Operator,

None) to assign to this role group.

6. Select the required options or both.

 KVM Access

 VMedia Access

Note: VMedia privilege is not applicable for LMedia and RMedia clients.

7. Click Save to save the new role group and return to the Role Group List.

8.

# 6.2.6.3.2 Active Directory Settings

An active directory is a directory structure used on Microsoft Windows based computers and servers to store information and data about networks and domains. An active directory (sometimes referred to as AD) does a variety of functions including the ability to provide information on objects. It also helps to organize these objects for easy retrieval and access, allows access by end users and administrators and allows the administrator to set security up for the directory.

In MegaRAC SP-X application, Active Directory allows you to configure the Active Directory Server Settings. The displayed table shows any configured Role Groups and the available slots. You can modify, add or delete role groups from here. Group domain can be the AD domain or a trusted domain. Group Name should correspond to the name of an actual AD group.

Note: To view the page, you must be at least a User and to modify or add a group, you must be an Administrator.

To open Active Directory Settings page, click Settings -> External User Settings -> Active Directory from the menu bar. A sample screenshot of Active Directory Settings page is shown below.

![Active directory Settings\nGeneral Settings\nRole Groups](.axe-7220sr-50m-22810-1000-10/7f0984c1cf8dd4658396adc444a6dd7671520c18abc5b7b2a52cfe2218b522cb.jpg)

The fields of Active Directory page are explained below.

General Settings: This option is used to configure Active Directory General Settings. Options are Enable Active Directory Authentication, Secret User Name, Secret Password, User Domain name, and up to three Domain Controller Server Addresses.

Role Groups: To add a new role group to the device. Alternatively, double click on a free slot to add a role group.

Note: It is recommended to Enable AD configuration from configure general settings page otherwise error message will pop-up stating that "AD configuration is not enabled" while trying to create/view AD role groups.

# Procedure

# Entering the details in General Active Directory Settings Page

1. Click on General Settings to open the General Active Directory Settings Page.

![General Active Directory Settings\nEnable Active Directory Authentication\nSSL\nSecret Username\nSecret Password\nUser Domain Name\nDomain Controller Server Address 1\nDomain Controller Server Address 2\nDomain Controller Server Address 3\nSave](.axe-7220sr-50m-22810-1000-10/72b63457fc9e433ac913488eaa2256f0b2b5891480d7a023505a1d3ae7405642.jpg)

2. In the Active Directory Settings page, check or uncheck the Enable Active directory Authentication check box to enable or disable Active Directory Authentication

respectively.

Note: If you have enabled Active Directory Authentication, enter the required information to access the Active Directory server.

3. SSL: Check or uncheck to enable or disable the SSL.
4. Specify the Secret user name and password in the Secret UserName and Secret Password fields respectively.

# Note:

Secret username/password for AD is not mandatory. When secret username & password is empty, Authentication fails will be always treated as Invalid Password error. For Invalid Password error PAM will not try other Authentication Methods.
 User Name is a string of 1 to 64 alpha-numeric characters.
 It must start with an alphabetical character.
 It is case-sensitive.
Special characters like comma, period, colon, semicolon, slash, backslash, square brackets, angle brackets, pipe, equal, plus, asterisk, question mark, ampersand, double quotes, space are not allowed.
Password must be at least 6 character long and will not allow more than 127 characters.
 White space is not allowed.

5. Specify the Domain Name for the user in the User Domain Name field. E.g.

MyDomain.com

6. Configure IP addresses in Domain Controller Server Address1, Domain Controller Server Address2 and Domain Controller Server Address3.

# Note:

IP address of Active Directory server: At least one Domain Controller Server Address must be configured.

 IP Address made of 4 numbers separated by dots as in "xxx.xxx.xxx.xxx".
 Each number ranges from 0 to 255.
 First number must not be 0.
 Domain Controller Server Addresses will supports IPv4 Address format and IPv6 Address format.

7. Click Save to save the entered settings and return to Active Directory Settings Page.

![Role Groups\nNone\nNone\nNone\nNone\nNone](.axe-7220sr-50m-22810-1000-10/570a994ce0f12efbd77e43322850120bc9e89ce0b368fc208c34bbe5f0fcc562.jpg)

The fields of Role Group page are explained below.

Role Group Name: The name that identifies the role group in the Active Directory.

# Note:

Maximum size of Role Group Name is 255 bytes.
 Special symbols hyphen and underscore are allowed.

Group Domain: The domain where the role group is located.

# Note:

Maximum size of Group Domain Name is 255 bytes.
Special symbols hyphen, underscore and dot are allowed.

Group Privilege: The level of privilege to assign to this role group.

KVM Access: To provide access to KVM for AD authenticated role group user.

VMedia Access: To provide access to VMedia for AD authenticated role group user.

# To add a new Role Group

1. In the Active Directory Settings Page, select a Role Group and click Add Role Group or alternatively double click on the blank row to open the Add Role group Page as shown in the screenshot below.

Note: It is recommended to Enable AD configuration from configure general settings page otherwise error message will pop-up stating that "AD configuration is not enabled" while trying to create/view AD role groups.

Role Groups
![Group Name\nGroup Domain\neg., MyDomain.com\nGroup Privilege\nKVM Access\nVMedia Access\nSave](.axe-7220sr-50m-22810-1000-10/de6c81fa43bcbc1b1712a3d15f0f5d3766d33971d6ffb88b93b1520aefc8f4bd.jpg)

2. In the Group Name field, enter the name that identifies the role group in the Active Directory.

# Note:

Maximum size of Role Group Name is 255 bytes.
Special symbols hyphen and underscore are allowed.

3. In the Group Domain field, enter the domain where the role group is located.

# Note:

Maximum size of Group Domain Name is 255 bytes.
Special symbols hyphen, underscore and dot are allowed.

4. In the Group Privilege field, enter the level of privilege to assign to this role group.
5. Select the required options

 KVM Access
 VMedia Access

Note: VMedia privilege is not applicable for LMedia and RMedia clients.

6. Click Save to add the new role group and return to the Role Group List.

# To Delete a Role Group

1. In the Role Groups Page, select the row that you wish to delete.
2. Click Delete Role Group.

# 6.2.6.3.3 RADIUS Settings

RADIUS is a modular, high performance and feature-rich RADIUS suite including server, clients, development libraries and numerous additional RADIUS related utilities.

In MegaRAC GUI, this page is used to set the RADIUS Authentication.

To open RADIUS Settings page, click Settings -> External User Settings -> RADIUS Settings from the menu bar. A sample screenshot of RADIUS Settings page is shown below.

RADIUS Settings

![The image displays a black telephone handset icon, specifically the receiver portion, oriented vertically against a plain white background. There is no text visible in the image.](.axe-7220sr-50m-22810-1000-10/b695cd6e4d47f466f82a2a555a2d6670fddb243813e752cd73e14d1f8ec5ade7.jpg)

![Three gray gears are displayed. A large gear is on the left, interlocking with two smaller gears positioned to its right. The gears are arranged diagonally and have a pixelated appearance.](.axe-7220sr-50m-22810-1000-10/d164df8c9efb9c58468738529e16fb42c3e78ab75545b7bb357ee5351d1a9625.jpg)

# General RADIUS Settings

General RADIUS Settings

![The image displays a blue square containing a white, downward-pointing arrow or chevron, positioned on the right side against a white background.](.axe-7220sr-50m-22810-1000-10/7b85f86003dc9ff0250b8ceef8f7c28c2077818fbcfca23e67bcb726f35d4b83.jpg)

Enable RADIUS Authentication

Server Address

Port

Secret

![The image displays a light blue square icon containing a centered, white checkmark. It resembles a digital button or interface element indicating a 'selected' or 'correct' state. There is no text present.](.axe-7220sr-50m-22810-1000-10/7d245c8611a9c53291eaf9ea21db811bb9bbf59d0aa6f915cffd34427c1be3d2.jpg)

Enable KVM Access

![The image displays a blue square containing a white checkmark centered within it. To the left and top, faint, blurry outlines of adjacent white squares are visible, suggesting a grid or list of checkboxes. The checkmark is oriented diagonally. The overall image is a close-up crop.](.axe-7220sr-50m-22810-1000-10/5430e4f393b5f95ed8c315003e738cd56bd6a36585e8e2adaa0fe93e4f982f8d.jpg)

Enable VMedia Access

Save

The fields of General RADIUS Settings page are explained below.

Enable RADIUS Authentication: Option to enable/disable RADIUS authentication.

Server Address: The IP address of RADIUS server.

# Note:

 IP Address (Both IPv4 and IPv6 format).
 FQDN (Fully Qualified Domain Name) format.

Port: The RADIUS Port number.

# Note:

 Default Port is 1812.
 Port value ranges from 1 to 65535.

Secret: The Authentication Secret for RADIUS server.

# Note:

 This field will not allow more than 31 characters.
 Secret must be at least 4 characters long.
White space is not allowed.

Enable KVM Access: This field provides access to KVM for RADIUS authenticated users.

Enable VMedia Access: This field provides access to VMedia for RADIUS authenticated users.

Save: To save the settings.

# Procedure

1. Enable the RADIUS Authentication check box to authenticate the RADIUS.
2. Click Advanced RADIUS Settings. This opens the Radius Authorization window as shown below.

# Note:

It will not allow more than 127 characters. Special characters like ‘;’ and ‘#’ are not allowed. It is recommended to Enable Radius configuration from configure general RADIUS settings page otherwise error message will pop-up stating that "Radius configuration is not enabled" while trying to create/view Advanced RADIUS Settings.

Advanced RADIUS Settings

![RADIUS Authorization\nAdministrator\nH=4\nOperator\nH=3\nUser\nH=2\nOEM Proprietary\nH=1\nNo Access\nH=0](.axe-7220sr-50m-22810-1000-10/9816dc89f62301e6a9ecec451bc22092a97b0c7be440bd8498deecafd5f10274.jpg)

For Authorization Purpose, configure the Radius user with Vendor Specific Attribute in Server side.

# Example:1

testadmin Auth-Type :=PAP,Cleartext-Password:= "admin"

Auth-Type :=PAP, Vendor-Specific="H=4"

# Example:2

testoperator Auth-Type := PAP, Cleartext-Password := "operator"

Auth-Type :=PAP, Vendor-Specific="H=3"

If you change the Vendor-Specific value in server then you should change the same values in this page.

3. Click Save to save the changes made.

# 6.2.6.4 Service Management

It is used to set service information on the BMC. A sample screenshot of service management is shown as below.

<table><tr><td>Service</td><td>Status</td><td>Interfaces</td><td>Secure Port</td><td>Timeout</td><td>Maximum Sessions</td></tr><tr><td>web</td><td>Active</td><td>both</td><td>443</td><td>1800</td><td>20</td></tr><tr><td>kvm</td><td>Active</td><td>both</td><td>443</td><td>1800</td><td>4</td></tr><tr><td>cd-media</td><td>Active</td><td>both</td><td>443</td><td>N/A</td><td>4</td></tr><tr><td>hd-media</td><td>Active</td><td>both</td><td>443</td><td>N/A</td><td>4</td></tr><tr><td>ssh</td><td>Active</td><td>NA</td><td>22</td><td>600</td><td>N/A</td></tr><tr><td>watchdog</td><td>Inactive</td><td>NA</td><td>N/A</td><td>N/A</td><td>1</td></tr></table>

The service management consists of the following items.

web
kvm
cd-media
hd-media
ssh
watchdog

(Click the "edit" button in the "watchdog" column to enter the "watchdog" configuration interface (the interface is as follows), watchdog default state is inactive, if watchdog is set to the active state, it will monitor the BMC in real time.)

# Service Configuration

![Service Name\nwatchdog\nActive\nMaximum Sessions\n1\nSave](.axe-7220sr-50m-22810-1000-10/821a1549a152457d494c734c756a544ca035185b0e1c2a089ff6465f3c3a660c.jpg)

# 6.2.6.5 Network Configuration

Note: Change the IP settings of the management ports will disconnect the network.

This section is used to configure the network settings for the available LAN channels.

# 6.2.6.5.1 Network IP Settings

This section is used to configure the network IP settings.

To open the Network IP Settings page, click Settings -> Network Settings -> Network IP Settings.

Network IP Settings

![Enable LAN\nLAN Interface\neth0\nMAC Address\n00:30:64:66:77:88\nEnable IPv4\nEnable IPv4 DHCP\nIPv4 Address\n188.188.1.100\nIPv4 Subnet\n255.255.255.0\nIPv4 Gateway\n188.188.1.1](.axe-7220sr-50m-22810-1000-10/81507e1b12233ba033b6301a03c2c6526335c21bcda49570fdaa088a46742074.jpg)

The fields of Network IP Settings page are explained below.

 Enable LAN: Enable or disable the LAN settings.
 LAN Interface: Select the LAN interface to be configured.
 MAC Address: Display the read-only MAC Address of the selected interface.
 Enable IPv4: Enable or disable the IPv4 settings for the selected interface.
 Enable IPv4 DHCP: Enable or disable the IPv4 DHCP support for the selected interface. If disable the IPv4 DHCP support, then static IP address is selected, configure the static IPv4 Address, IPv4 Subnet, and IPv4 Gateway.

# Notes:

 An IP address consists of 4 numbers separated by dots, as in "xxx.xxx.xxx.xxx".
 Each number ranges from 0 to 255.
 The first number must not be 0.

![Enable IPv6\nEnable IPv6 DHCP\nIPv6 Index\n0\nIPv6 Address\nfe80::15ca:1212:749e:8f27%4\nSubnet Prefix Length\n0\nIPv6 Gateway\n::](.axe-7220sr-50m-22810-1000-10/4302ee84c61ebe004a4b3c7b0e1ca0cdfa7035a124b7362b28866a22af160637.jpg)

 Enable IPv6: Enable or disable the IPv6 configuration settings.
 Enable IPv6 DHCP: Enable or disable the IPv6 DHCP support for the selected interface. It dynamically configures IPv6 address using DHCP (Dynamic Host Configuration Protocol).
Note: Disable this Enable IPv6 DHCP field and enter the values in following fields such as IPv6 Index, IPv6 Address, Subnet Prefix Length and IPv6 Gateway.
 IPv6 Index: Specify a static IPv6 index to be configured to the device. E.g.: 0
 IPv6 Address: Specify a static IPv6 address to be configured to the device. E.g.: 2004::2010.
 Subnet Prefix Length: Specify the subnet prefix length for the IPv6 settings. The value ranges from 0 to 128.
 IPv6 Gateway: Specify an IPv6 default gateway for the IPv6 settings.

![Enable VLAN\nVLAN ID\n0\nVLAN Priority\n0\nSave](.axe-7220sr-50m-22810-1000-10/5097bb12ffe025b58c3a0dc1672b0bc4f2b6e55b0abec820d6a8268351ec09f2.jpg)

 Enable VLAN: Enable or disable VLAN support for the selected interface.
 VLAN ID: Value ranges from 2 to 4094. VLAN ID 0, 1 & 4095 are reserved VLAN IDs.
 VLAN Priority: Value ranges from 0 to 7. 7 is the highest priority for VLAN.
 Save: Save the entries.

# 6.2.6.5.2 Network Link Configuration

This section is used to configure the network link.

To open Network Link Configuration page, click Settings ->Network Settings -> Network Link Configuration.

Network Link Configuration

![LAN Interface\neth1\n✓ Auto Negotiation\nLink Speed\n100 Mbps\nDuplex Mode\nFULL Duplex\nNCSI Interface\nEnabled\nSave](.axe-7220sr-50m-22810-1000-10/287f12fe2dc0f4fe947c2b58c1a51b55d91babe0bea3c90cc89dd1aefcec72b2.jpg)

The fields of the Network Link Configuration page are explained below.

 LAN Interface: Select the required network interface from the list to which the link speed and duplex mode are to be configured.
 Auto Negotiation: Enable to allow the device to perform automatic configuration to achieve the best possible mode of operation (speed and duplex) over a link.
 Link Speed: Link speed will list all the supported capabilities of the network interface. It can be 10/100/1000 Mbps.
Note: Link speed of 1000 Mbps is not applicable when Auto Negotiation is OFF.
 Duplex Mode: This field could be either Half Duplex or Full Duplex.
 NCSI Interface: The NCSI interface status could be either Enabled or Disabled for the selected LAN interface.
 Save: Save the settings.

# 6.2.6.5.3 DNS Configuration

The Domain Name System (DNS) is a distributed hierarchical naming system for computers, services, or any resource connected to the Internet or a private network. It associates the information with domain names assigned to each of the participants. Most importantly, it translates domain names meaningful to humans into the numerical (binary) identifiers associated with networking equipment for the purpose of locating and addressing these devices worldwide.

This section is used to manage the DNS settings of a device.

To open DNS Configuration page, click Settings > Network Settings > DNS Configuration.

# DNS Configuration

![DNS Enabled\nmDNS Enabled\nHost Name Setting\nAutomatic Manual\nHost Name\nAMI003064667788](.axe-7220sr-50m-22810-1000-10/eb101895823bb46579c9e4993574614f58f9f5d053e82ba2a1edb52f854db72e.jpg)

The fields of DNS Configuration page are explained below.

# Domain Name Service Configuration

 DNS Enabled: Enable or disable all the DNS service configurations.
 mDNS Enabled: Enable or disable the multicast DNS.
 Host Name Setting: Choose either Automatic or Manual settings.
 Host Name: Display host name of the device.

\- If the Host setting is chosen as Manual, then specify the host name of the device.

# Notes:

 Value ranges from 1 to 64 alpha-numeric characters.
 Special character ‘-’(hyphen) is allowed.
 It must not start or end with a ‘-’(hyphen).
√ The underscore (\_) character and double hyphen (--) character are not a legal character for use in host names.

BMC Registration Settings

BMC Interface

etho

![The image shows a blue square containing a white checkmark centered inside.](.axe-7220sr-50m-22810-1000-10/b3ec150f50342ffc8cdc4ed7ba4470a267b189c779f3a85af60033c19532bc44.jpg)

Register BMC

Registration Method

![The image displays a blue circle containing a white checkmark in the center.](.axe-7220sr-50m-22810-1000-10/d22b2b6392d2ed0d2e577c166113e8223b8cd59a92c8d292cf5e6047b5c3a866.jpg)

Nsupdate

![The image displays a simple, thin white circle centered on a solid black background. There is no text present in the image.](.axe-7220sr-50m-22810-1000-10/d43625875858a1145d13bda85b04d0918ebf9a79f4e1dae4aa5094d6c52a9d44.jpg)

DHCP Client FQDN

![The image displays a thin, grey circular outline centered on a white background. Vertical black bars frame the left and right sides of the image. There is no text present.](.axe-7220sr-50m-22810-1000-10/8818d68a9b236760713dff1984ceab56b8374af03d3cca8537ca8bd42f18245f.jpg)

Hostname

BMC Interface

eth1

![The image displays a blue square icon containing a centered white checkmark. The square is flanked by thin white vertical strips on either side.](.axe-7220sr-50m-22810-1000-10/16b896d64fa37128abd50ad6284d37d5e8e8903af0c0fe1f9f98ffd464a992c6.jpg)

Register BMC

Registration Method

![The image displays a solid blue circle containing a centered white checkmark. There is no text present.](.axe-7220sr-50m-22810-1000-10/243394408726956bf911e310d74a3baf520bdd38a7bd8a0c5c5f18be9549ab1d.jpg)

Nsupdate

![The image features three white circles aligned horizontally across a light grey background. The circles are of equal size and are spaced evenly from one another.](.axe-7220sr-50m-22810-1000-10/9983ce6124ee0286286e16e05a83bc40622c7a7a1d242b9c5b4ff7a0c87a3597.jpg)

DHCP Client FQDN

![The image displays a vertical white rectangle bordered by thick black vertical bars on the left and right sides. Centered within the white area is a large, thin, light gray circle.](.axe-7220sr-50m-22810-1000-10/6f05c7157f713d9bbab724d1cc85bda39c9e20c1dfc9c16fc4c5a64b9d4d112d.jpg)

Hostname

# BMC Registration Settings

 BMC Interface: Options to register the BMC through the Interfaces (eth0&eth1).

 Register BMC: Register BMC through registration method.
 Registration Method: Options to register the BMC through Nsupdate or DHCP Client FQDN or Hostname.

![Both\nEth0 TSIG Configuration\nTSIG Authentication Enabled\nCurrent TSIG Private File Information\nNot Available\nNew TSIG Private File\nEth1 TSIG Configuration\nTSIG Authentication Enabled\nCurrent TSIG Private File Information\nNot Available\nNew TSIG Private File](.axe-7220sr-50m-22810-1000-10/5e59bf26989a287377a22361221169598d6b333101f42aa89558993e222188f5.jpg)

# TSIG Configuration

 Both: Check this option to modify TSIG authentication for both interfaces.
 Eth 0&1:

- TSIG Authentication Enabled: Check this box to enable TSIG authentication while registering DNS via nsupdate. Separate TSIG files can be uploaded for each LAN interface.
Current TSIG Private File Information: The information of current TSIG private file along with its uploaded date and time will be displayed (read only).
- New TSIG Private File: Browse and navigate to the TSIG private file.

Domain Setting

![A blue circle containing a white checkmark.](.axe-7220sr-50m-22810-1000-10/35da1b716ae06e1df03a7c8b67e6ec875092342946dc36ad72cd32a0c9605602.jpg)

Automatic

![The image features a simple, thin white circle centered on a solid black background.](.axe-7220sr-50m-22810-1000-10/f9147e58214d69334a46ac62cfff72b973ae04398138600e92c3018f241bb229.jpg)

Manual

Domain Interface

eth1\_v4

![The image displays a black, downward-pointing chevron or caret symbol centered on a white background. The graphic is low-resolution and pixelated. There is no text present in the image.](.axe-7220sr-50m-22810-1000-10/901d2d05c0180cdea2693f9ce539c8363ce075ab14617480382f99b99e508662.jpg)

 Domain Setting: Select whether the domain interface will be configured manually or automatically.

- Automatic: If you select Automatic, the Domain Name cannot be configured as it will be done automatically.
- Manual: If you select Manual, then specify the domain name of the device.

# Notes:

 If you select Automatic, it displays the Domain Interface option. If you select Manual, it displays Domain name.

 Domain name must be a string of 4 to 253 alphanumeric characters. (254 characters are allowed only if the last byte is dot.)
 Domain name must start with a letter and end with a letter or digit. (Must contain at least one dot character) Only letters, digits, dot and hyphen are allowed.

![Domain Name Server Setting\n✓ Automatic ○ Manual\nDNS Interface\neth0\nIP Priority\n✓ IPv4 ○ IPv6\nSave](.axe-7220sr-50m-22810-1000-10/09c7ef2f4ccb8fc036664ffd66835e3883325c3d7229ef73b9f95f13b98d6ccc.jpg)

#  Domain Name Server Setting:

- Automatic - If you select Automatic, DNS Interface option should be explained.
- Manual - Specify the DNS (Domain Name System) server address to be configured for the BMC.

#  IP Priority:

- IPv4: It will have 2 IPv4 DNS servers and 1 IPv6 DNS server.
- IPv6: It will have 2 IPv6 DNS servers and 1 IPv4 DNS server.
Note: This is not applicable for Manual configuration.

#  DNS Server 1, 2 & 3:

Specify the DNS (Domain Name System) server address to be configured for the BMC. Notes:

- IPv4 Addresses should be given in dotted decimal representation.
- IPv6 Addresses are supported and must be global unicast addresses.
- DNS Server Address will support the following:

IPv4 Address format.
IPv6 Address format.

 Save: Save the entered changes.

# 6.2.6.5.4 Sideband Interface (NC-SI)

This section is used to configure Network Controller Sideband Interface (NCSI) settings.

To open the Sideband Interface (NC-SI) page, click Settings -> Network Settings -> Sideband Interface (NC-SI).

Sideband Interface (NC-SI)

![NCSI Mode\n✓ Auto Failover Mode ○ Manual Switch Mode\nNCSI Interface\neth1\nPackage ID\n0 (active)\nChannel Number\n0 (package 0)(active)](.axe-7220sr-50m-22810-1000-10/35a2a0787acfe6c9c3862bc8fa1ee304ac301bede12dedb6470ea225a5ad2fb4.jpg)

The fields of the Sideband Interface (NC-SI) page are explained below.

 NCSI Mode:

 If you select Auto Failover Mode, the NCSI interface and other settings will be configured automatically.
 If you select Manual Switch Mode, you are allowed to configure the below settings.

 NCSI Interface: Select the NSCI interface for which you need to configure NCSI settings.
 Package ID: Select the package ID to be configured for the selected interface.
 Channel Number: Select the channel number to be configured for the selected interface.
 Save: Save the settings.

# 6.2.6.6 NIC Management

This page displays the NIC Controller information by using WEB UI support. To open the NIC Controller Information page, click Settings -> NIC Management -> NIC Controller Information.

# NIC Controller Information

![The image shows a vertical rectangular graphic with a light green circle centered on a white background. Inside the circle is a white question mark.](.axe-7220sr-50m-22810-1000-10/738a6f5ce1086f1a246cf85595d6bb10277c453fc2f1a750e6475e237a70c7be.jpg)

NIC Controller

NCSI Version:

Firmware Name :

E810 FW ver

Firmware Version :

00.00.04.50

Capabilities Flags :

<table><tr><td>Hardware Arbitration Capability</td><td>Not Supported</td></tr><tr><td>Host NC Driver Status</td><td>Supported</td></tr><tr><td>Network Controller to Management Controller Flow Control Support</td><td>Not Supported</td></tr><tr><td>Management Controller to Network Controller Flow Control Support</td><td>Not Supported</td></tr><tr><td>All multicast addresses support</td><td>Not Supported</td></tr><tr><td>Hardware Arbitration Implementation Status</td><td>Implemented Not Implemented</td></tr></table>

Broadcast Capability:

<table><tr><td>ARP Packets</td><td>Filter out this packet type</td></tr><tr><td>DHCP Client Packets</td><td>Filter out this packet type</td></tr><tr><td>DHCP Server Packets</td><td>Filter out this packet type</td></tr><tr><td>NetBIOS Packets</td><td>Filter out this packet type</td></tr></table>

The fields of NIC Controller Information are as follows.

 NIC Controller: This field contains NIC MCTP EID value.
 NCSI Version: This field contains data of both NCSI Alpha 1 and NCSI Alpha 2 versions.
 Firmware Name: This field contains data of Firmware Name 1, Firmware Name 2 and

Firmware Name 3.

 Firmware Version: This field contains data of Firmware version.
 Capabilities Flags: This field contains data of Capabilities Flags. It displays information like Hardware Arbitration Capability, Host NC Driver Status, Network Controller to Management Controller Flow Control Support, Management Controller to Network Controller Flow Control Support, All multicast addresses support and Hardware Arbitration Implementation Status.
 Broadcast Capability: This field contains data of Broadcast Capability. It displays the information like ARP Packets, DHCP Client Packets, DHCP Server Packets, and NetBIOS Packets.
 Multicast Capability: This field contains data of Multicast Capability. It displays the information like IPv6 Neighbor Advertisement, IPv6 Router Advertisement, DHCPv6 relay and server multicast, DHCPv6 multicasts from server to clients listening on wellknown UDP Ports, IPv6 MLD, and IPv6 Neighbor Solicitation.
 Buffering Capability: This field contains data of Buffering capability.
 AEN Control Support: This field contains data of AEN Control support.
 VLAN Filter Count: This field contains data of VLAN Count.
 VLAN Mode Support: This field contains the data of VLAN support information.
 Channel Count: This field contains data of Channel Count.
 MAC Address Count: This field contains data of MAC Address Count.
 MAC Address: This field contains data of MAC Address based on the number of MAC Address Count.
 MAC Address Flags: This field contains data of MAC address flags.
 VLAN Tag Count: This field contains data of VLAN Tag Count.
 VLAN Tag Flags: This field contains data of VLAN Tag Flags.
 Link Setting: This field contains data of Link Settings.
 Link Status: This field contains data of Link Status.
 Config Flags: This field contains data of config flags.
 Flow Control: This field contains data of flow control.

OEM Information: This field contains data of OEM information. It displays information like MAC address of each channel, Maximum Temperature (Intel), Max Operating Temperature (Mellanox), Max Measured Temperature (Mellanox), and Current Temperature.

# 6.2.7 Remote Management

The "Remote Control" includes two functions: KVM and SOL, KVM is mainly used to remotely access the x86 system through WEB, and SOL is mainly to access x86 BIOS configuration information through WEB, WEB UI is as follows.

Remote Control Remote KVM & SOL

H5Viewer

Click here to go to Remote Session Settings.

![The image displays a white icon on a solid green background. The icon is a square outline with the top-right corner missing, featuring an arrow pointing diagonally outward from that corner. There is no text present in the image.](.axe-7220sr-50m-22810-1000-10/60c950ac127d71bbd31ab0e9c4bfa1e2456c053243be3c77e1df169332a3dd6a.jpg)

Launch H5Viewer

Serial Over LAN

![The image displays a white icon on a solid green background. The icon is a square with rounded corners. Inside the square, an arrow points diagonally upwards and to the right, with its tip extending outside the top-right border of the square.](.axe-7220sr-50m-22810-1000-10/8939f80b3c4acfe8118b240c4a97082f05e1456eab8a4bfe3bd9d2765353ab2f.jpg)

Activate

# 6.2.7.1 KVM

# Launch H5Viewer

The system and browser requirements for Remote Control are given below.

# System Requirements

Client machine with 8GB RAM.

If the client machine has 4GB RAM or lower, there will be lag in Video/Keyboard/ Mouse/Media redirection functionality.

# Supported Browsers

 Chrome latest version
 IE11 and above
 Firefox (with limited support)
 Edge
 Safari (On Mac only)

Note: It is advisable to use Chrome or IE for H5Viewer, since Firefox has its own memory limitations.

To open Remote Control page, click Remote Control from the menu bar. A detailed description of the menu items is given below.

Open the "Remote Control" page, click "Launch H5Viewer". A sample screenshot of the Remote KVM page is shown below.

![Remote KVM (172.20.2.137) - (1024 x 768 ) - Google Chrome\n不安全 https://172.20.2.137/viewer.html\nStop KVM\nVideo Mouse Options Keyboard Send Keys Hot Keys Video Record Power Active Users Help\nCD Image: Browse File (0 KB) Start Media\nZoom 100 %\nUsername\nUbuntu\nLWIN RWIN LALT LCTRL RALT RCTRL NUM CAPS SCR](.axe-7220sr-50m-22810-1000-10/9afe9750907ec039f05de3527ea28eed017b46b7933a6cef194999824cbb859e.jpg)

# Procedure to Start KVM

1. Click Launch H5Viewer to open the Remote Control KVM page.
2. To stop the H5Viewer video redirection, click Stop KVM.

# Procedure to Start /Stop Media

1. Click Browse File to select CD Image. After selecting the image, Select/Unselect media boost option.
2. Click Start Media to redirect the selected CD image file to the Host. A sample screenshot is as shown below.

Note: If media boost mode is selected, the processes related to media redirection will have high priority than other processes. This will improve media performance but other processes will have limited access to CPU cycle.

CD Image:ubuntu-2.04-desktop-amd64.iso (14665 KB)  Media Boost Stop Media

# 3. To stop the CD Image redirection, click Stop Media.

A detailed description of menu items are given below.

# Video

This menu contains the following sub menu items.

Pause Video: This option is used for pausing Console Redirection.

Resume Video: This option is used to resume the Console Redirection when the session is paused.

Refresh Video: This option can be used to update the display shown in the Console Redirection window.

Capture Screen: This option helps to take the screenshot of the host screen and save it in the client s system.

# Mouse

Show Client Cursor: This menu item can be used to show or hide the local mouse cursor on the remote client system.

Mouse Mode: This option handles mouse emulation from local window to remote screen using either of the two methods. Only Administrator has the right to configure this option.

Absolute mouse mode: The absolute position of the local mouse is sent to the server if this option is selected.
Relative mouse mode: The Relative mode sends the calculated relative mouse position displacement to the server if this option is selected.
Other mouse mode: This mouse mode sets the client cursor in the middle of the client system and sends the deviation to the host. This mouse mode is specific for SUSE Linux installation.
Note: AMI MegaRAC SP‐X suggests users to use Linux version of OS except SUSE11.4 with BMC to avoid mouse sync issue in absolute mouse mode.
Client cursor will be hidden always. If you want to enable, use Alt + C to access the menu.

# Options

# Zoom:

Normal - By default, this option is selected.

Zoom In - For increasing the screen size. This zoom varies from 100% to 150% with an interval of 10%

Zoom Out - For decreasing the screen size. This zoom varies from 100% to 50% with an interval of 10%

Block Privilege Request: To enable or disable the access privilege of the user.

\*Compression Mode: This option helps to compress the Video data transfer to the specific mode.

\*DTC Quantization Table: This option helps to choose the video quality.

Note: \*Specific to AST SOC.

# Keyboard

Keyboard Layout: This feature is fully compatible when host and client has the same keyboard language layout. If the client and host language layouts differ, some special characters will not be compatible.

List of Host Physical Keyboard languages supported in SPX H5Viewer.

 English U.S.
 German.
 Japanese.

# Send Keys

This option is used to key items. This menu contains the following sub menu items.

Hold Down

Press and Release

# Hold Down

This menu contains the following sub menu items.

Right Ctrl Key: This menu item can be used to act as the right-side &lt;CTRL&gt; key when in Console Redirection.

Right Alt Key: This menu item can be used to act as the right-side &lt;ALT&gt; key when in Console Redirection.

Right Windows Key: This menu item can be used to act as the right-side &lt;WIN&gt; key when in Console Redirection.

Left Ctrl Key: This menu item can be used to act as the left-side &lt;CTRL&gt; key when in Console Redirection.

Left Alt Key: This menu item can be used to act as the left-side &lt;ALT&gt; key when in Console Redirection.

Left Windows Key: This menu item can be used to act as the left-side &lt;WIN&gt; key when in Console Redirection. You can also decide how the key should be pressed: Hold Down or Press and Release.

# Press and Release

Ctrl+Alt+Del: This menu item can be used to act as if you depressed the &lt;CTRL&gt;, &lt;ALT&gt;and&lt;DEL&gt; keys down simultaneously on the server that you are redirecting.

Left Windows Key: This menu item can be used to act as the left-side &lt;WIN&gt; key when in Console Redirection. You can also decide how the key should be pressed: Hold Down or Press and Release.

Right Windows Key: This menu item can be used to act as the right-side &lt;WIN&gt; key when in Console Redirection.

Context Menu Key: This menu item can be used to act as the context menu key, when in Console Redirection.

Print Screen Key: This menu item can be used to act as the print screen key, when in Console Redirection.

# Hot Keys

This menu is used to add the user configurable shortcut keys to invoke in the host machine.

The configured key events are saved in the BMC.

This menu contains the following sub menu items.

• Add Hot Keys - This menu is used to enable macros. Click Add to macros.

# Video Record

This menu contains the following sub menu items.

Record Video: This option is to start recording the screen.

Stop Recording: This option is used to stop the recording.

Record Settings: This option is used to set video record duration and video compression value. Video record duration value should be in the range of 1 to 1800 seconds. Video Compression value should be in the range of 0.1 (Low image quality) to 1.0 (High image quality).

Normalized video resolution to 1024 X 768 (\*specific to AST SOC): Host video will be scaled to 1024 x 768 in the recorded video file. Enabling this option improves client side video recording performance in H5Viewer.

Disable this option to record video at same resolution as host video. The host video capture depends on client system performance. If this option is disabled, recorded video file may have inconsistency. (i.e., Recorded video file duration may not be the same as configured value).

# Note:

The Maximum video file size allowed is around 40MB. If the video file size reaches its max size limit, the recorded file is downloaded and recording will be in progress until the configured video recording time is reached. The video file is saved as video date‐month‐year hr‐min‐sec part no in client side video recording.

User have to take care of saving the video files in different browsers.

When H5Viewer focus is lost and if video recording is in progress, the recording will be stopped with a notification message and the recorded video file will be discarded.

Due to browser limitation, Set timeout/set interval will be delayed from specified time of interval when browser window loses focus, hence video server will not send the video packets to H5Viewer and so the video recording will be stopped.

# Power

The power options are to perform any power cycle operation. Click on the required option to perform the following operation.

Reset Server: To reboot the system without powering off (warm boot).

Immediate Shutdown: To perform Power OFF Immediately.

Orderly Shutdown: To Power OFF the server in proper order.

Power ON Server: To Power ON the server.

Power Cycle Serve: To first power off, and then reboot the system (cold boot).

# Active Users

Click this option to display the active users and their system ip address.

Active KVM Session can be terminated when there are multiple KVM Session from Master [FULL Privilege KVM Session].

# Help

Click this option to get more information About H5Viewer. The KVM Remote Console utility version and plugin version will be displayed.

# Quick Buttons

Quick Buttons: The upper right of H5Viewer window displays all the quick buttons. These quick buttons allow you to perform the below functions by clicking them.

<table><tr><td>Quick Buttons</td><td>Explanation</td></tr><tr><td>&lt;img src="images/86be72b6085e155f6bdd9b514f7dec82b184c22821f2990ca8a5297d1918092a.jpg"/&gt;</td><td>This quick button will show / hide notifications dropdown menu, which will contains the list of notifications displayed by H5Viewer.</td></tr><tr><td>&lt;img src="images/962c6a6f9ccd1b4c42caa9dd2c6054506848a68e9f0650efaf0464bdfb97c594.jpg"/&gt;</td><td>It shows the current zoom value in percentage.</td></tr><tr><td>&lt;img src="images/36c92dd60a177872fa005286fe4c1fc48a969d93fc21bd4e20e68084c05dd4ae.jpg"/&gt;</td><td>This quick button is used to display the current host monitor status. If icon is in green color then host monitor is unlocked. If the icon is in red color host monitor is locked. By clicking the button, host monitor status can be toggled.</td></tr><tr><td>&lt;img src="images/15f428587af77a884c25ea388e858f696bc98f2574d04ce67807750eecb1985f.jpg"/&gt;</td><td>This quick button is used to display the current server power status. If the icon is in green color, the server status is powered on. If the icon is in red color, the server status is powered off. Click the button to toggle immediate power off / power on the host.</td></tr></table>

# Status barbuttons

![LWIN RWIN LALT LCTRL RALT RCTRL NUM CAPS SCR](.axe-7220sr-50m-22810-1000-10/e9ccac821d0c5771d642590958874f0544f00a4bc6918d4156ef8495b0a89bcf.jpg)

Num/Caps/Scroll lock buttons are LED status buttons that denotes the current status of Num/Caps/ Scroll lock in the host.

# Keyboard LED Sync

When the H5Viewer is launched, the keyboard locks status and LEDs denoting the lock status of the host machine, should be in sync with the client machine. That is, if the Num/Caps/Scroll lock is enabled/disabled in the client machine, the same should be updated in the host machine as well.

# Note:

# Client Side Limitations

Due to web browser related security concerns, this feature has following limitations.

‐ Host LED status will be synced with client LED status, only if user presses any key in client keyboard when H5Viewer window is in focus.
‐ Client keyboard LED status cannot be updated from web browsers.

# Host Side Limitations

In some Linux hosts, when the host is booted into text mode, CAPS LOCK LED status will not be updated properly. CAPS LOCK LED will not turn ON/OFF while changing the CAPS lock status in the host OS.

‐ In such cases, H5Viewer CAPS LOCK synchronization functionality will not work properly.

‐Example ‐ Typing letters in H5Viewer (after pressing CAPS LOCK) will toggle between lower to upper case inside host.

# KVM Sharing

MegaRAC SP-X stack supports N number of KVM redirection sessions. Only one full permission H5Viewer session at a time. With Full permission in H5Viewer, the user can control the KVM redirection, and the other H5Viewer users can only view the video redirected from the server without intervention.

When the First user launches H5Viewer, the user will get full permission to control the host during KVM redirection. When another H5Viewer session is launched, the Video server will send KVM sharing permission request packet to the current session, for the new Requesting session.

Once the requesting session is authenticated, a packet containing the information such as the client IP/hostname and user name of the newly authenticated or logged in user, will be send to the current session. The first client shows the dialog as a shown below:

![Slave Permission\n\nadmin user with IP address 172.20.2.72 is trying to connect. What level of permission do you wish to grant them?(If Full Permission is selected, active H5Viewer media redirection will be terminated)\nYou have 4 more seconds to make a decision. The YES option will be chosen if no answer is obtained.\n\nFull Permission	Partial Permission	Block Privilege Request	No Permission\n		Partial Permission\n		No Permission](.axe-7220sr-50m-22810-1000-10/5723d66b66a4c4aee4836e75acca11c8b707f7d0b17b60e62477176d7b0b8b92.jpg)

Clicking the button in the dialog box will trigger specified action:

Full Permission: When this button is clicked, the requesting session will receive full access permission, and the current (full permission) session will have a partial KVM access permission only.

Partial Permission: When this button is clicked, the requesting session will receive partial permission and can only view server display (Video only).

Block Privilege Request -> Partial Permission: Once this option is selected, both newly requesting session and active partial privileged session will get partial permission as auto response and can only view server display. Further request will be served by auto response mechanism.

Block Privilege Request -> No Permission: Once this option is selected, both newly requesting session and active partial privileged session access will be denied as auto response. Further request will be served by auto response mechanism.

No Permission: When this button is clicked, the requesting session access will be denied.

# 6.2.7.2 SOL

The serial over LAN (SOL) feature is very useful, and the SOL redirects the local serial interface via an IPMI session, allowing remote access to the console.

Click the "Active" button on the "Remote Control" interface to enter the SOL output window, and then enter the BIOS configuration interface, and the content of the BIOS configuration will be redirected to the WEB UI, as shown in the following figure.

<table><tr><td colspan="5">Aptio Setup - AMI</td><td></td></tr><tr><td>Main</td><td>Advanced</td><td>Platform</td><td>Configuration</td><td>Socket Configuration</td><td>Server Mgmt S</td></tr><tr><td>BIOS Information</td><td></td><td></td><td></td><td></td><td>Set the Date.</td></tr><tr><td>BIOS Vendor</td><td></td><td></td><td>American Megatrends</td><td></td><td>switch between</td></tr><tr><td>BIOS Version</td><td></td><td></td><td>1.2.10</td><td></td><td>Default Range</td></tr><tr><td>Build Date</td><td></td><td></td><td>01/24/2024</td><td></td><td>Year: 1998-99</td></tr><tr><td>RC Version</td><td></td><td></td><td>370.P03</td><td></td><td>Months: 1-12</td></tr><tr><td>SPS FW Version</td><td></td><td></td><td>6.1.2.48</td><td></td><td>Days: Depende</td></tr><tr><td></td><td></td><td></td><td></td><td></td><td>Range of Year</td></tr><tr><td>System Information</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Project Name</td><td></td><td></td><td>MECS-7120</td><td></td><td></td></tr><tr><td>CPU Board Version</td><td></td><td></td><td>A1</td><td></td><td></td></tr><tr><td>CPU Brand String</td><td></td><td></td><td>Intel(R) Xeon? Gold 542 3N</td><td></td><td></td></tr><tr><td>CPU Frequency</td><td></td><td></td><td>2.10GHz</td><td></td><td></td></tr><tr><td>Total Memory</td><td></td><td></td><td>16384 MB (DDR5)</td><td></td><td>&gt;&lt;: Select Sc</td></tr><tr><td>Memory Frequency</td><td></td><td></td><td>4000 MHz</td><td></td><td>^v: Select It</td></tr><tr><td>PCH SKU</td><td></td><td></td><td>EBG B1</td><td></td><td>Enter: Select</td></tr><tr><td></td><td></td><td></td><td colspan="2">Save &amp; Exit ----</td><td>+/-: Change O</td></tr><tr><td>System Date</td><td></td><td></td><td rowspan="6" colspan="2">Quit without saving?</td><td>F1: General H</td></tr><tr><td>System Time</td><td></td><td></td><td>F8: Previous</td></tr><tr><td rowspan="3">Access Level</td><td rowspan="3"></td><td rowspan="3"></td><td>F9: Optimized</td></tr><tr><td>F10: Save &amp; E</td></tr><tr><td>ESC: Exit</td></tr><tr><td>PCH SKU</td><td></td><td></td><td></td></tr></table>

# 6.2.8 Server Maintenance

This function is mainly maintenance tasks on the device. Click Maintenance on the left function bar to enter the following interface.

Maintenance

![Backup Configuration\nFirmware Update\nSystem Administrator](.axe-7220sr-50m-22810-1000-10/8cd6440647f7161d46ad3a8b16a51b4cdf930388c034b37190b3b529c0a0f0d8.jpg)

![Dual Image configuration\nPreserve Configuration](.axe-7220sr-50m-22810-1000-10/a35e8eeb5a9d1db906f6a3295d01354f112b4c70489081c0920ebe95f3919a10.jpg)

![Firmware Image Location\nRestore Configuration](.axe-7220sr-50m-22810-1000-10/2b4f133892f70bb5d058b1c56fdd8050806694898f0013ba0ca8c59df2d9592a.jpg)

![Firmware Information\nRestore Factory Defaults](.axe-7220sr-50m-22810-1000-10/1bd8540ec8c04b080d09567641ab6d7090344abbf6259a12aa668c78c6da9574.jpg)

# 6.2.8.1 Firmware Update

The system upgrade function is for updating and maintaining the system. Mainly used to update BMC and BIOS. Here's how to update via the Web.

# 6.2.8.1.1 BMC Update

# Preserve Configuration

This page allows the user to configure the preserve configuration items, which will be used by the Restore factory defaults to preserve the existing configuration without overwriting with defaults/Firmware Upgrade configuration.

To open Preserve Configuration page, click Maintenance -> Preserve Configuration from the menu bar. A sample screenshot of Preserve Configuration page is shown below.

![Preserve Configuration\nClick here to go to Firmware Update or Restore Factory Defaults\n✓ Check All\n✓ SDR\n✓ FRU\n✓ SEL\n✓ IPMI\n✓ Network\n✓ NTP\n✓ SNMP\n✓ SSH\n✓ KVM\n✓ Authentication\n✓ Syslog\n✓ Web\n✓ Extlog\n✓ Redfish\nSave](.axe-7220sr-50m-22810-1000-10/47cb611726b6c10ed02f780b77bc8756153cacbf31430fd5482781d7fd74a836.jpg)

The various fields of Preserve Configuration are as follows.

Click here to go to Firmware Update or Restore Factory Defaults: This link will redirect

to the Firmware Update or Restore Factory Defaults page which needs to be preserved.

Check All: To check the entire configuration list.

Save: To save any changes made.

# Procedure

1. Click Firmware Update or Restore Configuration link to view Firmware Update or Restore Configuration page accordingly.
2. Select the required Preserve Configuration items by either choosing the items individually by selecting the appropriate check boxes or by selecting all or none using Check All.
3. Click Save to save the changes.

# Firmware Update

This wizard takes you through the process of firmware upgradation. A reset of the box will automatically follow if the upgrade is completed or cancelled. An option to Preserve All Configuration is available. Enable it, if you wish to preserve configured settings through the upgrade.

To perform Dual Firmware Update operation, click Maintenance -> Firmware Update from the menu bar.

# Procedure

1. Click Browse to select firmware image.
Note: A file upload pop-up will be displayed for http/https but in the case of tftp files, the file is automatically uploaded displaying the status of upload.
2. Click Start firmware update to load the Firmware Update information. A sample screenshot is displayed below.

# Firmware Update

![A green circular icon featuring a white question mark in the center.](.axe-7220sr-50m-22810-1000-10/b0e2b295f859fd7d786befcbcb3a62c43c7d6f789ed442f75435dfc609e9de40.jpg)

#

Select Firmware Image

![The image shows a blue background with a white, abstract shape resembling a folded paper bird on the left and five white dots arranged horizontally to the right.](.axe-7220sr-50m-22810-1000-10/6f197aa8f1982c0bc0e741047de72bb2d0631d3d43c233789cb5aaf7b78990d6.jpg)

# Start firmware update

Thedualimageformationtobeused forfirmware updateis displayed as follows.To configureImage tobebooted from upon Reset, choose 'Dual Image Configuration' under Maintenance.

Current Active Image

Image to be Undated

Inactive Image

![The image displays a blurry, dark grey or black downward-pointing chevron or triangle shape centered on a white background. There is no text visible in the image.](.axe-7220sr-50m-22810-1000-10/d07588e78b5e055622c5a3a22a3242b2650551a05d2d1722a4853c8c2a63744c.jpg)

Preserve all Configuration.This willpreserve allthe configuration settings during thefrmware update-irrespective of the individual items marked as preserve/overwrite in the table below.

All configurationitems below willbe preserved as default during the restore configuration operation. Click "Edit Preserve

<table><tr><td>S.No</td><td>Preserve Configuration Item</td><td>Preserve Status</td></tr><tr><td>1</td><td>SDR</td><td>Overwrite</td></tr><tr><td>2</td><td>FRU</td><td>Overwrite</td></tr><tr><td>3</td><td>SEL</td><td>Overwrite</td></tr><tr><td>4</td><td>IPMI</td><td>Overwrite</td></tr><tr><td>5</td><td>NETWORK</td><td>Overwrite</td></tr><tr><td>6</td><td>NTP</td><td>Overwrite</td></tr><tr><td>7</td><td>SNMP</td><td>Overwrite</td></tr><tr><td>8</td><td>SSH</td><td>Overwrite</td></tr><tr><td>9</td><td>KVM</td><td>Overwrite</td></tr><tr><td>10</td><td>AUTHENTICATION</td><td>Overwrite</td></tr><tr><td>11</td><td>SYSLOG</td><td>Overwrite</td></tr><tr><td>12</td><td>WEB</td><td>Overwrite</td></tr><tr><td>13</td><td>EXTLOG</td><td>Overwrite</td></tr><tr><td>14</td><td>REDFISH</td><td>Overwrite</td></tr></table>

# Proceed to Flash

BOOT,and APP components of Firmware.

3. Select an Image (Inactive Image, Image 1, Image 2 or Both Image) from Image to be Updated drop-down list. The selected image will be getting flashed.

• Image to be Updated: To update an Image (Inactive, Image 1, Image 2 or Both) to be flashed. If You select an Inactive image, the Inactive image will be flashed. If you select both images, then Both Image 1 and Image 2 will be flashed with uploaded image file.
• reboot the device after update: This option is used to reboot the device after the firmware update.

![Protocol Type: HTTPS\nThe dual image formation to be used for firmware update is displayed as follows. To configure Image to be booted from upon Reset, choose 'Dual Image Configuration' under Maintenance.\nCurrent Active Image Image-1\nImage to be Updated\nInactive Image\nInactive Image\nImage 1\nImage 2\nBoth Images](.axe-7220sr-50m-22810-1000-10/84c5a3d6b652686cd10861a187c05bc71f580819f89c790dc735783bf875d3cd.jpg)

4. Click Preserve all Configuration to preserve all configuration.

• Preserve all Configuration: To preserve all configuration.
• Edit Preserve Configuration: To modify the Preserve status settings.

5. Click Proceed to Flash, it will prompt you with the warning message. Click Ok to start the Firmware update.

# The Dual Firmware Update undergoes the following steps:

a) Closing all active client requests
b) Preparing Device for Firmware Upgrade
c) Uploading Firmware Image
d) Verifying Firmware Image:

In Section Based Firmware Update, you can configure the firmware image for section based flashing. Check the required sections and click Proceed to update the firmware.

If flashing is required for all images, select the option Full Flash.

If you select Version Compare Flash option from web, the current and uploaded module versions, FMHlocation, size will be compared.

• If the modules differ in size and location, proceed with force firmware upgrade.

If all the module versions are same, restart BMC by saying all the module versions are similar.

If only few module versions are differ, those modules will be flashed.

Section Based Firmware Update

![The image displays three white squares arranged horizontally side-by-side. A thin black horizontal line runs across the middle of the image, passing through the center of each square. The squares are outlined with thin black borders.](.axe-7220sr-50m-22810-1000-10/0c24b531200bedd79f3cba4a2037304c54afb06f05433fd33ec85f01e4d76db0.jpg)
Version Compare Flash

![The image displays a simple geometric diagram consisting of a horizontal rectangle divided into three equal vertical sections. Two vertical black lines separate the sections, creating three adjacent white rectangular spaces arranged side-by-side. There is no text visible in the image.](.axe-7220sr-50m-22810-1000-10/9b291af4d11f683f565d578e4a53bc682b6e1e15f1f493fe78f8004a0f73e204.jpg)
Full Flash

<table><tr><td>Section Name</td><td>Image-1 Version</td><td>Image-2 Version</td><td>Uploaded version</td><td>Upgradable/Non-Upgradable</td></tr><tr><td>boot</td><td>13.5.000000</td><td>13.5.000000</td><td>13.5.000000</td><td></td></tr><tr><td>conf</td><td>13.5.000000</td><td>13.5.000000</td><td>13.5.000000</td><td></td></tr><tr><td>root</td><td>13.5.000000</td><td>13.5.000000</td><td>13.5.000000</td><td></td></tr><tr><td>osimage</td><td>13.5.000000</td><td>13.5.000000</td><td>13.5.000000</td><td></td></tr><tr><td>www</td><td>13.5.000000</td><td>13.5.000000</td><td>13.5.000000</td><td></td></tr><tr><td>extlog</td><td>13.5.000000</td><td>13.5.000000</td><td>13.5.000000</td><td></td></tr><tr><td>extlog</td><td>13.5.000000</td><td>0.0.</td><td>13.5.000000</td><td></td></tr><tr><td>bootlogo</td><td>1.0.000000</td><td>1.0.000000</td><td>1.0.000000</td><td></td></tr><tr><td>arcity</td><td>13.5.010003</td><td>13.5.010002</td><td>13.5.010003</td><td></td></tr></table>

e) Flashing Firmware Image
f) Resetting the image

# 6.2.8.1.2 BIOS Update

This wizard takes you through the process of BIOS firmware upgradation.

To perform BIOS Firmware Update operation, click Maintenance -> Firmware Update.

![Firmware Update\nNote:\nFollowing are the Firmware update methods and components supported in this page.\n• Dual Firmware update.\n• HPM Firmware update supports the following components.\n    ○ BOOT and APP\n    ○ BIOS\n• BIOS Firmware update.\n\nSelect Firmware Image\nMECS-7120_1110.BIN\n\nStart firmware update\n\nPreparing to flash...\n\nProceed\n\nWARNING: Please note that after entering the update mode, the widgets, other web pages and services will not work. All the open widgets will be automatically closed. If the upgradation is cancelled in the middle of the wizard, the device will be reset only for BMC BOOT, and APP components of Firmware.](.axe-7220sr-50m-22810-1000-10/f1cdd674967d2e76dbeee204011b5eab167f6a4a0408631619411f35c4c04170.jpg)

# Procedure

1. Click Browse to select BIOS Firmware Image.
Note: Firmware update wizard will detect .bin and .bin\_enc extensions, and validate as BIOS firmware image.
2. Click Start firmware update to load the BIOS firmware image information.
3. Click Proceed, it will prompt you with the warning message. Click OK to start the firmware update.

172.20.2.12 says

Are you sure you want to flash?

![This image displays two horizontal buttons. On the left is a blue button with the white text 'OK'. On the right is a white button with the black text 'Cancel'.](.axe-7220sr-50m-22810-1000-10/436b2865f8f96231d269e155f4058232df34202321c24be2a32b2b819cb2ce52.jpg)

4. Select the components from the list to flash. BIOS is mandatory, ME and NVRAM are optional.

# Firmware Update

![The image displays a single, centered graphic which is a green circle containing a white question mark. The entire image is blurry and out of focus.](.axe-7220sr-50m-22810-1000-10/1a024f59842f4be5c23353394a5f0d32579e8e6838be1d06308bc52e05bc97ca.jpg)

#

Select Firmware Image

MECS-7120\_1110.BIN

![A white icon on a blue background featuring a stack of three documents or folders followed by five dots.](.axe-7220sr-50m-22810-1000-10/995f2aa2a409a18f6346aaeaa48d965373a1a47ab22dab4e646d21feff35da94.jpg)

#

List of Components

<table><tr><td>#</td><td>Component Name</td><td>Existing Version</td><td>Uploaded Version</td><td>Upgrade</td><td>Progress</td></tr><tr><td>1</td><td>BIOS</td><td></td><td>2280811</td><td></td><td>In progress...</td></tr><tr><td>2</td><td>ME</td><td></td><td></td><td></td><td></td></tr><tr><td>3</td><td>NVRAM</td><td></td><td></td><td></td><td></td></tr><tr><td colspan="2">Proceed to flash image</td><td>Cancel</td><td></td><td></td><td></td></tr><tr><td colspan="6">Uploading 100%</td></tr></table>

WARNING: Please note that after entering the update mode,the widgets, other web pages and services middle of the wizard,the device willbe reset only for BMC BOOT, and APP components of Firmware.

# 5. Click Proceed to flash image, it will prompt you with the selection message. Click Cancel, the update will be cancelled.

172.20.2.12 says

Are you sure the BlOS upgrade takes effect immediately? If yes, BMC will power off and power on the chassis after flash update. If no, the BlOS upgrade will take effect when the chassis is powered off.

OK

Cancel

Click OK: Update the device immediately, the chassis will be powered cycle. Once the BIOS firmware update is completed, it will prompt you with the success message. Click OK to complete the process.

172.20.2.12 says

The device has been updated successfully.

OK

Click Cancel: Update the device when the chassis is powered off. It will prompt you with the notification message. Click OK to complete the process.

172.20.2.12 says

The BlOS upgrade will take effect when the chassis is powered off.

# 6.2.8.1.3 HPM Firmware Update – CPLD/BIOS

To perform HPM Firmware Update operation, click Maintenance -> Firmware Update from the menu bar.

Note: For BIOS or CPLD firmware update, it is required to hash its uploaded image via creating HPM image utility.

# Create HPM Image

```txt
./CreateHPMImage create hpmimage.conf
```

CreateHPMImage is the creating HPM image utility from AMI.

Sample of hpmimage.conf
```ini
[GLOBAL]

DeviceID = 0x20 ;1B Device ID as per IPMI

ManufacturerID = 0x005f13 ;3B Manufacturer ID as per IPMI

ProductID = 0x7120 ;2B Product ID

HPMImage = /home/bmc/outputjbc_02b4.hpm ;Path & Filename of final output HPM Image

[CPLD] ;Component Type: BIOS, CPLD

UpgradeActionType = 0x02 ;1B Upgrade Action Type: 0x02 = Upload, 0x03 - 0xFF =
Reserved

FwVersionMajor = 0x02 ;1B This component's Major Version

FwVersionMinor = 0x04 ;1B This component's Minor Version

FwVersionAux = 0x02200000 ;4B This component's Aux Version

FwDescription = "cpld" ;21B Firmware Description String to be used

FwData = /home/bmc/cpld_02b4.jbc ;Path & Filename of Component's Image

SectionFlash = 0x0 ;For Section based flashing of the particular component 0 -
disabled 1 - enabled
```

Note: The CPLD Image should be a .jbc file and enable the option "Enable real-time ISP to allow background programming when available".

Enablereal-time ISPtoalowbackground programming when available

# Procedure for CPLD Firmware Update

1. Select HPM format of CPLD supported image to perform the CPLD Firmware Update.
2. Click Start firmware update to load the Firmware Update information. Once the image is successfully uploaded, the uploaded image information such as Component Name, Existing Version, Uploaded Version and Upgrade will be displayed as shown in the screenshot below. In addition, all the CPLD devices information such as Name, Interface, Interface Number, ID code and Firmware Version will be displayed as well. User can select the device that needs to be updated.

#

Select Firmware Image

outputjbc\_02b4.hpm

![This image displays a white icon of two overlapping file folders followed by a horizontal ellipsis (three dots) on a blue background.](.axe-7220sr-50m-22810-1000-10/6154a0e7bc9ba1fba3ec1ebb048527782d0079dac9835faaaf5d17573156f6b9.jpg)

Start firmware update

#

![The image displays a blue square containing a centered white checkmark.](.axe-7220sr-50m-22810-1000-10/80c5d5ecb5e4bfc3ee48798e46647140ced3743e491f90d25cef6c4e9aea7af1.jpg)

List of Components

<table><tr><td>#</td><td>Component Name</td><td>Existing Version</td><td>Uploaded Version</td><td>Upgrade</td></tr><tr><td>1</td><td>CPLD</td><td>0.0.0</td><td>2.4.35651584</td><td>[0xxt]</td></tr></table>

List of CPLD devices

<table><tr><td>Name</td><td>Interface</td><td>Interface Number</td><td>ID Code</td><td>Firmware Version</td></tr><tr><td>ALTERA 10M50DA CPLD</td><td>JTAG</td><td>0x0</td><td>0x31050dd</td><td>0x65bba5&lt;img src="images/e19cff9b00374a6fca7d7558fbd90c30fe9348e8f4207838bd68a2d2bd3e7e04.jpg"/&gt;</td></tr></table>

Proceed

3. Click Proceed, it will prompt you with the warning message. Click OK to start the firmware update.

172.20.2.18 says

Are you sure you want to flash?

OK

Cancel

If a CPLD firmware has been uploaded, it will prompt you with the selection message. Click Cancel, the update will be cancelled.

# 172.20.2.18 says

A new firmware has been upload. Are you sure to force update?

OK

Cancel

# A sample screenshot is displayed below.

![Note:\nFollowing are the Firmware update methods and components supported in this page.\n• Dual Firmware update.\n• HPM Firmware update supports the following components.\n    ○ BOOT and APP\n    ○ BIOS\n    ○ CPLD\n• BIOS Firmware update\n\nSelect Firmware Image\noutputjbc_02b4.hpm\n\nStart firmware update\n\nPreparing to flash...\n\nUpdate All\n\nList of Components\n# Component Name Existing Version Uploaded Version Upgrade Progress\n1 CPLD 0.0.0 2.4.35651584 In progress...\n\nList of CPLD devices\nName Interface Interface Number ID Code Firmware Version\nALTERA 10M50DA CPLD JTAG 0x0 0x31050dd 0x65bba5\nProceed\n\nUpgrade (50%)](.axe-7220sr-50m-22810-1000-10/a8c2a9f195e667cfde61bf71858dd2b3443f7b27bc420ca1e1784d4ca013314e.jpg)

4. Once the CPLD Firmware Update process is completed, an alert message will be displayed as shown in the screenshot below.

# 172.20.2.18 says

The device has been updated successfully.

OK

# 6.2.8.1.4 PLDM Firmware Update

PLDM is the Platform Level Data Model Specification of DMTF. DSP0267 describes firmware update procedure for Firmware Device (FD), which is a component-based firmware update process. And the update agent (UA, the YAFU tool used to perform the firmware update) can update the component’s firmware individually.

To perform PLDM Firmware Update process, click Maintenance -> Firmware Update from the menu bar. The PLDM Firmware Update will be displayed as part of the Help content. A sample screenshot of Firmware Update page is displayed below.

# Firmware Update

![The image displays a blurry, light green circle containing a white question mark symbol, set against a plain white background.](.axe-7220sr-50m-22810-1000-10/801b464d45b53ebe68234370d77f249cf0935f5abe7c9c33a418b7141353684b.jpg)

# Note:

# Select Firmware Image

E810\_4p60.pldm

![The image displays a white folder icon on the left side of a blue background. To the right of the folder icon, there are three horizontal dots, suggesting a menu or additional options. The graphic appears to be a cropped section of a digital interface, possibly a file explorer or navigation bar.](.axe-7220sr-50m-22810-1000-10/b91cfff064bdc5cc8be7bef90ed518a44830ce823541fb233b94bce0dc6c9c15.jpg)

# Startfirmware update

WARNING:Please note that after entering the update mode,the widgets,other web pages and services will not work. All the open widgets will be automatically closed. If for BMC BOOT,and APP components of Firmware.

# Procedure

1. Select any vendor PLDM supported image to perform PLDM Firmware Update.
2. Click Start firmware update to proceed PLDM firmware update process. Click OK to start the firmware update.

172.20.2.18 says

Are you sure you want to flash PLDM Image?

OK

Cancel

3. Once the image is successfully uploaded, the uploaded image information such as EID, Uploaded Version, Existing Version and Upgrade will be displayed as shown below.

Note: SignImage Public Key is feature based option. If encrypted Signimage feature is

enabled, then support to Upload a public.pem key info option will be available.

Firmware Update

![Note:\nFollowing are the Firmware update methods and components supported in this page.\n• Dual Firmware update.\n• HPM Firmware update supports the following components.\n    ○ BOOT and APP\n    ○ BIOS\n    ○ CPLD\n• PLDM Firmware update.\n• BIOS Firmware update\n\nSelect Firmware Image\nE810_4p60.pldm\n\nStart firmware update\n\nPreparing to flash...\nPlease note that PLDM Firmware Update process time will depend on vendor specific.So it may take some time to complete Firmware Update.\n\n#	EID	Medium	Uploaded Version	Existing Version	Upgrade	Progress\n1	9	PCIe	4.60 (0x8001E8C9)	4.50 (0x8001D8CE)\nProceed	Cancel\n\nUploading 100%\n\nWARNING:Please note that after entering the update mode, the widgets, other web pages and services will not work. All the open widgets will be automatically closed. If the upgradation is cancelled in the middle of the wizard, the device will be reset only for BMC BOOT,and APP components of Firmware.](.axe-7220sr-50m-22810-1000-10/270a92b2816bb3055715fb6e43a4ccc83ba3255ca105e70661ff4952e0bd56ab.jpg)

4. Click Proceed to start flashing procedure. Or, click Cancel to cancel the ongoing firmware update process and reload the current page. A sample screenshot is displayed below.

![Firmware Update\nNote:\nFollowing are the Firmware update methods and components supported in this page.\n• Dual Firmware update.\n• HPM Firmware update supports the following components.\n    ○ BOOT and APP\n    ○ BIOS\n    ○ CPLD\n• PLDM Firmware update.\n• BIOS Firmware update\nSelect Firmware Image\nE810_4p60.pldm\nStart firmware update\nProcessing...\nPreparing to flash...\nPlease note that PLDM Firmware Update process time will depend on vendor specific.So it may take some time to complete Firmware Update.\n# EID Medium Uploaded Version Existing Version Upgrade Progress\n1 9 PCIe 4.60 (0x8001E8C9) 4.50 (0x8001D8CE) In progress... 0%\nProceed Cancel\nUploading 100%\nWARNING:Please note that after entering the update mode, the widgets, other web pages and services will not work. All the open widgets will be automatically closed. If the upgradation is cancelled in the middle of the wizard,\nthe device will be reset only for BMC BOOT,and APP components of Firmware.](.axe-7220sr-50m-22810-1000-10/b7df559beb1c81fc2ffb8c77189a0db27fc10499858bd08ffbde1b0be93151b5.jpg)

5. Once the PLDM Firmware Update process is completed, an alert message will be displayed as shown in the screenshot below.

![172.20.2.18 says\nPLDM Firmware Update is completed. Please check the activation method for each selected device.\nOK\nNote:\nFollowing are the Firmware update methods and components supported in this page.\n• Dual Firmware update.\n• HPM Firmware update supports the following components.\n    ○ BOOT and APP\n    ○ BIOS\n    ○ CPLD\n• PLDM Firmware update.\n• BIOS Firmware update\nSelect Firmware Image\nE810_4p60.pldm\nStart firmware update\nProcessing...\nPreparing to flash...\nPlease note that PLDM Firmware Update process time will depend on vendor specific.So it may take some time to complete Firmware Update.\n# EID Medium Uploaded Version Existing Version Upgrade Progress\n1 9 PCIe 4.60 (0x8001E8C9) 4.50 (0x8001D8CE) In progress... 52%\nProceed Cancel\nUploading 100%](.axe-7220sr-50m-22810-1000-10/4b0a3c5b0f757e9d23f9f03d83ed6015d78816d51d2497a70915f1574a700324.jpg)

6. Clicking OK in alert message, will reload the current page.

# 6.2.8.2 Firmware Configuration 6.2.8.2.1 Dual Image Configuration

This page is used to configure the dual image information. Dual Image support feature is helpful to store two firmware images on two SPI flash, and boot any of the image according to users request.

The running firmware is responsible for setting the Boot Selector options and Firmware Upload Selector options.

To open Dual Image Configuration, click Maintenance -> Dual Image Configuration from the menu bar. A sample screenshot of Dual Image Configuration page is shown below.

![Dual Image configuration\nIMAGE 1\nFirmware Version 13.05.10003\nState Active\n✓ Image to be booted from upon reset\nIMAGE 2\nFirmware Version 13.05.10002\nState stand-by\n○ Image to be booted from upon reset\n○ Higher firmware version\n○ Lower firmware version\n○ Most recently updated firmware\n○ Least recently updated firmware\nSave](.axe-7220sr-50m-22810-1000-10/4bdb2cc8544e7a237dc2a9c0c02b0f44627ba41eca9b3a239c727123fcea22e6.jpg)

The various options of Dual Image Configuration are given below.

Firmware Version: Displays the firmware version of both images.

State: Displays the current state of both images.

Image to be booted from upon reset: This option is to boot particular image (either 1 or 2) in the next boot up process.

Higher firmware version: This option is to boot higher firmware version image among the dual images in the next boot up process.

Lower firmware version: This option is to boot lower firmware version image among the dual images in the next boot up process.

Most recently updated firmware: This option is to boot most recently updated firmware image among the dual images in the next boot up process.

Least recently updated firmware: This option is to boot least recently updated firmware image among the dual images in the next boot up process.

# Procedure

1. Select the required image to be configured or the required option for Image setting.

2. Click Save to save the changes.

# Fail Safe Booting Configuration:

Hardware based fail safe boot support: This feature supports switching to secondary image as failsafe using hardware configurations. Using this feature, the user can boot into secondary image, even though primary uboot is crashed. Please verify whether SOC supports this feature.

Software FailSafe Boot: Legacy AMI dual image support. This feature uses common UBOOT which switches between 2 different images based on user requirement. This feature does not requires a special hardware support.

# 6.2.9 One-Click Log Collection

The One-Click Log Collection feature enables users to download essential BMC information data for detailed analysis of BMC status or issue identification.

To open the One-Click Log Collection, click One-click Log collection from the menu bar. A sample screenshot of Event Log page is shown below.

One-click Log Collection

![A horizontal rectangular button with a green background featuring a white download icon on the left and the text 'Download' in white on the right.](.axe-7220sr-50m-22810-1000-10/04e143cd958b2ad6a73cd4f5ebdc74ab64d70f3ab1a6a517cb463ec98e1c7833.jpg)

Click the "Download" button to automatically download the Log to the system.

The log package is named：

One-Click\_Collection\_Log\_[time].zip

Inside the zip file, you will find the following folders:

• conf: Configuration files
• tmp: Temporary files
• var: Variable files

# 6.2.10 Firmware and Hardware versions

To get the version info of BMC, BIOS, CPLD and hardware, please refer to home page, upleft corner.

For example:

![MECS-7120\nVersion Information\nBMC: 1.4.dd360de7\nBIOS: 1.2.10\nCPLD: 02b4\nHW: A2 SKU: 1U\nMar 15 2024 05:58:02 UTC\nHost Online](.axe-7220sr-50m-22810-1000-10/dd4b91e7d221f9f5ea988312a5182a99290d6505bb25880568d545550aaa4b09.jpg)

# 6.2.11 PLDM

# 6.2.1.11.1 PLDM Sensor Reading

This page displays all the PLDM Numeric/State sensor-related information. To open the Sensor Readings page, click PLDM from the main menu, and then click Sensor Reading from the PLDM page. A sample screenshot is displayed below.

Show Entity Association

BAll numeric sensors are normal

<table><tr><td>Containing Entity</td><td>Physical/Logical</td><td>Entity</td><td>State Set</td><td>Present State</td><td>Previous State</td><td>Event State</td></tr><tr><td>Entity(0)</td><td>Physical</td><td>Add-in Card 1</td><td>Health StateConfiguration StateChanged ConfigurationThermal Trip</td><td>NormalValid ConfigurationNormalNormal</td><td>UnknownUnknownUnknownUnknown</td><td>NormalValid ConfigurationNormalNormal</td></tr><tr><td>Physical Add-in Card 1</td><td>Physical</td><td>Network Controller 1</td><td>Health StateConfiguration StateChanged ConfigurationThermal TripVersion</td><td>NormalValid ConfigurationNormalNormalNormal</td><td>UnknownUnknownConfiguration ChangeDetectedUnknownUnknown</td><td>NormalValid ConfigurationNormalNormalNormal</td></tr><tr><td>Physical Network Controller 1</td><td>Physical</td><td>Ethernet 1</td><td>Link State</td><td>Disconnected</td><td>Unknown</td><td>Disconnected</td></tr><tr><td>Physical Network Controller 1</td><td>Physical</td><td>Ethernet 2</td><td>Link State</td><td>Disconnected</td><td>Unknown</td><td>Disconnected</td></tr><tr><td>Physical Connector 1</td><td>Physical</td><td>SFP28 (SFF-8402) 1</td><td>Presence</td><td>Not Present</td><td>Unknown</td><td>Not Present</td></tr><tr><td>Physical Connector 2</td><td>Physical</td><td>SFP28 (SFF-8402) 1</td><td>Presence</td><td>Not Present</td><td>Unknown</td><td>Not Present</td></tr></table>

<table><tr><td>Containing Entity</td><td>Physical/Logical</td><td>Entity</td><td>Reading</td><td>Present State</td><td>Previous State</td><td>Event State</td><td>Behavior</td></tr><tr><td>Physical Network Controller 1</td><td>Physical</td><td>Ethernet 1</td><td>0 Bits</td><td>Normal</td><td>Normal</td><td>Normal</td><td></td></tr><tr><td>Physical Network Controller 1</td><td>Physical</td><td>Ethernet 2</td><td>0 Bits</td><td>Normal</td><td>Normal</td><td>Normal</td><td></td></tr><tr><td>Physical Add-in Card 1</td><td>Physical</td><td>Network Controller 1</td><td>39 Degrees C</td><td>Normal</td><td>Unknown</td><td>Normal</td><td></td></tr></table>

This PLDM Sensor Readings page contains the following information.

 Severe Sensors: These includes the Numeric Sensors that are not in Normal State.
 State Sensors: It includes detailed information about Containing Entity, Physical/Logical, Entity, State Set, Present State, Previous State, and Event State.
 Normal Numeric Sensors: It includes detailed information of Containing Entity, Physical/Logical, Entity, Reading, Present State, Previous State, Event State and Live Readings.
 Other Operational State Sensors: It contains the Numeric/State Sensor with Operation State that are not in the Enabled State.
 Show Entity Association: By clicking this button, it displays a model view to show an Entity Association Block Diagram as shown in the screenshot below.

Entity Association Block Diagram

System

Physical Add-in Card 1

Physical Connector 1

Physical SFP28 (SFF-8402) 1

Physical Cable 1

Physical Connector 2

Physical SFP28 (SFF-8402) 1

Physical Cable 1

Physical Network Controller 1

Physical Ethernet1

Physical Ethernet 2

Physical Communication Channel1

Physical Communication Channel2

# 6.2.1.11.2 PLDM FRU Information

The PLDM FRU page displays all the PLDM FRU Record.

To open the FRU page, click PLDM from the main menu and then click on FRU Information icon. A sample screenshot of PLDM FRU is displayed below.

![PLDM FRU PLDM Field Replaceable Units\nSelect the PLDM Device Endpoint ID(9)\nAvailable FRU Record (1)\nFRU Record Set ID 1\nFRU Record Type General FRU Record\nFRU Data Version 1.0\nFRU Table Maximum Size 0\nFRU Record (4)\nSerial Number 000100000000\nManufacturer Intel(R) Corporation\nName Intel(R) Ethernet Controller E810-XXVAM2\nVendor IANA 0](.axe-7220sr-50m-22810-1000-10/945421c60d94bc9b90d96ba1375cb9a022dc90c3e832cfa1d4aec30530d19a46.jpg)

The PLDM Field Replaceable Unit (FRU) page contains the following information.

 Available FRU Record - It contains the information like FRU Record Set ID, FRU Record Type, FRU Data Version, and FRU table maximum size.
 FRU Record - It contains the detail information of selected FRU Record Set ID.

# 6.2.1.11.3 PLDM Event Log

This PLDM Event Log page displays the details of PLDM event log.

To open the event log page, click PLDM from the main menu and then click on Event Log icon. A sample screenshot of PLDM Event Log is displayed below.

<table><tr><td>index</td><td>Type</td><td>Data Length</td><td>Timestamp</td><td>Format Version</td><td>TID</td><td>Event Class</td><td>Event Data</td></tr></table>

 index: It shows the index number.
 Type: This field displays the type of entry.
 Data Length: The size in bytes of the entryData field.
 Timestamp: This value corresponds to a 40-bit unsigned integer that represents the number of seconds since midnight UTC of January 1, 1970 (not counting leap seconds).
 Format Version: It shows the version of the event format.
 TID: It displays Terminus ID for the terminus that originated the event message.
 Event Class: The class of event being sent.
 Event Data: Event data based on the event class (display in hexadecimal).

# 6.3 IPMI

Intelligent Platform Management Interface (IPMI) is a standardized interface used for managing a computer system and monitoring its operation. It provides a set of specifications for hardware-based management, independent of the operating system.

# 6.3.1 Overview of ipmitool

The ipmitool is a command-line utility that interfaces with the IPMI system. It allows administrators to execute a range of IPMI commands to manage and monitor servers. This tool is essential for system management, providing an interface to the IPMI functionalities of the server's BMC.

# 6.3.1.1 General Usage of ipmitool

The ipmitool allows for a range of operations through its command-line interface. The general syntax includes various parameters for network communication and authentication.

Common Parameters:

-H or --hostname: Hostname or IP address of the target server (for network interfaces).
-U or --user: Username for login.
-P or --password: Password for login (it's recommended to input interactively for security).

<table><tr><td>Parameter</td><td>Alias</td><td>Description</td></tr><tr><td>-H</td><td>--hostname</td><td>Hostname or IP address of the target server (for network interfaces).</td></tr><tr><td>-U</td><td>--user</td><td>Username for login.</td></tr><tr><td>-P</td><td>--password</td><td>Password for login (recommended to be input interactively for security).</td></tr></table>

# 6.3.1.2 Specific Interface Options

# LAN Interface (lan)

Usage: ipmitool -I lan -H [hostname] -U [username] -P [password] [command]

Note: The LAN interface is suitable for local communication with IPMI. For remote management capabilities, the LANplus interface should be used.

# Example:

```txt
~ # ipmitool -I lan -H 127.0.0.1 -U admin -P admin.123 mc info
IOCTL to get IP failed: -1
Device ID : 32
Device Revision : 1
Firmware Revision : 1.03
IPMI Version : 2.0
Manufacturer ID : 24339
Manufacturer Name : ADLINK Technology Inc.
Product ID : 28960 (0x7120)
Product Name : Unknown (0x7120)
Device Available : yes
Provides Device SDRs : yes
Additional Device Support :
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
IPMB Event Generator
Chassis Device
Aux Firmware Rev Info :
0x11
0x0d
0x10
0xb9
```

# LANplus Interface (lanplus)

Usage: ipmitool -I lanplus -H [hostname] -U [username] -P [password] [command] Enhanced LAN interface with better encryption and additional features for secure remote communication.

# Example:

```txt
root@adlink-Default-string:/home/adlink# ipmitool -I lanplus -H 172.20.2.137 -U admin -P admin.123 mc info
Device ID : 32
Device Revision : 1
Firmware Revision : 1.03
IPMI Version : 2.0
Manufacturer ID : 24339
Manufacturer Name : ADLINK Technology Inc.
Product ID : 28960 (0x7120)
Product Name : Unknown (0x7120)
Device Available : yes
Provides Device SDRs : yes
Additional Device Support :
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
IPMB Event Generator
Chassis Device
Aux Firmware Rev Info :
0x11
0x0d
0x10
0xb9
```

# KCS Interface (kcs)

Usage: ipmitool [command]

KCS (Keyboard Controller Style) is used for communication between the x86 segment and the BMC directly, without needing the -I parameter. It's used for local, direct communication with BMC.

# Example:

```txt
root@adlink-Default-string:/home/adlink#
root@adlink-Default-string:/home/adlink# ipmitool mc info
Device ID : 32
Device Revision : 1
Firmware Revision : 1.03
IPMI Version : 2.0
Manufacturer ID : 24339
Manufacturer Name : ADLINK Technology Inc.
Product ID : 28960 (0x7120)
Product Name : Unknown (0x7120)
Device Available : yes
Provides Device SDRs : yes
Additional Device Support :
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
IPMB Event Generator
Chassis Device
Aux Firmware Rev Info :
0x11
0x0d
0x10
0xb9
root@adlink-Default-string:/home/adlink#
```

# 6.3.2 ipmitool Command Introduction

This section is dedicated to introducing and explaining a variety of ipmitool commands, with detailed descriptions of their specific uses.

# 6.3.2.1 Fan Control

The ipmitool provides capabilities to manage and monitor fan control settings, including reading the current fan level and switching between manual and automatic control modes.

# Get Fan Level

To retrieve the current fan level, the following specific OEM command is used for systems:

Command:

<table><tr><td>(NetFn = 2Eh, Cmd = 81h)</td></tr><tr><td>ipmitool raw 0x2e 0x81 0x13 0x5f 0x00 &lt;Fan Number&gt;</td></tr></table>

<table><tr><td rowspan="8">Request DataResponse Data</td><td>Byte</td><td>Data Field</td></tr><tr><td>1~3</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr><tr><td>4</td><td>Fan Number: Fan Tray Site Number start from 0.</td></tr><tr><td>1</td><td>Completion Code</td></tr><tr><td>2~4</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr><tr><td>5</td><td>The current mode of the fan:00h: Fan in local (automatic) control mode.01h: Fan level in override (manual) control mode with a fixed speed.02h: Minimum fan level in override control mode.Other values are invalid.</td></tr><tr><td>6</td><td>Minimum FAN level, value range (1~max)</td></tr><tr><td>7</td><td>Current FAN level, value range (1~max)</td></tr></table>

# Example:

![root@adlink-MECS-7120:/# ipmitool raw 0x2e 0x81 0x13 0x5f 0x00 1\n13 5f 00 00 01 01\nroot@adlink-MECS-7120:/#\nroot@adlink-MECS-7120:/# ipmitool raw 0x2e 0x81 0x13 0x5f 0x00 0\n13 5f 00 00 01 01\nCmd Manufacturer ID Fan num](.axe-7220sr-50m-22810-1000-10/792330424de757e4a2f9729777bb6dd3c14e9d841dd00a55f260fd4e781cbb4c.jpg)

Manufacturer ID Fan control mode mini fan level Current fan level

# Set Fan Level

The ipmitool is the ability to set the fan level, allowing administrators to manually control the speed of the fans within their server system.

# Command:

(NetFn = 2Eh, Cmd = 80h)

ipmitool raw 0x2e 0x80 0x13 0x5f 0x00 &lt;Fan Number&gt; &lt;Fan Control Mode&gt; [&lt;Fan Level&gt;]

<table><tr><td rowspan="4">Request Data</td><td>Byte</td><td>Data Field</td></tr><tr><td>1~3</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr><tr><td>4</td><td>Fan Number: Fan Tray Site Number start from 0.FFh: Control all fans.</td></tr><tr><td>5</td><td>Fan Control Mode: Set the desired control mode for the fan.00h: Fan in local (automatic) control mode.01h: Fan level in override (manual) control mode with a fixed speed.02h: Minimum fan level in override control mode.</td></tr><tr><td rowspan="3">Response Data</td><td>6</td><td>Fan Level: FAN level to set, value range (1~max).Ignored when byte 5 is set to 00h.Fix the current FAN level when byte 5 is set to 01h.Fix the mini FAN level when byte 5 is set to 02h.</td></tr><tr><td>1</td><td>Completion Code</td></tr><tr><td>2~4</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr></table>

# Example:

<table><tr><td>root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x81 0x13 0x5f 0x00 013 5f 00 00 01 01</td></tr><tr><td>root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x80 0x13 0x5f 0x00 0 0x01 313 5f 00</td></tr><tr><td>root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x81 0x13 0x5f 0x00 013 5f 00 01 00 03</td></tr><tr><td>root@adlink-Default-string:/home/adlink#</td></tr><tr><td>root@adlink-Default-string:/home/adlink#</td></tr><tr><td>root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x80 0x13 0x5f 0x00 0 0x0013 5f 00</td></tr><tr><td>root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x81 0x13 0x5f 0x00 013 5f 00 00 01 01</td></tr><tr><td>root@adlink-Default-string:/home/adlink#</td></tr><tr><td>root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x80 0x13 0x5f 0x00 0 0x02 413 5f 00</td></tr><tr><td>root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x81 0x13 0x5f 0x00 013 5f 00 02 04 04</td></tr><tr><td>root@adlink-Default-string:/home/adlink#</td></tr><tr><td>root@adlink-Default-string:/home/adlink#</td></tr><tr><td>root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x80 0x13 0x5f 0x00 0 0x0013 5f 00</td></tr><tr><td>root@adlink-Default-string: /home/adlink# ipmitool raw 0x2e 0x81 0x13 0x5f 0x00 013 5f 00 00 01 04</td></tr><tr><td>root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x81 0x13 0x5f 0x00 013 5f 00 00 01 01</td></tr></table>

Setting Fan to Manual Mode

control Mode

Setting Minimum Fan Level Mode

# 6.3.2.2 Sensor Information

The ipmitool command is used to retrieve sensor information, allowing system users to monitor various hardware sensors within the server. These sensors can include temperature, voltage, fan speed, and other key operating metrics.

List sensor information using ipmitool command:

# Command:

ipmitool sensor ipmitool sensor list

Return Details:

<table><tr><td>Return Details</td><td>Description</td></tr><tr><td>Sensor Name</td><td>Identifies the sensor.</td></tr><tr><td>Reading</td><td>The current value or status reported by the sensor.</td></tr><tr><td>Units</td><td>The measurement units for the sensor reading.</td></tr><tr><td>Status</td><td>Indicates the operational status of the sensor.</td></tr><tr><td>Lower/Upper Thresholds</td><td>The predefined limits for the sensor values, indicating warning or critical conditions.</td></tr></table>

Example:

<table><tr><td colspan="10">root@adlink-Default-string:/home/adlink# ipmitool sensor list</td></tr><tr><td>P12V_PSU</td><td>12.230</td><td>Volts</td><td>ok</td><td>10.800</td><td>11.160</td><td>11.400</td><td>12.600</td><td>12.840</td><td>13.200</td></tr><tr><td>P12V_AUX</td><td>12.200</td><td>Volts</td><td>ok</td><td>10.800</td><td>11.160</td><td>11.400</td><td>12.600</td><td>12.840</td><td>13.200</td></tr><tr><td>P3V3</td><td>3.315</td><td>Volts</td><td>ok</td><td>2.970</td><td>3.069</td><td>3.135</td><td>3.465</td><td>3.531</td><td>3.630</td></tr><tr><td>P5V</td><td>5.120</td><td>Volts</td><td>ok</td><td>4.500</td><td>4.650</td><td>4.750</td><td>5.250</td><td>5.350</td><td>5.500</td></tr><tr><td>PVNN_PCH_AUX</td><td>0.905</td><td>Volts</td><td>ok</td><td>0.810</td><td>0.837</td><td>0.855</td><td>0.941</td><td>0.963</td><td>0.990</td></tr><tr><td>P1V05_PCH_AUX</td><td>1.057</td><td>Volts</td><td>ok</td><td>0.945</td><td>0.977</td><td>0.998</td><td>1.082</td><td>1.124</td><td>1.155</td></tr><tr><td>P1V8_AUX</td><td>1.816</td><td>Volts</td><td>ok</td><td>1.620</td><td>1.674</td><td>1.728</td><td>1.864</td><td>1.926</td><td>1.980</td></tr><tr><td>P3V_BAT</td><td>2.998</td><td>Volts</td><td>ok</td><td>2.002</td><td>2.302</td><td>2.500</td><td>3.148</td><td>3.208</td><td>3.298</td></tr><tr><td>PVCCIN_CPU</td><td>1.813</td><td>Volts</td><td>ok</td><td>1.441</td><td>1.489</td><td>1.519</td><td>1.891</td><td>1.927</td><td>1.981</td></tr><tr><td>P0V8_E810</td><td>0.822</td><td>Volts</td><td>ok</td><td>0.720</td><td>0.744</td><td>0.760</td><td>na</td><td>na</td><td>0.880</td></tr><tr><td>PVCCINFAON</td><td>1.090</td><td>Volts</td><td>ok</td><td>0.856</td><td>0.900</td><td>0.930</td><td>1.130</td><td>1.150</td><td>1.180</td></tr><tr><td>P3V3_AUX</td><td>3.300</td><td>Volts</td><td>ok</td><td>2.970</td><td>3.069</td><td>3.135</td><td>3.465</td><td>3.531</td><td>3.630</td></tr><tr><td>PVCCFA_EHV_FIVRA</td><td>1.812</td><td>Volts</td><td>ok</td><td>1.620</td><td>1.674</td><td>1.710</td><td>1.890</td><td>1.926</td><td>1.980</td></tr><tr><td>P0V9_E810</td><td>0.888</td><td>Volts</td><td>ok</td><td>0.810</td><td>0.837</td><td>0.855</td><td>0.945</td><td>0.963</td><td>0.990</td></tr><tr><td>PVCCD_HV</td><td>1.124</td><td>Volts</td><td>ok</td><td>0.990</td><td>1.030</td><td>1.050</td><td>1.192</td><td>1.220</td><td>1.270</td></tr><tr><td>P12V_S3_DIMM</td><td>12.060</td><td>Volts</td><td>ok</td><td>10.800</td><td>11.160</td><td>11.400</td><td>12.600</td><td>12.840</td><td>13.200</td></tr><tr><td>PCIE_Outlet_Temp</td><td>27.000</td><td>degrees C</td><td>ok</td><td>na</td><td>na</td><td>na</td><td>55.000</td><td>60.000</td><td>65.000</td></tr><tr><td>CPU_Outlet_Temp</td><td>33.000</td><td>degrees C</td><td>ok</td><td>na</td><td>na</td><td>na</td><td>na</td><td>na</td><td>na</td></tr><tr><td>SYS_Inlet_Temp</td><td>28.000</td><td>degrees C</td><td>ok</td><td>na</td><td>na</td><td>na</td><td>na</td><td>na</td><td>na</td></tr><tr><td>HDD_BP_Temp</td><td>22.000</td><td>degrees C</td><td>ok</td><td>na</td><td>na</td><td>na</td><td>47.000</td><td>51.000</td><td>55.000</td></tr><tr><td>CPU_Temp</td><td>37.000</td><td>degrees C</td><td>ok</td><td>na</td><td>na</td><td>na</td><td>91.000</td><td>95.000</td><td>99.000</td></tr><tr><td>CPU_TJMAX</td><td>97.000</td><td>degrees C</td><td>ok</td><td>na</td><td>na</td><td>na</td><td>na</td><td>na</td><td>na</td></tr><tr><td>PCH_Temp</td><td>31.000</td><td>degrees C</td><td>ok</td><td>na</td><td>na</td><td>na</td><td>na</td><td>na</td><td>na</td></tr><tr><td>DIMM_A1_Temp</td><td>na</td><td>degrees C</td><td>na</td><td>na</td><td>na</td><td>na</td><td>106.000</td><td>116.000</td><td>125.000</td></tr><tr><td>DIMM_B1_Temp</td><td>na</td><td>degrees C</td><td>na</td><td>na</td><td>na</td><td>na</td><td>106.000</td><td>116.000</td><td>125.000</td></tr><tr><td>DIMM_C1_Temp</td><td>na</td><td>degrees C</td><td>na</td><td>na</td><td>na</td><td>na</td><td>106.000</td><td>116.000</td><td>125.000</td></tr><tr><td>DIMM_E1_Temp</td><td>31.000</td><td>degrees C</td><td>ok</td><td>na</td><td>na</td><td>na</td><td>106.000</td><td>116.000</td><td>125.000</td></tr><tr><td>DIMM_G1_Temp</td><td>na</td><td>degrees C</td><td>na</td><td>na</td><td>na</td><td>na</td><td>106.000</td><td>116.000</td><td>125.000</td></tr><tr><td>DIMM_H1_Temp</td><td>na</td><td>degrees C</td><td>na</td><td>na</td><td>na</td><td>na</td><td>106.000</td><td>116.000</td><td>125.000</td></tr><tr><td>ACPI_Power</td><td>0x0</td><td>discrete</td><td>0x0180</td><td>na</td><td>na</td><td>na</td><td>na</td><td>na</td><td>na</td></tr></table>

# Other ipmitool Commands Related to Sensor Information

Below is a table summarizing additional ipmitool commands pertinent to sensor management and monitoring:

<table><tr><td>Command Element</td><td>Description</td></tr><tr><td>ipmitool sdr list</td><td>Lists all Sensor Data Records (SDR) in a compact format.</td></tr><tr><td>ipmitool sensor get</td><td>Retrieves detailed information for a specific sensor.</td></tr><tr><td>ipmitool sensor thresh</td><td>Displays the threshold values for a specific sensor.</td></tr><tr><td>ipmitool sdr enlist all</td><td>Lists all Sensor Data Records (SDR) in an extended format, providing more details.</td></tr><tr><td>ipmitool sensor thresh</td><td>Sets a specific threshold value for a sensor, such as upper or lower limits.</td></tr></table>

# 6.3.2.3 Power Control

Using ipmitool commands, you can effectively control the power mode, check the status of the power supply unit (PSU), and view its output power. This includes viewing and setting PSU redundancy modes.

# 6.3.2.3.1 Redundancy Mode

Changing this mode with ipmitool commands directly affects the Power LED's status. The LED's behavior—solid, blinking, or off—visually indicates the current redundancy setting. For understanding these LED states, refer to 6.2.4 Power LED.

# Get PSU Redundancy Mode

# Command:

(NetFn = 2Eh, Cmd = 59h)

ipmitool raw 0x2e 0x59 0x13 0x5f 0x00 &lt;PSU Number&gt;

<table><tr><td></td><td>Byte</td><td>Data Field</td></tr><tr><td>Request Data</td><td>1~3</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr><tr><td rowspan="4">Response Data</td><td>4</td><td>PSU Number: Start from 1.</td></tr><tr><td>1</td><td>Completion Code</td></tr><tr><td>2~4</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr><tr><td>5</td><td>PSU redundancy mode.</td></tr></table>

# Set PSU Redundancy Mode

# Command:

(NetFn = 2Eh, Cmd = 58h)

ipmitool raw 0x2e 0x58 0x13 0x5f 0x00 &lt;PSU Number&gt; &lt;Redundancy Mode&gt;

<table><tr><td rowspan="4">Request Data</td><td>Byte</td><td>Data Field</td></tr><tr><td>1~3</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr><tr><td>4</td><td>PSU Number.0x1 -&gt; PSU10x2 -&gt; PSU20x3 -&gt; PSU3...0xFE -&gt; PSU2540xFF -&gt; all PSUs are set together.</td></tr><tr><td>5</td><td>Redundancy Mode: Set PSU redundancy mode.0x00: Standard redundancy (default power-on state).0x01: Cold redundancy active.0x02 - 0x05: Various levels of cold standby.0x06 - 0xFF: Reserved for future use or manufacturer-specific modes.</td></tr><tr><td>Response Data</td><td>1</td><td>Completion Code</td></tr></table>

<table><tr><td>Byte</td><td>Data Field</td></tr><tr><td>2~4</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr></table>

# Example:

This example shows using ipmitool to manage PSU redundancy modes in a server. It covers checking PSU statuses, changing their redundancy modes, and seeing how the system responds to these changes.

<table><tr><td>root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x59 0x13 0x5f 0x00 0x01 13 5f 00 00</td><td>ipmitool</td><td>raw</td><td>0x2e</td><td>0x59</td><td>0x13</td><td>0x5f</td><td>0x00</td><td>0x01</td><td rowspan="12">Checking Redundancy Mode of Individual PSUs</td></tr><tr><td colspan="9">root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x59 0x13 0x5f 0x00 0x02</td></tr><tr><td colspan="9">root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x58 0x13 0x5f 0x00 0xff 13 5f 00</td></tr><tr><td colspan="9">root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x59 0x13 0x5f 0x00 0x01 Setting All PSUs to Active Redundancy Mode</td></tr><tr><td colspan="9">root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x59 0x13 0x5f 0x00 0x02</td></tr><tr><td colspan="9">root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x58 0x13 0x5f 0x0O 0x02</td></tr><tr><td colspan="9">root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x59 0x13 0x5f 0x0O 0x01 Setting PSU2 to Cold Redundancy Mode</td></tr><tr><td colspan="9">root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x59 0x13 0x5f 0x0O 0x02</td></tr><tr><td colspan="9">root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x58 0x13 0x5f 0x0O 0x01</td></tr><tr><td colspan="9">root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x59 0x13 0x5f 0x0O 0x01 Attempt to set PSU1 to Redundancy while PSU2 is in Redundancy Mode</td></tr><tr><td colspan="9">root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x59 0x13 0x5f 0x0O 0x02</td></tr><tr><td colspan="9">root@adlink-Default-string:/home/adlink# ipmitool raw 0x2e 0x59 0x13 0x5f 0x0O 0x02</td></tr></table>

# Note:

Both PSUs in redundancy mode is not a valid configuration, the system reverts all PSUs to the default mode.

# 6.3.2.3.2 Power Supply Reading

This section explains two methods to read power consumption data from a server’s PSUs using ipmitool.

Method 1: Using ipmitool sensor list

Refer to 6.13.2 Sensor Information for details on using ipmitool sensor list to read PSU power metrics.

Method 2: Using ipmitool dcmi Command

# Command:

ipmitool dcmi power reading [sample time]

# With sample time

The sample time parameter determines the length of time over which the power readings are averaged or analyzed, which include:

5\_sec, 15\_sec, 30\_sec, 1\_min, 3\_min, 7\_min, 15\_min, 30\_min, and 1\_hour.

# Without sample time

If the sample time parameter is omitted, the command will automatically default to providing power readings that encompass the entire duration from the system's last startup to the present time.

This command is used to get detailed power readings from the server's PSU.

<table><tr><td>Return Details</td><td>Description</td></tr><tr><td>Instantaneous Power Reading</td><td>Shows the current power usage in Watts.</td></tr><tr><td>Minimum During Sampling Period</td><td>The lowest power usage recorded during the period.</td></tr><tr><td>Maximum During Sampling Period</td><td>The highest power usage recorded during the period.</td></tr><tr><td>Average Power Reading Over Sample Period</td><td>Average power usage over the entire period.</td></tr><tr><td>IPMI Timestamp</td><td>Timestamp of the reading.</td></tr><tr><td>Sampling Period</td><td>Duration of the power reading sample.</td></tr><tr><td>Power Reading State</td><td>Current state of the power reading.</td></tr></table>

# Example:

<table><tr><td colspan="2">root@adlink-Default-string:/home/adlink# ipmitool dcmi power reading</td><td rowspan="8">General Power Reading</td></tr><tr><td>Instantaneous power reading:</td><td>88 Watts</td></tr><tr><td>Minimum during sampling period:</td><td>84 Watts</td></tr><tr><td>Maximum during sampling period:</td><td>96 Watts</td></tr><tr><td>Average power reading over sample period:</td><td>80 Watts</td></tr><tr><td>IPMI timestamp:</td><td>Thu Jan 18 16:50:55 2024</td></tr><tr><td>Sampling period:</td><td>00004473 Seconds.</td></tr><tr><td>Power reading state is:</td><td>activated</td></tr><tr><td colspan="2">root@adlink-Default-string:/home/adlink# ipmitool dcmi power reading 0</td><td rowspan="12">Viewing Available Parameters</td></tr><tr><td colspan="2">Invalid sample time. Valid times are:</td></tr><tr><td>5_sec</td><td></td></tr><tr><td>15_sec</td><td></td></tr><tr><td>30_sec</td><td></td></tr><tr><td>1_min</td><td></td></tr><tr><td>3_min</td><td></td></tr><tr><td>7_min</td><td></td></tr><tr><td>15_min</td><td></td></tr><tr><td>30_min</td><td></td></tr><tr><td>1_hour</td><td></td></tr><tr><td colspan="2">| | | | | | | | |</td></tr><tr><td colspan="2">root@adlink-Default-string:/home/adlink# ipmitool dcmi power reading 5_sec</td><td rowspan="8">Reading Power Over 5 Seconds</td></tr><tr><td>Instantaneous power reading:</td><td>164 Watts</td></tr><tr><td>Minimum during sampling period:</td><td>88 Watts</td></tr><tr><td>Maximum during sampling period:</td><td>164 Watts</td></tr><tr><td>Average power reading over sample period:</td><td>148 Watts</td></tr><tr><td>IPMI timestamp:</td><td>Thu Jan 18 16:51:17 2024</td></tr><tr><td>Sampling period:</td><td>5_sec</td></tr><tr><td>Power reading state is:</td><td>activated</td></tr><tr><td colspan="2">root@adlink-Default-string:/home/adlink# ipmitool dcmi power reading 15_min</td><td rowspan="8">Reading Power Over 15 Minutes</td></tr><tr><td>Instantaneous power reading:</td><td>92 Watts</td></tr><tr><td>Minimum during sampling period:</td><td>84 Watts</td></tr><tr><td>Maximum during sampling period:</td><td>164 Watts</td></tr><tr><td>Average power reading over sample period:</td><td>88 Watts</td></tr><tr><td>IPMI timestamp:</td><td>Thu Jan 18 16:51:29 2024</td></tr><tr><td>Sampling period:</td><td>15_min</td></tr><tr><td>Power reading state is:</td><td>activated</td></tr></table>

# 6.3.2.3.3 Chassis Power Reboot Reasons

To understand the reasons behind a chassis reboot, ipmitool provides a specific command that reveals the cause of the last system restart.

# Command:

ipmitool chassis restart cause

Return Details:

<table><tr><td>Restart Cause</td><td>Description</td></tr><tr><td>OEM</td><td>System restarts from within the operating system.</td></tr><tr><td>Chassis Power Control Command</td><td>The system was rebooted using a web interface or an ipmitool command.</td></tr><tr><td>Power-up via Pushbutton</td><td>Suggests that the system was restarted using the power button on the front panel.</td></tr></table>

# 6.3.2.3.4 Power Control Method

Using ipmitool command, it can control the power, such as power on, power off, power cycle, power reset.

# Command:

ipmitool power &lt;on | off | cycle | reset&gt;

<table><tr><td>Command Element</td><td>Description</td></tr><tr><td>ipmitool power on</td><td>Power on the chassis.</td></tr><tr><td>ipmitool power off</td><td>Power off the chassis.</td></tr><tr><td>ipmitool power cycle</td><td>Power off the chassis and power on the chassis.</td></tr><tr><td>ipmitool power reset</td><td>Restart the chassis.</td></tr></table>

# Example:

```txt
root@bmc:/# ipmitool power on Chassis Power Control: Up/On
root@bmc:/# ipmitool power off Chassis Power Control: Down/Off
root@bmc:/# ipmitool power cycle Chassis Power Control: Cycle
root@bmc:/# ipmitool power reset Chassis Power Control: Reset
```

# 6.3.2.4 LED Control

This section details how to use ipmitool commands for controlling the operational status of LEDs on a server.

# 6.3.2.4.1 OEM Command

Servers come with OEM commands to control certain LEDs, including the USR LED (Yellow, HDD shared), Alert LED (Red), and Health LED (Green).

# Get LED Status

Command:

(NetFn = 2Eh, Cmd = 11h)

ipmitool raw 0x2e 0x11 0x13 0x5f 0x00 &lt;LED ID&gt;

<table><tr><td rowspan="2">Request Data</td><td>Byte</td><td>Data Field</td></tr><tr><td>1~3</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr><tr><td rowspan="6">Response Data</td><td>4</td><td>LED ID:02h = USR LED (Yellow, HDD shared)03h = Alert LED (Red)04h = Health LED (Green)</td></tr><tr><td>1</td><td>Completion Code</td></tr><tr><td>2~4</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr><tr><td>5</td><td>LED ID:02h = USR LED (Yellow, HDD shared)03h = Alert LED (Red)04h = Health LED1 (Green)Other values: reserved</td></tr><tr><td>6</td><td>LED Function:00h = LED OFF override.01h - 1Eh = LED BLINKING override. The off duration is specified by the value of this byte, and the on duration is specified by the value of byte 7. Both values specify the time in hundreds of milliseconds (100 ms-3 s).1Fh = LED is in Local Control state20h-FEh ReservedFFh = LED ON override</td></tr><tr><td>7</td><td>On-duration:The LED on-time in hundreds of milliseconds if (01h Byte 6 1Eh) and ignored otherwise set to 0h.</td></tr></table>

# Set LED Status

Command:

(NetFn = 2Eh, Cmd = 10h)

ipmitool raw 0x2e 0x10 0x13 0x5f 0x00 &lt;LED ID&gt; &lt;LED Function&gt; &lt;On Duration&gt;

Request Data

<table><tr><td>Byte</td><td>Data Field</td></tr><tr><td>1~3</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr><tr><td>4</td><td>LED ID:02h = USR LED (Yellow, HDD shared)</td></tr></table>

Response Data

<table><tr><td>Byte</td><td>Data Field</td></tr><tr><td></td><td>03h = Alert LED (Red)04h = Health LED (Green)Other values: reserved</td></tr><tr><td>5</td><td>LED Function:00h = LED OFF override.01h - 1Eh = LED BLINKING override. The off duration is specified by the value of this byte, and the on duration is specified by the value of byte 5. Both values specify the time in hundreds of milliseconds (100 ms-3 s).1Fh = LED state is restored to Local Control state20h-FEh ReservedFFh = LED ON override</td></tr><tr><td>6</td><td>On Duration:The LED on-time in hundreds of milliseconds if (01h &lt;=Byte 6&lt;=1Eh) and ignored otherwise.Otherwise, this field is ignored and is set to 0h.</td></tr><tr><td>1</td><td>Completion Code</td></tr><tr><td>2~4</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr></table>

# Note:

USR LED: By default, it is not controlled by the BMC and acts as an HDD activity indicator. Manual control requires hardware changes (e.g., dip switch adjustments).

Example:

<table><tr><td>root@adlink-Default-string:/# ipmitool raw 0x2e 0x11 0x13 0x5f 0x00 0x0213 5f 00 02 1f root@adlink-Default-string:/# ipmitool raw 0x2e 0x11 0x13 0x5f 0x00 0x0313 5f 00 03 1f root@adlink-Default-string:/# ipmitool raw 0x2e 0x11 0x13 0x5f 0x00 0x0413 5f 00 04 1f</td><td>Reading Initial LED States</td></tr><tr><td>root@adlink-Default-string:/# ipmitool raw 0x2e 0x10 0x13 0x5f 0x00 0x02 0x0013 5f 00 root@adlink-Default-string:/# ipmitool raw 0x2e 0x10 0x13 0x5f 0x00 0x03 0x0013 5f 00 root@adlink-Default-string:/# ipmitool raw 0x2e 0x11 0x13 0x5f 0x00 0x0213 5f 00 02 00 root@adlink-Default-string:/# ipmitool raw 0x2e 0x11 0x13 0x5f 0x00 0x0313 5f 00 03 00</td><td>Turning Off USR LED and Alert LED</td></tr><tr><td>root@adlink-Default-string:/# ipmitool raw 0x2e 0x10 0x13 0x5f 0x00 0x03 0x05 0x0513 5f 00 root@adlink-Default-string:/# ipmitool raw 0x2e 0x11 0x13 0x5f 0x00 0x0313 5f 00 03 05 05</td><td>Setting Alert LED to BlinkBlink 0.5 sec; Stay lit 0.5 sec</td></tr><tr><td>root@adlink-Default-string:/# ipmitool raw 0x2e 0x10 0x13 0x5f 0x00 0x04 0x0a 0x0513 5f 00 root@adlink-Default-string:/# ipmitool raw 0x2e 0x11 0x13 0x5f 0x00 0x0413 5f 00 04 0a 05</td><td>Setting Health LED to BlinkBlink 1 sec; Stay lit 0.5 sec</td></tr><tr><td>root@adlink-Default-string:/# ipmitool raw 0x2e 0x10 0x13 0x5f 0x00 0x02 0x1f13 5f 00 root@adlink-Default-string:/# ipmitool raw 0x2e 0x10 0x13 0x5f 0x00 0x03 0x1f13 5f 00 root@adlink-Default-string:/# ipmitool raw 0x2e 0x10 0x13 0x5f 0x00 0x04 0x1f13 5f 00 root@adlink-Default-string:/# ipmitool raw 0x2e 0x11 0x13 0x5f 0x00 0x0213 5f 00 02 1f root@adlink-Default-string:/# ipmitool raw 0x2e 0x11 0x13 0x5f 0x00 0x03 13 5f 00 03 1f root@adlink-Default-string:/# ipmitool raw 0x2e 0x11 0x13 0x5f 0x00 0x0413 5f 00 04 1f</td><td>Restoring Initial LED States</td></tr></table>

# 6.3.2.4.2 ipmitool for UID LED

The control of the UID LED can be managed using standard IPMI commands through ipmitool. These commands allow for the activation of the UID LED for a specified duration or indefinitely.

# Command:

```txt
ipmitool chassis identify [&lt;second&gt; | force]
```

seconds: Specifies the duration for which the UID LED should remain active. The duration is set in seconds.

force: This parameter keeps the UID LED on indefinitely, without any time limit.

If no parameter is provided, the UID LED will default to a 15-second active period.

# Example:

```txt
root@bmc:/# ipmitool chassis identify
Activates the UID LED for 15 seconds, which is the default time period.

root@bmc:/# ipmitool chassis identify 50
Turns on the UID LED for 50 seconds.

root@bmc:/# ipmitool chassis identify 100
Turns on the UID LED for 100 seconds.

root@bmc:/# ipmitool chassis identify force
Keeps the UID LED on.
```

# Note:

The UID LED's behavior controlled by ipmitool commands can be overridden by physical interactions with the server's chassis, and vice versa.

Command Overrides Physical Button:

If the UID LED is activated using the ipmitool chassis identify command and then the physical UID button on the server is pressed, the LED will turn off, overriding the command's action.

Physical Button Overrides Command:

Conversely, if the UID LED is turned on using the physical button and subsequently a command is executed to change its state (e.g., ipmitool chassis identify 0 to turn it off), the command will take precedence and alter the LED's state as specified.

# 6.3.2.5 Network Configuration

# 6.3.2.5.1 Get the current configuration of the management port

ipmitool lan print [&lt;channel number&gt;]

Note: To determine on which channel the LAN interface is located, issue the 'ipmitool channel info number' command until you come across a valid 802.3 LAN channel.

# Example:

```yaml
root@bmc:/# ipmitool lan print 8
Set in Progress : Set Complete
Auth Type Support :
Auth Type Enable : Callback :
: User :
: Operator :
: Admin :
: OEM :
IP Address Source : DHCP Address
IP Address : 192.168.1.12
Subnet Mask : 255.255.255.0
MAC Address : 00:30:64:a8:7b:04
SNMP Community String : AMI
IP Header : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10
BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled
Gratituous ARP Intrvl : 1.0 seconds
Default Gateway IP : 192.168.1.1
Default Gateway MAC : 50:7b:9d:25:56:a1
Backup Gateway IP : 0.0.0.0
Backup Gateway MAC : 00:00:00:00:00:00
802.1q VLAN ID : Disabled
802.1q VLAN Priority : 0
RMCP+ Cipher Suites : 3,17
Cipher Suite Priv Max : XXXaXXXXXXXXaXXX
: X=Cipher Suite Unused
: c=CALLBACK
: u=USER
: o=OPERATOR
: a=ADMIN
: O=OEM
Bad Password Threshold : 0
Invalid password disable: no
Attempt Count Reset Int.: 0
User Lockout Interval : 0
```

# 6.3.2.5.2 Set the IP address source

ipmitool lan set &lt;channel number&gt; ipsrc &lt;source&gt;

# source:

 static: manually configured static IP address
 dhcp: address obtained by BMC running DHCP

# 6.3.2.5.3 Set the IP address

ipmitool lan set &lt;channel number&gt; ipaddr &lt;x.x.x.x&gt;

# Example:

root@bmc:/# ipmitool lan set 8 ipaddr 192.168.1.100

Setting LAN IP Address to 192.168.1.100

# 6.3.2.5.4 Set the netmask

ipmitool lan set &lt;channel number&gt; netmask &lt;x.x.x.x&gt;

# 6.3.2.5.5 Set the default gateway IP address

ipmitool lan set &lt;channel number&gt; defgw ipaddr &lt;x.x.x.x&gt;

Note: Make sure the gateway IP address is pingable.

# 6.3.2.5.6 Set network configuration via BIOS

Enter BIOS Setup -> Server Mgmt -> BMC network configuration.

<table><tr><td colspan="3">Aptio Setup - AMI</td></tr><tr><td></td><td></td><td>Server Mgmt</td></tr><tr><td>--BMC network configuration--</td><td>^</td><td>Select to configure LAN ^</td></tr><tr><td>***************</td><td>*</td><td>channel parameters *</td></tr><tr><td>Configure IPv4 support</td><td>*</td><td>statically or *</td></tr><tr><td>***************</td><td>*</td><td>dynamically(by BIOS or *</td></tr><tr><td></td><td>+</td><td>BMC). Unspecified *</td></tr><tr><td>Lan channel 1</td><td>+</td><td>option will not modify *</td></tr><tr><td>Configuration Address [Unspecified]</td><td>+</td><td>any BMC network +</td></tr><tr><td>Current Configuration DynamicAddressBmcDhcp</td><td>+</td><td>parameters during BIOS v</td></tr><tr><td>Station IP address 0.0.0.0</td><td>+</td><td></td></tr><tr><td>Subnet mask 0.0.0.0</td><td>+</td><td></td></tr><tr><td>Station MAC address 00-30-64-66-77-88</td><td>+</td><td>&lt;: Select Screen</td></tr><tr><td>Router IP address 0.0.0.0</td><td>+</td><td>^v: Select Item</td></tr><tr><td>Router MAC address 00-00-00-00-00-00</td><td>+</td><td>Enter: Select</td></tr><tr><td></td><td>+</td><td>+/-: Change Opt.</td></tr><tr><td>Lan channel 2</td><td>+</td><td>F1: General Help</td></tr><tr><td>Configuration Address [Unspecified]</td><td>+</td><td>F8: Previous Values</td></tr><tr><td>Current Configuration DynamicAddressBmcDhcp</td><td>+</td><td>F9: Optimized Defaults</td></tr><tr><td>Station IP address 192.168.1.12</td><td>v</td><td>F10: Save &amp; Exit</td></tr><tr><td></td><td>|ESC: Exit</td><td></td></tr></table>

<table><tr><td colspan="3">Aptio Setup - AMI</td></tr><tr><td></td><td></td><td>Server Mgmt</td></tr><tr><td>--BMC network configuration--</td><td>^</td><td>Select to configure LAN ^</td></tr><tr><td>***************</td><td>*</td><td>channel parameters *</td></tr><tr><td>Configure IPv4 support</td><td>*</td><td>statically or *</td></tr><tr><td>***************</td><td>*</td><td>dynamically(by BIOS or *</td></tr><tr><td></td><td>+</td><td>BMC). Unspecified *</td></tr><tr><td>Lan channel 1</td><td>+</td><td>option will not modify *</td></tr><tr><td>Configuration Address [Static]</td><td>+</td><td>any BMC network +</td></tr><tr><td>Station IP address 188.188.1.2</td><td>+</td><td>parameters during BIOS v</td></tr><tr><td>Subnet mask 255.255.255.0</td><td>+</td><td></td></tr><tr><td>Station MAC address 00-30-64-66-77-88</td><td>+</td><td></td></tr><tr><td>Router IP address 188.188.1.1</td><td>+</td><td>&lt;: Select Screen</td></tr><tr><td>Router MAC address 00-00-00-00-00-00</td><td>+</td><td>v: Select Item</td></tr><tr><td></td><td>+</td><td>Enter: Select</td></tr><tr><td>Lan channel 2</td><td>+</td><td>+/-: Change Opt.</td></tr><tr><td>Configuration Address [Unspecified]</td><td>+</td><td>F1: General Help</td></tr><tr><td>Current Configuration DynamicAddressBmcDhcp</td><td>+</td><td>F8: Previous Values</td></tr><tr><td>Station IP address 192.168.1.12</td><td>+</td><td>F9: Optimized Defaults</td></tr></table>

![| Subnet mask | 255.255.255.0 | v|F10: Save & Exit |\n| --- | --- | ESC: Exit |\nVersion 2.22.1289 Copyright (C) 2024 AMI](.axe-7220sr-50m-22810-1000-10/f018cbad866053e5329dc7f5ce6a382915c1095ac40baaad4281b7be72c0c16a.jpg)

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>Configuration Address source</td><td>StaticDynamicBmcDhcp</td><td>Set the IP address source</td></tr><tr><td>Station IP address</td><td>x.x.x.x</td><td>Set the IP address</td></tr><tr><td>Subnet mask</td><td>x.x.x.x</td><td>Set the netmask</td></tr><tr><td>Router IP address</td><td>x.x.x.x</td><td>Set the default gateway IP address</td></tr><tr><td>Router MAC address</td><td>xx:xx:xx:xx:xx:xx</td><td>Set the default gateway MAC address</td></tr></table>

# 6.3.2.6 x86 Watchdog Configuration

The x86 watchdog is used to guard the x86 system health.

# 6.3.2.6.1 Configure the watchdog via BIOS

Enter BIOS Setup -> Server Mgmt.
```txt
Aptio Setup - AMI
Main Advanced Platform Configuration Socket Configuration Server Mgmt >
| BMC Self Test Status PASSED ^ | If enabled, starts a ^ |
| BMC Device ID 32 * | BIOS timer which can *
| BMC Device Revision 81 * | only be shut off by *
| BMC Firmware Revision 1.03 * | Management Software *
| IPMI Version 2.0 * | after the OS loads. *
| IPMI BMC Interface KCS * | Helps determine that *
| BMC Support [Enabled] * | the OS successfully +
| IPMI Interface Type [Kcs Interface] *
| Wait For BMC [Enabled] *
| FRB-2 Timer [Enabled] * | loaded or follows the v |
| FRB-2 Timer timeout 6 * | >&lt;: Select Screen *
| FRB-2 Timer Policy [Do Nothing] * | ^v: Select Item *
| OS Watchdog Timer [Enabled] * | Enter: Select *
| OS Wtd Timer Timeout 10 * | +/-: Change Opt. *
| OS Wtd Timer Policy [Reset] * | F1: General Help *
| &gt; Bmc self test log + | F8: Previous Values *
| > BMC network configuration v | F9: Optimized Defaults *
| ESC: Exit
Version 2.22.1289 Copyright (C) 2024 AMI
```

<table><tr><td>BIOS Item</td><td>Options</td><td>Description</td></tr><tr><td>FRB-2 Timer</td><td>EnabledDisabled</td><td>Enable or disable FRB-2 Watchdog Timer.</td></tr><tr><td>FRB-2 Timer timeout</td><td>Number</td><td>Set FRB-2 Watchdog Timer expiration time. Unit is minutes. Not available if FRB-2 Watchdog Timer is disabled.</td></tr><tr><td>FRB-2 Timer Policy</td><td>Do NothingResetPower DownPower Cycle</td><td>Configure how the system should respond if the FRB-2 Watchdog Timer expires. Not available if FRB-2 Watchdog Timer is disabled.</td></tr><tr><td>OS Watchdog Timer</td><td>EnabledDisabled</td><td>Enable or disable OS Watchdog Timer.</td></tr><tr><td>OS Wtd Timer Timeout</td><td>Number</td><td>Set OS Watchdog Timer expiration time. Unit is minutes. Not available if OS Watchdog Timer is disabled.</td></tr><tr><td>OS Wtd Timer Policy</td><td>Do NothingResetPower DownPower Cycle</td><td>Configure how the system should respond if the OS Watchdog Timer expires. Not available if OS Watchdog Timer is disabled.</td></tr></table>

# 6.3.2.6.2 Get Watchdog Timer

ipmitool mc watchdog get

# Example:

root@bmc:/# ipmitool mc watchdog get

Watchdog Timer Use: OS Load (0x43)

Watchdog Timer Is: Started/Running

Watchdog Timer Actions: Power Down (0x02)

Pre-timeout interval: 0 seconds

Timer Expiration Flags: 0x00

Initial Countdown: 300 sec

Present Countdown: 229 sec

# 6.3.2.6.3 Set Watchdog Timer

This command is used for initializing and configuring the watchdog timer.

(NetFn = 06h, Cmd = 24h)

ipmitool raw 0x06 0x24 &lt;Timer Use&gt; &lt;Timer Actions&gt; &lt;Pre-timeout interval&gt; &lt;Timer

Expiration Flags&gt; &lt;Initial Countdown lsbyte&gt; &lt;Initial Countdown msbyte&gt;

Request Data

<table><tr><td>Byte</td><td>Data Field</td></tr><tr><td>1</td><td>Timer Use[7] - 1b[6] - 1b = don&#x27;t stop timer on &#x27;Set Watchdog Timer&#x27; command new parameters take effect immediately. If timer is already running, countdown value will get set to given value ahs countdown will continue from that point. If timer is already stopped, it will remain stopped. If the pre-timeout interrupt bit is set, it will get cleared.0b = timer stops automatically when &#x27;Set Watchdog Timer&#x27; command is received[5:3] - reserved[2:0] - timer use (logged on expiration when &quot;don&#x27;t log&quot; bit = 0b)000b = reserved001b = BIOS FRB2010b = BIOS/POST011b = OS Load100b = SMS/OS101b = OEM110b - 111b = reserved</td></tr><tr><td>2</td><td>Timer Actions[7] - reserved[6:4] - pre-timeout interrupt (logged on expiration when &quot;don&#x27;t log&quot; bit = 0b)000b = none001b = SMI (optional)010b = NMI / Diagnostic Interrupt (optional)011b = Messaging Interrupt100b - 111b = reserved[3] - reserved[2:0] - timeout action000b = no action001b = Hard Reset010b = Power Down011b = Power Cycle100b - 111b = reserved</td></tr><tr><td>3</td><td>Pre-timeout interval in seconds.</td></tr><tr><td>4</td><td>Timer Use Expiration flags clear(0b = leave alone, 1b = clear timer use expiration bit)</td></tr></table>

<table><tr><td>Byte</td><td>Data Field</td></tr><tr><td></td><td>[7] - reserved[6] - reserved[5] - OEM[4] - SMS/OS[3] - OS Load[2] - BIOS/POST[1] - BIOS FRB2[0] - reserved</td></tr><tr><td>5</td><td>Initial countdown value, lsbyte (100 ms/count)</td></tr><tr><td>6</td><td>Initial countdown value, msbyte</td></tr><tr><td>1</td><td>Completion Code</td></tr></table>

# Example:

root@bmc:/# ipmitool raw 0x06 0x24 0x04 0x02 0x00 0x10 0xb8 0x0b

root@bmc:/# ipmitool mc watchdog get

Watchdog Timer Use: SMS/OS (0x04)

Watchdog Timer Is: Stopped

Watchdog Timer Actions: Power Down (0x02)

Pre-timeout interval: 0 seconds

Timer Expiration Flags: 0x00

Initial Countdown: 300 sec

Present Countdown: 300 sec

# 6.3.2.6.4 Reset Watchdog Timer

This command is used for starting and restarting the Watchdog Timer from the initial countdown value that was specified in the 'Set Watchdog Timer' command.

ipmitool mc watchdog reset

# 6.3.2.6.5 Shutoff Watchdog Timer

ipmitool mc watchdog off

# 6.3.2.7 BIOS POST Code

# 6.3.2.7.1 Read Latest BIOS POST Code

(NetFn = 2Eh, Cmd = 92h)

ipmitool raw 0x2e 0x92 0x13 0x5f 0x00

<table><tr><td></td><td>Byte</td><td>Data Field</td></tr><tr><td>Request Data</td><td>1~3</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr><tr><td rowspan="3">Response Data</td><td>1</td><td>Completion Code</td></tr><tr><td>2~4</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr><tr><td>5</td><td>Latest BIOS POST Code</td></tr></table>

# Example:

root@bmc:/# ipmitool raw 0x2e 0x92 0x13 0x5f 0x00 13 5f 00 e3

# 6.3.2.7.2 Read BIOS POST Codes

(NetFn = 32h, Cmd = 73h)

ipmitool raw 0x32 0x73 <Code>

<table><tr><td></td><td>Byte</td><td>Data Field</td></tr><tr><td>Request Data</td><td>1</td><td>Code: read old/current data00h = Current BIOS POST Codes01h = Previous BIOS POST Codes</td></tr><tr><td rowspan="2">Response Data</td><td>1</td><td>Completion Code</td></tr><tr><td>2~n</td><td>BIOS POST Codes</td></tr></table>

# Example:

<table><tr><td colspan="16">root@bmc:/# ipmitool raw 0x32 0x73 0x00</td></tr><tr><td>50</td><td>10</td><td>01</td><td>02</td><td>03</td><td>04</td><td>05</td><td>06</td><td>03</td><td>03</td><td>23</td><td>23</td><td>00</td><td>02</td><td>7f</td><td>48</td></tr><tr><td>0e</td><td>49</td><td>4a</td><td>4d</td><td>15</td><td>52</td><td>55</td><td>19</td><td>f4</td><td>31</td><td>00</td><td>a1</td><td>a3</td><td>a3</td><td>a7</td><td>a9</td></tr><tr><td>a9</td><td>a2</td><td>a2</td><td>a7</td><td>a7</td><td>a7</td><td>a9</td><td>a9</td><td>a8</td><td>aa</td><td>ae</td><td>e0</td><td>e0</td><td>e0</td><td>e1</td><td>e4</td></tr><tr><td>e3</td><td>e5</td><td>af</td><td>b0</td><td>b5</td><td>7e</td><td>cf</td><td>7e</td><td>73</td><td>cd</td><td>b0</td><td>7e</td><td>c1</td><td>70</td><td>b1</td><td>b1</td></tr><tr><td>7e</td><td>7e</td><td>c2</td><td>7e</td><td>7e</td><td>7e</td><td>b1</td><td>b1</td><td>b1</td><td>b6</td><td>7e</td><td>b4</td><td>b8</td><td>b2</td><td>c6</td><td>b3</td></tr><tr><td>b3</td><td>b6</td><td>b6</td><td>b6</td><td>b0</td><td>b7</td><td>b6</td><td>b6</td><td>7e</td><td>7e</td><td>7e</td><td>7e</td><td>b7</td><td>b7</td><td>b7</td><td>b7</td></tr><tr><td>7e</td><td>70</td><td>70</td><td>70</td><td>70</td><td>7e</td><td>b7</td><td>b7</td><td>be</td><td>be</td><td>7e</td><td>7e</td><td>d2</td><td>7e</td><td>d2</td><td>d6</td></tr><tr><td>70</td><td>b9</td><td>7e</td><td>cc</td><td>b7</td><td>b7</td><td>b7</td><td>b7</td><td>b8</td><td>b8</td><td>d7</td><td>da</td><td>db</td><td>ba</td><td>70</td><td>70</td></tr><tr><td>7e</td><td>70</td><td>70</td><td>7e</td><td>70</td><td>7e</td><td>7e</td><td>cb</td><td>bb</td><td>bb</td><td>bb</td><td>bb</td><td>bb</td><td>bb</td><td>bb</td><td>bb</td></tr><tr><td>bb</td><td>bb</td><td>7e</td><td>7e</td><td>d0</td><td>7e</td><td>d0</td><td>7e</td><td>d0</td><td>7e</td><td>d1</td><td>d1</td><td>7e</td><td>70</td><td>7e</td><td>b7</td></tr><tr><td>ca</td><td>ca</td><td>dc</td><td>7e</td><td>cc</td><td>bc</td><td>bc</td><td>bc</td><td>bc</td><td>bc</td><td>ce</td><td>c6</td><td>7e</td><td>bf</td><td>af</td><td>af</td></tr><tr><td>e7</td><td>e9</td><td>eb</td><td>ec</td><td>ed</td><td>ee</td><td>03</td><td>23</td><td>02</td><td>22</td><td>00</td><td>02</td><td>7f</td><td>48</td><td>0e</td><td>49</td></tr><tr><td>4a</td><td>4d</td><td>15</td><td>52</td><td>55</td><td>02</td><td>22</td><td>00</td><td>04</td><td>06</td><td>0b</td><td>0c</td><td>0d</td><td>15</td><td>7f</td><td>00</td></tr><tr><td>7f</td><td>40</td><td>41</td><td>42</td><td>47</td><td>4f</td><td>33</td><td>60</td><td>61</td><td>68</td><td>70</td><td>90</td><td>91</td><td>92</td><td>94</td><td>94</td></tr><tr><td>94</td><td>94</td><td>94</td><td>94</td><td>94</td><td>94</td><td>94</td><td>94</td><td>94</td><td>94</td><td>95</td><td>96</td><td>ef</td><td>92</td><td>92</td><td>92</td></tr><tr><td>92</td><td>92</td><td>92</td><td>99</td><td>91</td><td>92</td><td>92</td><td>92</td><td>92</td><td>92</td><td>92</td><td>92</td><td>97</td><td>98</td><td>9d</td><td>9a</td></tr><tr><td>9c</td><td>b4</td><td>b4</td><td>b4</td><td>b4</td><td>b4</td><td>b4</td><td>b4</td><td>b4</td><td>98</td><td>b4</td><td>b4</td><td>b4</td><td>b4</td><td>b4</td><td>b4</td></tr><tr><td>92</td><td>a0</td><td>a2</td><td>a2</td><td>a2</td><td>a2</td><td>a2</td><td>a0</td><td>a2</td><td>a2</td><td>a2</td><td>a2</td><td>99</td><td>92</td><td>92</td><td>92</td></tr><tr><td>92</td><td>92</td><td>92</td><td>ad</td><td>af</td><td>b0</td><td>b1</td><td>b1</td><td>84</td><td>ee</td><td>aa</td><td>e3</td><td>e3</td><td>e3</td><td></td><td></td></tr></table>

# 6.3.2.8 MAC Address Burning

# 6.3.2.8.1 Burning ethx MAC Address Preparation

(NetFn = 0Ch, Cmd = 01h)

ipmitool raw 0x0c 0x01 &lt;eth0|eth1&gt; 0xc2

<table><tr><td></td><td>Byte</td><td>Data Field</td></tr><tr><td rowspan="2">Request Data</td><td>1</td><td>Which eth?0x01 is for eth00x08 is for eth1</td></tr><tr><td>2</td><td>0xC2 is for burning MAC preparation</td></tr><tr><td>Response Data</td><td>1</td><td>Completion Code</td></tr></table>

# Example:

root@bmc:/# ipmitool raw 0x0c 0x01 0x01 0xc2

# 6.3.2.8.2 Burning ethx MAC Address

(NetFn = 0Ch, Cmd = 01h)

ipmitool raw 0x0c 0x01 &lt;eth0|eth1&gt; 0x05 &lt;MAC address&gt;

<table><tr><td rowspan="3">Request Data</td><td>Byte</td><td>Data Field</td></tr><tr><td>1</td><td>Which eth?0x01 is for eth00x08 is for eth1</td></tr><tr><td>2</td><td>0x05 is for burning MAC</td></tr><tr><td rowspan="2">Response Data</td><td>3~8</td><td>Ethernet MAC address</td></tr><tr><td>1</td><td>Completion Code</td></tr></table>

# Example:

root@bmc:/# ipmitool raw 0x0c 0x01 0x01 0x05 0x00 0x30 0x64 0x11 0x22 0x33

Note: Config the eth0 MAC address to run the first ipmitool command (ipmitool raw 0x0c 0x01 0x01 0xc2) and then execute the second ipmitool command (ipmitool raw 0x0c 0x01 0x01 0x05 0x00 0x30 0x64 0x11 0x22 0x33).

# 6.3.2.9 SOL

The serial over LAN (SOL) feature is very useful, and the SOL redirects the local serial interface via an IPMI session, allowing remote access to the console.

Open SOL functionality using ipmitool command:

# Command:

ipmitool sol activate

Example:

<table><tr><td colspan="3">Main Advanced Platform Configuration Socket Configuration Server Mgmt &gt;</td></tr><tr><td>BIOS Information</td><td></td><td>|Set the Date|</td></tr><tr><td>BIOS Vendor</td><td>American Megatrends</td><td>|switch betwe|</td></tr><tr><td>BIOS Version</td><td>1.2.10</td><td>|Default Rang|</td></tr><tr><td>Build Date</td><td>01/24/2024</td><td>|Year: 1998-9|</td></tr><tr><td>RC Version</td><td>370.P03</td><td>|Months: 1-12|</td></tr><tr><td>SPS FW Version</td><td>6.1.2.48</td><td>|Days: Depend|</td></tr><tr><td></td><td></td><td>|Range of Yea|</td></tr><tr><td>System Information</td><td></td><td></td></tr><tr><td>Project Name</td><td>MECS-7120</td><td></td></tr><tr><td>CPU Board Version</td><td>/---- Save &amp; Exit ----\</td><td></td></tr><tr><td>CPU Brand String</td><td></td><td></td></tr><tr><td></td><td>| Quit without saving? |</td><td></td></tr><tr><td>CPU Frequency</td><td></td><td></td></tr><tr><td>Total Memory</td><td></td><td>|&lt;&lt;: Select S</td></tr><tr><td>Memory Frequency</td><td>| Yes No |</td><td>|^v: Select I</td></tr><tr><td>PCH SKU</td><td></td><td>|Enter: Selec|</td></tr><tr><td></td><td></td><td>|+/-: Change</td></tr><tr><td>System Date</td><td>[Fri 01/26/2024]</td><td>|F1: General</td></tr><tr><td>System Time</td><td>[03:01:19]</td><td>|F8: Previous|</td></tr><tr><td></td><td></td><td>|F9: Optimize|</td></tr><tr><td>Access Level</td><td>Administrator</td><td>|F10: Save &amp;</td></tr><tr><td></td><td></td><td>|ESC: Exit|</td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr></table>

Enter the "ipmitool sol activate" command on CLI to enter the SOL output window, then enter the BIOS configuration interface, and the content of the BIOS field interface will be redirected to the local terminal, as shown in the above figure.

# Other ipmitool Commands Related to SOL

Below is a table summarizing additional ipmitool commands related to SOL:

<table><tr><td>Command Element</td><td>Description</td></tr><tr><td>ipmitool sol deactivate</td><td>Close SOL functionality</td></tr><tr><td>ipmitool sol info</td><td>Show SOL detailed information</td></tr><tr><td>ipmitool sol setenabled | force-encryption | force-authentication | privilege-level | character-accumulate-level | character-send-threshold | retry-count | retry-interval | non-volatile-bit-rate | volatile-bit-rate&gt;&lt;value&gt;</td><td>Set SOL parameter value</td></tr><tr><td>ipmitool sol payload &lt;enable | disable | status&gt;</td><td>Set SOL payload value</td></tr><tr><td>ipmitool sol looptest</td><td>SOL connection stress test</td></tr></table>

# 6.3.2.10 Firmware and Hardware Versions

Normally there should be the following firmware components on board which all have version control.

 BMC
 BIOS
 CPLD

# 6.3.2.10.1 Get Device ID

Besides, some of the products also provide PCB revision and hardware SKU version. To get the information via ipmitool please refer to the following command:

ipmitool mc info

For example:
```txt
root@bmc:/# ipmitool mc info
Device ID : 32
Device Revision : 1
Firmware Revision : 1.03
IPMI Version : 2.0
Manufacturer ID : 24339
Manufacturer Name : ADLINK Technology Inc.
Product ID : 28960 (0x7120)
Product Name : Unknown (0x7120)
Device Available : yes
Provides Device SDRs : yes
Additional Device Support :
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
IPMB Event Generator
Chassis Device
Aux Firmware Rev Info :
0x12
0x22
0x10
0xb3
```

BMC version:

# Refer to "Firmware Revision".

Please be noted that due to the fixed format of ipmitool, minor version number always takes two digits, and do not consider it as a decimal.

Such as "1.03", means the version number is "1.3".

# BIOS, CPLD, PCB, SKU versions:

They are all in "Aux Firmware Rev Info", assign numbers to them as following

Aux Firmware Rev Info:

0x12 Byte 1

0x22  Byte 2

0x10 Byte 3

0xb3  Byte 4

# Byte 1

Low 4 bits - PCB version. In this case, 0x2, means A2.

High 4 bits - SKU version. In this case, 0x1, means SKU 1.

# Byte 2 and byte 3

BIOS version.

High 3 bits of byte 2 - Leading version. In this case, 0b001, for 1.

Low 5 bits of byte 2 - Major version. In this case, 0b00010, for 2.

Byte 3 - Minor version. In this case, 0x10.

# Please pay special attention that minor version of BIOS is always represented in hexadecimal number.

Combined version number should be 1.2.10.

# Byte 4

CPLD version. In this case, 0xb3.

# 6.3.2.10.2 Get CPLD Version and SKU Version

(NetFn = 2Eh, Cmd = 20h)

ipmitool raw 0x2e 0x20 0x13 0x5f 0x00

<table><tr><td>Request Data</td></tr><tr><td>Response Data</td></tr></table>

<table><tr><td>Byte</td><td>Data Field</td></tr><tr><td>1~3</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr><tr><td>1</td><td>Completion Code</td></tr><tr><td>2~4</td><td>ADLINK Manufacturer ID - 005F13h, LS byte first.</td></tr><tr><td>5~5+N</td><td>CPLD Version, &quot;N&quot; is the length of CPLD Version. Byte 5+N is 0.</td></tr><tr><td>6+N~15+N</td><td>SKU Version (ASCII text).</td></tr></table>

# Example:

root@bmc:/# ipmitool raw 0x2e 0x20 0x13 0x5f 0x00

13 5f 00 b4 02 00 31 55 00 00 00 00 00 00 00 00

CPLD Version is 02b4.

SKU Version is "31 55"(ASCII) -> "1U".

# 6.3.2.11 CPLD Update

ipmitool -z 0x3fff hpm upgrade &lt;hpm file&gt; component 5 force

Note: If a CPLD firmware has been uploaded, it will print "Firmware upgrade procedure failed".

# Example:

root@bmc:/# ipmitool -I lanplus -H 172.20.2.18 -U admin -P admin.123 -z 0x3fff hpm upgrade outputjbc\_02b4.hpm component 5 force

Setting large buffer to 16383

PICMG HPM.1 Upgrade Agent 1.0.9:

Validating firmware image integrity...OK

Performing preparation stage...

Services may be affected during upgrade. Do you wish to continue? (y/n): y OK

Performing upgrade stage:

<table><tr><td>ID</td><td>Name</td><td colspan="3">Versions</td><td>%</td></tr><tr><td></td><td></td><td>Active</td><td>Backup</td><td>File</td><td></td></tr><tr><td>* 5</td><td>CPLD</td><td>0.00 00000000</td><td>---.-- ----</td><td>2.04 00002002</td><td>100%</td></tr><tr><td></td><td colspan="2">Upload Time: 00:00</td><td colspan="2">Image Size: 454924 bytes</td><td></td></tr></table>

(\*) Component requires Payload Cold Reset

Firmware upgrade procedure successful

# 6.4 Redfish

Redfish is a modern, RESTful API used for the management of servers, storage, and networking equipment in data centers and large-scale enterprise environments. It's designed to replace older, less efficient management interfaces with a standardized, scalable, and secure approach.

# 6.4.1 Network Configuration

# 6.4.1.1 GET - Ethernet Interface Collection

# Request:

GET https://{{bmc ip}}/redfish/v1/Managers/Self/EthernetInterfaces

# Response:

The response status is 200 OK.

# Example:

GET https://172.20.2.12/redfish/v1/Managers/Self/Ethernetlnterfaces

```jsonl
{
    "@odata.context": "/redfish/v1/$metadata#EthernetInterfaceCollection.EthernetInterfaceCollection",
    "@odata.etag": "\"1705564980\",
    "@odata.id": "/redfish/v1/Managers/Self/EthernetInterfaces",
    "@odata.type": "#EthernetInterfaceCollection.EthernetInterfaceCollection",
    "Description": "Collection of Ethernet Interfaces for this Manager",
    "Members": [
    {
    "@odata.id": "/redfish/v1/Managers/Self/EthernetInterfaces/eth0"
    },
    {
    "@odata.id": "/redfish/v1/Managers/Self/EthernetInterfaces/eth1"
    },
    {
    "@odata.id": "/redfish/v1/Managers/Self/EthernetInterfaces/usb0"
    }
    ],
    "Members@odata.count": 3,
    "Name": "Ethernet Network Interface Collection"
}
```

# 6.4.1.2 GET - Ethernet Interface Instance

# Request:

GET https://{{bmc ip}}/redfish/v1/Managers/Self/EthernetInterfaces/{{instance}}

Response:

The response status is 200 OK. The format is JSON.

Ethernet Interface Properties:

<table><tr><td>Name</td><td>Type</td><td>Read Only</td><td>Description</td></tr><tr><td>AutoNeg</td><td>Boolean</td><td>×</td><td>Auto negotiation of speed and duplex on this interface is enabled or not.</td></tr><tr><td>DHCPv4</td><td>Object</td><td>×</td><td>Refer to DHCPv4 properties.</td></tr><tr><td>DHCPv6</td><td>Object</td><td>×</td><td>Refer to DHCPv6 properties.</td></tr><tr><td>Description</td><td>String</td><td>√</td><td></td></tr><tr><td>FullDuplex</td><td>Boolean</td><td>×</td><td>The value of this property shall represent the duplex status of the Ethernet connection on this interface.</td></tr><tr><td>HostName</td><td>String</td><td>×</td><td>DNS Hostname without any domain information.Maximum string size limit is 64.Minimum string size limit is 2.</td></tr><tr><td>IPv4Addresses</td><td>Array of Objects</td><td>√</td><td>Refer to IPv4 Address properties.</td></tr><tr><td>IPv4StaticAddresses</td><td>Array of Objects</td><td>×</td><td>Refer to IPv4 Address properties.</td></tr><tr><td>IPv6Addresses</td><td>Array of Objects</td><td>√</td><td>Refer to IPv6 Address properties.</td></tr><tr><td>IPv6StaticAddresses</td><td>Array of Objects</td><td>×</td><td>Refer to IPv6 Address properties.</td></tr><tr><td>IPv6DefaultGateway</td><td>String</td><td>√</td><td></td></tr><tr><td>Id</td><td>String</td><td>√</td><td></td></tr><tr><td>InterfaceEnabled</td><td>Boolean</td><td>×</td><td></td></tr><tr><td>LinkStatus</td><td>String</td><td>√</td><td></td></tr><tr><td>MACAddress</td><td>String</td><td>√</td><td></td></tr><tr><td>MTUSize</td><td>Number</td><td>×</td><td>Maximum size limit is 1500.Minimum size limit is 576.</td></tr><tr><td>MaxIPv6StaticAddresses</td><td>Number</td><td>√</td><td></td></tr><tr><td>Name</td><td>String</td><td>√</td><td></td></tr><tr><td>NameServers</td><td>Array of Strings</td><td>√</td><td></td></tr><tr><td>Oem</td><td>Object</td><td>√</td><td></td></tr><tr><td>PermanentMACAddress</td><td>String</td><td>√</td><td></td></tr><tr><td>SpeedMbps</td><td>Number</td><td>×</td><td>The current link speed of the interface in Mbps.</td></tr><tr><td>StatelessAddressAutoConfig</td><td>Object</td><td>×</td><td>This object shall contain the IPv4 and IPv6 Stateless Address Automatic Configuration (SLAAC) properties for this interface.</td></tr><tr><td>StaticNameServers</td><td>Array of Strings</td><td>×</td><td>Statically-defined set of DNS server IPv4 and IPv6 addresses.</td></tr><tr><td>Status</td><td>Object</td><td>√</td><td></td></tr><tr><td>VLAN</td><td>Object</td><td>×</td><td>VLANId: 0~4094.</td></tr></table>

DHCPv4 properties:

<table><tr><td>Name</td><td>Type</td><td>Read Only</td><td>Description</td></tr><tr><td>DHCPEnabled</td><td>Boolean</td><td>×</td><td>Determines whether DHCPv4 is enabled on this interface.</td></tr></table>

DHCPv6 properties:

<table><tr><td>Name</td><td>Type</td><td>Read Only</td><td>Description</td></tr><tr><td>OperatingMode</td><td>Boolean</td><td>×</td><td>This property shall control the operating mode of DHCPv6 on this interface. DHCPv6 stateful mode is used to configure addresses, and when it is enabled, stateless mode is also implicitly enabled.</td></tr></table>

IPv4 Address properties:

<table><tr><td>Name</td><td>Type</td><td>Read Only</td><td>Description</td></tr><tr><td>Address</td><td>String</td><td>-</td><td>IPv4 address.</td></tr><tr><td>AddressOrigin</td><td>String</td><td>-</td><td>IPv4 address source.</td></tr><tr><td>Gateway</td><td>String</td><td>-</td><td>IPv4 default gateway IP address.</td></tr><tr><td>SubnetMask</td><td>String</td><td>-</td><td>IPv4 netmask.</td></tr></table>

IPv6 Address properties:

<table><tr><td>Name</td><td>Type</td><td>Read Only</td><td>Description</td></tr><tr><td>Address</td><td>String</td><td>-</td><td>IPv6 address.</td></tr><tr><td>AddressOrigin</td><td>String</td><td>-</td><td>IPv6 address source.</td></tr><tr><td>PrefixLength</td><td>String</td><td>-</td><td>IPv6 network prefix length in bits. Max is 128.</td></tr></table>

# Example:

GET

https://172.20.2.12/redfish/v1/Managers/Self/Ethernetlnterfaces/eth1

```javascript
"@odata.context": "/redfish/v1/$metadata#EthernetInterface.EthernetInterface",
"@odata.etag": "\"1705564980\",
"@odata.id": "/redfish/v1/Managers/Self/EthernetInterfaces/eth1",
"@odata.type": "#EthernetInterface.v1_6_2.EthernetInterface",
"AutoNeg": true,
"DHCPv4": {
    "DHCPEnabled": true
},
"DHCPv6": {
    "OperatingMode": "Stateless"
},
"Description": "Ethernet Interface eth1",
"FullDuplex": true,
"HostName": "AMI003064667788",
```

```csv
"IPv4Addresses": [
    {
    "Address": "172.20.2.12",
    "AddressOrigin": "DHCP",
    "Gateway": "172.20.2.1",
    "SubnetMask": "255.255.255.0"
    }
],
"IPv6Addresses": [
    {
    "Address": "fe80::230:64ff:fea1:b104",
    "AddressOrigin": "LinkLocal",
    "PrefixLength": 64
    }
],
"IPv6DefaultGateway": null,
"Id": "eth1",
"InterfaceEnabled": true,
"LinkStatus": "LinkUp",
"MACAddress": "00:30:64:A1:B1:04",
"MTUSize": 1500,
"MaxIPv6StaticAddresses": 16,
"Name": "eth1",
"NameServers": [
    "192.168.1.213",
    "192.168.1.214"
],
"Oem": {
    "Ami": {
    "@odata.type": "#AMIDNSConfiguration.v1_0_0.AMIDNSConfiguration",
    "DNSEnabled": true,
    "HostNameSetting": "Auto"
    }
},
"PermanentMACAddress": "00:30:64:A1:B1:04",
"SpeedMbps": 100,
"StatelessAddressAutoConfig": {
    "IPv4AutoConfigEnabled": false,
    "IPv6AutoConfigEnabled": false
},
"StaticNameServers": [
    null,
    null,
    null
],
"Status": {
    "Health": "OK",
    "State": "Enabled"
},
"VLAN": {
    "VLANEnable": false,
    "VLANId": 0
```

```txt
}
}
```

# 6.4.1.3 PATCH - Ethernet Interface Instance

# Request:

```txt
PATCH https://{bmc ip}/redfish/v1/Managers/Self/EthernetInterfaces/{instance}
```

Please refer to the Ethernet Interface Properties that are patchable for which Read Only is False that can be sent as Request body in JSON format.

# Response:

The response status is 202 Accepted, with newly created Task details.

Example: Disable IPv4 DHCP and set static IPv4 address.

Add a key "If-Match" in request Headers tab. The value is your ETag value.

![PATCH https://172.20.2.12/redfish/v1/Managers/Self/EthernetInterfaces/eth1\nParams Authorization • Headers (10) Body • Pre-request Script Tests Settings\nHeaders 9 hidden\nKey Value\nIf-Match '1705564980'\nKey Value](.axe-7220sr-50m-22810-1000-10/c67e1c6b7357140fcdcc4120be67a4822ce01b0977cff1eaa3ecd21e7d2e658a.jpg)

Add raw body data in request Body tab. The data format is JSON.

```json
{
    "DHCPv4": {
    "DHCPEnabled": false
    },
    "IPv4StaticAddresses": [
    {
    "Address": "172.20.2.234",
    "Gateway": "172.20.2.1",
    "SubnetMask": "255.255.255.0"
    }
    ]
}
```

Response body content.

```jsonl
{
    "@odata.context": "/redfish/v1/$metadata#Task.Task",
    "@odata.id": "/redfish/v1/TaskService/Tasks/1",
    "@odata.type": "#Task.v1_4_2.Task",
}
```

```json
"Description": "Task for EthernetInterface Action",
"Id": "1",
"Name": "EthernetInterface Action",
"TaskMonitor": "/redfish/v1/TaskService/TaskMonitors/1",
"TaskState": "New"
}
```

# 6.4.2 BIOS Configuration

# 6.4.2.1 GET - HostInterface Instance

# Request:

GET https://{{bmc ip}}/redfish/v1/Managers/Self/HostInterfaces/Self

# Response:

The response status is 200 OK.

# Example:

GET

![The image displays three identical downward-pointing chevron icons arranged horizontally in a row against a white background.](.axe-7220sr-50m-22810-1000-10/0d5d437eb6e789979fd57f92f2d59efd58b6e3933ef5820d55e96e97210526fd.jpg)

https://172.20.2.12/redfish/v1/Managers/Self/Hostlnterfaces/Self

```jsonl
{
    "@odata.context": "/redfish/v1/$metadata#HostInterface.HostInterface",
    "@odata.etag": "\"1705997262\",
    "@odata.id": "/redfish/v1/Managers/Self/HostInterfaces/Self",
    "@odata.type": "#HostInterface.v1_3_0.HostInterface",
    "AuthenticationModes": [
    "BasicAuth",
    "RedfishSessionAuth"
],
    "CredentialBootstrapping": {
    "EnableAfterReset": false,
    "Enabled": true,
    "RoleId": "HostInterfaceAdministrator"
},
    "Description": "Host Interface",
    "ExternallyAccessible": false,
    "HostEthernetInterfaces": {
    "@odata.id": "/redfish/v1/Managers/Self/HostInterfaces/Self/HostEthernetInterfaces"
},
    "HostInterfaceType": "NetworkHostInterface",
    "Id": "Self",
    "InterfaceEnabled": true,
    "Links": {
    "ComputerSystems": [
    {
    "@odata.id": "/redfish/v1/Systems/Self"
    }
    ],
    "ComputerSystems@odata.count": 1,
    "CredentialBootstrappingRole": {
    "@odata.id": "/redfish/v1/AccountService/Roles/HostInterfaceAdministrator"
    }
},
    "ManagerEthernetInterface": {
    "@odata.id": "/redfish/v1/Managers/Self/EthernetInterfaces/usb0"
}
```

```txt
},
"Name": "Host Interface",
"NetworkProtocol": {
    "@odata.id": "/redfish/v1/Managers/Self/NetworkProtocol"
},
"Status": {
    "Health": "OK",
    "State": "Enabled"
}
```

# 6.4.2.2 GET – BIOS and BIOS/SD

# Request:

Get current BIOS Settings:

GET https://{{bmc ip}}/redfish/v1/Systems/Self/Bios

Get future BIOS Settings:

GET https://{{bmc ip}}/redfish/v1/Systems/Self/Bios/SD

# Response:

The response status is 200 OK.

# Example:

GET

https://172.20.2.12/redfish/v1/Systems/Self/Bios

```jsonl
{
    "@Redfish.Settings": {
    "@odata.type": "#Settings.v1_2_2.Settings",
    "SettingsObject": {
    "@odata.id": "/redfish/v1/Systems/Self/Bios/SD"
    }
},
"@odata.context": "/redfish/v1/$metadata#Bios.Bios",
"@odata.etag": "\"1705640880\",\"",
"@odata.id": "/redfish/v1/Systems/Self/Bios",
"@odata.type": "#Bios.v1_2_0.Bios",
"Actions": {
    "#Bios.ChangePassword": {
    "@Redfish.ActionInfo": "/redfish/v1/Systems/Self/Bios/ChangePasswordActionInfo",
    "target": "/redfish/v1/Systems/Self/Bios/Actions/Bios.ChangePassword"
    },
    "#Bios.ResetBios": {
    "target": "/redfish/v1/Systems/Self/Bios/Actions/Bios.ResetBios"
    }
},
"AttributeRegistry": "BiosAttributeRegistry22808.1.1.0",
```

```json
"Attributes": {
    "ACPI004": false,
    "CRCS005": "CRCS005Enable",
    "FBO001": "FBO001UEFI",
    "FBO101": "FBO101HardDisk",
    "FBO102": "FBO102NVME",
    ...
},
"Description": "Current BIOS Settings",
"Id": "Bios",
"Name": "Current BIOS Settings",
"ResetBiosToDefaultsPending": false
}
```

# 6.4.2.3 POST – Reset BIOS Settings

# Request:

POST https://{{bmc ip}}/redfish/v1/Systems/Self/Bios/Actions/Bios.ResetBios

# Response:

The response status is 204 No Content.

# Example:

Add raw body data in request Body tab. The data format is JSON.

![POST\nhttps://172.20.2.137/redfish/v1/Systems/Self/Bios/Actions/Bios.ResetBios\nParams Authorization \nHeaders (9) Body \nPre-request Script Tests Settings\nnone form-data x-www-form-urlencoded raw binary JSON \n1 \n2](.axe-7220sr-50m-22810-1000-10/6b4b4c9b82fb404879f349029b9c21ee3d5d979a3a522e5492e385288ee2d2bd.jpg)

# 6.4.2.4 POST – Change BIOS Password

# Request:

POST https://{{bmc ip}}/redfish/v1/Systems/Self/Bios/Actions/Bios.ChangePassword

# Response:

The response status is 204 No Content.

# Example:

Add raw body data in request Body tab. The data format is JSON.

```txt
POST https://172.20.2.137/redfish/v1/Systems/Self/Bios/Actions/Bios.ChangePassword
Params Authorization Headers (9) Body Pre-request Script Tests Settings
none form-data x-www-form-urlencoded raw binary JSON
{
"PasswordName": "SETUP001",
"OldPassword": "old",
"NewPassword": "new"
}
```

# 6.4.2.5 PATCH – BIOS SD

Change the values of the attributes.

# Request:

PATCH https://{{bmc ip}}/redfish/v1/Systems/Self/Bios/SD

# Response:

The response status is 204 No Content.

Refer to PATCH - BIOS Watchdog Configuration.

# 6.4.3 x86 Watchdog Configuration

# 6.4.3.1 GET - BIOS Watchdog Configuration

# Request:

Get current BIOS Settings:

```txt
GET https://{bmc ip}/redfish/v1/Systems/Self/Bios
```

Get future BIOS Settings:

```txt
GET https://{bmc ip}/redfish/v1/Systems/Self/Bios/SD
```

<table><tr><td>BIOS Item</td><td>Redfish Attribute</td><td>Redfish Value</td></tr><tr><td>FRB-2 Timer</td><td>IPMI100</td><td>IPMI100EnabledIPMI100Disabled</td></tr><tr><td>FRB-2 Timer timeout</td><td>IPMI101</td><td>Number: 1~30</td></tr><tr><td>FRB-2 Timer Policy</td><td>IPMI102</td><td>IPMI102DoNothingIPMI102ResetIPMI102PowerDownIPMI102PowerCycle</td></tr><tr><td>OS Watchdog Timer</td><td>IPMI103</td><td>IPMI103DisabledIPMI103Enabled</td></tr><tr><td>OS Wtd Timer Timeout</td><td>IPMI104</td><td>Number: 1~30</td></tr><tr><td>OS Wtd Timer Policy</td><td>IPMI105</td><td>IPMI105DoNothingIPMI105ResetIPMI105PowerDownIPMI105PowerCycle</td></tr></table>

# Response:

The response status is 200 OK.

# Example:

GET

![A gray, downward-pointing arrow or chevron icon centered on a white background.](.axe-7220sr-50m-22810-1000-10/39ed7d2de077ae45a62c3553e244c732dda25617cfedd8788270495b417c82f0.jpg)

https://172.20.2.12/redfish/v1/Systems/Self/Bios

```json
{
    "@odata.etag": "\"1705653894", ← Used in PATCH method
...
    "AttributeRegistry": "BiosAttributeRegistry22808.1.1.0",
    "Attributes": {
    ...
    "IPMI100": "IPMI100Enabled",
    "IPMI101": 6,
    "IPMI102": "IPMI102DoNothing",
    "IPMI103": "IPMI103Enabled",
    "IPMI104": 5,
    "IPMI105": "IPMI105PowerDown",
    ...
}
```

```txt
},
"Description": "Current BIOS Settings",
"Id": "Bios",
"Name": "Current BIOS Settings",
"ResetBiosToDefaultsPending": false
}
```

# 6.4.3.2 PATCH - BIOS Watchdog Configuration

# Request:

PATCH https://{{bmc ip}}/redfish/v1/Systems/Self/Bios/SD

Please refer to the GET - BIOS Watchdog Configuration to get “etag”.

# Response:

The response status is 204 No Content.

Example: Enable the OS Watchdog Timer, set the expiration time and action.

Add a key "If-Match" in request Headers tab. The value is your ETag value.

![PATCH https://172.20.2.12/redfish/v1/Systems/Self/Bios/SD\nParams Authorization Headers (10) Body Pre-request Script Tests Settings\nHeaders 9 hidden\nKey Value\nIf-Match '1705653894'\nKey Value](.axe-7220sr-50m-22810-1000-10/350698a6145b6ac103fc393d77f6571bdb9bf2ffb2c9d2803cce6283e477b6e5.jpg)

Add raw body data in request Body tab. The data format is JSON.

```json
Params Authorization Headers (10) Body Pre-request Script Tests Settings
none form-data x-www-form-urlencoded raw binary JSON
{
    "Attributes": {
    "IPMI103": "IPMI103Enabled",
    "IPMI104": 5,
    "IPMI105": "IPMI105PowerCycle"
    }
}
```

# 6.4.4 Sensor Information

This section is dedicated to explaining how to obtain sensor information through Redfish. Users can obtain the specific data of the required sensor through the following command.

# Request:

```txt
GET https://{bmc ip}/redfish/v1/Chassis/Self/Sensors/{Sensor ID}
```

# Response:

The response status is 200 OK.

# Example:

GET

![The image displays a small, light gray, downward-pointing chevron or arrow icon centered on a white background. It appears to be a standard user interface element, likely serving as a dropdown or collapse button. There is no text present in the image.](.axe-7220sr-50m-22810-1000-10/6184e474b45ac624f522388ac9096d4409df0fc8502e5cc67d9d33b3ba995dab.jpg)

https://172.20.2.36/redfish/v1/Chassis/Self/Sensors/1

```jsonl
{
    "@odata.context": "/redfish/v1/$metadata#Sensor.Sensor",
    "@odata.etag": "\"1708661966\",
    "@odata.id": "/redfish/v1/Chassis/Self/Sensors/1",
    "@odata.type": "#Sensor.v1_0_2.Sensor",
    "Accuracy": null,
    "AdjustedMaxAllowableOperatingValue": null,
    "AdjustedMinAllowableOperatingValue": null,
    "ApparentVA": null,
    "Description": null,
    "ElectricalContext": null,
    "Id": "1",
    "LoadPercent": null,
    "Location": {
    "AltitudeMeters": null,
    "Contacts": [
    null
    ],
    "Latitude": null,
    "Longitude": null,
    "PartLocation": {
    "LocationOrdinalValue": null,
    "LocationType": null,
    "Orientation": null,
    "Reference": null,
    "ServiceLabel": null
    },
    "Placement": {
    "AdditionalInfo": null,
    "Rack": null,
    "RackOffset": null,
    "RackOffsetUnits": null,
    "Row": null
    },
}
```

```txt
"PostalAddress": {
    "AdditionalCode": null,
    "AdditionalInfo": null,
    "Building": null,
    "City": null,
    "Community": null,
    "Country": null,
    "District": null,
    "Division": null,
    "Floor": null,
    "HouseNumber": null,
    "HouseNumberSuffix": null,
    "Landmark": null,
    "LeadingStreetDirection": null,
    "Name": null,
    "Neighborhood": null,
    "POBox": null,
    "PlaceType": null,
    "PostalCode": null,
    "Road": null,
    "RoadBranch": null,
    "RoadPostModifier": null,
    "RoadPreModifier": null,
    "RoadSection": null,
    "RoadSubBranch": null,
    "Room": null,
    "Seat": null,
    "Street": null,
    "StreetSuffix": null,
    "Territory": null,
    "TrailingStreetSuffix": null,
    "Unit": null
},
"MaxAllowableOperatingValue": null,
"MinAllowableOperatingValue": null,
"Name": "P12V_PSU",
"PeakReading": null,
"PeakReadingTime": null,
"PhysicalContext": "VoltageRegulator",
"PhysicalSubContext": null,
"PowerFactor": null,
"Precision": null,
"ReactiveVAR": null,
"Reading": 12.22,
"ReadingRangeMax": 13.25,
"ReadingRangeMin": 10.7,
"ReadingType": "Voltage",
"ReadingUnits": null,
"SensingFrequency": null,
"SensorResetTime": null,
"Status": {
```

```txt
"Health": "OK",
"HealthRollup": null,
"State": "Enabled"
},
"Thresholds": {
"LowerCaution": {
"Activation": null,
"DwellTime": null,
"Reading": 11.4
},
"LowerCritical": {
"Activation": null,
"DwellTime": null,
"Reading": 11.16
},
"LowerFatal": {
"Activation": null,
"DwellTime": null,
"Reading": 10.8
},
"UpperCaution": {
"Activation": null,
"DwellTime": null,
"Reading": 12.6
},
"UpperCritical": {
"Activation": null,
"DwellTime": null,
"Reading": 12.84
},
"UpperFatal": {
"Activation": null,
"DwellTime": null,
"Reading": 13.2
}
},
"VoltageType": null
}
```

Other commands to access sensor information using Redfish:

# General Thermal Sensors Information

GET https://{{bmc ip}}/redfish/v1/Chassis/Self/Thermal

Retrieves detailed information about the server's thermal sensors, including current temperature readings.

# Temperature Sensor IDs

GET https://{{bmc ip}}/redfish/v1/Chassis/Self/ThermalSubsystem/ThermalMetrics

Retrieves IDs and specific metrics of temperature-related sensors.

# General Power Sensors Information

GET https://{{bmc ip}}/redfish/v1/Chassis/Self/Power

Retrieves comprehensive data about power-related sensors, including power supply status and output power.

# Power Sensor IDs

GET https://{{bmc ip}}/redfish/v1/Chassis/Self/PowerSubsystem

Retrieves IDs and detailed metrics related to power sensors.

# 6.4.5 BMC Update

This section specifically explains how to obtain and upgrade BMC through Redfish. Users can upgrade BMC and set Preserve Configuration through the following commands.

# 6.4.5.1 GET - Preserve Configuration

This section describes how to use redfish to Get Preserve Configuration before upgrading BMC.

# Request:

GET https://{{bmc ip}}/redfish/v1/UpdateService

# Response:

The response status is 200 OK.

# Example:

GET

![The image displays three identical grey icons arranged in a horizontal row against a white background. Each icon is a downward-pointing triangle or chevron shape with a slight shadow effect, giving it a subtle three-dimensional appearance. There is no text in the image.](.axe-7220sr-50m-22810-1000-10/57ceb7c4bac5bec87b44cf0042cbfd019e45b0c2e92a1be511b94af04c276502.jpg)

https://172.20.2.36/redfish/v1/UpdateService

```jsonl
{
    "@odata.context": "/redfish/v1/$metadata#UpdateService.UpdateService",
    "@odata.etag": "\"1708925760\",
    "@odata.id": "/redfish/v1/UpdateService",
    "@odata.type": "#UpdateService.v1_6_0.UpdateService",
    "Actions": {
    "#UpdateService.SimpleUpdate": {
    "@Redfish.ActionInfo": "/redfish/v1/UpdateService/SimpleUpdateActionInfo",
    "target": "/redfish/v1/UpdateService/Actions/SimpleUpdate"
    },
    "Oem": {
    "#UpdateService.UploadCABundle": {
    "@Redfish.ActionInfo": "/redfish/v1/UpdateService/UploadCABundleActionInfo",
    "target": "/redfish/v1/UpdateService/Actions/Oem/UpdateService.UploadCABundle"
    }
    }
    },
    "Description": "Redfish Update Service",
    "FirmwareInventory": {
    "@odata.id": "/redfish/v1/UpdateService/FirmwareInventory"
    },
    "Id": "UpdateService",
    "MaxImageSizeBytes": 496611328,
    "MultipartHttpPushUri": "/redfish/v1/UpdateService/upload",
    "Name": "Update Service",
    "Oem": {
    "AMIUpdateService": {
    "@odata.type": "#AMIUpdateService.v1_0_0.AMIUpdateService",
```

```json
"FlashPercentage": null,
"PreserveConfiguration": {
    "Authentication": false,
    "EXTLOG": false,
    "FRU": false,
    "IPMI": false,
    "KVM": false,
    "NTP": false,
    "Network": false,
    "REDFISH": false,
    "SDR": false,
    "SEL": false,
    "SNMP": false,
    "SSH": false,
    "Syslog": false,
    "WEB": false
},
"UpdateStatus": null,
"UpdateTarget": null
},
"BMC": {
"@odata.type": "#AMIUpdateService.v1_0_0.BMC",
"DualImageConfigurations": {
"ActiveImage": "2",
"BootImage": "2",
"FirmwareImage1Name": "Image1",
"FirmwareImage1Version": "13.05.010004",
"FirmwareImage2Name": "Image2",
"FirmwareImage2Version": "13.05.010003"
}
},
"ServiceEnabled": true,
"Status": {
"Health": "OK",
"State": "Enabled"
}
```

# 6.4.5.2 PATCH - Preserve Configuration

This section describes how to use redfish to Set Preserve Configuration before upgrading BMC.

# Request:

PATCH https://{{bmc ip}}/redfish/v1/UpdateService

Please refer to the GET - Preserve Configuration.

# Response:

The response status is 204 No Content.

Example: Enable saving IPMI and SEL when upgrading BMC.

Add a key "If-Match" in request Headers tab. The value is your ETag value. This value can be obtained from GET - Preserve Configuration.

![PATCH https://172.20.2.36/redfish/v1/UpdateService\nParams Authorization • Headers (8) Body Pre-request Script Tests • Settings\nHeaders 7 hidden\nKey Value\nIf-Match '1706750916'\nKey Value](.axe-7220sr-50m-22810-1000-10/700578c0fde302f92c3274d5cf877285068eca248c42445f2c5628eec71c8291.jpg)

Add raw body data in request Body tab. The data format is JSON.
```json
Params Authorization Headers (10) Body Pre-request Script Tests Settings
none form-data x-www-form-urlencoded raw binary JSON
{
    "Oem": {
    "AMIUpdateService": {
    "PreserveConfiguration": {
    "IPMI": true,
    "SEL": true
    }
    }
    }
}
```

# 6.4.5.3 POST – Firmware Update

This section describes how to use redfish to Update BMC firmware.

# Request:

```txt
POST https://{bmc ip}*/redfish/v1/UpdateService/upload
```

# Response:

The response status is 202 Accepted.

# Example:

Using POSTMAN, please follow the steps as given below.

1. Ensure that all necessary files mentioned in the subsequent steps are placed in your working directory. Go to the top right corner of POSTMAN and click on the settings button. In the general settings, make the necessary adjustments.

# Working directory

![The image displays a simple graphic of a toggle switch in the 'off' position. It features a horizontal, grey, rounded rectangular track with a white circular knob positioned on the left side. There is no text present.](.axe-7220sr-50m-22810-1000-10/7237b930c8893f3bab64e575b1b1aabbb0351cc172bdfd238b67f6d8e92e6909.jpg)

2. Create a JSON file parameters.json with content like below.

```json
{
    "Targets": [
    "/redfish/v1/UpdateService/FirmwareInventory/BMCImage1"
    ]
}
```

3. Create a JSON file oem\_parameters.json with content like below.

```json
{
    "ImageType": "BMC"
}
```

4. Open POSTMAN and enter the URI to POST the request.

5. Select POST method.

6. In the Authorization tab, select Basic Auth and update request.

7. In the Body tab, select form-data and provide the key name as UpdateFile in the KEY section and change its type from Text to File.

8. Click on Select File in the VALUE section to select the signed image which is available in your local machine to update.

9. Like step 7 and 8, provide key name UpdateParameters and select parameters.json created in step 2.

10.Like step 7 and 8, provide key name OemParameters and select oem\_parameters.json created in step 3.

11.Click Send.

![POST\nhttps://172.20.2.36/redfish/v1/UpdateService/upload\nSend\nParams Authorization Headers (9) Body Pre-request Script Tests Settings\nnone form-data x-www-form-urlencoded raw binary GraphQL\nKey Value Description --- Bulk Edit\nUpdateParameters File parameters.json\nOemParameters File oem_parameters.json\nUpdateFile File rom.ima\nKey Text Value Description](.axe-7220sr-50m-22810-1000-10/1b29c9f55c16dc8b48087b285a9cb4a995c00f26a713b28f20e1924dcfc08435.jpg)

# Response:

<table><tr><td colspan="2">Body Cookies Headers (14) Test Results Status: 202 Accepted</td></tr><tr><td>Pretty</td><td>Raw Preview Visualize JSON</td></tr><tr><td>1</td><td></td></tr><tr><td>2</td><td>&quot;@odata.type&quot;: &quot;#UpdateService.v1_6_0.UpdateService&quot;,</td></tr><tr><td>3</td><td>&quot;Messages&quot;: [</td></tr><tr><td>4</td><td>{</td></tr><tr><td>5</td><td>&quot;@odata.type&quot;: &quot;#Message.v1_0_8.Message&quot;,</td></tr><tr><td>6</td><td>&quot;Message&quot;: &quot;A new task /redfish/v1/TaskService/Tasks/4 was created.&quot;,</td></tr><tr><td>7</td><td>&quot;MessageArgs&quot;: [</td></tr><tr><td>8</td><td>&quot;/redfish/v1/TaskService/Tasks/4&quot;</td></tr><tr><td>9</td><td>],</td></tr><tr><td>10</td><td>&quot;MessageId&quot;: &quot;Task.1.0.New&quot;,</td></tr><tr><td>11</td><td>&quot;Resolution&quot;: &quot;None&quot;,</td></tr><tr><td>12</td><td>&quot;Severity&quot;: &quot;OK&quot;</td></tr><tr><td>13</td><td>},</td></tr><tr><td>14</td><td>{</td></tr><tr><td>15</td><td>&quot;@odata.type&quot;: &quot;#Message.v1_0_8.Message&quot;,</td></tr><tr><td>16</td><td>&quot;Message&quot;: &quot;The action UpdateService.MultipartPush was submitted to do firmware update.&quot;,</td></tr><tr><td>17</td><td>&quot;MessageArgs&quot;: [</td></tr><tr><td>18</td><td>&quot;UpdateService.MultipartPush&quot;</td></tr></table>

# Note:

The details of UpdateParameters are given in the table below.

<table><tr><td>Allowed value</td><td>Description</td></tr><tr><td>redfish/v1/UpdateService/FirmwareInventory/BMC</td><td>When the system does not support Dual Flash</td></tr><tr><td>redfish/v1/UpdateService/FirmwareInventory/BMCImage1</td><td>For systems with Dual Flash support, to upgrade Image 1</td></tr><tr><td>redfish/v1/UpdateService/FirmwareInventory/BMCImage2</td><td>For systems with Dual Flash support, to upgrade Image 2</td></tr></table>

# 6.4.6 BIOS Update

This section specifically explains how to obtain and upgrade BIOS through Redfish. Users can upgrade BIOS through the following commands.

# 6.4.6.1 GET - BIOS Update Status

# Request:

GET https://{{bmc ip}}/redfish/v1/UpdateService

# Response:

The response status is 200 OK.

<table><tr><td>Name</td><td>Type</td><td>Read Only</td><td>Description</td></tr><tr><td>BIOSFlashEffectStatus</td><td>String</td><td>√</td><td>Indicates the BIOS update effect status:Waiting: there is a BIOS update task waiting to take effect.Updating: someone is updating BIOS.null: no BIOS update task.</td></tr></table>

# Example:

GET https://172.20.2.18/redfish/v1/UpdateService

```jsonl
{
    "@odata.context": "/redfish/v1/$metadata#UpdateService.UpdateService",
    "@odata.etag": "\"1708587273\",
    "@odata.id": "/redfish/v1/UpdateService",
    "@odata.type": "#UpdateService.v1_6_0.UpdateService",
    "Actions": {
    "#UpdateService.SimpleUpdate": {
    "@Redfish.ActionInfo": "/redfish/v1/UpdateService/SimpleUpdateActionInfo",
    "target": "/redfish/v1/UpdateService/Actions/SimpleUpdate"
    },
    "Oem": {
    "#UpdateService.UploadCABundle": {
    "@Redfish.ActionInfo": "/redfish/v1/UpdateService/UploadCABundleActionInfo",
    "target": "/redfish/v1/UpdateService/Actions/Oem/UpdateService.UploadCABundle"
    }
    }
},
"Description": "Redfish Update Service",
"FirmwareInventory": {
    "@odata.id": "/redfish/v1/UpdateService/FirmwareInventory"
},
"Id": "UpdateService",
"MaxImageSizeBytes": 496717824,
"MultipartHttpPushUri": "/redfish/v1/UpdateService/upload",
"Name": "Update Service",
```

```json
"Oem": {
    "AMIUpdateService": {
    "@odata.type": "#AMIUpdateService.v1_0_0.AMIUpdateService",
    "BIOSFlashEffectStatus": null,
    "FlashPercentage": null,
    "PreserveConfiguration": {
    "Authentication": false,
    "EXTLOG": false,
    "FRU": false,
    "IPMI": false,
    "KVM": false,
    "NTP": false,
    "Network": false,
    "REDFISH": false,
    "SDR": false,
    "SEL": false,
    "SNMP": false,
    "SSH": false,
    "Syslog": false,
    "WEB": false
    },
    "UpdateStatus": null,
    "UpdateTarget": null
    },
    "BMC": {
    "@odata.type": "#AMIUpdateService.v1_0_0.BMC",
    "DualImageConfigurations": {
    "ActiveImage": "1",
    "BootImage": "1",
    "FirmwareImage1Name": "Image1",
    "FirmwareImage1Version": "13.05.010004",
    "FirmwareImage2Name": "Image2",
    "FirmwareImage2Version": "13.05.010003"
    }
    }
},
"ServiceEnabled": true,
"Status": {
    "Health": "OK",
    "State": "Enabled"
}
```

# 6.4.6.2 POST – Firmware Update

This section describes how to use redfish to Update BIOS firmware.

# Request:

POST https://{{bmc ip}}/redfish/v1/UpdateService/upload

# Response:

The response status is 202 Accepted.

# Example:

Using POSTMAN, please follow the steps as given below.

1. Ensure that all necessary files mentioned in the subsequent steps are placed in your working directory. Go to the top right corner of POSTMAN and click on the settings button. In the general settings, make the necessary adjustments.

# Working directory

![This image displays a grayscale toggle switch icon in the 'off' position, featuring a white circular knob on the left side of a light gray rectangular track.](.axe-7220sr-50m-22810-1000-10/078fe8bfd81997ee111215043c8df2e504a9e9a5ac1b0216a3886faebbfb6e46.jpg)

2. Create a JSON file parameters.json with content like below.

```json
{
    "Targets" : [
    "/redfish/v1/UpdateService/FirmwareInventory/BIOS"
    ]
}
```

3. Create a JSON file oem\_parameters.json with content like below.

```json
{
    "ImageType" : "BIOS",
    "update_me" : false,
    "update_nvram" : false,
    "effect_poweroff" : false,
    "force_update" : false
}
```

<table><tr><td>Name</td><td>Type</td><td>Description</td></tr><tr><td>update_me</td><td>Boolean</td><td>Optional. Default value is false. true: update ME. false: skip ME.</td></tr><tr><td>update_nvram</td><td>Boolean</td><td>Optional. Default value is false. true: update NVRAM. false: skip NVRAM.</td></tr><tr><td>effect_poweroff</td><td>Boolean</td><td>Optional. Default value is false. true: take effect when powered off.false: take effect immediately.</td></tr><tr><td>force_update</td><td>Boolean</td><td>Optional. Default value is false. true: force to update. false: do not update when other user is in in update mode or a BIOS firmware has been uploaded.</td></tr></table>

4. Open POSTMAN and enter the URI to POST the request.
5. Select POST method.
6. In the Authorization tab, select Basic Auth and update request.
7. In the Body tab, select form-data and provide the key name as UpdateFile in the KEY section and change its type from Text to File.
8. Click on Select File in the VALUE section to select the signed image which is available in your local machine to update.
9. Like step 7 and 8, provide key name UpdateParameters and select parameters.json created in step 2.
10.Like step 7 and 8, provide key name OemParameters and select oem\_parameters.json created in step 3.

# 11.Click Send.

![POST\nhttps://172.20.2.18/redfish/v1/UpdateService/upload\nSend\nParams Authorization Headers (10) Body Pre-request Script Tests Settings\nnone form-data x-www-form-urlencoded raw binary\nKey Value 000 Bulk Edit\nUpdateFile MECS-7120_1210.BIN ×\nUpdateParameters parameters.json ×\nOemParameters oem_parameters.json ×\nKey Value](.axe-7220sr-50m-22810-1000-10/0a68fb6279ae90743d9f24b7feb56dc289d7ef4ee1a96892aee7542823b3d740.jpg)

# Response:

```json
{
    "@odata.type": "#UpdateService.v1_6_0.UpdateService",
    "Messages": [
    {
    "@odata.type": "#Message.v1_0_8.Message",
    "Message": "A new task /redfish/v1/TaskService/Tasks/1 was created.",
    "MessageArgs": [
    "/redfish/v1/TaskService/Tasks/1"
    ],
    "MessageId": "Task.1.0.New",
    "Resolution": "None",
```

```txt
"Severity": "OK"
},
{
"@odata.type": "#Message.v1_0_8.Message",
"Message": "The action UpdateService.MultipartPush was submitted to do firmware update.",
"MessageArgs": [
"UpdateService.MultipartPush"
],
"MessageId": "UpdateService.1.0.StartFirmwareUpdate",
"Resolution": "None",
"Severity": "OK"
}
]
```

# 6.4.7 CPLD Update

This section specifically explains how to obtain and upgrade BIOS through Redfish. Users can upgrade BIOS through the following commands.

# 6.4.7.1 GET - CPLD Update Status

# Request:

GET https://{{bmc ip}}/redfish/v1/UpdateService

# Response:

The response status is 200 OK.

<table><tr><td>Name</td><td>Type</td><td>Read Only</td><td>Description</td></tr><tr><td>CPLDFlashEffectStatus</td><td>String</td><td>√</td><td>Indicates the CPLD update effect status:Waiting: there is a CPLD update waiting to take effect.Updating: someone is updating Firmware.null: no CPLD update.</td></tr></table>

# Example:

```txt
GET √ https://172.20.2.18/redfish/v1/UpdateService
```

```txt
{
...
    "Oem": {
    "AMIUpdateService": {
    "@odata.type": "#AMIUpdateService.v1_0_0.AMIUpdateService",
    "BIOSFlashEffectStatus": null,
    "CPLDFlashEffectStatus": null,
    "FlashPercentage": null,
    }
}
```

# 6.4.7.2 POST – Firmware Update

This section describes how to use redfish to Update CPLD firmware.

# Request:

POST https://{{bmc ip}}/redfish/v1/UpdateService/upload

# Response:

The response status is 202 Accepted.

# Example:

Using POSTMAN, please follow the steps as given below.

1. Ensure that all necessary files mentioned in the subsequent steps are placed in your working directory. Go to the top right corner of POSTMAN and click on the settings button. In the general settings, make the necessary adjustments.

# Working directory

![The image displays a horizontal toggle switch interface element. It features a grey, rounded rectangular track with a white circular knob positioned on the left side. A soft, blurred drop shadow is visible directly beneath the switch.](.axe-7220sr-50m-22810-1000-10/776fd7af98cea17249a36b44cce9fd6f185ac95afae9d354a0c88119671c07a1.jpg)

2. Create a JSON file parameters.json with content like below.

```json
{
    "Targets" : [
    "/redfish/v1/UpdateService/FirmwareInventory/CPLD"
    ]
}
```

3. Create a JSON file oem\_parameters.json with content like below.

```json
{
    "ImageType" : "HPM",
    "force_update" : false
}
```

<table><tr><td>Name</td><td>Type</td><td>Description</td></tr><tr><td>force_update</td><td>Boolean</td><td>Optional. Default value is false. true: force to update. false: do not update when other user is in in update mode or a CPLD firmware has been uploaded.</td></tr></table>

4. Open POSTMAN and enter the URI to POST the request.
5. Select POST method.
6. In the Authorization tab, select Basic Auth and update request.
7. In the Body tab, select form-data and provide the key name as UpdateFile in the KEY section and change its type from Text to File.
8. Click on Select File in the VALUE section to select the signed image which is available in your local machine to update.

9. Like step 7 and 8, provide key name UpdateParameters and select parameters.json created in step 2.

10.Like step 7 and 8, provide key name OemParameters and select oem\_parameters.json created in step 3.

# 11.Click Send.

![POST\nhttps://172.20.2.18/redfish/v1/UpdateService/upload\nSend\nParams Authorization \nHeaders (10) Body \nPre-request Script Tests Settings\nnone \nform-data x-www-form-urlencoded raw binary\nKey Value 000 Bulk Edit\nUpdateFile outputjbc_02b4.hpm\nUpdateParameters parameters.json\nOemParameters oem_parameters.json\nKey Value](.axe-7220sr-50m-22810-1000-10/1756bf8e26f8f4998a50192ae54dee3e92f5518754b8e74a691b403679158165.jpg)

# Response:

```jsonl
{
    "@odata.type": "#UpdateService.v1_6_0.UpdateService",
    "Messages": [
    {
    "@odata.type": "#Message.v1_0_8.Message",
    "Message": "A new task /redfish/v1/TaskService/Tasks/1 was created.",
    "MessageArgs": [
    "/redfish/v1/TaskService/Tasks/1"
    ],
    "MessageId": "Task.1.0.New",
    "Resolution": "None",
    "Severity": "OK"
    },
    {
    "@odata.type": "#Message.v1_0_8.Message",
    "Message": "The action UpdateService.MultipartPush was submitted to do firmware update.",
    "MessageArgs": [
    "UpdateService.MultipartPush"
    ],
    "MessageId": "UpdateService.1.0.StartFirmwareUpdate",
    "Resolution": "None",
    "Severity": "OK"
    }
    ]
}
```

# 6.4.8 Power Control

This section is dedicated to explaining how to control power through Redfish.

# Request:

POST https://{{bmc ip}}/redfish/v1/Chassis/Self/Actions/Chassis.Reset

# Response:

The response status is 202 Accepted.

# Example:

```txt
POST https://172.20.2.16/redfish/v1/Chassis/Self/Actions/Chassis.Reset
Params Authorization Headers (10) Body Pre-request Script Tests Settings
none form-data x-www-form-urlencoded raw binary JSON
{
"ResetType": "ForceRestart"
}
```

Note: The ResetType can be one of the following values: "On", "ForceOff", "GracefulShutdown", "ForceRestart", "PowerCycle".

# Response:

```json
{
    "@odata.context": "/redfish/v1/$metadata#Task.Task",
    "@odata.id": "/redfish/v1/TaskService/Tasks/1",
    "@odata.type": "#Task.v1_4_2.Task",
    "Description": "Task for Chassis Reset",
    "Id": "1",
    "Name": "Chassis Reset",
    "TaskMonitor": "/redfish/v1/TaskService/TaskMonitors/1",
    "TaskState": "New"
}
```

# 6.4.9 Firmware and Hardware Versions

To get BMC version, CPLD version and hardware version, use "Managers" class.

# Request:

```txt
POST https://{bmc ip}/redfish/v1/Managers/Self
```

# Response:

The response status is 202 OK.

# Example:

![GET https://172.20.2.16/redfish/v1/Managers/Self\nParams Authorization Headers (8) Body Pre-request Script Tests Settings\nnone form-data x-www-form-urlencoded raw binary](.axe-7220sr-50m-22810-1000-10/0ac1c37cd8ef2295c9a870c124129c4fa0315e7b137fac0897d92f17ef6ed98b.jpg)

![Body Cookies Headers (24) Test Results\n200 OK 203 ms 4.36 KB S\nPretty Raw Preview Visualize JSON √ = ?\n62 },\n63 'FirmwareVersion': '1.04 - 0xb4000012',\n64 'GraphicalConsole': {\n65 'ConnectTypesSupported': (\n66 'KVMIP'\n45 'CPLDVersion': '02b4',](.axe-7220sr-50m-22810-1000-10/34da355ee12abbb20ac146d5d7424905beed00fd947eeaf7cebc7112b14695eb.jpg)

Member "FirmwareVersion" consists of:

BMC version - 1.4

CPLD version - 02b4

Hardware version - 2.1 (PCB A2 SKU 1)

# 6.4.10 BIOS Version

To get BIOS version, use "Systems" class.

# Request:

POST https://{{bmc ip}}/redfish/v1/Systems/Self

# Response:

The response status is 202 OK.

# Example:

![GET\nhttps://172.20.2.18/redfish/v1/Systems/Self\nParams Authorization Headers (9) Body Pre-request Script\nBody Cookies Headers (31) Test Results\nPretty Raw Preview Visualize JSON\n32 },\n33 'BiosVersion': '1.2.10',\n34 'Boot': {\n35 'RootNext': null.](.axe-7220sr-50m-22810-1000-10/9f4c23c704d8751ad2e5dfaf1447a3fe1e05cb19a52af276a5a70401de5b0c4d.jpg)

Member "BiosVersion" has the value.

"1.2.10" - Leading version.Major version.Minor version

Please pay special attention that minor version of BIOS is always represented in hexadecimal number.

# Important Safety Instructions

For user safety, please read and follow all instructions, WARNINGS, CAUTIONS, and NOTES marked in this manual and on the associated equipment before handling/operating the equipment.

1. Read these safety instructions carefully.
2. Keep this user’s manual for future reference.
3. Read the specifications section of this manual for detailed information on the operating environment of this equipment.
4. The equipment can be operated at an ambient temperature of $4 0 ^ { \circ } \mathsf { C } .$
5. When installing/mounting or uninstalling/removing equipment; or when removal of the chassis lid required for user servicing (Section 3.1-3.5):
• Turn off power and unplug any power cords/cables, and
Reinstall the chassis lid before restoring power.

![The image displays a red triangular warning sign with a white exclamation point in the center. Beneath the triangle, the text 'WARNING:' is written in black, uppercase letters.](.axe-7220sr-50m-22810-1000-10/fb3b5416561e64053e1845deec1f135a156f6c3e48aed804816931005f3f834e.jpg)

Hazardous moving parts. Keep body parts out of the motion path.

![The image displays a black and white line drawing. Inside a triangle with a thick black outline, there is a symbol resembling a fan with five curved blades radiating from a central point. The top and bottom of the image are bordered by thick black horizontal lines.](.axe-7220sr-50m-22810-1000-10/02e9e3a1dabf6b62acd0021d771d84a50da557672fcf98dbba2c0fceaa4f0423.jpg)

6. To avoid electrical shock and/or damage to equipment:

• Keep equipment away from water or liquid sources;
• Keep equipment away from high heat or high humidity;
• Keep equipment properly ventilated (do not block or cover ventilation openings);
• Make sure to use recommended voltage and power source settings;
• Always install and operate equipment near an easily accessible electrical socketoutlet;
• Secure the power cord (do not place any object on/over the power cord);
Only install/attach and operate equipment on stable surfaces and/or recommended mountings;
If the equipment will not be used for long periods of time, turn off and unplug the equipment from its power source.
• The power cord must be connected to a socket or outlet with a ground connection.

7. Never attempt to fix the equipment. Equipment should only be serviced by qualified personnel.

8. An RTC battery may be provided for uninterrupted, backup or emergency power.

![The image shows a standard warning sign featuring a yellow triangle with a black border and a black exclamation point in the center. Below the triangle is the text 'CAUTION:' in black capital letters.](.axe-7220sr-50m-22810-1000-10/6d43df57e01b4b763ed553263812468a5fa0709e18d36b45065e7fd73bf170d3.jpg)

Risk of explosion if battery is replaced with one of an incorrect type. Discard used batteries according to the manufacturer's instructions.

9. This equipment is not suitable for use in locations where children are likely to be present.

10.Equipment must be serviced by authorized technicians when:

• The power cord or plug is damaged;
Liquid has penetrated the equipment;
• It has been exposed to high humidity/moisture;
• It is not functioning or does not function according to the user’s manual;
• It has been dropped and/or damaged; and/or,
It has an obvious sign of breakage.

11.Please pay strict attention to all warnings and advisories appearing on the device, to avoid injury or damage.

12.The equipment may have more than one power supply input. To reduce the risk of electrical shock, trained personnel should disconnect all power supply inputs before servicing.

![The image displays a standard safety warning sign featuring a yellow triangle with a thick black border. Inside the triangle is a large black exclamation point. Below the triangle, the word 'CAUTION' is written in black, capital letters.](.axe-7220sr-50m-22810-1000-10/02743bef937054e0e598dd4010e258902656cb603dea145eebcf720e22d7874e.jpg)

Shock hazard! Disconnect all power supply inputs before servicing.

![The image shows a yellow triangular warning sign with a black border and a black lightning bolt symbol in the center. Below the symbol is the text 'Shock hazard!'.](.axe-7220sr-50m-22810-1000-10/8be30618b37cd0ca658f505c49755cd71e991a5849b4430d8900212f8b249935.jpg)

![Multiple power sources](.axe-7220sr-50m-22810-1000-10/797e1ea1760769556b7a9f4a19a78ae8dbf0b844daf52a065cd3a0f1ac77c4d5.jpg)

13.It is recommended that equipment be installed only in a server room or computer room where access is:

Restricted to qualified service personnel or users familiar with restrictions applied to the location, reasons therefor, and any precautions required;
Only afforded by the use of a tool or lock and key, or other means of security, and is controlled by the authority responsible for the location.

14.Suitable for installation in Information Technology Rooms in accordance with Article 645 of the National Electrical Code and NFPA 75.

15.When using a Fiber Optic Small-Form Pluggable (SFP) module, ensure it is IEC 60825-1, IEC 60825-2 and IEC 60950-1 or IEC 62368-1 certified and a Class 1 Laser Product.

16.Make sure to connect the power cord to a socket-outlet with earthing if supplied by Class I power supply or power source.

17.Equipment intended for installation in Restricted Access Location.

# Consignes de Sécurité Importantes

Pour assurer la sécurité de l’utilisateur, veuillez lire et suivre toutes les directives, ainsi que les AVERTISSEMENTS, MISES EN GARDE et REMARQUES de ce manuel et indiqués sur l’équipement associé avant de manipuler ou utiliser l’équipement.

1. Veuillez lire attentivement ces instructions de sécurité avec soin.
2. Veuillez conserver ce manuel pour référence future.
3. Veuillez lire la section des spécifications de ce manuel pour avoir des informations détaillées sur l’environnement d’exploitation de cet équipement.
4. L’équipement peut être utilisé à une température ambiante de $40 \%$ .
5. Lors de l’installation ou du montage et de la désinstallation ou de la dépose de l’équipement; ou lors de la dépose du couvercle du châssis pour procéder à l’entretien par l’utilisateur (Sections 3.1-3.5):

• Coupez l’alimentation et débranchez les cordons et les câbles d’alimentation, et
• Reposez le couvercle du châssis avant de remettre l’alimentation.

![The image displays a standard safety symbol consisting of a red triangle with a white exclamation point in its center. Below the triangle, the word 'WARNING' is printed in black capital letters.](.axe-7220sr-50m-22810-1000-10/e6b955e1c0a4776e7e7241f25d2cfee6d55d921e8a069e87cd12b50b32dd3dfc.jpg)
AVERTISSEME AT

Pièces mobiles dangereuses. Gardez les parties du corps hors de la trajectoire.

![The image displays a black triangular outline containing a stylized, four-bladed fan or propeller symbol in its center.](.axe-7220sr-50m-22810-1000-10/bb9d1aa9cff91417edcbf0595de9eb2883e2fae6079129a0b37805f15bdd1c85.jpg)

6. Pour éviter un risque d’électrocution et pour éviter d’endommager l’équipement :

• Éloignez l’équipement de l’eau et de toute source liquide;
• Éloignez l’équipement de toute source de chaleur ou d’humidité élevée;
Gardez l’équipement correctement ventilé (ne pas bloquer ou couvrir les ouvertures de ventilation);
Veillez à utiliser la tension recommandée et les réglages adéquats pour la source d’alimentation;
Veuillez toujours installer et exploiter l’équipement à proximité d’une prise de courant facilement accessible;
Assurez-vous que le cordon d’alimentation est acheminé de manière sécuritaire (ne déposez aucun objet dessus);
Installez, fixez et utilisez l’équipement sur des surfaces stables ou sur les fixations recommandées uniquement;
Si l’équipement n’est pas utilisé pendant une longue période, éteignez-le et débranchez-le de sa source d’alimentation.
• Le cordon d'alimentation doit être connecté à une prise ou à une prise de courant avec mise à la terre.

7. N’essayez jamais de réparer l’équipement. L’équipement ne doit être réparé que par du personnel qualifié.

8. Une pile au lithium peut être installée pour assurer l’alimentation de secours ou d’urgence en continu.

![The image displays a yellow triangular warning sign with a black border and a black exclamation point in the center. Below the triangle, the word 'CAUTION:' is written in black capital letters. Underneath that, the phrase 'mise en garde' is printed in black lowercase text.](.axe-7220sr-50m-22810-1000-10/c7b1014d9d92c3ca3a2b50307e8bed0c3963ee5f84674bbbd9f5ec88d4c3c55f.jpg)

Risque d'explosion si la batterie est remplacée par une batterie d'un type incorrect. Jetez les piles usagées conformément aux instructions du fabricant.

9. Cet équipement ne convient pas à une utilisation dans des lieux pouvant accueillir des enfants.
10.L’équipement doit être entretenu par des techniciens agréés lorsque :

le cordon d’alimentation est endommagé ou lorsque la fiche électrique est endommagée;
du liquide a pénétré à l’intérieur de l’équipement;
l’équipement a été exposé à un taux d’humidité élevé;
• l’équipement ne fonctionne pas ou ne fonctionne pas conformément au manuel de l’utilisateur;
• l’équipement est tombé ou lorsqu’il a été endommagé;
• l’équipement présente un signe évident de défaillance.

11.Veuillez porter une attention rigoureuse à tous les avertissements et à tous les avis figurant sur l’appareil, pour éviter des blessures ou des dommages.
12.L’équipement peut avoir plus d’une entrée d’alimentation. Pour réduire le risque d’électrocution, le personnel qualifié devrait déconnecter toutes les entrées d’alimentation avant de procéder à l’entretien.

![The image displays a standard yellow triangular warning sign with a black border. Centered inside the triangle is a large black exclamation point. Below the triangle, the text 'CAUTION:' is printed in black, uppercase letters.](.axe-7220sr-50m-22810-1000-10/8fee76a595a198da69e4e0607dfdbf4ead361bb5d63814683b477ffa89b328c6.jpg)
mise en garde

Risque d'électrocution! Débranchez toutes les entrées d'alimentation avant de procéder à l'entretien.

![The image displays a triangular warning sign with a bright yellow background and a thick black border. Centered inside the triangle is a black lightning bolt symbol, indicating an electrical hazard or high voltage.](.axe-7220sr-50m-22810-1000-10/44adb1cd75619f8255b495549ea03b0e74f8923f2e4bde0b965175d584f48cba.jpg)
Shock hazard! Risgue d'électrocution!

![The image displays a digital logic symbol. Central to the image is a triangle pointing to the right, representing a buffer or amplifier. On the left side, three horizontal lines enter the flat base of the triangle as inputs. On the right side, three horizontal lines exit the apex of the triangle as outputs. Above the triangle, a long arrow points to the right. To the far left of the inputs, there are two vertical parallel lines.](.axe-7220sr-50m-22810-1000-10/5240e9987fdc43ff7ed305a7360e878ee523c5765e65d24492143d9f88403f30.jpg)
Multiple power sources Sources d'alimentation multiples

13.Il est recommandé que l'équipement soit installé que dans une salle de serveur ou de la salle informatique où:

L'accès est limité au personnel de maintenance qualifié ou utilisateurs familiers avec les restrictions appliquées à l'emplacement, motifs, et tout les précautions nécessaires, et;
• L'accès est uniquement assurée par l'utilisation d'un outil ou clé, ou d'autres moyens de sécurité, et est contrôlé par l'autorité responsable de l'emplacement.

14.Peut être installé dans des salles de matériel de traitement de l’information conformément à l’article 645 du National Electrical Code et à la NFPA 75.
15.Lorsque vous utilisez un module à fibre optique Small-Form Pluggable (SFP), assurezvous qu'il est certifié CEI 60825-1, CEI 60825-2 et CEI 60950-1 ou CEI 62368-1 et qu'il s'agit d'un produit laser de classe 1.
16. Assurez-vous de connecter le cordon d'alimentation à une prise de courant avec connexion à la terre si elle est fournie par une alimentation ou une source d'alimentation de classe I.
17.Équipement destiné à être installé dans un emplacement à accès restreint

# Getting Service

Ask an Expert: https://www.adlinktech.com/en/Askanexpert

# ADLINK Technology, Inc.

Address: No. 66, Huaya 1st Rd., Guishan District

Taoyuan City 333411, Taiwan

333411 桃園市龜山區華亞一路66號

Tel: +886-3-216-5088

Fax: +886-3-328-5706

Email: service@adlinktech.com

# Ampro ADLINK Technology, Inc.

Address: 6450 Via Del Oro, San Jose, CA 95119-1208, USA

Tel: +1-408-360-0200

Toll Free: +1-800-966-5200 (USA only)

Fax: +1-408-600-1189

Email: info@adlinktech.com

# ADLINK Technology (China) Co., Ltd.

Address: 上海市浦东新区张江高科技园区芳春路 300 号 (201203)

300 Fang Chun Rd., Zhangjiang Hi-Tech Park, Pudong New Area

Shanghai, 201203 China

Tel: +86-21-5132-8988

Fax: +86-21-5132-3588

Email: market@adlinktech.com

# ADLINK Technology GmbH

Address: Hans-Thoma-Strasse 8-10, 68163, Mannheim, Germany

Tel: +49-621-43214-0

Fax: +49-621 43214-30

Email: emea@adlinktech.com

Please visit the Contact page at www.adlinktech.com for information on how to contact the ADLINK regional office nearest you.
[🔗 Link to the original document](.axe-7220sr-50m-22810-1000-10/axe-7220sr-50m-22810-1000-10.pdf)