Scci File Format - Cisco C880 M5 Configuration Manual

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 software components 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.
Benefits of remote iRMC configuration
Remote configuration of the iRMC via web-based access provides the following benefits:
Uses HTTP POST (Power on self test) operation for uploading files onto the
l
iRMC. No special tool is required. Any generic tool or scripting environments
supporting authenticated HTTP POST operations can be used.
Uses built-in authentication and authorization methods of the iRMC Web server.
l
Supports HTTP 1.1 Basic and Digest authentication based on RFC 2617 with
l
local iRMC user accounts.
Features optional built-in strong encryption with standard HTTPS-based access.
l
Can be used with global user accounts (managed by an LDAP directory service)
l
and HTTP 1.1 Basic authentication.
Uses a configuration file format that is based on XML. You can edit the file
l
manually, or 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.
l
Server Configuration Manager).
Can be easily extended to new configuration items and new
l
supported SCCI commands.
5.4.2

SCCI file format

The format of the XML configuration file (.pre) with iRMC S5-specific notes is
shown below.
Cisco C880 M5 Configuration Guide
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.
5.4 SCCI
67