1. Manuals
  2. Brands
  3. Datacom Manuals
  4. Network Hardware
  5. DM-SV01
  6. User manual

Datacom DM-SV01 User Manual

Hide thumbs Also See for DM-SV01:
Table of Contents

Advertisement

Quick Links

Download this manual
DM-SV01 Server
BMC User Manual
Revision 2.1 – Last updated Nov 2022
DATACOM

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the DM-SV01 and is the answer not in the manual?

Questions and answers

Related Manuals for Datacom DM-SV01

Summary of Contents for Datacom DM-SV01

  • Page 1 DM-SV01 Server BMC User Manual Revision 2.1 – Last updated Nov 2022 DATACOM...
  • Page 2 Datacom or its suppliers have been advised of the possibility of such damages. In particular, Datacom shall not have liability for the costs of replacing, repairing or recovering software, data or hardware related to the product or its use.

  • Page 3: Table Of Contents

    2.4.2.2.1 FW image upload 2.4.2.2.2 FW activation 2.4.2.3 Factory Reset - BIOS and BMC 2.4.3 Date and time settings 2.5 Access Menu 2.5.1 LDAP 2.5.1.1 Enabling and configuring the LDAP 2.5.1.2 Role Groups Management DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 4 3.3.5.5 Energy sensor reset 3.3.6 Indicator LED 3.3.6.1 Turn on Indicator LED 3.3.6.2 Turn off Indicator LED 3.3.7 Host Power Actions 3.3.7.1 Power On Host 3.3.7.2 Power Off Host 3.3.7.3 Restart Host DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 5 3.3.13 Logging 3.3.13.1 View Log Entries 3.3.13.2 Delete Log Entries 3.3.14 BMC Reset 3.3.14.1 Reboot BMC 3.3.14.2 Reset BMC to Factory Defaults 4 References 5 Annex A - Frequently Asked Questions DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 6: Introduction

    BMC management and monitoring functionalities. In the DM-SV01, the BMC can be accessed and controlled by a dedicated Ethernet port present in the front panel of the system (out of band management) or by means of the Ethernet port from the mezzanine NIC card, sharing the traffic with the host CPUs (in band management).

  • Page 7: Getting Started

    BMC are configured as DHCP clients. So, the user can connect to the BMC dedicated Ethernet port in the DM-SV01 front panel for an out of band management or to the Mezzanine NIC port 0 for an in band traffic, and activate a DHCP server to send an IP Address to the BMC. Detailed information about the BMC network configuration can be found in section “2.4.1 Network settings”.

  • Page 8: Best Practices For Improving The Bmc Security

    ● Block outgoing BMC traffic to the internet using a firewall. ● Install a proper certificate for HTTP access to the BMC. ● Contact Datacom support team periodically to check for available BMC FW upgrades. 1.4 Redfish The redfish is a RESTful (Representational State Transfer) application programming interface (API) developed by the DMTF (Distributed Management Task Force) and used for a broad range of converged infrastructure (CI) equipment, such as servers, storage devices, network equipment, etc.
  • Page 9 The Refish interface is available in the DM-SV01 server as a remote management tool for accessing and controlling several resources available at the BMC. In the DM-SV01, the redfish API can be used for accessing and controlling a variety of resources of the BMC, such as inventory information, sensors data, host power actions, boot override configuration, users management, logs, FW update, etc.

  • Page 10: Bmc Web Gui

    LED, please refer to the section “2.3.2 Server LED”. 2. Serial over LAN console: redirects the user to the “Serial over LAN console” menu. Details regarding this function can be found in section “2.3.4 Serial over LAN console”. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 11: Health Menu

    The events or alarms triggered in the system are identified by the BMC and logged in the database, allowing the user to check them later by means of the “Event log” menu. An example of an event log from the DM-SV01 server can be seen in Figure 4 and Figure 5. Figure 4: BMC Event log menu...
  • Page 12 Event c. Oem 2. Filter by severity: a. All b. Critical c. Warning d. OK 3. Filter by date. 4. Filter by type, if applicable. Figure 6: BMC Event log filters DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 13: Event Logs Through Server Health Button

    3. The user can mark an event as resolved. When doing this, the event will still be available in the database, but it will not cause any alarm indication in the system. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 14: Remote Logging Server

    Logging Server” option is available, as shown in Figure 10. This option allows the user to configure a remote server to receive the logs from the BMC. Figure 10: Remote Logging Server button DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 15: Hardware Status

    The “Hardware status” menu is used to check the inventory information of the following system components: ● Motherboard ● NVMes ● DIMMs ● Mezzanine card ● CPUs ● Riser Cards ● 2xE1.S Adapter Card DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 16 The data available for each component depends on the component type. In general, the user can access information such as presence, model, part number, serial number, etc. The figure below shows an example of the inventory data for one of the CPUs compatible with the DM-SV01 server. Figure 13: Hardware status menu - CPUs view The NVMe devices are listed in the menu by following a predefined numbered sequence.
  • Page 17 Information about DDR memory installed at socket P0, slot C DIMM 3 Information about DDR memory installed at socket P0, slot D DIMM 4 Information about DDR memory installed at socket P0, slot E DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 18: Sensors

    2.2.3 Sensors The DM-SV01 server has a set of sensors which are responsible for monitoring the voltage, current and temperature at several relevant spots of the system. The sensors information is used for controlling the FANs speed and generating alarms or emergency shutdown in case of reaching a critical threshold.
  • Page 19 The figure below shows the location of the temperature sensors in the DM-SV01 motherboard. Figure 22: DM-SV01 temperature sensors location The table below shows the description of each sensor and its respective alias in the BMC web management interface. Sensor name...
  • Page 20 3, when connected. Table 2: DM-SV01 temperature sensors description Additionally, the DM-SV01 is also capable of monitoring the system input power, the FANs speed and some primary voltages. The table below shows the additional monitoring outputs of the DM-SV01.

  • Page 21: Power Consumption Sensors

    2.2.3.1 Power consumption sensors The DM-SV01 server has some sensors that are capable of monitoring the power consumption of the system. The following power sensors are available: ● Total Energy: this sensor displays the accumulated energy consumed by the DM-SV01 server in “joules”.

  • Page 22: Control Menu

    The procedure to perform a reboot or shutdown is pretty straightforward. The user selects between the options “orderly” or “immediate” by marking the corresponding checkbox and then click on the respective “Reboot” or “Shut down” button. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 23 Figure 19: Server Power Operations menu when the host processors are powered off Figure 20: Server Power Operations menu when the host processors are powered on DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 24: Host Os Boot Settings - Boot Override

    ● The “TPM Required Policy” can be enabled in order to ensure that the system will boot only if the TPM (Trusted Platform Module) is active and functional. Please refer to the “DM-SV01 BIOS Manual” (2) for details regarding the TPM settings and refer to the “DM-SV01 Product Manual”...

  • Page 25: Server Led

    2.3.2 Server LED The “ID LED”, or “Server LED” can be controlled via the ID button in the front panel of the DM-SV01 server and also via the BMC WEB management interface. For details regarding the physical ID button, please refer to the DM-SV01 Product Manual (1).

  • Page 26: Reboot Bmc

    Important: the ID LED can also be physically activated by means of the ID button - details of this functionality can be found at the “DM-SV01 Product Manual” (1). When the ID LED is turned on or off by means of the ID button, the “Server LED light” button in the BMC web GUI will update its status only after the web page is refreshed.

  • Page 27: Serial Over Lan Console

    BIOS/UEFI or OS by means of the keyboard and mouse directly in the web page. This allows full remote access to the server BIOS/UEFI and OS, once the users can perform any operation as if they have direct access to the equipment. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 28 KVM screen will be displayed. This button does not close the current KVM screen being displayed, it just opens a new window in the web browser with another KVM screen. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 29: Virtual Media

    Figure 29: Virtual Media activation procedure When the “.ISO” image is active, the text “Active Session” becomes available in the screen, as shown in the Figure 30. Figure 30: Virtual Media active DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 30: Configuration Menu

    ● eth1: it is the default out-of-band management interface of the BMC. It can be accessed by means of the dedicated Ethernet port present in the front panel of the DM-SV01. For additional information regarding the BMC Ethernet ports and how to connect to them, please refer to the “DM-SV01 Product Manual”...

  • Page 31: Ipv4 Settings

    ● Configure the network interface as a DHCP client to receive the IP address automatically (default option). ● Assign a static IP address to the network interface. The selection is done by means of the checkboxes shown below: DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 32 ● Netmask prefix length: integer number from “1” up to “32”. Figure 34: BMC network settings - configuring static IPv4 entries The operation can be confirmed by clicking on the “Save Settings” button (step 3 in Figure 35). DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 33: Dns Settings

    The image below shows an example of the FW menu section that shows the current FW versions of both BMC and BIOS running on the system. Figure 36: Firmware menu - current FW versions DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 34: Fw Update Process - Bmc Or Bios

    FW image is placed in the respective image field. The Figure 41 shows an example of a BIOS FW image already uploaded and ready for the update. The BIOS FW has two types of image for updating: DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 35 ● Clear BIOS settings image: this image updates the BIOS FW and resets all BIOS settings to the factory default. The changes performed by the user will not be preserved after the update. Please consult the Datacom sales team whenever necessary for checking which type of image is available for the update.

  • Page 36: Fw Activation

    Figure 41: BIOS FW activation The Figure 42 shows an example of FW update, where a BMC image has been successfully uploaded and is ready to be activated. Figure 42: BMC FW activation DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 37 ● Activate Firmware File and Automatically Reboot BMC (recommended): the FW image will be updated and the BMC will be rebooted automatically. When this option is selected, any BMC FW change will take effect immediately after the automatic reboot is performed. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 38: Factory Reset - Bios And Bmc

    Please note that some settings may require a host reset or power cycle to be applied. Additional details can be found in the DM-SV01 BIOS User Manual (2). ● BMC Factory Reset: this option resets all BMC settings to the factory default.

  • Page 39: Date And Time Settings

    ○ 2) Click on “Add new NTP server”. ○ 3) Fill in the text box with the NTP server IP address, in the format “111.111.111.111”. ○ 4) Click on the “Save settings” button below. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 40 Note: The owner option is only available in previous releases of BMC SW. ○ 4) Click on the “Save settings” button below. Figure 47: Date and Time configuration - configuring manually DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 41: Access Menu

    ● Secure LDAP using SSL: enables or disables the secure LDAP. In order to be able to enable the secure LDAP, the user must first create a certificate. The procedure to do so is described in the section “2.5.3 SSL certificates”. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 42: Role Groups Management

    ○ NoAccess It is possible to check the actions allowed for each privilege level in the “Local Users” menu. Please refer to the section “2.5.2 Local users” for additional information about this. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 43: Instructions For Implementing The Ldap Server

    There are some recommendations that must be followed when implementing an LDAP server using OpenLDAP or Active Directory, in order to guarantee that the authentication will be performed successfully with the BMC: DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 44: Local Users

    The Figure 52 shows the main screen of the menu. Figure 52: Local users menu 2.5.2.1 Account policy settings The “Account policy settings” button is used to configure some basic settings related to security, as shown in the Figure 53. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 45 Figure 54. ○ Manual: when this option is selected, the user is completely blocked whenever the maximum number of login attempts is exceeded. Figure 54: Account policy settings menu DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 46 Administrator account, clicking on the pencil icon to modify the locked user and then clicking on the “Unlock” button, as shown in the Figure 56. Figure 55: Edit User option Figure 56: Unlock User button DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 47: Managing Users

    ○ Operator ○ ReadOnly ○ NoAccess In order to add a new user, the system administrator must configure the settings mentioned above and then click on the “Add user” button below. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 48 It is possible to check the actions allowed for each privilege level in the “Local Users” menu main page, by clicking on the “Hide privilege role descriptions” button, as shown in the Figure 59. Figure 59: User privilege roles description DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 49 In order to delete an user, just click on the “trash” symbol related to the user you would like to delete, as shown in the Figure 61. Figure 61: Delete User DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 50: Ssl Certificates

    Signing Request). 2.5.3.1 Adding or replacing a certificate In order to add a new certificate, the user must click on the “Add new certificate” button, as shown in the Figure 63. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 51 The user can also replace an already loaded certificate. This can be done by clicking on the replace icon shown in the Figure 65, then clicking on the “Choose file” button to browse the new certificate file and finally confirming the operation by clicking on the “Replace” button. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 52: Csr Generation

    HTTPS certificate or LDAP certificate. The LDAP certificate can be used to configure the secure LDAP, as described in the section “2.5.1.1 Enabling and configuring the LDAP”. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 53 There are also two types of private key algorithms for selection: EC or RSA, available for selection in the right corner of the window. Figure 68: CSR - Key algorithm selection DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 54 ● If RSA is set, the user is prompted to select the “Key Bit Length”. The only option available in this case is “2048”. Figure 69: CSR - EC key curve ID configuration Figure 70: CSR - RSA key bit length configuration DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 55 After selecting the certificate type and private key algorithm, the user must fill out the form manually and then click on “Generate CSR” to confirm the operation. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 56: Redfish Api

    URL below: ● https://<BMC_IP>/redfish/v1 After accessing the link above, the user is able to navigate throughout the links of the DM-SV01 redfish interface in the web browser and access the resources available at the BMC, such as sensors, system inventory data, etc.

  • Page 57: Informational Status Codes

    Already Reported 209-225 Unassigned IM Used 227-299 Unassigned Table 6: HTTP Successful status codes 3.2.3 Redirection Status Codes Code Description Multiple Choices Moved Permanently Found See Other Not Modified Use Proxy DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 58: Client Error Status Codes

    Content Too Large URI Too Long Unsupported Media Type Range Not Satisfiable Expectation Failed (Unused) 419-420 Unassigned Misdirected Request Unprocessable Content Locked Failed Dependency Too Early Upgrade Required Unassigned Precondition Required DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 59: Server Error Status Codes

    The table below lists all the requests available in the BMC. Every request has a specific section explaining its functionality and an example of how to perform the operation. Function Method Section BMC Login POST 3.3.1 Session Login BMC Logout DELETE 3.3.3 Session Logout DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 60 Configure Open LDAP PATCH 3.3.10.1 Open LDAP Configure LDAP - Active Directory PATCH 3.3.10.2 Active Directory Configure LDAP - Role Groups PATCH 3.3.10.3 Role Groups Change root password PATCH 3.3.11.1 Change root password DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 61: Session Login

    Once the operation is successful, it returns the response “201 Created”. The session location is then created with a corresponding ID and an X-Auth-Token is generated. Important: The X-Auth-Token is used in the header of further redfish requests as an authorization ID. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 62: Using The X-Auth-Token

    Figure 72. When using Postman, the token is available in the “Headers” tab of the request response workspace. Figure 72: BMC session authentication token DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 63: Session Logout

    In the URI, it is required to add the session ID to be deleted. As an example, the session created in section “3.3.1 Session Login” could be deleted by using the URI below: ● https://<BMC_IP>/redfish/v1/SessionService/Sessions/jl9y8Zjudl. Function BMC Logout Operation DELETE https://<BMC_IP>/redfish/v1/SessionService/Sessions/<session_ID> Payload None X-Auth-Token: “<token>” Header Expected 200 OK response DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 64: System Inventory

    The “System Inventory” section describes the resources used to retrieve information about several system components, such as motherboard, CPUs, memories, storage devices, etc. 3.3.4.1 Mainboard Inventory Using a GET request, it is possible to retrieve inventory information from the DM-SV01 mainboard. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 65 Reply Please, see the example below. As an example, the excerpt below shows the data provided by the DM-SV01 motherboard using the redfish GET request. The user can check relevant information such as indicator LED status, part number, serial number, power state, system health status, etc.
  • Page 66 "HealthRollup": "OK", "State": "StandbyOffline" "Thermal": { "@odata.id": "/redfish/v1/Chassis/motherboard/Thermal" Once the operation is successful, it returns the response “200 OK” and the inventory information is retrieved. Figure 75: Redfish - Motherboard inventory DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 67: Processors Inventory

    Reply Please, see the example below. As an example, the excerpt below shows the data provided by the DM-SV01 motherboard using the redfish GET request, where the user can check the CPU count. Additionally, the user can view the list of “Members”, which are the available CPUs in the system that can be accessed to retrieve more...

  • Page 68: Detailed Inventory About A Specific Processor

    Using a GET request, it is possible to retrieve detailed inventory information from a specific CPU of the DM-SV01 server. The user can check which CPUs are available for requesting the inventory by using the procedure described in section “3.3.4.2”. Anyway, the CPUs available by default are “cpu0” and “cpu1”...
  • Page 69 Once the operation is successful, it returns the response “200 OK” and the inventory information is retrieved. If the CPU is not present in the system, the field "State” is shown as “Absent” and no inventory information is retrieved. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 70: Memory Modules Inventory

    Figure 77: Redfish - Specific CPU detailed Inventory 3.3.4.4 Memory modules inventory Using a GET request, it is possible to retrieve inventory information from the DM-SV01 DDR memory modules. Function Inventory - DDR memories Operation https://<BMC_IP>/redfish/v1/Systems/system/Memory Payload none X-Auth-Token: “<token>”...
  • Page 71 "@odata.id": "/redfish/v1/Systems/system/Memory/", "@odata.type": "#MemoryCollection.MemoryCollection", "Members": [ "@odata.id": "/redfish/v1/Systems/system/Memory/dimm0" "@odata.id": "/redfish/v1/Systems/system/Memory/dimm1" "@odata.id": "/redfish/v1/Systems/system/Memory/dimm10" "@odata.id": "/redfish/v1/Systems/system/Memory/dimm11" "@odata.id": "/redfish/v1/Systems/system/Memory/dimm12" "@odata.id": "/redfish/v1/Systems/system/Memory/dimm13" "@odata.id": "/redfish/v1/Systems/system/Memory/dimm14" "@odata.id": "/redfish/v1/Systems/system/Memory/dimm15" "@odata.id": "/redfish/v1/Systems/system/Memory/dimm2" "@odata.id": "/redfish/v1/Systems/system/Memory/dimm3" "@odata.id": "/redfish/v1/Systems/system/Memory/dimm4" "@odata.id": "/redfish/v1/Systems/system/Memory/dimm5" DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 72 "@odata.id": "/redfish/v1/Systems/system/Memory/dimm9" "Members@odata.count": 16, "Name": "Memory Module Collection" Once the operation is successful, it returns the response “200 OK” and the inventory information is retrieved. Figure 78: Redfish - Memories inventory DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 73: Detailed Inventory Information About Specific Memory Module

    Using a GET request, it is possible to retrieve detailed inventory information from a specific DDR memory device installed in the DM-SV01 server. The user can check which memories are available for requesting the inventory by using the procedure described in section “3.3.4.4 Memory modules inventory”.

  • Page 74: Storage Inventory

    If the memory is not present in the system, the field "State” is shown as “Absent” and no inventory information is retrieved. Figure 79: Redfish - Specific memory detailed Inventory 3.3.4.6 Storage inventory Using a GET request, it is possible to retrieve inventory information from the DM-SV01 storage devices. Function Inventory - storage devices Operation https://<BMC_IP>/redfish/v1/Systems/system/1/...
  • Page 75 "@odata.id": "/redfish/v1/Systems/system/Storage/1", "@odata.type": "#Storage.v1_7_1.Storage", "Drives": [ "@odata.id": "/redfish/v1/Systems/system/Storage/1/Drives/nvme0" "@odata.id": "/redfish/v1/Systems/system/Storage/1/Drives/nvme1" "@odata.id": "/redfish/v1/Systems/system/Storage/1/Drives/nvme10" "@odata.id": "/redfish/v1/Systems/system/Storage/1/Drives/nvme2" "@odata.id": "/redfish/v1/Systems/system/Storage/1/Drives/nvme3" "@odata.id": "/redfish/v1/Systems/system/Storage/1/Drives/nvme4" "@odata.id": "/redfish/v1/Systems/system/Storage/1/Drives/nvme5" "@odata.id": "/redfish/v1/Systems/system/Storage/1/Drives/nvme6" "@odata.id": "/redfish/v1/Systems/system/Storage/1/Drives/nvme7" "@odata.id": "/redfish/v1/Systems/system/Storage/1/Drives/nvme8" "@odata.id": "/redfish/v1/Systems/system/Storage/1/Drives/nvme9" "Drives@odata.count": 11, DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 76: Detailed Inventory About A Specific Storage Device

    Using a GET request, it is possible to retrieve detailed inventory information from a specific storage device of the DM-SV01 server. The user can check which storage devices are available for requesting the inventory by using the procedure described in section “3.3.4.6 Storage inventory”. Anyway, the storage devices available by default are “nvme0”...
  • Page 77 Once the operation is successful, it returns the response “200 OK” and the inventory information is retrieved. If the storage device is not present in the system, the field "State” is shown as “Disabled” and no inventory information is retrieved. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 78: Sensors

    Figure 81: Redfish - Specific storage device detailed Inventory 3.3.5 Sensors The power and temperature sensors available in the DM-SV01 server can be read by means of the redfish interface. Details regarding the functionality of the DM-SV01 sensors can be found in section “2.2.3 Sensors”.
  • Page 79 As an example, the excerpt below shows the data provided by the DM-SV01 motherboard using the redfish GET request. The user can check power and voltage measurements from all the power sensors available in the server. "@odata.id": "/redfish/v1/Chassis/chassis/Power", "@odata.type": "#Power.v1_5_2.Power", "Id": "Power",...
  • Page 80 "LowerThresholdCritical": 2.97, "LowerThresholdNonCritical": 3.1350000000000002, "MaxReadingRange": 0.0, "MemberId": "VDD_33_DUAL", "MinReadingRange": 0.0, "Name": "VDD 33 DUAL", "ReadingVolts": 3.399, "Status": { "Health": "OK", "State": "Enabled" "UpperThresholdCritical": 3.63, "UpperThresholdNonCritical": 3.465 "@odata.id": "/redfish/v1/Chassis/chassis/Power#/Voltages/3", "@odata.type": "#Power.v1_0_0.Voltage", "LowerThresholdCritical": 2.97, DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 81 "Name": "VDD 5 DUAL", "ReadingVolts": 5.204, "Status": { "Health": "OK", "State": "Enabled" "UpperThresholdCritical": 5.5, "UpperThresholdNonCritical": 5.25 Once the operation is successful, it returns the response “200 OK” and the sensors information is retrieved. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 82: Temperature Sensors

    Reply Please, see the example below. As an example, the excerpt below shows the data provided by the DM-SV01 motherboard using the redfish GET request. The user can check the measurements from all the temperature sensors available in the server.
  • Page 83 "Name": "Thermal", "Redundancy": [], "Temperatures": [ [...] "@odata.id": "/redfish/v1/Chassis/chassis/Thermal#/Temperatures/2", "@odata.type": "#Thermal.v1_3_0.Temperature", "LowerThresholdCritical": 0.0, "LowerThresholdNonCritical": 5.0, "MaxReadingRangeTemp": 0.0, "MemberId": "INLET", "MinReadingRangeTemp": 0.0, "Name": "INLET", "ReadingCelsius": 25.313, "Status": { "Health": "OK", "State": "Enabled" DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 84: Power Consumption Sensors

    Using a GET request, it is possible to retrieve the instantaneous total current being consumed by the DM-SV01 server. Function System Total Current Consumption Operation https://<BMC_IP>/redfish/v1/Chassis/chassis/Sensors/POWER_SUPPLY Payload none X-Auth-Token: “<token>” Header DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 85 "Reading": 0.0 "LowerCritical": { "Reading": 0.0 "UpperCaution": { "Reading": 61.0 "UpperCritical": { "Reading": 65.0 Once the operation is successful, it returns the response “200 OK” and the sensor information is retrieved. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 86: Power Consumption

    “Reading” field. The measurement unit (Watts) is shown in the “ReadingUnits” field. Additionally, the user can check the health status of the sensor and the respective warning and critical thresholds. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 87 "Reading": 0.0 "LowerCritical": { "Reading": 0.0 "UpperCaution": { "Reading": 732.0 "UpperCritical": { "Reading": 780.0 Once the operation is successful, it returns the response “200 OK” and the sensor information is retrieved. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 88: Peak Power

    Figure 85: Redfish - Power consumption 3.3.5.3.3 Peak Power Using a GET request, it is possible to retrieve the peak power consumed by the DM-SV01 server. Function System Peak Power Operation https://<BMC_IP>/redfish/v1/Chassis/chassis/Sensors/PEAK_POWER Payload none X-Auth-Token: “<token>” Header Expected 200 OK...
  • Page 89 "Reading": 0.0 "LowerCritical": { "Reading": 0.0 "UpperCaution": { "Reading": 732.0 "UpperCritical": { "Reading": 780.0 Once the operation is successful, it returns the response “200 OK” and the sensor information is retrieved. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 90: Peak Power Sensor Reset

    Using a POST request, it is possible to reset the Peak Power Sensor. Function Reset Peak Power sensor Operation POST https://<BMC_IP>/redfish/v1/Managers/bmc/Oem/Datacom/Actions/Manager.Re setPeakPowerSensor Payload "ResetToDefaultsType": "ResetAll" X-Auth-Token: “<token>” Header Expected 200 OK response DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 91 Important: if the “Peak Power” sensor is not available in the BMC, please update the BMC SW by following the procedure described in section 2.4.2.2 FW update process - BMC or BIOS. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 92: Energy Sensor Reset

    "@odata.type": "#Message.v1_0_0.Message", "Message": "Successfully Completed Request", "MessageArgs": [], "MessageId": "Base.1.4.0.Success", "Resolution": "None", "Severity": "OK" Once the operation is successful, it returns the response “200 OK” and the energy sensor reset is performed. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 93: Indicator Led

    Using a PATCH request, it is possible to turn the LED indicator on. Function Turn on Server Indicator LED Operation PATCH https://<BMC_IP>/redfish/v1/Systems/system Payload "IndicatorLED": "Lit" X-Auth-Token: “<token>” Header Expected 204 No Content response DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 94: Turn Off Indicator Led

    Payload "IndicatorLED": "Off" X-Auth-Token: “<token>” Header Expected 204 No Content response Reply None Once the operation is successful, it returns the response “204 No Content” and the LED is deactivated. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 95: Host Power Actions

    3.3.7.1 Power On Host Using a POST request, it is possible to power the host processors on. Function Host power on Operation POST https://<BMC_IP>/redfish/v1/Systems/system/Actions/ComputerSystem.Reset Payload "ResetType": "On" X-Auth-Token: “<token>” Header Expected 200 OK response DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 96: Power Off Host

    Once the operation is successful, it returns the response “200 OK” and the host processors are powered Figure 91: Redfish - Host power on 3.3.7.2 Power Off Host Using a POST request, it is possible to turn the host processors off. Function Host power off Operation POST DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 97 "MessageId": "Base.1.4.0.Success", "Resolution": "None", "Severity": "OK" Once the operation is successful, it returns the response “200 OK” and the host processors are powered off. Figure 92: Redfish - Host power off DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 98: Restart Host

    "@odata.type": "#Message.v1_0_0.Message", "Message": "Successfully Completed Request", "MessageArgs": [], "MessageId": "Base.1.4.0.Success", "Resolution": "None", "Severity": "OK" Once the operation is successful, it returns the response “200 OK” and the host processors are restarted. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 99: Force Power Off Host

    Using a POST request, it is possible to forcibly turn the host processors off. Function Host forced power off Operation POST https://<BMC_IP>/redfish/v1/Systems/system/Actions/ComputerSystem.Reset Payload "ResetType": "ForceOff" X-Auth-Token: “<token>” Header Expected 200 OK response DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 100: Force Restart Host

    Once the operation is successful, it returns the response “200 OK” and the host processors are forcibly powered off. Figure 94: Redfish - Host force power off 3.3.7.5 Force Restart Host Using a POST request, it is possible to forcibly restart the host processors. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 101 "MessageId": "Base.1.4.0.Success", "Resolution": "None", "Severity": "OK" Once the operation is successful, it returns the response “200 OK” and the host processors are forcibly restarted. Figure 95: Redfish - Host force restart DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 102: Network Settings

    ● “eth1”: it is the default out-of-band management interface of the BMC. It can be accessed by means of the dedicated Ethernet port present in the front panel of the DM-SV01. The configuration parameters are inserted in the payload of the request, as shown in the example from the table below.

  • Page 103: Boot Override Options

    Header Expected 204 No Content response Reply None Once the operation is successful, it returns the response “204 No Content” and the host system will boot by means of the PXE. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 104: Force Cd-Rom/Virtual Media Boot Override

    204 No Content response Reply None Once the operation is successful, it returns the response “204 No Content” and the host system will boot by means of the CD or virtual media. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 105: Force Bios Setup Boot Override

    X-Auth-Token: “<token>” Header Expected 204 No Content response Reply None Once the operation is successful, it returns the response “204 No Content” and the host system will boot the BIOS/UEFI setup screen. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 106: Force Usb Boot Override

    Header Expected 204 No Content response Reply None Once the operation is successful, it returns the response “204 No Content” and the host system will boot by means of the USB. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 107: Force Hdd Boot Override

    Header Expected 204 No Content response Reply None Once the operation is successful, it returns the response “204 No Content” and the host system will boot by means of the HDD. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 108: Disable Boot Override

    Once the operation is successful, it returns the response “204 No Content” and the next boot of the host system will be performed using the boot sequence configured in the BIOS menu, without any overriding. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 109: Ldap Configuration

    ● UsernameAttribute (User ID Attribute - optional): additional user ID attribute (CN), if applicable. ● GroupsAttribute (Group ID Attribute - optional): additional group ID attribute (GID), if applicable. Function Configure Open LDAP Operation PATCH https://<BMC_IP>/redfish/v1/AccountService DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 110 Same as payload Once the operation is successful, it returns the response “200 OK” and the LDAP is configured according to the data sent inside the payload of the request operation. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 111: Active Directory

    ● UsernameAttribute (User ID Attribute - optional): additional user ID attribute (CN), if applicable. ● GroupsAttribute (Group ID Attribute - optional): additional group ID attribute (GID), if applicable. Function Configure LDAP - Active Directory Operation PATCH DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 112 Same as payload Once the operation is successful, it returns the response “200 OK” and the Active Directory is configured according to the data sent inside the payload of the request operation. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 113: Role Groups

    ● LocalRole (Privilege): the privilege level for the group of users. There are four options available: ○ Administrator ○ Operator ○ ReadOnly ○ NoAccess Function Configure LDAP - Role Groups Operation PATCH https://<BMC_IP>/redfish/v1/AccountService DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 114 Figure 105: Redfish - Configuring Role Groups Important: If the user desires to delete all the role groups, it is possible to send a “null” value in the payload, inside the “RemoteRoleMapping” resource, as shown below: DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 115: Users Management

    Reply None Once the operation is successful, it returns the response “200 OK” and the password is changed according to the new string sent inside the payload of the request operation. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 116: Add Bmc User

    ○ “Administrator” ○ “Operator” ○ “ReadOnly” ○ “NoAccess” Function Add new BMC user Operation POST https://<BMC_IP>/redfish/v1/AccountService/Accounts Payload "UserName": "<username>", "Password" : "<password>", "RoleId" : "<privilege>" X-Auth-Token: “<token>” Header Expected 201 Created response DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 117 Once the operation is successful, it returns the response “201 Created” and the user is created according to the specifications sent inside the payload of the request. Figure 107: Redfish - Adding a new BMC user DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 118: Change Bmc User Role

    "Resolution": "None", "Severity": "OK" Once the operation is successful, it returns the response “200 OK” and the user role is changed according to the string sent inside the payload of the request. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 119: Change Bmc User Password

    Therefore, very simple sequences of characters will not be accepted. Function Change BMC user password Operation PATCH https://<BMC_IP>/redfish/v1/AccountService/Accounts/<username> Payload “Password”:”<new password>” X-Auth-Token: “<token>” Header Expected 200 OK response Reply None DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 120: Delete Bmc User

    Using a DELETE request, it is possible to delete an user. The username is placed in the URI of the DELETE request Function Delete BMC user Operation DELETE https://<BMC_IP>/redfish/v1/AccountService/Accounts/<username> Payload None X-Auth-Token: “<token>” Header Expected 200 OK response DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 121: Fw Update

    Figure 110: Redfish - Deleting an user 3.3.12 FW Update The user can update the BMC FW or the BIOS FW by means of the redfish. Details regarding FW update can be found in section “2.4.2.2”. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 122: Update Bmc Firmware

    Important: the POST request uploads the FW image and prepares it for the update. However, the FW will only be updated after a manual reboot of the BMC, which can be performed by following the procedure described in section “3.3.14.1 Reboot BMC”. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 123: Update Bios Firmware

    “binary” option inside the “Body” tab. Function Update BIOS FW Operation POST https://<BMC_IP>/redfish/v1/UpdateService Payload Upload file X-Auth-Token: “<token>” Header Expected 200 OK response Reply "@odata.id": "/redfish/v1/TaskService/Tasks/0", "@odata.type": "#Task.v1_4_3.Task", "Id": "0", "TaskState": "Running", "TaskStatus": "OK" DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 124: Logging

    3.3.13.1 View Log Entries Using a GET request, it is possible to retrieve all the log entries. Function View log entries Operation https://<BMC_IP>/redfish/v1/Systems/system/LogServices/EventLog/Entries Payload None X-Auth-Token: “<token>” Header Expected 200 OK response DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 125 Reply Please, see the example below. As an example, the excerpt below shows the data provided by the DM-SV01 motherboard using the redfish GET request. The user can check relevant information of each event logged in the BMC. "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries", "@odata.type": "#LogEntryCollection.LogEntryCollection",...
  • Page 126 "Severity": "Critical" "Members@odata.count": 4, "Name": "System Event Log Entries" Once the operation is successful, it returns the response “200 OK” and the logs are shown in the body of the request response. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 127: Delete Log Entries

    Important: please be careful because this operation cannot be reverted. Once the logs are deleted, their information is completely lost. Function Clear log entries Operation POST https://<BMC_IP>/redfish/v1/Systems/system/LogServices/EventLog/Actions/Lo gService.ClearLog Payload None X-Auth-Token: “<token>” Header Expected 200 OK response DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 128: Bmc Reset

    BMC reboot can be found in section “2.3.3 Reboot BMC” and information about the BMC reset to factory defaults can be found in section “2.4.2.3 Factory Reset - BIOS and BMC”. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 129: Reboot Bmc

    "@odata.type": "#Message.v1_0_0.Message", "Message": "Successfully Completed Request", "MessageArgs": [], "MessageId": "Base.1.4.0.Success", "Resolution": "None", "Severity": "OK" Once the operation is successful, it returns the response “200 OK” and the BMC is immediately rebooted. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 130: Reset Bmc To Factory Defaults

    None Once the operation is successful, it returns the response “200 OK” and all the BMC settings are reverted back to the factory defaults, including network settings, users, root password, etc. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...
  • Page 131 Figure 116: Redfish - BMC factory reset DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 132: References

    “DM-SV01 - BIOS User Manual”. RFC 9110 - HTTP Semantics, available at “https://www.rfc-editor.org/rfc/rfc9110.html”. John Leung, Intel. “Introduction and Overview of Redfish”. SNIA, 2017. Available at “https://www.snia.org/educational-library/introduction-and-overview-redfish-2017”. “Redfish”. DMTF. Available at “https://www.dmtf.org/standards/redfish”. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

  • Page 133: Annex A - Frequently Asked Questions

    5 Annex A - Frequently Asked Questions Q: Why is the Firmware update rejected by the BMC? A: Updates are digitally signed by Datacom to ensure integrity. Only correctly signed update packages will be accepted. Furthermore, BMC only supports update and downdate, not redate.
  • Page 134 - Added FAQ section (Annex A) 2022/11/07 Release 2.1 - Added section to clarify some requirements for configuring an LDAP server. - Added section 2.5.1.3 Instructions for implementing the LDAP server. DM-SV01 Server ● BMC User Manual ● Rev. 2.1...

Table of Contents