OID reference

arrisMtaDevLoopVoltagePolicy

1.3.6.1.4.1.4115.1.3.3.1.2.3.11.2

Description

1. Maintain loop idle voltage at all times. 2. Apply loop idle voltage at all times except when no RF QAM carrier is detected. The intent of this policy option is to maintain idle voltage for all normal operation but to remove it if RF conditions appear to match a malicious cable cut (such may happen if a burglar is t…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.4115.1.3.3.1.2.3.11 (arrisMtaDevLoopVoltageMgmt)
Node code
2
Node name
arrisMtaDevLoopVoltagePolicy
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.4115.1.3.3.1.2.3.11.2
URN notation
urn:oid:1.3.6.1.4.1.4115.1.3.3.1.2.3.11.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 4115 1 3 3 1 2 3 11 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisMtaDevMib(3) arrisMtaDevMibObjects(1) arrisMtaDevSetup(2) arrisMtaDevOperationalSetup(3) arrisMtaDevLoopVoltageMgmt(11) arrisMtaDevLoopVoltagePolicy(2)}
OID-IRI notation
  • /1/3/6/1/4/1/4115/1/3/3/1/2/3/11/2
  • /ISO/Identified-Organization/6/1/4/1/4115/1/3/3/1/2/3/11/2
  • /ISO/3/6/1/4/1/4115/1/3/3/1/2/3/11/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/4115/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/identified-organization/dod/internet/private/enterprise/arris/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/identified-organization/dod/internet/private/enterprises/4115/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/identified-organization/dod/internet/private/enterprises/arris/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/4115/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/arris/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/identified-organization/dod/internet/private/vendor-objects/4115/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/identified-organization/dod/internet/private/vendor-objects/arris/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/org/dod/internet/private/enterprise/4115/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/org/dod/internet/private/enterprise/arris/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/org/dod/internet/private/enterprises/4115/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/org/dod/internet/private/enterprises/arris/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/org/dod/internet/private/ldap-enterprise/4115/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/org/dod/internet/private/ldap-enterprise/arris/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/org/dod/internet/private/vendor-objects/4115/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • /iso/org/dod/internet/private/vendor-objects/arris/arrisProducts/arrisProdIdCM/arrisMtaDevMib/arrisMtaDevMibObjects/arrisMtaDevSetup/arrisMtaDevOperationalSetup/arrisMtaDevLoopVoltageMgmt/arrisMtaDevLoopVoltagePolicy
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
default-operation

Enumerated values

ValueName
1always-voltage-present
2rf-carrier-voltage-present
3in-service-voltage-present
4default-operation

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.4115.1.3.3.1.2.3.11.2.0

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.

arrisMtaDevLoopVoltagePolicy OBJECT-TYPE
     SYNTAX INTEGER {
         always-voltage-present(1),
         rf-carrier-voltage-present(2),
         in-service-voltage-present(3),
         default-operation(4)
     }
     MAX-ACCESS read-write
     STATUS current
     DESCRIPTION 
         "1. Maintain loop idle voltage at all times.
          2. Apply loop idle voltage at all times except when no RF QAM carrier is
             detected.   The intent of this policy option is to maintain idle
             voltage for all normal operation but to remove it if RF conditions
             appear to match a malicious cable cut (such may happen if a burglar is
             trying to disable the alarm system).
          3. Apply loop idle voltage only when the MTA device  is In-service (MTA IP
             address is received and valid config file has been received) and during
             manually initiated resets (either reset button or SNMP).  If this policy
             criterion is selected, then the EMTA MUST maintain loop idle voltage if a
             reset command is received (via SNMP or reset button or as part of a
             management initiated software upgrade).  Once the MTA has come back in-
             service,  any subsequent MTA out-of-service condition MUST result in
             removal of loop idle voltage (except for another manually initiated reset).
             As a failsafe, if the MTA has not come in-service within a provisionable
             time, then loop idle voltage MUST be removed.
          4. Apply loop idle voltage whenever the MTA device is in-service.
          5. This MIB is only writable via configuration file."
     DEFVAL { default-operation }
     ::= { arrisMtaDevLoopVoltageMgmt 2 }

