OID reference

igAdminStatus

1.3.6.1.4.1.5504.4.3.1.1.1.9

Description

GR-303-CORE The following requirements on status and control of the overall RDT and IDT may also be used during service assurance (e.g., placing out-of-service for maintenance purposes). Placing an RDT out-of-service means stopping it from providing access services to the customers. It does not mean cutting off commun…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.5504.4.3.1.1.1 (interfaceGroupEntry)
Node code
9
Node name
igAdminStatus
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.5504.4.3.1.1.1.9
URN notation
urn:oid:1.3.6.1.4.1.5504.4.3.1.1.1.9
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 5504 4 3 1 1 1 9}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneGR303(1) interfaceGroupTable(1) interfaceGroupEntry(1) igAdminStatus(9)}
OID-IRI notation
  • /1/3/6/1/4/1/5504/4/3/1/1/1/9
  • /ISO/Identified-Organization/6/1/4/1/5504/4/3/1/1/1/9
  • /ISO/3/6/1/4/1/5504/4/3/1/1/1/9
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/identified-organization/dod/internet/private/enterprise/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/identified-organization/dod/internet/private/enterprise/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/identified-organization/dod/internet/private/enterprises/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/identified-organization/dod/internet/private/enterprises/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/identified-organization/dod/internet/private/enterprises/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/org/dod/internet/private/enterprise/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/org/dod/internet/private/enterprise/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/org/dod/internet/private/enterprise/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • /iso/org/dod/internet/private/enterprises/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneGR303/interfaceGroupTable/interfaceGroupEntry/igAdminStatus
  • Additional combinations skipped.

SNMP properties

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

Enumerated values

ValueName
1inService
2outOfService

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. The index encoding is not inferred here.

Published row index: igNameId.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.5504.4.3.1.1.1.9

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.

igAdminStatus OBJECT-TYPE
            SYNTAX INTEGER
                {
                inService(1),
                outOfService(2)
                }
            MAX-ACCESS read-create
            STATUS current
            DESCRIPTION
                "GR-303-CORE The following requirements on status 
                and control of the overall RDT and IDT may also 
                be used during service assurance (e.g., placing 
                out-of-service for maintenance purposes). Placing
                an RDT out-of-service means stopping it from 
                providing access services to the customers. It 
                does not mean cutting off communication with a
                managing system (eg, ZMS) that controls the RDT.
                
                R5-20 [272] An RDT shall receive from a remote 
                managing system (eg, ZMS) and process requests
                to place the RDT out-of-service or in-service.
                An RDT shall confirm with the managing system
                before executing the request to place the system 
                out-of-service.
                
                R5-21 [273] An RDT shall receive from a remote
                managing system (eg, ZMS) and process requests 
                to retrieve the servic status of the RDT (in
                or out of service).
                
                Valid values are InService and OutOfService.
                
                When an Interface Group is in outOfService state,
                it is removed from the GR303 protocol stack and
                is no longer installed on a specific card.
                
                This field is mandatory for IG row creation."
            REFERENCE
                "GR-303-CORE R5-20 [272], R5-21 [273]"
            ::= { interfaceGroupEntry 9 }

Meaning

Descriptions

1 unique

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

GR-303-CORE The following requirements on status and control of the overall RDT and IDT may also be used during service assurance (e.g., placing out-of-service for maintenance purposes). Placing an RDT out-of-service means stopping it from providing access services to the customers. It does not mean cutting off communication with a managing system (eg, ZMS) that controls the RDT. R5-20 [272] An RDT shall receive from a remote managing system (eg, ZMS) and process requests to place the RDT out-of-service or in-service. An RDT shall confirm with the managing system before executing the request to place the system out-of-service. R5-21 [273] An RDT shall receive from a remote managing system (eg, ZMS) and process requests to retrieve the servic status of the RDT (in or out of service). Valid values are InService and OutOfService. When an Interface Group is in outOfService state, it is removed from the GR303 protocol stack and is no longer installed on a specific card. This field is mandatory for IG row creation.

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

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

