OID reference

apexQamRfConfigTable

1.3.6.1.4.1.1166.1.31.8.1.4

Description

Table of configuration items configurable on a QAM RF Port basis. There can be up to 12 RF Ports on an APEX1000 depending on how the 3 QAM slots are populated. There can be 2 or 4 RF Ports in each QAM slot. The 2 RF Ports in a 2x8(2x4) QAM module (1,2) in a QAM slot are mapped to table rows as follows: Slot Rows (RF p…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1166.1.31.8.1 (apexQamConfig)
Node code
4
Node name
apexQamRfConfigTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1166.1.31.8.1.4
URN notation
urn:oid:1.3.6.1.4.1.1166.1.31.8.1.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1166 1 31 8 1 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) gi(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) giMIB(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) gi(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) giMIB(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) gi(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) giMIB(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) gi(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) giMIB(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) gi(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) giMIB(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) gi(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) giMIB(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) gi(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) giMIB(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) gi(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) giMIB(1166) giproducts(1) apex(31) apexQam(8) apexQamConfig(1) apexQamRfConfigTable(4)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1166/1/31/8/1/4
  • /ISO/Identified-Organization/6/1/4/1/1166/1/31/8/1/4
  • /ISO/3/6/1/4/1/1166/1/31/8/1/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1166/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/identified-organization/dod/internet/private/enterprise/gi/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/identified-organization/dod/internet/private/enterprise/giMIB/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/identified-organization/dod/internet/private/enterprises/1166/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/identified-organization/dod/internet/private/enterprises/gi/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/identified-organization/dod/internet/private/enterprises/giMIB/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1166/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/gi/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/giMIB/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/1166/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/gi/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/giMIB/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/org/dod/internet/private/enterprise/1166/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/org/dod/internet/private/enterprise/gi/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/org/dod/internet/private/enterprise/giMIB/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • /iso/org/dod/internet/private/enterprises/1166/giproducts/apex/apexQam/apexQamConfig/apexQamRfConfigTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF ApexQamRfConfigEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

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.

apexQamRfConfigTable OBJECT-TYPE
    SYNTAX SEQUENCE OF ApexQamRfConfigEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
        "Table of configuration items configurable on a QAM RF Port basis.

         There can be up to 12 RF Ports on an APEX1000 depending on how the 3
         QAM slots are populated. There can be 2 or 4 RF Ports in each QAM slot.
         
         The 2 RF Ports in a 2x8(2x4) QAM module (1,2) in a QAM slot are mapped
         to table rows as follows:
         
               Slot        Rows (RF port)
                1          1,2
                2          3,4
                3          5,6

         If a QAM Module in a slot only has 2 RF ports, the first three rows
         in this table for that slot are to be used.  For example, if there
         is a 2x4 or 2x8 module in slot 3, port 5 and 6  are to be used for
         configuring the RF Ports of the module.
         
         The 4 RF Ports in a 4x4 QAM module (1,2,7,8) in a QAM slot are mapped
         to table rows as follows:
               Slot        Rows (RF port)
                1          1,2,7,8
                2          3,4,9,10
                3          5,6,11,12

         All entries/rows in this table are used for the 4x4 QAM Module with
         any exceptions noted in the descriptions for the table entries.
         
         All entries in this table have the same ranges for the 4x4 QAM Module
         with any exceptions noted in the descriptions for the table entries.
         
         Refer to the description of apexQamChannelConfigTable for information
         on QAM Channel to RF Port mapping.
         
         Tables apexQamRfPortChannelInfoTable and apexQamChannelIdTable can be
         used to assist in referencing between QAM slots, RF Ports, and QAM
         Channels (Output Transport Streams) for the installed modules.
         
         Once written, the change to this table will only take immediate
         effect after apexQamConfigApplyChange is set to 'apply'.  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)
         @Commit(param=apexQamConfigApplyChange, value=2)
         @Save(apexSaveConfig, value=2)
         @File(config.ini, type='ini')
        "
::= { apexQamConfig 4 }

Meaning

Descriptions

1 unique

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

