Filter
Top Products
412 iRMC S2/S3
Configuring the iRMC S2/S3 via SCCI and scripted configuration
12.2 Configuring the iRMC S2/S3 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 S2/S3.
– Scripted configuration of the iRMC S2/S3
12.2.1 iRMC S2/S3 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 S2/S3 stores internal configuration data in two separate sections of
its NVRAM (Non-volatile RAM):
– FTS-specific ConfigSpace data, which is addressed by the firmware via a
fixed internal description table.
– Original, manufacturer-specific NVCFG data, which is accessed by offset
definitions.
Some configuration data from the original 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 S2/S3 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 S2/S3-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.