Environment variables
Environment variables are used to select the different SR-SIM components. The variables are a way of passing information from the container management system to the container itself. This information is then used to emulate the required hardware and provide BOF-specific initial configuration information.
It is not mandatory for users to configure environment variables. If environment variables are not provided, the SR-SIM automatically uses either statically defined or dynamically adjusted values for the variables.
The environment variable field names must be provided in uppercase letters. The value of the environment variable is case-insensitive.
The following table lists the available environment variables and their default values.
| Environment variable | Default | Description |
|---|---|---|
NOKIA_SROS_CHASSIS |
sr-1 |
Chassis type |
NOKIA_SROS_CHASSIS_TOPOLOGY |
Unset | If the user requires an XRS-40, the chassis topology must be set to
xrs40. This only applies when the
NOKIA_SROS_CHASSIS variable is set to
xrs-20 or xrs-20e. |
NOKIA_SROS_SLOT |
A |
Identifies the slot the container relates to |
NOKIA_SROS_SFM |
dynamic | The SFM type (if required) |
NOKIA_SROS_CARD |
dynamic | The card type |
NOKIA_SROS_XIOM_<M> |
dynamic | The XIOM type (if required). <M> represents
the XIOM position. |
NOKIA_SROS_MDA_[<M>_]<N> |
dynamic | The MDA type (if required). <M> and
<N> represent the MDA position. |
NOKIA_SROS_ADDRESS_IPV4_ACTIVE |
dynamic | Lead CPM management IPv4 address. Dynamically assigned by the container management system if not set. |
NOKIA_SROS_ADDRESS_IPV6_ACTIVE |
dynamic | Lead CPM management IPv6 address. Dynamically assigned by the container management system if not set. |
NOKIA_SROS_STATIC_ROUTE_<N> |
0.0.0.0/0@<gateway_ip>1 |
Static route in the format of subnet/bits@nexthop,
for example: 192.168.40.0/24@192.168.10.1.
<N> is an integer starting from
1, and should be incremented for each static route
required. |
NOKIA_SROS_SYSTEM_BASE_MAC |
dynamic | The system base MAC address in the format of
aa:bb:cc:dd:ee:ff, for example:
de:ff:ab:c9:43:fe. |
NOKIA_SROS_MGMT_IF |
eth0 |
Management interface name inside the container |
NOKIA_SROS_FABRIC_IF |
eth1 |
Fabric interface name inside the container |
NOKIA_SROS_PORT_SPEED |
c5-c12-1g/10g |
The default port speed for built-in ports on the 7705 SAR-Hx and 7705 SAR-Mx. Valid options are c5-c12-1g/10g and
c5-c10-10g+c11-c12-10g/25g. |
NOKIA_SROS_SYSTEM_PROFILE |
profile-a |
The system chassis profile for FP4/FP5 and SAR Gen 2 systems to
define chassis behavior. Valid options are profile-a,
profile-b, a, or
b. |
NOKIA_SROS_EMULATED_SYSTEM_SECRET |
Unset |
Specifies the emulated system secret. This is a top-level secret used for local encryption functions. Some examples include encryption of confidential system files on the local filesystem and protection of the primary secret, which is used for hash3 configuration shared secrets. See "Configuration secrets" in the 7450 ESS, 7750 SR, 7950 XRS, and VSR System Management Guide for more information about primary secret and hash3. Note: It is highly recommended to commission each
system with a unique emulated system secret generated from a
high-entropy source.
The emulated system secret is a string with the following constraints:
On distributed SR-SIM systems, the secret is not required for IOMs. For redundant CPMs, the system will use whatever secret is commissioned against CPM A (the CPM B secret is ignored and CPM B will use the secret from CPM A). |
<gateway_ip> is replaced by the default
gateway provided by the container management system. If no default
gateway is provided, this will remain unset.