White Papers
Table Of Contents
- 1 Zero-Touch Overview
- 2 Introduction
- 2.1 Interactions between components in Auto Config architecture
- 2.2 DHCP provisioning options
- 2.3 DHCP—current and new configuration options
- 2.4 Prerequisites for enabling Auto Config
- 2.5 iDRAC interfaces to enable Auto Config
- 2.5.1 Enabling Auto Config using RACADM (local or remote)
- 2.5.2 Enabling Auto Config using Redfish
- 2.5.3 Enabling Auto Config using iDRAC UI
- 2.6 Using Auto Config in an IPv6 Network
- 2.7 Server Configuration Profiles
- 3 Performing Firmware Repository Update During Auto Config
- 4 Performing Operating System Deployment During Auto Config
- 5 Configuring Windows and Linux DHCP servers to support Auto Config
- 5.1 Auto Config Server Configuration Profile String Format for DHCP Option 43 and DHCPv6 Option 17
- 5.2 Configuring Windows DHCP server option 43
- 5.3 Configuring Windows DHCP server option 60
- 5.4 Configuring Windows DHCPv6 server options 16 and 17
- 5.5 Configuring a Linux DHCP server
- 5.6 Configuring a Linux DHCPv6 Server
- 6 File naming behavior with iDRAC Auto Config
- 7 Workflow Examples
- 8 Troubleshooting Auto Config issues
- 9 Conclusion
- A Technical support and resources
20
URI:
redfish/v1/Managers/iDRAC.Embedded.1/Actions/Oem/EID_674_Manager.ExportSystemC
onfiguration
Header: content-type application/json
Body:
{"ExportFormat":"JSON","ShareParameters":{"Target":"ALL","IPAddress":"192.168.
0.130","ShareType":"HTTP","ShareName":"http_share","FileName":"R640_SCP_file.j
son"}}
NOTE: For more details on supported parameters and values, see schema
“redfish/v1/Schemas/OemManager_v1.xml.”
2. Query the job ID using TaskService URI, verify you see a job status of completed successfully.
NOTE: Once the job ID is marked completed, the task ID is auto deleted within a few seconds. To check the
job status, use URI “redfish/v1/JobService/Jobs/<job ID>.”