TAIT-INFRA93SERIES-MIB :: nwChannelGroupTransmitterSynchStatus

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TAIT-INFRA93SERIES-MIB › nwChannelGroupTransmitterSynchStatus

nwChannelGroupTransmitterSynchStatus

Module: TAIT-INFRA93SERIES-MIB

OID (symbolic): TAIT-INFRA93SERIES-MIB::nwChannelGroupTransmitterSynchStatus

OID (numeric): 1.3.6.1.4.1.3570.2.2.2.1.5.2.7

Node type: OBJECT-TYPE

Type: TransmitterSyncStatus

Access: read-only

Description: The Synchronization status indicates whether the base station's transmission is synchronized and if not then gives reasons why. A base station transmitter in a simulcast channel group must be synchronized for simulcast operation. An unsynchronized base station does not transmit, unless it is specifically configured to transmit even though unsynchronized. Range: no-license(0): The base station does not have a license to operate in Simulcast mode. non-simulcast-operation(1): The current channel profile does not enable simulcast. bad-frequency-reference(2): The base station has frequency reference either faulty or absent and is therefore unsynchronized. never-had-1pps(3): The base station has never had a 1PPS. It is either faulty or absent and is therefore unsynchronized. never-had-ntp(4): The base station has never had NTP so it is therefore unsynchronized. missing-1pps-or-ntp(5): 1PPS or NTP is faulty or absent after initial synchronisation. synchronized(6): The transmitter is able to synchronize its transmissions with the other members of the channel group. Simulcast is functioning properly. non-channelgroup-operation(7):The current channel profile does not enable channel group operation.

What is nwChannelGroupTransmitterSynchStatus?

Reports whether the base station's transmitter is synchronized within its simulcast channel group -- required for it to transmit at all, unless specifically configured to transmit while unsynchronized -- and if not, gives a specific reason such as a bad frequency reference, missing 1PPS/NTP, or no simulcast license. Admins use the specific reason value to target the correct fix, since 'unsynchronized' alone doesn't say whether the problem is licensing, hardware, or timing signals.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3570.2.2.2.1.5.2.7
snmpwalk -v2c -c public <target> TAIT-INFRA93SERIES-MIB::nwChannelGroupTransmitterSynchStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3570.2.2.2.1.5.2.7.1
snmpget -v2c -c public <target> TAIT-INFRA93SERIES-MIB::nwChannelGroupTransmitterSynchStatus.1

Start monitoring Tait TB93XX-series DMR/analog base station (license/RF-status/RSSI monitoring) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TAIT-INFRA93SERIES-MIB::nwChannelGroupTransmitterSynchStatus OID value, configure state conditions and alerts, and monitor any Tait TB93XX-series DMR/analog base station (license/RF-status/RSSI monitoring) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.3570taitTAIT-COMMON-MIB
1.3.6.1.4.1.3570.2taitGenericTAIT-COMMON-MIB
Numeric OIDNameModule
1.3.6.1.4.1.3570.2.2infra93MIBTAIT-INFRA93SERIES-MIB
1.3.6.1.4.1.3570.2.2.2monitoredTAIT-INFRA93SERIES-MIB
1.3.6.1.4.1.3570.2.2.2.1mibObjectsTAIT-INFRA93SERIES-MIB
1.3.6.1.4.1.3570.2.2.2.1.5networkInterfacesTAIT-INFRA93SERIES-MIB
1.3.6.1.4.1.3570.2.2.2.1.5.2nwChannelGroupTAIT-INFRA93SERIES-MIB
1.3.6.1.4.1.3570.2.2.2.1.5.2.7nwChannelGroupTransmitterSynchStatusTAIT-INFRA93SERIES-MIB