Status in source: current.

Names: igAdminStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "igAdminStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "inService",
    "(",
    "1",
    ")",
    ",",
    "outOfService",
    "(",
    "2",
    ")",
    "}",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"GR-303-CORE The following requirements on status and control of the overall RDT and IDT may also be used during service assurance (e.g., placing out-of-service for maintenance purposes). Placing an RDT out-of-service means stopping it from providing access services to the customers. It does not mean cutting off communication with a managing system (eg, ZMS) that controls the RDT. R5-20 [272] An RDT shall receive from a remote managing system (eg, ZMS) and process requests to place the RDT out-of-service or in-service. An RDT shall confirm with the managing system before executing the request to place the system out-of-service. R5-21 [273] An RDT shall receive from a remote managing system (eg, ZMS) and process requests to retrieve the servic status of the RDT (in or out of service). Valid values are InService and OutOfService. When an Interface Group is in outOfService state, it is removed from the GR303 protocol stack and is no longer installed on a specific card. This field is mandatory for IG row creation.\"",
    "REFERENCE",
    "\"GR-303-CORE R5-20 [272], R5-21 [273]\"",
    "::=",
    "{",
    "interfaceGroupEntry",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "inService",
            1
          ],
          [
            "outOfService",
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "GR-303-CORE The following requirements on status and control of the overall RDT and IDT may also be used during service assurance (e.g., placing out-of-service for maintenance purposes). Placing an RDT out-of-service means stopping it from providing access services to the customers. It does not mean cutting off communication with a managing system (eg, ZMS) that controls the RDT. R5-20 [272] An RDT shall receive from a remote managing system (eg, ZMS) and process requests to place the RDT out-of-service or in-service. An RDT shall confirm with the managing system before executing the request to place the system out-of-service. R5-21 [273] An RDT shall receive from a remote managing system (eg, ZMS) and process requests to retrieve the servic status of the RDT (in or out of service). Valid values are InService and OutOfService. When an Interface Group is in outOfService state, it is removed from the GR303 protocol stack and is no longer installed on a specific card. This field is mandatory for IG row creation."
    ],
    [
      "REFERENCE",
      "GR-303-CORE R5-20 [272], R5-21 [273]"
    ],
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.5504)

Goldberg Allen

Siblings (17)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.5504.4.3.1.1.1.1 igNameId00
1.3.6.1.4.1.5504.4.3.1.1.1.2 igShelf00
1.3.6.1.4.1.5504.4.3.1.1.1.3 igSlot00
1.3.6.1.4.1.5504.4.3.1.1.1.4 igPeerShelf00
1.3.6.1.4.1.5504.4.3.1.1.1.5 igPeerSlot00
1.3.6.1.4.1.5504.4.3.1.1.1.6 igSwitchType00
1.3.6.1.4.1.5504.4.3.1.1.1.7 igPrimaryEocTmcDs1IfIndex00
1.3.6.1.4.1.5504.4.3.1.1.1.8 igSecondaryEocTmcDs1IfIndex00
1.3.6.1.4.1.5504.4.3.1.1.1.10 igOperationalStatus00
1.3.6.1.4.1.5504.4.3.1.1.1.11 igPeerStatus00
1.3.6.1.4.1.5504.4.3.1.1.1.12 igMaxConfigCalls00
1.3.6.1.4.1.5504.4.3.1.1.1.13 igCurrActiveCalls00
1.3.6.1.4.1.5504.4.3.1.1.1.14 igStatsTimeElapsed00
1.3.6.1.4.1.5504.4.3.1.1.1.15 igStatsValidIntervals00
1.3.6.1.4.1.5504.4.3.1.1.1.16 igStatsInvalidIntervals00
1.3.6.1.4.1.5504.4.3.1.1.1.17 igRowStatus00
1.3.6.1.4.1.5504.4.3.1.1.1.18 igWorkingMode00