# AXE-7420GWA # User’s Manual 4U Short-depth AI GPU Server with Intel® Xeon® 600 Processors for Workstations ![Front view of a server rack unit with hexagonal ventilation slots and drive ports (no visible text or labels)](.axe-7420gwa-50m-22811-1000-02/f8bee5ef363d767a12303178ba000ea0c3652d82ba26addc2c35db6ff5a7b29b.jpg) Manual Rev.: 0.2 Preliminary Revision Date: June 15, 2026 Part Number: 50M-22811-1000 # Preface # Copyright Copyright 2026 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 with two crossed lines and a solid rectangle below (no text or labels)](.axe-7420gwa-50m-22811-1000-02/5a00dd3f139b4a4a3bb286280e4771231a872933ad42df42c5cb9708d101bf8e.jpg) Battery Labels (for products with battery) ![Simple line drawing of a trash bin crossed out by two diagonal lines (no text or symbols)](.axe-7420gwa-50m-22811-1000-02/e2dbbe97eecc73eb6fe940aa1c5df7994d6df32885d0a8a5ed1caf48a07a3679.jpg) ![The image displays a black recycling symbol featuring three chasing arrows enclosed within a square border. Directly below the square, the text 'Li-ion' appears in bold, black letters.](.axe-7420gwa-50m-22811-1000-02/79afcccce23dcbc8c8fb112efc5268f924200345be962cd917ef878dadf16eba.jpg) ![RECYCLE\nRBRC\nLi-ion\n1.800.822.8837](.axe-7420gwa-50m-22811-1000-02/c14408a8546f259d28e4429a2d3585a183872a8dfe0bd6f365b822fd2893dea2.jpg) ![廢電池請回收](.axe-7420gwa-50m-22811-1000-02/95f5184f8f0ee98bbdbe530d93fbf07e5cb3312bf3180e5687c820744a736ae7.jpg) # California Proposition 65 Warning ![The image displays a standard warning sign featuring a yellow triangle with a thick black border. Inside the triangle, centered, is a black exclamation mark.](.axe-7420gwa-50m-22811-1000-02/0408a6b44aadd794da568b1f667c04d814153211e49c11c0f4a991681eeef457.jpg) WARNING: This product can expose you to chemicals including acrylamide, arsenic, benzene, cadmium, Tris(1,3-dichloro-2-propyl)phosphate (TDCPP), 1,4-Dioxane, formaldehyde, lead, DEHP, styrene, DINP, BBP, PVC, and vinyl materials, which are known to the State of California to cause cancer, and acrylamide, benzene, cadmium, lead, mercury, phthalates, toluene, DEHP, DIDP, DnHP, DBP, BBP, PVC, and vinyl materials, which are known to the State of California to cause birth defects or other reproductive harm. For more information go to www.P65Warnings.ca.gov. # Trademarks Product names mentioned herein are used for identification purposes only and may be trademarks and/or registered trademarks of their respective companies. # Conventions Take note of the following conventions used throughout this manual to make sure that users perform certain tasks and instructions properly. ![The image is a square icon enclosed by a black border. It depicts a white document resembling a piece of paper with a folded top-right corner. Faint gray horizontal lines are visible on the document, simulating text. A large, bold red checkmark is superimposed over the document, angled from the bottom left to the top right.](.axe-7420gwa-50m-22811-1000-02/a2cddcc167136a624718ad0f8e6c7deab5a3bdc22afb7c8648a0892e08a8089c.jpg) NOTE: Additional information, aids, and tips that help users perform tasks. ![The image shows a yellow triangle with a black border containing a large black exclamation point in the center.](.axe-7420gwa-50m-22811-1000-02/2463727f5b325c187893d46fb8b64bea2604e4bc14ca787763028f2b7c1ce0a6.jpg) CAUTION: Information to prevent minor physical injury, component damage, data loss, and/or program corruption when trying to complete a task. ![A red triangle containing a white exclamation point.](.axe-7420gwa-50m-22811-1000-02/80e8da517c243d69ab688c940f4139f01d4ac858ebec2f10d1d55e01f1d63aa4.jpg) WARNING: Information to prevent serious physical injury, component damage, data loss, and/or program corruption when trying to complete a specific task. # Revision History
RevisionDescriptionDateBy
0.1Preliminary release2026-05-05AL
0.2Specifications, block diagram, and BIOS setup updated2026-06-15AL
# Table of Contents # Preface... # List of Figures .... .vii # List of Tables...... .viii # 1 Introduction.... 1.1 Features... 1.2 Packing List . 1.3 Optional Accessories . # Specifications ... # Functional Block Diagram ....... # 4 Mechanical Layout .. 4.1 Mechanical Dimensions . 7 4.2 Server Layout .. .8 4.3 Connector Locations .. ..10 # Connector Pinouts and Jumper Settings ...... .11 5.1 Rear I/O Connectors . .11 5.2 Onboard Headers and Connectors.. ..18 5.3 Jumper and Switch Settings....... ..27 5.4 Expansion Slots .31 # Getting Started....... .45 6.1 Installing Memory Modules . ..45 6.2 PCIe Slot Secondary Power Supply.. ..46 6.3 BMC LAN Configuration.. ..46 6.4 BIOS Update... ..47 6.5 BMC Firmware Update via Network . ..47 6.6 CPLD Update... ..47 6.7 Create a RAID Volume... ..48 # 7 BIOS Settings..... .49 7.1 BIOS Setup Menu.. .Error! Bookmark not defined. 7.2 Main Menu.. .Error! Bookmark not defined. 7.3 Advanced Menu.... .Error! Bookmark not defined. 7.4 Chipset Menu.... .Error! Bookmark not defined. 7.5 Security Menu... .Error! Bookmark not defined. 7.6 Boot Menu . .Error! Bookmark not defined. 7.7 Save & Exit Menu . .Error! Bookmark not defined. 7.8 Server Management . .Error! Bookmark not defined. 7.9 View System Event Log .. .Error! Bookmark not defined. 7.10 BMC User Settings . .Error! Bookmark not defined. 7.11 BMC Warm Reset.. .Error! Bookmark not defined. # 8 BMC .... ..89 8.1 BMC Introduction .... ..89 8.2 Web GUI Introduction.. ..90 8.3 IPMI . ..141 8.4 Redfish . .151 # Safety Instructions... ..182 # Consignes de Sécurité Importantes.. ..184 # FCC Warning ........ ..186 # Getting Service............ ....187 # List of Figures Figure 1: Functional block diagram.. 5 Figure 2: Mechanical dimensions .. Figure 3: AXE-7420GWA rear panel . .8 Figure 4: AXE-7420GWA front panel.. .9 Figure 5: Onboard LED indicators . ..10 Figure 6: Jumper and switch locations . .27 Figure 7: Expansion slot block diagram.. ..31 # List of Tables Table 1: Motherboard layout descriptions. ..10 # Introduction ADLINK AXE-7420GWA is a 4U 19" rackmount edge computing server/workstation system powered by 6thgeneration Intel® Xeon™ 600 workstation processors with Intel® W890 chipset. For providing rich IO expansion, there are 12x PCIe slots on chassis, up to 8x 2.5” storage bay and 1x 3.5” storage bay. It also features high-speed data transfer interfaces such as PCIe 5.0, USB 3.2 Gen 2, and SATA 6 Gb/s (SATA III), along with quad-channel DDR5 memory supporting up to 6400 MT/s for edge AI applications. With an abundant I/O port design and high-speed data transfer interfaces, the AXE-7420GWA provides a significant competitive advantage for edge AI computing in terms of device compatibility, durable connectivity, and readiness for extreme environments. # 1.1 Features The main features of the AXE-7420GWA as follows: • 4U chassis with a single Intel® Xeon® 600 Processors for Workstations, up to 350W TDP • 12-slot expansion design, including 4x PCIe x16(1x via MICO) & 2x PCIe x8 & 2x PCIe x4 Up to 4x GPU cards with extension board Up to 11x PCIe slots with extension board 8x 2.5” SATA SSD 3x Internal fan modules & 2x optional external fan modules Supports a single Intel® Granite Rapids-Workstation family processor 8× DDR5 DIMMs, up to 6400 MT/s (4 channels, 1DPC) • Supports up to 11 PCIe slots with extension board, including 3× PCIe x16 slots Supports up to 4 MCIO connectors Onboard VGA and DisplayPort (DP) ports • 1× 1GbE (Intel® I210) and 1× 2.5GbE (Intel® I226); supports Wake-on-LAN (WOL) and PXE boot BMC with AST2600, compliant with IPMI v2.0 and Redfish Dimension: 550mm(L) x 438mm(W) x 176mm(H) # 1.2 Packing List • AXE-7420GWA bare bone CPU cooler Power code # 1.3 Optional Accessories • 2-bay SlimSAS storage (Part Number: 29-0450A-0000) • 8-bay 2.5 Inch SATA/SAS 6Gbps Hard Drive kit (Part Number: 29-04300-0000) • 1-slot PCIex16 extension (Part Number: xxx) • 4-slots PCIe extension board, 2x PCIex8, 2PCIex4 (55-37233-000E) • 2-port USB 2.0 cable with bracket (Part Number: 30-25010-3010) • 2-port USB 3.0 cable with bracket (Part Number: 30-25046-0100) • 2-port COM cable with bracket (Part Number: 30-25116-0000-A0) This page intentionally left blank. Specifications
SystemForm Factor4U 19" Rackmount
Dimension (WxDxH)438 x 550 x 177mm (17.23 x 21.65 x 6.95 inch)
Gross Weight21.4kg (47.18 lbs)
Net Weight18.1kg (39.90 lbs)
ProcessorSocket TypeSocket E2, LGA 4710 socket
Support CPU SeriesSingle Intel® Xeon® 600 Processors for Workstations, up to 350W TDP
TDPSupport up to 350W
ChipsetPCHW890
GPUType3x FHFL GPU Gen5 x16
MemorySlot Count8x DIMM slots
Capacity1TB, 128GBx 8 slot(note)
DIMM Type/Speed4 Channel DDR5, 8 slots DDR5 RDIMM ECC Memory speed: Up to 6400MT/S (1DPC), 5200 MT/S (2DPC)
StorageSATA4x SATA III slots, SATA RAID 0/1/5/10 supported by PCH or Up to 8x SATA III slots, SATA RAID 0/1/5/10 supported by PCH (optional)
M.2 (2242/2280)2x M.2(M-Key) NVMe #1 support 2280/22110/25110 #2 support 2280/22110
PCIe Expansion SlotConfigurationExpert stream (128L): 3x PCIe 5.0 x16 2x PCIe 5.0 x8 2x PCIe 5.0 x4 Mainstream (80L): 2x PCIe 5.0 x16 2x PCIe 5.0 x8 2x PCIe 5.0 x4
CoolingSystem Fan3x fan modules (80x38 fan) 1x fan modules in rear end (60x 25 fan)
Power SupplyPSU TypeATX PS2
Efficiency80 Plus Titanium
Output Watts1650W
Voltage100V to 240V AC @50-60Hz
Redundancy1+1
Front I/OLEDsPower on x1, system event x1, thermal alarm x1
USB2x USB 2.0
Others1x Power button 1x Reset hole
Rear I/OLAN1x 1Gb RJ45 Ethernet port (shared with IPMI Management LAN) 1x 2.5Gb RJ45 Ethernet port
COM1x DB-9 COM connector with RS-232/422/485
USB5x Type A USB3.2 Gen2 10Gbps 1x Type C USB3.2 Gen2 10Gbps
Graphic1x D-Sub 15-pin VGA port 1x DP port
Button1x Clear CMOS reset hole button
SecurityTPM (Optional)TPM 2.0 module SPI
BMC ControllerChipsetASPEED AST2600 with IPMI 2.0 and Redfish support
BIOSChipsetAMI BIOS on SPI flash memory
EnvironmentTemperatureOperating: 0°C to +40°C · Storage: -40°C to +70°C Relative Humidity: 10%–85% (long term), 5%–90% (short term)
Operation systemOSWindows® 11 LTSC (64 bit)Ubuntu 24.04 (64 bit)
![The image displays a simple icon featuring a white sheet of paper with its top-left corner folded down (a 'dog-ear'). Faint horizontal lines run across the lower portion of the paper. A large, bold red checkmark is superimposed over the center of the document, angled slightly upward from left to right.](.axe-7420gwa-50m-22811-1000-02/c517f42816691d9d1924bad8904544028ff3c490a1d69af1f041955a52aa92c2.jpg) NOTE: \* Follow the latest Intel® Memory POR # Functional Block Diagram ![Based on the provided flowchart, here is the accurate and concise description of the labeled blocks and their connections:\n\n**Power and Memory Section (Top Left)**\n* **Blocks:** 'CRPS Redundant PSUs Supports 12V DC input', 'ATX Connector 24P x4', 'ATX Connector 8P x4', 'DDR5 RDIMM 5200 MT/s (2DPC) 4 Channel 2DPC configuration Max System Capacity ~2TB', 'DDR5 RDIMM slot x2' (repeated 4 times).\n* **Connections:**\n * 'CRPS Redundant PSUs...' connects to 'ATX Connector 24P x4' and 'ATX Connector 8P x4' via 'Power/PMBus'.\n * 'DDR5 RDIMM 5200...' connects to four 'DDR5 RDIMM slot x2' blocks.\n * Each 'DDR5 RDIMM slot x2' connects via 'DDR5' to 'CHA', 'CHC', 'CHE', and 'CHG' respectively.\n\n**Processor and PCIe Expansion Section (Top Center & Right)**\n* **Blocks:** 'Processor Intel CPU Socket E2 LGA 4710 (Granite Rapids Expert + Mainstream Workstation, TDP 350W)', 'PCIe x16 CEM-Slot4', 'PCIe x16 CEM-Slot1', 'MCIO x8 74P x2' (repeated), 'MCIO 1&2', 'MCIO 3&4', 'PCIe x16 CEM-Slot7', 'PCIe x4 CEM-Slot6', 'PCIe x8 CEM-Slot5', 'M .2_2280/22110/25110', 'PCIe x8 CEM-Slot3', 'PCIe x8 CEM-Slot2', 'M .2_2280/22110', 'TPM pin header', 'TPM Module INFINEON TPM 2.0 SLM 9670AQ2.0'.\n* **Connections:**\n * 'Processor' connects to 'PCIe x16 CEM-Slot4' via 'PE6' and 'PCIe Gen5 x16'.\n * 'Processor' connects to 'PCIe x16 CEM-Slot1' via 'PE8' and 'PCIe Gen5 x16'.\n * 'Processor' connects to 'MCIO 3&4' via 'PE7', 'PCIe Gen5 x16', and 'MCIO x8 74P x2'.\n * 'Processor' connects to 'MCIO 1&2' via 'PE3', 'PCIe Gen5 x16', and 'MCIO x8 74P x2'.\n * 'Processor' connects to 'PCIe x16 CEM-Slot7' via 'PE0' and 'PCIe Gen5 x16'.\n * 'Processor' connects to 'PCIe x4 CEM-Slot6' via 'PE0' and 'PCIe Gen5 x4'.\n * 'Processor' connects to 'PCIe x8 CEM-Slot5' via 'PE2' and 'PCIe Gen5 x8'.\n * 'Processor' connects to 'M .2_2280/22110/25110' via 'PE0' and 'PCIe Gen5 x4'.\n * 'Processor' connects to 'PCIe x8 CEM-Slot3' via 'PE0' and 'PCIe Gen5 x4'.\n * 'Processor' connects to 'PCIe x8 CEM-Slot2' via 'PE2' and 'PCIe Gen5 x8'.\n * 'Processor' connects to 'M .2_2280/22110' via 'PE0' and 'PCIe Gen5 x4'.\n * 'Processor' connects to 'TPM pin header' via 'SPI'.\n * 'TPM pin header' connects to 'TPM Module INFINEON TPM 2.0 SLM 9670AQ2.0'.\n\n**Central Hub (W890) and Peripherals**\n* **Blocks:** 'W890', 'Microphone Speaker 3.5mm Jack', 'Mic-in', 'Line-in', 'Line-out', 'Codec Realtek ALC897', 'MDI', 'Intel Ethernet Controller I226-V', 'PCIe Gen3 x1', 'HDA', '2.5G BaseT RJ45 + 2x1 Type-A USB3', '2x USB3.2', '2x USB2.0', 'TI TUSB1002AIRGER USB 3.2 Re-driver', 'USB3.2 Gen2', 'USB2.0/1.1', '1G BaseT RJ45 + 2x1 Type-A USB3', 'TI TUSB1002AIRGER USB 3.2 2P Re-driver', 'USB Type-C 10G + USB 3 Type A', 'U3#1', 'U3#2', 'U3#3', 'U3#6', '8x 7pin SATA3 Header', 'SATA#0~7', 'VROC Header', 'GPP F23'.\n* **Connections:**\n * 'W890' connects to 'Processor' via 'DMI Gen4 x8' and 'eSPI'.\n * 'Microphone Speaker 3.5mm Jack' connects via 'Mic-in', 'Line-in', 'Line-out' to 'Codec Realtek ALC897'.\n * 'Codec Realtek ALC897' connects via 'MDI' to 'Intel Ethernet Controller I226-V'.\n * 'Intel Ethernet Controller I226-V' connects via 'PCIe Gen3 x1' to 'W890' (labeled 'PCIe#3' and 'HDA').\n * '2.5G BaseT RJ45 + 2x1 Type-A USB3' connects via '2x USB3.2' and '2x USB2.0' to 'TI TUSB1002AIRGER USB 3.2 Re-driver'.\n * 'TI TUSB1002AIRGER USB 3.2 Re-driver' connects via 'USB3.2 Gen2', 'USB2.0/1.1', 'USB3.2 Gen2' to 'W890' (labeled 'U3#2').\n * '1G BaseT RJ45 + 2x1 Type-A USB3' connects via '2x USB3.2' and '2x USB2.0' to 'TI TUSB1002AIRGER USB 3.2 2P Re-driver'.\n * 'TI TUSB1002AIRGER USB 3.2 2P Re-driver' connects via 'USB2.0/1.1', 'USB3.2 Gen2' to 'W890' (labeled 'U3#6').\n * 'USB Type-C 10G + USB 3 Type A' connects via 'USB3.2 Gen2', 'USB2.0/1.1', 'USB3.2 Gen2', 'USB2.0/1.1' to 'TI TUSB1002AIRGER USB 3.2 Re-driver'.\n * 'TI TUSB1002AIRGER USB 3.2 Re-driver' connects via 'USB2.0/1.1', 'USB3.2 Gen2', 'USB2.0/1.1' to 'W890' (labeled 'U3#1').\n * 'USB Type-C 10G + USB 3 Type A' connects via 'USB2.0/1.1', 'USB3.2 Gen2', 'USB2.0/1.1' to 'TI TUSB1002AIRGER USB 3.2 Re-driver'.\n * 'TI TUSB1002AIRGER USB 3.2 Re-driver' connects via 'USB2.0/1.1', 'USB3.2 Gen2', 'USB2.0/1.1' to 'W890' (labeled 'U3#2').\n * '8x 7pin SATA3 Header' connects via 'SATA#0~7' to 'W890'.\n * 'VROC Header' connects via 'GPP F23' to 'W890'.\n\n**Server IPMC and Headers Section (Bottom Right)**\n* **Blocks:** 'Server IPMC ASPEED AST2600', 'PCIe#9~12', 'PCIe Gen4 x4', 'SlimSAS 1', 'PCIe#21~24', 'SlimSAS 2', 'U3#7~10', 'USB2.0/1.1', 'USB3.2 Gen1', 'USB3.2 x4 Header', 'USB3.2 x4', 'U2#11~12', 'USB2.0 x2', 'U3#3', 'NC-SI', 'To I210-IT', 'PCIe#7', 'MDI', 'To AST2600', 'U2#13~14', 'KCS/Redfish', 'I2C/SMBus', 'I2C', 'Nuvoton NCT6126D', 'UART', 'PCIe#4', 'PCIe Gen2 x1', 'DISPLAY PORT', 'DP connector', 'VGA', 'DBG UART', 'IPMC Header', 'GPIOs', 'UID/Reset/Power button', 'Front panel', 'PWM/TACH', '48W Fan x2', 'System Fan x4', 'CPU Fan', 'UARTx2', 'RS485 Transceiver x2 EXAR SP339', 'COMx1', '2x1 D-SUB connector', 'UARTx3', 'RS232 Transceiver ADM213EARSZ', 'COMx4', 'COM x5 Header', 'SPI Switch', 'BIOS Flash 64MB', 'SPI', 'eSPI'.\n* **Connections:**\n * 'W890' connects to 'Server IPMC ASPEED AST2600' via 'PCIe Gen2 x1' (from 'PCIe#4').\n * 'W890' connects to 'SlimSAS 1' via 'PCIe#9~12' and 'PCIe Gen4 x4'.\n * 'W890' connects to 'SlimSAS 2' via 'PCIe#21~24' and 'PCIe Gen4 x4'.\n * 'W890' connects to 'USB3.2 x4 Header' via 'U3#7~10' and 'USB3.2 Gen1' (and 'USB2.0/1.1').\n * 'USB3.2 x4 Header' connects via 'USB3.2 x4' to 'USB3.2 x4 Header'.\n * 'W890' connects to 'USB2.0 x2' via 'U2#11~12'.\n * 'W890' connects to 'USB2.0 x2' via 'U3#7~10' and 'USB2.0/1.1'.\n * 'W890' connects to 'To I210-IT' via 'U3#3' and 'NC-SI'.\n * 'W890' connects to 'To AST2600' via 'PCIe#7' and 'MDI'.\n * 'W890' connects to 'SPI Switch' via 'U3#6' and 'SPI'.\n * 'SPI Switch' connects to 'BIOS Flash 64MB' via 'SPI'.\n * 'BIOS Flash 64MB' connects to 'Server IPMC' via 'SPI'.\n * 'W890' connects to 'Server IPMC' via 'U2#13~14' and 'KCS/Redfish'.\n * 'W890' connects to 'Nuvoton NCT6126D' via 'I2C/SMBus' and 'I2C'.\n * 'Nuvoton NCT6126D' connects to 'Server IPMC' via 'UART'.\n * 'Server IPMC' connects to 'DP connector' via 'DISPLAY PORT'.\n * 'Server IPMC' connects to 'VGA' via 'VGA'.\n * 'Server IPMC' connects to 'IPMC Header' via 'DBG UART'.\n * 'Server IPMC' connects to 'UID/Reset/Power button' and 'Front panel' via 'GPIOs'.\n * 'Server IPMC' connects to '48W Fan x2', 'System Fan x4', and 'CPU Fan' via 'PWM/TACH'.\n * 'Server IPMC' connects to '2x1 D-SUB connector' via 'UARTx2', 'RS485 Transceiver x2 EXAR SP339', and 'COMx1'.\n * 'Server IPMC' connects to 'COM x5 Header' via 'UARTx3', 'RS232 Transceiver ADM213EARSZ', and 'COMx4'.\n\n**Legend (Top Right)**\n* **Blocks:** 'Key IC', 'Internal connector', 'I/O', 'Expert Workstation SKU'.\n* **Connections:** 'Expert Workstation SKU' is an arrow pointing to the right.](.axe-7420gwa-50m-22811-1000-02/9daf4e86b2586a9ab00b9fa23cb11052ba7a027f2b961398408b53f29af297d7.jpg) Figure 1: Functional block diagram This page intentionally left blank. # Mechanical Layout # 4.1 Mechanical Dimensions ![The image displays a technical engineering drawing of a server chassis featuring five orthographic projections with dimensional annotations:\n\n* **Top View:** Shows the rear panel with fans and I/O ports, marked with a width of **438.00**.\n* **Middle Left View:** A side profile view indicating a total height of **550.00**, a horizontal hole spacing of **76.00**, and a small bottom dimension of **7.00**.\n* **Middle Center View:** A large side panel view showing internal mounting holes, marked with a width of **438.00**.\n* **Middle Right View:** A side profile view featuring a hexagonal vent pattern, marked with a width of **176.00**.\n* **Bottom View:** The front panel view showing drive bays and a control area with small text labels reading **SYS** and **TEMP**.](.axe-7420gwa-50m-22811-1000-02/c3e5743a3ae661d7bfda77221305beab09d4eeeafa412edb8460ae74ef33db82.jpg) Figure 2: Mechanical dimensions # 4.2 Server Layout # AXE-7420GWA Rear Panel ![2.5 Gb LAN\nDP\nCOM\n1Gb LAN\nAudio\nPSU\nClear CMOS reset hole\nVGA\nUSB3.2 Gen2\nUSB3.2 Type C\nPCIE Slot](.axe-7420gwa-50m-22811-1000-02/73ec486f7fe3c1a233fb5c0172313dfe604e5048ccf1a6c784e26d4ddf212ec2.jpg) Figure 3: AXE-7420GWA rear panel # AXE-7420GWA Front Panel ![System event LED\nThermal alarm LED\nSYS\nTEMP\n5.25' Bay\n3.3' Bay\nUSB 2.0\nPower button Reset button](.axe-7420gwa-50m-22811-1000-02/c787dcb24613fd4c2a382b3d5247b6b48169e41311a184e40bcc9b1083c6b447.jpg) Figure 4: AXE-7420GWA front panel # 4.3 Connector Locations ![Circuit board layout diagram with numbered components and labeled slots, likely for a computer or hardware assembly.](.axe-7420gwa-50m-22811-1000-02/8295c136dd919910130c135e96ad84a88351f0e84131d11a95163830d510a325.jpg) Figure 5: Onboard LED indicators Table 1: Motherboard layout descriptions
No.Description
1Clear CMOS reset hole
2System Fan
3System Fan
4DP connector
5COM+VGA
62.5Gb LAN + USB3.2 Gen2
71Gb LAN+USB 3.2 Gen2
8USB3.2 Gen2 + Type C
9Audio
10System Fan
11System Fan
12PCIe x16
13PCIe x8
14PCIe x4 with x8 connector
15PCIex16
16PCIex8
17PCIex4
18PCIex16
19XDP (for debug)
20CPU fan
21Case open detection
22CPU Power connector
23DDR5 slot
No.Description
24DDR5 slot
25DDR5 slot
26DDR5 slot
27CRPS power board header
28DIDO header
29IPMB header
30USB3.2 Gen1 header
31USB3.2 Gen1 header
32CPU
33VROC
34COM port
35CMOS battery
36PCH-W890
37M.2 connector
3880 port display
39COM port
40COM port
41COM port
42DDR5 slot
43DDR5 slot
44DDR5 slot
45DDR5 slot
46M.2 connector
No.Description
47COM port
48CPU Power connector
49USB 2.0 header
50SlimSAS
51ESPI header
52SMBus header
53CPLD JTAG header
54SGPIO header
55MCIO connector
56MCIO connector
57MCIO connector
58MCIO connector
59ATX Power connector
60System Fan
61System Fan
62SlimSAS
63PCIe power connector
64PCIe power connector
65SATA III x2
66SATA III x2
67SATA III x2
68SATA III x2
69Front Panel header
![The image shows a white document icon with a folded top-right corner and horizontal black lines running down the page. A large red checkmark is superimposed over the left side of the document. There is no text present in the image.](.axe-7420gwa-50m-22811-1000-02/8cfb9d438c59a55f9f5c4c19e6d5266dbc3f36951a2023a5b0860c4dfd39b10a.jpg) NOTE: Please ensure the correct pin definition when connecting the power cables. # Connector Pinouts and Jumper Settings # 5.1 Rear I/O Connectors # Clear CMOS Reset Button (SW2)
SignalPin
PCH_RTCRST-L1
GND2
GND3
GND4
![0.40\n(.016)\n0.70\n(.028)\n4.50\n(.177)\n7.00±0.50\n(.276±.020)\n8.50±0.40\n(.335±.016)\n1.80 ±0.3\n(.071±.03)\n4.00\n(.157)\n7.20\n(.283)\n3.50±0.50\n(.138±.020)](.axe-7420gwa-50m-22811-1000-02/b1cf2fcec50d0c1ea8d9ce574c88ee3ff0aa6679a9eb6edd121546a30d340e05.jpg) ![6.55\n(.258)\nØ3.50\n(.138)\n0.30\n(.012)\n2.55\n(.100)\nH\n0.70\n(.028)\n2.50\n(.098)\n4.00\n(.157)](.axe-7420gwa-50m-22811-1000-02/0835d0f04faf4b2cdf98016b5a8def9bde8f0bc467d2a6771784353770b315b6.jpg) ![The image shows a schematic labeled 'CIRCUIT DIAGRAM' at the bottom. It depicts two parallel horizontal branches.\n\nThe top branch connects a circle labeled 'T3' to a circle labeled 'T4' via a capacitor symbol (two parallel vertical lines). A line extends to the right from 'T4' and connects to a ground symbol, which is labeled 'GROUND TERMINAL'.\n\nThe bottom branch connects a circle labeled 'T1' to a circle labeled 'T2' via an open switch symbol.](.axe-7420gwa-50m-22811-1000-02/820d87757cf7b08b3e13cf1f487da46e2a10539d62eaf3409584af8c0ea432c7.jpg) # DisplayPort Connector (DP\_DDI1) ![Isometric line drawing of an electronic component housing (no text or symbols)](.axe-7420gwa-50m-22811-1000-02/1577faeb201496ca4abff466a3b479ec12b6956bcb61be2a342e218f485f7108.jpg) ![16.10 (.634)\n12.00 (.472)\n19-0.50 (.020)(PITCH)\nCL OF 16.10\nPIN 1\n4-0.40 (.016)\n20-0.20 (.008)\n2-0.120 (.047)\nPIN 20\n164±0.1 (.065±0.04)\nCL OF 12.00\n5-R0.30±0.2 (R.012±0.008)\n10.50 (.413)\nPIN 2\n4.76 (.187)\nPIN 19\n1.64±0.1 (.065±0.04)](.axe-7420gwa-50m-22811-1000-02/9c5470ee271e30fd6350f9178cd6de1efe6b5d6478a15d7f9840228de365d8a0.jpg) ![DP_DDI1\n1 ML_LANE_0P\n2 GND1\n3 ML_LANE_0N\n4 ML_LANE_1P\n5 GND2\n6 ML_LANE_1N\n7 ML_LANE_2P\n8 GND3\n9 ML_LANE_2N\n10 ML_LANE_3P\n11 GND4\n12 ML_LANE_3N\n13 CONFIG1\n14 CONFIG2\n15 AUX_CHP\n16 GND7\n17 AUX_CHN\n18 HPD\n19 RTN\n20 PWR\nDisplayPort_20\nN1 N2\n1 2\n1 9 20\nMTG1 MTG2 MTG3 MTG4\nG1 G2 G3 G4](.axe-7420gwa-50m-22811-1000-02/33b9b6e5a2d747b02fc813e369d4333bff931690135b1e33a19071f70082c048.jpg)
PIN#Signal NamePIN#Signal Name
1DDI2_PAIR0_P_Ch_CN13DP_CONN_CFG1(1M ohm to GND)
2GND14DP_CONN_CFG2(1M ohm to GND)
3DDI2_PAIR0_N_Ch_CN15DP_AUX_CONN_P
4DDI2_PAIR1_P_Ch_CN16GND
5GND17DP_AUX_CONN_N
6DDI2_PAIR1_N_Ch_CN18CN_DDI2_HPD
7NC19GND
8GND20DP_3V3
9NCG1GND
10NCG2GND
11GNDG3GND
12NCG4GND
# VGA+ DSUB(9P) VGA\_COM1 ![16.84±0.13\n( .663±.005 )\n2.77\n( .109 )\n1.385\n( .0545 )\n8.38±0.13\n( TYP.) \nPOS.1\n2.84\n( .112 )\n( TYP.)\n4-40 UNC\n( 4PL.) \nPOS.1\n19.05±0.25\n( .750±.010 )\n31.47±0.38\n( 1.239±.015 )\n1.98( .078 )\n1.98( .078 )\n2.29\n( .090 )\n( TYP.)\n1.145 ( .045 )\n( TYP.)\n0.25 ( .010 )\n16.31±0.13\n( .642±.005 )\n24.99±0.25\n( .984±.010 )\n30.81±0.38\n( 1.213±.015 )\n②\n③\n6.27±0.25\n( .247±.010 )\n3.90 ±0.18 ( .154 ± .006 )\n5](.axe-7420gwa-50m-22811-1000-02/45a4ca4c10056afccc1044266e0dfe660ef17db031ff793c7463f2fa27079290.jpg) ![5.97±0.13\n(.235±.005)\n①\n⑨\n⑧\n1.27±0.20\n(.050±.008)\n12.55±0.38\n(.494±.015)\n6.17±0.13\n(.243±.005)\n8.89±0.25\n(.350±.010)\n11.43±0.25\n(.450±.010)\n13.97±0.25\n(.550±.010)\n17.88±0.25\n(.704±.010)\n3.18±0.20\n(.125±.008)](.axe-7420gwa-50m-22811-1000-02/64718ea7735dc1b48f11402dec4634e9e9b8b87ff3b4b100db516028cbc96302.jpg) ![VGA COM1B\nUP COM\n20\n24\n19\n23\n18\n22\n17\n21\n16\nD-SUB+H/D_9_F15](.axe-7420gwa-50m-22811-1000-02/a78502b1259330ce2a9f37137098afcee60a2d56d8760cf29516ae2eb2c93e43.jpg)
PIN#Signal NamePIN#Signal Name
16COM1_DCD-L21COM1_DSR-L
17COM1_RXD22COM1_RTS-L
18COM1_TXD23COM1_CTS-L
19COM1_DTR-L24P_+5V_PSU/P_+12V_PSU
20GND
![VGA COM1A\n| Pin Number | Label |\n| ----------- | ----------- |\n| 25 | DOWN |\n| 26 | VGA |\n| 27 | |\n| 28 | |\n| 6 | |\n| 1 | |\n| 7 | |\n| 2 | |\n| 8 | |\n| 3 | |\n| 9 | |\n| 4 | |\n| 10 | |\n| 5 | |\n| 26 | |\n| | D-SUB+H/D_9_F15 |](.axe-7420gwa-50m-22811-1000-02/fa185604674d57a2f5e305d1b76d659066a86a39ff156e88252517b59844284c.jpg)
PIN#Signal NamePIN#Signal Name
1RED13CRT_HSYNC
2GREEN14CRT_VSYNC
3BLUE15SD_CLK
4NC25GND
5GND26GND
6GND27GND
7GND28GND
8GND
9P_+5V_PSU
10GND
11NC
12SD_DATA
# 2.5G Base-T\_RJ45 + USB3.2 Gen2 x2 RJ45\_USB1 ![Left LED\nC\nRight LED\nC8\nC1\n12.63 ±0.25\n4.13 ±0.25\n19.59 ±0.25\nU18\nU14\nU13\nU9\nU5\nU4\n0.2~0.6\nAfter Pre-Soldering\n0.45 ±0.08\nUSB\n12.7~14.2\n15.80 ±0.50\n18.55 ±0.38\n0.50 ±0.08 LED](.axe-7420gwa-50m-22811-1000-02/ae472a0171382da1b273edafa60c52ccdd9e09bc5cb0f5df85dc346ea2848d6d.jpg) ![L3\nOrange(橙)\n+\n+\nGreen(綠)\nL4](.axe-7420gwa-50m-22811-1000-02/15cb873e7ba87dbb7776384ab3f2e30e56903a6edf459897d71fc4ff43b16401.jpg) ![L1\nL2\nYellow(黄)](.axe-7420gwa-50m-22811-1000-02/60784ecb057c260829e8b3367f4e1ef50052834f907eb2611da2affde65bc8e4.jpg)
Emitting Colorλp (nm)Vf @If=20mAIr @Vr=5V
Green5701.7 ~2.6 V10μA max.
Orange6051.7 ~2.6 V10μA max.
Yellow5881.7 ~2.6 V10μA max.
![RJ45_USB1\nR2 TD1+\nR3 TD1-\nR4 TD2+\nR5 TD2-\nR6 TD3+\nR7 TD3-\nR8 TD4+\nR9 TD4-\nLAN\nL1\nL2\nL3\nL4\nR1 VCC GND_1\nU1 VBUS1 USB VBUS2 U10\nU2 DM1 DM2 U11\nU3 DP1 DP2 U12\nU4 GND_2 GND_4 U13\nU5 SSRXN1 SSRXN2 U14\nU6 SSRXP1 SSRXP2 U15\nU7 GND_3 GND_5 U16\nU8 SSTXN1 SSTXN2 U17\nU9 SSTXP1 SSTXP2 U18\nG G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G\nG1 G2 G3 G4 G5 G6 G7 G8 RJ45-USB3](.axe-7420gwa-50m-22811-1000-02/b06ba2ff1da5d185380c4e5012a324524c162af0e2ece8b0e58b69f5a8d6b304.jpg)
PIN#Signal NamePIN#Signal Name
R1LAN1_CTU7GND
R2LAN1_MDI0_PU8USB31_3_TX_RE_CN_DN
R3LAN1_MDI0_NU9USB31_3_TX_RE_CN_DP
R4LAN1_MDI1_PU10USBVCC2
R5LAN1_MDI1_NU11USB2_P4_CMC_DN
R6LAN1_MDI2_PU12USB2_P4_CMC_DP
R7LAN1_MDI2_NU13GND
R8LAN1_MDI3_PU14USB31_4_RX_RE_CN_DN
R9LAN1_MDI3_NU15USB31_4_RX_RE_CN_DP
R10GNDU16GND
L1LIINK_AT_1U17USB31_4_TX_RE_CN_DN
L2ACT_AT_1U18USB31_4_TX_RE_CN_DP
L3LINK1000J_1G1GND
L4LINK2500J_1G2GND
U1USBVCC1G3GND
U2USB2_P3_CMC_DNG4GND
U3USB2_P3_CMC_DPG5GND
U4GNDG6GND
U5USB31_3_RX_RE_CN_DNG7GND
U6USB31_3_RX_RE_CN_DPG8GND
# 1G Base-T\_RJ45 + USB3.2 Gen2 x2 RJ45\_USB2 ![Left LED\nC8\nC1\nRight LED\n12.63 ±0.25\nU18\nU14\nU13\n4.13 ±0.25\n19.59 ±0.25\nU9\nU5\nU1\nU4\n0.2~0.6\nAfter Pre-Soldering\n0.45 ±0.08\nUSB\n0.50 ±0.08 LED\n12.7~14.2\n15.80 ±0.50\n18.55 ±0.38](.axe-7420gwa-50m-22811-1000-02/1de58813f5c6771e41305a6d649ab16f41829c0e316f2e47c003ae0c35c9f0e0.jpg) ![L3\nOrange(橙)\nL4\nGreen(綠)](.axe-7420gwa-50m-22811-1000-02/c4d72c4ad93a751557dadd2b8fe3f31ec5c52ccea256e3b4ee20e3e03d0b1b0d.jpg) ![L1\nYellow(黄)\nL2](.axe-7420gwa-50m-22811-1000-02/0d1273065555cc7b8b40b5a9799e50707867b17fabab41c87bafccb0a9af14b5.jpg)
Emitting Color $\lambda_{p}$ (nm)Vf @lf=20mAIr @Vr=5V
Green5701.7 ~2.6 V10μA max.
Orange6051.7 ~2.6 V10μA max.
Yellow5881.7 ~2.6 V10μA max.
<img src="images/7d62074436401ba063fab67c6d3ef562b7e3f336075f7d690c38de03ca259ee5.jpg"/>PIN#Signal NamePIN#Signal Name
R1LAN2_CTU7GND
R2LAN2_MDI0_PU8USB31_5_TX_RE_CN_DN
R3LAN2_MDI0_NU9USB31_5_TX_RE_CN_DP
R4LAN2_MDI1_PU10USBVCC4
R5LAN2_MDI1_NU11USB2_P6_CMC_DN
R6LAN2_MDI2_PU12USB2_P6_CMC_DP
R7LAN2_MDI2_NU13GND
R8LAN2_MDI3_PU14USB31_6_RX_RE_CN_DN
R9LAN2_MDI3_NU15USB31_6_RX_RE_CN_DP
R10GNDU16GND
L1LIINK_AT_2U17USB31_6_TX_RE_CN_DN
L2ACT_AT_2U18USB31_6_TX_RE_CN_DP
L3LINK1000J_2G1GND
L4LINK2500J_2G2GND
U1USBVCC3G3GND
U2USB2_P5_CMC_DNG4GND
U3USB2_P5_CMC_DPG5GND
U4GNDG6GND
U5USB31_5_RX_RE_CN_DNG7GND
U6USB31_5_RX_RE_CN_DPG8GND
# USB3.2 Gen2 Type-A USB2 ![Technical line drawing of a mechanical component with no visible text or symbols](.axe-7420gwa-50m-22811-1000-02/6596df7f9ae170b424a251cdc731f3ce81c05a7e29c358957ac6cc86e7f24b45.jpg) ![12.50±0.10\n11.10±0.10\n①\n②\n③\n④\n9 8 7 6 5\n1 2 3 4\n12.58\n7.23\n3.27\n9-2.34\n1.84±0.05\n5.12±0.10\n9-0.40±0.1\n2.00\n4.00\n7.00\n8.00\n9.18](.axe-7420gwa-50m-22811-1000-02/8f8b6ae9791c9ada49f2d1c7ca835c7beefa9128213c45ecf29469797587c055.jpg)
<img src="images/65e36a8166f37517ac1ee2d232c837a2af29b896f51e517fb9d9e40c354cbb4d.jpg"/>PIN#Signal NamePIN#Signal Name
1HUB_VBUS_USB18USB31_2_TX_RE_CN_DN
2USB2_P2_CMC_DN9USB31_2_TX_RE_CN_DP
3USB2_P2_CMC_DPG1GND
4GNDG2GND
5USB31_2_RX_RE_CN_DNG3GND
6USB31_2_RX_RE_CN_DPG4GND
7GND
# USB3.2 Gen2 Type-C USB1 ![Technical line drawing of a mechanical housing or enclosure component (no text or symbols)](.axe-7420gwa-50m-22811-1000-02/9e4d272651939beb76b4e5341e1041419a5b5663a6fa790c58c7845fcbdab6a3.jpg) ![(8.34)\nA1\nY\n0.25(2X)\n(2.54)\nB12\nH\nB1](.axe-7420gwa-50m-22811-1000-02/4b4161788fcc869a91341b2f59547440fc54dfdaea5f54167c70f4384e5e0760.jpg)
USB1A2TX1_P RX1_P B11B10TX1_N RX1_NA11B3TX2_P RX2_P A11B10TX2_N RX2_NA10A6USB2_P_T VBUS_A4 A4B7USB2_P_T USB2_N_T VBUS_A9 A9B4B6USB2_P_B VBUS_B4 B9VBUS_B9A1A5CC1 GND_A1 A12B5CC2 GND_A12 B1GND_B1 B12SBU1 GND_B12A12G3CGND_G3 1 pin CGND_G1 G1G5CGND_G5 1 pin CGND_G2G6CGND_G4 1 pinCGND_G6 N1 N2N1N261_USB_24P_G6PT_2NP_Type-C_0_BPIN#Signal NamePIN#Signal Name
A1GNDB4P_5V_VBUS_C2
A2USB31_1_TX1_CN_DPB5TYPE_C2_CC2
A3USB31_1_TX1_CN_DNB6USB2_P1_CMC_DP
A4P_5V_VBUS_C2B7USB2_P1_CMC_DN
A5TYPE_C2_CC1B8NC
A6USB2_P1_CMC_DPB9P_5V_VBUS_C2
A7USB2_P1_CMC_DNB10USB31_1_RX1_CN_DN
A8NCB11USB31_1_RX1_CN_DP
A9P_5V_VBUS_C2B12GND
A10USB31_1_RX2_CN_DNG1GND
A11USB31_1_RX2_CN_DPG2GND
A12GNDG3GND
B1GNDG4GND
B2USB31_1_TX2_CN_DPG5GND
B3USB31_1_TX2_CN_DNG6GND
# Audio Jack $3 ^ { \star } 1$ Φ3.5 AUDIO1 ![This image is a technical engineering drawing of a multi-port electronic connector, featuring three distinct sections: a 3D view, a dimensioned 2D view, and a circuit schematic.\n\n**Left Section:**\nAn isometric view of a rectangular component. It features three large circular ports stacked vertically on the front face and a row of pins extending from the bottom edge.\n\n**Center Section:**\nA 2D front view with dimensional callouts.\n* **Labels:** 'PORT 3', 'PORT 2', and 'PORT 1' identify the three circular ports.\n* **Dimensions:**\n * Top width: '12.66 (0.498)'\n * Hole sizes: '3-Ø3.60 (Ø0.142)' and '3-Ø7.00 (Ø0.276)'\n * Vertical spacing: '3.73 (.147)', '2.50±0.25 (.099±0.1)', '6.50 (0.256)', '3.00 (0.118)', '17.50 (0.689)', '28.50 (1.122)'\n * Bottom pin details: '13-0.70±0.10 (.028±0.004)', '2.00 (.079)', and spacing '13.9 (.547)'\n\n**Right Section:**\nA diagram labeled 'CIRCUIT SCHEMATIC' at the bottom. It displays three groups of electrical connections corresponding to the ports.\n* **PORT 3:** Lists pins '32', '34', '33', '35', and '1'. An arrow points from the top group to the text 'INSULATOR'. Pins 33 and 35 have switch symbols.\n* **PORT 2:** Lists pins '22', '24', '23', '25', and '1'. Pins 24 and 25 have switch symbols.\n* **PORT 1:** Lists pins '2', '4', '3', '5', and '1'. Pins 4 and 5 have switch symbols.\n* Resistor symbols are connected to the switch terminals on the right side for all three port groups.](.axe-7420gwa-50m-22811-1000-02/7b91c94f6539ab7eb37547e1c61842c9c89bd8beb8edd85b0758ce2ce7a2c231.jpg) PORT3 CIRCUIT SCHEMATIC ![AUDIO1\nINSULATOR\nblue\nG1\n32\n34\n33\n35\nG2\n34\nG3\n33\nG4\nN1\n22\n24\n23\n25\n1\n2\n4\n3\n5\nline\npink\nAJ_P3_3.5mm](.axe-7420gwa-50m-22811-1000-02/e7b47af84ecbbc3496c8fd449b9b43b05ed69bf9f1ff14932d2895e727a6ce64.jpg) ![Line-In\nFront\nSpeaker\nOut\nMIC-In](.axe-7420gwa-50m-22811-1000-02/c328a0d559b780ce763f0c404479288bb2c6d682d143fa61ac119de0058e9867.jpg)
PIN#Signal NamePIN#Signal Name
1AGND_AU32CN_LINE1_L
2CN_MIC1_L33LINE1_JD
3MIC1_JD34AGND_AU
4AGND_AU35CN_LINE1_R
5CN_MIC1_RG1AU_CHGND
22CN_FRONT_LG2AU_CHGND
23FRONT_JDG3AU_CHGND
24AGND_AUG4AU_CHGND
25CN_FRONT_R
# 5.2 Onboard Headers and Connectors # Chassis Intrusion Pin Header/Cable Definition ![The image is a diagram titled '**Front panel extension cable**'. It depicts a cable assembly connecting a large multi-pin connector on the left to five distinct 4-pin blocks on the right.\n\n**Labeled Blocks (Right Side):**\nFrom top to bottom, the text labels on the five terminal blocks are:\n1. **PWR SW+**, **PWR SW-**, **RST SW+**, **RST SW-**\n2. **PLED+**, **PLED-**, **HDD LED+**, **HDD LED-**\n3. **LAN1 LED+**, **LAN1 LED-**, **LAN2 LED+**, **LAN2 LED-**\n4. **SYSLF1+**, **SYSLF1-**, **SYSALARM+**, **SYSALARM-**\n5. **UID SW+**, **UID SW-**, **UID LED+**, **UID LED-**\n\n**Connections:**\n* A bundle of wires originates from the large connector block on the left.\n* These wires run through the central cable (represented by a hatched rectangle).\n* The cable splits into five separate groups of wires, each connecting the central cable to one of the four labeled blocks listed above.](.axe-7420gwa-50m-22811-1000-02/a84352d530ebeae1ef8f8e90dc3556bf8fb32d11b5a21118cdd228dd9dfd6415.jpg) ![20\n19\n2\n1](.axe-7420gwa-50m-22811-1000-02/cc6bc88f342e3751f240406b57e929a95add7abe8e018e663f7b1adb644abb6f.jpg)
PinSignalPinSignal
1PWR SW-2SYS_FLT-
3PWR SW+4SYS_FLT+
5PLED+6UID SW+
7PLED-8UID SW-
9LAN1_LED+10LAN2_LED-
11LAN1_LED-12LAN2_LED+
13HDD_LED_+14UID_LED-
15HDD_LED_-16UID_LED+)
17THRM_ALRM+18RST_SW+
19THRM_ALRM-20RST_SW-
# Common Redundant Power Supply CRPS1
PinSignalPinSignal
P1GNDP2PSU2_ALARM-L
P3PMBUS_CLK_OP4PSU2_PSON-L
P5PMBUS_DAT_OP6P_+3V3_DUAL
P7PWROK_PSU1_NP8NC
P9PWROK_PSU2_NP10GND
P11GNDP12CRPS_PSU1_DET#
P13NCP14CRPS_PSU2_DET#
P15EXT_SMBUS_ALERT-LP16EXT_SMBUS_SDA
P17PSU1_PSON-LP18EXT_SMBUS_SCL
P19PSU1_ALARM-LP20GND
![Pin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\nPin1\n20\n2\n3\n4\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\n16\n17\n18\n19\n20](.axe-7420gwa-50m-22811-1000-02/8745aa54eeaac9f85850814c750a44f6a7274639e21a43030a33be92e6bfaa49.jpg) # DI and DO CN21
PinSignal
P1GND
P2DO0_CN
P3DO1_CN
P4DO2_CN
P5DO3_CN
P6DI0_CN
P7DI1_CN
P8DI2_CN
P9DI3_CN
P10DIDO_PWR
![Pin1](.axe-7420gwa-50m-22811-1000-02/5b67a5951ce90b1544705a49dd4f270551cbb88a8942ea696b49d6a6ab90a3f1.jpg) # SMBus SMBus2
PinSignal
P1PMBUS_CLK_O
P2PMBUS_DAT_O
P3SMBUS1_ALERT
P4GND
P5P_+3V3_DUAL
![GND\nPin1](.axe-7420gwa-50m-22811-1000-02/d362759c0fa8f7adcd52068f0b7e6f6f088cab9f83a1aa5a206e0f3cdbeec0f1.jpg) # USB USB 3 and USB 4 ![P1\n11 10\n20 1\nP2\n11 10\n20 1\n*8mm Max\n(32.5)\n+450 ± 30\n(35)\n①\n②⑦③④](.axe-7420gwa-50m-22811-1000-02/018ff221bc2fdacd8223a9c0f54bb3e6eab2d32962fed447004d4cd3d99285ab.jpg)
PinSignalPinSignal
P1P_+5V_USB_VBUS_A3
P2USB31_9_RX_CN_DNP19P_+5V_USB_VBUS_A4
P3USB31_9_RX_CN_DPP18USB31_10_RX_CN_DN
P4GNDP17USB31_10_RX_CN_DP
P5USB31_9_TX_CN_DNP16GND
P6USB31_9_TX_CN_DPP15USB31_10_TX_CN_DN
P7GNDP14USB31_10_TX_CN_DP
P8USB2_P9_CMC_DNP13GND
P9USB2_P9_CMC_DPP12USB2_P10_CMC_DN
P10USB_OC5-LP11USB2_P10_CMC_DP
![Pin1](.axe-7420gwa-50m-22811-1000-02/c1708b95e6ac92ff033773c8647092dd8e32f8f0a4b4fb375ab9d4a846dd7ed5.jpg) # VROC CN15
PinSignal
P1GND
P2P_+3V3_S1
P3GND
P4PCH_SATA_RAID_KEY
![Pin1](.axe-7420gwa-50m-22811-1000-02/86f49ebccfbfffa8759bc6402384358b668f4f5f5c116abd3a240b8af84aa521.jpg) # COM SER 1, SER 2, SER 3, SER 4
PinSignalPinSignal
P1COM5_RS232_DCD-LP2COM5_RS232_DSR-L
P3COM5_RS232_RXDP4COM5_RS232_RTS-L
P5COM5_RS232_TXDP6COM5_RS232_CTS-L
P7COM5_RS232_DTR-LP8COM5_RS232_RI
P9GNDP10N.C
![Diagram of a control panel with labeled buttons and indicators, including a red square button and yellow circles.](.axe-7420gwa-50m-22811-1000-02/a92fbaf80749c8deee54e028d2b388886942b34e6efdfc0d9055f7bc598b7a00.jpg) # SPGIO CN7
PinSignalPinSignal
P1SATA_SDATAOUT1P2N.C
P3SATA_SLOADP4GND
P5SATA_SCLOCKP6SATA_SCLOCK
P7GNDP8SATA_SLOAD
P9N.CP10SATA_SDATAOUT0
![Pin1](.axe-7420gwa-50m-22811-1000-02/ad1ef7801148a8e0fd9d89c77e519d5d4da6509b738e6817859dd94a67388797.jpg) # Misc F\_MISC1
PinSignalPinSignal
P1GNDP2CUSTOM_LED2-L
P3PWRBTN-LP4CUSTOM_LED2_PWR(3V3)
P5S0_LED_PWR(3V3)P6FP_ID_BTN_R_N
P7S0_LED-LP8GND
P9LAN1_LED_PWR(3V3)P10LAN2_LED_ACT-L
P11LAN1_LED_ACT-LP12LAN2_LED_PWR(3V3)
P13HDD_LED_PWR (5V)P14FP_ID_LED-U
P15HDD_LED_NP16UID_LED_PWR(3V3)
P17CUSTOM_LED1_PWR(3V3)P18RSTBTN_3V3-L
P19CUSTOM_LED1-LP20GND
![Pin1](.axe-7420gwa-50m-22811-1000-02/15575bfdf3b2d51eb8ad71d748585321a0b8787d8fa5ab3b0fa54a2ca4e1843c.jpg) # SATA SATA\_CN1, SATA\_CN2, SATA\_CN3, SATA\_CN4
PinSignalPinSignal
AS1GNDBS1GND
AS2SATA_0_TX_DPBS2SATA_1_TX_DP
AS3SATA_0_TX_DNBS3SATA_1_TX_DN
AS4GNDBS4GND
AS5SATA_0_RX_DNBS5SATA_1_RX_DN
AS6SATA_0_RX_DPBS6SATA_1_RX_DP
AS7GNDBS7GND
![Pin1](.axe-7420gwa-50m-22811-1000-02/b405f0aac087c08128561bbdb4bc94800070c6ff974982b0f1a28b91f95dd7f3.jpg) # USB2 PH CN6
PinSignalPinSignal
P1P5VA_U2RT3_4P2P5VA_U2RT3_4
P3USB2_P12_CMC_DNP4USB2_P11_CMC_DN
P5USB2_P12_CMC_DPP6USB2_P11_CMC_DP
P7GNDP8GND
P9N.CP10
![8\n9\nPin1](.axe-7420gwa-50m-22811-1000-02/06fb57a4da90bbd539267263c70f9035b368af9fe86e9f6c1eed360e8f5c67a4.jpg) # eSPI PH ESPDB1
PinSignalPinSignal
P1P_+DBPWR (1V8/3V3)P2GND
P3ESPI_DB_DAT1P4ESPI_DB_DAT2
P5ESPI_DB_CLKP6ESPI_DB_DAT0
P7ESPI_DB_RST-LP8ESPI_DB_CS-L
P9ESPI_DB_DAT3P10P_+DBPWR (1V8/3V3)
![Pin1](.axe-7420gwa-50m-22811-1000-02/23f714f8347257068267fa9bc994580901c1aa5b793301a6a0c687d228df85e0.jpg) SlimSAS
PinSignalPinSignal
A1GNDB1GND
A2PCIE_21_RX_DPB2PCIE_21_TX_DP
A3PCIE_21_RX_DNB3PCIE_21_TX_DN
A4GNDB4GND
A5PCIE_22_RX_DPB5PCIE_22_TX_DP
A6PCIE_22_RX_DNB6PCIE_22_TX_DN
A7GNDB7GND
A8N.CB8N.C
A9N.CB9N.C
A10GNDB10N.C
A11CLK_SRC6_DPB11SAS_RST-L
A12CLK_SRC6_DNB12N.C
A13GNDB13GND
A14PCIE_23_RX_DPB14PCIE_23_TX_DP
A15PCIE_23_RX_DNB15PCIE_23_TX_DN
A16GNDB16GND
A17PCIE_24_RX_DPB17PCIE_24_TX_DP
A18PCIE_24_RX_DNB18PCIE_24_TX_DN
A19GNDB19GND
![A1\nB1](.axe-7420gwa-50m-22811-1000-02/53fd3f85e316ea39808d3084d573cbd3eec90ff41c2fe9d28aebf72b241a7f17.jpg) # ATX\_PCIe CN11, CN12
PinSignalPinSignal
P1P_+12V_PSUP5GND
P2P_+12V_PSUP6SENSEO
P3P_+12V_PSUP7GND
P4SENSE1P8GND
![B51A51\n8\n7\n6\n5\n4\n3\n2\n1\nN2\nN1](.axe-7420gwa-50m-22811-1000-02/048e29de19de76223bbe8ed75fed5937be16e6314ec0b1609fbbbbd06d91cb12.jpg) # ATX\_CPU CN9, CN10
PinSignalPinSignal
P1GNDP5P_+12V_PSU
P2GNDP6P_+12V_PSU
P3GNDP7P_+12V_PSU
P4GNDP8P_+12V_PSU
![Circuit board layout diagram with labeled components and connection points](.axe-7420gwa-50m-22811-1000-02/2669e60f526ae8ea3bff893c70df2f9c48a69c92ae1f38b2eb470af8e9d01b55.jpg) # ATX\_24P PCN4
PinSignalPinSignal
P1P_+3V3_PSUP13P_+3V3_PSU
P2P_+3V3_PSUP14-V12
P3GNDP15GND
P4P_+5V_PSUP16PSON-L
P5GNDP17GND
P6P_+5V_PSUP18GND
P7GNDP19GND
P8PSU_PWROKP20-V5
P9P_+5VSB_PSUP21P_+5V_PSU
P10P_+12V_PSUP22P_+5V_PSU
P11P_+12V_PSUP23P_+5V_PSU
P12P_+3V3_PSUP24GND
![Technical diagram of a circuit board layout with numbered components and labeled terminals](.axe-7420gwa-50m-22811-1000-02/c2baf70fb4f69157d128215b40abad6daf04b1e7575e98b1cf85c964833f10ce.jpg) # MCIO MCIO\_CN1, MCIO\_CN2, MCIO\_CN3,MCIO\_CN4
PinSignalPinSignal
A1GNDB1GND
A2CPU_PCIE5_PE3_RX_0_DPB2CPU_PCIE5_PE3_TX_0_C_DP
A3CPU_PCIE5_PE3_RX_0_DNB3CPU_PCIE5_PE3_TX_0_C_DN
A4GNDB4GND
A5CPU_PCIE5_PE3_RX_1_DPB5CPU_PCIE5_PE3_TX_1_C_DP
A6CPU_PCIE5_PE3_RX_1_DNB6CPU_PCIE5_PE3_TX_1_C_DN
A7GNDB7GND
A8MCIO_1A_PWRBRK_CLKREQ_NB8SMB_MCIO1A_SCL
A9MCIO_1A_SMB_ALERT_WAKE_NB9SMB_MCIO1A_SDA
A10GNDB10GND
A11CLK_100M_DB2000_MCIO_1A_DPB11MCIO1_RST0_N
A12CLK_100M_DB2000_MCIO_1A_DNB12MCIO1_PRSNT0_N
A13GNDB13GND
A14CPU_PCIE5_PE3_RX_2_DPB14CPU_PCIE5_PE3_TX_2_C_DP
A15CPU_PCIE5_PE3_RX_2_DNB15CPU_PCIE5_PE3_TX_2_C_DN
A16GNDB16GND
A17CPU_PCIE5_PE3_RX_3_DPB17CPU_PCIE5_PE3_TX_3_C_DP
A18CPU_PCIE5_PE3_RX_3_DNB18CPU_PCIE5_PE3_TX_3_C_DN
A19GNDB19GND
A20CPU_PCIE5_PE3_RX_4_DPB20CPU_PCIE5_PE3_TX_4_C_DP
A21CPU_PCIE5_PE3_RX_4_DNB21CPU_PCIE5_PE3_TX_4_C_DN
A22GNDB22GND
A23CPU_PCIE5_PE3_RX_5_DPB23CPU_PCIE5_PE3_TX_5_C_DP
A24CPU_PCIE5_PE3_RX_5_DNB24CPU_PCIE5_PE3_TX_5_C_DN
A25GNDB25GND
A26MCIO_1A_PWRBRK_CLKREQ_NB26SMB_MCIO1B_SCL
A27MCIO_1A_SMB_ALERT_WAKE_NB27SMB_MCIO1B_SDA
A28GNDB28GND
A29CLK_100M_DB2000_MCIO_1B_DPB29MCIO1_RST0_N
A30CLK_100M_DB2000_MCIO_1B_DNB30MCIO1_PRSNT0_N
A31GNDB31GND
A32CPU_PCIE5_PE3_RX_6_DPB32CPU_PCIE5_PE3_TX_6_C_DP
A33CPU_PCIE5_PE3_RX_6_DNB33CPU_PCIE5_PE3_TX_6_C_DN
A34GNDB34GND
A35CPU_PCIE5_PE3_RX_7_DPB35CPU_PCIE5_PE3_TX_7_C_DP
A36CPU_PCIE5_PE3_RX_7_DNB36CPU_PCIE5_PE3_TX_7_C_DN
A37GNDB37GND
![H-3\n1.5 mm\nH-2\n4 mm FOR RA CABLE APPLICATION ON WAITING HEIGHT\nH-1\nFOR RA CABLE APPLICATION ON WAITING HEIGHT\nA37\n1.5 mm\nABOVE L2.\nABOVE L1.](.axe-7420gwa-50m-22811-1000-02/09a83af73baa312fdf30c669c7ba816150d792a0d6fad4972c0c7150587a135c.jpg) # Door Open Connector CN19, CN20
PinSignal
P1FRONT_CHASSIS
P2GND
![Pin1](.axe-7420gwa-50m-22811-1000-02/4207cec92c708360b19393f0ace91803bed8dbb5b6aec252ce09210d91baaae8.jpg) # IPMB IPMB1
PinSignal
P1IPMB_SDA
P2IPMB_SCL
P3NC
P4GND
P5P_+3V3_DUAL
![GND\nPin1\nGND](.axe-7420gwa-50m-22811-1000-02/09f5059718f57e5cb7879064efd00180c27e99ac1e1309e166432fbbde465a7c.jpg) # CPLD\_JTAG CN28
PinSignalPinSignal
P1GNDP2P_+3V3SB
P3GNDP4FPGA_TMS
P5GNDP6FPGA_TCK
P7GNDP8FPGA_TDO
P9GNDP10FPGA_TDI
![2\n1\n1\n2\n4\n6\n3\n10\n1\n3\n5\n7\n9\n9\nG2\nA\n1](.axe-7420gwa-50m-22811-1000-02/d92403d9459a2fe70cb9318e8e73f07f9ab3a9c0b1b1ba12b4f39a51445dde8a.jpg) # Backplane PCIe Header CN24
PinSignal
P1P_3V3_DUAL
P2PCIE_HP_SCL
P3PCIE_HP_SDA
P4PCIE_HP_ALERT-L
P5GND
![Pin1\nGND\nGND](.axe-7420gwa-50m-22811-1000-02/2406aa241af12601cf7a6fd3f66ae5b9d638daa14a897e66f45fa4f048172ed1.jpg) # MIPI60 ![2\n60\nN1\n61\n52\n63\n54\n1\n59\nN2\n60\n1](.axe-7420gwa-50m-22811-1000-02/6e3be436e7d12e681765491b22759c6ffd29a75491617f262c9422beb4e1a932.jpg) # Debug UART CN27
PinSignalPinSignal
P1P_+1V8_TPMP2GND
P3CN_UART_RTSP4CN_UART_TXD
P5CN_UART_CTSP6CN_UART_RXD
![Flowchart](.axe-7420gwa-50m-22811-1000-02/33ff6cac9660c48a62018733398b618df3b4e159b62205df13c9b1b7ef22eee4.jpg) # FAN Connector FAN\_\*
PinSignal
P1GND
P2P_12V_FAN_*
P3*_FAN_TACH
P4*U_PWMOUT
![Pure electrical circuit lines without any symbols](.axe-7420gwa-50m-22811-1000-02/ec1bb103be512ef8c898ead98ea9ab09737fdefc2946030e1af982057f827753.jpg) # TPM Connector TPM\_CN1
PinSignalRemarkPinSignal
P1GNDP2SPI_CPU0_TPM_CS-L
P3TPM_IRQ-LP4SPI_CPU0_TPM_MISO
P5TPM_PRESNT-LP6SPI_CPU0_TPM_MOSI
P7LPC_RST-LP8SPI_CPU0_TPM_CLK
P9P_+1V8_TPMPWRP10GND
![GND\nTM_WT_C1K\nTM_WT_M2K\nTM_WT_M3K\nTM_WT_PCA\nPin1\nGND](.axe-7420gwa-50m-22811-1000-02/302dd0c1fa5517de516553ed7a39e09fd7833dec922d997cc6838980042287c8.jpg) # 5.3 Jumper and Switch Settings # Jumper and Switch Locations ![CN26\nCN8\nCN1\nSW3\nCN22\nCN17\nCN18\nCN16\nCN25\nCN23](.axe-7420gwa-50m-22811-1000-02/afeb7a5304d229e16e20b81137ea83195c2077860e30b0d55aa6affcc5251e45.jpg) Figure 6: Jumper and switch locations # Clear CMOS Header
CN1Settings
1-2N/A (Default)
2-3Clear CMOS
<img src="images/f69ca36dc6a21e736a4eb09fe2b1672460dbbbca5bd33e117f7f8c3824097f6d.jpg"/>PIN#Signal Name
1NC
2PCH_RTCRST-L
3CLR_CMOS (1K ohm to GND)
# ME Reset Header
CN8Settings
1-2N/A (Default)
2-3Reset ME (Please do not use except special situation)
PIN#Signal Name
1NC
2PCH_SRTCRST-L
31K ohm to GND
# COM3 Power Supply Selection Header
CN16Settings
NCNo Power Supply (Default)
1-25V Power Supply
2-312V Power Supply
<img src="images/e8b8b494c8bbba11aefd77eaff2abf2daa6ea129834f8b504e5edeba65cdd23f.jpg"/>PIN#Signal Name
1P_+5V_PSU
2COM3 Power Supply
3P_+12V_PSU
# COM4 Power Supply Selection Header
CN17Settings
NCNo Power Supply (Default)
1-25V Power Supply
2-312V Power Supply
<img src="images/2d30fc252614f6d488a17041d8940de0668238d5662fb6459105206f5c92c79a.jpg"/>PIN#Signal Name
1P_+5V_PSU
2COM4 Power Supply
3P_+12V_PSU
# Flash Descriptor Security Override (FDSO) CN18
CN18Settings
1-2Enable FDSO
2-3Disable FDSO (ME Lock) (Default)
![Based on the visual evidence, here is an accurate and concise description of the flowchart:\n\n**Labeled Blocks and Shapes:**\n\n* **Left Column:** There are three blue rectangular blocks arranged vertically on the left side (two near the top, one below the main central block). Each blue block contains two purple squares side-by-side. Inside each purple square is a white vertical bar resembling the number '1'.\n* **Central Structure:** A large yellow rectangular frame dominates the center. Inside this frame:\n * **Left Section:** A nested shape consisting of a yellow square border, a green square border inside it, and a central yellow circle containing a '1'.\n * **Right Section:** Two yellow circles side-by-side, each containing a '1'.\n* **Right Column:** On the far right, there is a blue rectangular block containing two purple squares stacked vertically.\n* **Bottom Row:** Below the central area, there is a row of three items:\n * A purple rectangle.\n * A blue square outline.\n * A purple rectangle labeled with the text 'GRID'.\n\n**Connections:**\n\n* **Arrow:** A yellow arrow points from the left side (positioned between the top-left blocks) towards the large yellow central frame, indicating flow into the system. There are no other explicit connecting lines between the blocks.](.axe-7420gwa-50m-22811-1000-02/cb74742f2f94fe396385640ec329c1b973d2e39df1cc235260091a48d0fc9f95.jpg)
PIN#Signal Name
1+VCCPGPPDR_3P3_1P8
2FLASH_DES_STRAP
320K ohm to GND
# COM5 Power Supply Selection Header
CN22Settings
NCNo Power Supply (Default)
1-25V Power Supply
2-312V Power Supply
<img src="images/f942b500e09f506815bfcdd3e1d7f0556eea4db9d4eb3f63acb39986c0a08c9e.jpg"/>PIN#Signal Name
1P_+5V_PSU
2COM5 Power Supply
3P_+12V_PSU
# Force Enable S0 Power CN23 (Debug only, do not use)
CN23Settings
1-2N/A (Default)
2-3Force Enable S0 Power (Debug only, do not use)
![Based on the provided image, here is the description of the flowchart/block diagram:\n\n**Labeled Blocks:**\n* **Top Left:** A vertical stack of three purple rectangles. The top rectangle is labeled **'TOP'**. The middle and bottom rectangles are unlabeled.\n* **Top Right:** A single purple rectangle labeled **'REMAIN'**.\n* **Center Top:** A large yellow rectangle containing three internal elements:\n * A circle labeled **'00'**.\n * An unlabeled circle.\n * An unlabeled square inside a square.\n* **Bottom Row:** Four purple squares arranged horizontally on a blue line. The first three squares are labeled **'01'**. The fourth square (far right) is unlabeled.\n\n**Connections:**\n* **Downward Arrows:** Two blue, downward-pointing arrows originate from the bottom edge of the central yellow rectangle. One points from the center towards the first **'01'** block, and the other points from the right side towards the third **'01'** block.\n* **Bus/Line Structure:** A blue wire-like structure connects the components.\n * A vertical blue line connects the left stack (starting from the **'TOP'** block).\n * A horizontal blue line connects the bottom row of squares.\n * A vertical blue line connects the **'REMAIN'** block to the bottom right area (above the unlabeled square).\n* **Side Arrow:** A yellow triangle pointing to the right is positioned between the central yellow rectangle and the **'REMAIN'** block.](.axe-7420gwa-50m-22811-1000-02/15871e697bafdbb2e3cad24a48db332717531b2e0a69b10a1c0370e13f3e82ec.jpg)
PIN#Signal Name
1NC
2PSON-L
3GND
# COM2 Power Supply Selection Header
CN25Settings
NCNo Power Supply (Default)
1-25V Power Supply
2-312V Power Supply
![Pure electrical circuit lines without any symbols](.axe-7420gwa-50m-22811-1000-02/552fd9bd2a08d2e8de5b2b4917cfba13282c4204b3f16bf9eb574c2b170322e5.jpg)
PIN#Signal Name
1P_+5V_PSU
2COM2 Power Supply
3P_+12V_PSU
# COM1 Power Supply Selection Header
CN26Setting
NCNo Power Supply (Default)
1-25V Power Supply
2-312V Power Supply
![Diagram of a traffic light system with labeled components and colored indicators](.axe-7420gwa-50m-22811-1000-02/96c6dc22cade6314f49f66e4de7963a7427493655fb756d8025b2bcbf6fb8972.jpg)
PIN#Signal Name
1P_+5V_PSU
2COM1 Power Supply
3P_+12V_PSU
RS-485 Fail-Safe (Switch)
SW3Setting OFFSetting ON (Default)
1-8COM1 RS-485 Fail-Safe DisableCOM1 RS-485 Fail-Safe Enable
2-7
3-6COM2 RS-485 Fail-Safe DisableCOM2 RS-485 Fail-Safe Enable
4-5
![M1908F14\nM1908F24\nM1908F35\nM1908F47](.axe-7420gwa-50m-22811-1000-02/79fc7f7e38b377e49f3cd55b8359d1ab2252f0e89475e150578f9cce05c92263.jpg)
PIN#Signal NamePIN#Signal Name
1COM1_RXD_B51K ohm to GND
2COM1_DCD-L_B61K ohm to P_+5V_PSU
3COM2_RXD_B71K ohm to GND
4COM2_DCD-L_B81K ohm to P_+5V_PSU
# 5.4 Expansion Slots # Expansion Slot Block Diagram Project Name: AXE-7400 PC BoardName:37233 Rev.A1 ![The diagram depicts a block labeled 'Cle extension board_1' containing several internal components and external connections.\n\n**Internal Blocks:**\n* **Top Row:** Four dashed rectangular blocks arranged horizontally:\n * 'PCle_CN1' (subtext: 'PCle Gen5 X8')\n * 'PCle_CN2' (subtext: 'PCle Gen5X8')\n * 'PCle_CN3' (subtext: 'PCle Gen5X4')\n * 'PCle_CN4' (subtext: 'PCle Gen5 X4')\n* **Middle Row:** Three solid rectangular blocks: 'MCIO_1', 'MCIO_2', and 'MCIO_3'.\n* **Bottom Left:** A block containing 'FAN_CN1' and 'FAN_CN2'. To its right is a block labeled 'U15 NCT7363Y FAN CTRL IC' with an arrow pointing towards the fan connector block.\n* **Bottom Center:** Two blocks labeled 'PCle PWR_1' and 'PCle PWR_2'.\n* **Bottom Right:** A single block labeled 'SMBUS1'.\n\n**Connections:**\n* **Fan Outputs:** Two arrows point left from 'FAN_CN1' and 'FAN_CN2' towards the text 'SYSTEM_FAN' (which appears twice on the left side).\n* **Power Input:** An arrow originates from the text 'P_+V12_PSU' at the bottom and splits to point upwards into both 'PCle PWR_1' and 'PCle PWR_2'.\n* **MB Connection:** Four lines connect 'SMBUS1' to an external block labeled 'MB' on the right:\n * 'P_+3V3_BMC' (arrow points right towards MB)\n * 'PMBus_ALERT#_R_PSU' (arrow points right towards MB)\n * 'BMC_SMBUS_DAT' (arrow points left towards SMBUS1)\n * 'BMC_SMBUS_CLK' (arrow points left towards SMBUS1)](.axe-7420gwa-50m-22811-1000-02/32a8cb8617e7bd9e02bca6806334970ec0ac9c9b492cae6b4163f61544a9ec5c.jpg) Figure 7: Expansion slot block diagram # MCIO Connectors Location: MCIO\_CN1; MCIO\_CN2; MCIO\_CN3 Description: MCIO x8, FML 74P RT ![Technical line drawing of a mechanical component with internal channels and mounting brackets (no text or symbols)](.axe-7420gwa-50m-22811-1000-02/db33addc273d29147eaf4e22433ab3954fc5d8b674bca4b3dc00ef4735c23cc9.jpg) ![22.48\n21.60\n1.00±0.20\nB1\nA1\n0.22\n0.15\n0.60\n24.445\n(2X)25.50\n3.05±0.88\nCENTER HEIGHT\nA37\n0.10\nALL SMT TAIL](.axe-7420gwa-50m-22811-1000-02/c40cd5f9b9e387b73da2c47e60e3a07f93c6922a141e0eb7ec31cd8da97aecbb.jpg) MCIO\_CN1
SignalPinPinSignal
GNDA1B1GND
MCIO_PCIE5_PE1_RX_0_DPA2B2MCIO_PCIE5_PE1_TX_0_DP
MCIO_PCIE5_PE1_RX_0_DNA3B3MCIO_PCIE5_PE1_TX_0_DN
GNDA4B4GND
MCIO_PCIE5_PE1_RX_1_DPA5B5MCIO_PCIE5_PE1_TX_1_DP
MCIO_PCIE5_PE1_RX_1_DNA6B6MCIO_PCIE5_PE1_TX_1_DN
GNDA7B7GND
MCIO_1A_PWRBRK_CLKREQ_NA8B8SMB_MCIO1A_SCL
MCIO_1A_SMB_ALERT_WAKE_NA9B9SMB_MCIO1A_SDA
GNDA10B10GND
CLK0_100M_MCIO_1_DPA11B11MCIO_1A_RST_N
CLK0_100M_MCIO_1_DNA12B12MCIO_1A_PRSNT_N
GNDA13B13GND
MCIO_PCIE5_PE1_RX_2_DPA14B14MCIO_PCIE5_PE1_TX_2_DP
MCIO_PCIE5_PE1_RX_2_DNA15B15MCIO_PCIE5_PE1_TX_2_DN
GNDA16B16GND
MCIO_PCIE5_PE1_RX_3_DPA17B17MCIO_PCIE5_PE1_TX_3_DP
MCIO_PCIE5_PE1_RX_3_DNA18B18MCIO_PCIE5_PE1_TX_3_DN
GNDA19B19GND
MCIO_PCIE5_PE1_RX_4_DPA20B20MCIO_PCIE5_PE1_TX_4_DP
MCIO_PCIE5_PE1_RX_4_DNA21B21MCIO_PCIE5_PE1_TX_4_DN
GNDA22B22GND
MCIO_PCIE5_PE1_RX_5_DPA23B23MCIO_PCIE5_PE1_TX_5_DP
MCIO_PCIE5_PE1_RX_5_DNA24B24MCIO_PCIE5_PE1_TX_5_DN
GNDA25B25GND
NCA26B26NC
NCA27B27NC
GNDA28B28GND
NCA29B29NC
NCA30B30NC
GNDA31B31GND
MCIO_PCIE5_PE1_RX_6_DPA32B32MCIO_PCIE5_PE1_TX_6_DP
MCIO_PCIE5_PE1_RX_6_DNA33B33MCIO_PCIE5_PE1_TX_6_DN
GNDA34B34GND
MCIO_PCIE5_PE1_RX_7_DPA35B35MCIO_PCIE5_PE1_TX_7_DP
MCIO_PCIE5_PE1_RX_7_DNA36B36MCIO_PCIE5_PE1_TX_7_DN
GNDA37B37GND
GNDG1N1NC
GNDG2N2NC
GNDG3
GNDG4
MCIO\_CN2
SignalPinPinSignal
GNDA1B1GND
MCIO_PCIE5_PE2_RX_0_DPA2B2MCIO_PCIE5_PE2_TX_0_DP
MCIO_PCIE5_PE2_RX_0_DNA3B3MCIO_PCIE5_PE2_TX_0_DN
GNDA4B4GND
MCIO_PCIE5_PE2_RX_1_DPA5B5MCIO_PCIE5_PE2_TX_1_DP
MCIO_PCIE5_PE2_RX_1_DNA6B6MCIO_PCIE5_PE2_TX_1_DN
GNDA7B7GND
MCIO_2A_PWRBRK_CLKREQ_NA8B8SMB_MCIO2A_SCL
MCIO_2A_SMB_ALERT_WAKE_NA9B9SMB_MCIO2A_SDA
GNDA10B10GND
CLK0_100M_MCIO_2_DPA11B11MCIO_2A_RST_N
CLK0_100M_MCIO_2_DNA12B12MCIO_2A_PRSNT_N
GNDA13B13GND
MCIO_PCIE5_PE2_RX_2_DPA14B14MCIO_PCIE5_PE2_TX_2_DP
MCIO_PCIE5_PE2_RX_2_DNA15B15MCIO_PCIE5_PE2_TX_2_DN
GNDA16B16GND
MCIO_PCIE5_PE2_RX_3_DPA17B17MCIO_PCIE5_PE2_TX_3_DP
MCIO_PCIE5_PE2_RX_3_DNA18B18MCIO_PCIE5_PE2_TX_3_DN
GNDA19B19GND
MCIO_PCIE5_PE2_RX_4_DPA20B20MCIO_PCIE5_PE2_TX_4_DP
MCIO_PCIE5_PE2_RX_4_DNA21B21MCIO_PCIE5_PE2_TX_4_DN
GNDA22B22GND
MCIO_PCIE5_PE2_RX_5_DPA23B23MCIO_PCIE5_PE2_TX_5_DP
MCIO_PCIE5_PE2_RX_5_DNA24B24MCIO_PCIE5_PE2_TX_5_DN
GNDA25B25GND
NCA26B26NC
NCA27B27NC
GNDA28B28GND
NCA29B29NC
NCA30B30NC
GNDA31B31GND
MCIO_PCIE5_PE2_RX_6_DPA32B32MCIO_PCIE5_PE2_TX_6_DP
MCIO_PCIE5_PE2_RX_6_DNA33B33MCIO_PCIE5_PE2_TX_6_DN
GNDA34B34GND
MCIO_PCIE5_PE2_RX_7_DPA35B35MCIO_PCIE5_PE2_TX_7_DP
MCIO_PCIE5_PE2_RX_7_DNA36B36MCIO_PCIE5_PE2_TX_7_DN
GNDA37B37GND
GNDG1N1NC
GNDG2N2NC
GNDG3
GNDG4
MCIO\_CN3
SignalPinPinSignal
GNDA1B1GND
MCIO_PCIE5_PE3_RX_0_DPA2B2MCIO_PCIE5_PE3_TX_0_DP
MCIO_PCIE5_PE3_RX_0_DNA3B3MCIO_PCIE5_PE3_TX_0_DN
GNDA4B4GND
MCIO_PCIE5_PE3_RX_1_DPA5B5MCIO_PCIE5_PE3_TX_1_DP
MCIO_PCIE5_PE3_RX_1_DNA6B6MCIO_PCIE5_PE3_TX_1_DN
GNDA7B7GND
MCIO_3A_PWRBRK_CLKREQ_NA8B8SMB_MCIO3A_SCL
MCIO_3A_SMB_ALERT_WAKE_NA9B9SMB_MCIO3A_SDA
GNDA10B10GND
CLK0_100M_MCIO_3_DPA11B11MCIO_3A_RST_N
CLK0_100M_MCIO_3_DNA12B12MCIO_3A_PRSNT_N
GNDA13B13GND
MCIO_PCIE5_PE3_RX_2_DPA14B14MCIO_PCIE5_PE3_TX_2_DP
MCIO_PCIE5_PE3_RX_2_DNA15B15MCIO_PCIE5_PE3_TX_2_DN
GNDA16B16GND
MCIO_PCIE5_PE3_RX_3_DPA17B17MCIO_PCIE5_PE3_TX_3_DP
MCIO_PCIE5_PE3_RX_3_DNA18B18MCIO_PCIE5_PE3_TX_3_DN
GNDA19B19GND
MCIO_PCIE5_PE3_RX_4_DPA20B20MCIO_PCIE5_PE3_TX_4_DP
MCIO_PCIE5_PE3_RX_4_DNA21B21MCIO_PCIE5_PE3_TX_4_DN
GNDA22B22GND
MCIO_PCIE5_PE3_RX_5_DPA23B23MCIO_PCIE5_PE3_TX_5_DP
MCIO_PCIE5_PE3_RX_5_DNA24B24MCIO_PCIE5_PE3_TX_5_DN
GNDA25B25GND
MCIO_3B_PWRBRK_CLKREQ_NA26B26SMB_MCIO3B_SCL
MCIO_3B_SMB_ALERT_WAKE_NA27B27SMB_MCIO3B_SDA
GNDA28B28GND
CLK1_100M_MCIO_3_DPA29B29MCIO_3B_RST_N
CLK1_100M_MCIO_3_DNA30B30MCIO_3B_PRSNT_N
GNDA31B31GND
MCIO_PCIE5_PE3_RX_6_DPA32B32MCIO_PCIE5_PE3_TX_6_DP
MCIO_PCIE5_PE3_RX_6_DNA33B33MCIO_PCIE5_PE3_TX_6_DN
GNDA34B34GND
MCIO_PCIE5_PE3_RX_7_DPA35B35MCIO_PCIE5_PE3_TX_7_DP
MCIO_PCIE5_PE3_RX_7_DNA36B36MCIO_PCIE5_PE3_TX_7_DN
GNDA37B37GND
GNDG1N1NC
GNDG2N2NC
GNDG3
GNDG4
# PCIe Slots (PCIe x8) Location: PCIE\_CN1; PCIE\_CN2 Description: PCIe Slot 98P x8 ST ![Technical line drawing of a rectangular electronic component with mounting holes and a recessed slot (no text or symbols)](.axe-7420gwa-50m-22811-1000-02/6fbfc5d465eff65ad9469b597f347ade97bb972596abe4e31622c1249a62d2aa.jpg) PCIE\_CN1
SignalPinPinSignal
P_+12V_PSUB1A1MCIO_1A_PWRBRK_CLKREQ_N
P_+12V_PSUB2A2P_+12V_PSU
P_+12V_PSUB3A3P_+12V_PSU
GNDB4A4GND
SMB_MCIO1A_SCLB5A5NC
SMB_MCIO1A_SDAB6A6NC
GNDB7A7NC
P_+3V3_S0B8A8NC
NCB9A9P_+3V3_S0
P_+3V3_S0B10A10P_+3V3_S0
MCIO_1A_SMB_ALERT_WAKE_NB11A11MCIO_1A_RST_N
Separation Key
NCB12A12GND
GNDB13A13CLK_100M_MCIO_1A_DP
MCIO_PCIE5_PE1_TX_0_DPB14A14CLK_100M_MCIO_1A_DN
MCIO_PCIE5_PE1_TX_0_DNB15A15GND
GNDB16A16MCIO_PCIE5_PE1_RX_0_DP
MCIO_1A_PRSNT_NB17A17MCIO_PCIE5_PE1_RX_0_DN
GNDB18A18GND
MCIO_PCIE5_PE1_TX_1_DPB19A19NC
MCIO_PCIE5_PE1_TX_1_DNB20A20GND
GNDB21A21MCIO_PCIE5_PE1_RX_1_DP
GNDB22A22MCIO_PCIE5_PE1_RX_1_DN
MCIO_PCIE5_PE1_TX_2_DPB23A23GND
MCIO_PCIE5_PE1_TX_2_DNB24A24GND
GNDB25A25MCIO_PCIE5_PE1_RX_2_DP
GNDB26A26MCIO_PCIE5_PE1_RX_2_DN
MCIO_PCIE5_PE1_TX_3_DPB27A27GND
MCIO_PCIE5_PE1_TX_3_DNB28A28GND
GNDB29A29MCIO_PCIE5_PE1_RX_3_DP
NCB30A30MCIO_PCIE5_PE1_RX_3_DN
MCIO_1A_PRSNT_NB31A31GND
GNDB32A32NC
MCIO_PCIE5_PE1_TX_4_DPB33A33NC
MCIO_PCIE5_PE1_TX_4_DNB34A34GND
GNDB35A35MCIO_PCIE5_PE1_RX_4_DP
GNDB36A36MCIO_PCIE5_PE1_RX_4_DN
MCIO_PCIE5_PE1_TX_5_DPB37A37GND
MCIO_PCIE5_PE1_TX_5_DNB38A38GND
GNDB39A39MCIO_PCIE5_PE1_RX_5_DP
GNDB40A40MCIO_PCIE5_PE1_RX_5_DN
MCIO_PCIE5_PE1_TX_6_DPB41A41GND
MCIO_PCIE5_PE1_TX_6_DNB42A42GND
GNDB43A43MCIO_PCIE5_PE1_RX_6_DP
GNDB44A44MCIO_PCIE5_PE1_RX_6_DN
MCIO_PCIE5_PE1_TX_7_DPB45A45GND
MCIO_PCIE5_PE1_TX_7_DNB46A46GND
GNDB47A47MCIO_PCIE5_PE1_RX_7_DP
MCIO_1A_PRSNT_NB48A48MCIO_PCIE5_PE1_RX_7_DN
GNDB49A49GND
NCN1N2NC
GNDG1G2GND
PCIE\_CN2
SignalPinPinSignal
P_+12V_PSUB1A1MCIO_2A_PWRBRK_CLKREQ_N
P_+12V_PSUB2A2P_+12V_PSU
P_+12V_PSUB3A3P_+12V_PSU
GNDB4A4GND
SMB_MCIO2A_SCLB5A5NC
SMB_MCIO2A_SDAB6A6NC
GNDB7A7NC
P_+3V3_S0B8A8NC
NCB9A9P_+3V3_S0
P_+3V3_S0B10A10P_+3V3_S0
MCIO_2A_SMB_ALERT_WAKE_NB11A11MCIO_2A_RST_N
Separation Key
NCB12A12GND
GNDB13A13CLK_100M_MCIO_2A_DP
MCIO_PCIE5_PE2_TX_0_DPB14A14CLK_100M_MCIO_2A_DN
MCIO_PCIE5_PE2_TX_0_DNB15A15GND
GNDB16A16MCIO_PCIE5_PE2_RX_0_DP
MCIO_2A_PRSNT_NB17A17MCIO_PCIE5_PE2_RX_0_DN
GNDB18A18GND
MCIO_PCIE5_PE2_TX_1_DPB19A19NC
MCIO_PCIE5_PE2_TX_1_DNB20A20GND
GNDB21A21MCIO_PCIE5_PE2_RX_1_DP
GNDB22A22MCIO_PCIE5_PE2_RX_1_DN
MCIO_PCIE5_PE2_TX_2_DPB23A23GND
MCIO_PCIE5_PE2_TX_2_DNB24A24GND
GNDB25A25MCIO_PCIE5_PE2_RX_2_DP
GNDB26A26MCIO_PCIE5_PE2_RX_2_DN
MCIO_PCIE5_PE2_TX_3_DPB27A27GND
MCIO_PCIE5_PE2_TX_3_DNB28A28GND
GNDB29A29MCIO_PCIE5_PE2_RX_3_DP
NCB30A30MCIO_PCIE5_PE2_RX_3_DN
MCIO_2A_PRSNT_NB31A31GND
GNDB32A32NC
MCIO_PCIE5_PE2_TX_4_DPB33A33NC
MCIO_PCIE5_PE2_TX_4_DNB34A34GND
GNDB35A35MCIO_PCIE5_PE2_RX_4_DP
GNDB36A36MCIO_PCIE5_PE2_RX_4_DN
MCIO_PCIE5_PE2_TX_5_DPB37A37GND
MCIO_PCIE5_PE2_TX_5_DNB38A38GND
GNDB39A39MCIO_PCIE5_PE2_RX_5_DP
GNDB40A40MCIO_PCIE5_PE2_RX_5_DN
MCIO_PCIE5_PE2_TX_6_DPB41A41GND
MCIO_PCIE5_PE2_TX_6_DNB42A42GND
GNDB43A43MCIO_PCIE5_PE2_RX_6_DP
GNDB44A44MCIO_PCIE5_PE2_RX_6_DN
MCIO_PCIE5_PE2_TX_7_DPB45A45GND
MCIO_PCIE5_PE2_TX_7_DNB46A46GND
GNDB47A47MCIO_PCIE5_PE2_RX_7_DP
MCIO_2A_PRSNT_NB48A48MCIO_PCIE5_PE2_RX_7_DN
GNDB49A49GND
NCN1N2NC
GNDG1G2GND
# PCIe Slots (PCIe x4) Location: PCIE\_CN3; PCIE\_CN4 Description: PCIe Slot 64P x4 ST ![PCI-E 5.0](.axe-7420gwa-50m-22811-1000-02/6ad9a35321354f29f9137071dc35781e2908c3ae70f10bd94a6f8c3b9f872570.jpg) PCIE\_CN3
SignalPinPinSignal
P_+12V_PSUB1A1MCIO_3A_PWRBRK_CLKREQ_N
P_+12V_PSUB2A2P_+12V_PSU
P_+12V_PSUB3A3P_+12V_PSU
GNDB4A4GND
SMB_MCIO3A_SCLB5A5NC
SMB_MCIO3A_SDAB6A6NC
GNDB7A7NC
P_+3V3_S0B8A8NC
NCB9A9P_+3V3_S0
P_+3V3_S0B10A10P_+3V3_S0
MCIO_3A_SMB_ALERT_WAKE_NB11A11MCIO_3A_RST_N
Separation Key
NCB12A12GND
GNDB13A13CLK_100M_MCIO_3A_DP
MCIO_PCIE5_PE3_TX_0_DPB14A14CLK_100M_MCIO_3A_DN
MCIO_PCIE5_PE3_TX_0_DNB15A15GND
GNDB16A16MCIO_PCIE5_PE3_RX_0_DP
MCIO_3A_PRSNT_NB17A17MCIO_PCIE5_PE3_RX_0_DN
GNDB18A18GND
MCIO_PCIE5_PE3_TX_1_DPB19A19NC
MCIO_PCIE5_PE3_TX_1_DNB20A20GND
GNDB21A21MCIO_PCIE5_PE3_RX_1_DP
GNDB22A22MCIO_PCIE5_PE3_RX_1_DN
MCIO_PCIE5_PE3_TX_2_DPB23A23GND
MCIO_PCIE5_PE3_TX_2_DNB24A24GND
GNDB25A25MCIO_PCIE5_PE3_RX_2_DP
GNDB26A26MCIO_PCIE5_PE3_RX_2_DN
MCIO_PCIE5_PE3_TX_3_DPB27A27GND
MCIO_PCIE5_PE3_TX_3_DNB28A28GND
GNDB29A29MCIO_PCIE5_PE3_RX_3_DP
NCB30A30MCIO_PCIE5_PE3_RX_3_DN
MCIO_3A_PRSNT_NB31A31GND
GNDB32A32NC
NCN1N2NC
GNDG1G2GND
PCIE\_CN4
SignalPinPinSignal
P_+12V_PSUB1A1MCIO_3B_PWRBRK_CLKREQ_N
P_+12V_PSUB2A2P_+12V_PSU
P_+12V_PSUB3A3P_+12V_PSU
GNDB4A4GND
SMB_MCIO3B_SCLB5A5NC
SMB_MCIO3B_SDAB6A6NC
GNDB7A7NC
P_+3V3_S0B8A8NC
NCB9A9P_+3V3_S0
P_+3V3_S0B10A10P_+3V3_S0
MCIO_3B_SMB_ALERT_WAKE_NB11A11MCIO_3B_RST_N
Separation Key
NCB12A12GND
GNDB13A13CLK_100M_MCIO_3B_DP
MCIO_PCIE5_PE3_TX_4_DPB14A14CLK_100M_MCIO_3B_DN
MCIO_PCIE5_PE3_TX_4_DNB15A15GND
GNDB16A16MCIO_PCIE5_PE3_RX_4_DP
MCIO_3B_PRSNT_NB17A17MCIO_PCIE5_PE3_RX_4_DN
GNDB18A18GND
MCIO_PCIE5_PE3_TX_5_DPB19A19NC
MCIO_PCIE5_PE3_TX_5_DNB20A20GND
GNDB21A21MCIO_PCIE5_PE3_RX_5_DP
GNDB22A22MCIO_PCIE5_PE3_RX_5_DN
MCIO_PCIE5_PE3_TX_6_DPB23A23GND
MCIO_PCIE5_PE3_TX_6_DNB24A24GND
GNDB25A25MCIO_PCIE5_PE3_RX_6_DP
GNDB26A26MCIO_PCIE5_PE3_RX_6_DN
MCIO_PCIE5_PE3_TX_7_DPB27A27GND
MCIO_PCIE5_PE3_TX_7_DNB28A28GND
GNDB29A29MCIO_PCIE5_PE3_RX_7_DP
NCB30A30MCIO_PCIE5_PE3_RX_7_DN
MCIO_3B_PRSNT_NB31A31GND
GNDB32A32NC
NCN1N2NC
GNDG1G2GND
# PCIe 12V Power Connectors Location: CN1; CN2 Description: Power Header ML 2x4P ![VIEW A\n9.60\n1.00\n4.20\nVIEW B\nR0.30\n3.20±0.20\n4.20\n(PIN No-1)*4.2](.axe-7420gwa-50m-22811-1000-02/50116ba63b5c0c8a1ef8cf977dd1dc5ae8f195a27563feab5d421a489dcd05cd.jpg) ![3.17\n11.40\n2.90\nDIM.A\n7.30\n4.20](.axe-7420gwa-50m-22811-1000-02/a33d6b7b9190acc0f478e21924726731036af09724150580f3c072bbf3a03720.jpg) CN1
<img src="images/76eacc32e3029aaa29b5761cadfd9fbd9d9bef636d59fd242998baa98d59b7d8.jpg"/>PIN#Signal NamePIN#Signal Name
1P_+12V_PSU5CN1_SENSE0(10K ohm to GND)
2P_+12V_PSU6GND
3P_+12V_PSU7GND
4CN1_SENSE1(10K ohm to GND)8GND
CN2
<img src="images/1cfd44871971624c03122de21e75ba5cfe559efc168b3acfd2b5c5d151c74d29.jpg"/>PIN#Signal NamePIN#Signal Name
1P_+12V_PSU5CN2_SENSE0(10K ohm to GND)
2P_+12V_PSU6GND
3P_+12V_PSU7GND
4CN2_SENSE1(10K ohm to GND)8GND
# System Fan Connectors Location: FAN\_CN1; FAN\_CN2 Description: WAFER ML 1x4P ST D2.54 ![Circuit 1\n2.54±0.10\n7.62±0.20](.axe-7420gwa-50m-22811-1000-02/9a584e248f8ac325af1bbfa7cbf4bf4c1fcc2a66cf694bb0c1f2ee2b6aa8f761.jpg) ![Isometric line drawing of a mechanical component with multiple pins (no text or symbols)](.axe-7420gwa-50m-22811-1000-02/f1739d8175303eada27c3478c4cf700f8be618dafd4e263855f000ad848ed36c.jpg) # FAN\_CN1 ![FAN_CN1](.axe-7420gwa-50m-22811-1000-02/7325f7ce1e4b70a1325ae5ca0f8020f252a52f8232f39ff649a81bb5802934da.jpg)
PIN#Signal Name
1GND
2P_+12V_FAN1
3FAN1_PWM_IN
4FAN1_PWM_OUT
# FAN\_CN2 ![FAN_CN2](.axe-7420gwa-50m-22811-1000-02/af673d61f4e9940824a2dd6436ec1db436cbbdc3ab1ba69b1d29b1ab2f38ca7a.jpg)
PIN#Signal Name
1GND
2P_+12V_FAN2
3FAN2_PWM_IN
4FAN2_PWM_OUT
# SMBus Connector Location: SMBUS1 Description: WAFER ML 1x5P ST D1.0 ![Isometric line drawing of a rectangular electronic component with internal slots and mounting holes (no text or symbols)](.axe-7420gwa-50m-22811-1000-02/e88ca130f3ad6e733269e0b4c086322148774f0e3029420c5da5cba005b2bbb5.jpg) # SMBUS1
SMBUS1 GND BMC_SMBCCLK BNC_SMBCCLK BNC_SMBCCLK GND PART BNC GNDPIN#Signal Name
1BMC_SMBCLK
2BMC_SMBDAT
3BMC_ALERT
4GND
5P_+3V3_BMC
G1GND
G2GND
This page intentionally left blank. # Getting Started # 6.1 Installing Memory Modules Memory modules must be populated as shown (slots $1 > 2 > 3 > 4 > 5 > 6 )$ . ![Technical diagram of a computer motherboard with labeled components and numbered parts](.axe-7420gwa-50m-22811-1000-02/6163ea94bad021a42ad06ac3aed71a6a264445248dd971e8a6bac86a78d787ea.jpg) Granite Rapids DDR5 only DIMM configurations diagram
DIMM QuantityAXE-7420GWA DIMM
DIMM3DIMM4DIMM1DIMM2DIMM6DIMM5DIMM8DIMM7
1DIMMV
1DIMMV
2DIMMVV
2DIMMVV
4DIMMVVVV
8DIMMVVVVVVVV
# 6.2 PCIe Slot Secondary Power Supply The AXE-7420GWA is equipped with two 8-pin ATX-type 12V power connectors on the mainboard (see section 4.2 Connector Locations) The pin definitions of the connectors and cables are described below. ![A yellow triangle with a black border containing a large black exclamation point in the center.](.axe-7420gwa-50m-22811-1000-02/00a86f0b51eed6448b8c176cefe6d780499227931a45d91342c61cdf413f61e6.jpg) CAUTION: mise en garde All installation procedures are restricted to skilled personnel. Toutes les procédures d'installation sont réservées au personnel qualifié. # 8-Pin ATX-Type 12V Power Connector Pinout
Pin #Signal
1P12V
2P12V
3P12V
4SENSE1
5GND
6SENSE0
7GND
8GND
![Pure architectural floor plan lines without any text, numbers, or symbols](.axe-7420gwa-50m-22811-1000-02/b7587f81a2002b0d6245455e3db0688dce7da6dd88a2116b226c8fbce914cc8a.jpg) # 6.3 BMC LAN Configuration Users can modify the BMC IP via ipmitool commands. Show the current LAN setting ipmitool lan print 1 # [Static IP] 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 # [DHCP IP] Set IP source to DHCP ipmitool lan set 1 ipsrc dhcp ![The image displays a standard icon representing a document. It features a white sheet of paper with a folded top-right corner. Faint, horizontal gray lines run across the document, simulating text lines. A large, thick red checkmark is superimposed on the left side of the paper, indicating approval or completion.](.axe-7420gwa-50m-22811-1000-02/dedad9af9b8feddaae9f075ea1b7557f482272a958ce26ba4c23526e85e121bc.jpg) NOTE: BMC IP can be set in the BIOS. # 6.4 BIOS Update Users can update the AXE-7420GWA system BIOS via various interfaces (Gigabit LAN, KCS, and the console port). # Updating BIOS via Host with BIOS Tool 1. Boot/Login to the Shell 2. Update the BIOS from the host using the following commands: Example: AfuEfix64 BIOS.ROM /p /b /n /x (to update BIOS without ME) ![FS0:\) cd AXE-7400GRW_00510_FullImage\nFS0:\AXE-7400GRW_00510_FullImage\) 1s\nDirectory of: FS0:\AXE-7400GRW_00510_FullImage\\n12/03/2025 14:54 (DIR) 16,384 .\n12/03/2025 14:54 (DIR) 0 ..\n12/03/2025 01:27 684,048 AfuEfix64.efi\n12/03/2025 01:27 50,331,648 AXE-7400GRW_00510.ROM\n12/03/2025 01:27 67,108,864 AXE-7400GRW_00510_Corporate.BIN\n12/03/2025 01:27 6,202 HISTORY.txt\n12/03/2025 01:27 405 pBIOS.nsh\n5 File(s) 118,131,167 bytes\n2 Dir(s)\nFSO:\AXE-7400GRW_00510_FullImage\)](.axe-7420gwa-50m-22811-1000-02/ea48136962cb2ac3790db972529f3622fee690d1a479a72b8bded8f58c082514.jpg) ![The image displays a simple line-art icon of a document. It features a white sheet of paper with a folded top-left corner and several horizontal black lines running across it, suggesting text. A large, thick red checkmark is superimposed over the center of the document.](.axe-7420gwa-50m-22811-1000-02/88290425aa3806753eb4eaafdbfd8161cb175557824f86a75f4062a5add83b7c.jpg) NOTE: Updating BIOS via BMC, please refer to Chapter 9 BMC. # 6.5 BMC Firmware Update via Network This section outlines the various methods available for updating the BMC firmware. BMC firmware updates can be performed through four primary methods: # 1. Web interface update For detailed steps and guidelines, please refer to Section 8.2.8.1.1 BMC Update. # 2. Redfish update For detailed steps and guidelines, please refer to Section 8.4.4 BMC Update. # 6.6 CPLD Update This section outlines the various methods available for updating the BMC firmware. BMC firmware updates can be performed through four primary methods: # 1. Web interface update For detailed steps and guidelines, please refer to Section 8.2.8.2.1 HPM Firmware Update-CPLD/BIOS. # 2. Redfish update For detailed steps and guidelines, please refer to Section 8.4.6 CPLD Update. # 3. ipmitool update For detailed steps and guidelines, please refer to Section 8.3.2.6 CPLD Update. # 6.7 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 section 8.4.2.1 SATA Configuration) 1. Go to Chipset > PCH Configurations > SATA Configuration. 2. Set SATA Mode Selection to RAID, save changes, and reboot the system. ![Aptio Setup - AMI\nChipset\nSATA Configuration\nSATA Controller(s) (Enabled)\nSATA Mode Selection (AHCI)\nForce SATA Gen Speed (Gen3)\nPort 0 (Not Installed)\nPort 0 (Enabled)\nPort 1 (Not Installed)\nPort 1 (Enabled)\nPort 2 (Not Installed)\nPort 2 (Enabled)\nPort 3 (Not Installed)\nPort 3 (Enabled)\nPort 4 (Not Installed)\nPort 4 (Enabled)\nPort 5 (Not Installed)\nPort 0 (Enabled)\nPort 6 (Not Installed)\nEnable/Disable SATA Device.\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.1294 Copyright (C) 2025 AMI](.axe-7420gwa-50m-22811-1000-02/6c0e15217feafd34ab322735e8af21701993c48d5c294f965c85a7b713ff6292.jpg) To create a RAID volume, go to the Advanced menu ![Aptio Setup - AMI\nMain Advanced Chipset Security Boot Save & Exit Server Mgmt\nCPU Configuration\nPower Management\nBIOS Watchdog Timer\nSuper IO Configuration\nSerial Port Console Redirection\nHardware Monitor\nTrusted Computing\nNVMe Configuration\nLAN Configuration\nUSB Configuration\nNetwork Stack Configuration\nAll Cpu Information\niSCSI Configuration\nIntel(R) EVROC SATA Controller\nIntel(R) Ethernet Controller I226-V -\n00:30:64:76:38:F8\nCoCPU Configuration\nce\ns.\n#\n#\n#\n#:\n#:\n#:(: Select Screen\n#: Select Item\n#Enter: Select\n#+/-: Change Opt.\n#F1: General Help\n#F8: Previous Values\n#F9: Optimized Defaults\n#F10: Save & Exit\nESC: Exit\nVersion 2.22.1294 Copyright (C) 2026 AMI\nAB](.axe-7420gwa-50m-22811-1000-02/85e8ece16e01318bbe2d8f50b6d75d631d3e282a82c36501b8a1eab76963ffae.jpg) Enter the Intel(R) VROC sSATA Controller submenu and click on Create RAID Volume. # BIOS Settings To enter the BIOS setup screen, follow these steps: 1. Power on the AXE-7420GWA. 2. Press the <Delete> or <ESC> 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 <Delete> or <ESC> key will still allow you to enter the BIOS setup screen.) ![ami™\nVersion 2.22.1294. Copyright (C) 2025 AMI\nAXE-7400RGW REV:0.05.10\nPress (DEL) or (ESC) to enter setup.](.axe-7420gwa-50m-22811-1000-02/b6ea19ebd1c58a796e9745325cd0b1850fdcf6d6b57eba1873ae1c160a9b512b.jpg) 3. After pressing the <Delete> or <ESC> 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. # 7.1 BIOS Setup Menu The BIOS setup utility is invoked by pressing <ESC> or <DEL> 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. <F1>: General help in setup menu <F8>: Load previous BIOS values <F9>: Load BIOS default in setup utility <F10>: Save & Exit setup utility To navigate through the BIOS setup menu, use the following.
→←Left/Right. The Left and Right < Arrow > keys allow you to select a setup screen.For example: Main screen, Advanced screen, Chipset screen, and so on.
↑↓Up/Down The Up and Down < Arrow > keys allow you to select a setup item or sub-screen.
+-Plus/Minus The Plus and Minus < Arrow > keys allow you to change the field value of a particular setup item.For example: Date and Time.
TabThe < Tab > key allows you to select setup fields.
# 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 Chipset Menu Security Menu Boot Menu Save & Exit Menu Server Mgmt # 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. # 7.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.
Main Advanced Chipset Security Boot Save & Exit Server Mgmt
BIOS Information BIOS Vendor American Megatrends Inc. BIOS Version 0.05.10 Build Date 12/05/2025 ME FW Version 19.10.0.1267 System Information Project Name AXE-7400GRW CPU Board Version A1 CPU Brand String Intel(R) Xeon(R) 696X CPU Frequency 2.40GHz Total Memory 32768 MB (DDR5) Memory Frequency 6400 MHz PCH SKU W890 System Date [Thu 12/04/2025] System Time [13:12:30] Access Level AdministratorSet the Date. Use Tab to switch between Date elements. Default Ranges: Year: 1998-9999 Months: 1-12 Days: Dependent on month Range of Years may vary. +: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS Information
BIOS ItemOptionsDescription
BIOS VendorInfo-only.American MegatrendsDisplay vendor name of system BIOS.
BIOS VersionInfo-only.x.yy.zzDisplay version of booting BIOS.
Build DateInfo-only.MM/DD/YYYYIt shows the date that BIOS was built.
MRC VersionInfo-only.xxx.RyyDisplay the revision of MRC code which is implemented in BIOS.
ME FW VersionInfo-only.ww:x.y.z.aaaDisplay the version of Intel manageability firmware which is implemented in BIOS.
System Information
BIOS ItemOptionsDescription
Project NameInfo-only.Shows Project Name
CPU Board VersionInfo-only.Shows Main Board Version
CPU Brand StringInfo-only.Intel(R) Core, ...Shows what CPU is booting the system.
CPU FrequencyInfo-only.XXXX MHzShows CPU frequency.
Total MemoryInfo-only.XXXX MB (DDR4)Shows total memory size used on the motherboard and memory type.
Memory FrequencyInfo-only.XXXX MHzShows memory frequency.
System DateMM/DD/YYYYFor configuring/showing system date. When setting the Date, usekey to switch between Date elements.
System TimeHH:MM:SSFor configuring/showing system time. When setting the Time, usekey to switch between Time elements.
Access LevelInfo-only.Administrator/UserIt shows what access level is used to enter BIOS setup menu.
# 7.3 Advanced Menu This menu contains the Advance settings.
Aptio Setup - AMI
Main Advanced Chipset Security Boot Save & Exit Server Mgmt
CPU ConfigurationPower ManagementBIOS Watchdog TimerSuper IO ConfigurationSerial Port Console RedirectionHardware MonitorTrusted ComputingNVMe ConfigurationLAN ConfigurationUSB ConfigurationNetwork Stack ConfigurationAll Cpu InformationIntel(R) Ethernet Controller I226-V -00:30:64:76:38:FAIntel(R) I210 Gigabit Network Connection -00:30:64:76:38:FBCPU Configuration
+: Select Screen↑↓: Select ItemEnter: Select+/-: Change Opt.F1: General HelpF8: Previous ValuesF9: Optimized DefaultsF10: Save & ExitESC: Exit
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS ItemOptionsDescription
1CPU ConfigurationSub-MenuFor Cpu setting
2Power ManagementSub-MenuFor Power Management
3BIOS Watchdog TimeSub-MenuFor BIOS Watchdog Time setting
4Super IO ConfigurationSub-MenuFor Super IO Configuration
5Serial Port Console RedirectionSub-MenuFor configuring serial console
6Hardware MonitorSub-MenuFor Hardware Monitor
7Trusted ComputingSub-MenuFor TPM settings
8NVMe ConfigurationSub-MenuFor NVMe Device Information
9Lan ConfigurationSub-MenuFor Lan settings
10USB ConfigurationSub-MenuFor USB settings
11Network Stack ConfigurationSub-MenuFor configuring Network Stack.
12All Cpu InformationSub-Menu
13Intel(R) Ethernet Controller I226-VSub-MenuOnboard 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.
14Intel(R) I210 Gigabit Network ConnectSub-MenuOnboard 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.
# CPU Configuration
AdvancedAptio Setup - AMI
CPU ConfigurationEnable Intel(R) TXT Enable SMX VMX Hyper-threading Enable (LP) X2APIC is enabled ASPM Support (Global) Native ASPM SpeedStep (Pstates) Turbo Mode Energy Efficient Turbo Monitor MWAIT C1 to C1e Promotion[Disabled][Disabled][Enabled][ALL LPs][Disabled][Disabled][Enabled][Enabled][Enabled][Enabled][Enabled]Enables Intel(R) TXT.+: Select Screen↑↓: Select ItemEnter: Select+/-: Change Opt.F1: General HelpF8: Previous ValuesF9: Optimized DefaultsF10: Save & ExitESC: Exit
Version 2.22.1294 Copyright (C) 2026 AMI
BIOS ItemOptionsDescription
Enable Intel(R) TXTDisabledEnabledEnables Intel(R) TXT.
Enable SMXDisabledEnabledEnables Safer Mode Extensions.
VMXDisabledEnabledEnables theVanderpoolTechnology, takes effect after reboot.
Hyper-Threading Enable (LP)All LPsSingle LPEnable Logical processor (software Method to Enable/Disable Logical Processor threads)
X2APIC is enableInfo
ASPM Support (Global)DisabledEnabledThis option can disable ASPM support for all PCIe root ports.
Native ASPMDisabledEnabledEnabled - OS Controlled ASPM, Disabled - ASPM Off, AUTO - BIOS Controlled ASPM
SpeedStep (PStates)DisabledEnabledEnable/Disable EIST (P-States)
Turbo modeDisabledEnabledEnable/Disable processorTurboMode
Energy Efficient TurboDisabledEnabledEnable/Disable Energy EfficientTurbo.Enable: MSR 0x1FC Bit[19] = 0, Disable: MSR 0x1FC Bit[19] =1.
Monitor MWAITDisabledEnabledAllows Monitor and MWAIT instructions.
C1 to C1e PromotionDisabledEnabledCPU will promote C1 request to C1e state.
# Power Management
Advanced Aptio Setup - AMI
Power Management State After G3 [S0 State] RTC Wake system from S5 [Disabled]Specify what state to go to when power is re-applied after a power failure (G3 state).
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2026 AMI
BIOS ItemOptionsDescription
State After G3S0 StateDisabledS5 StateLast StateTo enable or disable WOL
RTC Wake system from S5DisabledEnabledEnable and Set wake on timeEnable: Enable Wake on RTC feature but not set RTC wake up value(used for set RTC value by OS tool). Disable: Disable Wake on RTC feature. Enabled and set wake time: Enable System wake on alarm event and set wake on the day::hr::min::sec specified.
Wake Up hour0
Wake Up minute0
Wake Up second0
# Super IO Configuration
Aptio Setup - AMI
Advanced
Super IO Configuration COM1 Mode Control [RS232] COM2 Mode Control [RS232] COM1 TX termination [Disable] COM2 TX termination [Disable]Select COM1 mode. RS232, RS422, RS485
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2026 AMI
BIOS ItemOptionsDescription
COM1 Mode ControlRS232RS422RS485Select COM1 mode. RS232, RS422, RS485
COM2 Mode ControlRS232RS422RS485Select COM2 mode. RS232, RS422, RS485
Com1 TX terminationDisabledEnabledCOM1 TX termination Enable/Disable
Com2 TX terminationDisabledEnabledCOM2 TX termination Enable/Disable
# Serial Port Console Redirection
Aptio Setup - AMI Advanced
Super IO Configuration COM1 Mode Control [RS232] COM2 Mode Control [RS232] COM1 TX termination [Disable] COM2 TX termination [Disable]Select COM1 mode. RS232, RS422, RS485
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2026 AMI
BIOS ItemOptionsDescription
Console RedirectionEnabledDisabledEnable or disable serial port console redirection function.
Console Redirection SettingsSub-MenuFor configuring serial port settings when console redirection function is enabled.
# Console Redirection Settings
Aptio Setup - AMI Advanced
COM1 Console Redirection SettingsEmulation: 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
Terminal Type [ANSI] Bits per second [115200] Data Bits [8] Parity [None] Stop Bits [1] Flow Control [None] VT-UTF8 Combo Key [Enabled]
Support Recorder Mode [Disabled] Resolution 100x31 [Disabled] Putty KeyPad [VT100]+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS ItemOptionsDescription
Terminal TypeVT100VT100+VT-UTF8ANSIConfigure 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.
Bits per second9600192003840057600115200Selects serial port transmission speed. The speed must be matched on the other side. Long or noisy lines may require lower speed.
Data Bits78Configure the number of data bits in each transmitted or received serial character for both serial ports.
ParityNoneEvenOddMarkSpaceConfigures 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.
Stop Bits12Configures 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.
Flow ControlNoneHardware RTS/CTSConfigures flow control for console redirection. Hardware flow control uses RTC/CTS.
VT-UTF8 Combo Key SupportDisabledEnabledEnable VT-UTF8 Combination Key Support for ANSI/VT100 terminals
Recorder ModeDisabledEnabledThis mode only text wil be sent
Resolution 100x31DisabledEnabledTo enable or disable extended terminal resolution
Putty KeypadVT100Select Function Key and keypad on Putty
# Trusted Computing
Aptio Setup - AMI Advanced
Configuration Security Device [Enabled] SupportEnables or Disables BIOS support for security device. 0.S. will not show Security Device. TCG EFI protocol and INT1A interface will not be available.
+:-: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS ItemOptionsDescription
Security Device SupportEnabledDisabledSecurity Device Support
# NVMe Configuration ![Aptio Setup - AMI\nAdvanced\nNVMe Configuration\n► TS500GMTE110Q\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\nVersion 2.22.1294 Copyright (C) 2025 AMI](.axe-7420gwa-50m-22811-1000-02/59267248a722dc1336efc82a20ec31e0b3326f7f821873ec90af28c4a3782422.jpg)
BIOS ItemOptionsDescription
NVME InfoSub-MenuDynamically generated information for NVME
Aptio Setup - AMI
Advanced
Seg:Bus:Dev:Func00:0B:00:00Select either Short or Extended Self Test. Short option will take couple of minutes and extended option will take several minutes to complete.
Model NumberTS500GMTE110Q
Total Size500.1 GB
Vendor ID1D79
Device ID5766
Namespace: 1Size: 500.1 GB
Device Self Test:Self Test Option[Short]
Self Test Action[Controller Only Test]
Run Device Self Test
Short Device Selftest Result[Not Available]+: Select Screen↑↓: Select ItemEnter: Select+/-: Change Opt.F1: General HelpF8: Previous ValuesF9: Optimized DefaultsF10: Save & ExitESC: Exit
Extended Device Selftest Result[Not Available]
# VGA Configuration
AdvancedAptio Setup - AMI
VGA ConfigurationOnboard VGA Enable [Enabled]Enable or Disable Onboard VGA
+: Select Screen↑↓: Select ItemEnter: Select+/-: Change Opt.F1: General HelpF8: Previous ValuesF9: Optimized DefaultsF10: Save & ExitESC: Exit
Version 2.22.1294 Copyright (C) 2026 AMI
BIOS ItemOptionsDescription
Onboard VGA EnableDisabledEnabledEnable or Disable onboard VGA
# LAN Configuration ![Advanced\nLAN Configuration\nOnboard LAN1 Control (i226) (Enabled)\nOnboard LAN2 Control (i210) (Enabled)\nEnable/Disable LAN 1 Controller\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.1294 Copyright (C) 2026 AMI](.axe-7420gwa-50m-22811-1000-02/d054af3a0bb02ad7f551af91ee8ac779c6cbac81cbb326bfb1d73b64628409d2.jpg)
BIOS ItemOptionsDescription
Onboard LAN1 control (i226)EnabledDisabledEnable/Disable Lan 1 Controller
Onboard LAN2 control (i210)EnabledDisabledEnable/Disable Lan 2 Controller
# USB Configuration ![Aptio Setup - AMI\nAdvanced\nUSB Configuration\nUSB Module Version 40\nUSB Controllers:\n1 XHCI\nUSB Devices:\n9 Drives, 2 Keyboards, 1 Mouse, 1 Hub\nXHCI Hand-off (Enabled)\nUSB Mass Storage Driver Support (Enabled)\nUSB hardware delays and time-outs:\nUSB transfer time-out (20 sec)\nDevice reset time-out (20 sec)\nDevice power-up delay (Auto)\nMass Storage Devices:\nADLINK Virtual CDROM0 1.00 (Auto)\nADLINK Virtual HDisk0 1.00 (Auto)\nKingstonDT microDuo 3C PMAP (Auto)\nADLINK Virtual CDROM1 1.00 (Auto)\nADLINK Virtual CDROM2 1.00 (Auto)\nADLINK Virtual CDROM3 1.00 (Auto)\nADLINK Virtual HDisk1 1.00 (Auto)\nThis is a workaround for OSes without XHCI hand-off support.\nThe XHCI ownership change should be claimed by XHCI driver.\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.1294 Copyright (C) 2026 AMI](.axe-7420gwa-50m-22811-1000-02/80d48536bac2d025ff56d8b18f483619b8f07d4989fa7a10648bf06d388ef47f.jpg)
BIOS ItemOptionsDescription
XHCI Hand-offEnabledDisabledThis is a workaround for OSes without XHCI hand-off support. The XHCI ownership change should be claimed by XHCI driver.
USB Mass Storage Driver SupportEnabledDisabledConfigure the USB Mass Storage Devices.
USB transfer time-out1 Sec5Sec10 Sec20 SecThe time-out value for Control, Bulk, and Interrupt transfers
Device reset time-out10 Sec20 Sec30 Sec40 SecUSB mass storage device Start Unit command time-out.
Device power-up delayAutoManualMaximum time the device will take before it properly reports itself to the Host Controller. 'Auto' uses default value: for a Root port it is 100 ms, for a Hub port the delay is taken from Hub descriptor.
# Miscellaneous
Aptio Setup - AMI Advanced
Miscellaneous PCIE Resizable BAR Support [Enabled] Resizable BAR Max Size 26Enable/Disable PCIE Resizable BAR Support
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2026 AMI
BIOS ItemOptionsDescription
PCIE Resizable BAR SupportDisabledEnabledEnable/Disable PCIE Resizable BAR Support
Resizable BAR Max sizenumericSet platform limit for max size to pick from Resizable BAR Capability register.Decimal value 'n' is interpreted as 2^(n+20), which means 0=>1MB, 1=>2MB, 2=>4MB, 3=>8MB, etc.Maximum possible to set is half of processor address width, i.e. address width - 1.
# Network Stack Configuration
Aptio Setup - AMI Advanced
Network Stack Configuration Network Stack [Enabled] IPv4 PXE Support [Disabled] IPv4 HTTP Support [Disabled] IPv6 PXE Support [Disabled] IPv6 HTTP Support [Disabled] PXE boot wait time 0 Media detect count 1Enable/Disable UEFI Network Stack
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS ItemOptionsDescription
Network stackEnabledDisabledEnable/Disable UEFI Network Stack
IPv4 PXESupportEnabledDisabledEnable/Disable IPv4 PXE boot support. If disabled, IPv4 PXE boot support will not be available.
IPv4 HTTP SupportEnabledDisabledEnable/Disable IPv4 HTTP boot support. If disabled, IPv4 HTTP boot support will not be available.
IPv6 PXESupportEnabledDisabledEnable/Disable IPv6 PXE boot support. If disabled, IPv6 PXE boot support will not be available.
IPv4 HTTP SupportEnabledDisabledEnable/Disable IPv6 HTTP boot support. If disabled, IPv4 HTTP boot support will not be available.
PXE Boot wait time0Wait time in seconds to press ESC key to abort the PXE boot. Use either +/- or numeric keys to set the value
Media detect count1Number of times the presence of media will be checked. Use either +/- or numeric keys to set the value.
# All CPU Information ![Aptio Setup - AMI\nAdvanced\nTotal CPU Number: 128\nCPU0\nCPUID: 000A06D1\nStepping: 1\nMicroCodeRev: 01000140\nPlatformID: 0004000000000000\nCoreFreq(MHz): 2400\nActCpuFreq(MHz): 2376\nCPU1\nCPUID: 000A06D1\nStepping: 1\nMicroCodeRev: 01000140\nPlatformID: 0004000000000000\nCoreFreq(MHz): 2400\nActCpuFreq(MHz): 2376\nCPU2\nCPUID: 000A06D1\nStepping: 1\nMicroCodeRev: 01000140\nPlatformID: 0004000000000000\nCoreFreq(MHz): 2400\nActCpuFreq(MHz): 2376\nCPU3\nCPUID: 000A06D1\nStepping: 1\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.1294 Copyright (C) 2025 AMI](.axe-7420gwa-50m-22811-1000-02/aee76b3e2943ab84b43e1b4650abc5bf3205f71daad46b2f44aeeefc8383144d.jpg) # Intel(R) Ethernet Controller I226-V
Aptio Setup - AMI Advanced
How long the UEFI PXE driver should wait for link
UEFI Driver:Intel(R) Ethernet Controller 2.5G 1.0.5
PCI Device ID125C
PCI Address2D:00:00
MAC Address00:30:64:76:38:FA
Link StatusDisconnected
Link auto-negotiation Timeout8+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS ItemOptionsDescription
Link auto-negotiationTimeout8How long the UEFI PXE driver should wait for link
# Intel(R) I210 Gigabit Network Connect
Aptio Setup - AMI Advanced
Firmware Image Properties NIC ConfigurationView device firmware version information.
Blink LEDs 0
UEFI Driver Intel(R) PRO/1000 9.8.33 PCI-E
Adapter PBA 000300-000
Device Name Intel(R) I210 Gigabit Network Connection
Chip Type Intel i210+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
PCI Device ID 1533
PCI Address 30:00:00
Link Status [Disconnected]
MAC Address 00:30:64:76:38:FB
Virtual MAC Address 00:00:00:00:00:00
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS ItemOptionsDescription
Firmware Image PropertiesSub-MenuView device firmware version information
NIC ConfigurationSub-Menu
Blink LEDs0
# 7.4 Chipset Menu This menu contains the Chipset settings. ![Aptio Setup - AMI\nMain Advanced Chipset Security Boot Save & Exit Server Mgmt\nSocket Configurations\nPCH Configuration\nChipset Security Configuration\nSocket Configurations\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.1294 Copyright (C) 2025 AMI](.axe-7420gwa-50m-22811-1000-02/604d339ccb2af4d98b53f4cd7230141c4d3264a122642b5a95040f8d605a8867.jpg)
BIOS ItemOptionsDescription
Socket ConfigurationsSub-MenuFor Socket Configurations.
PCH ConfigurationsSub-MenuFor PCH Configurations.
Chipset Security ConfigurationsSub-MenuFor Chipset Security Configurations
# Socket Configuration ![Aptio Setup - AMI\nChipset\nSocket Configurations\n► IIO Configurations\n► Memory Configurations\nIIO Configurations\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.1294 Copyright (C) 2025 AMI](.axe-7420gwa-50m-22811-1000-02/8a09bc7a063497b07a3948e0670e7448ffe1d8c6be0848e55ed030851cf09407.jpg)
BIOS ItemOptionsDescription
IIO ConfigurationsSub-MenuFor IIO Configurations
Memory ConfigurationsSub-MenuFor Memory Configurations
# IIO Configurations
Aptio Setup - AMI
Chipset
IIO Configurations ►PCIE_CN3/PCIE_CN6/M.2_CN2/M.2_CN3 ►PCIE_CN2/PCIE_CN5 ►MCIO_CN1/MCIO_CN2 ►PCIE_CN7 ►PCIE_CN4 ►MCIO_CN3/MCIO_CN4 ►PCIE_CN1PCIE_CN3/PCIE_CN6/M.2_CN2/M.2_CN3
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS ItemOptionsDescription
PCIE_CN3/PCIE_CN6/M.2_CN2/M.2_CN3Sub-MenuFor PCIE_CN3/PCIE_CN6/M.2_CN2/M.2_CN3
PCIE_CN2/PCIE_CN5Sub-MenuFor PCIE_CN2/PCIE_CN5
MCIO_CN1/MCIO_CN2Sub-MenuFor MCIO_CN1/MCIO_CN2
PCIE_CN7Sub-MenuFor PCIE_CN7
PCIE_CN4Sub-MenuFor PCIE_CN4
MCIO_CN1/MCIO_CN2Sub-MenuFor MCIO_CN1/MCIO_CN2
PCIE_CN1Sub-MenuFor PCIE_CN1
# 7.4.1.1.1 PCIE\_CN3/PCIE\_CN6/M.2\_CN2/M.2\_CN3
Aptio Setup - AMI Chipset
PCIE_CN3/PCIE_CN6/M.2_CN2/M.2_CN3 --------[---]Press <Enter> to bring up the Intel VMD for Volume Management Device Configuration menu.
Intel VMD technology Bifurcation [x4x4x4x4]
Port A
Port B
Port C
Port D
Port E
Port F
Port G
Port H
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS ItemOptionsDescription
Intel VMD technologySub-MenuPressto bring up the Intel VMD for Volume Management Device Configuration menu.
BifurcationAutox4x4x4x4x4x4x_x8x_x8x4x4x_x8x_x_x16x2x2x4x_x8x4x2x2x_x8x_x8x2x2x4x2x2x4x4x4x2x2x4x4x4x4x2x2x4x2x2x2x2x_x8x2x2x2x4x4x2x2x4x2x2x2x2x4x2x2x2x2x2x4x_x8x4x2x2x4x4x4x4x2x2x2x8x2x2x4x4x2x2x4x4x2x2x4x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2xSelects PCIe port Bifurcation for selected slot(s)Port Format: xGxExCxAThe port can further be x2x2
Port ASub-Menu
Port BSub-Menu
Port CSub-Menu
Port DSub-Menu
Port ESub-Menu
Port FSub-Menu
Port GSub-Menu
Port HSub-Menu
# 7.4.1.1.2 PCIE\_CN2/PCIE\_CN5
Aptio Setup - AMI Chipset
PCIE_CN2/PCIE_CN5 --------[x_x8x_x8]Press <Enter> to bring up the Intel VMD for Volume Management Device Configuration menu.
▶Intel VMD technology Bifurcation
▶Port A
▶Port B
▶Port C
▶Port D
▶Port E
▶Port F
▶Port G
▶Port H
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS ItemOptionsDescription
Intel VMD technologySub-MenuPressto bring up the Intel VMD for Volume Management Device Configuration menu.
BifurcationAutox4x4x4x4x4x4x_x8x_x8x4x4x_x8x_x_x16x2x2x4x_x8x4x2x2x_x8x_x8x2x2x4x2x2x4x4x4x4x4x4x4x4x4x4x2x2x2x4x2x2x2x2x_x8x2x2x2x2x4x4x2x2x2x2x4x2x2x2x2x2x4x2x2x2x2x2x2x4x_x8x4x2x2x4x4x4x4x2x2x2x_x8x2x2x2x2x2x2x2x4x4x2x2x2x2x4x4x2x2x2x2x4x4x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2xSelects PCIe port Bifurcation for selected slot(s)Port Format: xGxExCxAThe port can further be x2x2
Port ASub-Menu
Port BSub-Menu
Port CSub-Menu
Port DSub-Menu
Port ESub-Menu
Port FSub-Menu
Port GSub-Menu
Port HSub-Menu
# 7.4.1.1.3 MCIO\_CN1/MCIO\_CN2 ![Aptio Setup - AMI\nChipset\nMCIO_CN1/MCIO_CN2\n--------)\nIntel VMD technology\nBifurcation (x_x8x_x8)\nPort A\nPort B\nPort C\nPort D\nPort E\nPort F\nPort G\nPort H\nPress (Enter) to bring up the Intel VMD for Volume Management Device Configuration menu.\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.1294 Copyright (C) 2025 AMI](.axe-7420gwa-50m-22811-1000-02/dadd406f4926a0e091626e5c28e5922b330b5d9c32100053e6b1bb8793591817.jpg)
BIOS ItemOptionsDescription
Intel VMD technologySub-MenuPressto bring up the Intel VMD for Volume Management Device Configuration menu.
BifurcationAutox4x4x4x4x4x4x_x8x_x8x4x4x_x8x_x_x_x16x2x2x4x_x8x4x2x2x_x8x_x8x2x2x4x4x4x2x2x4x4x4x4x2x2x4x2x2x2x2x_x8x2x2x2x2x4x4x2x4x2x2x4x4x2x2x2x2x4x2x2x2x2x2x2x4x_x8x4x2x2x4x4x4x4x2x2x2x8x8x2x2x2x2x2x2x2x4x4x2x2x2x2x2x4x4x2x2x2x2x2x2x4x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2xx4x2x2x2x2x2x2Selects PCIe port Bifurcation for selected slot(s)Port Format: xGxExCxAThe port can further be x2x2
Port ASub-Menu
Port BSub-Menu
Port CSub-Menu
Port DSub-Menu
Port ESub-Menu
Port FSub-Menu
Port GSub-Menu
Port HSub-Menu
# 7.4.1.1.4 PCIE\_CN7 ![Aptio Setup - AMI\nChipset\nPCIE_CN7\n--------)\n▶ Intel VMD technology\nBifurcation (Auto)\n▶ Port A\n▶ Port B\n▶ Port C\n▶ Port D\n▶ Port E\n▶ Port F\n▶ Port G\n▶ Port H\nPress (Enter) to bring up the Intel VMD for Volume Management Device Configuration menu.\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.1294 Copyright (C) 2025 AMI](.axe-7420gwa-50m-22811-1000-02/c40b0f6111f274a925a617350c2ee55848dbf30f71706eb5d4d1268eb9ac0e39.jpg)
BIOS ItemOptionsDescription
Intel VMD technologySub-MenuPressto bring up the Intel VMD for Volume Management Device Configuration menu.
BifurcationAutox4x4x4x4x4x4x_x8x_x8x4x4x_x8x_x_x16x2x2x4x_x8x4x2x2x_x8x_x8x2x2x4x4x4x2x2x4x4x4x4x2x2x4x2x2x2x2x_x8x2x2x2x2x4x4x2x2x4x2x2x4x4x2x2x2x2x2x4Selects PCIe port Bifurcation for selected slot(s)Port Format: xGxExCxAThe port can further be x2x2
x_x8x4x2x2x4x4x4x2x2x_x8x2x2x2x2x2x2x4x4x2x2x4x2x2x4x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x
Port ASub-Menu
Port BSub-Menu
Port CSub-Menu
Port DSub-Menu
Port ESub-Menu
Port FSub-Menu
Port GSub-Menu
Port HSub-Menu
# 7.4.1.1.5 PCIE\_CN4 ![Aptio Setup - AMI\nChipset\nPCIE_CN4\n--------)\n---------- Intel VMD technology\nBifurcation (Auto)\n▶ Port A\n▶ Port B\n▶ Port C\n▶ Port D\n▶ Port E\n▶ Port F\n▶ Port G\n▶ Port H\nPress (Enter) to bring up the Intel VMD for Volume Management Device Configuration menu.\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.1294 Copyright (C) 2025 AMI](.axe-7420gwa-50m-22811-1000-02/2697bb92ef7846eed3a3df41868ea2d60f417da28ebe359781409154d5850f20.jpg)
BIOS ItemOptionsDescription
Intel VMD technologySub-MenuPressto bring up the Intel VMD for Volume Management Device Configuration menu.
BifurcationAutox4x4x4x4x4x4x_x8x_x8x4x4x_x8x_x_x16x2x2x4x_x8x4x2x2x_x8x_x8x2x2x4x2x2x4x4x4x2x2x4x4x4x4x2x2x4x2x2x2x2x_x8x2x2x2x4x4x2x4x2x2x4x4x2x2x2x2x4x2x2x2x2x2x2x4x_x8x4x2x2x4x4x4x4x2x2x2x_x8x2x2x2x2x2x2x2x4x4x2x2x4x2x2x4x4x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2xSelects PCIe port Bifurcation for selected slot(s)Port Format: xGxExCxAThe port can further be x2x2
Port ASub-Menu
Port BSub-Menu
Port CSub-Menu
Port DSub-Menu
Port ESub-Menu
Port FSub-Menu
Port GSub-Menu
Port HSub-Menu
# 7.4.1.1.6 MCIO\_CN3/MCIO\_CN4
Aptio Setup - AMI Chipset
MCIO_CN3/MCIO_CN4 --------> ► Intel VMD technology Bifurcation [x_x8x_x8] ► Port A ► Port B ► Port C ► Port D ► Port E ► Port F ► Port G ► Port HPress <Enter> to bring up the Intel VMD for Volume Management Device Configuration menu.
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS ItemOptionsDescription
Intel VMD technologySub-MenuPressto bring up the Intel VMD for Volume Management Device Configuration menu.
BifurcationAutox4x4x4x4x4x4x_x8x_x8x4x4x_x8x_x_x16x2x2x4x_x8x4x2x2x_x8x_x8x2x2x4x2x2x4x4x4x2x2x4x4x4x4x2x2x4x2x2x2x2x_x8x2x2x2x4x4x2x2x4x2x2x2x4x2x2x2x2x4x2x2x2x2x2x4x_x8x4x2x2x4x4x4x4x2x2x2x8x8x2x2x2x2x2x2x2x4x4x2x2x2x2x4x4x2x2x2x2x2x4x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2xSelects PCIe port Bifurcation for selected slot(s)Port Format: xGxExCxAThe port can further be x2x2
Port ASub-Menu
Port BSub-Menu
Port CSub-Menu
Port DSub-Menu
Port ESub-Menu
Port FSub-Menu
Port GSub-Menu
Port HSub-Menu
# 7.4.1.1.7 PCIE\_CN1 ![Aptio Setup - AMI\nChipset\nPCIE_CN1\n--------)\n▶ Intel VMD technology\nBifurcation (Auto)\n▶ Port A\n▶ Port B\n▶ Port C\n▶ Port D\n▶ Port E\n▶ Port F\n▶ Port G\n▶ Port H\nPress (Enter) to bring up the Intel VMD for Volume Management Device Configuration menu.\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.1294 Copyright (C) 2025 AMI](.axe-7420gwa-50m-22811-1000-02/644b7ed3f57c83572f42cf94a9955348f2e966ad73fb675c4452121fce69b679.jpg)
BIOS ItemOptionsDescription
Intel VMD technologySub-MenuPressto bring up the Intel VMD for Volume Management Device Configuration menu.
BifurcationAutox4x4x4x4x4x4x_x8x_x8x4x4x_x8x_x_x16x2x2x4x_x8x4x2x2x_x8x_x8x2x2x4x4x2x2x4x4x4x2x2x4x4x4x4x2x2x4x2x2x2x2x_x8x2x2x2x4x4x2x2x4x2x2x4x4x2x2x2x2x4x2x2x2x2x2x2x4x_x8x4x2x2x4x4x4x4x2x2x2x8x8x2x2x2x2x2x2x2x4x4x2x2x2x2x2x4x4x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2x2xSelects PCIe port Bifurcation for selected slot(s)Port Format: xGxExCxAThe port can further be x2x2
Port ASub-Menu
Port BSub-Menu
Port CSub-Menu
Port DSub-Menu
Port ESub-Menu
Port FSub-Menu
Port GSub-Menu
Port HSub-Menu
# Memory Configurations
Chipset Aptio Setup - AMI
Memory Configurations Host Memory Frequency [Auto] ► Memory TopologyMaximum Host DDR Memory Frequency Selections in MT/s. If the "AUTO" option has been selected, a frequency is chosen automatically based on the minimum tCK given by the SPD. If Enforce POR is disabled, user will be able to run at higher frequencies than the memory support (limited by processor support). Note: For
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2026 AMI
BIOS ItemOptionsDescription
Host Memory FrequencyAuto48005200560060006400Maximum Host DDR Memory FrequencySelections in MT/s. If the "AUTO" optionhas been selected, a frequency is chosenautomatically based on the minimum tCKgiven by the SPD. If Enforce POR isdisabled, user will be able to run at higherfrequencies than the memory support(limited by processor support). Note: ForMRDIMM, DDR DRAM frequency is half ofHost frequency
Memory TopologySub-MenuDisplays memory topology with Dimmpopulation information
# 7.4.1.2.1 Memory Topology ![Aptio Setup - AMI\nChipset\n\nSocket0.ChC.Dimm0: 6400MT/s Actica DRx8 32GB RDIMM\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.1294 Copyright (C) 2025 AMI](.axe-7420gwa-50m-22811-1000-02/465604a6403cf80f80f6b8e3813fea208d5d957ec0a63abce2117aacea35e4ca.jpg) # PCH Configurations ![Aptio Setup - AMI\nChipset\nPCH Configuration\n▶ SATA Configuration\nSATA Device Options 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.1294 Copyright (C) 2025 AMI](.axe-7420gwa-50m-22811-1000-02/5296b7b6de3018f573e28dba0b6731ba98d2555ab85c866d0c997fac4d350cc8.jpg)
BIOS ItemOptionsDescription
SATA ConfigurationSub-MenuSATA Device options Settings
# SATA Configuration ![Chipset\nAptio Setup - AMI\nSATA Configuration\nSATA Controller(s) (Enabled)\nSATA Mode Selection (AHCI)\nForce SATA Gen Speed (Gen3)\nPort 0 (Not Installed)\nPort 0 (Enabled)\nHot Plug (Disabled)\nPort 1 (Not Installed)\nPort 1 (Enabled)\nHot Plug (Disabled)\nPort 2 (Not Installed)\nPort 2 (Enabled)\nHot Plug (Disabled)\nPort 3 (Not Installed)\nPort 3 (Enabled)\nHot Plug (Disabled)\nPort 4 (Not Installed)\nPort 4 (Enabled)\nHot Plug (Disabled)\nEnable/Disable SATA Device.\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.1294 Copyright (C) 2026 AMI](.axe-7420gwa-50m-22811-1000-02/30d3453b9b585e4d3ac868edd47f10a68d73bd2d916ce542dd1a0e89a0f5300c.jpg)
BIOS ItemOptionsDescription
SATA Controller(s)EnabledDisabledEnable/Disable SATA Device.
SATA Mode SelectionAHCIRAIDDetermines how SATA controller(s) operate.
Force SATA Gen SpeedGen1Gen2Gen3Changes SATA Gen Speed for port.
Port 0Not InstalledSoftware Preserve
Port 0EnabledDisabledEnable or Disable SATA Port
Hot PlugEnabled/DisabledDesignates this port as Hot Pluggable.
Port 1Not InstalledSoftware Preserve
Port 1EnabledDisabledEnable or Disable SATA Port
Hot PlugEnabled/DisabledDesignates this port as Hot Pluggable.
Port 2Not InstalledSoftware Preserve
Port 2EnabledDisabledEnable or Disable SATA Port
Hot PlugEnabled/DisabledDesignates this port as Hot Pluggable.
Port 3Not InstalledSoftware Preserve
Port 3EnabledDisabledEnable or Disable SATA Port
Hot PlugEnabled/DisabledDesignates this port as Hot Pluggable.
Port 4Not InstalledSoftware Preserve
Port 4EnabledDisabledEnable or Disable SATA Port
Hot PlugEnabled/DisabledDesignates this port as Hot Pluggable.
Port 5Not InstalledSoftware Preserve
Port 5EnabledDisabledEnable or Disable SATA Port
Hot PlugEnabled/DisabledDesignates this port as Hot Pluggable.
Port 6Not InstalledSoftware Preserve
Port 6EnabledDisabledEnable or Disable SATA Port
Hot PlugEnabled/DisabledDesignates this port as Hot Pluggable.
Port 7Not InstalledSoftware Preserve
Port 7EnabledDisabledEnable or Disable SATA Port
Hot PlugEnabled/DisabledDesignates this port as Hot Pluggable.
# Chipset Security Configurations
Chipset Setup - AMI
Chipset Security Configuration BIOS Lock [Disabled] Global Reset Lock [Auto] SPD Write Disable [True]Enable/Disable the IBL BIOS Lock Enable feature. Required to be enabled to ensure SMM protection of flash.
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS ItemOptionsDescription
BIOS LockDisabledEnabledEnable/Disable the IBL BIOS Lock Enable feature. Required to be enabled to ensure SMM protection of flash.
Global Reset LockDisableEnableAutoEnable/Disable locking global host reset
SPD Write DisableTrueFalseEnable/Disable setting SPD Write Disable. For security recommendations, SPD write disable bit must be set.
# 7.5 Security Menu
Aptio Setup - AMI
Main Advanced Chipset Security Boot Save & Exit Server Mgmt
Password Description If ONLY the Administrator's password is set, then this only limits access to Setup and is only asked for when entering Setup. If ONLY the User's password is set, then this is a power on password and must be entered to boot or enter Setup. In Setup the User will have Administrator rights. The password length must be in the following range: Minimum length 3 Maximum length 20 Administrator Password User Password Secure BootSet Administrator Password
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS ItemOptionsDescription
Administrator PasswordEnter to set passwordConfigure/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.
User PasswordEnter to set passwordConfigure/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.
Secure BootSub-MenuSecure Boot Menu. Default is Disabled.
# 7.6 Boot Menu This menu contains the settings for bootable devices in the system. ![Aptio Setup - AMI\nMain Advanced Chipset Security Boot Save & Exit Server Mgmt\nBoot Configuration\nSetup Prompt Timeout 1\nBootup NumLock State (On)\nQuiet Boot (Enabled)\nFast Boot (Disabled)\nFIXED BOOT ORDER Priorities\nBoot Option #1 (Hard Disk)\nBoot Option #2 (NVME)\nBoot Option #3 (CD/DVD)\nBoot Option #4 (SD)\nBoot Option #5 (USB Hard Disk)\nBoot Option #6 (USB CD/DVD)\nBoot Option #7 (USB Key:UEFI:\nJetFlashTranscend 32GB\n1100, Partition 1)\nBoot Option #8 (USB Floppy)\nBoot Option #9 (USB Lan)\nBoot Option #10 (Network)\n► UEFI USB Key Drive BBS Priorities\nNumber of seconds to wait for\nsetup activation key. The\nmaximum value is 8\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.1294 Copyright (C) 2025 AMI](.axe-7420gwa-50m-22811-1000-02/853a27d83df67ed0e46ca666e680d1ecbcf7ae21085b4f7d9c18737ccf3001e7.jpg)
BIOS ItemOptionsDescription
Setup Prompt Timeout1Number of seconds to wait for setup activation
Bootup NumLock StateOnOffSelect the keyboard NumLock state
Quiet BootEnabledDisabledEnables or disables Quiet Boot option
Fast BootDisableEnableEnables or disables boot with initialization of a minimal set of devices required to launch active boot option. Has no effect for BBS boot options.
Boot Option #1 ~ #9#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: NetworkFor boot priority setting.
XXXX Drive BBS PrioritiesSub-MenuWhen 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.
# 7.7 Save & Exit Menu
Aptio Setup - AMI
Main Advanced Chipset Security Boot Save & Exit Server Mgmt
Save Changes and Exit Discard Changes and Exit Save Changes and Reset Discard Changes and Reset Save Options Save Changes Discard Changes Restore Defaults Save as User Defaults Restore User Defaults Boot Override UEFI: JetFlashTranscend 32GB 1100, Partition 1 (JetFlashTranscend 32GB 1100) UEFI: Built-in EFI Shell Launch EFI Shell from filesystem deviceExit system setup after saving the changes.
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2025 AMI
BIOS ItemOptionsDescription
Save Changes and ExitEnterSave changed settings and exit BIOS setup utility.
Discard Changes and ExitEnterSkip changed setting and exit BIOS setup utility.
Save Changes and ResetEnterSave all changed settings and let system do reset to boot system.
Discard Changes and ResetEnterDiscard all changed settings and let system do reset to boot system.
Save ChangesEnterSave all changed settings.
Discard ChangesEnterDiscard changes done so far to any of the setup options.
Restore DefaultEnterLoad the default made when BIOS was built.
Save as User DefaultEnterSave all changed done so far as User Defaults.
Restore User DefaultEnterLoad the default that user save as user defaults.
Boot OverrideInfo-only
# 7.8 Server Management ![Aptio Setup - AMI\nMain Advanced Chipset Security Boot Save & Exit Server Mgmt\nBMC Self Test Status PASSED\nBMC Device ID 32\nBMC Device Revision 81\nBMC Firmware Revision 0.02.2\nIPMI Version 2.0\nIPMI BMC Interface KCS\nBMC Support (Enabled)\nIPMI Interface Type (Kcs Interface)\nWait For BMC (Disabled)\nWait For Full BMC Initialization (Disabled)\nFRB-2 Timer (Enabled)\nFRB-2 Timer timeout 6\nFRB-2 Timer Policy (Do Nothing)\nOS Watchdog Timer (Disabled)\nOS Wtd Timer Timeout 10\nOS Wtd Timer Policy (Reset)\nBMC Configured Power\nControl Policy Power Restore\nPower Control Policy (Unspecified)\n► System Event Log\n► Bmc self test log\nEnable/Disable interfaces to communicate with 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.1294 Copyright (C) 2026 AMI](.axe-7420gwa-50m-22811-1000-02/af35e7fd9370f39d5362b23a64895d3d1fbeb2f9d7dea03f9968289335ff7732.jpg)
BIOS ItemOptionsDescription
BMC SupportEnabledDisabledEnable/Disable interfaces to communicate with BMC.
IPMI Interface TypeKcs InterfaceType of Interface to communicate BMC from HOST.
Wait For BMCEnabledDisabledWait for BMC response for specified time out. In PILOT II, BMC starts at the same time when BIOS starts during AC power ON. It takes around 30 seconds to initialize HOST to BMC interfaces.
Wait For Full BMC InitializationEnabledDisabledBased on above rules, additional provide user can manually increase the waiting time on different platforms if necessary.
FRB-2 TimerEnabledDisabledEnable/Disable Fault Resilient Boot level 2 timer in POST stage.
FRB-2 Timer timeout6Enter value between 1 to 30 min for FRB-2 timer expiration.
FRB-2 Timer PolicyDo NothingResetPower DownPower CycleConfigure how the system should respond if the FRB-2 timer expires. Not available if FRB-2 timer is disabled.
OS Watchdog TimerEnabledDisabledIf 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.
OS Wtd Timer Timeout10Enter the value between 1 to 30 min for OS Boot Watchdog Timer expiration. Not available if OS Boot Watchdog Timer is disabled.
OS Wtd Timer PolicyDo NothingResetPower DownPower CycleConfigure how the system should respond if the OS Boot Watchdog Timer expires. Not available if OS Boot Watchdog Timer is disabled.
BMC Configured Power Control PolicyPower Restore
Power Control PolicyDo Not Power UpLast Power StatePower RestoreUnspecifiedConfigure how the system should respond if AC power is lost, reset not required as selected power policy will be set in BMC when policy is saved.
# System Event Log
Aptio Setup - AMI Server Mgmt
Enabling/Disabling Options SEL Components [Enabled]Change this to enable or disable event logging for error/progress codes during boot.
Erasing Settings Erase SEL [No] When SEL is Full [Do Nothing]
Custom EFI Logging Options Log EFI Status Codes [Error code]
NOTE: All values changed here do not take effect until computer is restarted.
+: Select Screen ↑↓: Select Item Enter: Select +/-: Change Opt. F1: General Help F8: Previous Values F9: Optimized Defaults F10: Save & Exit ESC: Exit
Version 2.22.1294 Copyright (C) 2026 AMI
BIOS ItemOptionsDescription
SEL ComponentsEnabledDisabledEnable/Disable event logging for error/progress codes during boot.
Erase SELNoYes, on next resetYes, on every resetChoose options for erasing SEL.
When SEL is FullDo NothingErase ImmediatelyDelete Oldest RecordChoose options for reactions to a full SEL.
Log EFI Status CodesDisabledBothError codeChoose options for logging EFI Status Codes.
Progress code
# BMC Self Test Log ![Aptio Setup - AMI\nServer Mgmt\nLog area usage = 00 out of 20 logs\nErase Log (Yes, On every reset)\nWhen log is full (Clear Log)\nLog Empty\nErase Log Options\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.1294 Copyright (C) 2026 AMI](.axe-7420gwa-50m-22811-1000-02/cca22020ffd0a5a8d9c3457a280fb95f84e3b9e37d0e27fb7449451e06d52563.jpg)
BIOS ItemOptionsDescription
Erase LogYes, on every resetNoChoose options for erasing logs.
When log is fullClear LogDo not log any moreChoose options for reactions to a full log.
# BMC Network Configuration ![Aptio Setup - AMI\nServer Mgmt\n--BMC network configuration--\n*****************\nConfigure IPv4 support\n*****************\nLan channel 1\nConfiguration Address source (Unspecified)\nCurrent Configuration Address staticAddress\nsource\nStation IP address 192.168.1.1\nSubnet mask 255.255.255.0\nStation MAC address 82-E2-BB-69-71-90\nRouter IP address 0.0.0.0\nRouter MAC address 00-00-00-00-00-00\n*****************\nConfigure IPv6 support\n*****************\nLan channel 1\nIPv6 Support (Enabled)\nConfiguration Address source (Unspecified)\nSelect to configure LAN\nchannel parameters statically\nor dynamically(by BIOS or\nBMC). Unspecified option will\nnot modify any BMC network\nparameters during BIOS phase\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.1294 Copyright (C) 2026 AMI](.axe-7420gwa-50m-22811-1000-02/5037c890bf8bdd84dd3ff6860e94d825e5ed30ecc4a06f85f019968b4490ee32.jpg)
BIOS ItemOptionsDescription
IPv4Configuration Address sourceUnspecifiedStaticDynamicBmcDhcpDynamicBmcNonDhcpSelect to configure LAN channel parameters statically or dynamically (by BIOS or BMC). Unspecified option will not modify any BMC network parameters during BIOS phase.
IPv6 SupportEnabledDisabledEnable/Disable LAN1 IPv6 Support
IPv6Configuration Address sourceUnspecifiedStaticDynamicBmcDhcpDynamicBmcNonDhcpSelect to configure LAN channel parameters statically or dynamically (by BIOS or BMC). Unspecified option will not modify any BMC network parameters during BIOS phase.
IPv6Configuration Router Lan1 Address sourceUnspecifiedStaticDynamicBmcDhcpSelect to configure LAN channel parameters statically or dynamically (by BIOS or BMC). Unspecified option will not modify any BMC network parameters during BIOS phase
VLAN SupportEnabledDisabledUnspecifiedEnable VLAN Support to specify the 802.1q VLAN ID
# 7.9 View System Event Log ![Aptio Setup - AMI\nMain Advanced Chipset Security Boot Save & Exit Server Mgmt\nIPMI Version 2.0\nIPMI BMC Interface KCS\nBMC Support (Enabled)\nIPMI Interface Type (Kcs Interface)\nWait For BMC (Disabled)\nWait For Full BMC Initialization (Disabled)\nFRB-2 Timer (Enabled)\nFRB-2 Timer timeout View System Event Log\nFRB-2 Timer Policy\nOS Watchdog Timer Retrieving all system events will take time. Do you want to continue?\nOS Wtd Timer Timeout\nOS Wtd Timer Policy\nBMC Configured Power Yes No\nControl Policy Select\nPower Control Policy\nSystem Event Log\nBmc self test log\nBMC network configuration\nView System Event Log\nBMC User Settings\nBMC Warm Reset\nPress (Enter) to view the System Event Log Records.\nF1: General Help\nF8: Previous Values\nF9: Optimized Defaults\nF10: Save & Exit\nESC: Exit\nVersion 2.22.1294 Copyright (C) 2026 AMI](.axe-7420gwa-50m-22811-1000-02/c7ffc1d8bb29b466857449ed00d2d587e8ead0b6eb130e339ae0f4ab1766f291.jpg)
BIOS ItemOptionsDescription
View System Event LogYesNoRetrieving all system events will take time. Do you want to continue?
# 7.10 BMC User Settings ![Aptio Setup - AMI\nServer Mgmt\nBMC User Settings\n► Add User\n► Delete User\n► Change User Settings\nPress (Enter) to Add a User.\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.1294 Copyright (C) 2026 AMI](.axe-7420gwa-50m-22811-1000-02/f3bd542c84758bf6d93b95916f25895cab13c5ea19cafc3b12c5f93f9a1dbfd3.jpg)
BIOS ItemOptionsDescription
Add UserEnterPress <Enter> to Add a User.
Delete UserEnterPress <Enter> to Delete a User.
Change User SettingsEnterPress <Enter> to Change User Settings.
# 7.11 BMC Warm Reset ![Aptio Setup - AMI\nMain Advanced Chipset Security Boot Save & Exit Server Mgmt\nIPMI Version 2.0\nIPMI BMC Interface KCS\nBMC Support (Enabled)\nIPMI Interface Type (Kcs Interface)\nWait For BMC (Disabled)\nWait For Full BMC Initialization (Disabled)\nFRB-2 Timer (Enabled)\nFRB-2 Timer timeout 6\nFRB-2 Timer Policy (Do Nothing)\nOS Watchdog Timer (Disabled)\nOS Wtd Timer Timeout 10\nOS Wtd Timer Policy (Reset)\nBMC Configured Power\nControl Policy Power Restore\nPower Control Policy (Unspecified)\n► System Event Log\n► Bmc self test log\n► BMC network configuration\n► View System Event Log\n► BMC User Settings\nBMC Warm Reset\nPress (Enter) to do Warm Reset\nBMC.\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.1294 Copyright (C) 2026 AMI](.axe-7420gwa-50m-22811-1000-02/eae1f288ea30d86d6d808cab52760f82b8d4f3758507b3e5ecb4c3f2a6e525f6.jpg)
BIOS ItemOptionsDescription
BMC Warm ResetEnterPress <Enter> to do Warm Reset BMC.
# BMC This chapter provides detailed information on understanding, configuring, and managing the BMC.
AbbreviationDescription
BMCBaseboard management controller
CLICommand line interface
FRUField replaceable unit
GUIGraphical user interface
IPMIIntelligent platform management interface
IPUIntelligence Processing Unit
NTPNetwork time protocol
PSUPower supply unit
SDRSensor data record
SELSystem event log
SNMPSimple network management protocol
SoLSerial over LAN
# 8.1 BMC Introduction # 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. # 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. # 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 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. # 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. # 8.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. # Web Login Web login to the BMC interface is a straightforward process designed to provide secure and easy access to server management tools. # 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 You can setup the BMC IP address from the server’s BIOS interface or ipmitool command listed in the section 5.3 BMC LAN Configuration. To setup from 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-7420gwa-50m-22811-1000-02/c7105e652120ba8bf53ce32bfff56ff889b7f01e45008716f83ba8f37141089b.jpg)  Security Considerations For security reasons, access to the BMC Web GUI is exclusively through HTTPS. # 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. ![ISB-W890 BMC\nUsername\nPassword\nUS - English\nRemember Username\nSign me in\nI forgot my password](.axe-7420gwa-50m-22811-1000-02/3a6163146e7a92f0386dcaef9773b7f54ac129c8582737356f30f938fc5b2c81.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 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. # 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. ![ADLINK\nISB-W890 BMC\nFirmware Information\n1.04.0\nJun 12 2026 09:36:18 CST\nHost Online\nQuick Links..\nDashboard Control Panel\n0 d 0 hrs\nPower-On Hours\n4\nAccess Logs\nMore info\nHome ) Dashboard\nSensors\nSystem Inventory\nFRU Information\nLogs & Reports\nSettings\nRemote Control\nImage Redirection\nPower Control\nMaintenance\nSign out](.axe-7420gwa-50m-22811-1000-02/5305c6d37171a6167a4449f0691d2b141403c23bb0ab44fd09feb10b1a314cd4.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.
FunctionIconDetailed Description
Message<img src="images/064540a0c795d2ba40e99dd3c57a0e1d1b6adfbff1ec09ba1bd88e4436a29e79.jpg"/>Display the messages received.
Notification<img src="images/df821db6aecddae8e6ed3eeacf3bd03d5c2af38d6fe9d43a921ea2320315d2d0.jpg"/>Display the notifications received.
Language<img src="images/1082baba26c5a6cd401c648456465dca41cbf6f267ae49766fe319c09adc893d.jpg"/>Set Board Language.
Bios interface<img src="images/2bc7905fc7d4b1e874c1da0056477c2ac18409df973cef9355ee82d90099e250.jpg"/>Open the new window or popup to configure the BIOS settings.
Dashboard Expansion<img src="images/49d64d03115d141560f10daa63ba1f404ff1e5c5dc82ce850be82ab2ec56d332.jpg"/>Show/Hide limited Dashboard Widgets.
2FA<img src="images/6c5cc5cbe3292d5e7bdfb49c830d9513facf217680c34d982ccd70b7c17340ec.jpg"/>Enable/Disable Two Factor Authentication.
Synchronization<img src="images/38418b5e38b76505e770b3aae53cc979681a70a7d1f420d6ac2b815ce26e6889.jpg"/>On/Off to synchronize with latest Sensor and Event Log updates.
Refresh<img src="images/aca3fd1c4ced604203ba3800f26d237720e1776dd31a65573fe2937272a1a522.jpg"/>Reload the current page.
Profile<img src="images/edd06bbd7d651377bf54d0f9e86061a3419b3b9ab54c8796ffa40e153441fc6a.jpg"/> [5X4T]Set the User Profile.
# 2. Server Version Information This section of the interface displays the current version information of various server components, listed in the following order: ![MegaRAC SP-X\nFirmware Information\n1.02.100\nJan 5 2026 12:03:34 CST\n● Host Offline](.axe-7420gwa-50m-22811-1000-02/63f95caff8dc495e9b607d20096dd5c82a70849780454ea4f603a7924ee7d5fb.jpg) BMC Version Information BMC Image Build Date and Time Chassis Power Status 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. The Chassis Power Status will be displayed as Host Online / Host Offline. To Change the Power Control Status, click Host Online / Host Offline link. # 3. Function Menu bar The menu bar displays the following.  Dashboard  Sensor  System Inventory  FRU Information  Logs & Reports  Settings  Remote Control  Image Redirection  Power Control  Maintenance  Sign out # Server Information # FRU Information ![The image shows a small rectangular dropdown menu box containing the number '0' on the left side and a downward-pointing triangle arrow on the right side.](.axe-7420gwa-50m-22811-1000-02/74ed393ed0d99c71325604f512010e67db3eb6a380b5aa4f30c9b761686063d4.jpg) FRU Device Name BMC\_FRU Chassis Information
Chassis Information Area Format Version1
Chassis TypeUnspecified
Chassis Part Number91-XXXX-XXX
Chassis Serial Number0000000000000000000
Chassis Extra Board Information
Board Information Area Format Version1
LanguageEnglish
Manufacture Date TimeFri Nov 17 19:33:00 2023
Board ManufacturerADLINK Technology
Board Product NameMECS-7120
Board Serial Number0000000000000000000
Board Part Number91-XXXX-XXX
FRU File ID
Board Extra
Product Information
Product Information Area Format Version1
LanguageEnglish
Product ManufacturerADLINK Technology
Product NameMECS-7120
Product Part Number91-XXXXX-XXX
Product Version1
Product Serial Number0000000000000000000
Asset TagTEST
FRU File ID
Product Extra
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:
Information CategoryDescription
Available FRU DevicesDetails about each FRU device:FRU Device IDFRU Device Name
Chassis InformationInformation related to the server's chassis, featuring:Chassis Information Area Format VersionChassis TypeChassis Part NumberChassis Serial NumberChassis Extra
Board InformationData about the server's mainboard, encompassing:Board Information Area Format VersionLanguageManufacture Date TimeBoard ManufacturerBoard Product NameBoard Serial NumberBoard Part NumberFRU File IDBoard Extra
Product InformationComprehensive details about the product, including:Product Information Area Format VersionLanguageProduct ManufacturerProduct NameProduct Part NumberProduct VersionProduct Serial NumberAsset TagFRU File IDProduct Extra
# 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 # 8.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 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 QDiscrete Sensor States (12)
Sensor NameState
ACPI_PowerS0/G0 'Working
FAN1_PresenceDevice Inserted / Device Present
FAN2_PresenceDevice Inserted / Device Present
FAN3_PresenceDevice Inserted / Device Present
FAN4_PresenceDevice Inserted / Device Present
FAN5_PresenceDevice Inserted / Device Present
HDD1_StatusDrive Presence
HDD2_StatusDrive Absence
PSU1_PresenceDevice Inserted / Device Present
PSU1_StatusPresence Detected, Power Supply Failure Detected, Power Supply Input Lost (AC/DC)
PSU2_PresenceDevice Inserted / Device Present
PSU2_StatusPresence Detected
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)
Sensor NameReadingBehavior
↓ CPU_Outlet_Temp28 °C
○ CPU_Power34 Watts
↓ CPU_TJMAX99 °C
↓ CPU_Temp31 °C
↓ DIMM_A1_Temp23 °C
♣ FAN1_Speed_Inner7050 Rpm
♣ FAN1_Speed_Outer6000 Rpm
♣ FAN2_Speed_Inner7050 Rpm
♣ FAN2_Speed_Outer6000 Rpm
♣ FAN3_Speed_Inner7050 Rpm
♣ FAN3_Speed_Outer6000 Rpm
♣ FAN4_Speed6750 Rpm
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 Q Disabled Sensors (16)
×DIMM_B1_Temp×DIMM_C1_Temp×DIMM_E1_Temp×DIMM_G1_Temp
×DIMM_H1_Temp×PSU2_Inlet_Temp×PSU2_Sec_Temp×PSU2_Prm_Temp
×TBF100_Up_Temp×TBF100_Down_Temp×PSU2_VOUT×PSU2_POUT
×PSU2_PIN×PSU2_Status×TBF100_Up_PWR×TBF100_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. # 8.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 detail All information about this sensor\nACPI_Power Sensor Information\nSensor State Reading - 0x8001\nACPI_Power Sensor Events\nJanuary 2024\nID: 48 ACPI_Power sensor of type System ACPI Power State logged a s5 or g2 soft off 3 days ago\nID: 36 ACPI_Power sensor of type System ACPI Power State logged a s0 or g0 working 3 days ago\nID: 34 ACPI_Power sensor of type System ACPI Power State logged a s5 or g2 soft off 3 days ago\nID: 18 ACPI_Power sensor of type System ACPI Power State logged a s0 or g0 working 3 days ago\nID: 16 ACPI_Power sensor of type System ACPI Power State logged a s5 or g2 soft off 3 days ago\nID: 12 ACPI_Power sensor of type System ACPI Power State logged a s0 or g0 working 3 days ago](.axe-7420gwa-50m-22811-1000-02/1ed447190d22e0259fe57d82662c5ea7f9a51da9ff7b471c29442282b910b9dd.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. ![A light green circular icon featuring a white question mark in the center, set against a white background.](.axe-7420gwa-50m-22811-1000-02/fd4ae11a0306957597dacee73609e8c64d08601383d0ffb72759ecaba0564d94.jpg) QPOV8\_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-7420gwa-50m-22811-1000-02/8462c4fd765229259e34095eb2b689f5db4a6111a0951b1fa4faedbe689188ab.jpg) 0.81Volts
Upper Non-Recoverable0.88 Volts
Upper CriticalNA
Upper Non-CriticalNA
Lower Non-Critical0.76 Volts
Lower Critical0.74 Volts
Lower Non-Recoverable0.72 Volts
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. # 8.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 two identical light green circular icons arranged side-by-side on a white background. Inside each green circle is a white question mark.](.axe-7420gwa-50m-22811-1000-02/83f82ee2831f16b6cbc04f70806acef646373e13b2a02cae77714dca5eb56750.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 ![The image displays a solid blue background featuring a white, pixelated graphic in the center. The graphic appears to be a stylized letter 'E' or a simplified document icon, characterized by a blocky white shape containing two dark, rectangular areas within it. The image is low-resolution and blurry.](.axe-7420gwa-50m-22811-1000-02/c8354bd617dd2720f2c2b7696d9af6d302b550be24ed328ea116f15a9ce48921.jpg) 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. # 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-7420gwa-50m-22811-1000-02/3d818adc8692bc6269c0167b1abfac896cedc7bbdf9c2eb9568b605c1642a1cb.jpg)  IPMI Event Log  System Log  Audit Log  Video Log  SOL Video Log # 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. ![| Event Log | Sensor Type | Event Log Count |\n| :--- | :--- | :--- |\n| January 2000 | All Events | 1 |\n| January 2022 | All Events | 3 |\n| January 2024 | All Events | 2 |](.axe-7420gwa-50m-22811-1000-02/9cc7709ce627f56abf155ef59f8f77c4ba5be5eb76e5fb4ead7cacf5cb4124df.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. # 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-7420gwa-50m-22811-1000-02/ef0fe86d9546b43eac869f767d4ff76c86807d5f9621ffdf3b6012aeb732c17c.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. # 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-7420gwa-50m-22811-1000-02/3c0eab3945b780a87dd3c33314b8b787055d1ca5e55df98a8b256e0ccfac603c.jpg) # 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-7420gwa-50m-22811-1000-02/9f461ceae2c9bb27678104c12ab57345f120bee86359e0cb6465f9b6d4402092.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 8:00\nUS - English\n2FA\nSync\nRefresh\nadmin\nHome ) Video Log\nID: 1 an hour ago](.axe-7420gwa-50m-22811-1000-02/120043b376ff61e443ea9b82bfe7a99f847a0322f41626f69efc2fa1e6b1cc15.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. # 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-7420gwa-50m-22811-1000-02/c17ff3315a6fbbf1493ef9eb8380790edac565a1052bf4eff8d3b9b5ebd39cb0.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. # 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 # Power Actions ![The image shows two light green circular icons positioned side-by-side. Inside each circle is a white question mark centered vertically. The background is white.](.axe-7420gwa-50m-22811-1000-02/12912ee0bad1bd961cabe15cf7caa23458c1ce7e5794876facc69876dd28f776.jpg) # ![A horizontal row of white circles arranged against a solid black background. The circles are evenly spaced and appear to be touching or slightly overlapping, creating a chain-like effect. Four complete circles are fully visible in the center, flanked by partial circles visible on the far left and far right edges.](.axe-7420gwa-50m-22811-1000-02/588a6b25231a0045e86746a1100c30380e418c9a32e0299639bd48b49fd47239.jpg) Power Off ![The image displays three faint, light gray concentric rings or circles arranged horizontally against a plain white background. There is no visible text.](.axe-7420gwa-50m-22811-1000-02/02384692d4343b229c1c4214f026accf55dadf16e35e0a1712a7876823a0d771.jpg) Power On ![Four white plates with raised rims and central indentations are arranged in a horizontal row against a plain background. There is no text in the image.](.axe-7420gwa-50m-22811-1000-02/7fbb4649db78d3900b77ba01879fee733fc926c7f7b628d0438cc098de8ee0fa.jpg) Power Cycle ![The image displays a blue circle containing a white checkmark centered within it.](.axe-7420gwa-50m-22811-1000-02/b7c028bfef3a4b2c31b5f73bdf56bbb32ff44815d6d41933b29a949f00929485.jpg) Hard Reset ![The image displays a vertical black line on the left side. To the right of this line is a circle drawn with a thin black outline and a white interior, set against a white background.](.axe-7420gwa-50m-22811-1000-02/25d6a388d35790ad37e3179e94fd10e5c43f11bd36a46747e601684840085507.jpg) ACPI Shutdown ![The image displays two white power icons arranged horizontally on a solid blue background.](.axe-7420gwa-50m-22811-1000-02/ad8435b3acb0bd40cc38a12fdeff6f371d762f9e57e65e4c287f4fd2b7776017.jpg) Perform Action 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. # 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. Settings ![Captured BSOD\nLog Settings\nPlatform Event Filter\nSystem Firewall](.axe-7420gwa-50m-22811-1000-02/fb9070b62dcd14dbc8b5fa1d3a29f99f28a999f485f08041ae4a0777a6e4c83f.jpg) ![Date & Time\nMedia Redirection Settings\nServices\nUser Management](.axe-7420gwa-50m-22811-1000-02/0221523705ace6d1f27a80803b466061b4effa8a52ba62df9d4216f2ec67ece5.jpg) ![External User Services\nNetwork Settings\nSMTP Settings\nVideo Recording](.axe-7420gwa-50m-22811-1000-02/7c5b182bb71dcbce5b7654ae9798c094d32340263b2407ad60aafef67b1a7b2f.jpg) ![KVM Mouse Setting\nPAM Order Settings\nSSL Settings\nIPMI Interfaces](.axe-7420gwa-50m-22811-1000-02/a935b0aafab7d583a070820485dd0215bbb1b2eeb9a76299d942d3a39103ddf7.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. # 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@amlqa:~\nroot@amlqa:-# 15:23](.axe-7420gwa-50m-22811-1000-02/f1e3c4d9ef62b5979c9adaa35bd2d80e5dd5ccac188c59997f1cd3d85952508c.jpg) Note: KVM service should be enabled to display the BSOD screen. KVM Service can be configured under Settings > Services > KVM. # 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 left half of a light green circle containing a white question mark.](.axe-7420gwa-50m-22811-1000-02/9a72c518420f7ffe18a89f41952e69e99509cfef923119bf8e429af60647d407.jpg) ![World map with scattered white circular markers indicating locations, no text or labels present](.axe-7420gwa-50m-22811-1000-02/b10930a687eef56712bc3345bce4745c00887cc59382b6803bec11a79c29cd94.jpg) \_Feb 26,202410:45:52AM(GMT+08:00 CST)-Asia/Shanghai ![The image contains no text. It depicts a simple black-and-white line drawing featuring a thin vertical black line on the left side and a large, empty rectangle with a double-line border to its right.](.axe-7420gwa-50m-22811-1000-02/0e82f2e8648f707e5b173bfa2b6b51668d61d7ade977684fe557a2e8b377fa8d.jpg) AutomaticNTPDate&Time ![The image displays a cropped vertical section of a graphic interface. On the left side, there is a blue rectangular area containing a white, downward-pointing arrow (or chevron) in its center. To the right of this blue area is a plain white background. There is no text present in the image.](.axe-7420gwa-50m-22811-1000-02/2272b65e14d4799966ac3781e8cbca7b9b89e21cc5f53d106b838c1b6c617422.jpg) Automatic PTP Date& Time PTP Interface ![The image features a white background above a solid black horizontal line. Four small, dark, triangular shapes are arranged in a row along the top edge of the black line. There is no text in the image.](.axe-7420gwa-50m-22811-1000-02/406940823c8cb51107123335ca2354fca8f171181ee91a8a50a75db09c5324f3.jpg) PTP Preset ![The image displays a white background with a thin, horizontal black line running across the center. On the left side of the line, there is a black shape resembling a bow tie or a rolled towel. On the right side, there is a black shape resembling a pair of scissors.](.axe-7420gwa-50m-22811-1000-02/753563b3a46559e1ea4ef01f4c26e1a6c9e9eb4638afcd3e402f42ef5cd18604.jpg) PTP Transport ![The image displays a black, downward-pointing chevron or arrow symbol centered against a white background.](.axe-7420gwa-50m-22811-1000-02/789163c41d1272d33713bbe5cac26417c0cfd91abd0e2f70e9f0d5ee34aa8e06.jpg) Unicast ![The image displays a vertical column of six identical black shapes against a plain white background. Each shape is a solid, downward-pointing triangle or chevron, evenly spaced and centered horizontally.](.axe-7420gwa-50m-22811-1000-02/6e71338f5e1cd7742b1f1267e0f5976193f763858fbf8bd4417efa58ecf1e20f.jpg) PTPUnicast IP ![The image displays a thin, black horizontal line running across the very top edge against a plain white background.](.axe-7420gwa-50m-22811-1000-02/40b76945bf6e80de8858636d764d255b7f2422021f549dbe5ad1eff17350499e.jpg) PTP Delay Mechanism E2E ![Two black, downward-pointing chevrons are centered horizontally on a plain white background.](.axe-7420gwa-50m-22811-1000-02/4f97b19752e54411ef9b86082bb04b12438331f6c50b4c16a53c3bba4ccc8bc5.jpg) PTP Inbound Latency ![The image displays a white background with two thin, horizontal black lines. One line runs across the very top edge, and the other runs across the very bottom edge. There is no text present in the image.](.axe-7420gwa-50m-22811-1000-02/7bd56e73575ef4b88a5759c332fc972df99f3ac0fc8631d9bb0f5a7b933a8bd1.jpg) PTP Outbound Latency ![The image displays a blank, solid white horizontal rectangle. There is no text or other content visible.](.axe-7420gwa-50m-22811-1000-02/c772c4e8eb1408fb789162ce4c4a4f267de14561bb27556185f2f34ec48cef42.jpg) PTP Priority1 ![The image displays a white rectangular area. A thick black vertical line runs along the entire left edge, and a thin grey horizontal line is visible at the very top edge. There is no text.](.axe-7420gwa-50m-22811-1000-02/26c8fa1f54e756f2ef09e780607465a82bb2aca4c7f91bb5d31f971ec135712c.jpg) PTP Max Master capacity 5 ![The image displays a white background with two thin, vertical black lines running parallel to each other.](.axe-7420gwa-50m-22811-1000-02/4f1c6314178f9bd181525f00e00c331e659753a78a4356c52f87316787a6e027.jpg) ![The image displays a fragment of a grid or table structure on a white background. Visible elements include thin black vertical lines on the far left, center, and right sides, along with horizontal lines near the top. The arrangement of lines suggests a partial view of rectangular cells. There is no text present.](.axe-7420gwa-50m-22811-1000-02/cfa7c3f9d7f8680a012dbb909f3645371356f9e16eb50c506696b424fd843131.jpg) Panic Mode PTP Log request delay 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. # External User Services # 8.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 ![The image shows a dark grey icon resembling a document or notepad, tilted slightly to the left. On its surface, there are three horizontal white lines stacked vertically, representing text or a list. The object has a slight 3D appearance, with a darker shaded edge on the left side.](.axe-7420gwa-50m-22811-1000-02/813f13b6d5343f7195b4a8694eddf18438f3a1c71c4bbfe9dc7d15da3d519dd2.jpg) ![The image displays two dark, vertical, rounded rectangular shapes positioned side-by-side against a white background. There is no text present.](.axe-7420gwa-50m-22811-1000-02/b88f99216b29b09997ac91cc66d913708d7d7fe0e26ca86b097adf6a61e61ccf.jpg) ![The image displays a blurry, black silhouette of a telephone handset receiver positioned vertically against a plain white background.](.axe-7420gwa-50m-22811-1000-02/a9d0478f2ba8ab054af8d4e7b1d98d171d93cedc766efac9079a5f123e8f51c0.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 ![The image displays a simple black icon of a book, tilted slightly to the right. It features a dark, rounded rectangular shape with two horizontal white lines centered on the cover, resembling text.](.axe-7420gwa-50m-22811-1000-02/813d3536baeb02a66a265a3da90eba584c59541d2ede058409163a1761f50417.jpg) ![The image displays a black and white icon resembling a medal or award. It features a large circle at the top with a thick black outline and a solid black center. Below the circular section are two ribbon tails extending downwards.](.axe-7420gwa-50m-22811-1000-02/73a0d0451143c0abe66e981a3df4ed8380392a7b6a70588ee8228c43ca82e537.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-7420gwa-50m-22811-1000-02/709577fe7033c95b28d9a415afa6c6b7f327b49ad238cf5916cc846c304500b4.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. 5. Specify the LDAP Port in the Port field. Note: Default Port is 389. For SSL connections, default port is 636. The Port value ranges from 1 to 65535. 6. 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 7. 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. 8. 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. 9. 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. 10. Select CA Certificate File from the Browse field to identify the certificate of the trusted CA certs. 11. Select the Certificate File to find the client certificate filename. 12. Select Private Key to find the client private key filename. Note: All the 3 files are required, when SSL or StartTLS is enabled. 13. 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-7420gwa-50m-22811-1000-02/399273b0ad9de9c03d6c24549fa2447d8aa0f7480f4ad17f2f361de638890271.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.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 ![This is a vertical, low-resolution close-up image. On the far left is a thin, black vertical strip. To the right of this strip are two large, vertical, dark grey shapes with rounded tops that resemble buttons or columns. The image is extremely zoomed in, obscuring any specific context, and there is no legible text visible.](.axe-7420gwa-50m-22811-1000-02/f324311f13decf640d5f3a9d2078e46e900e3b3c681163e7be2f0861565b075e.jpg) ![The image displays a low-resolution, grayscale icon resembling a prize medal or rosette. It features a circular top composed of concentric rings, situated above two triangular shapes pointing downward that resemble ribbons.](.axe-7420gwa-50m-22811-1000-02/739cc12fede0007eab528e4cbe28707a9204f75e50e019a515214ffb4a3cdbf8.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 ![Enable 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-7420gwa-50m-22811-1000-02/7b4c8c8cbf9a4acb1c1a08b38206406e269c18d66033a62df323df096cc4da0e.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 support 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-7420gwa-50m-22811-1000-02/09211bdc765a16e80a7f8c3f334e57b6d3a378017836072725dae23014ec4b44.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](.axe-7420gwa-50m-22811-1000-02/731f38513018d2b364304e5c2bb63e93ee05f8443f0c769b56e1e1cc29314741.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. # 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 grey telephone handset icon centered horizontally. Below the icon, the text 'General RADIUS Settings' is written in grey.](.axe-7420gwa-50m-22811-1000-02/5332e0b75f8b44b899df2b7816ab5017f6bdb97a36b31c33a25d9420365c02df.jpg) ![The image displays a white background featuring a centered gray icon resembling a gear composed of puzzle pieces. Directly below the icon is the gray text 'Advanced RADIUS Settings'.](.axe-7420gwa-50m-22811-1000-02/ea58434dbe860889b924744a65453d39ca8d4e47c0253bd435fd0c18160983ec.jpg) # General RADIUS Settings General RADIUS Settings ![Enable RADIUS Authentication\nServer Address\n\nPort\n1812\n\nSecret\n\nEnable KVM Access\nEnable VMedia Access\n\nSave](.axe-7420gwa-50m-22811-1000-02/a5a1cab2b409aa1d870f2ed031aefdb0207b9440f59d0c5a851a11fcde160a71.jpg) 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-7420gwa-50m-22811-1000-02/9462320fe99a4755fba6fb08c275e16c56cb0a78d7df7899cd9c648b272abdb8.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. # Service Management It is used to set service information on the BMC. A sample screenshot of service management is shown as below. Services Home
Service ⇆Status ⇆Interfaces ⇆Secure Port ⇆Timeout ⇆Maximum Sessions ⇆
webActiveboth443180020≡ √
kvmActiveboth44318004≡ √
cd-mediaActiveboth443N/A4≡ √
hd-mediaActiveboth443N/A4≡ √
sshActiveNA22600N/A≡ √
watchdogInactiveNAN/AN/A1≡ √
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](.axe-7420gwa-50m-22811-1000-02/b7df9f6bd5adcd8c47ba2668804942955d4d19d7a5a50c42334234093554505b.jpg) # 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. # 8.2.6.6.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-7420gwa-50m-22811-1000-02/638aaa40c0321d2e9a32f56ef50352a99d6073bb42c22ce1ed20cc003aa8480f.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. ![A blue square icon featuring a white checkmark in the center.](.axe-7420gwa-50m-22811-1000-02/e2d8b8e8c9c3114ca747959e50caf28fc30f6864a198a707e0f05a085a98f43b.jpg) Enable IPv6 ![The image displays a vertical schematic or diagram. In the center is a large white rectangle. Flanking this rectangle on both the left and right sides are thin vertical gray lines. Outside of those gray lines are thicker black vertical bars. On the far left and far right edges, there are additional thin vertical gray lines.](.axe-7420gwa-50m-22811-1000-02/e5520bf058b8a31bf1b58540e503228bcbe21fab69408d9c9c3fe67482e50834.jpg) Enable IPv6 DHCP IPv6 Index 0 < IPv6 Address fe80::15ca:1212:749e:8f27%4 Subnet Prefix Length 0 IPv6 Gateway  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. ![The image displays a diagram consisting of three adjacent rectangular boxes arranged horizontally. From left to right, the boxes contain the letters 'A', 'B', and 'C' respectively.](.axe-7420gwa-50m-22811-1000-02/ece67f9358c6046a7ff3b6e15b87e2a3db9dc881b6d5198e446a7f3e8dfb8f3e.jpg) Enable VLAN VLAN ID VLAN Priority ![The image features a white, pixelated icon of a floppy disk centered on a solid blue background. This is the universal symbol for 'Save.' The icon consists of a rectangular outline with a smaller rectangular cutout near the top and a square cutout in the lower right section.](.axe-7420gwa-50m-22811-1000-02/cd663b7330224db9f6f9f55bc5a3ef9aa4fa3793e80904342fc45a832d7c3a14.jpg) Save  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. # 8.2.6.6.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-7420gwa-50m-22811-1000-02/d598013d99533c9afe313f5306e0596ee6256295f6e5cefc472da241dfd53360.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. # 8.2.6.6.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-7420gwa-50m-22811-1000-02/948bcfa96aef607364559c1db33656cfc520b27fe54896b89e773e1b513b5b1f.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 within it.](.axe-7420gwa-50m-22811-1000-02/1e932185febf457b29c1e55d0b05ddf18cb94a356b9ad36a99e6d89a5a96eb9f.jpg) Register BMC Registration Method ![A blue circle with a white check mark in the center.](.axe-7420gwa-50m-22811-1000-02/fb37c57bfcd65ca492517ca10b0273764a353938235ac256d24ea23d497f48a5.jpg) Nsupdate ![Three white circles are arranged horizontally against a light grey background, separated by thin vertical black lines.](.axe-7420gwa-50m-22811-1000-02/4e214db44f652506ddd81fb878e8826ca191d78c930116304ddd8d62b145f981.jpg) DHCP Client FQDN ![The image displays a vertical composition featuring solid black bars on the left and right edges. Centered between them is a large white square. Inside this white square is a concentric square outline drawn in a thin, faint gray line.](.axe-7420gwa-50m-22811-1000-02/bc2c3b5c26d333a0525380378da9223f7536996e39adba16c0f25907897c4d0d.jpg) Hostname BMC Interface eth1 ![The image displays a cropped view of a digital interface featuring two adjacent light blue squares. Each square contains a centered white checkmark. A thin dark vertical strip runs along the far left edge.](.axe-7420gwa-50m-22811-1000-02/680b0dde51ede63d7085ba667fb6c7d6e4c986e13bcee3fcda693ae970758c90.jpg) Register BMC Registration Method ![The image displays a blue circle containing a white checkmark in the center.](.axe-7420gwa-50m-22811-1000-02/28a272b6ac299412b6ba0b0b237af7b82e66ea24e4ad439f9fe36164726d591f.jpg) Nsupdate ![The image displays three white circles aligned horizontally in a row against a black background. A black horizontal bar runs across the very top edge of the image.](.axe-7420gwa-50m-22811-1000-02/5e3e5e52e0ee979515e5b2184481ef1016fc488d75f1e7faee75b8ee1e8cbb50.jpg) DHCP Client FQDN ![The image displays a white background with a thin black horizontal line running across the very top edge. Below this line are two white circles with thin grey outlines, positioned side-by-side. There is no visible text.](.axe-7420gwa-50m-22811-1000-02/5a3ef8c5834fdeaadee07f115ecf3eda9936b01fc9225968f97c4d4a739d6056.jpg) Hostname # BMC Registration Settings  BMC Interface: Options to register the BMC through the Interfaces (eth0ð1).  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-7420gwa-50m-22811-1000-02/0a9db855a137b57c95445aa9b776e6acf00c46cfa757bb7c1c2f7f625fbd4803.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 centered white checkmark.](.axe-7420gwa-50m-22811-1000-02/9b06e6acd286c1e81cfb48e008bea79880dde0aee72665cc4dfbfd62c06ab139.jpg) Automatic ![The image displays two identical white circles with thin black outlines, arranged vertically with one positioned directly above the other on a white background.](.axe-7420gwa-50m-22811-1000-02/240469751a157c9cb7eae4c12036c2f94e0b4621838d0fc76e3d406a38bb6cec.jpg) Manual Domain Interface eth1\_v4  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 ![A blue circle containing a white checkmark in the center.](.axe-7420gwa-50m-22811-1000-02/6fc3149c1538567cc07678a06a1102fb4eba35bafe9cd592fef3a712e632b096.jpg) Automatic ![The image displays four white circles arranged horizontally in a row. There is no text present.](.axe-7420gwa-50m-22811-1000-02/e585312b86471c84b5b900cb9d80d8e9e1cf4ad65ca89fa936377192cdd24a79.jpg) Manual DNS Interface IP Priority ![The image displays a blue circle containing a white checkmark in its center. The checkmark is stylized with a thick stroke. The circle appears to be part of a user interface icon, likely indicating a 'success' or 'completed' status. There is no text in the image.](.axe-7420gwa-50m-22811-1000-02/db32c7f697f8f36fc6a8cb3c2bcaf2686e866bb98a736a1e2fa4c63f4623f38c.jpg) IPv4 ![The image displays three identical white circles arranged horizontally in a row against a black background. The circles are evenly spaced and appear to be part of a loading or progress indicator.](.axe-7420gwa-50m-22811-1000-02/3086c7a7bc297254f35d0da5aa116c238b733df8271fe027a436fd17e4602925.jpg) IPv6 ![The image features a white icon of a floppy disk, commonly used to represent the 'Save' function, set against a solid blue background. The icon is positioned on the right side of the frame, next to a thin vertical strip visible along the far left edge.](.axe-7420gwa-50m-22811-1000-02/5ca0a89a270b7b833ddd2078b9b541ad3bf78e05e9a483a6a873c353cab48304.jpg) Save  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. # 8.2.6.6.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-7420gwa-50m-22811-1000-02/5c9577eaa6fdc365fe36f212e975240071df907a268a9e0ab0d0ba9d5e21d8fe.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. # 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 ![This image displays a cropped section of a bright green interface element, likely a button. It features a white icon depicting an arrow pointing diagonally upwards and to the right, emerging from the corner of an open square, which is the standard symbol for 'open in new tab' or an external link. There is no visible text in the image.](.axe-7420gwa-50m-22811-1000-02/06d7e143ddb25f6de6f1b176645f3d3ad992105cf63206b573c8b0615db99b48.jpg) Launch H5Viewer Serial Over LAN ![The image displays a cropped, low-resolution section of a white icon set against a solid bright green background. The icon consists of a square outline with an arrow inside it, pointing diagonally upwards and to the right from the upper right corner, resembling a 'share' or 'external link' symbol. There is no text visible in the image.](.axe-7420gwa-50m-22811-1000-02/844d61cc25a6264f7948006936e7aa2fbd188015356c81f25c7a51f5520516c5.jpg) Activate # 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\nCD Image: Browse File (0 KB) Start Media\nVideo Mouse Options Keyboard Send Keys Hot Keys Video Record Power Active Users Help\nZoom 100%\n1月 19 11:21\nUsername\nUbuntu\nLWIN RWIN LALT LCTRL RALT RCTRL NUM CAPS SCR](.axe-7420gwa-50m-22811-1000-02/919d6ab07b73057f800dfa981b233e4eb9656f6bea5da4805aeca4fbd5c385b5.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-22.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 <CTRL> key when in Console Redirection. Right Alt Key: This menu item can be used to act as the right-side <ALT> key when in Console Redirection. Right Windows Key: This menu item can be used to act as the right-side <WIN> key when in Console Redirection. Left Ctrl Key: This menu item can be used to act as the left-side <CTRL> key when in Console Redirection. Left Alt Key: This menu item can be used to act as the left-side <ALT> key when in Console Redirection. Left Windows Key: This menu item can be used to act as the left-side <WIN> 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 <CTRL>, <ALT>and<DEL> 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 <WIN> 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 <WIN> 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.
Quick ButtonsExplanation
This quick button will show / hide notifications dropdown menu, which will contain the list of notifications displayed by H5Viewer.
Zoom 100%It shows the current zoom value in percentage.
<img src="images/73d3e0fbcebf9dab50213f29ef4a6d2f42b7c6f5275f5b1518ce6e4ed894ee8a.jpg"/>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.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.
# Status bar buttons
LWINRWINLALTLCTRLRALTRCTRLNUMCAPSSCR
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 LEDstatus will be synced with client LEDstatus, only if user pressesany 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 admin 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) You have 4 more seconds to make a decision.The YES option will be chosen if no answer is obtained. Full Permission Partial Permission Block Privilege Request No Permission Partial Permission No Permission 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. # 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.
Aptio Setup - AMI
MainAdvancedPlatformConfigurationSocket ConfigurationServer Mgmt S
BIOS InformationSet the Date.
BIOS VendorAmerican Megatrendsswitch between
BIOS Version1.2.10Default Range
Build Date01/24/2024Year: 1998-99
RC Version370.P03Months: 1-12
SPS FW Version6.1.2.48Days: Depende
Range of Year
System Information
Project NameMECS-7120
CPU Board VersionA1
CPU Brand StringIntel(R) Xeon? Gold 542 3N
CPU Frequency2.10GHz-----
Total Memory16384 MB (DDR5)><: Select Sc
Memory Frequency4000 MHz^v: Select It
PCH SKUEBG B1Enter: Select
---- Save & Exit ----+/-: Change O
System DateQuit without saving?F1: General H
System TimeF8: Previous
F9: Optimized
Access Level----F10: Save & E
Yes NoESC: Exit
PCH SKU----
# Server Maintenance This function is mainly maintenance tasks on the device. Click Maintenance on the left function bar to enter the following interface. ![Maintenance\nBackup Configuration\nDual Image configuration\nFirmware Image Location\nFirmware Information\nFirmware Update\nPreserve Configuration\nRestore Configuration\nRestore Factory Defaults\nSystem Administrator](.axe-7420gwa-50m-22811-1000-02/da2c1c31924e325e1ebbee6a41095313a8178f1f8d4649435d9ed3ae212604a4.jpg) # 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. # 8.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\nCheck All\nSDR\nFRU\nSEL\nIPMI\nNetwork\nNTP\nSNMP\nSSH\nKVM\nAuthentication\nSyslog\nWeb\nExtlog\nRedfish\nSave](.axe-7420gwa-50m-22811-1000-02/b297ab8ec29e918ea806d331dd1ac4229e88da19e0e507e4be7db02cddef87d6.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\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\nSelect Firmware Image\nStart firmware update\nProtocol Type: HTTPS\nThe dual image formation to be used for firmware update is displayed as follows. To configure Image to be booted from upon\nReset, choose 'Dual image Configuration' under Maintenance.\nCurrent Active Image Image-1\nImage to be Updated\nInactive Image\nPreserve all Configuration. This will preserve all the configuration settings during the firmware update - irrespective of\nthe Individual Items marked as preserve/overwrite in the table below.\nAll configuration items below will be preserved as default during the restore configuration operation. Click 'Edit Preserve\nConfiguration' to modify the Preserve status settings.\nEdit Preserve Configuration\nS.No Preserve Configuration Item Preserve Status\n1 SDR Overwrite\n2 FRU Overwrite\n3 SEL Overwrite\n4 IPMI Overwrite\n5 NETWORK Overwrite\n6 NTP Overwrite\n7 SNMP Overwrite\n8 SSH Overwrite\n9 KVM Overwrite\n10 AUTHENTICATION Overwrite\n11 SYSLOG Overwrite\n12 WEB Overwrite\n13 EXTLOG Overwrite\n14 REDFISH Overwrite\nProceed to Flash\nWARNING:Please note that after entering the update mode, the widgets, other web pages and services will not work. All the open\nwidgets will be automatically closed. If the upgrading is cancelled in the middle of the wizard, the device will be reset only for BMC\nBOOT,and APP components of Firmware.](.axe-7420gwa-50m-22811-1000-02/f386a8cd268155112ca8088ad398b6c27711356dcf9ead36d852656fbbaeb0b9.jpg) 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-7420gwa-50m-22811-1000-02/f20d42fc8e4e36711a36fab0adea1bb38bcf9467616306d48f32a2f12d30c937.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 a few module versions differ, those modules will be flashed. Section Based Firmware Update The following section is used to allow the user to configure the firmware image for section based flashing.
□ Version Compare Flash□ Full Flash
Section NameImage-1 VersionImage-2 VersionUploaded versionUpgradable/Non-Upgradable
boot13.5.00000013.5.00000013.5.000000
conf13.5.00000013.5.00000013.5.000000
root13.5.00000013.5.00000013.5.000000
osimage13.5.00000013.5.00000013.5.000000
www13.5.00000013.5.00000013.5.000000
extlog13.5.00000013.5.00000013.5.000000
extlog13.5.0000000.0.13.5.000000
bootlogo1.0.0000001.0.0000001.0.000000
arcity13.5.01000313.5.01000213.5.010003
e) Flashing Firmware Image f) Resetting the image # 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 ![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• 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-7420gwa-50m-22811-1000-02/953277e6a67da31282510cd9acbf061d309adfb0a04f5ca98c2bf8b616e422b4.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 shows a pair of buttons. On the left is a blue button with the text 'OK' in white. On the right is a white button with the text 'Cancel' in black.](.axe-7420gwa-50m-22811-1000-02/def270e141c49acd1e3fc9f60575993167045e260bd111cff600518bbcc32edb.jpg) 4. Select the components from the list to flash. BIOS is mandatory, ME and NVRAM are optional. 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• BIOS Firmware update.\n\nSelect Firmware Image\nMECS-7120_1110.BIN\n\nStart firmware update\n\nPreparing to flash...\n\nList of Components\n# Component Name Existing Version Uploaded Version Upgrade Progress\n1 BIOS 2280811 In progress...\n2 ME \n3 NVRAM \n\nProceed to flash image 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 upgrading is cancelled in the middle of the wizard, the device will be reset only for BMC BOOT, and APP components of Firmware.](.axe-7420gwa-50m-22811-1000-02/09bfa4161001fd74aec3fded45c222eaf83ebb5b9d0bafbdbf945a7a508a1f07.jpg) 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. OK # 8.2.8.2.1 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 ./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". ☑ Enable real-time ISP to allow background 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 ![A low-resolution, cropped image featuring a blurry white shape resembling the letter 'F' or a flag icon set against a solid blue background.](.axe-7420gwa-50m-22811-1000-02/8d05599b9b18ee1f94eada1d37273f951624039a56e564a7f96695d0de145bfd.jpg) Start firmware update ![The image displays a close-up of a blue square icon containing a white checkmark in the center. It appears to be a selected checkbox interface element. The image is cropped on the left side and shows some pixelation. There is no text present.](.axe-7420gwa-50m-22811-1000-02/267a42cfc1a4a3bcf440a6b25b24eced2d7e789e48eaf538d256d3c966edcf68.jpg) List of Components
#Component NameExisting VersionUploaded VersionUpgrade
1CPLD0.0.02.4.35651584
List of CPLD devices
NameInterfaceInterface NumberID CodeFirmware Version
ALTERA 10M50DA CPLDJTAG0x00x31050dd0x65bba5
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 shown 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-7420gwa-50m-22811-1000-02/2049d35b5820399c44ca59b2185372401d767399dbebc14f0b8a066d2415020d.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 # Firmware Configuration # 8.2.8.3.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-7420gwa-50m-22811-1000-02/730de5ff9144c7d35acd08786c4a357564d66eb8f2fa24443e024a83c7168ed0.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. # 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 ![The image displays a bright green rectangular button. On the left side is a white icon depicting a downward-pointing arrow above a horizontal line. To the right of the icon is the white text 'Download' in a sans-serif font.](.axe-7420gwa-50m-22811-1000-02/316cf47457f929795af1aeffc2f7fb2030667ff87be9c745e3d36362c2e27039.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 # Firmware and Hardware versions To get the version info of BMC, BIOS, CPLD and hardware, please refer to home page, up-left 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-7420gwa-50m-22811-1000-02/4a79ae1ce7a1fdf085a86e89b5e8dc261cb0be249cd30d733a2ecc1ba86aacc8.jpg) # 8.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. # 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. # 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).
ParameterAliasDescription
-H--hostnameHostname or IP address of the target server (for network interfaces).
-U--userUsername for login.
-P--passwordPassword for login (recommended to be input interactively for security).
# 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: ![~ # ipmitool -I lan -H 127.0.0.1 -U admin -P admin.123 mc info\nIOCTL to get IP failed: -1\nDevice ID : 32\nDevice Revision : 1\nFirmware Revision : 1.03\nIPMI Version : 2.0\nManufacturer ID : 24339\nManufacturer Name : ADLINK Technology Inc.\nProduct ID : 28960 (0x7120)\nProduct Name : Unknown (0x7120)\nDevice Available : yes\nProvides Device SDRs : yes\nAdditional Device Support :\nSensor Device\nSDR Repository Device\nSEL Device\nFRU Inventory Device\nIPMB Event Receiver\nIPMB Event Generator\nChassis Device\nAux Firmware Rev Info :\n0x11\n0x0d\n0x10\n0xb9](.axe-7420gwa-50m-22811-1000-02/283440f27285650cc0efcf3d6b29508eabc374a5699c071c48cc11a3a16f3f47.jpg) # 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# ``` # ipmitool Command Introduction This section is dedicated to introducing and explaining a variety of ipmitool commands, with detailed descriptions of their specific uses. # 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:
Return DetailsDescription
Sensor NameIdentifies the sensor.
ReadingThe current value or status reported by the sensor.
UnitsThe measurement units for the sensor reading.
StatusIndicates the operational status of the sensor.
Lower/Upper ThresholdsThe predefined limits for the sensor values, indicating warning or critical conditions.
Example:
root@adlink-Default-string:/home/adlink# ipmitool sensor list
P12V_PSU12.230Voltsok10.80011.16011.40012.60012.84013.200
P12V_AUX12.200Voltsok10.80011.16011.40012.60012.84013.200
P3V33.315Voltsok2.9703.0693.1353.4653.5313.630
P5V5.120Voltsok4.5004.6504.7505.2505.3505.500
PVNN_PCH_AUX0.905Voltsok0.8100.8370.8550.9410.9630.990
P1V05_PCH_AUX1.057Voltsok0.9450.9770.9981.0821.1241.155
P1V8_AUX1.816Voltsok1.6201.6741.7281.8641.9261.980
P3V_BAT2.998Voltsok2.0022.3022.5003.1483.2083.298
PVCCIN_CPU1.813Voltsok1.4411.4891.5191.8911.9271.981
POV8_E8100.822Voltsok0.7200.7440.760nana0.880
PVCCINFAON1.090Voltsok0.8560.9000.9301.1301.1501.180
P3V3_AUX3.300Voltsok2.9703.0693.1353.4653.5313.630
PVCCFA_EHV_FIVRA1.812Voltsok1.6201.6741.7101.8901.9261.980
POV9_E8100.888Voltsok0.8100.8370.8550.9450.9630.990
PVCCD_HV1.124Voltsok0.9901.0301.0501.1921.2201.270
P12V_S3_DIMM12.060Voltsok10.80011.16011.40012.60012.84013.200
PCIE_Outlet_Temp27.000degrees Coknanana55.00060.00065.000
CPU_Outlet_Temp33.000degrees Coknananananana
SYS_Inlet_Temp28.000degrees Coknananananana
HDD_BP_Temp22.000degrees Coknanana47.00051.00055.000
CPU_Temp37.000degrees Coknanana91.00095.00099.000
CPU_TJMAX97.000degrees Coknananananana
PCH_Temp31.000degrees Coknananananana
DIMM_A1_Tempnadegrees Cnananana106.000116.000125.000
DIMM_B1_Tempnadegrees Cnananana106.000116.000125.000
DIMM_C1_Tempnadegrees Cnananana106.000116.000125.000
DIMM_E1_Temp31.000degrees Coknanana106.000116.000125.000
DIMM_G1_Tempnadegrees Cnananana106.000116.000125.000
DIMM_H1_Tempnadegrees Cnananana106.000116.000125.000
ACPI_Power0x0discrete0x0180nananananana
# Other ipmitool Commands Related to Sensor Information Below is a table summarizing additional ipmitool commands pertinent to sensor management and monitoring: # Power Control Using ipmitool commands, you can effectively control the power mode. # 8.3.2.2.1 Power Control Method Using ipmitool command, it can control the power, such as power on, power off, power cycle, power reset. # Command: ```typescript ipmitool power <on | off | cycle | reset> ```
Command ElementDescription
ipmitool power onPower on the chassis.
ipmitool power offPower off the chassis.
ipmitool power cyclePower off the chassis and power on the chassis.
ipmitool power resetRestart the chassis.
# 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 ``` # Network Configuration # 8.3.2.3.1 Get the current configuration of the management port ipmitool lan print [<channel number>] 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 ``` # 8.3.2.3.2 Set the IP address source ipmitool lan set <channel number> ipsrc <source> source: ```yaml - static: manually configured static IP address - dhcp: address obtained by BMC running DHCP ``` # 8.3.2.3.3 Set the IP Address ```txt ipmitool lan set <channel number> ipaddr <x.x.x.x> ``` # Example: ```batch root@bmc:/# ipmitool lan set 8 ipaddr 192.168.1.100 ``` ```txt Setting LAN IP Address to 192.168.1.100 ``` # 8.3.2.3.4 Set the Netmask ```txt ipmitool lan set <channel number> netmask <x.x.x.x> ``` # 8.3.2.3.5 Set the Default Gateway IP Address ```txt ipmitool lan set <channel number> defqw ipaddr <x.x.x.x> ``` Note: Make sure the gateway IP address is pingable. # 8.3.2.3.6 Set Network Configuration via BIOS Enter BIOS Setup > Server Mgmt > BMC network configuration. Aptio Setup - AMI Server Mgmt ```txt --BMC network configuration-- ^|Select to configure LAN ^ * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * |channel parameters * Configure IPv4 support * |statically or * * * * * * * * * * * * * * * * * * * * * * * +|BMC). Unspecified * Lan channel 1 +|option will not modify * Configuration Address [Unspecified] +|any BMC network + Current Configuration DynamicAddressBmcDhcp +|parameters during BIOS v| Station IP address 0.0.0.0 +| Subnet mask 0.0.0.0 +|---- Station MAC address 00-30-64-66-77-88 +|><: Select Screen | Router IP address 0.0.0.0 +|^v: Select Item | Router MAC address 00-00-00-00-00-00 +|Enter: Select | Lan channel 2 +|+/-: Change Opt. | Configuration Address [Unspecified] +|F1: General Help | Current Configuration DynamicAddressBmcDhcp +|F8: Previous Values | Station IP address 192.168.1.12 +|F9: Optimized Defaults | |ESC: Exit | ``` Version 2.22.1289 Copyright (C) 2024 AMI Aptio Setup - AMI Server Mgmt <table>--BMC network configuration--^|Select to configure LAN ^|****************|channel parameters *|Configure IPv4 support*|statically or *|****************|dynamically(by BIOS or *|+|BMC). Unspecified *|Lan channel 1+|option will not modify *|Configuration Address[Static]+|any BMC network +|Station IP address188.188.1.2+|parameters during BIOS v|Subnet mask255.255.255.0+|Station MAC address00-30-64-66-77-88+|----|Router IP address188.188.1.1+|><: Select Screen |Router MAC address00-00-00-00-00-00+|^v: Select Item |+|Enter: Select |Lan channel 2+|+/-: Change Opt. |Configuration Address[Unspecified]+|F1: General Help |Current ConfigurationDynamicAddressBmcDhcp+|F8: Previous Values |Station IP address192.168.1.12+|F9: Optimized Defaults |Subnet mask255.255.255.0v|F10: Save & Exit ||ESC: Exit | Version 2.22.1289 Copyright (C) 2024 AMI
BIOS ItemOptionsDescription
Configuration Address sourceStaticDynamicBmcDhcpSet the IP address source
Station IP addressx.x.x.xSet the IP address
Subnet maskx.x.x.xSet the netmask
Router IP addressx.x.x.xSet the default gateway IP address
Router MAC addressxx:xx:xx:xx:xx:xxSet the default gateway MAC address
# 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:
Main Advanced Platform Configuration Socket Configuration Server Mgmt >
BIOS Information|Set the Date|
BIOS VendorAmerican Megatrends|switch betwe|
BIOS Version1.2.10|Default Rang|
Build Date01/24/2024|Year: 1998-9|
RC Version370.P03|Months: 1-12|
SPS FW Version6.1.2.48|Days: Depend|
|Range of Yea|
System Information
Project NameMECS-7120
CPU Board Version/---- Save & Exit ----\
CPU Brand String
| Quit without saving? |
CPU Frequency
Total Memory|<<: Select S
Memory FrequencyYes No ||^v: Select I
PCH SKU|Enter: Selec|
+/-: Change
System Date[Fri 01/26/2024]|F1: General
System Time[03:01:19]|F8: Previous|
|F9: Optimize|
Access LevelAdministrator|F10: Save &
|ESC: Exit|
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:
Command ElementDescription
ipmitool sol deactivateClose SOL functionality
ipmitool sol infoShow SOL detailed information
ipmitool sol set <set-in-progress | enabled | force-encryption | force-authentication | privilege-level | character-accumulate-level | character-send-threshold | retry-count | retry-interval | non-volatile-bit-rate | volatile-bit-rate> <value>Set SOL parameter value
ipmitool sol payloadSet SOL payload value
ipmitool sol looptestSOL connection stress test
# BMC Information To get the BMC information via ipmitool please refer to the following command: ```txt 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 : 0x64 0x00 0x00 0x00 ``` The full BMC version number is composed of the “Firmware Revision” and the “Aux Firmware Rev Info”. The Firmware Revision contains the major and minor version numbers. The Aux Firmware Rev Info contains the auxiliary version number, which is in little-endian format. The full version number in the example above is as follows: Major: 1 Minor: 3 Aux: 0x00000064 (hex) -> 100 (decimal) # CPLD Update ```txt ipmitool -z 0x3fff hpm upgrade <hpm file> component 5 force ``` Note: If a CPLD firmware has been uploaded, it will print "Firmware upgrade procedure failed". # Example: ```batch 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 ``` ```txt Setting large buffer to 16383 ``` ```txt PICMG HPM.1 Upgrade Agent 1.0.9: ``` ```txt Validating firmware image integrity...OK ``` ```txt Performing preparation stage... ``` ```txt Services may be affected during upgrade. Do you wish to continue? (y/n): y OK ``` ```txt Performing upgrade stage: ```
| ID | Name |Versions| % |
| |ActiveBackup| File|
|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|--|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| --|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| ----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|-----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|--------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|****|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|mm|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| |----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| | * 5 | CPLD | 0.00 00000000 | ---.-- ---- | 2.04 00002002 | 100% | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Upload Time: 00:00 | Image Size: 454924 bytes | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
```ocaml (*) Component requires Payload Cold Reset ``` ```txt Firmware upgrade procedure successful ``` # 8.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. # Network Configuration # GET - Ethernet Interface Collection # Request: ```txt GET https://{bmc ip}/redfish/v1/Managers/Self/EthernetInterfaces ``` # Response: The response status is 200 OK. # Example: GET ![The image shows a narrow vertical section featuring a grey, downward-pointing chevron arrow centered horizontally. The arrow is situated within a white vertical band, flanked on either side by thin, darker vertical lines.](.axe-7420gwa-50m-22811-1000-02/84d9a9d202d107582492d29b7eaad556c36e211a46c4c9ea59d0c0a5e3c8b9ac.jpg) ```txt https://172.20.2.12/redfish/v1/Managers/Self/EthernetInterfaces ``` ```jsonl { "@odata.context": "/redfish/v1/$metadata#EthernetInterfaceCollection.EthernetInterfaceCollection", "@odata.etag": "\"1705564980 Main", "@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" } ``` # 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:
NameTypeRead OnlyDescription
AutoNegBoolean×Auto negotiation of speed and duplex on this interface is enabled or not.
DHCPv4Object×Refer to DHCPv4 properties.
DHCPv6Object×Refer to DHCPv6 properties.
DescriptionString√
FullDuplexBoolean×The value of this property shall represent the duplex status of the Ethernet connection on this interface.
HostNameString×DNS Hostname without any domain information.Maximum string size limit is 64.Minimum string size limit is 2.
IPv4AddressesArray of Objects√Refer to IPv4 Address properties.
IPv4StaticAddressesArray of Objects×Refer to IPv4 Address properties.
IPv6AddressesArray of Objects√Refer to IPv6 Address properties.
IPv6StaticAddressesArray of Objects×Refer to IPv6 Address properties.
IPv6DefaultGatewayString√
IdString√
InterfaceEnabledBoolean×
LinkStatusString√
MACAddressString√
MTUSizeNumber×Maximum size limit is 1500.Minimum size limit is 576.
MaxIPv6StaticAddressesNumber√
NameString√
NameServersArray of Strings√
OemObject√
PermanentMACAddressString√
SpeedMbpsNumber×The current link speed of the interface in Mbps.
StatelessAddressAutoConfigObject×This object shall contain the IPv4 and IPv6 Stateless Address Automatic Configuration (SLAAC) properties for this interface.
StaticNameServersArray of Strings×Statically-defined set of DNS server IPv4 and IPv6 addresses.
StatusObject√
VLANObject×VLANId: 0~4094.
DHCPv4 properties:
NameTypeRead OnlyDescription
DHCPEnabledBoolean×Determines whether DHCPv4 is enabled on this interface.
DHCPv6 properties:
NameTypeRead OnlyDescription
OperatingModeBoolean×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.
IPv4 Address properties:
NameTypeRead OnlyDescription
AddressString-IPv4 address.
AddressOriginString-IPv4 address source.
GatewayString-IPv4 default gateway IP address.
SubnetMaskString-IPv4 netmask.
IPv6 Address properties:
NameTypeRead OnlyDescription
AddressString-IPv6 address.
AddressOriginString-IPv6 address source.
PrefixLengthString-IPv6 network prefix length in bits. Max is 128.
# Example: GET ![The image displays a highly pixelated and blurry vertical section of a graphic, likely a user interface icon. Against a white background, there are dark gray shapes. The most prominent feature is a downward-pointing chevron or arrow at the bottom. A second, indistinct dark shape is visible directly above it. There is no text visible in the image.](.axe-7420gwa-50m-22811-1000-02/2ba31656cd3385a4bd086c7abfe0acdbc51fa3a8ac406681481c528d84a23d28.jpg) https://172.20.2.12/redfish/v1/Managers/Self/Ethernetlnterfaces/eth1 ```jsonl { "@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", "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, ``` ```txt "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 } ``` # 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-7420gwa-50m-22811-1000-02/b9efbe286799a3eb309e503b47f86d124cf42e7429663529c34606df3ead72d9.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. ```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 EthernetInterface Action", "Id": "1", "Name": "EthernetInterface Action", "TaskMonitor": "/redfish/v1/TaskService/TaskMonitors/1", "TaskState": "New" } ``` # BIOS Configuration # GET - HostInterface Instance # Request: ```txt GET https://{bmc ip}/redfish/v1/Managers/Self/HostInterfaces/Self ``` # Response: The response status is 200 OK. # Example: GET ![The image is a low-resolution, cropped section featuring three vertical black lines. To the right of these lines is a blurry, V-shaped or chevron-like graphic element. The background is white, and there is no legible text visible.](.axe-7420gwa-50m-22811-1000-02/6ec2415707789f356eba605ba00e17eb4013c91eb3acf7afac8caeb976fa0dd6.jpg) ```txt https://172.20.2.12/redfish/v1/Managers/Self/HostInterfaces/Self ``` ```javascript "@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", ``` ```txt "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" }, "Name": "Host Interface", "NetworkProtocol": { "@odata.id": "/redfish/v1/Managers/Self/NetworkProtocol" }, "Status": { "Health": "OK", "State": "Enabled" } } ``` # GET – BIOS and BIOS/SD # 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 ``` # Response: The response status is 200 OK. # Example: GET ![The image displays three identical grey, downward-pointing chevron icons arranged in a vertical column against a white background.](.axe-7420gwa-50m-22811-1000-02/b06e4b7960b93d3e0870053c2612c0b15a1161b101282afda1f3d29696f2e75d.jpg) https://172.20.2.12/redfish/v1/Systems/Self/Bios { ```javascript "@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", "Attributes": { "ACPI004": false, "CRCS005": "CRCS005Enable", "FBO001": "FBO001UEFI", ``` ```json "FBO101": "FBO101HardDisk", "FBO102": "FBO102NVME", ... }, "Description": "Current BIOS Settings", "Id": "Bios", "Name": "Current BIOS Settings", "ResetBiosToDefaultsPending": false } ``` # 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 Headers (9) Body Pre-request Script Tests Settings\nnone form-data x-www-form-urlencoded raw binary JSON\n1\n2](.axe-7420gwa-50m-22811-1000-02/e232fbf3d725c86de1616cd09373ec05c121bb8217bc38bbec5419d32d4de6f0.jpg) # 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. ![POST\nhttps://172.20.2.137/redfish/v1/Systems/Self/Bios/Actions/Bios.ChangePassword\nParams Authorization \nHeaders (9) Body \nPre-request Script Tests Settings\nnone form-data x-www-form-urlencoded raw binary JSON](.axe-7420gwa-50m-22811-1000-02/70f0a2bf0d85ca549aea78780bb0d8c26a8d50f28ccb36731bcf22f94d9e1a00.jpg) ```json { "PasswordName": "SETUP001", "OldPassword": "old", "NewPassword": "new" } ``` # PATCH – BIOS SD Change the values of the attributes. # Request: ```txt PATCH https://{bmc ip}/redfish/v1/Systems/Self/Bios/SD ``` # Response: The response status is 204 No Content. Refer to PATCH - BIOS Watchdog Configuration. # 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 two identical grey downward-pointing chevrons arranged horizontally on a white background.](.axe-7420gwa-50m-22811-1000-02/ff52048070acf862734399cc5e9beb58b0be88a5e40c350753082734d2bcbadd.jpg) ```txt https://172.20.2.36/redfish/v1/Chassis/Self/Sensors/1 ``` ```javascript "@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", ``` ```javascript "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 }, "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, ``` ```javascript "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, ``` ```txt "SensorResetTime": null, "Status": { "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 ``` ```txt } }, "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. # 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. # 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: ```batch GET https://172.20.2.36/redfish/v1/UpdateService ``` ```jsonl { "@odata.context": "/redfish/v1/$metadata#UpdateService.UpdateService", "@odata.etag": "\"1708925760\ "@odata.id": "/redfish/v1/UpdateService", ``` ```javascript "@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", "FlashPercentage": null, "PreserveConfiguration": { "Authentication": false, "EXTLOG": false, "FRU": false, "IPMI": false, "KVM": false, "NTP": false, "Network": false, "REDFISH": false, "SDR": false, "SEL": false, ``` ```javascript "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" } ``` # 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
ParamsAuthorizationHeaders (8)BodyPre-request ScriptTestsSettings
Headers7 hidden
KeyValue
If-Match"1706750916"
KeyValue
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 } } } } ``` # POST – Firmware Update This section describes how to use redfish to Update BMC 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 in the 'off' position. It features a white circular knob situated on the left side of a grey, pill-shaped track. There is no text.](.axe-7420gwa-50m-22811-1000-02/2b4cb18fc32564044cb63ee0dd6428dc8ec9381f4a2eec3c8d879a9c561452ea.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-7420gwa-50m-22811-1000-02/86065f7534ea77920661130c43cf52a9fa714f5d1c3648fa3650e671dabf82a4.jpg) # Response:
Body Cookies Headers (14) Test Results Status: 202 Accepted
PrettyRawPreviewVisualizeJSON
1
2"@odata.type": "#UpdateService.v1_6_0.UpdateService", "Messages": [
3
4#
5"@odata.type": "#Message.v1_0_8.Message", "Message": "A new task /redfish/v1/TaskService/Tasks/4 was created.", "MessageArgs": [ "/redfish/v1/TaskService/Tasks/4" ], "MessageId": "Task.1.0.New", "Resolution": "None", "Severity": "OK" } ,
9
10
11
12
13
14#
15"@odata.type": "#Message.v1_0_8.Message", "Message": "The action UpdateService.MultipartPush was submitted to do firmware update.", "MessageArgs": [ "UpdateService.MultipartPush"
16
17
18
# Note: The details of UpdateParameters are given in the table below.
Allowed valueDescription
redfish/v1/UpdateService/FirmwareInventory/BMCWhen the system does not support Dual Flash
redfish/v1/UpdateService/FirmwareInventory/BMCImage1For systems with Dual Flash support, to upgrade Image 1
redfish/v1/UpdateService/FirmwareInventory/BMCImage2For systems with Dual Flash support, to upgrade Image 2
# BIOS Update This section specifically explains how to obtain and upgrade BIOS through Redfish. Users can upgrade BIOS through the following commands. # GET - BIOS Update Status # Request: $\mathsf { G E T h t t p s } . / / \qquad | \mathsf { r e d f i s h } / \mathsf { v } 1 / \mathsf { U p d a t e S e r v i c e }$ # Response: The response status is 200 OK.
NameTypeRead OnlyDescription
BIOSFlashEffectStatusString√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.
# Example: # GET ![The image displays a row of four identical, dark gray, downward-pointing chevron symbols arranged horizontally against a white background.](.axe-7420gwa-50m-22811-1000-02/c2b41b5dd538f65d1227493f066a2c4bf8a9781d601c4bfbdf5aa138816bdd57.jpg) https://172.20.2.18/redfish/v1/UpdateService ```javascript "@odata.context": "/redfish/v1/$metadata#UpdateService.UpdateService", "@odata.etag": "\"1708587273 Main "@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", "Oem": { "AMIUpdateService": { "@odata.type": "#AMIUpdateService.v1_0_0.AMIUpdateService", "BIOSFlashEffectStatus": null, "FlashPercentage": null, "PreserveConfiguration": { "Authentication": false, "EXTLOG": false, ``` ```json "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" } ``` # 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 ![A grey, pill-shaped toggle switch with a white circular knob positioned on the left side, indicating an 'off' state.](.axe-7420gwa-50m-22811-1000-02/a60366890fd2858dd2495b82bd78d7b8b94c35509d29f2d22770c60af24d29c3.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 } ```
NameTypeDescription
update_meBooleanOptional. Default value is false. true: update ME. false: skip ME.
update_nvramBooleanOptional. Default value is false. true: update NVRAM. false: skip NVRAM.
effect_poweroffBooleanOptional. Default value is false. true: take effect when powered off. false: take effect immediately.
force_updateBooleanOptional. 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.
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.
POSThttps://172.20.2.18/redfish/v1/UpdateService/upload
Params Authorization Headers (10) Body Pre-request Script Tests Settings Cookies none form-data x-www-form-urlencoded raw binary
KeyValue∞∞Bulk Edit
✓UpdateFileMECS-7120_1210.BIN ×A
✓UpdateParametersparameters.json ×A
✓OemParametersoem_parameters.json ×A
KeyValue
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" } ] } ``` # CPLD Update This section specifically explains how to obtain and upgrade BIOS through Redfish. Users can upgrade BIOS through the following commands. # GET - CPLD Update Status Request: ```txt GET https://{bmc ip}/redfish/v1/UpdateService ``` # Response: The response status is 200 OK.
NameTypeRead OnlyDescription
CPLDFlashEffectStatusString√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.
# Example: GET ![The image displays a vertical white strip containing two identical grey chevrons pointing downwards, stacked one above the other. A thin, dark vertical line runs along the right edge of the strip.](.axe-7420gwa-50m-22811-1000-02/2eb12c4784a906533b92dc7841e1c9bcad67a54e7bb110673822b82b24efe25b.jpg) https://172.20.2.18/redfish/v1/UpdateService ```txt { ... "Oem": { "AMIUpdateService": { "@odata.type": "#AMIUpdateService.v1_0_0.AMIUpdateService", "BIOSFlashEffectStatus": null, "CPLDFlashEffectStatus": null, "FlashPercentage": null, } ``` # 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 simple toggle switch icon against a white background. It features a gray, horizontal, rounded rectangular track containing a white circular knob positioned on the left side, indicating an 'off' state.](.axe-7420gwa-50m-22811-1000-02/eee69dfa795b961e3a1d633f0dfebd366d8cc44b45192d048b14b6677da13099.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 } ```
NameTypeDescription
force_updateBooleanOptional. 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.
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 \nx-www-form-urlencoded \nraw \nbinary\nCookies\nKey\nValue\nooo\nBulk Edit\nUpdateFile\noutputjbc_02b4.hpm ×\nUpdateParameters\nparameters.json ×\nOemParameters\noem_parameters.json ×\nKey\nValue](.axe-7420gwa-50m-22811-1000-02/b809217b96a7309d62800487221c3f43c0fe3fc4084560f18331929308caf8d6.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" } ] } ``` # Power Control This section is dedicated to explaining how to control power through Redfish. # Request: ```txt POST https://{bmc ip}/redfish/v1/Chassis/Self/Actions/Chassis.Reset ``` # Response: The response status is 202 Accepted. # Example: ![POST\nhttps://172.20.2.16/redfish/v1/Chassis/Self/Actions/Chassis.Reset\nParams Authorization Headers (10) Body Pre-request Script Tests Settings\nnone form-data x-www-form-urlencoded raw binary JSON\n{\n'ResetType': 'ForceRestart'\n}](.axe-7420gwa-50m-22811-1000-02/029cf445a0511f385212a740ff997e45d4d1458dd7c8a2861a78ab7c4abc7c28.jpg) 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" } ``` # BMC Firmware Version To get BMC version, use "Managers" class. # Request: ```txt POST https://{bmc ip}/redfish/v1/Managers/Self ``` # Response: The response status is 200 OK. # Example: ![GET\nhttps://192.168.1.1/redfish/v1/Managers/Self\n≡ Docs Params Authorization • Headers (8) Body Scripts Settings\nnone ○ form-data ○ x-www-form-urlencoded ○ raw ○ binary ○ GraphQL](.axe-7420gwa-50m-22811-1000-02/094bffda7f660e3eb29360168278de4cbd802cb8acbcccf0f4a47a18263ecf89.jpg) ![Body Cookies Headers (24) Test Results | 200 OK · 198 ms · 4.34 KB · e.g. Sa\n{ } JSON ▷ Preview Visualize ▼\n62 'FirmwareVersion': '1.02.100',](.axe-7420gwa-50m-22811-1000-02/c8189ab091d83c1cabdd4a754e1e9501e9fb9b68e590babcc851ea8f9de21623.jpg) Member "FirmwareVersion" consists of: BMC version - 1.02.100 # BIOS Version To get BIOS version, use "Systems" class. # Request: ```txt 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-7420gwa-50m-22811-1000-02/db5f079a5ba1362ffebe4b192f4818cbb74a87ceb0a9998e7cbfc0e466c2588b.jpg) Member "BiosVersion" has the value. "1.2.10" - Leading version.Major version.Minor version Please note that minor version of BIOS is always represented in hexadecimal number. # 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 55°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 standard safety symbol consisting of a red equilateral triangle with a white exclamation point in the center. Below the triangle, the text 'WARNING:' is written in black, uppercase letters against a white background.](.axe-7420gwa-50m-22811-1000-02/e9b4837cbb4b113b14f93247cfc108e8070537097713bfe4b1e80a24dadba8ce.jpg) Hazardous moving parts. Keep body parts out of the motion path. ![The image displays a black and white line drawing. It features a large, upward-pointing equilateral triangle outlined in black. Centered inside the triangle is a symbol resembling a fan or propeller, consisting of a central dot with four curved, petal-like blades radiating outward.](.axe-7420gwa-50m-22811-1000-02/7895c81c376edc2ccc24b50109ae4fbbc462d55d9a8a34be657bbf51bc581222.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 socket-outlet; Secure the power cord (do not place any object on/over the power cord); The power cord must be connected to a socket or outlet with a ground connection. • 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. 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 yellow triangular warning sign with a thick black border. Centered inside the triangle is a large black exclamation point. Below the triangle, the text 'CAUTION:' is written in black capital letters.](.axe-7420gwa-50m-22811-1000-02/d80736b4b194eb4aa5b593a12f7f14688b3390e6d22cb021adb07145d89cbaf6.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 shows a yellow triangular warning sign with a black border. Inside the triangle is a large black exclamation point. Below the triangle, the text reads 'CAUTION:' in black capital letters.](.axe-7420gwa-50m-22811-1000-02/435eb3ff2a750a888facf00bad45ad963b047017af24e81b4d39cba01aaa92c1.jpg) Shock hazard! Disconnect all power supply inputs before servicing. ![The image features a yellow triangular warning sign with a black border and a black lightning bolt symbol in the center. Below the sign, the text 'Shock hazard!' appears in black font.](.axe-7420gwa-50m-22811-1000-02/b379721cb8758b58b485f9bb3543b8f041f1b3d77a4c9b7421f6fc03a10d4a18.jpg) ![Multiple power sources](.axe-7420gwa-50m-22811-1000-02/782e3cda5537f8482d7bc1c311f6a90ebc0f1dc8c15297675f1ba83baaf3b3a8.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. This product is intended to be supplied by a certified DC power source providing reinforced/double insulation from AC mains with an output rating of 36V to 72V DC ,20A min., Tma = 55°C. All power connection wiring must be performed by a qualified electrician in accordance with National Electrical Code, ANSI/NFPA 70 and Canadian Electrical Code, Part I, CSA C22.1. The DC power supply should be well-grounded to ensure safe operation. The protective earthing conductor shall be minimum 14 AWG and having green-and-yellow insulation. The ground wire should be installed first (before "+" and "-") and then removed. 16. 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. # 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 55 °C. 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 features a red triangle containing a white exclamation point, positioned above the black text 'WARNING:'.](.axe-7420gwa-50m-22811-1000-02/5cf9a6e85ba622f3074bd525470168fa61b03f2a9d3af1ffe98c954a462801c4.jpg) AVERTISSEMENT Pièces mobiles dangereuses. Gardez les parties du corps hors de la trajectoire. ![The image displays a black and white graphic featuring a large equilateral triangle with a thick black outline. Inside the triangle is a symbol resembling a four-bladed fan or propeller, with curved blades radiating from a small central white circle. The entire graphic is framed by thick black horizontal bars at the very top and bottom of the image.](.axe-7420gwa-50m-22811-1000-02/dd6a08437ab34ec1248aabbcd111e6b896cc1e98b4e2f3b1904266d654e04591.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 shows a yellow triangular warning sign with a thick black border. Inside the triangle is a large black exclamation point. Below the triangle, the word 'CAUTION:' appears in black capital letters.](.axe-7420gwa-50m-22811-1000-02/1b5ea27c7883c2fa92e1bcfdd5179cf794049008dea4424b49e3c5724fe4182d.jpg) mise en garde 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 yellow triangular warning sign containing a black exclamation point. Below the symbol, the text reads 'CAUTION:' in black capital letters, followed by 'mise en garde' in black lowercase letters on the line below.](.axe-7420gwa-50m-22811-1000-02/98cde554a6549f39380d867ee25862f81e99d381894b3c54944d1aadd0872f22.jpg) Risque d'électrocution! Débranchez toutes les entrées d'alimentation avant de procéder à l'entretien. ![The image shows a standard safety warning sign consisting of a yellow equilateral triangle with a thick black border. In the center is a black lightning bolt symbol, indicating a high voltage or electrical hazard.](.axe-7420gwa-50m-22811-1000-02/ae410faa2ca8ea3872520814c462849e117d7f9b8bfeaafafcc5e1876647a51f.jpg) Shock hazard! Risque d'électrocution! ![The image displays a black-and-white schematic symbol. On the far left, there are two vertical parallel lines. Next to them, two horizontal lines extend to the right and enter the left side of a triangle that points to the right. From the right side of the triangle, three horizontal lines emerge, each terminating in a short vertical bar perpendicular to the line. Above these three lines, a long horizontal arrow points to the right.](.axe-7420gwa-50m-22811-1000-02/18df9d1e660e0a67ab1a017b9921611daf373c04b8e696e83da78f8528fd9eb0.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. Ce produit est destiné à être alimenté par une source d'alimentation CC certifiée fournissant une isolation renforcée/double du secteur CA avec une puissance de sortie de -48 V à -60 V CC, 12 A min., Tma = 55°C. Tout le câblage de connexion d'alimentation doit être effectué par un électricien qualifié conformément au Code national de l'électricité, ANSI / NFPA 70 et au Code canadien de l'électricité, Partie I, CSA C22.1. L'alimentation CC doit être bien mise à la terre pour garantir un fonctionnement sûr. Le conducteur de mise à la terre de protection doit être au minimum 14 AWG et avoir une isolation verte et jaune. Le fil de terre doit être installé en premier (avant «+» et «-») puis retiré. # FCC Warning NOTE: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: — Reorient or relocate the receiving antenna. — Increase the separation between the equipment and receiver. — Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. 1 Consult the dealer or an experienced radio/TV technician for assistance. # Getting Service Ask an Expert: https://www.adlinktech.com/en/Askanexpert # ADLINK Technology, Inc. Address: No. 66, Huaya 1st Road, Guishan District Taoyuan City 333, Taiwan Tel: +886-3-216-5088 Fax: +886-3-328-5723 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 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-7420gwa-50m-22811-1000-02/axe-7420gwa-50m-22811-1000-02.pdf)