CLKM_1.3.6.1.4.1.2011.5.25.186.1.8.38 hwClockGnssModelChange

Trap Buffer Description

Switches the mode of the smart clock module. (hwClockPortIfIndex=[hwClockPortIfIndex], hwClockPortName=[hwClockPortName], hwClockGnssModel=[hwClockGnssModel], hwClockOldGnssModel=[hwClockOldGnssModel])

Module mode change notification.

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	hwClockGnssModelChange
Trap OID	1.3.6.1.4.1.2011.5.25.186.1.8.38
MIB	HUAWEI-CLOCK-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
hwClockPortIfIndex	Index of the port whose working mode is changed.
hwClockPortName	Name of the port whose working mode is changed.
hwClockGnssModel	New working mode. The value can be: gps(1) glonass(2) beidou(3) gps-glonass(4) gps-beidou(5)
hwClockOldGnssModel	Old working mode of the port. The value can be: gps(1) glonass(2) beidou(3) gps-glonass(4) gps-beidou(5)

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.186.1.7.26	hwClockPortIfIndex	-
1.3.6.1.4.1.2011.5.25.186.1.7.27	hwClockPortName	-
1.3.6.1.4.1.2011.5.25.186.1.7.28	hwClockGnssModel	-
1.3.6.1.4.1.2011.5.25.186.1.7.29	hwClockOldGnssModel	-

Impact on the System

This log message is informational only, and services are not affected.

Possible Causes

Cause 1: The user manually changed the configuration to switch the GNSS mode.

Cause 2: The mode of the module is automatically switched based on the priority.

Procedure

1. Run the display smart-clock command to check the current working mode and the number of working modes.

If the RAT information is consistent with that in the reported log, the log is reported normally. In this case, go to Step 3.
If the RAT is inconsistent with that in the reported log, go to Step 2.

2. Collect trap, log, and configuration information, and contact technical support.

3. End.