Fujitsu IRMC S2/S3 manual

Configuring the iRMC S2/S3 via SCCI and scripted configuration

12.2.1.3 Restrictions

All commands specified in the .pre file are normally executed sequentially. The following are exemptions from this rule:

–To prevent broken network connectivity, commands for IPv4 and VLAN network configuration are executed at the end of a command sequence.

–Currently, IPv6 configuration is limited to the configuration of the non-volatile IPv6 configuration parameters.

As a workaround, you can proceed as follows:

1.Arrange your script as follows:

a)At the beginning of the script: Disable IPv6.

b)Configure IPv6 parameters.

c)At the end of the script: Enable IPv6

2.Submit the script from an IPv4 address.

–The SSL certificate and the related matching private key are executed at the end of a command sequence. Both components must be present in the same .pre file and are checked for matching each other.

–If a power management operation for the managed server or a reboot of the iRMC S2/S3 is required or desired:

It is recommended (but not required) to run these commands in separate command files. You can achieve this e.g. by splitting the configuration and power management operations into separate tasks.

–Optional time delays between the execution of consecutive commands must implemented outside the script.

For example, you can achieve this as follows:

1.Devide the script appropriately into separate scripts.

2.Use the functional range of the client to insert time delays between sending the individual files.

418 iRMC S2/S3