OID reference

apexOutputTsConfPidRemappingMode

1.3.6.1.4.1.1166.1.31.14.1.6.1.2

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 mapp…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1166.1.31.14.1.6.1 (apexOutputTsConfigEntry)
Node code
2
Node name
apexOutputTsConfPidRemappingMode
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1166.1.31.14.1.6.1.2
URN notation
urn:oid:1.3.6.1.4.1.1166.1.31.14.1.6.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1166 1 31 14 1 6 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) gi(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) giMIB(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) gi(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) giMIB(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) gi(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) giMIB(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) gi(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) giMIB(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) gi(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) giMIB(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) gi(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) giMIB(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) gi(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) giMIB(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) gi(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) giMIB(1166) giproducts(1) apex(31) apexOutputTransport(14) apexOutputTsConfig(1) apexOutputTsConfigTable(6) apexOutputTsConfigEntry(1) apexOutputTsConfPidRemappingMode(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1166/1/31/14/1/6/1/2
  • /ISO/Identified-Organization/6/1/4/1/1166/1/31/14/1/6/1/2
  • /ISO/3/6/1/4/1/1166/1/31/14/1/6/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1166/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/identified-organization/dod/internet/private/enterprise/gi/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/identified-organization/dod/internet/private/enterprise/giMIB/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/identified-organization/dod/internet/private/enterprises/1166/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/identified-organization/dod/internet/private/enterprises/gi/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/identified-organization/dod/internet/private/enterprises/giMIB/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1166/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/gi/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/giMIB/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/1166/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/gi/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/giMIB/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/org/dod/internet/private/enterprise/1166/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/org/dod/internet/private/enterprise/gi/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/org/dod/internet/private/enterprise/giMIB/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • /iso/org/dod/internet/private/enterprises/1166/giproducts/apex/apexOutputTransport/apexOutputTsConfig/apexOutputTsConfigTable/apexOutputTsConfigEntry/apexOutputTsConfPidRemappingMode
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current

Enumerated values

ValueName
1disabled
2remapWithoutReuse
3remapProgramBased
4remapProgramBased2
5unrestricted

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In APEX-MIB, the row index apexOutputTsConfOutputTsNum is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1166.1.31.14.1.6.1.2.<apexOutputTsConfOutputTsNum>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1166.1.31.14.1.6.1.2

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

apexOutputTsConfPidRemappingMode OBJECT-TYPE
    SYNTAX INTEGER
        {
         disabled          (1),
         remapWithoutReuse (2),
         remapProgramBased (3),
         remapProgramBased2 (4),
         unrestricted (5)
        }
    MAX-ACCESS read-write
    STATUS current
    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).
        "
::= { apexOutputTsConfigEntry 2 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

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).

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

apexOutputTsConfPidRemappingMode · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: apexOutputTsConfPidRemappingMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "apexOutputTsConfPidRemappingMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "disabled",
    "(",
    "1",
    ")",
    ",",
    "remapWithoutReuse",
    "(",
    "2",
    ")",
    ",",
    "remapProgramBased",
    "(",
    "3",
    ")",
    ",",
    "remapProgramBased2",
    "(",
    "4",
    ")",
    ",",
    "unrestricted",
    "(",
    "5",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "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). \"",
    "::=",
    "{",
    "apexOutputTsConfigEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "disabled",
            1
          ],
          [
            "remapWithoutReuse",
            2
          ],
          [
            "remapProgramBased",
            3
          ],
          [
            "remapProgramBased2",
            4
          ],
          [
            "unrestricted",
            5
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "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)."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1166)

Fred Gotwald

Siblings (8)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1166.1.31.14.1.6.1.1 apexOutputTsConfOutputTsNum00
1.3.6.1.4.1.1166.1.31.14.1.6.1.3 apexOutputTsConfOperatingMode00
1.3.6.1.4.1.1166.1.31.14.1.6.1.4 apexOutputTsConfOutPatTsId00
1.3.6.1.4.1.1166.1.31.14.1.6.1.5 apexOutputTsConfPsipEnable00
1.3.6.1.4.1.1166.1.31.14.1.6.1.6 apexOutputTsConfEncryptionType00
1.3.6.1.4.1.1166.1.31.14.1.6.1.7 apexOutputTsConfSimulcryptMode00
1.3.6.1.4.1.1166.1.31.14.1.6.1.8 apexOutputTsConfPcrLess00
1.3.6.1.4.1.1166.1.31.14.1.6.1.9 apexOutputTsConfAutoSDTEnable00