APEX-MIB :: apexGbeConfLossOfInputTsType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsAPEX-MIBapexGbeConfLossOfInputTsType

apexGbeConfLossOfInputTsType

Module: APEX-MIB

OID (symbolic): APEX-MIB::apexGbeConfLossOfInputTsType

OID (numeric): 1.3.6.1.4.1.1166.1.31.7.1.1.12

Node type: OBJECT-TYPE

Type: RateComparisonTYPE

Access: read-write

Description: Loss of input stream type. Determines if detection of loss of an input stream is based on data rate or stream rate. Data rate includes only non-null MPEG packets (such as video and audio packets). Stream rate includes all packets, including null packets. The loss of an input stream uses the timeout value for the specific input (unicast or multicast) and the input type. If no packets are received within the specified timeout value, taking into account the loss of input type checking, then the input stream is determined to be missing.

Data rate should be used for detecting loss of input when the input stream is normally null filled. When a user requires notification of a loss of input stream when there is no content streamed, data rate should be selected.

Stream rate should be used for detecting loss of input stream when the user requires to be notified when there is no input stream at all being received.

Loss of input is used for determining all SDV failover conditions. It is also used for Manual Routing failover conditions when using hot/warm transport stream redundancy.

Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter.

@Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

What is apexGbeConfLossOfInputTsType?

Determines whether loss-of-input detection on GbE interfaces is based on the overall stream data rate (including null MPEG packets) or only the payload data rate (excluding null packets). The chosen method affects how quickly and accurately the device detects a missing input transport stream.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1166.1.31.7.1.1.12
snmpwalk -v2c -c public <target> APEX-MIB::apexGbeConfLossOfInputTsType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1166.1.31.7.1.1.12.1
snmpget -v2c -c public <target> APEX-MIB::apexGbeConfLossOfInputTsType.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.1166.1.31.7.1.1.12.1 s <value>

Start monitoring BigBand Networks APEX video/broadband gateway (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the APEX-MIB::apexGbeConfLossOfInputTsType OID value, configure state conditions and alerts, and monitor any BigBand Networks APEX video/broadband gateway (legacy) 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.1166giBCS-IDENT-MIB
1.3.6.1.4.1.1166.1giproductsBCS-IDENT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1166.1.31apexAPEX-MIB
1.3.6.1.4.1.1166.1.31.7apexGbeAPEX-MIB
1.3.6.1.4.1.1166.1.31.7.1apexGbeConfigAPEX-MIB
1.3.6.1.4.1.1166.1.31.7.1.1apexGbeConfigGeneralAPEX-MIB
1.3.6.1.4.1.1166.1.31.7.1.1.12apexGbeConfLossOfInputTsTypeAPEX-MIB