NETCONFC_1.3.6.1.4.1.2011.5.25.217.2.7 hwNetconfClientConfigFailed

Trap Buffer Description

Failed to deliver configurations to a peer device. (peerName=[peerName], addrType=[addrType], address=[address], featureName=[featureName])

The configuration delivered to the remote device fails to be executed.

In VS mode, this trap is supported only by the admin VS.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	REMOTE_NETCONF_CONFIG_FAILED
Trap OID	1.3.6.1.4.1.2011.5.25.217.2.7
MIB	HUAWEI-NETCONF-MIB
Alarm ID	0x082a2002
Alarm Name	REMOTE_NETCONF_CONFIG_FAILED
Alarm Type	communicationsAlarm
Raise or Clear	Raise
Match trap	NETCONFC_1.3.6.1.4.1.2011.5.25.217.2.8 hwNetconfClientConfigSynchronizedSuccess

Trap Buffer Parameters

Parameter	Description
peerName	Name of the remote end.
addrType	This object indicates the remote address type.
address	Remote IP address.
featureName	Module that fails to be started.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.217.1.8	hwNetconfClientPeerName	-
1.3.6.1.4.1.2011.5.25.217.1.4	hwNetconfSessionInetAddrType	-
1.3.6.1.4.1.2011.5.25.217.1.5	hwNetconfSessionPeerIPAddress	-
1.3.6.1.4.1.2011.5.25.217.1.9	hwNetconfClientAppFeatureName	-

Impact on the System

The configuration of the faulty module does not take effect on the remote end.

Possible Causes

The peer device fails to process the configuration packet sent from the local device for three consecutive times.

Procedure

1. View the NETCONF/6/NCA_OPER_RPC_REQ and NETCONF/6/NCA_OPER_RPC_RSP logs to locate the location where the configuration fails to be delivered and the cause.

2. Modify the configuration that fails to be delivered on the local end and deliver it again.

If the delivery is successful, no further action is required.
If the delivery fails, go to Step 3.

3. Collect log and configuration information, and contact technical support personnel.