System profiles

System profiles provide flexibility when using FP4-based line cards by supporting different system capabilities. The system profile is defined in the BOF and is used by the system when it is next rebooted. Contact your Nokia representative for system profile information.

The following system profiles are supported:

profile none

This profile represents the existing system capabilities and allows FP3- and FP4-based hardware to coexist within a system. This profile is indicated by the omission of the profile parameter in the BOF.
profile A
This profile is primarily targeted at subscriber services and Layer 2 and 3 VPN business services and is defined by configuring the following:
- MD-CLI
```
bof system profile profile-a
```
- classic CLI
```
bof system-profile profile-a
```
profile B

This profile is primarily targeted at infrastructure routing, core, peering, and DC-GW applications.

System profiles profile-a and profile-b support only FP4-based line cards. Provisioning FP2- or FP3-based line cards is prohibited when the system profile is set to profile-a or profile-b. If FP2- or FP3-based card types are present in the boot configuration when using these profiles, the boot sequence aborts the loading of the configuration file when it encounters their configuration.

When changing between system profiles, it is mandatory to remove all configuration commands for features that are not supported in the target system profile before rebooting the system, otherwise the reboot fails at the unsupported configuration command on startup.

On 7750 SR-1 and 7750 SR-s systems, the following conditions apply about the profile parameter:

The parameter should be configured to either profile-a or profile-b.
If the parameter is omitted, profile profile-a is used by the system.
If the parameter is configured to an invalid value, it is ignored and profile profile-a is used by the system.

On 7750 SR-7-B/12-B/12e and 7950 XRS-20/20e systems, the following conditions apply about the profile parameter:

The default system profile is none when the parameter is omitted.
The parameter can be configured to either profile-a or profile-b, in which case only FP4-based line cards are supported.
If the parameter is configured to an invalid value, it is ignored and profile none is used by the system.

On all other systems, the following conditions apply about the profile parameter:

These systems must use profile none (the existing system capabilities). As a result, the parameter must not be configured.
If the parameter is configured to profile-a or profile-b, the system boots, allowing access using the console and CPM management interface, but FP2-based and FP3-based line cards cannot be provisioned; if these card types are present in the boot configuration, the boot sequence aborts loading the configuration file when it encounters their configuration. This issue can be corrected by removing the parameter and rebooting the system.
If the parameter is configured to an invalid value, it is ignored and profile none is used by the system.

If a system has two CPMs, and the standby CPM boots with a different profile parameter than is used on the active CPM, the active CPM reboot the standby CPM and keep it in a down state. To correct the situation, the BOF can be reconfigured on the standby CPM to match the one configured on the active CPM, and then reboot the system. Alternatively, automatic BOF synchronization can be enabled to keep both CPMs in sync using the following command:

configure redundancy synchronize boot-env

When performing a minor or major ISSU software upgrade on dual CPM systems, it is important that the system profile in the BOF on both the active and standby CPM is the same and has a value supported on the pre-upgrade software release. If the standby CPM happened to have a system profile which is only supported in the post-upgrade release, the active CPM reboots the standby and keeps it down because of a system profile mis-match.

The BOF system profile can be displayed with the following command:

MD-CLI

admin show configuration bof | match profile

classic CLI
```
show bof | match system-profile
```

The BOF system profile used by the system when it booted can be seen in the boot messages (using the show boot-messages command), which display the BOF read when rebooting.

The system profile in use on the system can be displayed with the following command:

show chassis | match "System Profile"

To configure the system profile, use the following command:

MD-CLI
```
bof system profile
```
classic CLI
```
bof system-profile
```