Configuration Guide for Cisco NCS 1001, IOS XR Release 25.x.x

Fault profiles

Updated: July 27, 2026

Want to summarize with AI?

This topic explains how fault profiles change default fault severities for system, node, slot, and port scopes so that generated faults use the severity values that match your operational requirements.

A fault profile is a user-defined fault configuration that

contains one or more fault identifiers with assigned severities,
overrides the default severity for matching faults when the profile is applied, and
uses precedence from the most specific scope to the least specific scope.

The default fault list captures all the fault types generated by the system and the default severity for each fault type. When no fault profile is defined or applied, the system uses the default severity value.

Fault profile precedence starts at the most specific scope. Port-level profiles have the highest precedence, and system-level profiles have the lowest precedence.

Severity levels

Fault profiles support these severity levels:

Critical
Major
Minor
Non-Faulted
Non-Reported

Fault profile actions

You can use fault profiles to

create or delete a fault profile,
add alarms to a fault profile,
remove alarms from a fault profile, and
change the severity of an alarm in an existing fault profile.

Fault profile limitations

Use these limitations to decide whether fault profiles apply to your alarm management design.

Supported scope and profile limits

These limitations apply to fault profiles:

Fault profiling is available only for data path alarms. Supported alarms include Ethernet, generic framing procedure (GFP), optics, optical transport section (OTS), SDH, SONET, G.709, and Common Public Radio Interface (CPRI).
You can create a maximum of 61 profiles.
You can apply only one fault profile at each node level or port level.

Configure a fault profile

Use a fault profile when a fault requires a severity that differs from the default system profile.

The fault-profile command creates the profile, and the fault-profile apply command attaches the profile to the required scope.

The severity-level value for sas and nsas can be CRITICAL , MAJOR , MINOR , NONFAULTED , or NONREPORTED .

For each fault-type, the node supports a list of fault-name values that correspond to alarms that the node can raise. For example, HW_OTS supports OTS_AS_MT , OTS_APC_RUNNING , OTS_SWITCH_TO_PROTECT , OTS_APC_CONFIG_MISMATCH , OTS_APC_DISABLED , OTS_AUTO_POW_RED , OTS_AUTO_LASER_SHUT , OTS_AMPLI_GAIN_HIGH , OTS_AMPLI_GAIN_LOW , OTS_RX_LOC , OTS_RX_LOS_P , OTS_RX_POWER_FAIL_LOW , and OTS_TX_POWER_FAIL_LOW .

Before you begin

Identify the fault type, fault tag, severity values, and target scope for the profile.

Procedure

	1.	Enter global configuration mode. configure terminal
	2.	Use the fault-profile command to create a fault profile with a unique name. fault-profile fault-profile-name
	3.	Use the fault identifier command to add the fault identifier and severity values to the fault profile. fault identifier subsystem XR fault-type `{` HW_GFP `\|` HW_ETHERNET `\|` HW_SDH_CONTROLLER `\|` HW_SONET `\|` HW_OPTICS `\|` HW_G709 `\|` HW_CPRI `\|` HW_OTS`}` fault-tag fault-name sas severity-level nsas severity-level
	4.	Commit the profile configuration. commit
	5.	Apply the fault profile at the required scope. fault-profile fault-profile-name apply rack 0 slot `{` ALL `\|` LC1 `\|` LC2 `\|` LC3`} [` port port-id`]`
	6.	Commit the applied profile. commit
	7.	Exit configuration mode. exit

The fault profile changes the severity for matching faults at the scope where the profile is applied.

Port or slot-level profile

This example creates a fault profile and applies it at the port or slot level.


RP/0/RP0/CPU0:ios#configure terminal
RP/0/RP0/CPU0:ios(config)#fault-profile FpSystem fault-identifier subsystem XR
fault-type HW_OTS fault-tag OTS_SWITCH_TO_PROTECT sas NONFAULTED nsas NONFAULTED
RP/0/RP0/CPU0:ios(config)#commit
RP/0/RP0/CPU0:ios(config)#fault-profile FpSystem apply rack 0 slot LC2 port 1
RP/0/RP0/CPU0:ios(config)#commit
RP/0/RP0/CPU0:ios(config)#exit

Node-level profile

This example creates a fault profile and applies it at the node level.


RP/0/RP0/CPU0:ios#configure terminal
RP/0/RP0/CPU0:ios(config)#fault-profile FpNode fault-identifier subsystem XR
fault-type HW_OTS fault-tag OTS_RX_LOS_P sas CRITICAL nsas CRITICAL
RP/0/RP0/CPU0:ios(config)#commit
RP/0/RP0/CPU0:ios(config)#fault-profile FpNode apply rack 0 slot ALL
RP/0/RP0/CPU0:ios(config)#commit
RP/0/RP0/CPU0:ios(config)#exit

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.