BMC Configuration

Summary

In order to prepare all the hardware for the showroom environment and before it is going to be onboarded certain tasks need to be done.
In this case, the BMC needs to be configured and secured so that every server aligns with operational and security best practices.

Scope

✅ In Scope

• Delete or change default manufacturer credentials.
• Ensure no multiple user backends are active simultaneously.
• Avoid static network config – use DHCP.
• Configure/verify DNS and NTP.
• Discuss the integration with the logging & monitoring systems in the environment.
• The process should be kept as generic as possible, any usage of manufacturer specific tools needs to be documented

❌ Out of Scope

• The actual implementation of the logging & monitoring system for the whole environment is out of scope for this ticket.

Responsible Areas

Metal Automation, Documentation

Contributors

• @5kt

Acceptance Criteria

• Metal Automation

  • Before onboarding, a server's BMC must not use manufacturer default credentials
  • For the BMC network interface only DHCP must be used
  • DNS and NTP configuration must be correct

• Documentation

  • Provide documentation regarding the user credentials, network configuration, DNS, NTP BMC configuration.

Action Items

• Assign labels (e.g., area/ironcore-api, kind/design)
• Set milestone (e.g., H1/2025)
• Assign dependent sub-issues in each required area
• Assign an owner to the issue using the GitHub "Assignee" field
• List all contributors in the "Contributors" section above
• Add this issue to the Roadmap project board