Preparing the Installation Configuration File

You can optionally create an installation configuration file that contains all of the network settings you collected in Gathering Information. (Note that the file does not contain your passwords; you are prompted for them on the command line.) This installation configuration file, zen_config.yaml, is a template file located in /opt/stratus/install that you modify for your specific configuration. This option is useful for planning out and entering all of the configuration entries before starting the BMC configuration or software installation, especially if you intend to install more than one system with similar parameters.

You use the same installation configuration file as input to the BMC configuration script (bmc_config.sh), software installation script (install.sh), or network configuration script (net_config.sh).

If you exit out of the software installation script before completing the installation process, the system automatically saves a copy of your latest configuration entries in a configuration file with a time-stamped file name in the /opt/stratus/install directory.

For more information about the installation configuration file:

Example of the Installation Configuration File provides an example of the installation configuration file.
Creating the Installation Configuration File explains how to create or modify the installation configuration file for your system-specific needs.

Example of the Installation Configuration File

An example of the zen_config.yaml template file follows.

Notice: If your template file contains an entry for windows_osname instead of win_osname, change the entry to win_osname.

# SYSTEM INFORMATION
system_id:                                       # Use '$SYSTEM-ID$' to include in hostname construction
system_domain:                                   # Use '$SYSTEM-DOMAIN$' to include in hostname construction
system_nameserver:                               # Use '$NAMESERVER$ to use this for nameserver fields below or '--NONE--'

# Information shared by all components on the 1G ztC Endurance management network
# BMCs, Standby
zenmgmt_gateway:                                 # IPV4/V6 address or None (for dhcp)
zenmgmt_netmask:                                 # IPV4 subnet address or None (for dhcp/ipv6/(if prefix supplied in ip))
zenmgmt_ipv6_prefix:                             # IPV6 prefix or None (for dhcp/ipv4/(if prefix supplied in ip))


# BMC
bmca_hostname: $SYSTEM-ID$bmca.$SYSTEM-DOMAIN$   # BMCA hostname (may be a fully qualified domain name)
bmcb_hostname: $SYSTEM-ID$bmcb.$SYSTEM-DOMAIN$   # BMCB hostname (may be a fully qualified domain name)
bmc_netproto:                                    # BMC IP protocol ('dhcp' or 'static')
bmca_eth0:                                       # BMC A eth 0 IPV4/V6 address(ipaddr/prefix) or None (for dhcp)
bmca_eth1:                                       # BMC A eth 1 IPV4/V6 address(ipaddr/prefix) or None (for dhcp)
bmcb_eth0:                                       # BMC B eth 0 IPV4/V6 address(ipaddr/prefix) or None (for dhcp)
bmcb_eth1:                                       # BMC B eth 1 IPV4/V6 address(ipaddr/prefix) or None (for dhcp)

# Standby
standbya_hostname:  $SYSTEM-ID$a.$SYSTEM-DOMAIN$ # Standby A node hostname (may be a fully qualified domain name)
standbyb_hostname:  $SYSTEM-ID$b.$SYSTEM-DOMAIN$ # Standby B node hostname (may be a fully qualified domain name)
standby_netproto:                                # Standby IP protocol ('dhcp' or 'static')
standbya_ipaddr_1:                               # Standby IPV4/V6 address(ipaddr/prefix) or None (for dhcp) for A eno1
standbya_ipaddr_2:                               # Standby IPV4/V6 address(ipaddr/prefix) or None (for dhcp) for A eno2
standbyb_ipaddr_1:                               # Standby IPV4/V6 address(ipaddr/prefix) or None (for dhcp) for B eno1
standbyb_ipaddr_2:                               # Standby IPV4/V6 address(ipaddr/prefix) or None (for dhcp) for B eno2
standby_nameserver: $NAMESERVER$                 # Standby IPV4/V6 address or '--NONE--' (for dhcp)

# Windows
win_hostname: $SYSTEM-ID$.$SYSTEM-DOMAIN$        # Windows hostname (may be a fully qualified domain name)
win_bootproto:                                   # IP protocol ('dhcp' or 'static')
win_ipaddr:                                      # IPV4/V6 address(ipaddr/prefix) or None (for dhcp)
win_gateway:                                     # IPV4/V6 address or None (for dhcp)
win_netmask:                                     # IPV4 subnet address or None (for dhcp/ipv6/(if prefix supplied in ip))
win_ipv6_prefix:                                 # IPV6 prefix or None (for dhcp/ipv4/(if prefix supplied in ip))
win_nameserver: $NAMESERVER$                     # IPV4/V6 address or '--NONE--' 
windows_iso:                                     # Windows ISO path/URL
win_osname:                                      # Type of windows OS Datacenter/Standard

