1 White Paper irmc Remote Scripting and configuration White Paper irmc Remote Scripting and configuration This White Paper describes how to use in Fujitsu PRIMERGY servers the integrated Remote Management Controller's ( irmc ) internal Data Format Specification File to configure irmc settings remotely and use this mechanism for unattended Remote deployment of irmc parameters. Content Introduction 2. irmc configuration Data 2. Overview 2. Advantages through this Implementation 2. Restrictions and Known Limitations 3. SCCI File Format 3. Export of configuration Data from the irmc 5. Export of configuration Data with cURL 5. Import of configuration Data 6.
2 Scripted configuration of the irmc Family 7. Supported SCCI Commands in irmc S2 / irmc S3 / irmc S4 7. irmc S2 / irmc S3 Specific Commands 7. irmc S4 Specific Commands 7. Scripting with cURL 8. Generating Encrypted Passwords with 8. Change BIOS Parameters via irmc 9. BIOS Single Parameter Restoration via cURL 9. Error Checking and Reporting 9. Automatic Power-on After BIOS Single Parameter Restore 10. Remote scripted update of BIOS and irmc 10. Updating irmc Firmware from File 10. Updating BIOS from File 11. Checking an irmc Firmware or BIOS Update Progress 11. Error Checking and Progress Reporting 11. Sample Scripts 13. Attachments 15.
3 Glossary 15. Page 1 of 15 White Paper irmc Remote Scripting and configuration Introduction Within Fujitsu PRIMERGY servers the ServerView integrated Remote Management Controller ( irmc ) enables extensive monitoring and management functions. To perform the tasks of a Baseboard Management Controller (BMC) a large number of various irmc settings have to be defined and maintained. In smaller IT environments users commonly access a server manually before installing any operating system and prepare its configuration for the upcoming setup. Looking at the same situation in a larger environment with more servers, this method does not come in that handy anymore due to the big effort involved when preparing each and every single server manually.
4 In order to pre-configure and deploy PRIMERGY servers in a more automated approach Fujitsu introduced the Scripting functionality for the irmc . With Scripting only one irmc has to be configured according to the requirements of an environment; this configuration is then uploaded to all other PRIMERGY servers without the need to access them all one by one. This document explains: how Fujitsu's integrated Remote Management Controller stores its settings, which possibilities are given to set and change them how these configuration settings can be uploaded automatically to other PRIMERGY servers via the Scripting interface Furthermore, this White Paper shows how an unattended irmc update as well as the system's BIOS firmware is deployed.
5 Finally, it describes a way for changing BIOS parameters via a script using the irmc 's restoration mechanism. irmc configuration Data Overview The irmc family firmware stores internal configuration data in different NVRAM sections, namely the Fujitsu specific ConfigSpaces. Some configuration data is mapped internally by the firmware to be accessible via ConfigSpace access methods. For instance the DNS. servers and DNS configuration can be accessed via IPMI LAN configuration parameters, or via ConfigSpace. Both methods access the same low level data structures in the original NVCFG (nonvolatile configuration ) area. External tools, such as the ServerView Agents or the SCU.
6 (Server configuration Utility) or IPMIVIEW might provide additional mapping of standard IPMI related commands and configuration items, such as standard IPMI user configuration or IPv4 network configuration in order to abstract the IPMI BMC layer from higher software levels. The Server Control Command Interface (SCCI) is a generic API defined by Fujitsu for different server management controller hardware as well as server management software. It can be easily extended to new commands or to new configuration items. Starting with the irmc S2 firmware (IPv6 version) Remote configuration and Scripting via the http://< irmc IP address>/config URL is supported.
7 Please note, that this interface is mainly for Remote configuration and is not a SCCI implementation. It only uses the command and configuration definitions from SCCI and the file format. Advantages through this Implementation Remote configuration of the irmc via web based access provides the following advantages: Uses HTTP/HTTPS POST operation for file upload to the irmc S2 / irmc S3 / irmc S4. No special tool is required, any generic tool or Scripting environment which supports authenticated HTTP / HTTPS POST operations can be used Uses built-in authentication and authorization methods of the irmc web server A Remote user gets the same permissions for configuration as they get with an interactive logon to the irmc .
8 Support for HTTP Basic and Digest authentication based on RFC2617 with local irmc user accounts Optional built-in strong encryption with standard HTTPS based access Can be used with centralized Directory / LDAP user accounts and HTTP Basic authentication Note: When HTTP Basic authentication is used, it is recommended to use HTTPS as protocol for encryption and confidentiality in order to protect the username / password configuration file format is based on XML. The file can be manually edited or exported from a reference installation as well as exported from the SCU (Server configuration Utility). The configuration file can be re-used with other SCCI based installation methods (SCU or other).
9 Can be easily extended to new configuration items or new supported SCCI commands Page 2 of 15 White Paper irmc Remote Scripting and configuration Restrictions and Known Limitations All commands specified in the XML file (also a .pre-file type can be used) are normally executed sequentially, one command after the other. Exemptions from this rule are listed below: IPv4 and VLAN network configuration : These commands are executed at the end of a command sequence in order to prevent broken network connectivity SSL certificate and matching private key: These are executed at the end of a command sequence. Both components have to be present in the same XML file (also a.)
10 Pre file type can be used) and are checked for valid formats and for correct file types If a power management operation for the managed server or a reboot of the irmc itself is required or desired, it is recommended (but not required) to use separate command files for these commands, divide configuration and power management tasks into separate tasks. Optional delays between commands have to be performed outside of the script, divide the script into separate scripts and perform the delay between sending of the files with the operation possibilities of the client. SCCI File Format The format of the used XML configuration file is taken from the file Setup configuration help file which is installed together with the ServerView Agents on Windows platforms.