TAIT-INFRA93SERIES-MIB
Tait International LimitedrctRfTransmitter, rctRfReceiver, rctSelectedChannel related Monitored values in the TB93XX series Base Stations
snmptranslate -m TAIT-INFRA93SERIES-MIB -Tpsnmpwalk -v2c -c <community> -m TAIT-INFRA93SERIES-MIB <host> 1.3.6.1.4.1.3570.1.1.10.2Imports
| SNMP-FRAMEWORK-MIB | SnmpAdminString |
|---|---|
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP |
| SNMPv2-SMI | Bits, Counter32, Integer32, IpAddress, MODULE-IDENTITY, MibIdentifier, OBJECT-IDENTITY, OBJECT-TYPE, TimeTicks, Unsigned32, iso |
| SNMPv2-TC | DisplayString, PhysAddress, TEXTUAL-CONVENTION, TruthValue |
| TAIT-COMMON-MIB | taitGeneric |
| TAIT-INFRA93-94SERIES-COMMON-MIB | infra93-94MibModule |
| TAIT-INFRA93-94SERIES-TC-MIB | AlarmState, BaseStationMode, ChannelGroupStatus, Condition, CurrentmA, FrequencyHz, GateState, Milliseconds, OptionState, PowerW, TimingControlType, TransmitterStatus, VoltageV |
| TAIT-INFRA93SERIES-TC-MIB | ColourCode, ControlProtocolStatus, DcsCode, FallbackNodeStatus, FrequencydHz, LeveldBm, LogicalChannelState, MPTControlProtocolStatus, OperationalMode, Ratio, ReceiverSyncStatus, RxFrequencyResponse, SINADLevel, StandaloneNodeStatus, SubAudibleType, Temperature, TransmitterSyncStatus, TxFrequencyResponse |
OID tree
| Name | OID | Type | Access | Status | Example | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Iinfra93MibMonitored | 1.3.6.1.4.1.3570.1.1.10.2 | ||||||||||||
identity rctRfTransmitter, rctRfReceiver, rctSelectedChannel related Monitored values in the TB93XX series Base Stations | |||||||||||||
| Ninfra93MIB | 1.3.6.1.4.1.3570.2.2 | ||||||||||||
| Nmonitored | 1.3.6.1.4.1.3570.2.2.2 | ||||||||||||
| NmibObjects | 1.3.6.1.4.1.3570.2.2.2.1 | ||||||||||||
| NproductInfo | 1.3.6.1.4.1.3570.2.2.2.1.1 | ||||||||||||
| NproductSummary | 1.3.6.1.4.1.3570.2.2.2.1.1.1 | ||||||||||||
| Ninfo | 1.3.6.1.4.1.3570.2.2.2.1.1.1.1 | ||||||||||||
| SinfoTransmitterStatus | 1.3.6.1.4.1.3570.2.2.2.1.1.1.1.1 | TransmitterStatus | RO | ||||||||||
scalar · TransmitterStatus · read-only · current The current status of the transmitter. unknown(0): The transmitter is in an unknown, probably faulty state. unconfigured(1): The transmitter requires configuration before it can transmit. untuned(2): Something is wrong with the configuration, so the exciter is unable to set the selected frequency. idle(3): The transmitter is not transmitting on either channel. transmitting(4): The transmitter is actively transmitting. calibrating(5): The transmitter is being calibrated. fault(6): There is a detected fault with the transmitter. | |||||||||||||
| SinfoStandaloneNodeStatus | 1.3.6.1.4.1.3570.2.2.2.1.1.1.1.2 | StandaloneNodeStatus | RO | deprecated | |||||||||
scalar · StandaloneNodeStatus · read-only · deprecated The current status of standalone mode.
offline(0): A maintainer has taken the base station offline. The base station is not under node control.
standby(1): The standalone node is enabled and ready to become active if the base station loses contact with the node.
The standby state can also occur if the base station has lost contact with the node, but an activated major alarm at the base station prevents the standalone node from becoming active.
active(2): The base station has lost connection with the node and is in standalone node mode.
disabled(4): The standalone node feature is disabled in configuration.
running(5): The standalone node is contending with other embedded nodes on the site to take over as the master node.
master(6): The standalone node is acting as a master node and has set up a control channel on this base station. | |||||||||||||
| SinfoMPTFallbackNodeStatus | 1.3.6.1.4.1.3570.2.2.2.1.1.1.1.3 | FallbackNodeStatus | RO | ||||||||||
scalar · FallbackNodeStatus · read-only · current The current status of the MPT fallback node. | |||||||||||||
| SinfoDMRFallbackNodeStatus | 1.3.6.1.4.1.3570.2.2.2.1.1.1.1.4 | FallbackNodeStatus | RO | ||||||||||
scalar · FallbackNodeStatus · read-only · current The current status of the DMR fallback node. | |||||||||||||
| Nhealth | 1.3.6.1.4.1.3570.2.2.2.1.1.1.2 | ||||||||||||
| ShealthRunMode | 1.3.6.1.4.1.3570.2.2.2.1.1.1.2.2 | BaseStationMode | RO | 1 | |||||||||
scalar · BaseStationMode · read-only · current Indicates the current base station mode. Offline means that a maintainer has taken the base station out of service. offline(0): The base station is currently offline. It is out of service. It does not transmit or receive user traffic. It communicates with a web browser but not with nodes. online(1): The base station is currently online. This is its normal operating mode. unknown(2): The base station mode is unknown. This indicates a faulty condition. Example values from LibreNMS test devices
| |||||||||||||
| ShealthNetworkConnLogChan1State | 1.3.6.1.4.1.3570.2.2.2.1.1.1.2.3 | LogicalChannelState | RO | 3 | |||||||||
scalar · LogicalChannelState · read-only · current Indicates the state of logical channel 1. inactive(0): The logical channel is not transmitting. idle(1): The logical channel is currently idle. It is not currently a traffic channel or a control channel. traffic(2): The logical channel is currently operating as a traffic channel (voice/data). control(3): The logical channel is currently operating as a control channel. test(4): The logical channel is currently operating as a test channel. poll(5): The logical channel is currently operating as a poll channel. invalid(255): The logical channel configuration is invalid. Example values from LibreNMS test devices
| |||||||||||||
| ShealthNetworkConnLogChan2State | 1.3.6.1.4.1.3570.2.2.2.1.1.1.2.4 | LogicalChannelState | RO | 1 | |||||||||
scalar · LogicalChannelState · read-only · current Indicates the state of logical channel 2. inactive(0): The logical channel is not transmitting. idle(1): The logical channel is currently idle. It is not currently a traffic channel or a control channel. traffic(2): The logical channel is currently operating as a traffic channel (voice/data). control(3): The logical channel is currently operating as a control channel. test(4): The logical channel is currently operating as a test channel. poll(5): The logical channel is currently operating as a poll channel. invalid(255): The logical channel configuration is invalid. Example values from LibreNMS test devices
| |||||||||||||
| ShealthSecureShellRunning | 1.3.6.1.4.1.3570.2.2.2.1.1.1.2.5 | TruthValue | RO | 2 | |||||||||
scalar · TruthValue · read-only · current Indicates whether the remote secure shell interface is running. Range: true(1), false(2) Example values from LibreNMS test devices
| |||||||||||||
| NproductEnabledFeatures | 1.3.6.1.4.1.3570.2.2.2.1.1.2 | ||||||||||||
| SlicenceDmrFull | 1.3.6.1.4.1.3570.2.2.2.1.1.2.300 | TruthValue | RO | ||||||||||
scalar · TruthValue · read-only · current DMR Full license. The base station is licensed for operation on a DMR Full system. Range: true(1), false(2) | |||||||||||||
| SlicenceAnalogConventional | 1.3.6.1.4.1.3570.2.2.2.1.1.2.301 | TruthValue | RO | ||||||||||
scalar · TruthValue · read-only · current Analog Conventional licence. The base station is licenced for Analog conventional operation Range: true(1), false(2) | |||||||||||||
| SlicenceDmrExpress | 1.3.6.1.4.1.3570.2.2.2.1.1.2.302 | TruthValue | RO | ||||||||||
scalar · TruthValue · read-only · current DMR Express 6 license. The base station is licensed for operation on a DMR Express system. Range: true(1), false(2) | |||||||||||||
| SlicenceDmrAccess | 1.3.6.1.4.1.3570.2.2.2.1.1.2.303 | TruthValue | RO | ||||||||||
scalar · TruthValue · read-only · current DMR Access license. The base station is licensed for operation on a DMR Access system. Range: true(1), false(2) | |||||||||||||
| SlicenceDmrConventional | 1.3.6.1.4.1.3570.2.2.2.1.1.2.304 | TruthValue | RO | ||||||||||
scalar · TruthValue · read-only · current DMR Conventional license. The base station is licensed for operation on a DMR concentional system. Range: true(1), false(2) | |||||||||||||
| SlicenceDmrExpress20 | 1.3.6.1.4.1.3570.2.2.2.1.1.2.305 | TruthValue | RO | ||||||||||
scalar · TruthValue · read-only · current DMR Express 20 license. The base station is licensed for operation on a DMR Express 20 system. Range: true(1), false(2) | |||||||||||||
| SlicenceDmrCentralVoter | 1.3.6.1.4.1.3570.2.2.2.1.1.2.306 | TruthValue | RO | ||||||||||
scalar · TruthValue · read-only · current DMR Central Voter license. The base station is licensed for operation as a DMR Central Voter. Range: true(1), false(2) | |||||||||||||
| SlicenceDmrNetworkSatellite | 1.3.6.1.4.1.3570.2.2.2.1.1.2.307 | TruthValue | RO | ||||||||||
scalar · TruthValue · read-only · current DMR IP Networking Satellite license. The base station is licensed for operation as a DMR IP Networking satellite. Range: true(1), false(2) | |||||||||||||
| Nmodules | 1.3.6.1.4.1.3570.2.2.2.1.2 | ||||||||||||
| Nreciter | 1.3.6.1.4.1.3570.2.2.2.1.2.2 | ||||||||||||
| NrctSummary | 1.3.6.1.4.1.3570.2.2.2.1.2.2.1 | ||||||||||||
| NrctInfo | 1.3.6.1.4.1.3570.2.2.2.1.2.2.1.1 | ||||||||||||
| SrctInfoProductCode | 1.3.6.1.4.1.3570.2.2.2.1.2.2.1.1.1 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current The reciter product code. Product codes are explained in the Specifications Manual. | |||||||||||||
| SrctInfoSerialNumber | 1.3.6.1.4.1.3570.2.2.2.1.2.2.1.1.2 | SnmpAdminString | RO | 18271180 | |||||||||
scalar · SnmpAdminString · read-only · current The reciter serial number. A unique identifier assigned to the module in the factory. Example values from LibreNMS test devices
| |||||||||||||
| SrctInfoHardwareVersion | 1.3.6.1.4.1.3570.2.2.2.1.2.2.1.1.3 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current The reciter hardware version number. | |||||||||||||
| SrctInfoFirmwareVersion | 1.3.6.1.4.1.3570.2.2.2.1.2.2.1.1.4 | SnmpAdminString | RO | dmr-3.05.00.0007 | |||||||||
scalar · SnmpAdminString · read-only · current The version number of the firmware currently installed on the Reciter. Example values from LibreNMS test devices
| |||||||||||||
| NrctHealth | 1.3.6.1.4.1.3570.2.2.2.1.2.2.1.2 | ||||||||||||
| NrctSelectedChannel | 1.3.6.1.4.1.3570.2.2.2.1.2.2.2 | ||||||||||||
| SrctSelectedChannelNumber | 1.3.6.1.4.1.3570.2.2.2.1.2.2.2.1 | Unsigned32 | RO | 1 | |||||||||
scalar · Unsigned32 · read-only · current Number of the currently selected channel. Range: 1..1000 Example values from LibreNMS test devices
| |||||||||||||
| SrctSelectedChannelName | 1.3.6.1.4.1.3570.2.2.2.1.2.2.2.2 | SnmpAdminString | RO | LIN-1 | |||||||||
scalar · SnmpAdminString · read-only · current Name of the current channel. Example values from LibreNMS test devices
| |||||||||||||
| SrctSelectedChannelProfileName | 1.3.6.1.4.1.3570.2.2.2.1.2.2.2.3 | SnmpAdminString | RO | DMR Tier 3 | |||||||||
scalar · SnmpAdminString · read-only · current Name of the channel profile assigned to the currently selected channel. Example values from LibreNMS test devices
| |||||||||||||
| SrctSelectedChannelSigProfileName | 1.3.6.1.4.1.3570.2.2.2.1.2.2.2.4 | SnmpAdminString | RO | Color Code 0 | |||||||||
scalar · SnmpAdminString · read-only · current Name of the signalling profile assigned to the currently selected channel. Example values from LibreNMS test devices
| |||||||||||||
| SrctSelectedChannelTransmitPower | 1.3.6.1.4.1.3570.2.2.2.1.2.2.2.5 | PowerW | RO | 25 | |||||||||
scalar · PowerW · read-only · current Configured PA RF transmit power in watts for the current channel when it is powered by mains. Range: 0..100 Example values from LibreNMS test devices
| |||||||||||||
| SrctSelectedChannelTxFreq | 1.3.6.1.4.1.3570.2.2.2.1.2.2.2.6 | FrequencyHz | RO | 466687500 | |||||||||
scalar · FrequencyHz · read-only · current The transmit frequency of the current channel in Hz. Range: 100000000..1000000000 Example values from LibreNMS test devices
| |||||||||||||
| SrctSelectedChannelRxFreq | 1.3.6.1.4.1.3570.2.2.2.1.2.2.2.7 | FrequencyHz | RO | 456687500 | |||||||||
scalar · FrequencyHz · read-only · current The receive frequency of the current channel in Hz. Range: 100000000..1000000000 Example values from LibreNMS test devices
| |||||||||||||
| SrctSelectedChannelSystemType | 1.3.6.1.4.1.3570.2.2.2.1.2.2.2.10 | OperationalMode | RO | 3 | |||||||||
scalar · OperationalMode · read-only · current The type of network configured in the channel profile of the currently selected channel, analogConventional(1), dmrConventional(2), dmrTrunking(3), mptTrunking(4) Example values from LibreNMS test devices
| |||||||||||||
| SrctSelectedChannelColourCode | 1.3.6.1.4.1.3570.2.2.2.1.2.2.2.11 | ColourCode | RO | 0 | |||||||||
scalar · ColourCode · read-only · current The configured colour code for the currently selected channel Example values from LibreNMS test devices
| |||||||||||||
| SrctSelectedChannelGroupName | 1.3.6.1.4.1.3570.2.2.2.1.2.2.2.12 | SnmpAdminString | RO | Disabled | |||||||||
scalar · SnmpAdminString · read-only · current Name of the channel group assigned to the currently selected channel. Example values from LibreNMS test devices
| |||||||||||||
| NrctRfReceiveQuality | 1.3.6.1.4.1.3570.2.2.2.1.2.2.3 | ||||||||||||
| SrctRfRcvInterference | 1.3.6.1.4.1.3570.2.2.2.1.2.2.3.2 | TruthValue | RO | ||||||||||
scalar · TruthValue · read-only · current Interference level is above configured RSSI threshold. Range: true(1), false(2) | |||||||||||||
| SrctRfInterferenceCounter | 1.3.6.1.4.1.3570.2.2.2.1.2.2.3.3 | Counter32 | RO | ||||||||||
scalar · Counter32 · read-only · current Counter indicating cumulative number of seconds that interference has been present. Range: 0..4294967295 | |||||||||||||
| SrctRfInterferenceEvents | 1.3.6.1.4.1.3570.2.2.2.1.2.2.3.4 | Counter32 | RO | ||||||||||
scalar · Counter32 · read-only · current The number of times the receiver detects interference. | |||||||||||||
| NrctRfReceiver | 1.3.6.1.4.1.3570.2.2.2.1.2.2.4 | ||||||||||||
| SrctRfReceiverRSSI | 1.3.6.1.4.1.3570.2.2.2.1.2.2.4.1 | LeveldBm | RO | -8888 | |||||||||
scalar · LeveldBm · read-only · current The current strength of the received signal in dBm. Range: -12000..-6000 Example values from LibreNMS test devices
| |||||||||||||
| SrctRfReceiverLC1RSSI | 1.3.6.1.4.1.3570.2.2.2.1.2.2.4.2 | LeveldBm | RO | -12775 | |||||||||
scalar · LeveldBm · read-only · current The current strength of the received signal on logical channel 1 in dBm. Range: -12000..-6000 Example values from LibreNMS test devices
| |||||||||||||
| SrctRfReceiverLC2RSSI | 1.3.6.1.4.1.3570.2.2.2.1.2.2.4.3 | LeveldBm | RO | -12768 | |||||||||
scalar · LeveldBm · read-only · current The current strength of the received signal on logical channel 2 in dBm. Range: -12000..-6000 Example values from LibreNMS test devices
| |||||||||||||
| SrctRfReceiverLC1RxGateState | 1.3.6.1.4.1.3570.2.2.2.1.2.2.4.4 | TruthValue | RO | 2 | |||||||||
scalar · TruthValue · read-only · current Receiver gate state of logical channel 1. Only valid if the logical channel has received anything since powering up. Range: true(1), false(2) Example values from LibreNMS test devices
| |||||||||||||
| SrctRfReceiverLC2RxGateState | 1.3.6.1.4.1.3570.2.2.2.1.2.2.4.5 | TruthValue | RO | 2 | |||||||||
scalar · TruthValue · read-only · current Receiver gate state of logical channel 2. Only valid if the logical channel has received anything since powering up. Range: true(1), false(2) Example values from LibreNMS test devices
| |||||||||||||
| SrctRfReceiverSelectedDecodeCTCSS | 1.3.6.1.4.1.3570.2.2.2.1.2.2.4.8 | FrequencydHz | RO | ||||||||||
scalar · FrequencydHz · read-only · current The CTCSS value that the base station unmutes to. | |||||||||||||
| SrctRfReceiverSelectedDecodeSubAudibleType | 1.3.6.1.4.1.3570.2.2.2.1.2.2.4.9 | SubAudibleType | RO | ||||||||||
scalar · SubAudibleType · read-only · current The configured receive sub-audible signaling type. | |||||||||||||
| SrctRfReceiverSelectedSINADGatingLevel | 1.3.6.1.4.1.3570.2.2.2.1.2.2.4.10 | SINADLevel | RO | ||||||||||
scalar · SINADLevel · read-only · current The configured signal-to-noise gating threshold in dB. | |||||||||||||
| SrctRfReceiverSelectedDecodeDCS | 1.3.6.1.4.1.3570.2.2.2.1.2.2.4.11 | DcsCode | RO | ||||||||||
scalar · DcsCode · read-only · current The DCS value that the base station unmutes to. | |||||||||||||
| SrctRfReceiverSelectedFrequencyResponse | 1.3.6.1.4.1.3570.2.2.2.1.2.2.4.12 | RxFrequencyResponse | RO | ||||||||||
scalar · RxFrequencyResponse · read-only · current Specifies the receive baseband frequency response that applies to the channel. MPT Control channels have a flat speech charactieristic. MPT Traffic channels have a de-emphasis characteristic. Conventional analog channels take their setting from channel profile configuration. 'Flat speech' applies a constant gain to frequencies in the speech band (high pass above 300 Hz). 'De-emph speech' is a de-emphasis characteristic over the speech band (high pass above 300 Hz). | |||||||||||||
| SrctRfReceiverAnalogGateState | 1.3.6.1.4.1.3570.2.2.2.1.2.2.4.13 | TruthValue | RO | ||||||||||
scalar · TruthValue · read-only · current Analog receiver gate state of the channel. Range: true(1), false(2) | |||||||||||||
| SrctRfReceiverIsDisabled | 1.3.6.1.4.1.3570.2.2.2.1.2.2.4.14 | TruthValue | RO | ||||||||||
scalar · TruthValue · read-only · current Status of the receiver; if it is unavailable then the receiver can't be disabled in the current mode of operation. Range: true(1), false(2) | |||||||||||||
| NrctRfTransmitter | 1.3.6.1.4.1.3570.2.2.2.1.2.2.5 | ||||||||||||
| SrctRfTxSelectedEncodeCTCSS | 1.3.6.1.4.1.3570.2.2.2.1.2.2.5.10 | FrequencydHz | RO | ||||||||||
scalar · FrequencydHz · read-only · current The configured transmit CTCSS tone frequency in dHz. | |||||||||||||
| SrctRfTxSelectedEncodeSubAudibleType | 1.3.6.1.4.1.3570.2.2.2.1.2.2.5.11 | SubAudibleType | RO | ||||||||||
scalar · SubAudibleType · read-only · current The configured transmit sub-audible signaling type | |||||||||||||
| SrctRfTxSelectFrequencyResponse | 1.3.6.1.4.1.3570.2.2.2.1.2.2.5.12 | TxFrequencyResponse | RO | ||||||||||
scalar · TxFrequencyResponse · read-only · current Specifies the transmit baseband frequency response that applies to the channel. MPT Control channels have a flat speech charactieristic. MPT Traffic channels have a pre-emphasis characteristic. Conventional analog channels take their setting from channel profile configuration. 'Flat speech' applies a constant gain to frequencies in the speech band (high pass above 300 Hz). 'Pre-emph speech' is a pre-emphasis characteristic over the speech band (high pass above 300 Hz). | |||||||||||||
| SrctRfTxSelectedEncodeDCS | 1.3.6.1.4.1.3570.2.2.2.1.2.2.5.13 | DcsCode | RO | ||||||||||
scalar · DcsCode · read-only · current The DCS sub-audible signalling value that the base station applies while transmitting. | |||||||||||||
| SrctRfTxSelectedEncodeSubAudibleDeviation | 1.3.6.1.4.1.3570.2.2.2.1.2.2.5.14 | Unsigned32 | RO | ||||||||||
scalar · Unsigned32 · read-only · current The deviation that CTCSS or DCS signaling will cause to the carrier frequency. It is in Hz. | |||||||||||||
| SrctRfTxRfRepeatState | 1.3.6.1.4.1.3570.2.2.2.1.2.2.5.16 | OptionState | RO | ||||||||||
scalar · OptionState · read-only · current The current RF repeat state. disabled(0): RF is not repeated. The reciter acts as a base station. enabled(1): RF is repeated. The reciter acts as a repeater. | |||||||||||||
| NrctTemperature | 1.3.6.1.4.1.3570.2.2.2.1.2.2.6 | ||||||||||||
| SrctTemperatureBoard | 1.3.6.1.4.1.3570.2.2.2.1.2.2.6.1 | Temperature | RO | 42 | |||||||||
scalar · Temperature · read-only · current The reciter temperature in degrees Celsius, measured on the reciter circuit board. Range: -30..125 Example values from LibreNMS test devices
| |||||||||||||
| NrctSystemInterface | 1.3.6.1.4.1.3570.2.2.2.1.2.2.7 | ||||||||||||
| SrctSiConfiguredBalancedLineInLevel | 1.3.6.1.4.1.3570.2.2.2.1.2.2.7.1 | LeveldBm | RO | ||||||||||
scalar · LeveldBm · read-only · current The configured level of the balanced line input in dBm. Range: -30..0 | |||||||||||||
| SrctSiConfiguredBalancedLineOutLevel | 1.3.6.1.4.1.3570.2.2.2.1.2.2.7.2 | LeveldBm | RO | ||||||||||
scalar · LeveldBm · read-only · current The configured level of the balanced line output in dBm. Range: -30..0 | |||||||||||||
| SrctSiTxKey | 1.3.6.1.4.1.3570.2.2.2.1.2.2.7.3 | GateState | RO | ||||||||||
scalar · GateState · read-only · current The state of the Tx key input. Range: Active(1), Inactive(2) | |||||||||||||
| SrctSiRxGate | 1.3.6.1.4.1.3570.2.2.2.1.2.2.7.4 | GateState | RO | ||||||||||
scalar · GateState · read-only · current The state of the Rx Gate output. Range: Active(1), Inactive(2) | |||||||||||||
| NpowerAmplifier | 1.3.6.1.4.1.3570.2.2.2.1.2.3 | ||||||||||||
| NpaSummary | 1.3.6.1.4.1.3570.2.2.2.1.2.3.1 | ||||||||||||
| NpaInfo | 1.3.6.1.4.1.3570.2.2.2.1.2.3.1.1 | ||||||||||||
| SpaInfoProductCode | 1.3.6.1.4.1.3570.2.2.2.1.2.3.1.1.1 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current The power amplifier product code. Product codes are explained in the Specifications Manual. | |||||||||||||
| SpaInfoSerialNumber | 1.3.6.1.4.1.3570.2.2.2.1.2.3.1.1.2 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current Power amplifier serial number. A unique identifier assigned to the module in the factory. | |||||||||||||
| SpaInfoHardwareVersion | 1.3.6.1.4.1.3570.2.2.2.1.2.3.1.1.3 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current The power amplifier hardware version number. | |||||||||||||
| SpaInfoFirmwareVersion | 1.3.6.1.4.1.3570.2.2.2.1.2.3.1.1.4 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current The version number of the firmware currently installed on the power amplifier. | |||||||||||||
| NpaHealth | 1.3.6.1.4.1.3570.2.2.2.1.2.3.1.2 | ||||||||||||
| NpaTxOutput | 1.3.6.1.4.1.3570.2.2.2.1.2.3.2 | ||||||||||||
| SpaTxOutputForwardPower | 1.3.6.1.4.1.3570.2.2.2.1.2.3.2.1 | PowerW | RO | 25 | |||||||||
scalar · PowerW · read-only · current The measured forward power of the PA output in Watts. Range: 0..100 Example values from LibreNMS test devices
| |||||||||||||
| SpaTxOutputVSWR | 1.3.6.1.4.1.3570.2.2.2.1.2.3.2.2 | Ratio | RO | 11 | |||||||||
scalar · Ratio · read-only · current The transmitter's voltage standing wave ratio (VSWR). Example values from LibreNMS test devices
| |||||||||||||
| NpaTemperature | 1.3.6.1.4.1.3570.2.2.2.1.2.3.4 | ||||||||||||
| NpaGeneral | 1.3.6.1.4.1.3570.2.2.2.1.2.3.5 | ||||||||||||
| NpowerManagementUnit | 1.3.6.1.4.1.3570.2.2.2.1.2.4 | ||||||||||||
| NpmuSummary | 1.3.6.1.4.1.3570.2.2.2.1.2.4.1 | ||||||||||||
| NpmuInfo | 1.3.6.1.4.1.3570.2.2.2.1.2.4.1.1 | ||||||||||||
| SpmuInfoProductCode | 1.3.6.1.4.1.3570.2.2.2.1.2.4.1.1.1 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current The product code for the PMU. | |||||||||||||
| SpmuInfoSerialNumber | 1.3.6.1.4.1.3570.2.2.2.1.2.4.1.1.2 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current PMU serial number. A unique identifier assigned to the PMU in the factory. | |||||||||||||
| SpmuInfoHardwareVersion | 1.3.6.1.4.1.3570.2.2.2.1.2.4.1.1.3 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current The PMU hardware version number. | |||||||||||||
| SpmuInfoFirmwareVersion | 1.3.6.1.4.1.3570.2.2.2.1.2.4.1.1.4 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current The version number of the firmware currently installed on the PMU. | |||||||||||||
| SpmuInfoCalibrationUpdateDate | 1.3.6.1.4.1.3570.2.2.2.1.2.4.1.1.5 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current Indicates when the PMU was last calibrated. | |||||||||||||
| NpmuHealth | 1.3.6.1.4.1.3570.2.2.2.1.2.4.1.2 | ||||||||||||
| NpmuSubmodules | 1.3.6.1.4.1.3570.2.2.2.1.2.4.1.3 | ||||||||||||
| NpmuState | 1.3.6.1.4.1.3570.2.2.2.1.2.4.2 | ||||||||||||
| SpmuStateMainsInState | 1.3.6.1.4.1.3570.2.2.2.1.2.4.2.1 | Condition | RO | 1 | |||||||||
scalar · Condition · read-only · current The condition of the PMU's AC power input. Range: bad(0): The AC power input is off, or too low, or too high. good(1): The AC power input is usable. not fitted(2): The AC power input module is not fitted. Example values from LibreNMS test devices
| |||||||||||||
| SpmuStateBatteryInState | 1.3.6.1.4.1.3570.2.2.2.1.2.4.2.2 | Condition | RO | 0 | |||||||||
scalar · Condition · read-only · current The condition of the PMU's DC power input. Range: bad(0): The DC power input is off, or too low, or too high. good(1): The DC power input is usable. not fitted(2): The DC power input module is not fitted. Example values from LibreNMS test devices
| |||||||||||||
| SpmuStateBatteryInVoltage | 1.3.6.1.4.1.3570.2.2.2.1.2.4.2.3 | VoltageV | RO | 0 | |||||||||
scalar · VoltageV · read-only · current The measured voltage of the DC (battery) power supply to the PMU. Range: 10.5..15.5. Example values from LibreNMS test devices
| |||||||||||||
| SpmuStateOutCurrent | 1.3.6.1.4.1.3570.2.2.2.1.2.4.2.4 | CurrentmA | RO | 5930 | |||||||||
scalar · CurrentmA · read-only · current The output current in mA that the PMU is supplying to the subrack (PA(s), reciter(s) and control panel). Range: 0..20000. Example values from LibreNMS test devices
| |||||||||||||
| SpmuStateOutVoltage | 1.3.6.1.4.1.3570.2.2.2.1.2.4.2.5 | VoltageV | RO | 2807 | |||||||||
scalar · VoltageV · read-only · current The actual voltage of the PMU output(s) to the PA(s) and reciter(s) in the subrack (nominally 28 V). Range: 0..32. Example values from LibreNMS test devices
| |||||||||||||
| SpmuStateOutStatus | 1.3.6.1.4.1.3570.2.2.2.1.2.4.2.6 | Condition | RO | 1 | |||||||||
scalar · Condition · read-only · current The condition of the PMU power supply to the PA. Range: bad(0): The power supply is absent or its voltage is too low or too high. good(1): The power supply is OK. Example values from LibreNMS test devices
| |||||||||||||
| SpmuStateAuxOutState | 1.3.6.1.4.1.3570.2.2.2.1.2.4.2.7 | Condition | RO | 1 | |||||||||
scalar · Condition · read-only · current The condition of the auxiliary power output. Range: bad(0): The auxiliary power is off, or its voltage is too high or too low. good(1): The auxiliary power output is on. not fitted(2): The auxiliary power module is not fitted. Example values from LibreNMS test devices
| |||||||||||||
| SpmuStateBusConnect | 1.3.6.1.4.1.3570.2.2.2.1.2.4.2.9 | TruthValue | RO | 2 | |||||||||
scalar · TruthValue · read-only · current The state of the DC supply to the PMU's standby converter. Range: connected(1), not connected(2) Example values from LibreNMS test devices
| |||||||||||||
| NfrontPanel | 1.3.6.1.4.1.3570.2.2.2.1.2.5 | ||||||||||||
| NfpSummary | 1.3.6.1.4.1.3570.2.2.2.1.2.5.1 | ||||||||||||
| NfpInfo | 1.3.6.1.4.1.3570.2.2.2.1.2.5.1.1 | ||||||||||||
| SfpInfoProductCode | 1.3.6.1.4.1.3570.2.2.2.1.2.5.1.1.1 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current The product code for the front panel. | |||||||||||||
| SfpInfoSerialNumber | 1.3.6.1.4.1.3570.2.2.2.1.2.5.1.1.2 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current Front panel serial number. A unique identifier assigned to the front panel in the factory. | |||||||||||||
| SfpInfoHardwareVersion | 1.3.6.1.4.1.3570.2.2.2.1.2.5.1.1.3 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current Front panel hardware version number. | |||||||||||||
| SfpInfoFirmwareVersion | 1.3.6.1.4.1.3570.2.2.2.1.2.5.1.1.4 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current The version number of the firmware currently installed on the front panel. | |||||||||||||
| NfpHealth | 1.3.6.1.4.1.3570.2.2.2.1.2.5.1.2 | ||||||||||||
| Nalarms | 1.3.6.1.4.1.3570.2.2.2.1.3 | ||||||||||||
| NalarmSummary | 1.3.6.1.4.1.3570.2.2.2.1.3.1 | ||||||||||||
| SalarmSummaryBaseStation | 1.3.6.1.4.1.3570.2.2.2.1.3.1.1 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Base station summary alarm. The base station currently has one or more active alarms. Connect to the base station to see what these alarms are. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SalarmSummaryReciter | 1.3.6.1.4.1.3570.2.2.2.1.3.1.2 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Reciter summary alarm. The reciter currently has one or more active alarms. Connect to the base station to see what these alarms are. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SalarmSummaryPowerAmplifier | 1.3.6.1.4.1.3570.2.2.2.1.3.1.3 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current PA summary alarm. The PA currently has one or more active alarms. Connect to the base station to see what these alarms are. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SalarmSummaryPowerManagementUnit | 1.3.6.1.4.1.3570.2.2.2.1.3.1.4 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current PMU summary alarm. The PMU currently has one or more active alarms. Connect to the base station to see what these alarms are. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SalarmSummaryCustomAlarms | 1.3.6.1.4.1.3570.2.2.2.1.3.1.5 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Custom summary alarm. There are currently one or more active custom alarms. Connect to the base station to see what these alarms are. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SalarmSummaryFrontPanel | 1.3.6.1.4.1.3570.2.2.2.1.3.1.6 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Front panel summary alarm. The front panel currently has one or more active alarms. Connect to the base station to see what these alarms are. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SalarmSummarySystem | 1.3.6.1.4.1.3570.2.2.2.1.3.1.7 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current System summary alarm. One or more system conditions have triggered alarms. This does not indicate a base station fault. Connect to the base station to see what these alarms are. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SalarmSummaryMinor | 1.3.6.1.4.1.3570.2.2.2.1.3.1.8 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Minor summary alarm. The base station currently has one or more minor alarms. The node will select other channels in preference. Connect to the base station to see what these alarms are. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SalarmSummaryMajor | 1.3.6.1.4.1.3570.2.2.2.1.3.1.9 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Major summary alarm. The base station currently has one or more major alarms. The node will take it out of service. Connect to the base station to see what these alarms are. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| NreciterAlarms | 1.3.6.1.4.1.3570.2.2.2.1.3.3 | ||||||||||||
| SrctAlarmRxSynthOutOfLock | 1.3.6.1.4.1.3570.2.2.2.1.3.3.2 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Receiver synthesizer alarm. The receiver synthesizer is unable to lock on to the frequency it is configured to operate at. In response, the base station disabled the receiver. Check that this frequency is within the receiver's RF frequency range. If it is, send the reciter for repair. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SrctAlarmInvalidChannelSelected | 1.3.6.1.4.1.3570.2.2.2.1.3.3.3 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Channel invalid alarm. An invalid channel number was selected. The base station has stopped operating. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SrctAlarmOverTemperature | 1.3.6.1.4.1.3570.2.2.2.1.3.3.10 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Temperature high alarm. The reciter is approaching its maximum operating temperature. Check if the ambient temperature high alarm is active (Monitor > Alarms > System) and that the reciter, PMU and PA fan Diagnose > Sub-Systems > Fan Tests). This alarm could be caused by a high ambient temperature or a fan failure. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SrctAlarmTxCalibrationInvalid | 1.3.6.1.4.1.3570.2.2.2.1.3.3.13 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Transmitter calibration invalid alarm. This alarm activates if the exciter has become uncalibrated. Send the reciter for repair. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SrctAlarmRxCalibrationInvalid | 1.3.6.1.4.1.3570.2.2.2.1.3.3.14 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Reciter receiver calibration invalid alarm. The RSSI needs to be calibrated for the operational frequency of the channel. Connect to the base station and re-calibrate the RSSI. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SrctAlarmInvalidConfiguration | 1.3.6.1.4.1.3570.2.2.2.1.3.3.15 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Reciter hardware configuration invalid alarm, the base station modules are not compatible Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SrctAlarm25MHzSynthOutOfLock | 1.3.6.1.4.1.3570.2.2.2.1.3.3.16 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Synthesizer out of lock alarm. The reciter's 25 MHz synthesizer cannot remain locked to the external reference. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SrctAlarm6144MHzSynthOutOfLock | 1.3.6.1.4.1.3570.2.2.2.1.3.3.17 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Synthesizer out of lock alarm. The reciter's 61.44 MHz synthesizer cannot remain locked to the external reference. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SrctAlarmTxFSynthOutOfLock | 1.3.6.1.4.1.3570.2.2.2.1.3.3.18 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current The TxF synthesizer is unable to lock on to the frequency it is configured to operate at. In response, the base station disabled the transmitter.
Send the reciter for repair.
Range: unavailable(0), cleared(1), raised(2), disabled(3)Example values from LibreNMS test devices
| |||||||||||||
| SrctAlarmSimulcastSynch | 1.3.6.1.4.1.3570.2.2.2.1.3.3.19 | AlarmState | RO | 3 | |||||||||
scalar · AlarmState · read-only · current The base station cannot achieve synchronization to common time reference required for simulcast operation. If simulcast not needed, uncheck simulcast box in channel profile. Otherwise, check 1PPS and External reference units and NTP server and connectors. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SrctAlarmReceiverSynch | 1.3.6.1.4.1.3570.2.2.2.1.3.3.20 | AlarmState | RO | 3 | |||||||||
scalar · AlarmState · read-only · current Reports whether the receiver is aligned with the transmit TDMA frame synchronization of the transmitters of the channel group. Possible causes for the receiver unsynchronized alarm are: 1. The reciter does not have a valid 1PPS input and is not able to free run 1PPS [ref]. 2. The reciter is not synchronized to a valid NTP server and is not able to free run NTP time. This alarm should be disabled for other system types. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SrctAlarmTxRSynthOutOfLock | 1.3.6.1.4.1.3570.2.2.2.1.3.3.21 | AlarmState | RO | 0 | |||||||||
scalar · AlarmState · read-only · current The TxR synthesizer is unable to lock on to the frequency it is configured to operate at. In response, the base station disabled the transmitter.
Send the reciter for repair.
Range: unavailable(0), cleared(1), raised(2), disabled(3)Example values from LibreNMS test devices
| |||||||||||||
| NpaAlarms | 1.3.6.1.4.1.3570.2.2.2.1.3.4 | ||||||||||||
| SpaAlarmNoPADetected | 1.3.6.1.4.1.3570.2.2.2.1.3.4.1 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current PA not detected alarm. The reciter has not received a response from a PA over the control bus. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmInvalidFirmware | 1.3.6.1.4.1.3570.2.2.2.1.3.4.2 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current PA firmware invalid alarm. The firmware in the PA is invalid. 1. Connect to the base station and activate the latest PA firmware. 2. Replace the PA and send it for repair. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmInvalidCalibration | 1.3.6.1.4.1.3570.2.2.2.1.3.4.3 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Invalid PA calibration alarm. This alarm can only be triggered on start-up, when the PA carries out self-tests. It indicates that settings stored in firmware have values outside acceptable limits. In response, the base station disables the transmitter. Contact your regional Tait office for assistance. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmForwardPowerLow | 1.3.6.1.4.1.3570.2.2.2.1.3.4.5 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Forward power low alarm. The PA forward power output is below the configured minimum limit. If the VSWR is also raised, check for a load mismatch. Otherwise, there may be a fault in the output driver(s). Replace the PA and send for repair. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmPowerFoldback | 1.3.6.1.4.1.3570.2.2.2.1.3.4.7 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Power foldback alarm. The PA has detected a fault condition and, to prevent damage, reduced its power output to 35 Watts. (But only if the configured power output is higher than 35 Watts. If the configured output is less than or equal to 35, it stays the same.)
Check the other alarms to see what fault condition(s) have caused this. If the fault clears, the PA automatically returns to its previous power output level and the alarm returns to green.
This alarm causes the node to take the base station out of service. Once the problem is fixed, you need to send a test transmission to clear the alarm. Only then will the node bring the channel back into service.
Range: unavailable(0), cleared(1), raised(2), disabled(3)Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmReversePowerHigh | 1.3.6.1.4.1.3570.2.2.2.1.3.4.8 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Reverse power high alarm. The PA's reverse power is above the configured maximum.
Check for a load mismatch. This alarm has a resolution of only 1W so it isn't sufficiently sensitive for power outputs below 20W.
Note: This alarm will not show if the transmit combiner uses an isolator.
Range: unavailable(0), cleared(1), raised(2), disabled(3)Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmShutdownImminent | 1.3.6.1.4.1.3570.2.2.2.1.3.4.9 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current PA shut-down alarm. The PA is not operational. It detected a fault condition and disabled the transmitter to prevent damage. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmVSWRFault | 1.3.6.1.4.1.3570.2.2.2.1.3.4.10 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current VSWR alarm. The PA's Voltage Standing Wave Ratio (VSWR) is above the configured threshold. A normal VSWR is <= 2:1.
A high VSWR automatically means reduced output power. If the VSWR increases to 10:1 or more,
the PA folds back its power output to a low level. If the VSWR returns to 5:1 or less, the PA recovers.
Check for a load mismatch on the RF output.
This alarm causes the node to take the base station out of service.
Once the problem is fixed, you need to send a test transmission to clear the alarm. Only then will the node bring the channel back into service.
Range: unavailable(0), cleared(1), raised(2), disabled(3)Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmDriverCurrentHigh | 1.3.6.1.4.1.3570.2.2.2.1.3.4.11 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Driver current high alarm. The driver is drawing excessive current. A fixed limit has been exceeded. Replace the PA and send it for repair. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmFinal1CurrentHigh | 1.3.6.1.4.1.3570.2.2.2.1.3.4.12 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Final 1 current high alarm. The current in the PA's final 1 output stage has exceeded a fixed limit. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmFinal2CurrentHigh | 1.3.6.1.4.1.3570.2.2.2.1.3.4.13 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Final 2 current high alarm. The current in the PA's final 2 output stage has exceeded a fixed limit. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmCurrentImbalance | 1.3.6.1.4.1.3570.2.2.2.1.3.4.14 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Current imbalance alarm. One of the PA's final stages is drawing significantly more current than the other. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmSupplyVoltageLow | 1.3.6.1.4.1.3570.2.2.2.1.3.4.15 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Supply voltage low alarm. The PA supply voltage is 26 V or less, probably because the battery supply to the PMU is running low. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmSupplyVoltageHigh | 1.3.6.1.4.1.3570.2.2.2.1.3.4.16 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Supply voltage high alarm. The power supplied to the PA is 29 V or more. The PMU is faulty and needs replacing, Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmDriverTemperatureHigh | 1.3.6.1.4.1.3570.2.2.2.1.3.4.17 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Driver temperature high alarm. The temperature in the PA's driver output stage has exceeded the configured threshold. If it continues to rise and exceeds a built-in limit, the PA will fold back its power output. To see the actual temperature, connect to the base station and select Diagnose > Sub-Systems > Fan Tests. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmFinal1TemperatureHigh | 1.3.6.1.4.1.3570.2.2.2.1.3.4.18 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Final 1 temperature high alarm. The temperature in the PA's final 1 output stage has exceeded the configured threshold. If it continues to rise and exceeds a built-in limit, the PA will fold back its power output. To see the actual temperature, connect to the base station and select Diagnose > Sub-Systems > Fan Tests. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpaAlarmFinal2TemperatureHigh | 1.3.6.1.4.1.3570.2.2.2.1.3.4.19 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Final 2 temperature high alarm. The temperature in the PA's final 2 output stage has exceeded the configured threshold. If it continues to rise and exceeds a built-in limit, the PA will fold back its power output. To see the actual temperature, connect to the base station and select Diagnose > Sub-Systems > Fan Tests. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| NpmuAlarms | 1.3.6.1.4.1.3570.2.2.2.1.3.5 | ||||||||||||
| SpmuAlarmNoPMUDetected | 1.3.6.1.4.1.3570.2.2.2.1.3.5.1 | AlarmState | RO | 3 | |||||||||
scalar · AlarmState · read-only · current PMU not detected alarm. The reciter has not received a response from the PMU over the control bus. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpmuAlarmInvalidFirmware | 1.3.6.1.4.1.3570.2.2.2.1.3.5.2 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current PMU firmware invalid alarm. The firmware in the PMU is invalid. 1. Connect to the base station and activate the PMU firmware. 2. Replace the PMU and send it for repair. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpmuAlarmMainsFailure | 1.3.6.1.4.1.3570.2.2.2.1.3.5.4 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Mains supply alarm. The mains power supply to the PMU is absent or its voltage is outside acceptable limits. The PMU is using DC power instead. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpmuAlarmSelfTestFailure | 1.3.6.1.4.1.3570.2.2.2.1.3.5.5 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current PMU power-up fault. During start-up, the PMU detected an internal error and will reset itself. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpmuAlarmShutdownImminent | 1.3.6.1.4.1.3570.2.2.2.1.3.5.6 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Shut-down imminent alarm. A battery is currently powering the base station and its voltage has fallen below the configured power shut-down voltage. The PMU will shut down 30 seconds after activating this alarm. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpmuAlarmTemperatureHigh | 1.3.6.1.4.1.3570.2.2.2.1.3.5.7 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current PMU temperature alarm. One of the PMU temperature sensors has detected a temperature that is above the fixed limit. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpmuAlarmBatteryProtect | 1.3.6.1.4.1.3570.2.2.2.1.3.5.8 | AlarmState | RO | 3 | |||||||||
scalar · AlarmState · read-only · current Battery protection mode alarm. Battery protection mode is on. If mains power fails, the PMU will shut down to protect the battery. Battery protection mode is entered when the battery voltage falls below the configured power shutdown voltage. Check the battery backup system. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpmuAlarmBatteryVoltageLow | 1.3.6.1.4.1.3570.2.2.2.1.3.5.9 | AlarmState | RO | 3 | |||||||||
scalar · AlarmState · read-only · current Low battery voltage alarm. The DC voltage supply to the PMU is below the configured alarm threshold. If mains power is lost, the PMU is likely to reduce its output voltage or shut down. Check the charging system. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpmuAlarmBatteryVoltageHigh | 1.3.6.1.4.1.3570.2.2.2.1.3.5.10 | AlarmState | RO | 3 | |||||||||
scalar · AlarmState · read-only · current Battery voltage high alarm. The voltage of the DC power supply to the PMU is higher than the configured maximum. The base station takes no action until the voltage reaches the fixed maximum, when it shuts down. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpmuAlarmCurrentOutHigh | 1.3.6.1.4.1.3570.2.2.2.1.3.5.11 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current PMU high current alarm. The PMU is providing > 15 A of current and is automatically lowering its output voltage. There is a short circuit or the PMU is faulty. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpmuAlarmVoltageOutLow | 1.3.6.1.4.1.3570.2.2.2.1.3.5.12 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Output voltage low alarm. The PMU's DC output (nominally 28 V) is lower than the fixed minimum of 24 V. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SpmuAlarmVoltageOutHigh | 1.3.6.1.4.1.3570.2.2.2.1.3.5.13 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current High voltage alarm. The PMU's DC output (nominally 28 V) is higher than the fixed maximum of 32 V. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| NcustomAlarms | 1.3.6.1.4.1.3570.2.2.2.1.3.6 | ||||||||||||
| ScustomAlarm1 | 1.3.6.1.4.1.3570.2.2.2.1.3.6.1 | AlarmState | RO | ||||||||||
scalar · AlarmState · read-only · current Custom alarm 1. The state of digital input 1 has changed, triggering this alarm. This occurs when external equipment has been connected to the input. When configured as 'active high', a custom alarm is triggered when its input goes to 'high' (4.75V) and it is cleared when its input goes to 'low'. When configured as 'active low', a custom alarm is triggered when its input goes to 'low' (0V) and it is cleared when its input goes to 'high'. Range: unavailable(0), cleared(1), raised(2), disabled(3) | |||||||||||||
| ScustomAlarm2 | 1.3.6.1.4.1.3570.2.2.2.1.3.6.2 | AlarmState | RO | ||||||||||
scalar · AlarmState · read-only · current Custom alarm 2. The state of digital input 2 has changed, triggering this alarm. This occurs when external equipment has been connected to the input. When configured as 'active high', a custom alarm is triggered when its input goes to 'high' (4.75V) and it is cleared when its input goes to 'low'. When configured as 'active low', a custom alarm is triggered when its input goes to 'low' (0V) and it is cleared when its input goes to 'high'. Range: unavailable(0), cleared(1), raised(2), disabled(3) | |||||||||||||
| ScustomAlarm3 | 1.3.6.1.4.1.3570.2.2.2.1.3.6.3 | AlarmState | RO | ||||||||||
scalar · AlarmState · read-only · current Custom alarm 3. The state of digital input 3 has changed, triggering this alarm. This occurs when external equipment has been connected to the input. When configured as 'active high', a custom alarm is triggered when its input goes to 'high' (4.75V) and it is cleared when its input goes to 'low'. When configured as 'active low', a custom alarm is triggered when its input goes to 'low' (0V) and it is cleared when its input goes to 'high'. Range: unavailable(0), cleared(1), raised(2), disabled(3) | |||||||||||||
| ScustomAlarm4 | 1.3.6.1.4.1.3570.2.2.2.1.3.6.4 | AlarmState | RO | ||||||||||
scalar · AlarmState · read-only · current Custom alarm 4. The state of digital input 4 has changed, triggering this alarm. This occurs when external equipment has been connected to the input. When configured as 'active high', a custom alarm is triggered when its input goes to 'high' (4.75V) and it is cleared when its input goes to 'low'. When configured as 'active low', a custom alarm is triggered when its input goes to 'low' (0V) and it is cleared when its input goes to 'high'. Range: unavailable(0), cleared(1), raised(2), disabled(3) | |||||||||||||
| ScustomAlarm5 | 1.3.6.1.4.1.3570.2.2.2.1.3.6.5 | AlarmState | RO | ||||||||||
scalar · AlarmState · read-only · current Custom alarm 5. The state of digital input 5 has changed, triggering this alarm. This occurs when external equipment has been connected to the input. When configured as 'active high', a custom alarm is triggered when its input goes to 'high' (4.75V) and it is cleared when its input goes to 'low'. When configured as 'active low', a custom alarm is triggered when its input goes to 'low' (0V) and it is cleared when its input goes to 'high'. Range: unavailable(0), cleared(1), raised(2), disabled(3) | |||||||||||||
| ScustomAlarm6 | 1.3.6.1.4.1.3570.2.2.2.1.3.6.6 | AlarmState | RO | ||||||||||
scalar · AlarmState · read-only · current Custom alarm 6. The state of digital input 6 has changed, triggering this alarm. This occurs when external equipment has been connected to the input. When configured as 'active high', a custom alarm is triggered when its input goes to 'high' (4.75V) and it is cleared when its input goes to 'low'. When configured as 'active low', a custom alarm is triggered when its input goes to 'low' (0V) and it is cleared when its input goes to 'high'. Range: unavailable(0), cleared(1), raised(2), disabled(3) | |||||||||||||
| ScustomAlarm7 | 1.3.6.1.4.1.3570.2.2.2.1.3.6.7 | AlarmState | RO | ||||||||||
scalar · AlarmState · read-only · current Custom alarm 7. The state of digital input 7 has changed, triggering this alarm. This occurs when external equipment has been connected to the input. When configured as 'active high', a custom alarm is triggered when its input goes to 'high' (4.75V) and it is cleared when its input goes to 'low'. When configured as 'active low', a custom alarm is triggered when its input goes to 'low' (0V) and it is cleared when its input goes to 'high'. Range: unavailable(0), cleared(1), raised(2), disabled(3) | |||||||||||||
| ScustomAlarm8 | 1.3.6.1.4.1.3570.2.2.2.1.3.6.8 | AlarmState | RO | ||||||||||
scalar · AlarmState · read-only · current Custom alarm 8. The state of digital input 8 has changed, triggering this alarm. This occurs when external equipment has been connected to the input. When configured as 'active high', a custom alarm is triggered when its input goes to 'high' (4.75V) and it is cleared when its input goes to 'low'. When configured as 'active low', a custom alarm is triggered when its input goes to 'low' (0V) and it is cleared when its input goes to 'high'. Range: unavailable(0), cleared(1), raised(2), disabled(3) | |||||||||||||
| ScustomAlarm9 | 1.3.6.1.4.1.3570.2.2.2.1.3.6.9 | AlarmState | RO | ||||||||||
scalar · AlarmState · read-only · current Custom alarm 9. The state of digital input 9 has changed, triggering this alarm. This occurs when external equipment has been connected to the input. When configured as 'active high', a custom alarm is triggered when its input goes to 'high' (4.75V) and it is cleared when its input goes to 'low'. When configured as 'active low', a custom alarm is triggered when its input goes to 'low' (0V) and it is cleared when its input goes to 'high'. Range: unavailable(0), cleared(1), raised(2), disabled(3) | |||||||||||||
| ScustomAlarm10 | 1.3.6.1.4.1.3570.2.2.2.1.3.6.10 | AlarmState | RO | ||||||||||
scalar · AlarmState · read-only · current Custom alarm 10. The state of digital input 10 has changed, triggering this alarm. This occurs when external equipment has been connected to the input. When configured as 'active high', a custom alarm is triggered when its input goes to 'high' (4.75V) and it is cleared when its input goes to 'low'. When configured as 'active low', a custom alarm is triggered when its input goes to 'low' (0V) and it is cleared when its input goes to 'high'. Range: unavailable(0), cleared(1), raised(2), disabled(3) | |||||||||||||
| ScustomAlarm11 | 1.3.6.1.4.1.3570.2.2.2.1.3.6.11 | AlarmState | RO | ||||||||||
scalar · AlarmState · read-only · current Custom alarm 11. The state of digital input 11 has changed, triggering this alarm. This occurs when external equipment has been connected to the input. When configured as 'active high', a custom alarm is triggered when its input goes to 'high' (4.75V) and it is cleared when its input goes to 'low'. When configured as 'active low', a custom alarm is triggered when its input goes to 'low' (0V) and it is cleared when its input goes to 'high'. Range: unavailable(0), cleared(1), raised(2), disabled(3) | |||||||||||||
| ScustomAlarm12 | 1.3.6.1.4.1.3570.2.2.2.1.3.6.12 | AlarmState | RO | ||||||||||
scalar · AlarmState · read-only · current Custom alarm 12. The state of digital input 12 has changed, triggering this alarm. This occurs when external equipment has been connected to the input. When configured as 'active high', a custom alarm is triggered when its input goes to 'high' (4.75V) and it is cleared when its input goes to 'low'. When configured as 'active low', a custom alarm is triggered when its input goes to 'low' (0V) and it is cleared when its input goes to 'high'. Range: unavailable(0), cleared(1), raised(2), disabled(3) | |||||||||||||
| NfpAlarms | 1.3.6.1.4.1.3570.2.2.2.1.3.7 | ||||||||||||
| SfpAlarmFan1 | 1.3.6.1.4.1.3570.2.2.2.1.3.7.1 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Fan alarm. The reciter has failed to detect Fan 1 when attempting to activate it upon start-up or when a module temperature threshold is exceeded. The fan may need replacing. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SfpAlarmFan2 | 1.3.6.1.4.1.3570.2.2.2.1.3.7.2 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Fan alarm. The reciter has failed to detect Fan 2 when attempting to activate it upon start-up or when a module temperature threshold is exceeded. The fan may need replacing. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SfpAlarmFan3 | 1.3.6.1.4.1.3570.2.2.2.1.3.7.3 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Fan alarm. The reciter has failed to detect Fan 3 when attempting to activate it upon start-up or when a module temperature threshold is exceeded. The fan may need replacing. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SfpAlarmNoFPDetected | 1.3.6.1.4.1.3570.2.2.2.1.3.7.4 | AlarmState | RO | 3 | |||||||||
scalar · AlarmState · read-only · current The base station is unable to detect the front panel on the control bus. Check the connections of the D-range connector and system control bus cable. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SfpAlarmInvalidFirmware | 1.3.6.1.4.1.3570.2.2.2.1.3.7.5 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Invalid front panel firmware alarm. Connect to the base station and select Tools > Firmware Download to acquire valid firmware. If the firmware is valid contact your regional Tait office for assistance. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| NsystemAlarms | 1.3.6.1.4.1.3570.2.2.2.1.3.8 | ||||||||||||
| SsystemAlarmAmbientTempLow | 1.3.6.1.4.1.3570.2.2.2.1.3.8.1 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Ambient temperature low alarm. The ambient temperature at the front panel air intake is below the configured minimum. Fan operation and PA power output are unaffected by this alarm. This alarm could indicate an air conditioning failure. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SsystemAlarmAmbientTempHigh | 1.3.6.1.4.1.3570.2.2.2.1.3.8.2 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Ambient temperature high alarm. The ambient temperature at the front panel air intake has exceeded the configured maximum. Fan operation and PA power output are unaffected by this alarm. This alarm could indicate an air conditioning failure. Example values from LibreNMS test devices
| |||||||||||||
| SsystemAlarmExternalRefAbsent | 1.3.6.1.4.1.3570.2.2.2.1.3.8.3 | AlarmState | RO | 3 | |||||||||
scalar · AlarmState · read-only · current External frequency reference absent alarm. The base station did not detect an external reference frequency source. It is now using its own source. An external reference is critical for simulcast applications and for K-band operation. 1. The source has become unplugged. 2. The source is not working. 3. There is no external reference source and the alarm was not disabled at installation time. You can disable the alarm (Configure > Alarms > Control). Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SsystemAlarmQoSJitter | 1.3.6.1.4.1.3570.2.2.2.1.3.8.4 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current QoS jitter alarm. The incoming voice stream has a jitter equal to or greater than the configured threshold. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SsystemAlarmQoSLostPackets | 1.3.6.1.4.1.3570.2.2.2.1.3.8.5 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current QoS lost packets alarm. The number of lost packets in the incoming voice stream has equalled or exceeded the configured threshold. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SsystemAlarmFallbackControlled | 1.3.6.1.4.1.3570.2.2.2.1.3.8.6 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current This base station is controlled by an Embedded Node in fallback mode. Example values from LibreNMS test devices
| |||||||||||||
| SsystemAlarmDuplicateNodePriority | 1.3.6.1.4.1.3570.2.2.2.1.3.8.7 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current The base station's BSP priority is being used by another base station on the same site. This alarm is raised only if the base station has been configured as 'CCH Capable'. Example values from LibreNMS test devices
| |||||||||||||
| SsystemAlarmNTPSynchronisation | 1.3.6.1.4.1.3570.2.2.2.1.3.8.8 | AlarmState | RO | 3 | |||||||||
scalar · AlarmState · read-only · current The base station hasn't had received an NTP signal from a server and the clock might be out of synchronization. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SsystemAlarm1PPSAbsent | 1.3.6.1.4.1.3570.2.2.2.1.3.8.9 | AlarmState | RO | 3 | |||||||||
scalar · AlarmState · read-only · current In a simulcast system base stations must have a 1PPS pulse. This alarm should be disabled for other systems. It is not applicable to receive only base stations. The alarm warns that the base station isn't receiving a 1PPS pulse. If the base station loses the pulse but is still receiving its external reference, it phase-locks its transmit clock to the external frequency reference in order to maintain synchronization. This is called Holdover mode and is a temporary measure. When the holdover duration expires the base station becomes unsynchronized. The 'Simulcast unsynchronized' alarm under 'Reciter' below indicates whether the base station is synchronized for simulcast operation. The 'Receiver unsynchronised' alarm in this section indicates whether the base station receiver is synchronized. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SsystemAlarmQoSTransmitBuffer | 1.3.6.1.4.1.3570.2.2.2.1.3.8.10 | AlarmState | RO | 1 | |||||||||
scalar · AlarmState · read-only · current Simulcast satellite base station is receiving packets that cannot fit into the transmit buffer. The alarm can be raised due to one of the two reasons: packets arriving too late or too early. See nwQosUnderflowCount and nwQosOverflowCount for the events that cause the alarm condition. Most likely causes for packets being late are jitter, delay and configuration errors. Most likely cause for packets being too early is preemption. Use SNMP monitoring tools and base station's WUI (Monitoring->Interfaces->Channel Group) to identify the cause. Refer to logs, if the event has happened too far in the past. The alarm is asserted when rate of non-transmitted packets exceeds 1 percent. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SsystemAlarmCartesianLoopUnstable | 1.3.6.1.4.1.3570.2.2.2.1.3.8.11 | AlarmState | RO | 0 | |||||||||
scalar · AlarmState · read-only · current PA feedback loop to linearise transmitter can't achieve specified tolerances. Check TxR cable connected properly, otherwise return for repair. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| SsystemAlarmTxRCableAbsent | 1.3.6.1.4.1.3570.2.2.2.1.3.8.12 | AlarmState | RO | 0 | |||||||||
scalar · AlarmState · read-only · current PA feedback cable to reciter TxR is not working correctly/not present. Ensure that the TxR cable between PA and Reciter TxR is unbroken and connected securely, or return for repair. Range: unavailable(0), cleared(1), raised(2), disabled(3) Example values from LibreNMS test devices
| |||||||||||||
| NnetworkLinks | 1.3.6.1.4.1.3570.2.2.2.1.4 | ||||||||||||
| NnetworkLinksSummary | 1.3.6.1.4.1.3570.2.2.2.1.4.1 | ||||||||||||
| NlinkInfo | 1.3.6.1.4.1.3570.2.2.2.1.4.1.1 | ||||||||||||
| SlinkInfoCtrlProtocolStatus | 1.3.6.1.4.1.3570.2.2.2.1.4.1.1.1 | ControlProtocolStatus | RO | 3 | |||||||||
scalar · ControlProtocolStatus · read-only · current The status of the base station as reported to the node using the control protocol. Range: unconnected(0): The base station is not under node control. deprecatedUnconnected(1): DEPRECATED - The base station is not in contact with a node. standby(2): The base station is in contact with a node. Its air interface is not transmitting or receiving. dmr-aligned(3): The base station is transmitting a framesync structure together with an idle pattern or a payload. dmr-offset(4): Not currently used. dmr-two-slot-data(5): The base station is carrying a data call that uses both logical channels. dmr-hibernate(6): the base station is hibernating analogue(7): Not currently used. test-mode(8): Reserved. dmr-tier2-aligned(9): The base station is transmitting a framesync struture for Tier 2 operation Example values from LibreNMS test devices
| |||||||||||||
| SlinkInfoNetworkPacketCount | 1.3.6.1.4.1.3570.2.2.2.1.4.1.1.2 | Counter32 | RO | 5350406 | |||||||||
scalar · Counter32 · read-only · current Total packets received from the network on control and data protocols. This is an accumulating number. The counter is large enough that the number rolls over infrequently, such as once every few months, depending on call volumes. Example values from LibreNMS test devices
| |||||||||||||
| SlinkInfoMPTCtrlProtocolStatus | 1.3.6.1.4.1.3570.2.2.2.1.4.1.1.3 | MPTControlProtocolStatus | RO | ||||||||||
scalar · MPTControlProtocolStatus · read-only · current The status of the base station as reported to the node using the control protocol. unconnected(0): The base-station is not connected to any MPT-IP node, neither external nor fallback. idle(1): The base-station is connected to a MPT-IP node (either external or fallback). It is not transmitting anything on its air interface (transmitter is off). control(2): The base-station is connected to a MPT-IP node (either external or fallback). Air interface transmitting and receiving MPT control channel signalling only. traffic(3): The base-station is connected to a MPT-IP node (either external or fallback). Voice/Data packets are sent to and received from node, Air interface is transmitting as well as receiving. conventional(4): The base-station is connected to a fallback node. Voice/Data packets are repeated locally from uplink to downlink. Air interface is transmitting as well as receiving. | |||||||||||||
| SlinkInfoDMRNodeIPAddress | 1.3.6.1.4.1.3570.2.2.2.1.4.1.1.4 | SnmpAdminString | RO | 10.5.50.91 | |||||||||
scalar · SnmpAdminString · read-only · current The IP address of the DMR Node Controlling the base station. Example values from LibreNMS test devices
| |||||||||||||
| SlinkInfoDMRNodePriority | 1.3.6.1.4.1.3570.2.2.2.1.4.1.1.5 | Unsigned32 | RO | 1 | |||||||||
scalar · Unsigned32 · read-only · current The priority of the DMR Node Controlling the base station. Example values from LibreNMS test devices
| |||||||||||||
| SlinkInfoMPTNodeIPAddress | 1.3.6.1.4.1.3570.2.2.2.1.4.1.1.6 | SnmpAdminString | RO | ||||||||||
scalar · SnmpAdminString · read-only · current The IP address of the MPT Node Controlling the base station. | |||||||||||||
| SlinkInfoMPTNodePriority | 1.3.6.1.4.1.3570.2.2.2.1.4.1.1.7 | Unsigned32 | RO | ||||||||||
scalar · Unsigned32 · read-only · current The priority of the MPT Node Controlling the base station. | |||||||||||||
| NlinkHealth | 1.3.6.1.4.1.3570.2.2.2.1.4.1.2 | ||||||||||||
| SlinkHealthNetworkPacketLostCount | 1.3.6.1.4.1.3570.2.2.2.1.4.1.2.2 | Counter32 | RO | ||||||||||
scalar · Counter32 · read-only · current Total accumulated number of lost voice and control packets sent from the control and switching nodes. An increasing number indicates that the linking infrastructure has a problem or is congested. | |||||||||||||
| SlinkHealthNetworkJitterLastOver | 1.3.6.1.4.1.3570.2.2.2.1.4.1.2.3 | Unsigned32 | RO | ||||||||||
scalar · Unsigned32 · read-only · current The maximum jitter measured in the last over. | |||||||||||||
| SlinkHealthNetworkJitterCount | 1.3.6.1.4.1.3570.2.2.2.1.4.1.2.4 | Counter32 | RO | ||||||||||
scalar · Counter32 · read-only · current The total number of times the configured jitter threshold has been exceeded. | |||||||||||||
| SlinkHealthSequenceErrorsCount | 1.3.6.1.4.1.3570.2.2.2.1.4.1.2.5 | Counter32 | RO | ||||||||||
scalar · Counter32 · read-only · current The result of lost packets - i.e. the number of times packets have been received out of sequence. This is an accumulating number. | |||||||||||||
| NnetworkInterfaces | 1.3.6.1.4.1.3570.2.2.2.1.5 | ||||||||||||
| NnwNtpInterface | 1.3.6.1.4.1.3570.2.2.2.1.5.1 | ||||||||||||
| SnwConfiguredNtpServerAddress | 1.3.6.1.4.1.3570.2.2.2.1.5.1.1 | DisplayString | RO | ||||||||||
scalar · DisplayString · read-only · current The IP address configured for the preferred NTP server used by the base-station. The current status of NTP for the base-station including the selected server is available via the NTPv4-MIB (RFC 5907) | |||||||||||||
| SnwConfiguredNtpBackupServerAddress1 | 1.3.6.1.4.1.3570.2.2.2.1.5.1.2 | DisplayString | RO | ||||||||||
scalar · DisplayString · read-only · current The IP address configured for a backup NTP server used by the base-station. The current status of NTP for the base-station including the backup servers is available via the NTPv4-MIB (RFC 5907) | |||||||||||||
| SnwConfiguredNtpBackupServerAddress2 | 1.3.6.1.4.1.3570.2.2.2.1.5.1.3 | DisplayString | RO | ||||||||||
scalar · DisplayString · read-only · current The IP address configured for a backup NTP server used by the base-station. The current status of NTP for the base-station including the backup servers is available via the NTPv4-MIB (RFC 5907) | |||||||||||||
| NnwChannelGroup | 1.3.6.1.4.1.3570.2.2.2.1.5.2 | ||||||||||||
| SnwChannelGroupStatus | 1.3.6.1.4.1.3570.2.2.2.1.5.2.1 | ChannelGroupStatus | RO | ||||||||||
scalar · ChannelGroupStatus · read-only · current The voting role that the base station is currently playing within the channel group. | |||||||||||||
| SnwChannelGroupLocalBufferLevel | 1.3.6.1.4.1.3570.2.2.2.1.5.2.2 | Milliseconds | RO | ||||||||||
scalar · Milliseconds · read-only · current The lowest level of the transmit buffer, measured in milliseconds over a 5-second period. | |||||||||||||
| SnwChannelGroupEmptiestBufferLevel | 1.3.6.1.4.1.3570.2.2.2.1.5.2.3 | Milliseconds | RO | ||||||||||
scalar · Milliseconds · read-only · current The level of the transmit buffer (in ms) at the member that has got emptiest buffer-level. It is the smallest transmit buffer of any channel group member. If marshalling is self-regulating, the central voter is responsible for ensuring that there are no buffer underruns. If marshalling is fixed, the marshalling duration must be long enough to prevent buffer underruns. | |||||||||||||
| SnwChannelGroupMarshallingType | 1.3.6.1.4.1.3570.2.2.2.1.5.2.4 | TimingControlType | RO | ||||||||||
scalar · TimingControlType · read-only · current [Simulcast] The Marshalling Type configuration setting indicates how the marshalling time is determined. Range: fixed(0): Configuration defines the marshalling time. self-regulating(1): The network element dynamically adjusts the marshalling time based on the size of the smallest transmit buffer in the channel group. | |||||||||||||
| SnwChannelGroupMarshallingDuration | 1.3.6.1.4.1.3570.2.2.2.1.5.2.5 | Milliseconds | RO | ||||||||||
scalar · Milliseconds · read-only · current In simulcast, the current marshalling duration (in ms). This is fixed in configuration or automatically regulated. This parameter is only used by the central voter (channel group master). Range: 0..300 | |||||||||||||
| SnwChannelGroupReceiverSynchStatus | 1.3.6.1.4.1.3570.2.2.2.1.5.2.6 | ReceiverSyncStatus | RO | ||||||||||
scalar · ReceiverSyncStatus · read-only · current The receiver synchronization status indicates whether the base station's receiver is synchronized and if not then gives reasons why. Range: no-license(0): The base station does not have a license to operate in Simulcast mode. non-channelgroup-operation(1):The current channel group profile does not enable channel group operation. synchronized(2): The transmitter is able to synchronize its transmissions with the other members of the channel group. Simulcast is functioning properly. never-had-1pps(3): The base station has never had a 1PPS signal. 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. | |||||||||||||
| SnwChannelGroupTransmitterSynchStatus | 1.3.6.1.4.1.3570.2.2.2.1.5.2.7 | TransmitterSyncStatus | RO | ||||||||||
scalar · TransmitterSyncStatus · read-only · current 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. | |||||||||||||
| SnwChannelGroupLateStreamsCount | 1.3.6.1.4.1.3570.2.2.2.1.5.2.8 | Counter32 | RO | ||||||||||
scalar · Counter32 · read-only · current The number of times any transmission stream arrives later than the required transmit time. The count is aggregated one since system-startup. | |||||||||||||
| SnwChannelGroupOverflowCount | 1.3.6.1.4.1.3570.2.2.2.1.5.2.9 | Counter32 | RO | ||||||||||
scalar · Counter32 · read-only · current The number of channelgroup messages that did not fit in the transmit buffer or were too far into the future. The count is total such messages since system-startup. | |||||||||||||
| SnwChannelGroupUnderflowCount | 1.3.6.1.4.1.3570.2.2.2.1.5.2.10 | Counter32 | RO | ||||||||||
scalar · Counter32 · read-only · current The number of times transmit-buffer ran empty, since system-startup. | |||||||||||||
| SnwChannelGroupLostPacketsCount | 1.3.6.1.4.1.3570.2.2.2.1.5.2.11 | Counter32 | RO | ||||||||||
scalar · Counter32 · read-only · current The number of packets that were lost during a transmission stream, based on the packet sequence numbering. The count is aggregated one since system-startup. | |||||||||||||
| SnwChannelGroupJitter | 1.3.6.1.4.1.3570.2.2.2.1.5.2.12 | INTEGER | RO | ||||||||||
scalar · INTEGER · read-only · current The jitter-value calculated in compliance with RFC-1889. It is the mean deviation (absolute value) of the difference in packet spacing at the receiver compared to the sender for a pair of packets. The value is in milliseconds. | |||||||||||||
| NnwPorts | 1.3.6.1.4.1.3570.2.2.2.1.5.3 | ||||||||||||
| SnwSvpPort | 1.3.6.1.4.1.3570.2.2.2.1.5.3.1 | Unsigned32 | RO | ||||||||||
scalar · Unsigned32 · read-only · current The configured Simulcast Voted protocol UDP port. | |||||||||||||
| NmibConformance | 1.3.6.1.4.1.3570.2.2.2.5 | ||||||||||||
| NmibGroups | 1.3.6.1.4.1.3570.2.2.2.5.1 | ||||||||||||
| GhealthGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.1 | ||||||||||||
group · current The health Group. | |||||||||||||
| GalarmSummaryGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.2 | ||||||||||||
group · current The alarmSummary Group. | |||||||||||||
| GrctSelectedChannelGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.3 | ||||||||||||
group · current The rctSelectedChannel Group. | |||||||||||||
| GpaTxOutputGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.5 | ||||||||||||
| GlinkInfoGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.6 | ||||||||||||
group · current The linkInfo Group.
| |||||||||||||
| GcustomAlarmsGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.7 | ||||||||||||
group · current The customAlarms group. | |||||||||||||
| GsystemAlarmsGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.8 | ||||||||||||
group · current The systemAlarms Group. | |||||||||||||
| GfpAlarmsGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.9 | ||||||||||||
group · current The fpAlarms Group. | |||||||||||||
| GpaAlarmsGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.10 | ||||||||||||
group · current The paAlarms Group.
| |||||||||||||
| GpmuAlarmsGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.11 | ||||||||||||
group · current The pmuAlarms Group.
| |||||||||||||
| GreciterAlarmsGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.12 | ||||||||||||
group · current The reciterAlarms Group.
| |||||||||||||
| GinfoGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.13 | ||||||||||||
group · current The info Group.
| |||||||||||||
| GrctReceiveQualityGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.14 | ||||||||||||
group · current The receive quality Group. | |||||||||||||
| GrctReceiverGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.15 | ||||||||||||
group · current The receiver Group.
| |||||||||||||
| GrctTemperatureGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.16 | ||||||||||||
| GpmuStateGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.17 | ||||||||||||
group · current The pmu status indications group. | |||||||||||||
| GnwNtpInterfaceGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.18 | ||||||||||||
group · current The network ntp interface group. | |||||||||||||
| GrctTransmitterGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.19 | ||||||||||||
group · current The transmitter group. | |||||||||||||
| GnwChannelGroupGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.20 | ||||||||||||
group · current The group for channelgroup.
| |||||||||||||
| GnwPortsGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.21 | ||||||||||||
| GrctSystemInterfaceGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.22 | ||||||||||||
group · current Reciter system interface | |||||||||||||
| GlinearTransmissionCapability | 1.3.6.1.4.1.3570.2.2.2.5.1.23 | ||||||||||||
group · current Information depending on existence of a linear power amplifier | |||||||||||||
| GpmuInfoGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.24 | ||||||||||||
group · current The PMU info group. | |||||||||||||
| GdeprecatedOidGroup | 1.3.6.1.4.1.3570.2.2.2.5.1.27 | deprecated | |||||||||||
| NmibCompliance | 1.3.6.1.4.1.3570.2.2.2.5.2 | ||||||||||||
| MmibComplianceList | 1.3.6.1.4.1.3570.2.2.2.5.2.1 | ||||||||||||
compliance · current The requirements for conformance to the TAIT-INFRA93SERIES-MIB.
| |||||||||||||
Groups and compliance
- alarmSummaryGroup
- customAlarmsGroup
- deprecatedOidGroup
- fpAlarmsGroup
- healthGroup
- infoGroup
- linearTransmissionCapability
- linkInfoGroup
- mibComplianceList
- nwChannelGroupGroup
- nwNtpInterfaceGroup
- nwPortsGroup
- paAlarmsGroup
- paTxOutputGroup
- pmuAlarmsGroup
- pmuInfoGroup
- pmuStateGroup
- rctReceiveQualityGroup
- rctReceiverGroup
- rctSelectedChannelGroup
- rctSystemInterfaceGroup
- rctTemperatureGroup
- rctTransmitterGroup
- reciterAlarmsGroup
- systemAlarmsGroup