# Windows Management (ztC Endurance UI console)
win_mgmt_netproto:                               # Windows Management network  protocol ('dhcp' or 'static')
win_mgmt_ipaddr1:                                # Windows Managemen IPV4/V6 address(ipaddr/prefix) or None (for dhcp)
win_mgmt_ipaddr2:                                # Windows Managemen IPV4/V6 address(ipaddr/prefix) or None (for dhcp)

# ASN
asn_enabled:                                     # Indicates whether Support Notifications over ASN are enabled ('yes' or 'no')
asn_asset_id:                                    # Asset Identifier

# EOF

Creating the Installation Configuration File

The template installation configuration file is located in the Standby OS, which runs Linux. Therefore, you need to use a Linux-based text editor to modify the file. This topic describes how to use the nano text editor, which is installed on the Standby OS, to modify the file.

To learn more about the nano text editor, see help resources on the web. For example:

https://www.nano-editor.org/docs.php

Notes:

To use privileged commands in the zenadmin account, you need to add the sudo directive. If you open a file in nano without sudo, you cannot save the configuration file in its original, privileged directory.
In the examples, the dollar sign ($) is the command-line prompt; you do not type it.
When the Standby OS boots, you are in the zenadmin home directory, /home/zenadmin. To modify the zen_config.yaml file, you must change to the directory where the file is located, /opt/stratus/install.

The following procedure describes how to create or modify the zen_config.yaml file with the nano text editor.

To create or modify `zen_config.yaml` with `nano`

Change the directory from the zenadmin home directory to the directory where the template zen_config.yaml file is located.
```
$ cd /opt/stratus/install/ 
```
Save a copy of the existing template zen_config.yaml file as zen_config.yaml.orig.
```
$ sudo cp zen_config.yaml zen_config.yaml.orig 
```
Open the zen_config.yaml file with the nano text editor.
```
$ sudo nano zen_config.yaml  
```
When the file opens, use the arrow keys to navigate as you type the settings.

Note: The ^ characters shown on the bottom menu indicate the Ctrl key.
When you finish editing the file, press CtrlX , then press Y to save the changes or N to discard any changes to the file.

Additional considerations:

If you forgot to use the sudo directive, and the system does not allow you to save the configuration file, you can save your changes to a file in the /home/zenadmin directory. Later, you can specify the configuration file's path name on the command line, or you can simply specify its file name if /home/zenadmin is the current working directory.
When typing entries in the configuration file, you must add a space between the colon (:) and the entry text. For example, bmca_eth0: 10.10.40.32.
When you are typing and moving around the file, be careful not to insert any unsupported characters or text that would prevent the installation script from properly reading the file.
Avoid modifying the configuration file in other operating systems or word processors that might add unsupported line feeds or special characters. Use only a plain text editor such as nano.
If you are familiar with the vi text editor, you can use it to modify the configuration file rather than using nano.

Next Steps

After you have created your customized installation configuration file, return to IV. Transfer the Windows ISO Image to the ztC Endurance System.

Product Support Stratus Customer Service Phone: (US Toll-Free) 866-763-1813 Phone: (International) 602-852-3094	About Stratus U.S. Operations 5 Mill and Main Place Suite 500 Maynard, MA 01754-2660 978-461-7000 Worldwide Office Locations Contact Stratus
Product Documentation (PDF Format) ztC Endurance 3x00, 5x00, and 7x00 Systems: User's Guide (Windows) (R006C) ztC Endurance 3x00, 5x00, and 7x00 Systems: Unpacking a System (R004C) ztC Endurance 3x00, 5x00, and 7x00 Systems: Deploying a System (R002C)	About Help Help created at 8:36 AM on 4/22/2025. Notice and Copyrights

Preparing the Installation Configuration File

Example of the Installation Configuration File

Creating the Installation Configuration File

To create or modify zen_config.yaml with nano

Next Steps

To create or modify `zen_config.yaml` with `nano`