Configuring the iRMC via SCCI and scripted configuration
12.2
Configuring the iRMC via SCCI and scripted configuration
This section provides information on the following topics:
– How to use an SCCI (ServerView Common Command Interface) compliant interface for configuring the iRMC.
– Scripted configuration of the iRMC
12.2.1 iRMC configuration data
I
Please note that the interface described below is mainly for remote configuration and is not an SCCI implementation. It only uses the SCCI command and configuration definitions and the SCCI file format.
12.2.1.1 Overview
The iRMC stores internal configuration data in separate sections of its NVRAM
(Non-volatile RAM):
– FTS-specific ConfigSpace data, which is addressed by the firmware via an internal description or mapping table.
– Original, manufacturer-specific OMD NVCFG data, which is accessed by offset definitions.
Some configuration data from the original OMD NVCFG data is internally mapped by the firmware to be accessible via ConfigSpace access methods. For instance, DNS servers and DNS configuration of the iRMC can be accessed both via IPMI OEM LAN configuration parameters and via ConfigSpace. Both methods access the same low level data structures in the original NVCFG area.
Non-iRMC-specific ServerView software components (e.g. the ServerView
Agents or the Server Configuration Manager) in some cases also map standard
IPMI related commands and configuration items, such as standard IPMI user configuration or IPv4 network configuration. This implements an abstraction level between the IPMI BMC layer and higher software levels.
452
iRMC
Configuring the iRMC via SCCI and scripted configuration
The SCCI is a generic application programming interface (API) defined by
Fujitsu for different Server Management Controller hardware as well as Server
Management software (e.g. ServerView Agents). It can be easily extended to cover new commands or new configuration items. For an architectural overview of the SCCI, see the online help of the ServerView agents.
The iRMC supports remote configuration and limited scripting via the
/config URL
in the iRMC S4.
Benefits of remote iRMC configuration via web-based access
Remote configuration of the iRMC via web-based access provides the following benefits:
– Uses HTTP POST operation for uploading files onto the iRMC. No special tool is required. Any generic tool or scripting environments supporting authenticated HTTP POST operations can be used. Sample scripts can be found on the ServerView Suite DVD 2.
– Uses built-in authentication and authorization methods of the iRMC Web server.
– Supports HTTP 1.1 Basic and Digest authentication based on RFC 2617 with local iRMC user accounts.
– Features optional built-in strong encryption with standard HTTPS-based access.
– Can be used with global user accounts (managed by an LDAP directory service) and HTTP 1.1 Basic authentication.
I
If HTTP 1.1 Basic authentication is used, it is recommended that, for encryption and confidentiality reasons, you use the HTTPS protocol to protect the username/password combination.
– Uses a configuration file format that is based on XML. You have the option to edit the file manually, or to export it from a reference installation or from the Server Configuration Manager.
The configuration file can be re-used with other SCCI based installation methods (e.g. Server Configuration Manager).
– Can be easily extended to new configuration items and new supported SCCI commands.
iRMC S4
453
