Intel® Server Debug and Provisioning Tool (Intel® SDP Tool)

19092
7/17/2019

Introduction

The Intel® Server Debug and Provisioning Tool (Intel® SDP Tool) is used to debug and provision Intel® Server Boards and Systems through BMC out-of-band. (1.3 Build 8)

Available Downloads

  • Red Hat Enterprise Linux 6.8*, SUSE Linux Enterprise Server 11 SP4*, Red Hat Enterprise Linux 7.6*, SUSE Linux Enterprise Server 12 SP3*, Red Hat Enterprise Linux 7.3*, SUSE Linux Enterprise Server 15.1*, CentOS 7.3*, CentOS 6.8*, CentOS 7 (1804)*, Red Hat Enterprise Linux 7.5*
  • Size: 100 MB
  • SHA1: 66F85DD5ED00BD267DA70A8A50C030488FE89A40

Detailed Description

Purpose

The Intel® Server Debug and Provisioning Tool (Intel® SDP Tool) is a single-server tool used to debug and provision Intel® Server Boards and Intel® Server Systems remotely through BMC out-of-band network.


Use this utility under Red Hat Enterprise Linux* 6.8, 7.3, 7.5, and 7.6, SuSE Linux Enterprise Server* 11.4, 12.3, 15.1, and CentOS* 6.8, 7.3, and 7.5 to:

  • Update firmware.
  • Deploy user customized scripts.
  • Configure BIOS/BMC settings.
  • Save BIOS/BMC settings to .INI file.
  • Import BIOS/BMC setting from .INI file.
  • Launch KVM window for remote control.
  • Launch Virtual Media by redirecting image/iso file.
  • Execute ipmitool commands.
  • Get/set the power status.
  • Display sensor information.
  • Retrieve the SEL log.
  • Configure/disable BMC LAN IP ipv4/ipv6 address.
  • Set BMC LAN ipv4/ipv6 to DHCP.
  • Get/set LAN Fail Over option.
  • Display the node position in a chassis.
  • Display system/FRU/memory/CPU/power information.
  • Generate BMC debug log.

 

Available documentation 

Refer to the User Guide on how to use the toolkit.

See the release notes for installation instructions, supported hardware, what is new, bug fixes, and known issues.

This download is valid for the product(s) listed below.

Product and Performance Information

1

Intel is in the process of removing non-inclusive language from our current documentation, user interfaces, and code. Please note that retroactive changes are not always possible, and some non-inclusive language may remain in older documentation, user interfaces, and code.