CONFIGURATION_1.3.6.1.4.1.2011.6.10.2.5 hwCfgB2STransferFail

Trap Buffer Description

Failed to transfer the configuration file to (index=[hwCfgBackupIndex]) server [hwCfgBackupServerIp] through [hwCfgBackupProtocol] when automatically backing up the configuration.

The configuration file failed to be backed up to the server.

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

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	hwCfgB2STransferFail
Trap OID	1.3.6.1.4.1.2011.6.10.2.5
MIB	HUAWEI-CONFIG-MAN-MIB
Alarm ID	This is an event trap and does not involve alarm ID.
Alarm Name	This is an event trap and does not involve alarm name.
Alarm Type	This is an event trap and does not involve alarm type.
Raise or Clear	This is an event trap and does not involve alarm generation or clearance.
Match trap	-

Trap Buffer Parameters

Parameter	Description
hwCfgBackupIndex	Index of the server table.
hwCfgBackupServerIp	IP address of a server.
hwCfgBackupProtocol	File transfer mode.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.6.10.1.3.7.1.1	hwCfgBackupIndex	hwCfgBackupIndex
1.3.6.1.4.1.2011.6.10.1.3.7.1.2	hwCfgBackupServerIp	hwCfgBackupIndex
1.3.6.1.4.1.2011.6.10.1.3.7.1.3	hwCfgBackupProtocol	hwCfgBackupIndex

Impact on the System

If this alarm is generated multiple times, a configuration may be incorrect or a link fails. As a result, the configuration file cannot be backed up to the server.

Procedure

1. Run the ping command to test whether the server is reachable.

If the ping fails, check the routing configurations between the device and the server.
If the ping succeeds, go to step 2.

2. Use the device as the client and access the server to check whether the password is correct.

If the server cannot be accessed after you enter the password, the password is incorrect. Run the set save-configuration backup-to-server command to change the password to a correct one.
If the server can be accessed after you enter the password, the password is correct. Go to step 3.

3. Check the user name configurations on the server.

If the user name of the server is incorrect, reconfigure the user name.
If the user name is correct, go to step 4.

4. Check the path configurations on the server.

If the server path is incorrect, reconfigure the parameters.
If the server path is correct, go to step 5.

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