Meaning

Descriptions

1 unique

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

1. Maintain loop idle voltage at all times. 2. Apply loop idle voltage at all times except when no RF QAM carrier is detected. The intent of this policy option is to maintain idle voltage for all normal operation but to remove it if RF conditions appear to match a malicious cable cut (such may happen if a burglar is trying to disable the alarm system). 3. Apply loop idle voltage only when the MTA device is In-service (MTA IP address is received and valid config file has been received) and during manually initiated resets (either reset button or SNMP). If this policy criterion is selected, then the EMTA MUST maintain loop idle voltage if a reset command is received (via SNMP or reset button or as part of a management initiated software upgrade). Once the MTA has come back in- service, any subsequent MTA out-of-service condition MUST result in removal of loop idle voltage (except for another manually initiated reset). As a failsafe, if the MTA has not come in-service within a provisionable time, then loop idle voltage MUST be removed. 4. Apply loop idle voltage whenever the MTA device is in-service. 5. This MIB is only writable via configuration file.

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

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

Status in source: current.

Names: arrisMtaDevLoopVoltagePolicy

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "arrisMtaDevLoopVoltagePolicy",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "always-voltage-present",
    "(",
    "1",
    ")",
    ",",
    "rf-carrier-voltage-present",
    "(",
    "2",
    ")",
    ",",
    "in-service-voltage-present",
    "(",
    "3",
    ")",
    ",",
    "default-operation",
    "(",
    "4",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"1. Maintain loop idle voltage at all times. 2. Apply loop idle voltage at all times except when no RF QAM carrier is detected. The intent of this policy option is to maintain idle voltage for all normal operation but to remove it if RF conditions appear to match a malicious cable cut (such may happen if a burglar is trying to disable the alarm system). 3. Apply loop idle voltage only when the MTA device is In-service (MTA IP address is received and valid config file has been received) and during manually initiated resets (either reset button or SNMP). If this policy criterion is selected, then the EMTA MUST maintain loop idle voltage if a reset command is received (via SNMP or reset button or as part of a management initiated software upgrade). Once the MTA has come back in- service, any subsequent MTA out-of-service condition MUST result in removal of loop idle voltage (except for another manually initiated reset). As a failsafe, if the MTA has not come in-service within a provisionable time, then loop idle voltage MUST be removed. 4. Apply loop idle voltage whenever the MTA device is in-service. 5. This MIB is only writable via configuration file.\"",
    "DEFVAL",
    "{",
    "default-operation",
    "}",
    "::=",
    "{",
    "arrisMtaDevLoopVoltageMgmt",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "always-voltage-present",
            1
          ],
          [
            "rf-carrier-voltage-present",
            2
          ],
          [
            "in-service-voltage-present",
            3
          ],
          [
            "default-operation",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "1. Maintain loop idle voltage at all times. 2. Apply loop idle voltage at all times except when no RF QAM carrier is detected. The intent of this policy option is to maintain idle voltage for all normal operation but to remove it if RF conditions appear to match a malicious cable cut (such may happen if a burglar is trying to disable the alarm system). 3. Apply loop idle voltage only when the MTA device is In-service (MTA IP address is received and valid config file has been received) and during manually initiated resets (either reset button or SNMP). If this policy criterion is selected, then the EMTA MUST maintain loop idle voltage if a reset command is received (via SNMP or reset button or as part of a management initiated software upgrade). Once the MTA has come back in- service, any subsequent MTA out-of-service condition MUST result in removal of loop idle voltage (except for another manually initiated reset). As a failsafe, if the MTA has not come in-service within a provisionable time, then loop idle voltage MUST be removed. 4. Apply loop idle voltage whenever the MTA device is in-service. 5. This MIB is only writable via configuration file."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "default-operation"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.4115)

Wynn Robert

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.4115.1.3.3.1.2.3.11.1 arrisMtaDevLoopVoltageKey00
1.3.6.1.4.1.4115.1.3.3.1.2.3.11.3 arrisMtaDevLoopVoltageResetTimeout00
1.3.6.1.4.1.4115.1.3.3.1.2.3.11.4 arrisMtaDevLoopVoltageMaintTimeout00