APEX-MIB :: apexOutputTsConfPidRemappingMode

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsAPEX-MIBapexOutputTsConfPidRemappingMode

apexOutputTsConfPidRemappingMode

Module: APEX-MIB

OID (symbolic): APEX-MIB::apexOutputTsConfPidRemappingMode

OID (numeric): 1.3.6.1.4.1.1166.1.31.14.1.6.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The PID Remapping mode setting.

When 'disabled', the output PIDs for all services and ancillary PIDs are the same as the input PID values. This scheme can only be used when either mapping an entire MPTS to a QAM output or when SPTS are mapped and the user has already ensured that all of the PIDs across all inputs mapped to the same output stream are unique.

When 'remapWithoutReuse', the APEX will determine the output PIDs from a predetermined range of PIDs for services and ancillary PIDs. The APEX will use a scheme to limit the reuse of service PIDs for each service mapping. This scheme MUST be used for outputs in Session Control mode and in normally in UDP Port Mapping mode (exception noted below). When receiving SPTS inputs, in order to ensure there are no PID conflicts, this scheme should be selected.

When 'remapProgramBased', the APEX will determine the output PIDs from a predetermined range of PIDs for services and ancillary PIDs. The APEX uses a scheme to select the PMT PID based on the program number. The PMT PID is calculated as follows: (Program Number + 1) * 16.

The component PIDs are sequential after the PMT PID. This scheme only allows for a total of 15 component PIDs per program. Output program numbers are also limited (1-256). This scheme is intended to be used when in UDP Port Mapping mode at specific sites.

When 'unrestricted', the APEX will allocate output PIDs as long as they are needed using the whole available PIDs range, unlike other pid-remapping modes where PID values are internally pre-allocated for different uses (PMT, components, ECM, ...). This scheme is only recommended for cases when the user need a special pre-assigned EMM pid that can't be configured in the other pid-remapping modes.

PID Remapping mode changes can only occur when the output is not in use (no service, PID, or stream mapping active to the output).

What is apexOutputTsConfPidRemappingMode?

Controls whether output PIDs are remapped to new values or passed through unchanged from the input stream. When disabled, output PIDs match the input PIDs exactly; when enabled, the device assigns new PID values to avoid conflicts.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1166.1.31.14.1.6.1.2
snmpwalk -v2c -c public <target> APEX-MIB::apexOutputTsConfPidRemappingMode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1166.1.31.14.1.6.1.2.1
snmpget -v2c -c public <target> APEX-MIB::apexOutputTsConfPidRemappingMode.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.1166.1.31.14.1.6.1.2.1 i <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::apexOutputTsConfPidRemappingMode 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.14apexOutputTransportAPEX-MIB
1.3.6.1.4.1.1166.1.31.14.1apexOutputTsConfigAPEX-MIB
1.3.6.1.4.1.1166.1.31.14.1.6apexOutputTsConfigTableAPEX-MIB
1.3.6.1.4.1.1166.1.31.14.1.6.1apexOutputTsConfigEntryAPEX-MIB
1.3.6.1.4.1.1166.1.31.14.1.6.1.2apexOutputTsConfPidRemappingModeAPEX-MIB