Table of configuration items configurable on a QAM RF Port basis. There can be up to 12 RF Ports on an APEX1000 depending on how the 3 QAM slots are populated. There can be 2 or 4 RF Ports in each QAM slot. The 2 RF Ports in a 2x8(2x4) QAM module (1,2) in a QAM slot are mapped to table rows as follows: Slot Rows (RF port) 1 1,2 2 3,4 3 5,6 If a QAM Module in a slot only has 2 RF ports, the first three rows in this table for that slot are to be used. For example, if there is a 2x4 or 2x8 module in slot 3, port 5 and 6 are to be used for configuring the RF Ports of the module. The 4 RF Ports in a 4x4 QAM module (1,2,7,8) in a QAM slot are mapped to table rows as follows: Slot Rows (RF port) 1 1,2,7,8 2 3,4,9,10 3 5,6,11,12 All entries/rows in this table are used for the 4x4 QAM Module with any exceptions noted in the descriptions for the table entries. All entries in this table have the same ranges for the 4x4 QAM Module with any exceptions noted in the descriptions for the table entries. Refer to the description of apexQamChannelConfigTable for information on QAM Channel to RF Port mapping. Tables apexQamRfPortChannelInfoTable and apexQamChannelIdTable can be used to assist in referencing between QAM slots, RF Ports, and QAM Channels (Output Transport Streams) for the installed modules. Once written, the change to this table will only take immediate effect after apexQamConfigApplyChange is set to 'apply'. 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) @Commit(param=apexQamConfigApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

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

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

Status in source: current.

Names: apexQamRfConfigTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "apexQamRfConfigTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "ApexQamRfConfigEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Table of configuration items configurable on a QAM RF Port basis. There can be up to 12 RF Ports on an APEX1000 depending on how the 3 QAM slots are populated. There can be 2 or 4 RF Ports in each QAM slot. The 2 RF Ports in a 2x8(2x4) QAM module (1,2) in a QAM slot are mapped to table rows as follows: Slot Rows (RF port) 1 1,2 2 3,4 3 5,6 If a QAM Module in a slot only has 2 RF ports, the first three rows in this table for that slot are to be used. For example, if there is a 2x4 or 2x8 module in slot 3, port 5 and 6 are to be used for configuring the RF Ports of the module. The 4 RF Ports in a 4x4 QAM module (1,2,7,8) in a QAM slot are mapped to table rows as follows: Slot Rows (RF port) 1 1,2,7,8 2 3,4,9,10 3 5,6,11,12 All entries/rows in this table are used for the 4x4 QAM Module with any exceptions noted in the descriptions for the table entries. All entries in this table have the same ranges for the 4x4 QAM Module with any exceptions noted in the descriptions for the table entries. Refer to the description of apexQamChannelConfigTable for information on QAM Channel to RF Port mapping. Tables apexQamRfPortChannelInfoTable and apexQamChannelIdTable can be used to assist in referencing between QAM slots, RF Ports, and QAM Channels (Output Transport Streams) for the installed modules. Once written, the change to this table will only take immediate effect after apexQamConfigApplyChange is set to 'apply'. 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) @Commit(param=apexQamConfigApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini') \"",
    "::=",
    "{",
    "apexQamConfig",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "ApexQamRfConfigEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Table of configuration items configurable on a QAM RF Port basis. There can be up to 12 RF Ports on an APEX1000 depending on how the 3 QAM slots are populated. There can be 2 or 4 RF Ports in each QAM slot. The 2 RF Ports in a 2x8(2x4) QAM module (1,2) in a QAM slot are mapped to table rows as follows: Slot Rows (RF port) 1 1,2 2 3,4 3 5,6 If a QAM Module in a slot only has 2 RF ports, the first three rows in this table for that slot are to be used. For example, if there is a 2x4 or 2x8 module in slot 3, port 5 and 6 are to be used for configuring the RF Ports of the module. The 4 RF Ports in a 4x4 QAM module (1,2,7,8) in a QAM slot are mapped to table rows as follows: Slot Rows (RF port) 1 1,2,7,8 2 3,4,9,10 3 5,6,11,12 All entries/rows in this table are used for the 4x4 QAM Module with any exceptions noted in the descriptions for the table entries. All entries in this table have the same ranges for the 4x4 QAM Module with any exceptions noted in the descriptions for the table entries. Refer to the description of apexQamChannelConfigTable for information on QAM Channel to RF Port mapping. Tables apexQamRfPortChannelInfoTable and apexQamChannelIdTable can be used to assist in referencing between QAM slots, RF Ports, and QAM Channels (Output Transport Streams) for the installed modules. Once written, the change to this table will only take immediate effect after apexQamConfigApplyChange is set to 'apply'. 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) @Commit(param=apexQamConfigApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1166)

Fred Gotwald

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1166.1.31.8.1.4.1 apexQamRfConfigEntry1616

Siblings (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1166.1.31.8.1.1 apexQamConfigGeneral11
1.3.6.1.4.1.1166.1.31.8.1.2 apexQamModuleUpgrade33
1.3.6.1.4.1.1166.1.31.8.1.3 apexQamConfigApplyTable13
1.3.6.1.4.1.1166.1.31.8.1.5 apexQamChannelConfigTable14
1.3.6.1.4.1.1166.1.31.8.1.6 apexQamRfRedundancyConfig110
1.3.6.1.4.1.1166.1.31.8.1.7 apexQamChannelConfigApplyTable13